Doug Ewell scripsit: > But it SHOULD be noted that if we do allow 831 and 832 (and 833), and if > Addison is correct, we CANNOT subsequently register GG and JE (and IM) > if those codes are added to ISO 3166/MA, and make them the > Preferred-Values for the numeric codes. I think there is a common > assumption that we (or ietf-languages) would do that. UN codes are used > when there is no ISO code, but they cannot be superseded by ISO codes > that are added later. Which means that since 3166/MA MUST NOT add anything new unless UNSD does first, and 3166/MA only acts if a national body asks it to, we/ietf-languages SHOULD refrain from adding any M.49 code until it's clear that 3166/MA isn't going to act. Hence ltru, which has a limited lifespan, SHOULD NOT add 831 or 832 or 833, and leave action up to ietf-languages. -- There is no real going back. Though I John Cowan may come to the Shire, it will not seem jcowan at reutershealth.com the same; for I shall not be the same. http://www.reutershealth.com I am wounded with knife, sting, and tooth, http://www.ccil.org/~cowan and a long burden. Where shall I find rest? --Frodo _______________________________________________ Ltru mailing list Ltru at lists.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.