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.
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.
I would love to say rfc.me/bgp (for instance) and get what I’m looking for without wading through obsoleted RFCs. This would be a solid next step for the author. Significantly more work though.
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.
The way it is now, I imagine it took longer to purchase the domain name than it did to code up the redirect.
The back story here is that I purchased the domain in 2010, fully intending to have the same functionality back then, and each year since as I renewed it. So your sarcasm is absolutely warranted and welcome.
It did take all of 15 minutes fiddling with a mediocre RewriteRule to get the functionality I wanted.
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: http://rfcdothelp.herokuapp.com/
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.
Or if you're going to bookmark this website to go faster, why not just bookmark https://tools.ietf.org/html/rfc1000 ?