On Thu, 03 Jun 2004 11:04:06 PDT, Joe Touch said: > STD-5 is a nice choice - it actually refers to 6 different RFCs. > > So which one redirects to STD005.txt, and what is in it? > > (To see this noted in the RFCs themselves, see STD-62, which refers to a > set of 8 different RFCs.) > > And what happens when a STD is updated/revised? This is the IETF, we believe in rough consensus and running code. Note carefully that RFC2119 and RFC2026 are both BCP rather than Standard, indicating that even the meta-standard of how we produce standards is "running code" rather than an actual standard itself... ;) But anyhow, if we ever update STD005, we'll just do the obvious - create STD079 or whatever we're up to, stick an "Obsoletes: STD005" on it, and stick an "Obsoleted By: STD079" on STD005, and the RFC Editor will turn the crank and make sure all the appropriate indexes and webpages are updated to match. Again, this is all "running code" - we know how to issue an RFC that updates or obsoletes one (modulo the occasional corner case that crops up), and there's no obvious reason that the scheme that works for I-D, Draft, Proposed shouldn't work for a full Standard...
Attachment:
pgp00446.pgp
Description: PGP signature
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf