[hats on]I currently have Kent, Peter, Mark, and myself down as against changes on this issue. Please express your preference (and the reasons for it) if you haven't already done so. If you have expressed your opinion, but I haven't considered it, please also say so.
Unless somebody expresses a preference (and reason) for making a change, I'll declare consensus on this issue tomorrow my morning.
Regards, Martin. On 2009/06/10 0:35, Mark Davis wrote:
+1 Mark On Tue, Jun 9, 2009 at 06:54, Peter Constable<petercon at microsoft.com>wrote:I've commented on this already: I don't see a need for any change. -----Original Message----- From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On Behalf Of Randy Presuhn Sent: Monday, June 08, 2009 6:57 PM To: LTRU Working Group Subject: [Ltru] Issue #59: replace RECOMMENDED language with MUST language in 2.2.1 (Apps #12a) Hi - Note well that there are two very distinct issues in Apps #12. This thread is the first of the two. PLEASE do not confuse them in your followups!From: "Alexey Melnikov"<alexey.melnikov at isode.com> To: "LTRU Working Group"<ltru at ietf.org> Cc: "Martin J. Dürst"<duerst at it.aoyama.ac.jp>; "Randy Presuhn"<randy_presuhn at mindspring.com>Sent: Saturday, June 06, 2009 1:14 PM Subject: Re: Additional issues with 4646bis raised by an Apps Review Teamreview ....12). In Section 2.2.1:5. Any language subtags of 5 to 8 characters in length in the IANA registry were defined via the registration process in Section3.5and MAY be used to form the primary language subtag. An example of what such a registration might include: one of the grandfathered IANA registrations is "i-enochian". The subtag 'enochian' could be registered in the IANA registry as a primary language subtag (assuming that ISO 639 does not register this language first), making tags such as "enochian-AQ" and"enochian-Latn" valid. At the time this document was created, there were no examples of this kind of subtag and future registrations of this type are discouraged: primary languages are strongly RECOMMENDED for registration with ISO 639,I suggest that the RECOMMENDED is changed to a MUST, i.e. an attempt to register it with ISO 639 must be made. Even if the outcome might be known, arguments given by ISO 639 might provide useful input to the Language Subtag Expert.and proposals rejected by ISO 639/ RA- JAC will be closely scrutinized by the Language Subtag Reviewer before they are registered with IANA.... This is filed as issue #59 in the tracker. http://trac.tools.ietf.org/wg/ltru/trac/ticket/59 Randy _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.ietf.org/mailman/listinfo/ltru _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.ietf.org/mailman/listinfo/ltru------------------------------------------------------------------------ _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.ietf.org/mailman/listinfo/ltru
-- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.