Re: [DNSOP] [internet-dra...@ietf.org: New Version Notification for draft-edmonds-dnsop-capabilities-00.txt]

2017-07-03 Thread Robert Edmonds
Mark Andrews wrote: > There are three things that made it hard to deploy new features. > > 1) Firewall vendor shipping firewalls with ridiculously strict rules >with zero evidence that they are needed. > > 2) Misimplementation of STD 13 and RFC 2671 by nameserver vendors. > > 3) Unknown

Re: [DNSOP] [internet-dra...@ietf.org: New Version Notification for draft-edmonds-dnsop-capabilities-00.txt]

2017-07-03 Thread Paul Hoffman
On 2 Jul 2017, at 20:53, Mark Andrews wrote: There are three things that made it hard to deploy new features. 1) Firewall vendor shipping firewalls with ridiculously strict rules with zero evidence that they are needed. 2) Misimplementation of STD 13 and RFC 2671 by nameserver vendors.

Re: [DNSOP] [internet-dra...@ietf.org: New Version Notification for draft-edmonds-dnsop-capabilities-00.txt]

2017-07-02 Thread Mark Andrews
There are three things that made it hard to deploy new features. 1) Firewall vendor shipping firewalls with ridiculously strict rules with zero evidence that they are needed. 2) Misimplementation of STD 13 and RFC 2671 by nameserver vendors. 3) Unknown EDNS option behaviour was not well

[DNSOP] [internet-dra...@ietf.org: New Version Notification for draft-edmonds-dnsop-capabilities-00.txt]

2017-07-02 Thread Robert Edmonds
Hi, I've written a proposal for adding capability signaling to the DNS protocol that may be of interest to this group. The git repository is here: https://github.com/edmonds/draft-edmonds-dnsop-capabilities. - Forwarded message from internet-dra...@ietf.org - Date: Sun, 02 Jul 2017