Hello Martin, Thanks for the note. > However, we now have an informative reference in a normative > sentence: > > E. UN numeric codes and ISO 3166-1 alpha-2 codes for > countries > or areas listed as eligible for registration in Section > 4 of > [RFC4645] but not presently registered MAY be entered > into > the IANA registry via the process described in Section > 3.5. > Once registered, these codes MAY be used to form > language > tags. This is why the reference *was* normative, nu? > > My understanding from previous discussions (both Randy and I had > the same idea) was that for this instance of referencing [RFC4645], > we would replace it inline with the only instance left, resulting > in something like: > > E. The UN numeric code or ISO 3166-1 alpha-2 code (once > assigned) > for the Channel Islands MAY be entered into the IANA > registry > via the process described in Section 3.5 (for historic > details, see [RFC4645]). I will make this change and post it in the morning. > > [there won't be any need to include a reference to a new RFC, > you will just have to choose the right boilerplate] > > > BTW, the "local diff" link in your popup (the one going to > http://www.inter-locale.com/ID/rfcdiff.pyht.htm) still shows > the diff between -19 and -20. Yes. I need to fix it. Addison Addison Phillips Globalization Architect -- Lab126 Internationalization is not a feature. It is an architecture. _______________________________________________ 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.