This is amusing but is not really useful. Google + "RFC" + number seems faster.<p>Or if you're going to bookmark this website to go faster, why not just bookmark <a href="https://tools.ietf.org/html/rfc1000" rel="nofollow">https://tools.ietf.org/html/rfc1000</a> ?
Cool, but the documentation projects I really use often are ones that take the often antiquated presentation of the open-source site and puts it together in an easier-to-search/view way.<p>Example: <a href="http://docs.gl/" rel="nofollow">http://docs.gl/</a><p>What about...oh I dunno, maybe a few lists? By category, by number? Maybe a nice 'reader mode' for the actual .txt files? Sorry, maybe that's outside the scope of what you're going for here, I just don't usually mentally organize RFCs by their number. Instead I usually think, 'the RFC about TCP,' or whatever.
Wow, a URL redirect. Impressive. /s<p>If this is intended to actually be useful, you should follow the other suggestions here and add some lists (most popular) or categories (e-mail, web, routing protocols) or something.<p>The way it is now, I imagine it took longer to purchase the domain name than it did to code up the redirect.
I wrote a funny version of this once, that shows Lego sets with the same number as an RFC. Someone got a domain for it, but it appears to have lapsed: <a href="http://rfcdothelp.herokuapp.com/" rel="nofollow">http://rfcdothelp.herokuapp.com/</a>
Honestly, I can't consistently get the right version of RFCs (the tools.ietf.blah one) when I Google, so this is useful because I can actually remember the URL.