|
Two of us were working as UNIX developers on a project to add some internationalization
features to the email backend system for a large ISP. We were trying to identify
which RFCs needed to be consulted in order to spec
out how it should be implemented. It turns out that for email, there are a number of different specifications you need to look at. Different specifications talk about how the body of a message is encoded, how normal headers like the subject line are encoded, how filenames of attachments are encoded and how domain names are encoded. |
My partner in this effort suggested that "there ought to be a way" to see which
RFCs obsolete and update other RFCs, and the idea for the site was born. A
few long weekends of grinding out code and the site was up and running. Rfctree.com currently accepts no advertising. Its operating costs are paid for by a small commission we get from Amazon.com when you buy books or other products after clicking through our store page. It costs no more to go through the store page, but it will help to support rfctree.com. Thanks for your support! |
© 2006 Vance Gloster