Re: [Ltru] Issue #60: Require IETF Last Call for 2.2.1 (5) primary subtag case (Apps #12-b)

["Phillips, Addison" <addison at amazon.com>]

IETF LC would be inappropriate as an outcome for a language registration request. There already exists the appeals process, which has never been actually used (threatened, yes, but never used). The process seems to work. Elaborating it seems unnecessary.

It is also the case that a language rejected by ISO 639RA and by the expert subtag reviewer and presumably the ietf-languages@ consensus process and which is an exceptional registration (frowned at by our own preceding text), yet not in a way worthy of appeal on procedural grounds, is probably wholly inappropriate for an IETF LC.

Addison

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.


> -----Original Message-----
> From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On
> Behalf Of Randy Presuhn
> Sent: Monday, June 08, 2009 7:01 PM
> To: LTRU Working Group
> Subject: [Ltru] Issue #60: Require IETF Last Call for 2.2.1 (5)
> primary subtag case (Apps #12-b)
> 
> Hi -
> 
> Please note that this is the second half of apps review comment #12.
> Please do not confuse it with the first half of that same comment.
> 
> > 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 Team review
> ...
> > 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
> Section 3.5
> > >        and 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 might be a big deal, so this might actually require wider
> review,
> > such as IETF LC.
> ...
> 
> This is issue #60 in the tracker.
> http://trac.tools.ietf.org/wg/ltru/trac/ticket/60
> 
> Randy
> 
> 
> _______________________________________________
> Ltru mailing list
> Ltru at ietf.org
> https://www.ietf.org/mailman/listinfo/ltru