> -----Original Message----- > From: ietf-bounces@xxxxxxxx [mailto:ietf-bounces@xxxxxxxx] On > Behalf Of JFC (Jefsey) Morfin > Sent: Wednesday, August 24, 2005 5:03 AM > To: iesg@xxxxxxxx; ietf@xxxxxxxx > Subject: Re: Last Call: 'Tags for Identifying Languages' to BCP > > I would like to understand why > http://www.ietf.org/internet-drafts/draft-ietf-ltru-registry-12.txt > claims to be a BCP: it introduces a standard track proposition, > conflicting with current practices and development projects under way? > > I support it as a transition standard track RFC needed by some, as > long as it does not exclude more specific/advanced language > identification formats, processes or future IANA or ISO 11179 > conformant registries. In order to avoid conflicts, its ABNF should > be completed in dedicating a singleton to the general tag > URI > (http://www.ietf.org/internet-drafts/draft-kindberg-tag-uri-07.txt > accepted RFC). Jefsey, First, let's agree that you've asked this question [1], made this suggestion [2], and engaged in discussion of these topics on the LTRU working group mailing list. I know you haven't been happy with the way the discussion went, but these are not new topics. Agreed? Why a BCP? Production of this document is a direct requirement of the group charter: "This working group will address these issues by developing two documents. The first is a successor to RFC 3066." 3066 is BCP 47. The introduction and list of changes included in the document describe why and how it is obsoleting 3066. The ABNF suggestion has been discussed, partially accepted, and partially rejected by the working group. If you have new information to describe why you think the working group decision was a mistake, please describe it. -Scott- LTRU Area Advisor [1] http://www1.ietf.org/mail-archive/web/ltru/current/msg03360.html [2] http://www1.ietf.org/mail-archive/web/ltru/current/msg03196.html _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf