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

Re: [Ltru] Re: Note to RFC editor in initial registry



To summarize, I propose to amend draft-initial-04 by adding the
following text to the beginning of Section 3:

[NOTE TO RFC EDITOR: Please remove this note and the rest of this
section, replacing it with the following comment:

The initial set of subtags in the registry, which were specified by this
document, are those records in the IANA registry [IANA-registry] with
"Added" field-values no later than the date of publication of this
document.  Note that Section 3.1 of [ltru-registry] requires that an
"Added" field appear in each registration record and that Section 3.3(1)
specifies that field must not be changed after registration. Other
fields in these records may have been modified at a later date, subject
to the restrictions in Section 3.4 of [ltru-registry].  Because of this,
it may not be possible to use a future version of the Language Subtag
Registry to reconstruct an exact copy of the initial registry contents.]

I would need to know what to put within the square brackets for
[IANA-registry].  Presumably this would be a normative reference to
whatever URI is chosen for the Language Subtag Registry.  I would have
to get this information in time for AUTH48, or the RFC Editor would have
to plug in the correct value at the time of text substitution.

The only other amendment to draft-initial-04 would be the addition of
the following record to the initial registry contents:

Type: language
Subtag: rup
Description: Aromanian
Description: Arumanian
Description: Macedo-Romanian
Added: 2005-09-20

Note that 'ain' for Ainu is already in draft-initial-04, but not in
previous versions.

--
Doug Ewell
Fullerton, California
http://users.adelphia.net/~dewell/



_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www1.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.