Nice, but make sure to "replace" the URL when adding the user query (= don't "push"), otherwise the user has to press back many times before he can leave the website again
This works by loading a bunch of JSON on page load, and then do search on the client side in that json blob. I think it's fine, but I have looked into something similar to do as a toy project for learning postgres FTS by fetching an API provided by ietf, storing the data and doing search on the stored data. However, I couldn't find a straightforward API provided by IETF, and I was super surprised. Similarly I would also have liked a similar straightforward API from W3C for documents.
Out of the 45 search results, the most relevant one (the UDP RFC itself) was all the way at the bottom, listed as "RFC0768" and tagged as "legacy". (I'm not sure what legacy actually means here?)
This site does seem genuinely useful, but I think the UX could really use some polishing here, especially since I literally followed through with one of the example queries in the middle of the homepage.
"Legacy" here means that it (substantially) pre-dates the IETF deciding it needs the arrangement described in RFC 4844
Today a document like RFC 768 would most likely be the product of an IETF Working Group (possibly after being initially drafted outside and then adopted). In some cases an Area Director might authorise somebody to write a document without the Working Group process under their direct sponsorship instead. Together these form the IETF stream. This stream is the only means by which the IETF produces "standards track" documents, although it can also produce other documents from this stream.
Two other related groups, the IAB and IRTF, might create documents the RFC Editor cares about, they have their own streams. For example RFC 4844 is from the IAB stream.
Finally there are Individual Submissions. Sometimes these are documents nobody in any Working Group or Area cares about, occasionally they are documents a Working Group abandoned because it was unable to reach consensus and those who favoured the document finished it up as an Individual Submission. In some cases they're documenting a thing the authors would like to be public, just to get it down on paper.
The "Legacy" indication just means RFC 768 is too old to be classified by stream, the whole idea didn't exist back then.
So for most viewers of the site (who don't know and don't care about the IETF process), "legacy" is just misleading as it doesn't have the meaning they expect.
Thanks. The back/history feedback has been (hopefully) addressed.
I've been thinking about doing authors. The constraint is performance; the site loads the whole index, so adding author info would bloat the initial page load out (right now the index is about 2.2M, and GitHub Pages gzips it down to ~380k). The solution is probably to put author search, etc. on a separate page.
I searched for “SIP” as RFC3261 is my favorite, but there were hundreds of results in reverse numerical order, so RFC3261 which defines SIP was right at the bottom.
Maybe just reversing the result order would give more useful results?
