Another Data Point: One of the Apps Area ADs stopped by to tell the chairs that 1) they like the general idea; 2) their employer has a need for this *outside of the PTR space*; and 3) would be willing to shepherd the work through. Now, they also the first to admit that the Application people do the most abuse to DNS standards (hence the need for the attrleaf document).
In fact, my employer, who is quite abusive in how they deploy CNAMEs could very easily work up a very legitimate use case for using BULK for deploying some of our larger zones. Add that to the fact that my employer insists on deploying DNS between multiple vendors - whether it is DNS software or managed DNS services. So while it's great to trash IPv6 rDNS (and count me first in line to trash IPv6 anything), there are actual other reasons why this would be useful. Just keep that in mind. tim On Thu, Jul 20, 2017 at 1:36 PM, Jim Reid <j...@rfc1035.com> wrote: > > > On 20 Jul 2017, at 03:12, Woodworth, John R <john.woodwo...@centurylink.com> > wrote: > > > > For now, I think we've narrowed the draft opposition to two camps: > > > > Camp#1) Don't force me to use IPv6 reverse, I simply will never > > > > and > > > > Camp#2) Don't break DNS, even for a second > > Well I don't recognise either of these camps. > > What was it you were saying about beauty being in the eye of the beholder? > :-) > > I'm in Camp N (for some definition of N): where's the use > case/justification for BULK and is it worth the effort? > > It's not clear if the WG has fully considered the impact of BULK on signed > reverse zones. Doing something to the DNS that further hinders uptake of > DNSSEC is probably a bad idea IMO. YMMV. Proposed protocol changes which do > that need to come with compelling benefits that outweigh this drawback. > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
