On 2/20/15, 14:31, "John Levine" <[email protected]> wrote: >>There's an interesting specification in the ICANN new GTLD agreements: >>... > >>It's not concise or comprehensive; it's mostly a list of features of the >>master file format to not use. It looks like a wish list from those >>who've had to write custom parsers for the different "ZFA" file formats >>that the gTLD operators generate. > >That was mostly me and, yes, I tried to get them to specify a subset >of master file format that matched what we were already seeing from >large gTLDs so we could parse it easily. It took a few rounds to >explain to other people that the general 1035+all-other-DNS-RFCs >master file format was both impossible to specify and way more than >any TLD zone would need.
If just to wrap up - I’m aware of the ICANN specification. I guess I just want to translate it into an RFC and also put it up for IETF vetting. (Yes, I work for ICANN but my motivation is not to do something that would impact the new gTLDs agreements, my motivation is just to have a document for future reference.) Defining a canonical form in no way is meant to imply that any other form is wrong. The objective is to put a name on a canonical form, and provide a reference, so that anyone who wants to see zone files meeting a strict format can say so succinctly. (Plus, the document can discuss other issues, provide updated references, etc.) So, when I get around to it...
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
