In message <5b5ae40c-6d26-419c-a16a-392af2c33...@hopcount.ca>, Joe Abley writes : > On 2014-02-18, at 10:54, SM <s...@resistor.net> wrote: > > > Seriously, it may take some effort to get things deployed but that is > not an insurmountable task [1]. One of the problems is that there isn't > any money in doing that. > > > > [...] > > > > 1. I actually looked into it some time back. > > I had some experience with this recently with the document that became > RFC 7043. > > Code-point assignment was swift. Implementation in major nameservers was > swift (although one or two of them left the types commented out in the > source until the RFC was published). The RFC publication process was not > arduous, even given the privacy concerns with this particular proposal. > > I appreciate that knowing the process made things easier (mainly; I was > wrong about some things and had to be educated). But I would not describe > the process as difficult, and certainly not insurmountable. > > > Joe
The process for getting a new type hasn't been *hard* for a decade now. Nameserver developers have been deploying new types quickly for over a decade now. Recursive servers have had the bugs w.r.t. handling unknown types removed over a decade ago. Being able to lookup a unknown type is a REQUIREMENT of RFC 103[45] and there have been (stub) resolvers that can do this for the entire life of DNS (Microsoft just fail to ship one). We defined how to specify UNKNOWN record types in master files a decade ago and most nameserver vendors have shipped code that support unknown types for over a decade now. Microsoft is the obvious exception. There are some load balancers that don't handle unknown types properly. Lots of these don't handle anything other than A. Not AAAA, TXT, SOA, NS. These need to be chased down and removed / replaced / upgraded with extreme prejudice. There are the stupid DNS administration panels the don't handle UNKNOWN types or for that matter anything other that A, NS and maybe AAAA and TXT. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
