On 2009/06/11 1:54, Mark Davis wrote:
Oh, ask Mike Ksar about trying to get a response from the IETF charset registry!
I think that was years and years ago. Also, as far as I remember, he didn't understand very well how the process worked. Anyway, I think it's irrelevant for the current discussion.
Regards, Martin. [now, but not then, an expert reviewer for charsets]
But as I said, because the likelyhood of the text being invoked is so low, I'm ok with the current language, as imprecise as it is. Mark On Wed, Jun 10, 2009 at 08:25, Peter Constable<petercon at microsoft.com>wrote:From: Debbie Garside [mailto:debbie at ictmarketing.co.uk]What problem is being fixed here? (I don't know that we have an existingproblem.)It is a matter of clarity. If we do not state that a requester MUSTfirstapply to the ISO 639 JAC there will always be the awkward cuss who comes along and causes a huge rumpus - we have had our fair share of these and sometimes it is better to dot the i's and cross the t's. It could saveus alot of time in the future.You say, "we have had our fair share of these", but in over ten years participating in IETF-languages I don't recall any serious problems having arisen of the type we're discussing. Peter _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.ietf.org/mailman/listinfo/ltru------------------------------------------------------------------------ _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.ietf.org/mailman/listinfo/ltru
-- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.