In message , "Evan Hunt via RT " writes: > On Thu, Mar 10, 2016 at 12:18:34AM +0000, Mark Andrews via RT wrote: > > People also expect nameservers to reject garbage in records which is > > what named and dig are doing when they can. > > See my previous statement about obvious correctness. However, since > other implementors are likely to follow the RFC and allow nonalphanumeric > characters, and this will affect interoperability, I think Robert's > suggestion of allowing such records in wire-format but switching to > unknown-type format when rendering them to text is a pretty good one. No, it won't. You need people to publish non ASCII tags which means first people need to decide to use a non ASCII tag in contravention of lots of text saying to only use ASCII. You also need to get them added to the Certification Authority Restriction Properties registry run by IANA. They then will be published as \DDD encoded strings by all the DNS tools if we were to permit non ASCII to pass. DNS developers testing ambigious corner cases will do this but no one else ever will. There is no need for non ASCII here. Tags are like SMTP commands. They don't need to be anything other than ASCII as they are not for human consumption. These records are designed to be consumed by machines automatically checking if particular operations are permitted. The RFC itself needs to be fixed. It is self contradictory. One of the following needs to be changed. Tag values MAY contain US-ASCII characters 'a' through 'z', 'A' through 'Z', and the numbers 0 through 9. Tag values SHOULD NOT contain any other characters. Matching of tag values is case insensitive. or Tag: Is a non-zero sequence of US-ASCII letters and numbers in lower case. We don't need to do anything until that is decided. Mark > -- > Ticket History: https://bugs.isc.org/Ticket/Display.html?id=41900 -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org