Addison Phillips <addison at yahoo dash inc dot com> wrote: >> or the need to formally reconfirm the Reviewer when 4646bis is >> published (which we never did for 4646 or 3066). > > Actually, that's not true. There was "reconfirmation" (prehaps that is > too strong a word) of Michael as the reviewer at least in the > 3066->4646 changeover. True, IETF did confirm Michael in the position of Language Subtag Reviewer, in their response to one of the many appeals against 4646. They were never asked to solicit nominees anew, however, as they will be now. >> 2. New subtags and changes that come into being from individual >> requests have registration forms; those that come from ISO or UN >> standards do not. > > There are two types of *registration*. There are registrations > required by rule and there are registrations by request. The latter > includes a process for registering changes to ISO-assigned codes, > which has actually been used. These changes appear in the archive. > Registrations by rule do not. I'm sure there is an important distinction between my description of the situation and Addison's, and furthermore I'm sure Addison's description is better. I'm not sure the difference matters in this context. Under 4646, registration forms for "registrations by rule" do not appear in the archive, because there are no such forms. Under draft-4646bis, they do exist and are archived. > Hmm... I don't think it would be that big a change. In fact, it is > limited to a single sentence in Section 3.3, which currently reads: > > -- > Each individual subtag affected by a change MUST be sent to the > ietf-languages list with its own registration form and in a separate > message. > -- > > ... to which we would add: > > -- > Additions of new records MAY be batched together for submission to > IANA as a set. > -- If that is all we need to say, and there is no *requirement* to change things, and nobody feels the need to fine-tune this provision to death, then I have no problem with it, Again, cc'ing Michael to make sure he sees it. -- Doug Ewell * Fullerton, California, USA * RFC 4645 * UTN #14 http://www.ewellic.org http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages ˆ _______________________________________________ Ltru mailing list Ltru at ietf.org http://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.