> But I will make a change if the co-chairs and AD are OK with it.
> I don't like silly work either, and I'm not keen on hearing the
> Reviewer complain about this.
I'm not fond of the idea of changing the document either.
>
> > Registrations completed under RFC 4646 after this document was
> frozen
> > but before the registry was updated MUST be incorporated by IANA
> in
> > the order in which they were received (as determined by their
> > File-Date record) into the new registry as part of the update
> process.
> > Registrations after date yyyy-mm-dd are the ones to be
> scrutinized by
> > IANA.
>
> If we were to add something, I'd be OK with this particular wording,
> except that "frozen" worries me a little -- I don't think that's
> defined
> anywhere, and obviously if we make a change now, that "unfreezes"
> the document, so it won't help with the registrations made a month or
> two ('Zinh' and company).
>
"Frozen" is probably not the right thing. Perhaps just the simple:
--
Registrations completed after date yyyy-mm-dd MUST be incorporated into this registry by IANA. This includes some registrations completed under RFC 4646 prior to the adoption of this document.
--
Anyway, it shouldn't be very hard. If we don't make the change, the LSR could just send an email to IANA once the new registry is in place with a reminder to re-incorporate the changes (and listing which ones they are). Ad hoc processes are sometimes the best way to handle minor issues.
Addison
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.