[DNSOP] I-D Action: draft-ietf-dnsop-nxdomain-cut-05.txt

2016-09-18 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations of the IETF. Title : NXDOMAIN really means there is nothing underneath Authors : Stephane Bortzmeyer

Re: [DNSOP] I-D Action: draft-ietf-dnsop-nxdomain-cut-05.txt

2016-09-18 Thread Stephane Bortzmeyer
On Sun, Sep 18, 2016 at 08:26:09AM -0700, internet-dra...@ietf.org wrote a message of 47 lines which said: > Title : NXDOMAIN really means there is nothing underneath > Authors : Stephane Bortzmeyer > Shumon Huque > Filename

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread avri doria
On 12-Sep-16 16:19, Suzanne Woolf wrote: > It seems unlikely that they can be combined, so we simply have to ask > the WG to choose. I do not understand this point. Having now read both IDs, I see relevant points for the ongoing discussion in both of them. I see them as complementary where bo

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread John Levine
>On 12-Sep-16 16:19, Suzanne Woolf wrote: >> It seems unlikely that they can be combined, so we simply have to ask >> the WG to choose. The more I think about it, the more I think that they're both too long, and we'd be better off with a one or two sentence description of what we're trying to do,

[DNSOP] Mitigation of name collisions

2016-09-18 Thread Paul Hoffman
On 18 Sep 2016, at 14:10, John Levine wrote: 4.2.4. Name Collision in the DNS ... This study is from before the new gTLD program. The assumption in the report need to be tested against what actually happened in the round of new gTLDs before it can be included as part of the fact basis for

Re: [DNSOP] Mitigation of name collisions

2016-09-18 Thread John R Levine
It is impossible to measure the effectiveness without knowing how many collision queries are just noise (queries that will cause no noticeable damage if they started coming back with results). Agreed. I don't see how to find that out in ways that are not hard to back out if it turns out the d

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread Ted Lemon
Avri, thanks for the markups--I will take care of the ones that are actionable, and respond in a separate message, because I want to address the question of merging explicitly, along with John's comment about brevity. Why not merge the two documents? This sounds reasonable on the surface, but ple

[DNSOP] I-D Action: draft-ietf-dnsop-no-response-issue-05.txt

2016-09-18 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations of the IETF. Title : A Common Operational Problem in DNS Servers - Failure To Respond. Author : M. Andrews F

[DNSOP] I-D Action: draft-ietf-dnsop-no-response-issue-05.txt

2016-09-18 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations of the IETF. Title : A Common Operational Problem in DNS Servers - Failure To Respond. Author : M. Andrews F

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread John Levine
>To John's point, short isn't actually good, because it's important to >document the context-- No, really, short is essential. I'm happy to add the context once we have a concise statement of what the problem is. > But we tried to keep the actual >problem statement short and pithy; if you really

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread Ted Lemon
Dealing with toxic waste names is out of scope for the problem statement. The problem of toxic waste names is mentioned in the tldr problem statement as a problem, which could potentially be dealt with if the working group decides it's in scope. That's why the document is written the way it is.

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread John R Levine
Dealing with toxic waste names is out of scope for the problem statement. Well, that's one theory. Let's see of other people agree. R's, John Regards, John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread Phill
There is actually a fifth type of name, escaped names. Right now, the only names we have of this type are SRV protocol tags, (_http._tcp.example.com) and internationalized names (xn—wev.com) I want to add a third set of escaped names, one that has similar functionality to .onion but does not le

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread Phillip Hallam-Baker
There is actually a fifth type of name, escaped names. Right now, the only names we have of this type are SRV protocol tags, (_http._tcp.example.com) and internationalized names (xn—wev.com) I want to add a third set of escaped names, one that has similar functionality to .onion but does not leak

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread Ted Lemon
Okay, this is an interesting application that would certainly require some sort of 6761-style action. Do you believe that it is not covered by the current problem statement? On Sun, Sep 18, 2016 at 9:00 PM, Phill wrote: > There is actually a fifth type of name, escaped names. Right now, the on

Re: [DNSOP] Mitigation of name collisions

2016-09-18 Thread Paul Hoffman
On 18 Sep 2016, at 15:21, John R Levine wrote: It is impossible to measure the effectiveness without knowing how many collision queries are just noise (queries that will cause no noticeable damage if they started coming back with results). Agreed. I don't see how to find that out in ways tha

Re: [DNSOP] moving forward on special use names

2016-09-18 Thread George Michaelson
This is an instance of embedding. {th...@example.com}.{non-DNS-part} is not subject to special delegation rules in some sense, because the test of {non-DNS-part} requires no DNS action. If its synonymous with _special_label_.{non-DNS-part}.{example.com} then its about a conversation with upper syst