Martin Duerst wrote: > at some point, the other mailing list (ima at ietf.org) that I > originally cross-posted got lost. But the mail below, apart > from being cryptic except for people who have remembering > RFC numbers as a hobby, is all about email and nothing > about language codes, so the LTRU list is definitely > the wrong list to post to. Yes, I also can't tell why EAI discussions appear here, and Alexey's draft is about I18N for SMTP responses - neither EAI nor LTRU, that's why I proposed a followup to the SMTP list: >> Maybe fup2 the SMTP list. The cryptic 3461...3464 was my attempt to dedcode the "NOTARY", apparently the WG creating the predecessors 1891...1894 more than a decade ago, completely unrelated to language tags, this is about (mail) delivery status notifications. As you've seen in another article there is something in common between RFC 2034, EAI, and LTRU, at some point or another they try to use Unicode for I18N. In another article you said: > Please see http://www.ietf.org/liaisonActivities.html Thanks for info, appparently added (1)(2) April 2006, the last time I checked this page was in 2005. Frank 1: https://datatracker.ietf.org/public/liaisons.cgi 2: https://datatracker.ietf.org/documents/LIAISON/file305.pdf _______________________________________________ Ltru mailing list Ltru at 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.