McDonald, Ira wrote: > I support changing to unescaped UTF-8 for the registry I'm opposed. > (consistent with the IESG policy in BCP 18 / RFC 2277). That's about new protocols, not text/plain files like RFCs or the LTRU registry. > if we move to XML with IANA concurrence, we'll get UTF-8 > anyway. Several issues here: Where does the "IANA will convert everything to XML" rumour come from? I saw no discussion about this on the XML-dir list. Numerous RFCs define registries with text/plain registration templates, if those templates are anything it's a kind of "record-jar". IANA can't simply reformat all their registries when they feel like it. XML is perfectly able to support any charset. UTF-16 and UTF-8 are only the minimally supported encodings. With the required UTF-8 support implementations not supporting US-ASCII would be odd. For something like xml2rfc stupid. Frank _______________________________________________ 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.