Re: [Ltru] draft-21 mod: move RFC 4645 reference to informative

[Mark Davis <mark at macchiato.com>]

Just so we are all on the same page, the v21 text is:

UN numeric codes and ISO 3166-1 alpha-2 codes for countries or areas listed as eligible for registration in Section 4 of [RFC4645] (Ewell, D., "Initial Language Subtag Registry," September 2006.) but not presently registered MAY be entered into the IANA registry via the process described in Section 3.5 (Registration Procedure for Subtags). Once registered, these codes MAY be used to form language tags.

http://inter-locale.com/ID/draft-ietf-ltru-4646bis-20.html#region

I think the minimal change is:

UN numeric codes and ISO 3166-1 alpha-2 codes for countries or areas listed as eligible for registration in Section 4 of [RFC4645] (Ewell, D., "Initial Language Subtag Registry," September 2006.) but not presently registered MAY be entered into the IANA registry via the process described in Section 3.5 (Registration Procedure for Subtags), subject to provision D. Once registered, these codes MAY be used to form language tags.

While I think we are all clear that provision D limits provision E -- that is, that if ISO adds a code XX for 830, then 830 could no longer be registered -- we should make it very clear in the document. Once we do that, we can leave the rest of the information alone.

Mark

[Side note for some future version -- NOT for now.

The MUSTs and MAYs on what can and cannot be added to the registry found in various places:

1. http://inter-locale.com/ID/draft-ietf-ltru-4646bis-20.html#sources
2. http://inter-locale.com/ID/draft-ietf-ltru-4646bis-20.html#ianastability
3. http://inter-locale.com/ID/draft-ietf-ltru-4646bis-20.html#registrationProc
4. http://inter-locale.com/ID/draft-ietf-ltru-4646bis-20.html#possibleReg
5. perhaps others
   

Part of it is that we want to give users of the registry information on what can and cannot occur in the registry, and in other sections give the Language Subtag Reviewer information on what he/she must/may do, and then in other sections give those filling out the Registration form information on what they can/may request. But that means that we have duplication in various places, and it is hard to make sure that everything is covered everywhere. Ideally we would have one place where all the restrictions were set out, and we could just reference that.

End side note.]

On Tue, Feb 10, 2009 at 04:34, Kent Karlsson <kent.karlsson14 at comhem.se> wrote:

I agree.


Den 2009-02-10 07.32, skrev "Randy Presuhn" <randy_presuhn at mindspring.com>:

> I'm also wary of introducing technical changes at this late stage,
> particularly without any demonstrated need.  Please,let's just
> replace the paragraph with:
>
>        E.  The UN numeric code 830 (Channel Islands) and any corresponding
>            ISO 3166-1 alpha-2 code not presently registered MAY
>            be entered into the IANA registry via the process described
>            in Section 3.5.
>
> (I deliberately lost the last sentence of the paragraph.  It
> added nothing and would not be missed.)

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