![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
*> *> Is it possible the IETF will keep a repository *> of expired working documents? or is it a non *> affordable cost? *> *> Alessio, If you start an (official) repository for expired Internet Drafts, they aren't expired any more (!), and you have created a new archival document series in parallel to RFCs. The Internet technical community has a 15-year old consensus that this would generally be a bad idea. [Like most other IETF/Internet ideas, this one resulted from actual experience; at one point there was a separate document series called the IENs (Internet Experiment Notes) in parallel with RFCs, and the result was considerable confusion.] *> I just note that in order to prevent the loss *> of the "Two bits differentiated services architecture" *> the authors submitted it as a non std track RFC. *> This is exactly the right thing to do. Working documents that contain useful information should be published as Informational RFCs. Or, if their importance lies more in their style than their content, perhaps you should consider submitting them to CCR or IEEE Networks or ... Bob Braden *> Alessio *> *> PS there was an article about working documents *> getting lost on an issue of IEEE Networks, *> and I share the concerns of its author. *>
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.