[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltru] Issue #59: replace RECOMMENDED language withMUSTlanguage in 2.2.1 (Apps #12a)



Problems with the charset registry does not imply problems with the langtag registry. The problems that a change in wording *would* solve would be a case in which someone wants to register a primary language subtag and the LST Reviewer fails to ask that they go first to the JAC, or a case in which the requester is advised to check first with the JAC but they refuse to do so and IETF-languages doesn’t care, or a case in which they refuse to do that, IETF-languages rejects their request and the requester escalates to IESG. I don’t think there’s a real risk of these scenarios happening. (And the last would simply be a temporary inconvenience, not a lasting problem.)

 

 

Peter

 

From: mark.edward.davis at gmail.com [mailto:mark.edward.davis at gmail.com] On Behalf Of Mark Davis
Sent: Wednesday, June 10, 2009 9:54 AM
To: Peter Constable
Cc: debbie at ictmarketing.co.uk; Doug Ewell; LTRU Working Group
Subject: Re: [Ltru] Issue #59: replace RECOMMENDED language withMUSTlanguage in 2.2.1 (Apps #12a)

 

Oh, ask Mike Ksar about trying to get a response from the IETF charset registry!

But as I said, because the likelyhood of the text being invoked is so low, I'm ok with the current language, as imprecise as it is.

Mark

On Wed, Jun 10, 2009 at 08:25, Peter Constable <petercon at microsoft.com> wrote:

From: Debbie Garside [mailto:debbie at ictmarketing.co.uk]


>>What problem is being fixed here? (I don't know that we have an existing
problem.)

> It is a matter of clarity.  If we do not state that a requester MUST first
> apply to the ISO 639 JAC there will always be the awkward cuss who comes
> along and causes a huge rumpus - we have had our fair share of these and
> sometimes it is better to dot the i's and cross the t's.  It could save us a
> lot of time in the future.

You say, "we have had our fair share of these", but in over ten years participating in IETF-languages I don't recall any serious problems having arisen of the type we're discussing.



Peter

_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www.ietf.org/mailman/listinfo/ltru

 


Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.