RE: Last Call: Tags for the Identification of Languages to BCP

At 03:12 PM 10/20/00 -0700, Dan Kohn wrote:
> This is the normal way standards progress through maturity, as otherwise
> issuing any new RFC would require dozens or hundreds of other RFCs to be
> simultaneously reissued.
It would be normal if the RFC 1766 was being replaced by a
standard track document.  However, the proposal is to replace
RFC 1766 with a BCP.  This implies that RFC 1766 and all standard
track documents with normative references to RFC 1766 will be
moved to Historic status.

Kurt