RE: Last Call: 'Tags for Identifying Languages' to BCP
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Last Call: 'Tags for Identifying Languages' to BCP



JFC,

  In March, 1995, when RFC 1766 was published, the BCP track did not exist.
The Standards Track was being used for things that were not protocols
and did not fit well into the 3-stage process.  Since BCPs are subject to
the same consensus judging and scrutiny as standards-track documents, it's
been common practice to obsolete old standards-track documents with BCPs
when it's reasonable to think that the original document would have been
a BCP if BCPs had existed at the time.

  Bill

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.