I’m hoping to be able to use terms like “canonical zone file” (to define a file that has lines like FQDN/TTL/CLASS/TYPE/RDATA) - as opposed to other ‘equivalent’ versions of a zone file. I’d also like to see a delineation of all of the “dollar-directives” (like $TTL, $ORIGIN, $INCLUDE and $GENERATE) defined in a document.
Not to mention escape rules. This just flashed back at me. Two RFCs had examples of SIP DNS entries. One presented the line with escapes according to (what I’ll call) BIND’s parsing rules and the other presented the line with how a person would normally write it. This was called to my attention when a SIP implementer was confused over the differences because the escape rules were not that obvious to a non-BIND-experienced person. (And I’d like to distinguish between preferred encodings - is \075 or ‘K’ preferred?) Does such a thing exist (in one document)? Where I am going with this is - when one wants to automate looking at zone files today, there are many varied formats to consider. (Kind of like WhoIs.) With the inclusion of S-labels in some zone files I have seen, what was once simple parsing means loading in IDNA2008 libraries. And given the flashback I just related, it would be good to recommend how DNS records are shown in RFCs - for the sake of consistency between documents. IMHO, it would be good to (ahem) ‘clarify’ what is meant by a zone file. And how to write or document a DNS record. I’m been thinking that this is needed - or maybe I’ve overlooked a document that’s already in use. So I’m asking if anyone knows of a document?
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
