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

[Marek Vavruša]

On Wed, Jun 22, 2016 at 1:52 AM, Mark Andrews  wrote:
>
> In message 
> 

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

[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.

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

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

[Mark Andrews]

In message 

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

[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://cr-yp-to.996295.n3.nabble.com/Fixing-the-NXDOMAIN-NODATA-bug-in-tinydns-td17150.html

-- 
Robert Edmonds

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

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

[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 shortly.
> 
> tim
> 
> 
> On 5/26/16 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-nxdomain-cut
>> 
>> Current versions of the draft is available here:
>> 
>> https://datatracker.ietf.org/doc/draft-ietf-dnsop-nxdomain-cut/
>> 
>> This is a Standards Track document.
>> 
>> Please review the draft and offer relevant comments. Also, if someone
>> feels the document is *not* ready for publication, please speak out with
>> your reasons.
>> 
>> This starts a two week Working Group Last Call process, and ends at
>> midnight 10 June 2016.
>> 
>> thanks
>> tim

Sorry I’m late to the party, and hopefully I’m misunderstanding, but…. using 
tinydns as an authoritative server:

bsomers@dev194:~$ dig dev194.sjc.opendns.com @auth1.opendns.com

; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> dev194.sjc.opendns.com 
@auth1.opendns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5740
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 5
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;dev194.sjc.opendns.com.IN  A

;; ANSWER SECTION:
dev194.sjc.opendns.com. 3600IN  A   67.215.93.64

;; AUTHORITY SECTION:
opendns.com.604800  IN  NS  auth1.opendns.com.
opendns.com.604800  IN  NS  auth2.opendns.com.
opendns.com.604800  IN  NS  auth3.opendns.com.

;; ADDITIONAL SECTION:
auth1.opendns.com.  172800  IN  2620:119:30::53
auth1.opendns.com.  172800  IN  A   208.69.39.2
auth2.opendns.com.  172800  IN  2a04:e4c0:53::53
auth2.opendns.com.  172800  IN  A   146.112.60.53
auth3.opendns.com.  172800  IN  A   208.69.39.2

;; Query time: 9 msec
;; SERVER: 2620:119:30::53#53(2620:119:30::53)
;; WHEN: Tue Jun 21 22:56:28 UTC 2016
;; MSG SIZE  rcvd: 220

bsomers@dev194:~$ dig sjc.opendns.com @auth1.opendns.com

; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> sjc.opendns.com @auth1.opendns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53475
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;sjc.opendns.com.   IN  A

;; AUTHORITY SECTION:
opendns.com.86400   IN  SOA auth1.opendns.com. 
noc.opendns.com. 1466546759 16384 2048 1048576 2560

;; Query time: 5 msec
;; SERVER: 2620:119:30::53#53(2620:119:30::53)
;; WHEN: Tue Jun 21 22:56:41 UTC 2016
;; MSG SIZE  rcvd: 79

If we want to say somethings recursively non-existent, don’t we need an 
RNXDOMAIN rcode?

—
Brian


___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

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

[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 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:

https://datatracker.ietf.org/doc/draft-ietf-dnsop-nxdomain-cut/

This is a Standards Track document.

Please review the draft and offer relevant comments. Also, if someone
feels the document is *not* ready for publication, please speak out with
your reasons.

This starts a two week Working Group Last Call process, and ends at
midnight 10 June 2016.

thanks
tim


___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

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

[神明達哉]

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-dnsop-nxdomain-cut
>
> Current versions of the draft is available here:
>
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-nxdomain-cut/
>
> This is a Standards Track document.
>
> Please review the draft and offer relevant comments. Also, if someone
> feels the document is *not* ready for publication, please speak out with
> your reasons.

I've already provided comments on the latest version (03) of the
draft:
http://www.ietf.org/mail-archive/web/dnsop/current/msg17480.html

and I think it's ready for publication.  My comments are generally
minor and I'd leave it to the authors whether/how to address them.

--
JINMEI, Tatuya

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

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

[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:

https://datatracker.ietf.org/doc/draft-ietf-dnsop-nxdomain-cut/

This is a Standards Track document.

Please review the draft and offer relevant comments. Also, if someone 
feels the document is *not* ready for publication, please speak out with 
your reasons.


This starts a two week Working Group Last Call process, and ends at 
midnight 10 June 2016.


thanks
tim

___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop