Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-06-22 Thread Marek Vavruša
On Wed, Jun 22, 2016 at 1:52 AM, Mark Andrews wrote: > > In message > , > =?UTF-8?Q?Marek_Vavru=C5=A1a?= writes: >> >> This affects several major DNS providers currently. I've heard Akamai >> is rolling out update, but it's still returning NXDOMAIN for ENTs. >> While deploying the draft in the c

Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-06-22 Thread Stephane Bortzmeyer
On Tue, Jun 21, 2016 at 05:46:38PM -0700, Marek Vavruša wrote a message of 20 lines which said: > pointing out various broken implementations is fun, It is not "fun", it is the only way to have broken implementations (Akamai, djbdns) fixed. If we do not name them, they will continue forever.

Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-06-22 Thread Mark Andrews
In message , =?UTF-8?Q?Marek_Vavru=C5=A1a?= writes: > > This affects several major DNS providers currently. I've heard Akamai > is rolling out update, but it's still returning NXDOMAIN for ENTs. > While deploying the draft in the current state of Internet is not > really viable and pointing out

Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-06-21 Thread Marek Vavruša
This affects several major DNS providers currently. I've heard Akamai is rolling out update, but it's still returning NXDOMAIN for ENTs. While deploying the draft in the current state of Internet is not really viable and pointing out various broken implementations is fun, I think it's good to have

Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-06-21 Thread Robert Edmonds
Brian Somers wrote: > Sorry I’m late to the party, and hopefully I’m misunderstanding, but…. using > tinydns as an authoritative server: Hi, Brian: You might enjoy these threads: http://thread.gmane.org/gmane.ietf.dnsop/13393 http://thread.gmane.org/gmane.ietf.dnsext/20301 http:/

Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-06-21 Thread Brian Somers
On Jun 21, 2016, at 1:34 PM, Tim Wicinski wrote: > > > All > > The WGLC last call ended on this awhile ago, and the authors addressed all > the comments that were raised during the WGLC process. > > I want to thank everyone for their work on this. We'll be moving this one > along very short

Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-06-21 Thread Tim Wicinski
All The WGLC last call ended on this awhile ago, and the authors addressed all the comments that were raised during the WGLC process. I want to thank everyone for their work on this. We'll be moving this one along very shortly. tim On 5/26/16 8:53 AM, Tim Wicinski wrote: There has been

Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-05-31 Thread Bob Harold
On Thu, May 26, 2016 at 8:53 AM, Tim Wicinski wrote: > There has been some good discussion from the working group on the list, > and with the recent discussion on root server tar pitting, it makes sense > to move this document along. > > This starts a Working Group Last Call for draft-ietf-dnsop-

Re: [DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-05-31 Thread 神明達哉
At Thu, 26 May 2016 14:53:06 +0200, Tim Wicinski wrote: > There has been some good discussion from the working group on the list, > and with the recent discussion on root server tar pitting, it makes > sense to move this document along. > > This starts a Working Group Last Call for draft-ietf-dns

[DNSOP] Working Group Last Call: draft-ietf-dnsop-nxdomain-cut

2016-05-26 Thread Tim Wicinski
There has been some good discussion from the working group on the list, and with the recent discussion on root server tar pitting, it makes sense to move this document along. This starts a Working Group Last Call for draft-ietf-dnsop-nxdomain-cut Current versions of the draft is available here