RE: Last Call: Tags for the Identification of Languages to BCP
Dan Kohn <dan@dankohn.com> Fri, 20 October 2000 22:20 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id SAA18851 for ietf-outbound.10@ietf.org; Fri, 20 Oct 2000 18:20:05 -0400 (EDT)
Received: from mgate-01.teledesic.com (mgate-01.teledesic.com [216.190.22.41]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17167 for <ietf@ietf.org>; Fri, 20 Oct 2000 18:12:08 -0400 (EDT)
Received: by mgate-01.teledesic.com with Internet Mail Service (5.5.2650.21) id <4GTP27SA>; Fri, 20 Oct 2000 15:12:29 -0700
Message-ID: <25D0C66E6D25D311B2AC0008C7913EE00105A072@tdmail2.teledesic.com>
From: Dan Kohn <dan@dankohn.com>
To: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>, ietf@ietf.org
Subject: RE: Last Call: Tags for the Identification of Languages to BCP
Date: Fri, 20 Oct 2000 15:12:08 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
X-Loop: ietf@ietf.org
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@dankohn.com> <http://www.dankohn.com> <tel:+1-650-327-2600> -----Original Message----- From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org] Sent: Friday, 2000-10-20 08:46 To: ietf@ietf.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@ietf.org or ietf@ietf.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
- Re: Last Call: Tags for the Identification of Lan… Kurt D. Zeilenga
- RE: Last Call: Tags for the Identification of Lan… Dan Kohn
- RE: Last Call: Tags for the Identification of Lan… Kurt D. Zeilenga
- RE: Last Call: Tags for the Identification of Lan… Kurt D. Zeilenga
- RE: Last Call: Tags for the Identification of Lan… Patrik Fältström
- Re: Last Call: Tags for the Identification of Lan… Harald Alvestrand
- RE: Last Call: Tags for the Identification of Lan… Kurt D. Zeilenga
- RE: Last Call: Tags for the Identification of Lan… Harald Alvestrand
- RE: Last Call: Tags for the Identification of Lan… Kurt D. Zeilenga