Subject: Re: [DNSOP] Is there a concise and comprehensive definition of a "zone file"? Date: Sun, Feb 22, 2015 at 08:31:08AM -0800 Quoting Paul Hoffman ([email protected]): > On Feb 22, 2015, at 8:07 AM, Andrew Sullivan <[email protected]> wrote: > > > > On Sun, Feb 22, 2015 at 08:22:22AM +0100, Måns Nilsson wrote: > >> > >> ...we still very much would like STD80 charset in the canonical file. > > > > Anything in STD80? That's kinda strange. The STD13 "rule" is > > effectively the Preferred Syntax, which is LDH. Alternatively, labels > > are octets. Note that there are most definitely systems that put > > UTF-8 in zones, and this is entirely fine and legitimate; it just > > doesn't work that well on the Internet maximally construed.
And since that is the case, and since there most likely are zone file parsers that barf on anything !ASCII I still believe it is wise to limit the standard file format. As I understand it, one of the goals with defining the file format is that a file conforming to the format should pass most parsers today. That might seem like a backwards way of defining things, and it is, but we are trying to clarify something that is pretty old by any information technology time scale here.. > As I said earlier, I think that "labels in domain names should be encoded in > Punycode" would be sufficient, and would eliminate your problem with _labels, > I believe. That was at least what I meant. Thanks for helping me express myself ;-) -- Måns Nilsson primary/secondary/besserwisser/machina MN-1334-RIPE +46 705 989668 As President I have to go vacuum my coin collection!
signature.asc
Description: Digital signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
