I want to second Bob Braden's pithy observation re I-Ds. If they make it through the process and become RFCs (including informational RFCs) then they clearly merit retention and they achieve it, since RFcs are archival. However, many I-Ds do not make it through the process and to archive them may seem to elevate them to a status that they have not merited. I don't mean to suggest that these documents have not value. The next author of a book on the history of IETF standards would certainly find them of great value. But, I don't want to see them cited in some product marketing data sheet, further confusing folks who already are confused by the fact that all standards are RFCs, but not all RFCs are standards ... Steve
- Re: An Internet Draft as reference material Simon St.Laurent
- Re: An Internet Draft as reference material Robert Elz
- Re: An Internet Draft as reference material Simon St.Laurent
- Re: An Internet Draft as reference material John Stracke
- Re: An Internet Draft as reference material Keith Moore
- Re: An Internet Draft as reference material Rob Lanphier
- Re: An Internet Draft as reference material Dave Crocker
- Re: An Internet Draft as reference material Mark Allman
- Re: An Internet Draft as reference material Ole J. Jacobsen
- Re: An Internet Draft as reference material Garrett Wollman
- Re: An Internet Draft as reference material Stephen Kent
- Re: An Internet Draft as reference material Dave Crocker
- Re: An Internet Draft as reference material Pete Loshin
- Re: An Internet Draft as reference material Stephen Kent
- Re: An Internet Draft as reference material Greg Minshall
- Re: An Internet Draft as reference material Tim Salo
- Re: An Internet Draft as reference material Stephen Kent
- Re: An Internet Draft as reference material Bob Braden
- Re: An Internet Draft as reference material Vernon Schryver
- Re: An Internet Draft as reference material RJ Atkinson
- Re: An Internet Draft as reference material Randy Bush
