Doug Ewell scripsit: > I'd really like to start wrapping this up. I strongly agree. > One thing that worries me is being stuck in IETF Last Call or the RFC > Editor queue when ISO 639-3 releases their annual list of changes. I don't think either of those are relevant. If we are not yet approved, that just means we can't apply the changes directly in 4645bis but will have to process them through on ietf-languages in bulk, which shouldn't be much of a problem. (Of course, you'll have to play Official Doug.) As for the editor queue, it doesn't matter: as soon as 4645bis and 4646bis are approved, the new LSR goes into effect and so does the (mildly) new process. Delays in the queue only affect people who want to refer to some feature of the new RFC either directly or as part of BCP 47. -- Values of beeta will give rise to dom! John Cowan (5th/6th edition 'mv' said this if you tried http://www.ccil.org/~cowan to rename '.' or '..' entries; see cowan at ccil.org http://cm.bell-labs.com/cm/cs/who/dmr/odd.html) _______________________________________________ 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.