On Sun, 28 Aug 2005, Bruce Lilly wrote: > The only specific procedures for getting to Historic in 2026 are > in sections 6.2 and 6.3 and involve getting to Historic from the > Standards Track. Note that section 4.2.3 gives procedures for > Informational and Experimental RFCs, but that the only specific > procedures for Historic are in sections 6.2 and 6.3. RFC 2026 sets the rules for Internet standardization, i.e., it is authoritative with respect to the handling of standards or BCPs. So it's fair to conclude that the procedures in sections 6.2 and 6.3 are the only way for a standards-track document to get to Historic. However, RFC 2026 does not set the rules for non-standards track documents, as it explicitly says in Section 2.1. It is therefore incorrect to conclude from a lack of explicit mention of a mechanism in RFC 2026 that it is impermissible to publish an obsolete specification Historic without going through the standards track. There is a precedent, by the way: RFC 2341. Note that it postdates RFC 2026. //cmh _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf