As you can see from Appendix B, all of the changes are backward compatible,
and so you would treat all references to RFC 1766 as referencing the new
specification instead.
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.
- dan
--
Dan Kohn <mailto:dan(_at_)dankohn(_dot_)com>
<http://www.dankohn.com> <tel:+1-650-327-2600>
-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt(_at_)OpenLDAP(_dot_)org]
Sent: Friday, 2000-10-20 08:46
To: ietf(_at_)ietf(_dot_)org
Subject: Re: Last Call: Tags for the Identification of Languages to BCP
At 10:23 AM 10/20/00 -0400, The IESG wrote:
The IESG has received a request to consider Tags for the Identification
of Languages <draft-alvestrand-lang-tag-v2-05.txt> as a BCP. This has
been reviewed in the IETF but is not the product of an IETF Working
Group.
This document will obsolete RFC1766, currently a Proposed Standard.
If RFC 1766 is obsoleted, wouldn't any Proposed Standard which has
a normative reference to RFC 1766 also be obsolete?
This would include RFC 2596 (Use of Language Codes in LDAP) and
likely others. Has anyone a complete list of Standard Track RFC
which have normative references to 1766? I believe that such
is needed to judge the impact of the proposal.
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send any comments to the
iesg(_at_)ietf(_dot_)org or ietf(_at_)ietf(_dot_)org mailing lists by November
20, 2000.
Files can be obtained via
http://www.ietf.org/internet-drafts/draft-alvestrand-lang-tag-v2-05.txt