
From grothoff@in.tum.de  Wed Jan  1 13:36:23 2014
Return-Path: <grothoff@in.tum.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 966801AC43F for <dnsop@ietfa.amsl.com>; Wed,  1 Jan 2014 13:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFFMDtlxj9nD for <dnsop@ietfa.amsl.com>; Wed,  1 Jan 2014 13:36:20 -0800 (PST)
Received: from smtp1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9B41A802B for <dnsop@ietf.org>; Wed,  1 Jan 2014 13:36:20 -0800 (PST)
Received: from [192.168.178.20] (pd95c0f92.dip0.t-ipconnect.de [217.92.15.146]) by mail.net.in.tum.de (Postfix) with ESMTPSA id 7B2CD188E857 for <dnsop@ietf.org>; Wed,  1 Jan 2014 22:36:12 +0100 (CET)
Message-ID: <52C48A4A.6090303@in.tum.de>
Date: Wed, 01 Jan 2014 22:36:10 +0100
From: Christian Grothoff <grothoff@in.tum.de>
Organization: TU Munich
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info>
In-Reply-To: <20131231234421.GA5732@mx1.yitter.info>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Wed, 01 Jan 2014 14:29:54 -0800
Subject: Re: [DNSOP] More complete review of draft-grothoff-iesg-special-use-p2p-names-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 21:36:23 -0000

On 01/01/2014 12:44 AM, Andrew Sullivan wrote:
> On Tue, Dec 31, 2013 at 09:06:38PM +0100, Christian Grothoff wrote:
>>
>> What kind of metric do you propose, and how do you propose to acquire it?
> 
> From what you're saying about the different cases, it sounds like
> different metrics are going to be relevant.  For instance, it seems
> you could just count for .bit, but presumably the Tor examples could
> be worked out from rough estimates of the size of the Tor network.  

Yes, but to what end?

>> And again, a key question for me is, if you really want to _encourage_
>> people to _first_ deploy at large scale and _then_ reserve the name.
> 
> No, I don't.  What has happened here is, frankly, that the namespace
> was squatted on, and you're trying to normalize.  I think that's
> valuable and I want to support it.  But what would have been _better_
> is to have a discussion early when the names were being built into
> protocols.  How to do that is also a problem, but maybe if we can make
> it relatively painless in this case it will be more obvious that it
> could be less hard in future when it's needed.

Well, my point is that if you expect everybody to first get an RFC through
to document everything they are doing, expect squatting.

>> so a better question might be if there should be a process
>> to "unreserve" names should they fall into disuse.
> 
> How would you know?  If you can't count users of .gnu now (don't even
> know what "users" means, indeed), how would you know when it was safe?

Nobody working on maintaining the software and/or no user community
would be a strong indicator, and that's something one can find out
by looking / asking people.

>>> _Many_ of the references seem to be works in progress or unstable web
>>> pages.  That needs to be fixed for this document to be a useful
>>> specification.
>>
>> I was told that i2p2.de recently moved to geti2p.net.  Which other
>> pages are unstable in your experience? ("Worked for me...").
> 
> Oh, sorry.  I meant the other "stable": normally, we want the
> references in documents (and require the normative references) to be
> "stable references" in the sense that the target can't change.  So a
> URI isn't enough -- we need a permanent reference to a versioned
> document.  (This is the reason RFCs can't be changed once they're
> published.  They're an archival series.  If you want to "update" an
> RFC, you replace it with a new one.)

It is unclear to me how we even _could_ provide such a stable
document, especially for Namecoin and I2P where I don't even
see academic publications documenting the system on the horizon.
For Tor/GNS, we might be able to point to such references, but
of course then we have the problem that the protocols may still
evolve (there are ongoing discussions about changes to ".onion"),
so the "stable" links might then be outdated, whereas the links
we provided might remain current.

So even in the cases where "stable" links may exist, I'm
not convinced that only providing such "stable" links is
desirable.  But we could try to add additional references
to more stable design documents in cases where these
exist.

>>>     [â¦] Note that ".gnu"
>>>    names SHOULD follow the naming conventions of DNS.
>>>
>>> What does this mean exactly? 
>>
>>> Is this the LDH rule?
>>
>> Yes, in the sense of "SHOULD".
> 
> Ok.  This is probably the right interpretation of the STD 13
> "preferred syntax" (== LDH rule).  What STD 13 says, in effect, is
> that you can put anything in there, but things will tend to work
> better if you follow LDH.  (Note that RFC 1123 actually relaxed the
> rule, because originally labels couldn't start with a number either.)
> 
> What is the reason for continuing this tradition in GNS?  (That's
> probably out of scope for this document and even this draft, but the
> LDH rule has been a PITA and it's one of the things that would be nice
> to ditch if we could.)

Just backwards-compatibility with applications.

>>> Is GNS subject to IDNA?
>>
>> Yes.
> 
> Wow.  Are you sure you want to buy that much pain?

Well, again it's about backwards-compatibility with applications.
Browsers give us IDNA, so we deal with that.

>>> Or are labels just bags
>>> of octets?  
>>
>> No.
> 
> Why not?  If the LDH rule is only SHOULD, then what do you do with
> octets outside that range?  

Here's the short answer:

if (IDNA_SUCCESS !=
    idna_to_ascii_8z (label, &output, IDNA_ALLOW_UNASSIGNED))
   disallow();

Everything else goes.

>>> Are they only 63 octets each, with a maximum 255 limit?
>>
>> Yes, in the sense of "SHOULD". However, if the DNS protocol is not
>> used ("pure" GNS resolution with GNS-enabled applications where
>> a DNS packet is never created) is is theoretically permitted for
>> an application to not enforce these constraints.
> 
> This advice is worth what you're paying for it :) but I think that's
> going to hurt you in the long run.  You're going to get
> interoperability problems between people who actually enforce 63/255
> and people who don't.  Again, out of scope for this.

Well, right now our code enforces the 255 limit on everything, but
I wanted to leave a loophole in case that limit ever becomes a
problem in the future, for example if we ever need to resist
quantum cryptography and need much longer public keys.

>>  Also, yes, in theory appending
>> "f97f3b153fed6604230cd497a3d1e9815b007637.exit"
>> even once can cause one to run over the 255 limit on DNS names,
>> in which case the answer is "tough luck, won't work".
> 
> Ok.  It would be good to note that.
> 
> For the whole issue, then, I'd suggest something along these lines:
> 
>     Because every name ending in .exit is at least possibly a valid
>     hostname in itself, it should be noted that it is theoretically
>     possible for those names to be picked up and used in the construction
>     of .exit names again.  There is no reason to do this, but it is
>     possible.  In constructing such a name, it is possible to exceed
>     the total length limit for DNS names.  Such names may fail or
>     behave unpredictably when used with DNS resolvers.

Fine with me.

>> Well, if I had a 4,000-entry /etc/hosts file shared with tens of
>> thousands of other users, I think I would also try to put all of
>> those entries under some special TLD to ensure everyone knew that
>> I was using names from that list, as opposed to ordinary DNS names
> 
> Why?  My employer runs dyndns.org, among other names.  We have way
> more than 4,000 names under there.  Why wouldn't that work just as
> well in this case?

Well, you're running a DNS operation doing this, whereas these
are names that should not escape to DNS and users are supposed
to be aware that using those names gives them additional privacy.
Adding some DNS name as the suffix suggests to users that they're
using the "traditional" Internet, and here it is important to
make it clear that they are not.  And as it is not just a few
names, just using the label also is not nice, hence "label.i2p".

>> Well, I always thought of Namecoin and bitcoin as money-burning
>> activities, but feel free to invest in Namecoin then ;-). 
> 
> Snort.  I didn't say it'd make money _for me_!

Given that the code is GPL, why do you then allude to the fact
that it might make lots of money for someone else?  My point was
that if you really believe it to be that profitable, you should
make it work for you. If you believe that there is not much money
to be made, then suggesting that the users should pay 150k for
using some GPL'ed P2P software makes little sense.

>> I agree with you that the _technical_ reasons for a TLD are likely
>> the weakest for Namecoin, and I suspect the marketing/usability
>> concerns were the dominating reason.  But again, we're documenting
>> how it was deployed.
> 
> Yes.  But this is one of those joints between mere protocol and
> policy, because some time ago ICANN became responsible for the policy
> of root zone operation.  (The analogy with Apple is a good one -- the
> deployment of .local was, frankly, a similar case of
> namespace-squatting.)  Nobody cared about this before ICANN adopted an
> in-principle indefinite expansion of the root zone, but now we have a
> problem.
> 
> Getting evidence of the number of actual use (however we work that
> out) will go a long way in the argument, though.  On the other hand,
> suppose the registration doesn't happen.  The reason that .local (or,
> probably more directly comparable in this case, .corp) should possibly
> be on the special-use registration list is because we know that there
> are services using those names and that there will be security and
> user-confusion side effects if those names are also registered in the
> DNS name.  Similar arguments for this case wouldn't hurt.

Well, that is obviously the main argument for RFC 6761, and merely
by referencing that document this should be clear. But, as I think
you already suggested, we can stress that point more in the abstract.

>>> ajs@[gnu.org.f97f3b153fed6604230cd497a3d1e9815b007637.exit]?  I bet
>>> not.  It's simply not true that names and numbers can everywhere be
>>> used interchangeably.
>>
>> I don't quite see why this would not work in principle, assuming your
>> mail client is configured to route SMTP over Tor and the specified
>> exit supports exiting on port 25 to gnu.org.
> 
> Because the [ ] notation signals that what's in there is an IP
> address, not a name.

Ah, got it. We'll change the wording to try to address this.

>> I guess the question is what you define as "DNS resolver".  For example,
>> is the "dns2gns" proxy --- which speaks DNS (to applications) and then
>> forwards
>> ".gnu" and ".zkey" to GNS and everything else to DNS --- a "DNS resolver"?
> 
> Only partly.  This is similar to the confusion we had about recursive
> resolvers and caching name servers.  In the DNSSEC documents, you can
> see discussion about "the resovler side of a recursive name server"
> and "the name server side of a recursive name server" (or something
> similar).  Your example is of a general-purpose resolver system that
> does both DNS and GNS.  For the purposes of protocol, then, you have
> something like (ASCII art, sorry):
> 
>     resolver ---->  DNS ---->  DNS resolver ---> DNS
>      |----->  GNS --->  GNS resolver ---> GNS
> 
> For the purposes of implementation, these may well all be the same
> code.  But for the purposes of the protocol, we need to distinguish
> them.

Agreed.  We should probably add your ASCII art and adopt this kind
of terminology to clarify resolver vs. DNS resolver vs. GNS resolver.

>> I think you're mis-reading the point here, as the Namecoin block chain
>> is not obtained using the usual DNS protocol from some authority. So
>> DNS server operators that wanted to do this would NOT go out to some
>> IP address of a TLD operator that was granted ".bit" operation from
>> ICANN to fetch the block chain; instead, they'd have to participate
>> in the Namecoin network to observe block chain updates (a rather
>> daunting process, so this "MAY" is one that I personally don't expect
>> to see happening anytime soon by any major ISP).
> 
> This is an even worse idea.  What you're suggesting there is that
> recursive name server operators should add the .bit name to the
> answers they give out; but they don't get that answer from the DNS.

I think we wrote this as "MAY", not "SHOULD".  The point was that
if you do this, you still don't break user expectations --- they
get the value they (presumably) wanted.  However, you're right that
this turns the "recursive DNS resolver" into a "recursive resolver".
I'm not exactly sure why you think this would be so terrible, but
I'm happy to debate this issue (I don't even have a particularly
strong opinion).

> Quite apart from what happens in the presence of DNSSEC (I think it's
> "fails completely"), I think it is in general bad advice to tell
> people to populate their DNS caches with data from outside the DNS.

Well, it'd be a "resolver cache", not a "DNS cache" at this point ;-).

>> I expect them to be handed around by end-users and within applications.
>> I do not expect them to be handed around within UDP packets on port 53
>> (with the exception of ".bit").
> 
> But they will be:
>
>> I expect that this MAY happen, but if the draft is accepted, one
>> of our goals is to explicitly authorize DNS operators to prevent
>> this.
> 
> You can't "prevent it".  You can just have them swallowed somewhere
> else in the DNS system.  They _will_ get passed around on port 53.
> Therefore,

Well, I mean that DNS operators can "prevent it" in some cases,
but of course not categorically.

>>> "resolved or did not".  But perhaps what you are saying is that these
>>> ought to be added to the list in RFC 6303, and that they should always
>>> answer NXDOMAIN?  I could certainly live with that.
>>
>> Yes, exactly.  The formulation did end up a bit unclear and should
>> be fixed.  Our intention was exactly to allow servers to immediately
>> return NXDOMAIN without going to the root.
> 
> what I'd do is take a page out of RFC 6303, or follow the text in
> question 4 in the RFC 6761 discussion of .test:
> 
>    4.  Caching DNS servers SHOULD recognize test names as special and
>        SHOULD NOT, by default, attempt to look up NS records for them,
>        or otherwise query authoritative DNS servers in an attempt to
>        resolve test names.  Instead, caching DNS servers SHOULD, by
>        default, generate immediate negative responses for all such
>        queries. [â¦]

Yep, that's fine.

>> Again, thanks for your comments, we'll try to address those in the
>> next iteration, many of these were really helpful.
> 
> Glad to be of help.  
> 
> Best regards (and happy 2014),

Happy 2014 to you, too.

From dengguangqing@cnnic.cn  Wed Jan  1 22:46:33 2014
Return-Path: <dengguangqing@cnnic.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089981AE2FA for <dnsop@ietfa.amsl.com>; Wed,  1 Jan 2014 22:46:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.436
X-Spam-Level: 
X-Spam-Status: No, score=-0.436 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FSL_NEW_HELO_USER=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_75=0.6, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pemRGdKtJmTe for <dnsop@ietfa.amsl.com>; Wed,  1 Jan 2014 22:46:30 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id B83A81AE2F9 for <dnsop@ietf.org>; Wed,  1 Jan 2014 22:46:28 -0800 (PST)
X-EYOUMAIL-SMTPAUTH: dengguangqing@cnnic.cn
Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Thu, 02 Jan 2014 14:46:19 +0800
Date: Thu, 2 Jan 2014 14:46:19 +0800
From: "Guangqing Deng" <dengguangqing@cnnic.cn>
To: "Joe Abley" <jabley@hopcount.ca>
References: <20131231000412.GV4291@mx1.yitter.info>,  <52C323CE.3090909@grothoff.org>,  <67A7E258-BE45-4A7E-8D00-D3FEB31762C1@hopcount.ca>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 1, 3, 52[cn]
Mime-Version: 1.0
Message-ID: <2014010214461888230016@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart473422040536_=----"
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] More complete review of draft-grothoff-iesg-special-use-p2p-names-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 06:46:33 -0000

This is a multi-part message in MIME format.

------=_001_NextPart473422040536_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

Y29tbWVudHMgaW4tbGluZS4NCg0KDQoNCg0KR3VhbmdxaW5nIERlbmcNCkNOTklDIA0KDQpGcm9t
OiBKb2UgQWJsZXkNCkRhdGU6IDIwMTQtMDEtMDEgMDY6NDENClRvOiBDaHJpc3RpYW4gR3JvdGhv
ZmYNCkNDOiBoZWxsZWtpbjsgSUVURiBETlNPUCBXRzsgd2FjaHM7IGphY29iOyBBbmRyZXcgU3Vs
bGl2YW4NClN1YmplY3Q6IFJlOiBbRE5TT1BdIE1vcmUgY29tcGxldGUgcmV2aWV3IG9mIGRyYWZ0
LWdyb3Rob2ZmLWllc2ctc3BlY2lhbC11c2UtcDJwLW5hbWVzLTAxDQoNCj5PbiAyMDEzLTEyLTMx
LCBhdCAxNTowNiwgQ2hyaXN0aWFuIEdyb3Rob2ZmIDxjaHJpc3RpYW5AZ3JvdGhvZmYub3JnPiB3
cm90ZToNCg0KPj4gQW5kIGFnYWluLCBhIGtleSBxdWVzdGlvbiBmb3IgbWUgaXMsIGlmIHlvdSBy
ZWFsbHkgd2FudCB0byBfZW5jb3VyYWdlXw0KPj4gcGVvcGxlIHRvIF9maXJzdF8gZGVwbG95IGF0
IGxhcmdlIHNjYWxlIGFuZCBfdGhlbl8gcmVzZXJ2ZSB0aGUgbmFtZS4NCg0KPllvdSBjYW4gcmVz
ZXJ2ZSBhIG5hbWUgZm9yICQxMC95ZWFyLCBubyBJRVRGIHByb2Nlc3MgcmVxdWlyZWQuIExlc3Mg
aWYgeW91IHJlc2VydmUgdW5kZXIgYW4gZXhpc3RpbmcgZG9tYWluIG5hbWUuDQoNCj5UaGUga2V5
IHF1ZXN0aW9uIGZvciBtZSBpcywgd2h5IGRvIGFueSBvZiB0aGVzZSB1c2VzIG5lY2Vzc2FyaWx5
IHJlcXVpcmUgcmVzZXJ2YXRpb24gb2YgYSBUTEQgbGFiZWwsIG9yIHNvbWV0aGluZyB0aGF0IGxv
b2tzIGxpa2Ugb25lPw0KDQo+SWYgKHRvIHRha2UgYW4gZXhhbXBsZSBhdCByYW5kb20pIFRvciB1
c2VycyBjb3VsZCBtYWtlIHVzZSBvZiBuYW1lcyBvdXRzaWRlIG9mIHRoZSBETlMgdGhhdCBsb29r
IGxpa2UgRE5TIG5hbWVzIHVuZGVyIGEgLk9OSU9OIFRMRCwgd2h5IGNvdWxkIHRoZXkgbm90IGp1
c3QgYXMgZWFzaWx5IG1ha2UgdXNlIG9mID5uYW1lcyB0aGF0IGVuZCBpbiBPTklPTi5FRkYuT1JH
Pw0KDQpBbm90aGVyIGZhY3RvciBtYXkgYmUgdGhlIHJlc29sdXRpb24gZGVsYXksIGlmIHJlYWwt
dGltZSBpcyByZWFsbHkgdmVyeSBpbXBvcnRhbnQgZm9yIHRob3NlIHNvIGNhbGxlZCBQMlAgYXBw
bGljYXRpb25zLiBVc3VhbGx5IGluIHRoZSBoaWVyYWNoaWNhbCAgRE5TIHN5c3RlbSwgdGhlIHJl
c29sdXRpb24gZGVsYXkgb2YgZG9tYWluIG5hbWVzIGxpa2UgRVhBTVBMRS5PTklPTiBpcyBsZXNz
IHRoYW4gdGhhdCBvZiB0aG9zZSBsaWtlIEVYQU1QTEUuT05JT04uRUZGLk9SRy4gU28gbWF5YmUg
d2Ugc2hvdWxkIGNvbnNpZGVyIG1vcmUgYWJvdXQgZG9lcyB0aGUgVExEIChsaWtlIC5PTklPTikg
aXMgcmVhbGx5IG5lZWRlZD8gDQoNCj5UaGUgZ2VuZXJhbCBhbnN3ZXIgdG8gdGhpcyBxdWVzdGlv
biAoaW4gdGhlIEROUyB3b3JsZCkgaXMgdGhhdCBuYW1lcyB3aWxsIGFwcGVhciBpbiB0ZWxldmlz
aW9uIGFkcyBhbmQgYmlsbGJvYXJkIHBvc3RlcnMsIGFuZCBoZW5jZSBuZWVkIHRvIGJlIHNob3J0
IGFuZCBtZW1vcmFibGUuIEknbSBub3Qgc3VyZSBob3cgPmNvbnZpbmNpbmcgdGhhdCBhbnN3ZXIg
aXMgKHRpbWUgd2lsbCB0ZWxsLCBJIGd1ZXNzKSBidXQgaXQgc2VlbXMgbGVzcyBjb252aW5jaW5n
IGZvciBuYW1pbmcgc2NoZW1lcyB0aGF0IGludm9sdmUgZWFzaWx5LXR5cG8nZCwgbG9uZyBoZXhh
ZGVjaW1hbCBzdHJpbmdzIGFzIGludGVyaW9yIGxhYmVscy4gVGhlc2UgYXJlID5wcmVzdW1hYmx5
IG5vdCBpbnRlbmRlZCBmb3IgZGlyZWN0IGVudHJ5IGJ5IHVzZXJzLiBXaGVyZSBpcyB0aGUgbmVl
ZCBmb3IgYSBwaXRoeSBUTEQ/DQoNCj5JZiB0aGUgYW5zd2VyIGlzICJ3ZWxsLCBpdCB3YXNuJ3Qg
ZG9uZSB0aGF0IHdheSwgYW5kIHRoZXJlJ3MgYSBodWdlIGRlcGxveWVkIGJhc2UiIHRoZW4gSSB3
b3VsZCB0YWtlIHRoZSB0aW1lIHRvIGNvbnNpZGVyIG1pZ3JhdGlvbiBzdHJhdGVnaWVzIGF3YXkg
ZnJvbSBzY2hlbWVzIHRoYXQgc2VlbSB0byBpbnZvbHZlIHRvcC0+bGV2ZWwgRE5TIGxhYmVscyB0
b3dhcmRzIHNjaGVtZXMgdGhhdCBkb24ndC4gSXQncyBpbmV2aXRhYmxlIHRoYXQgdGhlc2UgbmFt
ZXMgd2lsbCBsZWFrIHRvIHRoZSBETlMsIGFuZCB0aG9zZSBsZWFrcyB3aWxsIGJlIGVhc2llciB0
byBtaXRpZ2F0ZSB0aGUgZnVydGhlciB0aGUgbmFtZXMgYXJlIGZyb20gdGhlIEROUyByb290Lg0K
DQo+PiBJIGV4cGVjdCB0aGF0IHRoaXMgTUFZIGhhcHBlbiwgYnV0IGlmIHRoZSBkcmFmdCBpcyBh
Y2NlcHRlZCwgb25lDQo+PiBvZiBvdXIgZ29hbHMgaXMgdG8gZXhwbGljaXRseSBhdXRob3JpemUg
RE5TIG9wZXJhdG9ycyB0byBwcmV2ZW50DQo+PiB0aGlzLiAgUmlnaHQgbm93LCBhIHdlbGwtY29u
ZmlndXJlZCwgMTAwJSBSRkMtY29tcGxpYW50IEROUyByZXNvbHZlcg0KPj4gTVVTVCBwYXNzIGEg
cmVxdWVzdCBmb3IgIi5vbmlvbiIgdG8gdGhlIHJvb3QuICBXaXRoIHRoaXMgZHJhZnQsIHdlDQo+
PiB3YW50IHRvIGV4cGxpY2l0bHkgQUxMT1cgMTAwJSBSRkMtY29tcGxpYW50IEROUyByZXNvbHZl
cnMgdG8gaW5zdGVhZA0KPj4gaW1tZWRpYXRlbHkgcmV0dXJuIE5YRE9NQUlOIGFuZCB0aHVzIGF2
b2lkIHRoZSBzZWN1cml0eSBhbmQgcGVyZm9ybWFuY2UNCj4+IGltcGxpY2F0aW9ucyBvZiBsZWFr
aW5nIHN1Y2ggcXVlcmllcyB0byB0aGUgcm9vdC4NCg0KPlRoZSBJRVRGIGlzIG5vdCB0aGUgcmVz
b2x2ZXIgcG9saWNlLiBSZXNvbHZlciBvcGVyYXRvcnMgbWl0aWdhdGUgd2VpcmQgcHJvYmxlbXMg
d2l0aCBhcHByb2FjaGVzIGxpa2UgdGhpcyBhbGwgdGhlIHRpbWUuIEl0J3MgYSBtaXN0YWtlIHRv
IGltYWdpbmUgdGhhdCBhIGJsZXNzaW5nIGVuc2hyaW5lZCBpbiBhIGRvY3VtZW50ID5wdWJsaXNo
ZWQgYnkgdGhlIElFVEYgd2lsbCBpbW1lZGlhdGVseSB0cmlnZ2VyIGNoYW5nZXMgaW4gZGVwbG95
ZWQgaW5mcmFzdHJ1Y3R1cmUsIG9yIHRoYXQgZGVwbG95ZWQgaW5mcmFzdHJ1Y3R1cmUgaXMgYmVp
bmcgaGFtc3RydW5nIGJ5IHRoZSBsYWNrIG9mIHN1Y2ggYSBibGVzc2luZy4NCg0KPkNvbnNpZGVy
LCBob3dldmVyLCB0aGUgZGlmZmVyZW50IGRlZ3JlZXMgb2YgY2hhb3MgdGhhdCBtaWdodCByZXN1
bHQgZnJvbToNCg0KPihhKSBpbnN0cnVjdCBhbGwgdGhlIHJlc29sdmVyIG9wZXJhdG9ycyBpbiB0
aGUgd29ybGQgdG8gbWFpbnRhaW4gY29uZmlndXJhdGlvbiB0aGF0IHNwZWNpYWwtY2FzZXMgYSBn
cm93aW5nIGxpc3Qgb2YgRE5TIG5hbWVzLiBvcg0KDQo+KGIpIGNob3NlIHlvdXIgbmFtaW5nIHNj
aGVtZSAoYWdhaW4sIHRoaW5rIE9OSU9OLkVGRi5PUkcpIHN1Y2ggdGhhdCB0aGUgTlhET01BSU5z
LCBuZWdhdGl2ZSBjYWNoaW5nLCBzaW5raG9saW5nLCB3aGF0ZXZlciBjYW4gYmUgY29udHJvbGxl
ZCBieSBzb21lb25lIHdobyBjYXJlcyBhYm91dCBUb3IgKHRoZSA+RUZGLk9SRyBhZG1pbmlzdHJh
dG9yKSB3aXRob3V0IHJlcXVpcmluZyBhbnkgc3BlY2lhbCBoYW5kbGluZyBlbHNld2hlcmUuDQoN
Cj5PcHRpb24gKGIpIGlzIG11Y2ggbW9yZSBmcmllbmRseSB0byB0aGUgSW50ZXJuZXQuDQoNCg0K
PkpvZQ0KDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KRE5TT1AgbWFpbGluZyBsaXN0DQpETlNPUEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbnNvcA==

------=_001_NextPart473422040536_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; COLO=
R: #000000; FONT-SIZE: 12pt
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18305"></HEAD>
<BODY style=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt">
<DIV style=3D"FONT-FAMILY: Times New Roman; FONT-SIZE: 11pt">comments=20
in-line.</DIV>
<DIV>&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV style=3D"FONT-FAMILY: Verdana"><SPAN>
<DIV=20
style=3D"MARGIN-TOP: 10px; FONT-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000=
; MARGIN-LEFT: 10px; FONT-SIZE: 10.5pt; MARGIN-RIGHT: 10px">
<DIV><SPAN style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000; FONT-=
SIZE: 10.5pt">Guangqing=20
Deng</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000; FONT-SIZE: 10.5p=
t">CNNIC&nbsp;</SPAN></DIV></DIV></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; FONT-=
FAMILY: tahoma; BACKGROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADD=
ING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:jabley@hopcount.ca">Joe Abley</A>=
</DIV>
<DIV><B>Date:</B>&nbsp;2014-01-01&nbsp;06:41</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:christian@grothoff.org">Christian=20
Grothoff</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:hellekin@gnu.org">hellekin</A>; <A=20
href=3D"mailto:dnsop@ietf.org">IETF DNSOP WG</A>; <A=20
href=3D"mailto:wachs@net.in.tum.de">wachs</A>; <A=20
href=3D"mailto:jacob@appelbaum.net">jacob</A>; <A=20
href=3D"mailto:ajs@anvilwalrusden.com">Andrew Sullivan</A></DIV>
<DIV><B>Subject:</B>&nbsp;Re: [DNSOP] More complete review of=20
draft-grothoff-iesg-special-use-p2p-names-01</DIV></DIV></DIV>
<DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;On 2013-12-31, at 15:06, Christian Grothoff=20
&lt;christian@grothoff.org&gt; wrote:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&gt; And again, a key question for me is, if you really want to=20
_encourage_</DIV>
<DIV>&gt;&gt; people to _first_ deploy at large scale and _then_ reserve t=
he=20
name.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;You can reserve a name for $10/year, no IETF process required. Le=
ss if=20
you reserve under an existing domain name.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;The key question for me is, why do any of these uses necessarily=20
require reservation of a TLD label, or something that looks like one?</DIV=
>
<DIV>&nbsp;</DIV>
<DIV>&gt;If (to take an example at random) Tor users could make use of nam=
es=20
outside of the DNS that look like DNS names under a .ONION TLD, why could =
they=20
not just as easily make use of &gt;names that end in ONION.EFF.ORG?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Another factor may be the resolution delay, if real-time is really ve=
ry=20
important for those so called P2P applications. Usually in the hierachical=
=20
&nbsp;DNS system, the resolution delay of domain names like EXAMPLE.ONION =
is=20
less than that of those like EXAMPLE.ONION.EFF.ORG. So maybe we should con=
sider=20
more about does the TLD (like .ONION) is really needed? </DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;The general answer to this question (in the DNS world) is that na=
mes=20
will appear in television ads and billboard posters, and hence need to be =
short=20
and memorable. I'm not sure how &gt;convincing that answer is (time will t=
ell, I=20
guess) but it seems less convincing for naming schemes that involve=20
easily-typo'd, long hexadecimal strings as interior labels. These are=20
&gt;presumably not intended for direct entry by users. Where is the need f=
or a=20
pithy TLD?</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;If the answer is "well, it wasn't done that way, and there's a hu=
ge=20
deployed base" then I would take the time to consider migration strategies=
 away=20
from schemes that seem to involve top-&gt;level DNS labels towards schemes=
 that=20
don't. It's inevitable that these names will leak to the DNS, and those le=
aks=20
will be easier to mitigate the further the names are from the DNS root.</D=
IV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&gt; I expect that this MAY happen, but if the draft is accepted,=
=20
one</DIV>
<DIV>&gt;&gt; of our goals is to explicitly authorize DNS operators to=20
prevent</DIV>
<DIV>&gt;&gt; this.&nbsp; Right now, a well-configured, 100% RFC-compliant=
 DNS=20
resolver</DIV>
<DIV>&gt;&gt; MUST pass a request for ".onion" to the root.&nbsp; With thi=
s=20
draft, we</DIV>
<DIV>&gt;&gt; want to explicitly ALLOW 100% RFC-compliant DNS resolvers to=
=20
instead</DIV>
<DIV>&gt;&gt; immediately return NXDOMAIN and thus avoid the security and=20
performance</DIV>
<DIV>&gt;&gt; implications of leaking such queries to the root.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;The IETF is not the resolver police. Resolver operators mitigate =
weird=20
problems with approaches like this all the time. It's a mistake to imagine=
 that=20
a blessing enshrined in a document &gt;published by the IETF will immediat=
ely=20
trigger changes in deployed infrastructure, or that deployed infrastructur=
e is=20
being hamstrung by the lack of such a blessing.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;Consider, however, the different degrees of chaos that might resu=
lt=20
from:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;(a) instruct all the resolver operators in the world to maintain=20
configuration that special-cases a growing list of DNS names. or</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;(b) chose your naming scheme (again, think ONION.EFF.ORG) such th=
at the=20
NXDOMAINs, negative caching, sinkholing, whatever can be controlled by som=
eone=20
who cares about Tor (the &gt;EFF.ORG administrator) without requiring any=20
special handling elsewhere.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;Option (b) is much more friendly to the Internet.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;Joe</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>_______________________________________________</DIV>
<DIV>DNSOP mailing list</DIV>
<DIV>DNSOP@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/dnsop</DIV>
<DIV>&nbsp;</DIV></DIV></BODY></HTML>

------=_001_NextPart473422040536_=------


From ajs@anvilwalrusden.com  Thu Jan  2 03:42:01 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1D81AE659 for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 03:42:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.16
X-Spam-Level: ***
X-Spam-Status: No, score=3.16 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_84=0.6, LOTS_OF_MONEY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9IIXuu5Ja2T for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 03:41:59 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 02DEA1AE656 for <dnsop@ietf.org>; Thu,  2 Jan 2014 03:41:58 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 6AB8D8A031 for <dnsop@ietf.org>; Thu,  2 Jan 2014 11:41:51 +0000 (UTC)
Date: Thu, 2 Jan 2014 06:41:46 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140102114146.GA6913@mx1.yitter.info>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <52C48A4A.6090303@in.tum.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] More complete review of draft-grothoff-iesg-special-use-p2p-names-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 11:42:01 -0000

On Wed, Jan 01, 2014 at 10:36:10PM +0100, Christian Grothoff wrote:
> 
> Well, my point is that if you expect everybody to first get an RFC through
> to document everything they are doing, expect squatting.

As I suggested at the start of this thread, that's actually a
different question, and one the IETF needs to engage broadly.  I am
not sure what to think.

On the one hand, I agree with you that there is the practical fact:
people might just do this.

On the other hand, the reason people historically felt this was ok was
because the root zone was (as zones go) small and stable.  That is, if
you stepped on a namespace at the top level, you had reasons to
suppose you weren't getting in anyone's way and precedent to expect
that you wouldn't face many negative effects in the future.  In the
present régime, however, those assumptions are both false.  So this
might actually just be an education problem to the rest of the world:
"You used to think this was safe.  It never was, but it used to work.
In future, you should expect it to break."  

> Nobody working on maintaining the software and/or no user community
> would be a strong indicator, and that's something one can find out
> by looking / asking people.

Which people?  We have learned (the hard way) on the Internet that any
assumption something will go away is extremely brittle.  In practice,
once you've started using a namespace, it's there for good (or at
least a very long time.  Just for instance, A6 records have long since
been deprecated, but one continues to see some queries).

> It is unclear to me how we even _could_ provide such a stable
> document, especially for Namecoin and I2P where I don't even
> see academic publications documenting the system on the horizon.

That's going to be awkward, then.  It's kind of hard to justify the
allocation of a TLD by this special procedure if it's for some sort of
protocol that might never go anywhere and might not even use that TLD
in the long run.

> For Tor/GNS, we might be able to point to such references, but
> of course then we have the problem that the protocols may still
> evolve (there are ongoing discussions about changes to ".onion"),
> so the "stable" links might then be outdated, whereas the links
> we provided might remain current.

That's an excellent way to document software systems but a poor way to
document specifications.  A specification document needs to say, "This
is what $x is for."  If the purpose of $x changes, you deprecate the
old and publish something new in order that someone else can come
along and code against whatever the spec is.  Should people coding
know about the changes that are happening while they're looking at the
"stale" spec?  Yes, certainly.  But at the very least, if one wants to
evaluate interoperability, it becomes necessary to point at something
stable.

Now, you might argue that this is a case of no interoperability.  But
that's not quite true: the specification is saying (for instance) that
an intermediate resolver SHOULD intercept these names and generate
RCODE=3.  That's a testable question of interoperation.  Could it
change?  Who knows?  We need a stable reference in order to know what
the behaviour is supposed to be at a given time.

I'm willing to help write stubby I-Ds, if need be, to document these
things.  They wouldn't need to describe everything about the various
systems, I think; just to describe the rules about the names in each
case.  I'll see if I can work up an example today or tomorrow and send
it off-list.

> Well, you're running a DNS operation doing this, whereas these
> are names that should not escape to DNS and users are supposed
> to be aware that using those names gives them additional privacy.
> Adding some DNS name as the suffix suggests to users that they're
> using the "traditional" Internet, and here it is important to
> make it clear that they are not.  And as it is not just a few
> names, just using the label also is not nice, hence "label.i2p".

I think this missed the point.  It could just as easily say
"label.i2p.invalid", for instance, which would guarantee that the
whole thing would already be covered by the .invalid rules.  The i2p
system would need to look for a name ending in "i2p.invalid", of
course, which is very slightly more work.  But once you're looking at
labels, peeling one off is nothing.

Now, I suppose some applications would check for names under .invalid
and stop immediately, knowing they're not allowed to be looked up.
For that reason, we might want to create a special space in (say)
.arpa for this.  Call it localdef.arpa.  Inside localdef.arpa is a
completely locally-defined namespace, and applications would be free
to do whatever they wanted there.  Then you could have
i2p.localdef.arpa.  Applications that don't know about localdef.arpa
still won't block because .arpa is a perfectly good domain.
Applications that do will know to strip off localdef.arpa and do stuff
according to their magic label.  This is _still_ not using the DNS.
It's just living comfortably inside the DNS namespace, which is not
what setting up random TLDs does.

> Given that the code is GPL, why do you then allude to the fact
> that it might make lots of money for someone else? 

It seems pretty clear that most of the alternative-currency systems
tend to attract speculators at the beginning.  I note that namecoin
attempts to blunt this compared to bitcoin, but new currencies are
_always_ the domain of speculators at the beginning.  To someone
interested in the new-TLD business (and I assure you that neither my
employer nor I are), that could look like someone trying to make money
without "paying their dues".

I don't know how far I buy this argument; I'm just trying to point out
the collision here between the IETF allocation procedure and the
regular TLD allocation procedure at ICANN.  (I freely admit that the
problem is caused at least partly by the somewhat dubious "cost
recovery" amount of US$185,000.  If I were boss of the world, there'd
be a lot of things I'd change.  You may imagine that ICANN's rules
would not make my first pass :-). )

> get the value they (presumably) wanted.  However, you're right that
> this turns the "recursive DNS resolver" into a "recursive resolver".
> I'm not exactly sure why you think this would be so terrible, but
> I'm happy to debate this issue (I don't even have a particularly
> strong opinion).

Unfortunately, many people have had the bright idea of injecting
things into "the recursive server" in order to "satisfy user
expectations".  This causes a number of (widely-documented) problems,
and in any case relies on a faulty picture of the real data paths for
DNS data.  It's true that the model is mostly ok for >90% of all
traffic, but the problems show up in the minority.  Even a very small
minority of problems turns into a major headache for help desks --
usually not the help desk of whever had the bright idea.  So, the IETF
cannot responsibly suggest yet another class of positive answer be
added to these intermediate resolvers.  NXDOMAIN seems to be harmless.
Everything else seems to cause trouble.

> > Quite apart from what happens in the presence of DNSSEC (I think it's
> > "fails completely"), I think it is in general bad advice to tell
> > people to populate their DNS caches with data from outside the DNS.
> 
> Well, it'd be a "resolver cache", not a "DNS cache" at this point ;-).

So what happens when that resolver gets a query from an end system
that is doing its own validation?  What if the CD bit is set on that
query?  Now, what if different applications on the same end system
have different resolver libraries, and one is asking for DNSSEC and
the other isn't?  Won't that be kinda confusing?  All this would need
to be spelled out in detail for an intermediate multimode resolver
that might synthesize DNS responses.  Yes, these are corner cases.
Those furry blobs you see in the corners of the DNS are not dust
bunnies.  They're monsters, and they bite.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From paul.hoffman@vpnc.org  Thu Jan  2 12:00:37 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D49F1AE167 for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 12:00:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqanTvHpYbwd for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 12:00:36 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id D99F31AE00C for <dnsop@ietf.org>; Thu,  2 Jan 2014 12:00:22 -0800 (PST)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s02K0DEM010136 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Jan 2014 13:00:15 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <52C48A4A.6090303@in.tum.de>
Date: Thu, 2 Jan 2014 12:00:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C051985-6E70-463A-9672-02657842754D@vpnc.org>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de>
To: Christian Grothoff <grothoff@in.tum.de>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>
Subject: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 20:00:37 -0000

On Jan 1, 2014, at 1:36 PM, Christian Grothoff <grothoff@in.tum.de> =
wrote:

> Well, my point is that if you expect everybody to first get an RFC =
through
> to document everything they are doing, expect squatting.

We do. And squatters should expect that the name that they are using =
might eventually be legitimately assigned later, possibly to someone =
whose intentions are quite different from the squatters. This is how the =
IETF has worked for over 20 years. The purpose of RFC 6761 is not to say =
"if you start squatting on a TLD, you will be able to later get it =
reserved". It is to say "if there are legitimate errors in TLD use, =
those can be dealt with".

It seems that one of the themes of your responses here is "the TLDs are =
now being used in software and we won't change that software ever". If =
that is a correct reading, then there really isn't any reason to move =
forwards on these requests. The folks using the names are squatting, and =
will continue to do so regardless of the outcome of the application, =
much less the outcome of ICANN later allocating those TLDs to someone =
else.

On the other hand, if the software using the currently-squatted TLDs are =
willing to change the names, there is room for discussion. One =
possibility for RFC 6761 is that an application can specify a use for a =
non-allocated TLD, and a random string (short, typeable, but unlikely to =
be wanted by anyone in the ICANN space) can be generated for that. So, =
instead of ".bit" (which has high value), ".gp4x7" could be allocated. =
That gets the community what they want (a string that ICANN is prevented =
from later allocating) and follows the spirit of RFC 6761.

--Paul Hoffman=

From christian@grothoff.org  Thu Jan  2 13:30:22 2014
Return-Path: <christian@grothoff.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E66CD1AC7EE for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 13:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CMwwX5dSa4wA for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 13:30:19 -0800 (PST)
Received: from smtp1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) by ietfa.amsl.com (Postfix) with ESMTP id C091E1A1F5F for <dnsop@ietf.org>; Thu,  2 Jan 2014 13:30:19 -0800 (PST)
Received: from [192.168.178.20] (pd95c0f92.dip0.t-ipconnect.de [217.92.15.146]) by mail.net.in.tum.de (Postfix) with ESMTPSA id 7072C1885373; Thu,  2 Jan 2014 22:30:08 +0100 (CET)
Message-ID: <52C5DA5C.1090605@grothoff.org>
Date: Thu, 02 Jan 2014 22:30:04 +0100
From: Christian Grothoff <christian@grothoff.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org>
In-Reply-To: <4C051985-6E70-463A-9672-02657842754D@vpnc.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 21:30:22 -0000

On 01/02/2014 09:00 PM, Paul Hoffman wrote:
> On Jan 1, 2014, at 1:36 PM, Christian Grothoff <grothoff@in.tum.de> 
> wrote:
> 
>> Well, my point is that if you expect everybody to first get an RFC
>>  through to document everything they are doing, expect squatting.
> 
> We do. And squatters should expect that the name that they are using
>  might eventually be legitimately assigned later, possibly to someone
>  whose intentions are quite different from the squatters. This is how
>  the IETF has worked for over 20 years. The purpose of RFC 6761 is
> not to say "if you start squatting on a TLD, you will be able to
> later get it reserved". It is to say "if there are legitimate errors
> in TLD use, those can be dealt with".

Well, let's just say my reading of the intent of RFC 6761 is different.

> It seems that one of the themes of your responses here is "the TLDs 
> are now being used in software and we won't change that software 
> ever".

You need to learn about about free software here, as you're assuming
that anyone really is in a position to say that. These are GPL projects,
thus anyone can change that software in any way they feel like.  I'm
merely suggesting that my personal opinion is that such a patch is
unlikely to be widely adopted. You're welcome to prove me wrong, writing
the patch should be hardly any work, after all.

> If that is a correct reading, then there really isn't any reason to 
> move forwards on these requests. The folks using the names are 
> squatting, and will continue to do so regardless of the outcome of 
> the application, much less the outcome of ICANN later allocating 
> those TLDs to someone else.

Didn't Apple squat on ".local" and get it reserved using RFC 6761? I
think you're are in total denial of facts that have been discussed in
this context on this very list already.

> On the other hand, if the software using the currently-squatted TLDs
>  are willing to change the names, there is room for discussion. One 
> possibility for RFC 6761 is that an application can specify a use for
> a non-allocated TLD, and a random string (short, typeable, but 
> unlikely to be wanted by anyone in the ICANN space) can be generated
>  for that. So, instead of ".bit" (which has high value), ".gp4x7" 
> could be allocated. That gets the community what they want (a string
>  that ICANN is prevented from later allocating) and follows the
> spirit of RFC 6761.

Sorry, Hollywood-math about the 'value' of a name has also already been
discussed.  However, I'm willing to agree that ".bit" has value to
society --- because it is already used by Namecoin. A name that is not
even used has no established value.



From ajs@anvilwalrusden.com  Thu Jan  2 14:18:34 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA0C1AC7F3 for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 14:18:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h7iXO45jyveD for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 14:18:33 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id DEA2A1AC4C1 for <dnsop@ietf.org>; Thu,  2 Jan 2014 14:18:32 -0800 (PST)
Received: from mx1.yitter.info (nat-02-mht.dyndns.com [216.146.45.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 5E91A8A031 for <dnsop@ietf.org>; Thu,  2 Jan 2014 22:18:25 +0000 (UTC)
Date: Thu, 2 Jan 2014 17:18:24 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140102221823.GF8050@mx1.yitter.info>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52C5DA5C.1090605@grothoff.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 22:18:34 -0000

On Thu, Jan 02, 2014 at 10:30:04PM +0100, Christian Grothoff wrote:
> Didn't Apple squat on ".local" and get it reserved using RFC 6761? 

Not exactly, no.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jabley@hopcount.ca  Thu Jan  2 15:02:05 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 788171AD67B for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 15:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_75=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uYD9li1_OBUU for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 15:02:04 -0800 (PST)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 5C5AA1AD67A for <dnsop@ietf.org>; Thu,  2 Jan 2014 15:02:04 -0800 (PST)
Received: by mail-ig0-f181.google.com with SMTP id k19so34860429igc.2 for <dnsop@ietf.org>; Thu, 02 Jan 2014 15:01:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=gV4vv8e6Z3t458BPmzL2HADyjPX0DJc+E7lrvIszJ/4=; b=Xql/nr2s0wA2fbmbRpZs58uHnfvqfkiGonX6L8PPoWaVi5b68HgB99gg6GBvfaXw9P mKB/ulfOXgLYMEkGcETUSwLrkgQZLOiz9DKOXHjEVNI8fiUMJrprXHq5caAOVIJVcTcC HqSBnH8jE1fQ/iMHbIEcYLocj8QiuLmq5Dul4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=gV4vv8e6Z3t458BPmzL2HADyjPX0DJc+E7lrvIszJ/4=; b=NlDaN20rzWT58SZKh+k7WW1Z3rrCTxvnxi475Fyk4tzvZHmD3kTAVdS8dibzhs+16R 0EyCuZkCk9bejSDtxDV1KR/7GHYM/dHodGjgZxvZr4DWQkeCgiGoHvbE68MJqVsd/8/x e7nKKzVIek6WYo8y6jQGNs5LO8n4Li1PXgXslM5Sf+ROEdJrkXg3LjXLJ9B3F6f6ty/u bmf23Mu+zacqwXKJz+nRGggoZcBjDY8t+qIuFbQkGpwLMgjdDQzHd1tws7+mMeZIq4LS LNwtSMfbshH5n/mw2u5n9xsSWSkSyaFhsCfKBx687PISF3zKARASg7Sg1uiBB+ZWjbpy Ojxw==
X-Gm-Message-State: ALoCoQnLOOqlPpWxN9is7s9bHrrQs2FJ+bnMHZkEBGBxYn1LOygTGA+iR5yRToscMK82UiPiLFVF
X-Received: by 10.50.41.106 with SMTP id e10mr57530008igl.37.1388703717150; Thu, 02 Jan 2014 15:01:57 -0800 (PST)
Received: from [199.212.90.62] (24-52-234-221.cable.teksavvy.com. [24.52.234.221]) by mx.google.com with ESMTPSA id o1sm75471456igh.9.2014.01.02.15.01.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Jan 2014 15:01:56 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E1217DE9-3DFE-45F9-8039-12809E0F1E1F"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Joe Abley <jabley@hopcount.ca>
X-Priority: 3
In-Reply-To: <2014010214461888230016@cnnic.cn>
Date: Thu, 2 Jan 2014 18:01:54 -0500
Message-Id: <E53D4A80-B99D-4B8D-B766-E6A6E1C5AF61@hopcount.ca>
References: <20131231000412.GV4291@mx1.yitter.info>, <52C323CE.3090909@grothoff.org>, <67A7E258-BE45-4A7E-8D00-D3FEB31762C1@hopcount.ca> <2014010214461888230016@cnnic.cn>
To: Guangqing Deng <dengguangqing@cnnic.cn>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] More complete review of draft-grothoff-iesg-special-use-p2p-names-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 23:02:05 -0000

--Apple-Mail=_E1217DE9-3DFE-45F9-8039-12809E0F1E1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi there,

On 2014-01-02, at 01:46, Guangqing Deng <dengguangqing@cnnic.cn> wrote:

>> If (to take an example at random) Tor users could make use of names =
outside of the DNS that look like DNS names under a .ONION TLD, why =
could they not just as easily make use of names that end in =
ONION.EFF.ORG?
> =20
> Another factor may be the resolution delay, if real-time is really =
very important for those so called P2P applications. Usually in the =
hierachical  DNS system, the resolution delay of domain names like =
EXAMPLE.ONION is less than that of those like EXAMPLE.ONION.EFF.ORG. So =
maybe we should consider more about does the TLD (like .ONION) is really =
needed?

Well, that's what local caches and long TTLs are for. But in this case, =
any query of this kind that hits the real DNS is by definition junk =
(it's a query for a name from a non-DNS namespace that has leaked into =
the DNS) so I can't imagine what performance difference this could =
possibly make.


Joe


--Apple-Mail=_E1217DE9-3DFE-45F9-8039-12809E0F1E1F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlLF7+IACgkQNI8MvYZSOiw/ygCeLwT1GoqEQ+fsDK5te2hlcwSL
wGUAn37ynxZTN0oS8YiqFTe1Lqd7uSZI
=7RrO
-----END PGP SIGNATURE-----

--Apple-Mail=_E1217DE9-3DFE-45F9-8039-12809E0F1E1F--

From paul.hoffman@vpnc.org  Thu Jan  2 15:02:28 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CC051AD75F for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 15:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XbTOmGUJuX7W for <dnsop@ietfa.amsl.com>; Thu,  2 Jan 2014 15:02:27 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 72AD71AD73E for <dnsop@ietf.org>; Thu,  2 Jan 2014 15:02:27 -0800 (PST)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s02N1ui2015174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Jan 2014 16:01:57 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <52C5DA5C.1090605@grothoff.org>
Date: Thu, 2 Jan 2014 15:02:00 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BE81E5D-4A35-4FCE-8119-4C676AE610B1@vpnc.org>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org>
To: Christian Grothoff <christian@grothoff.org>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 23:02:28 -0000

On Jan 2, 2014, at 1:30 PM, Christian Grothoff <christian@grothoff.org> =
wrote:

> On 01/02/2014 09:00 PM, Paul Hoffman wrote:
>> On Jan 1, 2014, at 1:36 PM, Christian Grothoff <grothoff@in.tum.de>=20=

>> wrote:
>>=20
>>> Well, my point is that if you expect everybody to first get an RFC
>>> through to document everything they are doing, expect squatting.
>>=20
>> We do. And squatters should expect that the name that they are using
>> might eventually be legitimately assigned later, possibly to someone
>> whose intentions are quite different from the squatters. This is how
>> the IETF has worked for over 20 years. The purpose of RFC 6761 is
>> not to say "if you start squatting on a TLD, you will be able to
>> later get it reserved". It is to say "if there are legitimate errors
>> in TLD use, those can be dealt with".
>=20
> Well, let's just say my reading of the intent of RFC 6761 is =
different.

I'm interested to hear what others think.

>> It seems that one of the themes of your responses here is "the TLDs=20=

>> are now being used in software and we won't change that software=20
>> ever".
>=20
> You need to learn about about free software here, as you're assuming
> that anyone really is in a position to say that.

I didn't say you were in a position to say that; I said that it sounded =
like you were saying you were.

> These are GPL projects,
> thus anyone can change that software in any way they feel like.  I'm
> merely suggesting that my personal opinion is that such a patch is
> unlikely to be widely adopted. You're welcome to prove me wrong, =
writing
> the patch should be hardly any work, after all.

Quite true, but irrelevant to your request for the names.

>> If that is a correct reading, then there really isn't any reason to=20=

>> move forwards on these requests. The folks using the names are=20
>> squatting, and will continue to do so regardless of the outcome of=20
>> the application, much less the outcome of ICANN later allocating=20
>> those TLDs to someone else.
>=20
> Didn't Apple squat on ".local" and get it reserved using RFC 6761?

No.

> I
> think you're are in total denial of facts that have been discussed in
> this context on this very list already.

Or, we simply disagree about what happened.

>=20
>> On the other hand, if the software using the currently-squatted TLDs
>> are willing to change the names, there is room for discussion. One=20
>> possibility for RFC 6761 is that an application can specify a use for
>> a non-allocated TLD, and a random string (short, typeable, but=20
>> unlikely to be wanted by anyone in the ICANN space) can be generated
>> for that. So, instead of ".bit" (which has high value), ".gp4x7"=20
>> could be allocated. That gets the community what they want (a string
>> that ICANN is prevented from later allocating) and follows the
>> spirit of RFC 6761.
>=20
> Sorry, Hollywood-math about the 'value' of a name has also already =
been
> discussed.  However, I'm willing to agree that ".bit" has value to
> society --- because it is already used by Namecoin. A name that is not
> even used has no established value.

And we disagree here as well, but at least it is now more clear what you =
are thinking in your application.

--Paul Hoffman=

From ietf-secretariat-reply@ietf.org  Sat Jan  4 05:12:02 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D0861ADF50 for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 05:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vB07XJN6Huyh for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 05:12:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ABD291ADF60 for <dnsop@ietf.org>; Sat,  4 Jan 2014 05:11:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140104131159.6219.6678.idtracker@ietfa.amsl.com>
Date: Sat, 04 Jan 2014 05:11:59 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-Mailman-Approved-At: Sat, 04 Jan 2014 05:20:07 -0800
Subject: [DNSOP] Milestones changed for dnsop WG
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 13:12:02 -0000

Changed milestone "Submit Locally-served DNS Zones to IESG for BCP",
resolved as "Done".

URL: http://datatracker.ietf.org/wg/dnsop/charter/

From ietf-secretariat-reply@ietf.org  Sat Jan  4 05:13:21 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8461ADF50 for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 05:13:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkihMsQ3xycu for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 05:13:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A3A141ADF60 for <dnsop@ietf.org>; Sat,  4 Jan 2014 05:13:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140104131318.31810.55280.idtracker@ietfa.amsl.com>
Date: Sat, 04 Jan 2014 05:13:18 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-Mailman-Approved-At: Sat, 04 Jan 2014 05:20:08 -0800
Subject: [DNSOP] Milestones changed for dnsop WG
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 13:13:21 -0000

Changed milestone "Submit I'm Being Attacked by PRISONER.IANA.ORG! to
IESG for FYI", resolved as "Done".

URL: http://datatracker.ietf.org/wg/dnsop/charter/

From ietf-secretariat-reply@ietf.org  Sat Jan  4 05:16:00 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4AB91ADF50 for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 05:16:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5PchguKSGgs for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 05:15:59 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 030221ADF63 for <dnsop@ietf.org>; Sat,  4 Jan 2014 05:15:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140104131559.10135.61997.idtracker@ietfa.amsl.com>
Date: Sat, 04 Jan 2014 05:15:59 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
X-Mailman-Approved-At: Sat, 04 Jan 2014 05:20:08 -0800
Subject: [DNSOP] Milestones changed for dnsop WG
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 13:16:01 -0000

Changed milestone "Submit AS112 Nameserver Operations to IESG for
Informational", resolved as "Done".

URL: http://datatracker.ietf.org/wg/dnsop/charter/

From internet-drafts@ietf.org  Sat Jan  4 12:40:38 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F349F1AE021; Sat,  4 Jan 2014 12:40:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUNXrKVq4NcJ; Sat,  4 Jan 2014 12:40:36 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BEA1AE093; Sat,  4 Jan 2014 12:40:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140104204035.7446.24984.idtracker@ietfa.amsl.com>
Date: Sat, 04 Jan 2014 12:40:35 -0800
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 20:40:38 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Domain Name System Operations Working Gro=
up of the IETF.

        Title           : Automating DNSSEC delegation trust maintenance
        Authors         : Warren Kumari
                          Olafur Gudmundsson
                          George Barwood
	Filename        : draft-ietf-dnsop-delegation-trust-maintainance-01.txt
	Pages           : 17
	Date            : 2014-01-04

Abstract:
   This document describes a method to allow DNS operators to more
   easily update DNSSEC Key Signing Keys using DNS as communication
   channel.  This document does not address the initial configuration of
   trust anchors for a domain.  The technique described is aimed at
   delegations in which it is currently hard to move information from
   the child to parent.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintain=
ance/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-delegation-trust-maintainance-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dnsop-delegation-trust-mainta=
inance-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From warren@kumari.net  Sat Jan  4 13:21:15 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A41611AE094 for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 13:21:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cs7N-RDZBJe0 for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 13:21:13 -0800 (PST)
Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by ietfa.amsl.com (Postfix) with ESMTP id 00C261AE091 for <dnsop@ietf.org>; Sat,  4 Jan 2014 13:21:12 -0800 (PST)
Received: by mail-wi0-f181.google.com with SMTP id hq4so1588697wib.14 for <dnsop@ietf.org>; Sat, 04 Jan 2014 13:21:03 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DV566oeCSv7mo6bfxDO6PSG/VwPWpNOxGqo7YzTwLIw=; b=KI7OBRkkrRGkV4m6cqy2eC1nVWfMcpUrEwHsyRYcaHYjDOq7egAV/ikfMNjLYhOTDq lDzIpb7Gb54ONhFxB3QDHyyN270qYUKtRFyv1Tp+7/69pydNC6raA7dVWSiotCAreY0N GZ8RziHb4cyZ5Mo2zcwFIWtRzrM/h5iTmkMhWDWI0xX5ePw0P/p+RIe9/A7FVunBV5oT bebgYQMweWHyK7ngCWOzF4WDe60s8zj9rkwIjnVtRooP5kUsGvxcZDJVJbBKmw734rAW O5+rpNGDJS9jHVvHkoYOFYCcVrvpL+gY0cBJaMLwB3KNPqj4cQFIxZzcuEmjMzFSHaXZ 81pg==
X-Gm-Message-State: ALoCoQnMaMXyhATIX2vlYiGUz+AV540FW7BgOhFlnc/v21yyaNKUPJP1Bs9ONG8bKNPM+hxIsDKa
MIME-Version: 1.0
X-Received: by 10.194.77.7 with SMTP id o7mr28227177wjw.35.1388870463518; Sat, 04 Jan 2014 13:21:03 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Sat, 4 Jan 2014 13:21:03 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <20140104204035.7446.24984.idtracker@ietfa.amsl.com>
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com>
Date: Sat, 4 Jan 2014 16:21:03 -0500
Message-ID: <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: internet-drafts@ietf.org
Content-Type: multipart/alternative; boundary=047d7bfd05fc9e0b7104ef2b9a99
Cc: dnsop@ietf.org, i-d-announce@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 21:21:15 -0000

--047d7bfd05fc9e0b7104ef2b9a99
Content-Type: text/plain; charset=ISO-8859-1

We think that this resolves the open comments and is ready for WGLC.



On Sat, Jan 4, 2014 at 3:40 PM, <internet-drafts@ietf.org> wrote:

>
> 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 Working
> Group of the IETF.
>
>         Title           : Automating DNSSEC delegation trust maintenance
>         Authors         : Warren Kumari
>                           Olafur Gudmundsson
>                           George Barwood
>         Filename        :
> draft-ietf-dnsop-delegation-trust-maintainance-01.txt
>         Pages           : 17
>         Date            : 2014-01-04
>
> Abstract:
>    This document describes a method to allow DNS operators to more
>    easily update DNSSEC Key Signing Keys using DNS as communication
>    channel.  This document does not address the initial configuration of
>    trust anchors for a domain.  The technique described is aimed at
>    delegations in which it is currently hard to move information from
>    the child to parent.
>
>
> The IETF datatracker status page for this draft is:
>
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintainance/
>
> There's also a htmlized version available at:
>
> http://tools.ietf.org/html/draft-ietf-dnsop-delegation-trust-maintainance-01
>
> A diff from the previous version is available at:
>
> http://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-delegation-trust-maintainance-01
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--047d7bfd05fc9e0b7104ef2b9a99
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">We think that this resolves the open comments and is ready=
 for WGLC.<div><br></div></div><div class=3D"gmail_extra"><br><br><div clas=
s=3D"gmail_quote">On Sat, Jan 4, 2014 at 3:40 PM,  <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-drafts=
@ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=A0This draft is a work item of the Domain Name System Operations Working G=
roup of the IETF.<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Automating DNSSEC delegation tr=
ust maintenance<br>
=A0 =A0 =A0 =A0 Authors =A0 =A0 =A0 =A0 : Warren Kumari<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Olafur Gudmundsson<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 George Barwood<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-dnsop-delegation-trust=
-maintainance-01.txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 17<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2014-01-04<br>
<br>
Abstract:<br>
=A0 =A0This document describes a method to allow DNS operators to more<br>
=A0 =A0easily update DNSSEC Key Signing Keys using DNS as communication<br>
=A0 =A0channel. =A0This document does not address the initial configuration=
 of<br>
=A0 =A0trust anchors for a domain. =A0The technique described is aimed at<b=
r>
=A0 =A0delegations in which it is currently hard to move information from<b=
r>
=A0 =A0the child to parent.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-tru=
st-maintainance/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-=
ietf-dnsop-delegation-trust-maintainance/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-dnsop-delegation-trust-mai=
ntainance-01" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-dnsop=
-delegation-trust-maintainance-01</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dnsop-delegation-t=
rust-maintainance-01" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3D=
draft-ietf-dnsop-delegation-trust-maintainance-01</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dnsop</a><br>
</blockquote></div><br></div>

--047d7bfd05fc9e0b7104ef2b9a99--

From muks@isc.org  Sat Jan  4 15:51:05 2014
Return-Path: <muks@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 804B01AE0C3 for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 15:51:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XxCZt3Ru6QP for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 15:51:03 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id A4EC71AE0C2 for <dnsop@ietf.org>; Sat,  4 Jan 2014 15:51:02 -0800 (PST)
Received: from totoro.home.mukund.org (unknown [115.118.150.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 58FAFE600EF; Sat,  4 Jan 2014 23:50:50 +0000 (GMT)
Date: Sun, 5 Jan 2014 05:20:45 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Warren Kumari <warren@kumari.net>
Message-ID: <20140104235045.GA24696@totoro.home.mukund.org>
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com> <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N"
Content-Disposition: inline
In-Reply-To: <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 23:51:05 -0000

--fUYQa+Pmc3FrFX/N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi Warren

On Sat, Jan 04, 2014 at 04:21:03PM -0500, Warren Kumari wrote:
> We think that this resolves the open comments and is ready for WGLC.

Here are some comments:

Section 1
---------

> CDS only allows transferring information about DNSSEC keys (DS and
> DNSKEY) from the child to the parental agent.  It lists exactly what

"CDS" is used without any prior description of it.

Section 1.1
-----------

Use of punctuation in this section can be improved.

> There terminology we use is defined in this section

"There terminology..." => "The terminology...".

Section 2.1
-----------

When mentioning RRtypes (NS, DS, etc.), it would be good to cite the
relevant RFCs where they were introduced.

> The second RRset the parent sometimes publishes is the DS set.  The
> DS RRset provides information about the key(s) that the child has
> told the parent it will use to sign its DNSKEY RRset.  In DNSSEC

May I suggest changing "keys(s)" => "DNSKEY(s)"?

> As the DS record can only be present at the parent RFC4034 [RFC4034],
> some other record/method is needed to automate the expression of what
> the parental zone DS records contents ought to be.  One possibility
> is to use flags in the DNSKEY record.  If the SEP bit is set, this

I suggest rewriting this sentence:

"As the DS record can only be present at the parent RFC4034 [RFC4034],
some method is needed to automate which DNSKEYs are picked to be
represented in the parent zone's DS records."

A sentence explaining why a method is needed to automate locating entry
point keys would be good to have here.

> indicates that the DNSKEY is intended for use as a secure entry
> point.  This DNSKEY signs the DNSKEY RRset, and the Parental Agent
> can calculate DS records based on that.  But this fails to meet some
> operating needs, including the child having no influence what DS

Does this mean that the Parental Agent automatically picks up DNSKEY RRs
with SEP=1 from the child zone? (How are these DNSKEYs validated?) This
should be explained.

> digest algorithms are used and DS records can only be published for
> keys that are in the DNSKEY RRset.

Does this imply use of additionally configured trust anchors when such
keys are not in the DNSKEY RRset? Such minor clues are useful when
reading.

Section 2.2
-----------

>                                        ... in which an organization
> may delegate parts of its name-space to be operated by a group that
> is not the same as that which operates the enterprise's DNS servers.

Do "organization" and "enterprise" in the trimmed context above refer to
the same entity? If the word "enterprise" covers all organizations,
"enterprise's DNS servers" seems to mean one particular organization's
DNS servers.

I was not able to follow this paragraph (though I follow what is
intended to be described).

Section 2.2.1
-------------

> A further complication is when the Child DNS Operation is not the
> Child.  There are two common cases of this,

"Child DNS Operation" => "Child DNS operator"

>   If the Parental Agent is the DNS operator, life is much easier, as
>   the Parental Agent can inject any delegation changes directly into
>   the Parents Provisioning system.  The techniques described below are
>   not needed in the case when Parental Agent is the DNS operator.

"Parents Provisioning system" => "Parent's Provisioning system"

>   Some parents want the child to express the changes in trust anchors
>   via DS records, while others want to receive DNSKEY records and

Is "trust anchor" used according to its definition here? Specifically it
pertains to a resolver's configuration. There is a similar use of "trust
anchor" in the abstract too.

> interface, to "upload / paste-in the zone's DS information".  The
> action of logging in through the delegation account user interface
> authenticates that the user is authorized to change delegation
> information published in the parent zone.  In the case where the

"... change delegation information *for the child* published in the
parent zone." (i.e., not all delegation information in the parent zone.)

> Furthermore when this is a manual process with cut and paste;
> operational mistakes will happen. Or worse the update action in not
> performed at all.

Please replace the above with the following (punctuation and typo
changes):

"Furthermore when this is a manual process with cut and paste,
operational mistakes will happen, or worse, the update action is not
performed at all."

Section 3
---------

> This document specifies two new DNS RRtypes (CDS and CDNSKEY) that
> indicates what the Child wants to be in the parents DS RRset.  It

Instead of "to be in the", I suggest something like:

"... what the Child wants to be included in the parent's DS RRset."

"... what the Child wants the parent's DS RRset to contain."

(also note the apostrophe in "parent's").

> allows the Child to present DS records and / or DNSKEY records (for
> those parents who would rather generate the DS records for their
> children).

> [RFC Editor: Please remove this paragraph before publication] Version
> -04 of this document defined a new record (CTA) that could hold
>  either a DS or a DNSKEY record (with a selector to differentiate
>  between them). ]

Where is version -04 of this document? What is this CTA record it is
referring to?

Section 5
---------

It is important to add a note here that the Child DNS Operator (or some
software) must delete old DNSKEYs only after verifying that the parent
zone has updated its DS records to match the new ones.

It is also important for the Child to not directly switch CDS / CDNSKEY
RRs (once published):

* before sending them through DNSKEY RRs first, and

* before verifying that the parent has updated to the new CDS / CDNSKEY
  data

as the parent may be in the process of updating to the new DS records
when such a change happens, breaking the chain.

Section 6.1.1
-------------

> environments the registry is prohibited from talking to the
> registrant.  In most these cases the registrant has a business

"most these cases" => "most of these cases"

Section 6.1.2
-------------

> DNSSEC, these mechanisms can be unauthenticated (for example, a child
> could call his parent and request the CDS action be performed, an

"could call his parent" => "could call its parent"

What does "CDS action" mean here? It should be described or this
sentence could be rewritten.

Section 6.2
-----------

If every nameserver is to be checked for the CDS / CDNSKEY RRs, what is
the action to be taken when there is a mismatch? Which CDS is used?


Section 9
---------

> This work is for the normal case, when things go wrong there is only
> so much that automation can fix.

Please change the comma to a full-stop.

> not detected before the DS in parent is changed.  If this type of
> change takes place, the child need to contact the parent (possibly

"child need to" => "child needs to"


> While it may be tempting, this SHOULD NOT be used for initial
> enrollment of keys since there is no way to ensure that the initial
> key is the correct one.  If is used, strict rules for inclusion of

Perhaps "authentic" or "valid" are better words than "correct" in this
context.

Some overall notes
------------------

"Child operator" and "Child DNS operator" are both used. Please update
the document to use the one defined in the "Terminology" section.

Can't the equivalent of CDS / CDNSKEY be achieved by introducing
additional DNSKEY RRs (with SEP=1) in the child zone that are polled by
the Parent DNS operator? Is it really so important that the child must
have control (overriding the parent's choice) over the value of fields
used in the DS record? For example, the parent operator can use the same
algorithm, etc. as in the initially configured DS record.

		Mukund

--fUYQa+Pmc3FrFX/N
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iQgcBAEBCgAGBQJSyJ5SAAoJENJq4EOcI4173es//2Oq4LYLwmBUSOz0gJAoAPw7
MnZA+0hd+YyHm9OtQo2Y5fEr59znZVZf4zcnHVuF50hBUI4N3K9y6cnQUzI9FNjz
K/NjMLYlcS5ltdaeEV50SN2RQ9Oxc1XcOHT+jE+7RZDQ4k7lnp1VoUvbTF8gDd5o
i9vefIyZLSuafRFIZmeq9TaXGttX3N1d964UvAMvC/g3vcbXuhxpf1wmIi9++q6N
q3cJ+NeJbthCkUKhY4q+jpg9zTb5RU6DgNJ3FvVeUCPxYVo9V4V16hoqMJiJsFBB
UbNdzm2njPlvOuro7Nn64I70urQFzoC/uk4IBs/s2irN+kMwiLIidxGVNgPUF5fE
6MGBW7JkFGeMl4h+D9idVRn3tWTWpsH0t4BYuiWiIZqEI4tusDoofbBjLB23LcsI
gaKryOLC7pCYvULTZv3KfRSzXx/iYbda2ipSKJ1NzFB53a1oq8l3I8OsHOdI+Rj/
GSDhloYzigJwiVbwiR+DwEZLmk9vyEacXkkO6RHuX5OmeJf76Uh/NGOiPN+7MyRK
l+EqmQROMqtYwxaR5baghvBrBDYkxK9aEhb1kCScOiW7cgvQxuydnuMFmFHRRhy+
6/WcikSA/xB9EBOovNnTMV2u1F1sEV2V8ou54npLuOF6WidLdBMjPSUthBC3znGd
eUYkBTN5F7a9SBsZmrQ5WKKDk5PDPOhzcMx/sciJUd8P7s36J6ReldMAT5YPVd4G
mjBCsmVB5khasIj6LMWOsvQADVS4waqfn3LdQ7xmyg7RgxxhIIQ2p+Vhk7njdqvJ
X9BcG7EuTemjjOLpCqa2nX5bDI6jDrWnv3fxMu84nQsKnqNIuU3Mj87Vd9Uy1oIN
/RAYC+idwFb1r22QWpRw1ncSNtkDmuv0OPfnA2/1c7ZMMVBqiSlHcTR4Ei+u9ZEt
OB9qc39+RXoWYhDLeX2Ws1eUBtmOMkcwCELIojHw67eeZUHni3J6eyWgmL4KPFS8
6KU5bLsneKJHiPQ0BLX64de8TRa+eOatTuZbenTmQ0fiI9Q2iTW/pWc8rQrpcmV0
3RuEXiOD2HNDpppDGHBxCLIdL3ZQPrYEp9i9kcmBG8gKZl179+bMiFYmlphRWQpX
0GtJRbbc9NCr7ufGWhuBmteq8nEe7CDuuqZS2jkh+WfXthPfy9shFIHR+zi2GHc5
bT7oqkMrwIcCcLCnYCsWUXf7lPOIkAZ6cKZg+izSbqTkOfzS50ksXq28QGJlW9A+
gCVNxEgirN05JxNvaoveg0OnFjcVZ9xXs1yL0Bi4hl6OmePlx16ZCPvCfni0H0+B
mSzQdJIBd1pElGm53/BzSolBJu9gpidiUjxtYQ1LbsP09k94NrU+YPVDBt6/1flf
mI26o/3QTOp8IiWfFhIFb6tFv7mlolPxC9UfMFnE/wLL49MUpuKmw9u/+/rB9E9V
HUQfufRH1GP2o4zR8rPokaDSPVo3jkSnMETF5x0qM9Yhzs5TnTo/PSNufBWTv3wN
NTjCRE6GQFYFOsjLc9gnxWiAVvy9xZcxLPX0WcghnFLnzi+Jq6IUgWXjkN6N/ziv
k6U6Ez50q2P7drNPGdirRiIbcuM3pRndjSsTsC16HM6G4vV+W0qVi+oifgGFYzFa
pUg1HnX37Lyjif9SuRYXs2tz4H4eV+emcgQcropaA4VrSG+oxpLs+vgkaOXQUfg9
S1Cgpa1tzFNabanZ0+3fOYBkuAR/cimIDAr4fR8PgR4B+4fze9kZFfOid7j890R6
c7Y3Gmzx/jNJMfYrvXJXvNUctAs8A+TdL+UvZAfyBfjbyYC1lr4FYUL8nt5H3qKz
XgNXLaqTbjrd2oDELX6x3fy4SwQcSCU/Hq2LrjCuB52uvLAztgpF3MCQMx7RjD03
BiHVD4e++/htSVTHHNIDNOMFHTZZsK5JsD5191iuxaiX8CTo30mmb/XW13D1m+d1
IdawaGZtJ7mfuTLAeeWtZR47QBrw5rXo/9A9QTCAjDM841M3sZg9wCGMp5Lc5UQV
PhgNzoK5vO3Vo+Ix/0a37cQrRb7Ihf7W2HJkeOrfEiAV5H2D7gS+g6+PsmWdQxJW
//9ZM8odR2+4RFjXKYzKozOFkca1EhLCbte/uKCriQLE8EQuGpj0imYi84OAzssO
6ztulx6Pqo57rxM2SO3P6qxC70tFR6FUEHZBoZ9rsjwITkOq/fYjjbC5aOfCA1AD
TL8G4FYvABrqqthBDg/+1X/pcDnDjw86m+Yh0FEG9tqp6A/yOQtJV5dE/d33PRBQ
xLoApOh+TcXDevmEg9S4eRT74dkJXMgNqxu8nHFx2QvhabkNMBvm5OkJj5Pjht5t
7H8xKvooN0I01mrrd6klTmw5SPurZqbWBLoy2pklbBrokjMr8EmMndQ5cxjMIKV0
YjcJfB+D1CHkfbXrBz91iH6C0N4rR9N/nMm1dpGUNcQaGiH3zev0CSNYeu9RvjbT
3mAYhccJa9vk0MGFLYOBKGXzUD/ZNpyElsXAHnHijheFo6vecO2VRHoJ25LK26UR
RVNf5IWvOJreGALI15N/rwaIfck6NBpo/V8YYkZbA7S9m9y3kWZgrLyrJHWi8L5d
X5pRjWkg69reDh5uGdHYBXOgbb/xrcLrwSJsNHZZTHzIN7JClP9I7nj8EH8sMM4Z
/T1LWGyGV+jt37LeKOO+4bvoaIDh04rsEGqW6Zz+fEoHWsY3Gjz5mk/KtkagLjqP
LT/ApAMoTkGu1OKdpxr4
=YnVe
-----END PGP SIGNATURE-----

--fUYQa+Pmc3FrFX/N--

From muks@isc.org  Sat Jan  4 15:55:35 2014
Return-Path: <muks@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3B0D1AE0C7 for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 15:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YyOJfwrO0-I9 for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 15:55:35 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id 167F41AE0C1 for <dnsop@ietf.org>; Sat,  4 Jan 2014 15:55:35 -0800 (PST)
Received: from totoro.home.mukund.org (unknown [115.118.150.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 1C11AE600EF; Sat,  4 Jan 2014 23:55:25 +0000 (GMT)
Date: Sun, 5 Jan 2014 05:25:23 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Warren Kumari <warren@kumari.net>
Message-ID: <20140104235523.GA24718@totoro.home.mukund.org>
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com> <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com> <20140104235045.GA24696@totoro.home.mukund.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1"
Content-Disposition: inline
In-Reply-To: <20140104235045.GA24696@totoro.home.mukund.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 23:55:36 -0000

--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Jan 05, 2014 at 05:20:45AM +0530, Mukund Sivaraman wrote:
> used in the DS record? For example, the parent operator can use the same
> algorithm, etc. as in the initially configured DS record.

s/algorithm/digest/ here.

		Mukund

--n8g4imXOkfNTN/H1
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iQgcBAEBCgAGBQJSyJ9oAAoJENJq4EOcI417hC1AAL+XQYFHIpHDmwDWy4VoByZH
22Mu5l7NkKaPIRbH3gNy/tjO2b6xvz+0Zm64jzrYr2zgfhnuUCbjv9zunIxnC8HH
4aDGTmbeGIIvvrC6OoX9Uh8XDJmv8B5a4e8u6ippk7D+vWcYEVIqoZoP0olSExV9
Hw+X4p/xwSNSg2rMKhxJw6bKXKidQKtnCZ4XTdr6252tnOJo+++dNSwPFEZIL/f2
zcxjd52/ZJE1jVekwXlIeBOL6A7c3rEWvPp16cmrEL1RmRja8aIdyXdslCmH7RtY
YYXjqPi9OXgBuL+nK1QGf8q7EV45rqFW/rRPbsfFm5w0NWZZoJDU/RxyImOwISgZ
WHCXtaBhFAwFflhcShUAKyyQn6Y9u36oOg+Q1N+v6Uws9mVrrIuxXGMftYAFW3QE
PN8MoBLmAJwexcJ83vpZ4VtFiQ3jUxlhVN9AJeLdbX1QgIRjjmef72c5mXHDqmAx
iNQh7GiPdPrAd5odR9jiML93k4DwDajoo6TFBjQ76N8chXexnlGx+HEZ9cbqSS3m
YRmLARa85OZONUhvCijW6n2RxBztt/W0D8RoWekc7s7QW8kLJgTVLdHal+BqqcaS
7x6xF2MZK6/66807QOHnHuo0ZUcjN8ZW8YoFO0HtqLMsOrxRBraZ4krseR+ThIxE
HMcqLsl4DLQzMwz0lmBFENKUoS+N+7/Bdknrzy9aSaJPD6gXYDyVMpcz5X1hO+b0
23IB2P51iOa1K3wR8pzL4jSTfNl+CWRzIf9aFZSJzKWcHCy0YYssaJavRlZS18vR
3jnMCZogcjH8agrlznLPqFQhrlz7LHPUgr414WT8eOG7cqQW160+AYspPWjX4tEW
0wpWxFqCKQQkqInd5i6FBigfcmjoirq/vxnJ3/RoPFcYyNLJB08SJORjglt+4l/0
f1w1TRi4F8mqgtGn6Epe7NUpCH865ZTmui6nk46BLkLlb1FuC97QLdmeZXrX6lVy
tdDeFltRDR5P3eRFLYeQqprmO6aC/a3z1HrVoSKSdiTQ8oOb5e7rIAt04OPVN2c+
Y7qq+Ll7g94Ib//0O0o+Fvw3rlb+EUfDalDMTnUxYg+op6ACYs+9DLfi6aXO4nje
9d9/B8fbEfnkKV83MVA+xJOLJDwTL4T07EksijoQ6srh9eM/pqBPOJi0zV5xXsKS
lwecIstmw2r8YVaePOj973WGX/1jJGGkHpHo2DNjXmlrqFvmazKr6vPwgoxwFgUq
M5FBOlemuMlgSj8iwcVDaT5PoQ9xchGqiLbgL28qD5yCHiKikSWEtv1vVEPxUdvc
2TJyrl9L9XDAIOk1yXxzJJbPgbkeb9cJE92DZUMFzscMBiYmXsJEQ6DytlzO/jQr
reIdqq0cRP8THRsslhysSbbF1c7Z1dRWpSrKYjfPrEkZHI7wvC6SBQ0ZFcwB3me7
aQmE/hMkglBlCPbel/gHadpKo+bCbQL6B2Rii/VP+54HdABnAzgzMNqD8u0dLH3h
Fqo6RgAN6ft1jQjExCMu7kzoaU+EsfRe7LJOU0C4SA7I+SK6htIyUsxB4bMegR6f
9eus7MWAp1PqxRIyc3y2m3DTfu0kwFJNzbiSF3M3TCNdh/wB5Otr9D85eW1X37wC
BgxHI2C0xtqTivENG4huMOAPXqpkAVEM2ISSx+tk4FwAbbHMdhPiSNJyEPdWg5ZI
SNu6keoDTEnCuiSO+CA+99hGXOyegfJtC+KEWBtq7dzRIpVYqj3Nt+HiNCDs/bQz
az1qew7N9ZUi97FrlJ/m2av6AgYMwGiBt7fOoC/y8zVWrVL7Ze2Brsk/c+192SPr
ndQ+c74U1d8W/xX1NrZvP8SsD08eZC9gEzj4q/DtBGIPLzjLuE/+0GHLUiqaaM+8
aN3reg24H/TVH8s7POfUfbwGM6vHKYHuVOeNbIPHs+wE3dFDEp1HPgdZ6ZKCgVSY
/39BXHokWVHYyFW1yEocG9VfGALuJhh2TAHycptImF6WXFJbPMSgumyQg+MSZYVo
MbNVGOGD7qonTfY9vg7KpQHPZrMljHEU+Ql2eI5YxjWZe6gp3faTgfzwSahmYDXc
admiCv5he87R7yDP3IPVOaMfHIqquRSZsm5LRK6WlpxjpzRDIPhDR1Yd2ru7IJ/g
KEoAqdm6qVvMiIVAs8o5LxTWwi1MBJiZlGAFCF2bNO6D9dBxluGe2ldD8Of3nYSN
1qhpxGK2KdeiWlfGd8l7ZTmnjyqMasRLCeapPcTdwrao40WfVI8KpBL5tUoAZEI+
BqxnNgZ8K5TrkyqoIwijqFhpHBUYqcT+YqXZMrLN7DinMM8svQ4k6N5WIj/b/xjo
OM31+W8YKX9waRBFP5+fyGTtLUifmL8B6gwYfKTFD1JJHBLmEbWtFgmZa8+qmZxj
BpQaJY6lBPoqPYVRbs9HEKkutyYQDjo72qov+vQAKYqQjD/bG6NdpbcEjEF+VuGV
NleTn52K3/nC0O2ox1ctXW+ryv7jLzghxXD47/DgwJ91CEWQt2t/kxQsg5tHny90
xhuZ8TCPsYnAPuIyJe3jnOX+dt5SZUNlPG2OIpMzLsQLJsXF0jP2IJ2VrYcXSsYO
swI6EwlhARlvM26DMlprhQNXzAHb0F9tYt7eRmzOWg6gLD+2iLFKomNmpjc5Es3l
q74+veI3pVWm8O3s6o5GZtPBTJ6YbbC+mK9pVxfRT5VW5tjfp9q89CEfVMvVkESp
/LW1CnSTdpI3edwK8JnG
=pY45
-----END PGP SIGNATURE-----

--n8g4imXOkfNTN/H1--

From warren@kumari.net  Sat Jan  4 17:52:25 2014
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96FA1AE0CF for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 17:52:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.723
X-Spam-Level: 
X-Spam-Status: No, score=0.723 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iv2q0Ouwn2ym for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 17:52:21 -0800 (PST)
Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) by ietfa.amsl.com (Postfix) with ESMTP id 0BAB81AE09E for <dnsop@ietf.org>; Sat,  4 Jan 2014 17:52:20 -0800 (PST)
Received: by mail-we0-f181.google.com with SMTP id x55so14513906wes.40 for <dnsop@ietf.org>; Sat, 04 Jan 2014 17:52:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=F9XqkMGABuTigfB/SrHtlRTkd6RosIoEY7Kj8QF8O4E=; b=mO2RLSC0U09yOI3QiOTiA8Ws15KWYMbj8lATQRCQ/whZ85eYv5IKDrMgAmOupFUIQx wIIRFfHWaKX/SajEHCA8TXwYddaKYqEq5WmtXREauuiW2lt+eLiNePoXnoNeH2kF1rNz ZWM7icXSkbPseepZ2oSmrm/PHKWWjiQ0aCC1NJa8kMgqEzqtGuIA28X7BOLui3WV7OKM dGSBx8Ys18SMDhUVkxxdYaC0VMnp4U50tcZnz9lCk+I9Lxm1Kn3jFOrwvqYu8NVCNorl Zjgln195cOk1OPUhqP/OYTB6cuTZwUn6suVK2xsrxIY0NREDUFWUn762jdXe8seQQqsv 9STg==
X-Gm-Message-State: ALoCoQlKIRx3PVHlRoviya5y+XXwOw5sPqIa5bhgEemy5n6yCWzJkYc9oStjzVA6cMOZmG1f3FHx
MIME-Version: 1.0
X-Received: by 10.194.6.161 with SMTP id c1mr88049wja.89.1388886732634; Sat, 04 Jan 2014 17:52:12 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Sat, 4 Jan 2014 17:52:12 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <20140104235045.GA24696@totoro.home.mukund.org>
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com> <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com> <20140104235045.GA24696@totoro.home.mukund.org>
Date: Sat, 4 Jan 2014 20:52:12 -0500
Message-ID: <CAHw9_iJ3z58PpoLi+1Cb6mgAo-8mNv9E_m-t-CwOZDVJ1q=vCA@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: Mukund Sivaraman <muks@isc.org>
Content-Type: multipart/alternative; boundary=047d7b4175a355116304ef2f64da
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jan 2014 01:52:26 -0000

--047d7b4175a355116304ef2f64da
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Jan 4, 2014 at 6:50 PM, Mukund Sivaraman <muks@isc.org> wrote:

> Hi Warren
>
> On Sat, Jan 04, 2014 at 04:21:03PM -0500, Warren Kumari wrote:
> > We think that this resolves the open comments and is ready for WGLC.
>
> Here are some comments:
>

Awesome, thank you for the detailed review (and even more so for the text
:-))
I have incorporated most of your comments / suggestions - a few of your
comments / questions require some more thought / discussions with
co-authors, but I wanted to respond on the ones I've incorporated.




>
> Section 1
> ---------
>
> > CDS only allows transferring information about DNSSEC keys (DS and
> > DNSKEY) from the child to the parental agent.  It lists exactly what
>
> "CDS" is used without any prior description of it.
>

Doh! Thank you.
Changed it to: "The solution described in this document only allows..." to
avoid cluttering up the Into.


>
> Section 1.1
> -----------
>
> Use of punctuation in this section can be improved.
>
> > There terminology we use is defined in this section
>
> "There terminology..." => "The terminology...".
>
>
DONE.


> Section 2.1
> -----------
>
> When mentioning RRtypes (NS, DS, etc.), it would be good to cite the
> relevant RFCs where they were introduced.
>

Fair 'nuff.
DONE.


>
> > The second RRset the parent sometimes publishes is the DS set.  The
> > DS RRset provides information about the key(s) that the child has
> > told the parent it will use to sign its DNSKEY RRset.  In DNSSEC
>
> May I suggest changing "keys(s)" => "DNSKEY(s)"?
>
>
You may :-)
DONE.



> > As the DS record can only be present at the parent RFC4034 [RFC4034],
> > some other record/method is needed to automate the expression of what
> > the parental zone DS records contents ought to be.  One possibility
> > is to use flags in the DNSKEY record.  If the SEP bit is set, this
>
> I suggest rewriting this sentence:
>
> "As the DS record can only be present at the parent RFC4034 [RFC4034],
> some method is needed to automate which DNSKEYs are picked to be
> represented in the parent zone's DS records."
>

I changed that slightly to be:
As the DS record can only be present at the parent, some other
record/method is needed to automate which DNSKEYs are picked to be
represented in the parent zone's DS records.
(added record / method). Does that work for you?



> A sentence explaining why a method is needed to automate locating entry
> point keys would be good to have here.
>

Fair 'nuff.
I'll chat with Olafur about this (and your other comments in this section)
to try draft better text. I cannot remember all the details, but AFAIR
Olafur explained the reason well in an email somewhere- will try drudge
that up...


>
> > indicates that the DNSKEY is intended for use as a secure entry
> > point.  This DNSKEY signs the DNSKEY RRset, and the Parental Agent
> > can calculate DS records based on that.  But this fails to meet some
> > operating needs, including the child having no influence what DS
>
> Does this mean that the Parental Agent automatically picks up DNSKEY RRs
> with SEP=1 from the child zone? (How are these DNSKEYs validated?) This
> should be explained.
>
> > digest algorithms are used and DS records can only be published for
> > keys that are in the DNSKEY RRset.
>
> Does this imply use of additionally configured trust anchors when such
> keys are not in the DNSKEY RRset? Such minor clues are useful when
> reading.
>
> Section 2.2
> -----------
>
> >                                        ... in which an organization
> > may delegate parts of its name-space to be operated by a group that
> > is not the same as that which operates the enterprise's DNS servers.
>
> Do "organization" and "enterprise" in the trimmed context above refer to
> the same entity? If the word "enterprise" covers all organizations,
> "enterprise's DNS servers" seems to mean one particular organization's
> DNS servers.
>
> I was not able to follow this paragraph (though I follow what is
> intended to be described).
>

How is:
"In another common case an enterprise may delegate parts of its name-space
to be operated by a group that is not the same as that which operates the
enterprise's DNS servers. In this case the flow of information is
frequently handled in either an ad hoc manner or via some corporate
mechanism; this can range from email to fully-automated operation. The word
enterprise above covers all organizations where the domains are not sold on
the open market and there is some relationship between the entities."

Still a little wordy, but I think better?


>
> Section 2.2.1
> -------------
>
> > A further complication is when the Child DNS Operation is not the
> > Child.  There are two common cases of this,
>
> "Child DNS Operation" => "Child DNS operator"
>

DONE.


>
> >   If the Parental Agent is the DNS operator, life is much easier, as
> >   the Parental Agent can inject any delegation changes directly into
> >   the Parents Provisioning system.  The techniques described below are
> >   not needed in the case when Parental Agent is the DNS operator.
>
> "Parents Provisioning system" => "Parent's Provisioning system"
>

DONE.


>
> >   Some parents want the child to express the changes in trust anchors
> >   via DS records, while others want to receive DNSKEY records and
>
> Is "trust anchor" used according to its definition here? Specifically it
> pertains to a resolver's configuration. There is a similar use of "trust
> anchor" in the abstract too.
>

Hmmm... We mean the DNSSEC key information. AFAIR we used the phrase 'trust
anchor' to decouple from either DNSKEY or DS.
How is: "Some parents want the child to express their DNSKEYS in the form
of DS records, while others want to receive the DNSKEY records and
calculate the DS records themselves."?

>
> > interface, to "upload / paste-in the zone's DS information".  The
> > action of logging in through the delegation account user interface
> > authenticates that the user is authorized to change delegation
> > information published in the parent zone.  In the case where the
>
> "... change delegation information *for the child* published in the
> parent zone." (i.e., not all delegation information in the parent zone.)
>

;-) Cute.

DONE.


>
> > Furthermore when this is a manual process with cut and paste;
> > operational mistakes will happen. Or worse the update action in not
> > performed at all.
>
> Please replace the above with the following (punctuation and typo
> changes):
>
> "Furthermore when this is a manual process with cut and paste,
> operational mistakes will happen, or worse, the update action is not
> performed at all."
>
>
Excellent. Thanks for the text.
DONE.


> Section 3
> ---------
>
> > This document specifies two new DNS RRtypes (CDS and CDNSKEY) that
> > indicates what the Child wants to be in the parents DS RRset.  It
>
> Instead of "to be in the", I suggest something like:
>
> "... what the Child wants to be included in the parent's DS RRset."
>
> "... what the Child wants the parent's DS RRset to contain."
>
> (also note the apostrophe in "parent's").
>

DONE and DONE.


>
> > allows the Child to present DS records and / or DNSKEY records (for
> > those parents who would rather generate the DS records for their
> > children).
>
> > [RFC Editor: Please remove this paragraph before publication] Version
> > -04 of this document defined a new record (CTA) that could hold
> >  either a DS or a DNSKEY record (with a selector to differentiate
> >  between them). ]
>
> Where is version -04 of this document? What is this CTA record it is
> referring to?
>

Doh. The document is
http://tools.ietf.org/id/draft-kumari-ogud-dnsop-cds-04.txt -- this was
before this was adopted, I'd forgotten to update the text. Now fixed.
The CTA record was the closest to consensus I've seen DNSOP come recently
-- basically there was consensus that it was a shitty idea and I should be
beaten round the head for suggesting it :-)



> Section 5
> ---------
>
> It is important to add a note here that the Child DNS Operator (or some
> software) must delete old DNSKEYs only after verifying that the parent
> zone has updated its DS records to match the new ones.
>
> It is also important for the Child to not directly switch CDS / CDNSKEY
> RRs (once published):
>
> * before sending them through DNSKEY RRs first, and
>
> * before verifying that the parent has updated to the new CDS / CDNSKEY
>   data
>
> as the parent may be in the process of updating to the new DS records
> when such a change happens, breaking the chain.
>

Will do. Will wait to discuss with Olafur -- my brain is mush at the
moment...

>
> Section 6.1.1
> -------------
>
> > environments the registry is prohibited from talking to the
> > registrant.  In most these cases the registrant has a business
>
> "most these cases" => "most of these cases"
>

DONE.


>
> Section 6.1.2
> -------------
>
> > DNSSEC, these mechanisms can be unauthenticated (for example, a child
> > could call his parent and request the CDS action be performed, an
>
> "could call his parent" => "could call its parent"
>

DONE.


>
> What does "CDS action" mean here? It should be described or this
> sentence could be rewritten.
>

DONE.
"As the CDS / CDNSKEY records are validated with DNSSEC, these mechanisms
can be unauthenticated (for example, a child could telephone its parent and
request that they process the new CDS or CDNSKEY record, an unauthenticated
POST could be made to a webserver (with rate-limiting), etc.)"


>
> Section 6.2
> -----------
>
> If every nameserver is to be checked for the CDS / CDNSKEY RRs, what is
> the action to be taken when there is a mismatch? Which CDS is used?
>

Will fix.


>
>
> Section 9
> ---------
>
> > This work is for the normal case, when things go wrong there is only
> > so much that automation can fix.
>
> Please change the comma to a full-stop.
>

DONE.

>
> > not detected before the DS in parent is changed.  If this type of
> > change takes place, the child need to contact the parent (possibly
>
> "child need to" => "child needs to"
>

DONE.

>
>
> > While it may be tempting, this SHOULD NOT be used for initial
> > enrollment of keys since there is no way to ensure that the initial
> > key is the correct one.  If is used, strict rules for inclusion of
>
> Perhaps "authentic" or "valid" are better words than "correct" in this
> context.
>

Hmmm... Actually I'm not sure. Perhaps "correct" is not correct. Will need
to think more.



>
> Some overall notes
> ------------------
>
> "Child operator" and "Child DNS operator" are both used. Please update
> the document to use the one defined in the "Terminology" section.
>

Good catch.
DONE.


>
> Can't the equivalent of CDS / CDNSKEY be achieved by introducing
> additional DNSKEY RRs (with SEP=1) in the child zone that are polled by
> the Parent DNS operator?


Technically yes, but see below.


> Is it really so important that the child must
> have control (overriding the parent's choice) over the value of fields
> used in the DS record? For example, the parent operator can use the same
> algorithm, etc. as in the initially configured DS record.
>

This has been discussed and the consensus was that it was preferable to be
explicit that the child want an action to occur -- this allows children to
opt-in or not.
Registrars and registries want to be able to log the fact  / audit that the
child has requested this to occur -- having a separate record to signal
this allows that.
A separate record type also allows a child to pre-publish a DNSKEY record
before using it / request that the parent stops publishing it (when aging
out).


>
>                 Mukund

--047d7b4175a355116304ef2f64da
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Jan 4, 2014 at 6:50 PM, Mukund Sivaraman <span dir=3D"ltr">=
&lt;<a href=3D"mailto:muks@isc.org" target=3D"_blank">muks@isc.org</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Hi Warren<br>
<div class=3D"im"><br>
On Sat, Jan 04, 2014 at 04:21:03PM -0500, Warren Kumari wrote:<br>
&gt; We think that this resolves the open comments and is ready for WGLC.<b=
r>
<br>
</div>Here are some comments:<br></blockquote><div><br></div><div>Awesome, =
thank you for the detailed review (and even more so for the text :-))</div>=
<div>I have incorporated most of your comments / suggestions - a few of you=
r comments / questions require some more thought / discussions with co-auth=
ors, but I wanted to respond on the ones I&#39;ve incorporated.</div>
<div><br></div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-colo=
r:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Section 1<br>
---------<br>
<br>
&gt; CDS only allows transferring information about DNSSEC keys (DS and<br>
&gt; DNSKEY) from the child to the parental agent. =A0It lists exactly what=
<br>
<br>
&quot;CDS&quot; is used without any prior description of it.<br></blockquot=
e><div><br></div><div>Doh! Thank you.</div><div>Changed it to: &quot;The so=
lution described in this document only allows...&quot; to avoid cluttering =
up the Into.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<br>
Section 1.1<br>
-----------<br>
<br>
Use of punctuation in this section can be improved.<br>
<br>
&gt; There terminology we use is defined in this section<br>
<br>
&quot;There terminology...&quot; =3D&gt; &quot;The terminology...&quot;.<br=
>
<br></blockquote><div><br></div><div>DONE.</div><div>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1p=
x;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1=
ex">

Section 2.1<br>
-----------<br>
<br>
When mentioning RRtypes (NS, DS, etc.), it would be good to cite the<br>
relevant RFCs where they were introduced.<br></blockquote><div><br></div><d=
iv>Fair &#39;nuff.</div><div>DONE.</div><div>=A0</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border=
-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<br>
&gt; The second RRset the parent sometimes publishes is the DS set. =A0The<=
br>
&gt; DS RRset provides information about the key(s) that the child has<br>
&gt; told the parent it will use to sign its DNSKEY RRset. =A0In DNSSEC<br>
<br>
May I suggest changing &quot;keys(s)&quot; =3D&gt; &quot;DNSKEY(s)&quot;?<b=
r>
<br></blockquote><div><br></div><div>You may :-)</div><div>DONE.</div><div>=
<br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);b=
order-left-style:solid;padding-left:1ex">

&gt; As the DS record can only be present at the parent RFC4034 [RFC4034],<=
br>
&gt; some other record/method is needed to automate the expression of what<=
br>
&gt; the parental zone DS records contents ought to be. =A0One possibility<=
br>
&gt; is to use flags in the DNSKEY record. =A0If the SEP bit is set, this<b=
r>
<br>
I suggest rewriting this sentence:<br>
<br>
&quot;As the DS record can only be present at the parent RFC4034 [RFC4034],=
<br>
some method is needed to automate which DNSKEYs are picked to be<br>
represented in the parent zone&#39;s DS records.&quot;<br></blockquote><div=
><br></div><div>I changed that slightly to be:</div><div>As the DS record c=
an only be present at the parent, some other record/method is needed to aut=
omate which DNSKEYs are picked to be represented in the parent zone&#39;s D=
S records.</div>
<div>(added record / method). Does that work for you?</div><div><br></div><=
div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-=
style:solid;padding-left:1ex">

A sentence explaining why a method is needed to automate locating entry<br>
point keys would be good to have here.<br></blockquote><div><br></div><div>=
Fair &#39;nuff.</div><div>I&#39;ll chat with Olafur about this (and your ot=
her comments in this section) to try draft better text. I cannot remember a=
ll the details, but AFAIR Olafur explained the reason well in an email some=
where- will try drudge that up...</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<br>
&gt; indicates that the DNSKEY is intended for use as a secure entry<br>
&gt; point. =A0This DNSKEY signs the DNSKEY RRset, and the Parental Agent<b=
r>
&gt; can calculate DS records based on that. =A0But this fails to meet some=
<br>
&gt; operating needs, including the child having no influence what DS<br>
<br>
Does this mean that the Parental Agent automatically picks up DNSKEY RRs<br=
>
with SEP=3D1 from the child zone? (How are these DNSKEYs validated?) This<b=
r>
should be explained.<br>
<br>
&gt; digest algorithms are used and DS records can only be published for<br=
>
&gt; keys that are in the DNSKEY RRset.<br>
<br>
Does this imply use of additionally configured trust anchors when such<br>
keys are not in the DNSKEY RRset? Such minor clues are useful when<br>
reading.<br>
<br>
Section 2.2<br>
-----------<br>
<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0... in which an organization<br>
&gt; may delegate parts of its name-space to be operated by a group that<br=
>
&gt; is not the same as that which operates the enterprise&#39;s DNS server=
s.<br>
<br>
Do &quot;organization&quot; and &quot;enterprise&quot; in the trimmed conte=
xt above refer to<br>
the same entity? If the word &quot;enterprise&quot; covers all organization=
s,<br>
&quot;enterprise&#39;s DNS servers&quot; seems to mean one particular organ=
ization&#39;s<br>
DNS servers.<br>
<br>
I was not able to follow this paragraph (though I follow what is<br>
intended to be described).<br></blockquote><div><br></div><div>How is:</div=
><div>&quot;In another common case an enterprise may delegate parts of its =
name-space to be operated by a group that is not the same as that which ope=
rates the enterprise&#39;s DNS servers. In this case the flow of informatio=
n is frequently handled in either an ad hoc manner or via some corporate me=
chanism; this can range from email to fully-automated operation. The word e=
nterprise above covers all organizations where the domains are not sold on =
the open market and there is some relationship between the entities.&quot;<=
/div>
<div><br></div><div>Still a little wordy, but I think better?</div><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:s=
olid;padding-left:1ex">

<br>
Section 2.2.1<br>
-------------<br>
<br>
&gt; A further complication is when the Child DNS Operation is not the<br>
&gt; Child. =A0There are two common cases of this,<br>
<br>
&quot;Child DNS Operation&quot; =3D&gt; &quot;Child DNS operator&quot;<br><=
/blockquote><div><br></div><div>DONE.</div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<br>
&gt; =A0 If the Parental Agent is the DNS operator, life is much easier, as=
<br>
&gt; =A0 the Parental Agent can inject any delegation changes directly into=
<br>
&gt; =A0 the Parents Provisioning system. =A0The techniques described below=
 are<br>
&gt; =A0 not needed in the case when Parental Agent is the DNS operator.<br=
>
<br>
&quot;Parents Provisioning system&quot; =3D&gt; &quot;Parent&#39;s Provisio=
ning system&quot;<br></blockquote><div><br></div><div>DONE.</div><div>=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex">

<br>
&gt; =A0 Some parents want the child to express the changes in trust anchor=
s<br>
&gt; =A0 via DS records, while others want to receive DNSKEY records and<br=
>
<br>
Is &quot;trust anchor&quot; used according to its definition here? Specific=
ally it<br>
pertains to a resolver&#39;s configuration. There is a similar use of &quot=
;trust<br>
anchor&quot; in the abstract too.<br></blockquote><div><br></div><div>Hmmm.=
.. We mean the DNSSEC key information. AFAIR we used the phrase &#39;trust =
anchor&#39; to decouple from either DNSKEY or DS.=A0</div><div>How is: &quo=
t;Some parents want the child to express their DNSKEYS in the form of DS re=
cords, while others want to receive the DNSKEY records and calculate the DS=
 records themselves.&quot;?</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
&gt; interface, to &quot;upload / paste-in the zone&#39;s DS information&qu=
ot;. =A0The<br>
&gt; action of logging in through the delegation account user interface<br>
&gt; authenticates that the user is authorized to change delegation<br>
&gt; information published in the parent zone. =A0In the case where the<br>
<br>
&quot;... change delegation information *for the child* published in the<br=
>
parent zone.&quot; (i.e., not all delegation information in the parent zone=
.)<br></blockquote><div><br></div><div>;-) Cute.</div><div><br></div><div>D=
ONE.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);b=
order-left-style:solid;padding-left:1ex">

<br>
&gt; Furthermore when this is a manual process with cut and paste;<br>
&gt; operational mistakes will happen. Or worse the update action in not<br=
>
&gt; performed at all.<br>
<br>
Please replace the above with the following (punctuation and typo<br>
changes):<br>
<br>
&quot;Furthermore when this is a manual process with cut and paste,<br>
operational mistakes will happen, or worse, the update action is not<br>
performed at all.&quot;<br>
<br></blockquote><div><br></div><div>Excellent. Thanks for the text.</div><=
div>DONE.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,2=
04);border-left-style:solid;padding-left:1ex">

Section 3<br>
---------<br>
<br>
&gt; This document specifies two new DNS RRtypes (CDS and CDNSKEY) that<br>
&gt; indicates what the Child wants to be in the parents DS RRset. =A0It<br=
>
<br>
Instead of &quot;to be in the&quot;, I suggest something like:<br>
<br>
&quot;... what the Child wants to be included in the parent&#39;s DS RRset.=
&quot;<br>
<br>
&quot;... what the Child wants the parent&#39;s DS RRset to contain.&quot;<=
br>
<br>
(also note the apostrophe in &quot;parent&#39;s&quot;).<br></blockquote><di=
v><br></div><div>DONE and DONE.</div><div>=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le=
ft-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<br>
&gt; allows the Child to present DS records and / or DNSKEY records (for<br=
>
&gt; those parents who would rather generate the DS records for their<br>
&gt; children).<br>
<br>
&gt; [RFC Editor: Please remove this paragraph before publication] Version<=
br>
&gt; -04 of this document defined a new record (CTA) that could hold<br>
&gt; =A0either a DS or a DNSKEY record (with a selector to differentiate<br=
>
&gt; =A0between them). ]<br>
<br>
Where is version -04 of this document? What is this CTA record it is<br>
referring to?<br></blockquote><div><br></div><div>Doh. The document is=A0<a=
 href=3D"http://tools.ietf.org/id/draft-kumari-ogud-dnsop-cds-04.txt">http:=
//tools.ietf.org/id/draft-kumari-ogud-dnsop-cds-04.txt</a> -- this was befo=
re this was adopted, I&#39;d forgotten to update the text. Now fixed.</div>
<div>The CTA record was the closest to consensus I&#39;ve seen DNSOP come r=
ecently -- basically there was consensus that it was a shitty idea and I sh=
ould be beaten round the head for suggesting it :-)</div><div><br></div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<br>
Section 5<br>
---------<br>
<br>
It is important to add a note here that the Child DNS Operator (or some<br>
software) must delete old DNSKEYs only after verifying that the parent<br>
zone has updated its DS records to match the new ones.<br>
<br>
It is also important for the Child to not directly switch CDS / CDNSKEY<br>
RRs (once published):<br>
<br>
* before sending them through DNSKEY RRs first, and<br>
<br>
* before verifying that the parent has updated to the new CDS / CDNSKEY<br>
=A0 data<br>
<br>
as the parent may be in the process of updating to the new DS records<br>
when such a change happens, breaking the chain.<br></blockquote><div><br></=
div><div>Will do. Will wait to discuss with Olafur -- my brain is mush at t=
he moment...</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-=
left-style:solid;padding-left:1ex">

<br>
Section 6.1.1<br>
-------------<br>
<br>
&gt; environments the registry is prohibited from talking to the<br>
&gt; registrant. =A0In most these cases the registrant has a business<br>
<br>
&quot;most these cases&quot; =3D&gt; &quot;most of these cases&quot;<br></b=
lockquote><div><br></div><div>DONE.</div><div>=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;borde=
r-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<br>
Section 6.1.2<br>
-------------<br>
<br>
&gt; DNSSEC, these mechanisms can be unauthenticated (for example, a child<=
br>
&gt; could call his parent and request the CDS action be performed, an<br>
<br>
&quot;could call his parent&quot; =3D&gt; &quot;could call its parent&quot;=
<br></blockquote><div><br></div><div>DONE.</div><div>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1p=
x;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1=
ex">

<br>
What does &quot;CDS action&quot; mean here? It should be described or this<=
br>
sentence could be rewritten.<br></blockquote><div><br></div><div>DONE.</div=
><div>&quot;As the CDS / CDNSKEY records are validated with DNSSEC, these m=
echanisms can be unauthenticated (for example, a child could telephone its =
parent and request that they process the new CDS or CDNSKEY record, an unau=
thenticated POST could be made to a webserver (with rate-limiting), etc.)&q=
uot;</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<br>
Section 6.2<br>
-----------<br>
<br>
If every nameserver is to be checked for the CDS / CDNSKEY RRs, what is<br>
the action to be taken when there is a mismatch? Which CDS is used?<br></bl=
ockquote><div><br></div><div>Will fix.</div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<br>
<br>
Section 9<br>
---------<br>
<br>
&gt; This work is for the normal case, when things go wrong there is only<b=
r>
&gt; so much that automation can fix.<br>
<br>
Please change the comma to a full-stop.<br></blockquote><div><br></div><div=
>DONE.=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">

<br>
&gt; not detected before the DS in parent is changed. =A0If this type of<br=
>
&gt; change takes place, the child need to contact the parent (possibly<br>
<br>
&quot;child need to&quot; =3D&gt; &quot;child needs to&quot;<br></blockquot=
e><div><br></div><div>DONE.=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">

<br>
<br>
&gt; While it may be tempting, this SHOULD NOT be used for initial<br>
&gt; enrollment of keys since there is no way to ensure that the initial<br=
>
&gt; key is the correct one. =A0If is used, strict rules for inclusion of<b=
r>
<br>
Perhaps &quot;authentic&quot; or &quot;valid&quot; are better words than &q=
uot;correct&quot; in this<br>
context.<br></blockquote><div><br></div><div>Hmmm... Actually I&#39;m not s=
ure. Perhaps &quot;correct&quot; is not correct. Will need to think more.</=
div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,2=
04,204);border-left-style:solid;padding-left:1ex">

<br>
Some overall notes<br>
------------------<br>
<br>
&quot;Child operator&quot; and &quot;Child DNS operator&quot; are both used=
. Please update<br>
the document to use the one defined in the &quot;Terminology&quot; section.=
<br></blockquote><div><br></div><div>Good catch.</div><div>DONE.</div><div>=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex">

<br>
Can&#39;t the equivalent of CDS / CDNSKEY be achieved by introducing<br>
additional DNSKEY RRs (with SEP=3D1) in the child zone that are polled by<b=
r>
the Parent DNS operator? </blockquote><div><br></div><div>Technically yes, =
but see below.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
Is it really so important that the child must<br>
have control (overriding the parent&#39;s choice) over the value of fields<=
br>
used in the DS record? For example, the parent operator can use the same<br=
>
algorithm, etc. as in the initially configured DS record.<br></blockquote><=
div><br></div><div>This has been discussed and the consensus was that it wa=
s preferable to be explicit that the child want an action to occur -- this =
allows children to opt-in or not.=A0</div>
<div>Registrars and registries want to be able to log the fact =A0/ audit t=
hat the child has requested this to occur -- having a separate record to si=
gnal this allows that.</div><div>A separate record type also allows a child=
 to pre-publish a DNSKEY record before using it / request that the parent s=
tops publishing it (when aging out).</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<span class=3D""><font color=3D"#888888"><br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mukund</font></span></blockquote></div></di=
v></div>

--047d7b4175a355116304ef2f64da--

From muks@isc.org  Sat Jan  4 20:57:39 2014
Return-Path: <muks@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F272C1AD67A for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 20:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZHjyqFZYORqf for <dnsop@ietfa.amsl.com>; Sat,  4 Jan 2014 20:57:37 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [IPv6:2a01:4f8:140:644b::225]) by ietfa.amsl.com (Postfix) with ESMTP id 12A521AD672 for <dnsop@ietf.org>; Sat,  4 Jan 2014 20:57:37 -0800 (PST)
Received: from totoro.home.mukund.org (unknown [115.118.105.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 42F04E6011C; Sun,  5 Jan 2014 04:57:27 +0000 (GMT)
Date: Sun, 5 Jan 2014 10:27:22 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Warren Kumari <warren@kumari.net>
Message-ID: <20140105045721.GA30643@totoro.home.mukund.org>
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com> <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com> <20140104235045.GA24696@totoro.home.mukund.org> <CAHw9_iJ3z58PpoLi+1Cb6mgAo-8mNv9E_m-t-CwOZDVJ1q=vCA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi"
Content-Disposition: inline
In-Reply-To: <CAHw9_iJ3z58PpoLi+1Cb6mgAo-8mNv9E_m-t-CwOZDVJ1q=vCA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jan 2014 04:57:39 -0000

--Qxx1br4bt0+wmkIi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Warren

On Sat, Jan 04, 2014 at 08:52:12PM -0500, Warren Kumari wrote:
> > > As the DS record can only be present at the parent RFC4034 [RFC4034],
> > > some other record/method is needed to automate the expression of what
> > > the parental zone DS records contents ought to be.  One possibility
> > > is to use flags in the DNSKEY record.  If the SEP bit is set, this
> >
> > I suggest rewriting this sentence:
> >
> > "As the DS record can only be present at the parent RFC4034 [RFC4034],
> > some method is needed to automate which DNSKEYs are picked to be
> > represented in the parent zone's DS records."
> >
>=20
> I changed that slightly to be:
> As the DS record can only be present at the parent, some other
> record/method is needed to automate which DNSKEYs are picked to be
> represented in the parent zone's DS records.
> (added record / method). Does that work for you?

This looks good.

> > A sentence explaining why a method is needed to automate locating entry
> > point keys would be good to have here.
> >
>=20
> Fair 'nuff.
> I'll chat with Olafur about this (and your other comments in this section)
> to try draft better text. I cannot remember all the details, but AFAIR
> Olafur explained the reason well in an email somewhere- will try drudge
> that up...

Nod.

> > Do "organization" and "enterprise" in the trimmed context above refer to
> > the same entity? If the word "enterprise" covers all organizations,
> > "enterprise's DNS servers" seems to mean one particular organization's
> > DNS servers.
> >
> > I was not able to follow this paragraph (though I follow what is
> > intended to be described).
> >
>=20
> How is:
> "In another common case an enterprise may delegate parts of its name-space
> to be operated by a group that is not the same as that which operates the
> enterprise's DNS servers. In this case the flow of information is
> frequently handled in either an ad hoc manner or via some corporate
> mechanism; this can range from email to fully-automated operation. The wo=
rd
> enterprise above covers all organizations where the domains are not sold =
on
> the open market and there is some relationship between the entities."
>=20
> Still a little wordy, but I think better?

Yes this is much better to understand.

> > >   Some parents want the child to express the changes in trust anchors
> > >   via DS records, while others want to receive DNSKEY records and
> >
> > Is "trust anchor" used according to its definition here? Specifically it
> > pertains to a resolver's configuration. There is a similar use of "trust
> > anchor" in the abstract too.
> >
>=20
> Hmmm... We mean the DNSSEC key information. AFAIR we used the phrase 'tru=
st
> anchor' to decouple from either DNSKEY or DS.
> How is: "Some parents want the child to express their DNSKEYS in the form
> of DS records, while others want to receive the DNSKEY records and
> calculate the DS records themselves."?

This is good. How about "supply" or "provide" instead of "express"?

> > > allows the Child to present DS records and / or DNSKEY records (for
> > > those parents who would rather generate the DS records for their
> > > children).
> >
> > > [RFC Editor: Please remove this paragraph before publication] Version
> > > -04 of this document defined a new record (CTA) that could hold
> > >  either a DS or a DNSKEY record (with a selector to differentiate
> > >  between them). ]
> >
> > Where is version -04 of this document? What is this CTA record it is
> > referring to?
> >
>=20
> Doh. The document is
> http://tools.ietf.org/id/draft-kumari-ogud-dnsop-cds-04.txt -- this was
> before this was adopted, I'd forgotten to update the text. Now fixed.
> The CTA record was the closest to consensus I've seen DNSOP come recently
> -- basically there was consensus that it was a shitty idea and I should be
> beaten round the head for suggesting it :-)

Nod. I didn't realise this had gone through many versions already. :)

> > It is important to add a note here that the Child DNS Operator (or some
> > software) must delete old DNSKEYs only after verifying that the parent
> > zone has updated its DS records to match the new ones.
> >
> > It is also important for the Child to not directly switch CDS / CDNSKEY
> > RRs (once published):
> >
> > * before sending them through DNSKEY RRs first, and
> >
> > * before verifying that the parent has updated to the new CDS / CDNSKEY
> >   data
> >
> > as the parent may be in the process of updating to the new DS records
> > when such a change happens, breaking the chain.
> >
>=20
> Will do. Will wait to discuss with Olafur -- my brain is mush at the
> moment...

Nod. This draft is small, so perhaps it won't be too bad to include a
section listing ordered steps from how a parent fetches a new CDS or
CDNSKEY to when the DS record is published. Similarly, steps for how a
child adds new CDS and CDNSKEY records and removes the old keys can be
included.

The hazard of not implementing it correctly is that resolvers determine
the data is bogus and things fail to resolve. So it's better to provide
step-by-step instructions that implementors can keep in mind.

> > What does "CDS action" mean here? It should be described or this
> > sentence could be rewritten.
> >
>=20
> DONE.
> "As the CDS / CDNSKEY records are validated with DNSSEC, these mechanisms
> can be unauthenticated (for example, a child could telephone its parent a=
nd
> request that they process the new CDS or CDNSKEY record, an unauthenticat=
ed
> POST could be made to a webserver (with rate-limiting), etc.)"

This looks good.

> > If every nameserver is to be checked for the CDS / CDNSKEY RRs, what is
> > the action to be taken when there is a mismatch? Which CDS is used?
> >
>=20
> Will fix.

Nod.

> > Can't the equivalent of CDS / CDNSKEY be achieved by introducing
> > additional DNSKEY RRs (with SEP=3D1) in the child zone that are polled =
by
> > the Parent DNS operator?
>=20
>=20
> Technically yes, but see below.
>=20
>=20
> > Is it really so important that the child must
> > have control (overriding the parent's choice) over the value of fields
> > used in the DS record? For example, the parent operator can use the same
> > algorithm, etc. as in the initially configured DS record.
> >
>=20
> This has been discussed and the consensus was that it was preferable to be
> explicit that the child want an action to occur -- this allows children to
> opt-in or not.
> Registrars and registries want to be able to log the fact  / audit that t=
he
> child has requested this to occur -- having a separate record to signal
> this allows that.
> A separate record type also allows a child to pre-publish a DNSKEY record
> before using it / request that the parent stops publishing it (when aging
> out).

I follow why it was done now. So this is to clearly mark that the
CDNSKEY is for the specific purpose of pulling into the parent (as per
this draft) and other DNSKEYs are not picked up. It may be good to add
this as a comment in the introduction (why a new record type was
created).

Because the wire format of CDNSKEY matches DNSKEY exactly, why hasn't an
extra flag been introduced in the DNSKEY RDATA instead of creating
additional RRtypes? The DNSKEY Flags field is 16-bits wide and only 2
bits are currently in use. Software that is supposed to manage this on
the child DNS operator side can easily switch the key from
"marked-for-pickup-by-parent" to "normal-DNSKEY" by changing a bit.

Using the DNSKEY RRtype would mean that existing resolvers can be used
as-is to validate the new DNSKEYs when fetched by the parent DNS
operator. Existing authoritative servers can serve them on the child
operator side. Implementors have less code to maintain.

		Mukund

--Qxx1br4bt0+wmkIi
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iQgcBAEBCgAGBQJSyOYvAAoJENJq4EOcI417k24//iNmdzzyUO6FwOFnJCktOMFD
z8yYELQCe112wgZqZ/bOtkw8E1BiTok4xRp38tjbqGDGdqFCcMmbfu7r8593QA3N
RCiHeKRLnYlrnHm8ZDOktV2m8K9MsyfUMW8rcCM+MUwdQxpfgYPRc57dQQnYXf8r
X3361PaRYVglVBYTyQ1vOiqCuBR/xSuxwpO0aPDy8xv1qUoAvrMN4QQlB/c1ggLO
iJjk+kepKTXmdEdNyiK0RaFuSKJ+7MnHHUeapMTpJP9TyoQVozE5gYg5g5D76Ziv
cMs4EekR2qCvlBCWcnE7WqJg/EWfRQyx7wX87hfZrdJ5AA/g1GG5vtnrvTvozC5s
xGlIAw+pLRayrumLRPnquylWEgMSQuR2TqQ+VsXKbK9RUNB6y2fqHLV3L0JBW/7Y
8WNw2rqFvylRrmRjbX/6TAMuTlgJEKS7DmIGdS1MeL+1ss19kv4m/2Y0LoKxjUlM
2/V5FEuu/LJ5cXMfD8GoFWeB1Y5vFL6hnkXAZ7yOHfMKpH4aJQmLFsjSMf9jAbdM
vV/XPG6Iuxsw7YdEMZ9WlpzayyYYUuF43zQzixpcpdJph+YyayuwMMgZQwm1wx9M
Ka7dP25YHAo/cpBQiR5RiKqIp/en9dtPrkSWjNg5EXyfwkOHtkk49FuY2oZPizvq
CnISeUbz6v0F3JE7Ihpv4Xf2tlc3AltPo6M+OzgttGtLU6X3ANeWYU735kCCXwzO
z9xxn3ErmhXe6t2iF/69/Fsnm1emVzFFF2dXzbM533yXC+e58ZoyMthUzQbq3v2p
KMW8g3/FHtEWeAsoz2SZK3IIRS2C0Tj0bk4VJAwZRvvCqXoYwplvC3qExLZtzuyW
nLq4lIi+6Svl1VExE+0rsBZbtWwVHsl+XL2YfKfGJq2hw3wA/Ao1jo7S4AHvoBaM
EjovnPgzeWE1Gz7ehMstc7KLsMBhUUtg1D0D2Gm2id0K8gnVWg61zU8gQ6PwdiH2
8v9N6jhq+3Eo83+seenUyUslX6/19bB5D9d/utGc72eQ6I6s+/95vKk8qyf5QA0y
ZuPhGFtAbrstLpZkkW9FLuphvwjnRHsDLguTOVKtzH3bSiAUke9s27BkmU3X7e9R
k1LtqQxdCNSBoJA9u/mRfx5zsvFeNtu8I0e+ONS/q1RNiUBf4KCfG9hnwYZr8sRw
DwkFPjJzwqrNDWlbXzF7zfK9oFL5q4w6mCdN+ihqE4yT9WS+95VFuok6eoiGT7ev
0T16xin6jkL3VzVfjF7eEiKGCFe71Tz8DQK6UjJIA1f34QDI0esRFo/AiOx6c7C4
TPilOeFwQp4SO909WZLKQZNbzovW1CIj/pQIVuOo1t0jlFScdyBSR/WIcSgs1BvE
PhyoZfW5lsqcCgIdbwzVUgEHIGYD6w3ZhKdnvgStaI7BqHJpwff02mAO4jMnHrnI
OncrJWq9+VDfoqo7XPZwIVZDxUBisZA/N/HuuMsH/1axeUIIkL1BvDK+gnsthoAq
IbPgZ3CS3F8zi5r09sf0e7e0GIhFUX2AEE9s1qiPmLOGmA30UEgF9WO2N96l0gUi
4DwLO6rYzGedcxIWuVa0rdoVs3QWvDSkr9dKGfitLA37MR64wiY4HKXDyxW5v44i
LLfpjfLect2s5WlbAZvMpUBBbLsNqeQQcUYKyUTv3yxWIDGOgS63kdiItphIj8tF
ZnfrtdtTyLL8wEULCoRpXFTyuZMAExgCriYzn3EXQXrgDgMcIAN/rEErTE9H4yrH
/Hubxbf/T2/nOeui+J1sT7FSDfu4ucfEVCzxnDtaCZUmgwv+xcutbXLALrJzwoJ9
xVgxtyw49Fexc+uhES8jHD8F1DhgMl6q4sc5VenX0wsywrPJmGzmz05Lmk+TMYbR
gI3k7duN3qJtB9E1pDMfmdpaI50/Q/SMi1N4waGgbnWtPrU5og/ShVwj04dN4gDj
FxJUWwTKUy2tf9MMlWMClYLJEyH1diyYjNMk7lhdRxCPd4dhQdLyVVFksjGdQg9F
+/9G77uJMkR+hxSjiKUKLbUlp3w3zI+MKIN0zm9aAVFby9fsjfLF+MIUPwCszsG2
koKegWFvc8v5FF7SkUmCtIg4wLqUqwtxExexENrxPXISzB8MpdJySTQAPT0+QAYd
4xDFGMWF2ebSGCsZjDU/x7dgZtgg0wE9xRUwkWnhKX2fm9WU4BOT7E1BaUW+J0FG
TffBk7P03k5zGRxquTtezB1XSwvebL6BY2UDte+8REb3uYXrLEcJAoCvqpCIYdl2
6+AvISh50pZprxiLVQa3rK7Ko+rAGIk5+JtWB7xgkRKuuuo+E6grlsQ3II7xQ0o8
osmyJ2lemM6gQq6YF60WzrsaUWa9H4VwnwjJ+WwoWotExZRUwmcYAW/3lw6krIGQ
6QKn6E7dL/tkeXs1EgJOfWcTYR+bw5AsFALrIkkG5vXFeql826FPC55i0hWQ/ifH
J/kvmiMVzr4iYT16eKTSlJZYFVlLci+rXgSH81hINjHceGcb5lwL0blWNn3DASFM
J4cTGoORIBYq3ENKUtEwiTEBdPbv5Xs8D3l4nyLLILlwlxlIDKklsFzgThHhvEeF
mtyaDNf0fyj3JYez58ENm8bZ/HW/GLmhyyonestYBjSHobFtOUwv38wDpLGsP3PH
cmv7ERD3zf1DYYedUTIApBPwMnrZ7lFX1ul60sC+MWbTjdTtPfhbTLhlP/KEvjht
dJEwXuNlS728jR/5u882
=e4tb
-----END PGP SIGNATURE-----

--Qxx1br4bt0+wmkIi--

From suzworldwide@gmail.com  Sun Jan  5 08:39:59 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 699951AEED6 for <dnsop@ietfa.amsl.com>; Sun,  5 Jan 2014 08:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7y0yMwNc8Jb for <dnsop@ietfa.amsl.com>; Sun,  5 Jan 2014 08:39:56 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 984881AEED7 for <dnsop@ietf.org>; Sun,  5 Jan 2014 08:39:56 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id ii20so2180685qab.1 for <dnsop@ietf.org>; Sun, 05 Jan 2014 08:39:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Lv/ZY8D9YmcevEC9wWVVmTxi1jeDfcX1CFS8zLDMS5M=; b=eXJ3H814QzmkT0b6L8TjNOGyepvVLpSPp24QJQV0DCeXlgBe9aoJBVZi5U6QiDzPXU 2IrrEb+d/szgHbBL8aK6QKryfxp1yaetO2M7UYqDZLcZPMUUUE7jPNQ3UZTlatlWpOzs +uyJ+r/9EHZ/wLFMetSjJ2YaxFilQvp7epADlg7hXr9fQlELopBcCFXFI7tTOhWvBT9Z C6fiEy3K1Txjc2iJTkvK9cC73hbKiH0Q4qk3K9D0ihenKSYhpRho8+54NuaHuOLLy4Kf EswZxJAfkH89Um0FTRQgbu6BXT0dRb//qtCCY+8Q9UbIFBOuJcIt4LAbf2Davhb9Yigk poqQ==
X-Received: by 10.224.16.80 with SMTP id n16mr171538757qaa.42.1388939988368; Sun, 05 Jan 2014 08:39:48 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id g10sm95425787qaf.9.2014.01.05.08.39.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 05 Jan 2014 08:39:47 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20131231000412.GV4291@mx1.yitter.info>
Date: Sun, 5 Jan 2014 11:39:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <27E859E9-0E94-4694-B931-B0C4D885D667@gmail.com>
References: <20131231000412.GV4291@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1510)
Cc: christian@grothoff.org, hellekin@gnu.org, dnsop@ietf.org, wachs@net.in.tum.de, jacob@appelbaum.net
Subject: [DNSOP] special names process & context Re: More complete review of draft-grothoff-iesg-special-use-p2p-names-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jan 2014 16:39:59 -0000

Hi,

(chair hat on, not sure it fits right quite yet=85.)

Thanks Andrew for the thorough review on this draft, and everyone for =
substantive followups.

To put the topic of this draft, and "special names" generally, into some =
context:=20

The "special names" registry is established in RFC 6761, which specifies =
"standards action or IESG approval" as the threshold for adding names. =
It also specifies in some detail what an RFC justifying such =
registrations needs to cover. (Section 4, 'If it is determined that =
special handling of a name is required in order to implement some =
desired new functionality, then an IETF "Standards Action" or "IESG =
Approval" specification [RFC5226] MUST be published describing the new =
functionality.' See also the registry at =
http://www.iana.org/assignments/special-use-domain-names/special-use-domai=
n-names.xhtml).

Accordingly, the outcome of a discussion of this draft, or any special =
names request, in DNSOP should be any advice or insight we have as DNS =
experts for the IESG.=20
The WG has no specific role in the process except as we can help the =
IESG decide whether to approve this set of additions to the registry.

Ted Lemon has participated here in earlier discussion of this draft, and =
I hope other IESG members will also feel free to step in and speak for =
themselves on their concerns. But earlier discussion, here and =
elsewhere, suggests that the most helpful input would be along a couple =
of lines:

1. The primary concern is on the specifics of whether this draft =
complies with RFC 6761 adequately to allow DNS implementors and =
operators to treat the proposed names consistently and interoperably, =
without unacceptable side effects.=20

2. It may also be useful to consider any concerns on the scalability or =
architectural implications of special names: Andrew's comments in his =
review on the "deep and extremely confusing path of mixing the domain =
name system and other namespaces," the possibility that such requests =
will not remain rare events, etc. This goes to the question of how high =
the barrier to approval for new special names should be, as the p2p =
draft is the first invocation of RFC 6761 since its publication and =
seems likely to be taken as precedent.


best,
Suzanne

Re:
On Dec 30, 2013, at 7:04 PM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:

> Dear colleagues,
>=20
> I made some remarks in the earlier discussion of
> draft-grothoff-iesg-special-use-p2p-names-00.  In this message, I
> attempt to review draft-grothoff-iesg-special-use-p2p-names-01
> completely.  I hope these remarks are useful.
>=20
> Overall
> =3D=3D=3D=3D=3D=3D=3D
>=20
> I remain extremely concerned that this effort represents another step
> along a deep and extremely confusing path of mixing the domain name
> system and other name spaces.  I think the IETF needs to figure out
> whether we're going to accept that, historically, we had multiple name
> spaces but that now we're going to have one big one; or whether we're
> going to continue pretending that every other name space doesn't end
> up wandering into the DNS anyway.  (If there are additional
> alternatives, I am unable to think of them.)  I think a pragmatic
> answer is to accept that, given the number of places we expose domain
> name slots, anything that uses a name is going to end up having to be
> somehow compatible with domain name slots.  But I think that is a
> wide-ranging discussion that almost certainly needs to be tackled
> #separately from the consideration of this particular draft.
>=20


From bortzmeyer@nic.fr  Mon Jan  6 00:40:14 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 912381AE008 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 00:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YdS_QGUcKca for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 00:40:12 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 40C1B1AE001 for <dnsop@ietf.org>; Mon,  6 Jan 2014 00:40:12 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 667F92802BE; Mon,  6 Jan 2014 09:40:02 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 620C92802BB; Mon,  6 Jan 2014 09:40:02 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 5FAD94C007C; Mon,  6 Jan 2014 09:39:32 +0100 (CET)
Date: Mon, 6 Jan 2014 09:39:32 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Christian Grothoff <grothoff@in.tum.de>
Message-ID: <20140106083932.GA27479@nic.fr>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52C48A4A.6090303@in.tum.de>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] More complete review of draft-grothoff-iesg-special-use-p2p-names-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 08:40:14 -0000

On Wed, Jan 01, 2014 at 10:36:10PM +0100,
 Christian Grothoff <grothoff@in.tum.de> wrote 
 a message of 245 lines which said:

> It is unclear to me how we even _could_ provide such a stable
> document, especially for Namecoin and I2P where I don't even see
> academic publications documenting the system on the horizon.

Also, the request from Andrew Sullivan to have "stable" references is
reasonable (it would be better to have "stable" references) but it is
a "nice to have", it is not mandatory in IETF processes here (RFC
6761, section 4 does not require it, nor any general RFC or IETF
process document does, for instance RFC 2223 - or its never-approved
successor - does not mention that requirment).


From bortzmeyer@nic.fr  Mon Jan  6 00:47:06 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85D521AE00F for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 00:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Pv1BmeaLrf2 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 00:47:05 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 594E01AE001 for <dnsop@ietf.org>; Mon,  6 Jan 2014 00:47:05 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id C8EFE2803C2; Mon,  6 Jan 2014 09:46:56 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id C3ED22802FF; Mon,  6 Jan 2014 09:46:56 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id C17254C0053; Mon,  6 Jan 2014 09:46:26 +0100 (CET)
Date: Mon, 6 Jan 2014 09:46:26 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20140106084626.GB27479@nic.fr>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C051985-6E70-463A-9672-02657842754D@vpnc.org>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop <dnsop@ietf.org>, Christian Grothoff <grothoff@in.tum.de>
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 08:47:06 -0000

On Thu, Jan 02, 2014 at 12:00:14PM -0800,
 Paul Hoffman <paul.hoffman@vpnc.org> wrote 
 a message of 16 lines which said:

> And squatters should expect that the name that they are using might
> eventually be legitimately assigned later, possibly to someone whose
> intentions are quite different from the squatters.

Come on, that's completely unrealistic. Can you imagine ICANN
delegating .local to any one, after it has been used massively by
Apple Bonjour, even before RFC 6761 sanctioned it? Can you imagine
ICANN delegating .onion to someone, giving the number of collisions it
would generate? ICANN did many stupid things but this one seems very
unlikely.

> The purpose of RFC 6761 is not to say "if you start squatting on a
> TLD, you will be able to later get it reserved".

But it is exactly what happened with the first actual use of RFC 6761,
.local.



From bortzmeyer@nic.fr  Mon Jan  6 00:47:44 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC4D1AE015 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 00:47:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVxBWqkjLpYO for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 00:47:43 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 70AFF1AE001 for <dnsop@ietf.org>; Mon,  6 Jan 2014 00:47:43 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id E2ABF2803C2; Mon,  6 Jan 2014 09:47:34 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id DDF342802FF; Mon,  6 Jan 2014 09:47:34 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id D2D874C0053; Mon,  6 Jan 2014 09:47:04 +0100 (CET)
Date: Mon, 6 Jan 2014 09:47:04 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Message-ID: <20140106084704.GC27479@nic.fr>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140102221823.GF8050@mx1.yitter.info>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 08:47:44 -0000

On Thu, Jan 02, 2014 at 05:18:24PM -0500,
 Andrew Sullivan <ajs@anvilwalrusden.com> wrote 
 a message of 16 lines which said:

> On Thu, Jan 02, 2014 at 10:30:04PM +0100, Christian Grothoff wrote:
> > Didn't Apple squat on ".local" and get it reserved using RFC 6761? 
> 
> Not exactly, no.

Yes, Apple did so. Exactly.


From bortzmeyer@nic.fr  Mon Jan  6 00:53:15 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0C91AE001 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 00:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uhMbbDkho4Kb for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 00:53:13 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6141ADEB7 for <dnsop@ietf.org>; Mon,  6 Jan 2014 00:53:13 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 1307E2803DD; Mon,  6 Jan 2014 09:53:05 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 0C4B42803C3; Mon,  6 Jan 2014 09:53:05 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 09A654C007C; Mon,  6 Jan 2014 09:52:35 +0100 (CET)
Date: Mon, 6 Jan 2014 09:52:35 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Joe Abley <jabley@hopcount.ca>
Message-ID: <20140106085234.GA29707@nic.fr>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <67A7E258-BE45-4A7E-8D00-D3FEB31762C1@hopcount.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <67A7E258-BE45-4A7E-8D00-D3FEB31762C1@hopcount.ca>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Christian Grothoff <christian@grothoff.org>, IETF DNSOP WG <dnsop@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>, hellekin@gnu.org, wachs@net.in.tum.de, jacob@appelbaum.net
Subject: Re: [DNSOP] More complete review of draft-grothoff-iesg-special-use-p2p-names-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 08:53:15 -0000

On Tue, Dec 31, 2013 at 05:41:13PM -0500,
 Joe Abley <jabley@hopcount.ca> wrote 
 a message of 106 lines which said:

> The key question for me is, why do any of these uses necessarily
> require reservation of a TLD label, or something that looks like
> one?

"require" is a strong word. But there are many reasons why a TLD is
better:

* shortness and memorability, that you already mentioned in your message

* dependency. For systems that are intented to allow independance from
organisations like the US governement, using a domain name which is
under a TLD controlled by the US rules may be a problem. Let's assume
Tor people are ready to switch from .onion to .onion.eff.org. For
normal Tor requests (which stay outside of the DNS protocol), it is
not a problem. Now, for leaked requests, something that will certainly
happen, .onion.eff.org depends on two more actors, besides the root,
and that may be seen as contradictory with the political goal of Tor
services.

> (a) instruct all the resolver operators in the world to maintain configuration that special-cases a growing list of DNS names. or
> 
> (b) chose your naming scheme (again, think ONION.EFF.ORG) such that the NXDOMAINs, negative caching, sinkholing, whatever can be controlled by someone who cares about Tor (the EFF.ORG administrator) without requiring any special handling elsewhere.
> 
> Option (b) is much more friendly to the Internet.

But the ship already sailed: RFC 6761 choosed a)

From paul@nohats.ca  Mon Jan  6 07:01:21 2014
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B625D1AE019 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 07:01:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGMKyEDe6R9I for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 07:01:20 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id F2E341ADE8B for <dnsop@ietf.org>; Mon,  6 Jan 2014 07:01:16 -0800 (PST)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 4300480055; Mon,  6 Jan 2014 10:01:06 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1389020466; bh=2ptrUoGgaG5UoEyJz4T0U3F8sQMOfgbvYub4qm4GZuM=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=rRfE+lNfmjOtofdntp1GgGXGnJqixxyZz/9CeRRb/IKtmSEKvoviMwWch9HREXnoc PZIvOiQ7ZgaElI5i4osy1cMcsrgVpNbhMD60DeurDJSMP6HNjpmMFj46ecwn1GM6dq 0lo80YwU7ow5OSHi6yhHHfEQeFjkOdNBzmd++Sz0=
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 2F7A280048; Mon,  6 Jan 2014 10:01:06 -0500 (EST)
Date: Mon, 6 Jan 2014 10:01:06 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
In-Reply-To: <20140106084626.GB27479@nic.fr>
Message-ID: <alpine.LFD.2.10.1401061000250.18543@bofh.nohats.ca>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <20140106084626.GB27479@nic.fr>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 15:01:21 -0000

On Mon, 6 Jan 2014, Stephane Bortzmeyer wrote:

> Come on, that's completely unrealistic. Can you imagine ICANN
> delegating .local to any one, after it has been used massively by
> Apple Bonjour, even before RFC 6761 sanctioned it? Can you imagine
> ICANN delegating .onion to someone, giving the number of collisions it
> would generate? ICANN did many stupid things but this one seems very
> unlikely.

I'll believe this when .mail won't get delegated......

Paul

From ajs@anvilwalrusden.com  Mon Jan  6 07:43:30 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5635F1AE048 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 07:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSXjEnfsW2vK for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 07:43:29 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 50D721AE041 for <dnsop@ietf.org>; Mon,  6 Jan 2014 07:43:29 -0800 (PST)
Received: from mx1.yitter.info (nat-02-mht.dyndns.com [216.146.45.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 443458A031 for <dnsop@ietf.org>; Mon,  6 Jan 2014 15:43:20 +0000 (UTC)
Date: Mon, 6 Jan 2014 10:43:15 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140106154315.GD10080@mx1.yitter.info>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <20140106083932.GA27479@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140106083932.GA27479@nic.fr>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] More complete review of draft-grothoff-iesg-special-use-p2p-names-01
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 15:43:30 -0000

On Mon, Jan 06, 2014 at 09:39:32AM +0100, Stephane Bortzmeyer wrote:
> reasonable (it would be better to have "stable" references) but it is
> a "nice to have", it is not mandatory in IETF processes here (RFC
> 6761, section 4 does not require it

I think I disagree.  6761 section 4 says 

   If it is determined that special handling of a name is required in
   order to implement some desired new functionality,

We need some way to make that determination, or else there's no reason
to allocate the labels.  In order to make such a determination, we'd
need either a stable reference or else details in the draft that wants
to allocate the new label.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From paul.hoffman@vpnc.org  Mon Jan  6 07:47:19 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3451AE048 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 07:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66EDasqEJ0EO for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 07:47:18 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3CF1AE036 for <dnsop@ietf.org>; Mon,  6 Jan 2014 07:47:18 -0800 (PST)
Received: from [10.20.30.90] (50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s06FRCln083184 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Jan 2014 08:27:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140106084626.GB27479@nic.fr>
Date: Mon, 6 Jan 2014 07:47:07 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F965982C-BBEA-408E-B103-6085754F231F@vpnc.org>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <20140106084626.GB27479@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>, Christian Grothoff <grothoff@in.tum.de>
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 15:47:19 -0000

On Jan 6, 2014, at 12:46 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:

> On Thu, Jan 02, 2014 at 12:00:14PM -0800,
> Paul Hoffman <paul.hoffman@vpnc.org> wrote=20
> a message of 16 lines which said:
>=20
>> And squatters should expect that the name that they are using might
>> eventually be legitimately assigned later, possibly to someone whose
>> intentions are quite different from the squatters.
>=20
> Come on, that's completely unrealistic. Can you imagine ICANN
> delegating .local to any one, after it has been used massively by
> Apple Bonjour, even before RFC 6761 sanctioned it?

No, because of the significant technical discussion of .local that =
happened in the IETF for many years before the new gTLD round. =
However...

> Can you imagine
> ICANN delegating .onion to someone, giving the number of collisions it
> would generate?

Yes, definitely. ICANN acknowledges that many of the new TLDs that are =
being added right now have collisions.

> ICANN did many stupid things but this one seems very
> unlikely.

We disagree (about the latter part).

>> The purpose of RFC 6761 is not to say "if you start squatting on a
>> TLD, you will be able to later get it reserved".
>=20
> But it is exactly what happened with the first actual use of RFC 6761,
> .local.

If you think that a name that was squatted, extremely widely deployed, =
and heavily discussed in the IETF is equivalent to a name that was =
squatted, barely deployed, and not even specified in an RFC, that's =
fine. Others might disagree for somewhat obvious reasons.

--Paul Hoffman=

From ajs@anvilwalrusden.com  Mon Jan  6 07:49:10 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE9A1AE04E for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 07:49:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CqyO_0O1bUfL for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 07:49:10 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E28EC1AE047 for <dnsop@ietf.org>; Mon,  6 Jan 2014 07:49:09 -0800 (PST)
Received: from mx1.yitter.info (nat-02-mht.dyndns.com [216.146.45.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 6AB928A031 for <dnsop@ietf.org>; Mon,  6 Jan 2014 15:49:01 +0000 (UTC)
Date: Mon, 6 Jan 2014 10:49:00 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140106154859.GE10080@mx1.yitter.info>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info> <20140106084704.GC27479@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140106084704.GC27479@nic.fr>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 15:49:11 -0000

On Mon, Jan 06, 2014 at 09:47:04AM +0100, Stephane Bortzmeyer wrote:
> 
> Yes, Apple did so. Exactly.

It may be true that RFC 6761 was in effect created in order to
regularlize the .local use, but my claim is that the .local use was
more akin to the current issues with .corp and .home than like these
cases, where penetration is quite a bit smaller.  (I realise that
.onion is important to Tor, but I am sceptical that Tor has the
Internet penetration that Bonjour did long before 6761 was published.
Certainly Namecoin use is insignificant compared to what Bonjour was.)

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From bortzmeyer@nic.fr  Mon Jan  6 08:09:53 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2F81AE053 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 08:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dUjCoNxlgmEv for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 08:09:51 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6D31AE055 for <dnsop@ietf.org>; Mon,  6 Jan 2014 08:09:51 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 0D96E2802C6; Mon,  6 Jan 2014 17:09:42 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 08BE9280291; Mon,  6 Jan 2014 17:09:42 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id 06FE7B38038; Mon,  6 Jan 2014 17:09:12 +0100 (CET)
Date: Mon, 6 Jan 2014 17:09:12 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Message-ID: <20140106160911.GA9632@nic.fr>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info> <20140106084704.GC27479@nic.fr> <20140106154859.GE10080@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140106154859.GE10080@mx1.yitter.info>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 16:09:53 -0000

On Mon, Jan 06, 2014 at 10:49:00AM -0500,
 Andrew Sullivan <ajs@anvilwalrusden.com> wrote 
 a message of 21 lines which said:

> (I realise that .onion is important to Tor, but I am sceptical that
> Tor has the Internet penetration that Bonjour did long before 6761
> was published.

Based on a completely unscientific guess, I don't think so. You've
never done shopping on Silk Road? :-)

But I disagree with the method of adding requirments which were not in
RFC 6761 (which does not talk about the size of the installed base).


From paul.hoffman@vpnc.org  Mon Jan  6 08:53:10 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48A951AE0F6 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 08:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7CVhaIcCuB7a for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 08:53:09 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7AF111AE0F1 for <dnsop@ietf.org>; Mon,  6 Jan 2014 08:53:09 -0800 (PST)
Received: from [10.20.30.90] (50-1-51-230.dsl.dynamic.fusionbroadband.com [50.1.51.230]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s06GX447085667 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Jan 2014 09:33:05 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-51-230.dsl.dynamic.fusionbroadband.com [50.1.51.230] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140106160911.GA9632@nic.fr>
Date: Mon, 6 Jan 2014 08:53:00 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <402563DA-872E-437D-B561-13E0742A24D9@vpnc.org>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info> <20140106084704.GC27479@nic.fr> <20140106154859.GE10080@mx1.yitter.info> <20140106160911.GA9632@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 16:53:10 -0000

On Jan 6, 2014, at 8:09 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:

> But I disagree with the method of adding requirments which were not in
> RFC 6761 (which does not talk about the size of the installed base).

It sounds like you're saying that if I create a protocol that is =
supposed to be only run on LANs that uses a TLD such as .stephane, I =
should be able to get an RFC 6761 allocation, regardless of how little =
it is deployed. If so, I disagree strongly. If not (and I hope not), =
*you* need to talk about size of the installed base.

--Paul Hoffman=

From Ted.Lemon@nominum.com  Mon Jan  6 10:48:18 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BEAA1AE17E for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 10:48:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ry-TGjSiTZaD for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 10:48:17 -0800 (PST)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 142A11AE15B for <dnsop@ietf.org>; Mon,  6 Jan 2014 10:48:17 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUsr6aK7QbmfpcQq/I792DqaCc9EKv7+l@postini.com; Mon, 06 Jan 2014 10:48:09 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 886A91B82E8 for <dnsop@ietf.org>; Mon,  6 Jan 2014 10:48:08 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6651619005C; Mon,  6 Jan 2014 10:48:08 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 6 Jan 2014 10:48:08 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140106154859.GE10080@mx1.yitter.info>
Date: Mon, 6 Jan 2014 13:48:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <DBE20231-BE59-41F4-B690-A74BC407BBC6@nominum.com>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info> <20140106084704.GC27479@nic.fr> <20140106154859.GE10080@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 18:48:18 -0000

On Jan 6, 2014, at 10:49 AM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
> I realise that
> .onion is important to Tor, but I am sceptical that Tor has the
> Internet penetration that Bonjour did long before 6761 was published.

It seems to me that TOR is a pretty vital application, even if it's not =
as popular as .local (which, let's be honest, is almost never seen, much =
less typed, by an end user).   I am deeply skeptical of the idea that =
the only relevant factor here is how widespread the squatting is on a =
particular top-level special-use domain.


From ajs@anvilwalrusden.com  Mon Jan  6 12:54:29 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 644A41AE120 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 12:54:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CBzLd5j9oagC for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 12:54:27 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id B65BB1AE14D for <dnsop@ietf.org>; Mon,  6 Jan 2014 12:54:27 -0800 (PST)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 19A088A031 for <dnsop@ietf.org>; Mon,  6 Jan 2014 20:54:19 +0000 (UTC)
Date: Mon, 6 Jan 2014 15:54:17 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140106205417.GC10517@mx1.yitter.info>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info> <20140106084704.GC27479@nic.fr> <20140106154859.GE10080@mx1.yitter.info> <DBE20231-BE59-41F4-B690-A74BC407BBC6@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DBE20231-BE59-41F4-B690-A74BC407BBC6@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 20:54:29 -0000

On Mon, Jan 06, 2014 at 01:48:04PM -0500, Ted Lemon wrote:
> It seems to me that TOR is a pretty vital application, even if it's
> not as popular as .local (which, let's be honest, is almost never
> seen, much less typed, by an end user). 

   Addresses in ".onion" are opaque, non-mnemonic, alpha-semi-numeric
   hashes corresponding to an 80-bit truncated SHA1 hash over a given
   Tor hidden service's public key. 

I'm pretty sure things in .onion are never supposed to be seen, much
less typed, by an end user too.

> I am deeply skeptical of
> the idea that the only relevant factor here is how widespread the
> squatting is on a particular top-level special-use domain.

I have never suggested that's the only relevant factor.  But I have
suggested that the argument, "This needs to be a TLD that steps on the
standard ICANN allocation mecahnism because it's already widely
deployed," needs some evidence of that wide deployment.  In the case
of .onion, for instance, it is very far from obvious to me that the
name needed to have been allocated directly beneath the root (as
opposed to, say, inside .arpa); but if Tor is already widely deployed,
the argument in favour of allocating that string in the root due to
practical side effects is made stronger.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From nweaver@icsi.berkeley.edu  Mon Jan  6 12:57:07 2014
Return-Path: <nweaver@icsi.berkeley.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0214B1AE223 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 12:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4q_gvEY8YXbX for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 12:57:05 -0800 (PST)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) by ietfa.amsl.com (Postfix) with ESMTP id 94FD51AE14D for <dnsop@ietf.org>; Mon,  6 Jan 2014 12:57:05 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 698982C402F; Mon,  6 Jan 2014 12:56:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at ICSI.Berkeley.EDU
Received: from rock.ICSI.Berkeley.EDU ([127.0.0.1]) by localhost (maihub.ICSI.Berkeley.EDU [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1riebVrPMC2N; Mon,  6 Jan 2014 12:56:57 -0800 (PST)
Received: from wifi183.sys.icsi.berkeley.edu (wifi183.sys.ICSI.Berkeley.EDU [192.168.6.183]) (Authenticated sender: nweaver) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id D6C5C2C4002; Mon,  6 Jan 2014 12:56:56 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_5B7672BA-0CA9-41D9-A599-AB9F7D7FF94E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Nicholas Weaver <nweaver@icsi.berkeley.edu>
In-Reply-To: <20140106205417.GC10517@mx1.yitter.info>
Date: Mon, 6 Jan 2014 12:56:53 -0800
Message-Id: <011B3D37-DA87-4055-9755-8519B7014F12@icsi.berkeley.edu>
References: <20131231000412.GV4291@mx1.yitter.info> <52C323CE.3090909@grothoff.org> <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info> <20140106084704.GC27479@nic.fr> <20140106154859.GE10080@mx1.yitter.info> <DBE20231-BE59-41F4-B690-A74BC407BBC6@nominum.com> <20140106205417.GC10517@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop WG <dnsop@ietf.org>, Nicholas Weaver <nweaver@icsi.berkeley.edu>
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 20:57:07 -0000

--Apple-Mail=_5B7672BA-0CA9-41D9-A599-AB9F7D7FF94E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jan 6, 2014, at 12:54 PM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:

> On Mon, Jan 06, 2014 at 01:48:04PM -0500, Ted Lemon wrote:
>> It seems to me that TOR is a pretty vital application, even if it's
>> not as popular as .local (which, let's be honest, is almost never
>> seen, much less typed, by an end user).=20
>=20
>   Addresses in ".onion" are opaque, non-mnemonic, alpha-semi-numeric
>   hashes corresponding to an 80-bit truncated SHA1 hash over a given
>   Tor hidden service's public key.=20
>=20
> I'm pretty sure things in .onion are never supposed to be seen, much
> less typed, by an end user too.

You'd like to think that, but sorry no.  They are seen all the time:

If you don't already have it bookmarked, you are going to have to type =
in or cut and paste or the like http://silkroad6ownowfk.onion if you =
want to visit the current incarnation of the Silk Road in order to =
invest in your future prosecution...


--Apple-Mail=_5B7672BA-0CA9-41D9-A599-AB9F7D7FF94E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIbBAEBCgAGBQJSyxiVAAoJEG2B1w+SDi/uUhcP92mMEvHeGDG9K1OXpCKGdB0e
+ZEgC4NZOhaDgb9iOMphxv/U2xybMLx93N1lsRHAsfmWg6ynGDZAI+7nAt6YIP4c
K0cyjnXSVNGZA6jx3wE9NGOYTr4y3B1jRoNTG2xJY+ZFWEFi0rUH7licvM8avdDT
9G9EYY16v2xRDO9qRNDzldaAE4e0nQ9fos4BPmCetSXbuJYja1/HQiB+HAmVIF9w
XzfTHbMVZIM9jlCcxH7psJWeLZZqpo81pQIUp2EPYDhdgnO4wiPPpJHN7fyH8UyD
Sp9CwIPZ51SC8X8J7snPpCJAl47Nm95g5XqeuKbd4ZYPajdjI1RFC83893kWDmox
ozkO3VBWSSWdqKT9xRN+HtFyRcs540cDhcjl2sOopG982KvCcDP9Y68i1UBJXZoZ
Wrbiu8Odq8xshJo84T3TWc9c0q3+XVaqob+fJLN/jUQgrZ2JBH5w4T/YACEy36B/
7ngUQ6Vr1Y9J9MnM6Gwgc6+s/XcjjxVTVabOFn6nvF05EjTRunjYiWE9KHbaADYo
MEISRHTZAbLaR/QG3f8rg84QmLvQoVXelqNAkGH8VrY+eAK2aIxJr5dBUuaQEHK2
kfufE17RF0BHS0BbMX2/hKJIdtXjAmR0+R0NJoz4UGxUzMtc2xGDdauDfVUNvwgk
5hNwDtJ+ZqtOc1cVXl4=
=Jr+j
-----END PGP SIGNATURE-----

--Apple-Mail=_5B7672BA-0CA9-41D9-A599-AB9F7D7FF94E--

From ajs@anvilwalrusden.com  Mon Jan  6 13:32:12 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E9FF1AE256 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 13:32:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HubzuX5qWhUh for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 13:32:11 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 39F941AE251 for <dnsop@ietf.org>; Mon,  6 Jan 2014 13:32:11 -0800 (PST)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 8C3228A031 for <dnsop@ietf.org>; Mon,  6 Jan 2014 21:32:02 +0000 (UTC)
Date: Mon, 6 Jan 2014 16:32:01 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140106213201.GJ10517@mx1.yitter.info>
References: <20131231234421.GA5732@mx1.yitter.info> <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info> <20140106084704.GC27479@nic.fr> <20140106154859.GE10080@mx1.yitter.info> <DBE20231-BE59-41F4-B690-A74BC407BBC6@nominum.com> <20140106205417.GC10517@mx1.yitter.info> <011B3D37-DA87-4055-9755-8519B7014F12@icsi.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <011B3D37-DA87-4055-9755-8519B7014F12@icsi.berkeley.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 21:32:12 -0000

On Mon, Jan 06, 2014 at 12:56:53PM -0800, Nicholas Weaver wrote:
> 
> You'd like to think that, but sorry no.  They are seen all the time:

No, that's different.  Now you're saying that sometimes people use
these for purposes other than what's documented, so they hand them
around.  If _that's_ the case, then on top of everything else the
documentation in this case is wrong, and therefore the argument for
the allocation is bad.

Look, I'm not opposed to these allocations in principle, but if we're
going to have two completely different ways of registering top level
domains and they're going to be responsible to two completely
different allocation bodies until the actual moment of registration
with IANA, then we are going to have to be _extremely careful_ with
how we do this.  It's true that .local was sort of a prior example,
but as Paul already pointed out there are quite significant
differences in the way that emerged.  Not the least of the differences
is that .local got going in an environment in which most of us were in
a position to assume the root zone was fairly small and fairly stable.
Those assumptions are now violated, and the plans for that violation
were announced a few years ago.  Conditions are different, and I think
it appropriate therefore to respond differently.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From matthijs@nlnetlabs.nl  Mon Jan  6 23:43:15 2014
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF221AE4A6 for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 23:43:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.444
X-Spam-Level: 
X-Spam-Status: No, score=-100.444 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XMqwY18yeLHJ for <dnsop@ietfa.amsl.com>; Mon,  6 Jan 2014 23:43:13 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B7B1AE496 for <dnsop@ietf.org>; Mon,  6 Jan 2014 23:43:12 -0800 (PST)
Received: from [IPv6:2001:981:19be:1:6ca6:5301:c9ef:7ad] ([IPv6:2001:981:19be:1:6ca6:5301:c9ef:7ad]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id s077gxrG079949 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <dnsop@ietf.org>; Tue, 7 Jan 2014 08:43:01 +0100 (CET) (envelope-from matthijs@nlnetlabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl s077gxrG079949
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1389080583; bh=eF2VQGeCseVTt31FUYtHeLVyf96BVZlR5AM+hBDh5E0=; h=Date:From:To:Subject:References:In-Reply-To; b=oMVoTQSjSlwdYWrYaurZS6i2HhKVvv46itxpCXGK1A9TvVCVYaar06iLdKlOtdoNB b6P0MiKhPo1awSK6Xl6xDeW59ZxbfufC8JpD/IwDkCzlsrp8n8cLl8Xs1xDfc9sNKi 8f39VqKSPYy4LeaFMWNREnU1GpCMyYMWi6HrJId8=
Message-ID: <52CBB003.2060905@nlnetlabs.nl>
Date: Tue, 07 Jan 2014 08:42:59 +0100
From: Matthijs Mekking <matthijs@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com> <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com>
In-Reply-To: <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Tue, 07 Jan 2014 08:43:01 +0100 (CET)
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 07:43:15 -0000

Hi,

About Child's CDS / CDNSKEY publication, I still think that it is too
strong that the Child DNS Operator SHOULD/MUST delete the CDS RRset when
the Parent DS is "in-sync". This should be a MAY.

As Joe Abley pointed out, keeping the CDS/CDNSKEY published is a nice
addition for debugging/monitoring purposes.

When the Parent sees that the CDS/ CDNSKEY RRset is empty, no action
should be taken. When the Parent sees that the CDS / CDNSKEY RRset is
already "in-sync", no action should be taken.

Best regards,
  Matthijs


On 01/04/2014 10:21 PM, Warren Kumari wrote:
> We think that this resolves the open comments and is ready for WGLC.
> 
> 
> 
> On Sat, Jan 4, 2014 at 3:40 PM, <internet-drafts@ietf.org
> <mailto:internet-drafts@ietf.org>> wrote:
> 
> 
>     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
>     Working Group of the IETF.
> 
>             Title           : Automating DNSSEC delegation trust maintenance
>             Authors         : Warren Kumari
>                               Olafur Gudmundsson
>                               George Barwood
>             Filename        :
>     draft-ietf-dnsop-delegation-trust-maintainance-01.txt
>             Pages           : 17
>             Date            : 2014-01-04
> 
>     Abstract:
>        This document describes a method to allow DNS operators to more
>        easily update DNSSEC Key Signing Keys using DNS as communication
>        channel.  This document does not address the initial configuration of
>        trust anchors for a domain.  The technique described is aimed at
>        delegations in which it is currently hard to move information from
>        the child to parent.
> 
> 
>     The IETF datatracker status page for this draft is:
>     https://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-trust-maintainance/
> 
>     There's also a htmlized version available at:
>     http://tools.ietf.org/html/draft-ietf-dnsop-delegation-trust-maintainance-01
> 
>     A diff from the previous version is available at:
>     http://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-delegation-trust-maintainance-01
> 
> 
>     Please note that it may take a couple of minutes from the time of
>     submission
>     until the htmlized version and diff are available at tools.ietf.org
>     <http://tools.ietf.org>.
> 
>     Internet-Drafts are also available by anonymous FTP at:
>     ftp://ftp.ietf.org/internet-drafts/
> 
>     _______________________________________________
>     DNSOP mailing list
>     DNSOP@ietf.org <mailto:DNSOP@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dnsop
> 
> 
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
> 


From ogud@ogud.com  Tue Jan  7 20:53:55 2014
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E56E81AE2D1 for <dnsop@ietfa.amsl.com>; Tue,  7 Jan 2014 20:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0hy7OvLtrbG1 for <dnsop@ietfa.amsl.com>; Tue,  7 Jan 2014 20:53:48 -0800 (PST)
Received: from smtp69.ord1c.emailsrvr.com (smtp69.ord1c.emailsrvr.com [108.166.43.69]) by ietfa.amsl.com (Postfix) with ESMTP id 982211AE2CF for <dnsop@ietf.org>; Tue,  7 Jan 2014 20:53:46 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 7B3351480D8; Tue,  7 Jan 2014 23:53:37 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp1.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 302921480D4;  Tue,  7 Jan 2014 23:53:37 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <20140104235045.GA24696@totoro.home.mukund.org>
Date: Tue, 7 Jan 2014 23:53:36 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <28570EA3-CF74-4FD2-95CD-D8672E64C199@ogud.com>
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com> <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com> <20140104235045.GA24696@totoro.home.mukund.org>
To: Mukund Sivaraman <muks@isc.org>
X-Mailer: Apple Mail (2.1510)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 04:53:56 -0000

Mukund,=20

thanks for your review I will respond to the points that Warren did not=20=

address in his reply.=20

On Jan 4, 2014, at 6:50 PM, Mukund Sivaraman <muks@isc.org> wrote:

> Hi Warren
>=20
> On Sat, Jan 04, 2014 at 04:21:03PM -0500, Warren Kumari wrote:
>> We think that this resolves the open comments and is ready for WGLC.
>=20
> Here are some comments:
>=20
>=20
>> As the DS record can only be present at the parent RFC4034 [RFC4034],
>> some other record/method is needed to automate the expression of what
>> the parental zone DS records contents ought to be.  One possibility
>> is to use flags in the DNSKEY record.  If the SEP bit is set, this
>=20
> I suggest rewriting this sentence:
>=20
> "As the DS record can only be present at the parent RFC4034 [RFC4034],
> some method is needed to automate which DNSKEYs are picked to be
> represented in the parent zone's DS records."
>=20
> A sentence explaining why a method is needed to automate locating =
entry
> point keys would be good to have here.

Hum Hum, the introduction and Background sections are supposed to do =
provide the=20
background, did we fail in conveying that message ?=20


>=20
>> indicates that the DNSKEY is intended for use as a secure entry
>> point.  This DNSKEY signs the DNSKEY RRset, and the Parental Agent
>> can calculate DS records based on that.  But this fails to meet some
>> operating needs, including the child having no influence what DS
>=20
> Does this mean that the Parental Agent automatically picks up DNSKEY =
RRs
> with SEP=3D1 from the child zone? (How are these DNSKEYs validated?) =
This
> should be explained.

This is background not protocol at this point, so I do not want to get =
into=20
validation at this point.=20

>=20
>> digest algorithms are used and DS records can only be published for
>> keys that are in the DNSKEY RRset.
>=20
> Does this imply use of additionally configured trust anchors when such
> keys are not in the DNSKEY RRset? Such minor clues are useful when
> reading.
>=20

The point is Child may want DS records referring to future/past/backup =
DNSKEY records=20
but does not want to include them in the DNSKEY RRset for some reason =
including size.=20



> I was not able to follow this paragraph (though I follow what is
> intended to be described).
>=20
> Section 2.2.1
> -------------
>=20
>> A further complication is when the Child DNS Operation is not the
>> Child.  There are two common cases of this,
>=20
> "Child DNS Operation" =3D> "Child DNS operator"
>=20
>>  If the Parental Agent is the DNS operator, life is much easier, as
>>  the Parental Agent can inject any delegation changes directly into
>>  the Parents Provisioning system.  The techniques described below are
>>  not needed in the case when Parental Agent is the DNS operator.
>=20
> "Parents Provisioning system" =3D> "Parent's Provisioning system"
>=20
>>  Some parents want the child to express the changes in trust anchors
>>  via DS records, while others want to receive DNSKEY records and
>=20
> Is "trust anchor" used according to its definition here? Specifically =
it
> pertains to a resolver's configuration. There is a similar use of =
"trust
> anchor" in the abstract too.
>=20
>> interface, to "upload / paste-in the zone's DS information".  The
>> action of logging in through the delegation account user interface
>> authenticates that the user is authorized to change delegation
>> information published in the parent zone.  In the case where the
>=20
> "... change delegation information *for the child* published in the
> parent zone." (i.e., not all delegation information in the parent =
zone.)
>=20
>> Furthermore when this is a manual process with cut and paste;
>> operational mistakes will happen. Or worse the update action in not
>> performed at all.
>=20
> Please replace the above with the following (punctuation and typo
> changes):
>=20
> "Furthermore when this is a manual process with cut and paste,
> operational mistakes will happen, or worse, the update action is not
> performed at all."
>=20
> Section 3
> ---------
>=20
>> This document specifies two new DNS RRtypes (CDS and CDNSKEY) that
>> indicates what the Child wants to be in the parents DS RRset.  It
>=20
> Instead of "to be in the", I suggest something like:
>=20
> "... what the Child wants to be included in the parent's DS RRset."
>=20
> "... what the Child wants the parent's DS RRset to contain."
>=20
> (also note the apostrophe in "parent's").
>=20
>> allows the Child to present DS records and / or DNSKEY records (for
>> those parents who would rather generate the DS records for their
>> children).
>=20
>> [RFC Editor: Please remove this paragraph before publication] Version
>> -04 of this document defined a new record (CTA) that could hold
>> either a DS or a DNSKEY record (with a selector to differentiate
>> between them). ]
>=20
> Where is version -04 of this document? What is this CTA record it is
> referring to?
>=20
> Section 5
> ---------
>=20
> It is important to add a note here that the Child DNS Operator (or =
some
> software) must delete old DNSKEYs only after verifying that the parent
> zone has updated its DS records to match the new ones.
>=20
> It is also important for the Child to not directly switch CDS / =
CDNSKEY
> RRs (once published):
>=20
> * before sending them through DNSKEY RRs first, and
>=20
> * before verifying that the parent has updated to the new CDS / =
CDNSKEY
>  data
>=20
> as the parent may be in the process of updating to the new DS records
> when such a change happens, breaking the chain.
>=20

There is no harm if the Child at time T publishes CDNSKEY and at time =
T+1 day publishes corresponding CDS=20
as long as they are the same.
 If child discovers after publishing CDS that that parent wants CDNSKEY =
it is harmless to
switch the out CDS for CDNSKEY=20

Your point that the child should not break the delegation by removing an =
"active" DNSKEy is a good
one and was too obvious to me, will add text to that effect.=20

> Section 6.2
> -----------
>=20
> If every nameserver is to be checked for the CDS / CDNSKEY RRs, what =
is
> the action to be taken when there is a mismatch? Which CDS is used?

>=20

Strictly speaking this is "local policy" for the parental agent.=20
But, assuming all the CDS/CDNSKEY records pass DNSSEC validation.=20

--> In this case the parental agent should ignore the records
and hope the situation is sorted out next time it checks.=20

If only some of the CDS/CDNSKEY validate then those that validate should =
be identical before triggering update to parent DNS.=20

It is quite possible that things are out of sync due to the =
loose-consistency of DNS and delays in getting new versions of zones to
all secondaries.=20
Not matching includes that some name servers have CDS/CDNSKEY records =
and some do not.=20

Thinking about adding this text:=20
Parental Agent is free to poll as many name servers for the child as it =
wants to check if they agree on the contents of the
CDS/CDNSKEY records, only if all the checked servers have identical =
records should the records be accepted.=20

Note;=20
This case is one of the reasons I want children to remove the C* records =
after parent performs the update,=20
then there is no chance of JoJo updates by parent depending on which =
Nameserver is polled.=20

>=20
>> While it may be tempting, this SHOULD NOT be used for initial
>> enrollment of keys since there is no way to ensure that the initial
>> key is the correct one.  If is used, strict rules for inclusion of
>=20
> Perhaps "authentic" or "valid" are better words than "correct" in this
> context.
>=20

"Correct" is the appropriate word here, as it refers to a key(s) that =
have been presented
via some authenticated out-of-band method.=20


> Some overall notes
> ------------------
>=20
> "Child operator" and "Child DNS operator" are both used. Please update
> the document to use the one defined in the "Terminology" section.
>=20
> Can't the equivalent of CDS / CDNSKEY be achieved by introducing
> additional DNSKEY RRs (with SEP=3D1) in the child zone that are polled =
by
> the Parent DNS operator? Is it really so important that the child must
> have control (overriding the parent's choice) over the value of fields
> used in the DS record? For example, the parent operator can use the =
same
> algorithm, etc. as in the initially configured DS record.
>=20
> 		Mukund
Thanks for great helpful review,=20

	Olafur



From bortzmeyer@nic.fr  Wed Jan  8 00:28:20 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 139DC1AE32D for <dnsop@ietfa.amsl.com>; Wed,  8 Jan 2014 00:28:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WtuLPfo500NU for <dnsop@ietfa.amsl.com>; Wed,  8 Jan 2014 00:28:18 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by ietfa.amsl.com (Postfix) with ESMTP id 099771ADEB4 for <dnsop@ietf.org>; Wed,  8 Jan 2014 00:28:17 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 80DEA3AC42; Wed,  8 Jan 2014 08:28:07 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 52E6B190C39; Wed,  8 Jan 2014 09:26:25 +0100 (CET)
Date: Wed, 8 Jan 2014 09:26:25 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Message-ID: <20140108082625.GA14486@sources.org>
References: <52C48A4A.6090303@in.tum.de> <4C051985-6E70-463A-9672-02657842754D@vpnc.org> <52C5DA5C.1090605@grothoff.org> <20140102221823.GF8050@mx1.yitter.info> <20140106084704.GC27479@nic.fr> <20140106154859.GE10080@mx1.yitter.info> <DBE20231-BE59-41F4-B690-A74BC407BBC6@nominum.com> <20140106205417.GC10517@mx1.yitter.info> <011B3D37-DA87-4055-9755-8519B7014F12@icsi.berkeley.edu> <20140106213201.GJ10517@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140106213201.GJ10517@mx1.yitter.info>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 7.2
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] On squatting and draft-grothoff-iesg-special-use-p2p-names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 08:28:20 -0000

On Mon, Jan 06, 2014 at 04:32:01PM -0500,
 Andrew Sullivan <ajs@anvilwalrusden.com> wrote 
 a message of 35 lines which said:

> Now you're saying that sometimes people use these for purposes other
> than what's documented,

I don't understand. Handing around .onion URLs is done all the time
and it's the normal use (specially important since you cannot use
Google on Tor hidden services). What is "not documented" here? 


From suzworldwide@gmail.com  Wed Jan  8 10:18:24 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE2A41ADBD7 for <dnsop@ietfa.amsl.com>; Wed,  8 Jan 2014 10:18:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ehnUc5VqV-z for <dnsop@ietfa.amsl.com>; Wed,  8 Jan 2014 10:18:20 -0800 (PST)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id B14731AE06C for <dnsop@ietf.org>; Wed,  8 Jan 2014 10:18:20 -0800 (PST)
Received: by mail-qc0-f170.google.com with SMTP id e9so1595241qcy.29 for <dnsop@ietf.org>; Wed, 08 Jan 2014 10:18:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version; bh=Y48UtmiiUtgCTh+q2moWEw1Gtf+FMFqLX2xRk4tArMM=; b=wodH0nJ+y5U+ua5xmZP1pKgvJUy8PQM/2uy2woKINr/moDIlY2pyG4ng+DXV2vVAUz XUg9091WQAVq12s//H6jiJy04lIHQNeJM3UlCLwEUZW6a09I964B8N7IwIxyx9MYK3NH TzTKbjr3DKurSMSN/PKFKxueTpE42TfTowQY2cObxDTVRzLrCtx22E63Pri3lrMRnEXW l4vkCQX+Zep5S0a8EMhgyFz3qdUvJY+omxNs/jlyRPJUfPxOs+D+QL7gvE2yyCglVGe9 Y9rw5pilpZN9rZpy6R+zF83gMKXhE6h+j5MLEGfgi/EhQMipd93fObxnYv8srxn0PFIN En2Q==
X-Received: by 10.49.15.202 with SMTP id z10mr213483042qec.46.1389205091306; Wed, 08 Jan 2014 10:18:11 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id ni10sm2418702qeb.23.2014.01.08.10.18.10 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 10:18:10 -0800 (PST)
From: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_370DB74F-A90D-4504-9579-BECE34DF9105"
Date: Wed, 8 Jan 2014 13:18:09 -0500
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Message-Id: <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 18:18:24 -0000

--Apple-Mail=_370DB74F-A90D-4504-9579-BECE34DF9105
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Colleagues,

This new internet-draft is another request for additions to the RFC 6761 =
special names registry, this time motivated by an interest in reserving =
the names most commonly found in recent analysis of TLDs in private name =
spaces. The special names registration would serve to minimize the =
chances of collision between private and public DNS namespaces by =
keeping these names unassigned in the public namespace.

In addition to discussion on the merits of this specific request, I =
would expect the IESG to be interested in any new aspects this request =
brings up to the discussion we were already having on the p2p special =
names draft, and the usability and scalability of the process in RFC =
6761.

thanks,
Suzanne


Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
> Date: January 8, 2014 10:11:28 AM EST
> To: i-d-announce@ietf.org
> Reply-To: internet-drafts@ietf.org
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>=20
>=20
>        Title           : Additional Reserved Top Level Domains
>        Authors         : Lyman Chapin
>                          Mark McFadden
> 	Filename        : draft-chapin-additional-reserved-tlds-00.txt
> 	Pages           : 26
> 	Date            : 2014-01-08
>=20
> Abstract:
>   The Internet Domain Name System (DNS) defines a tree of names
>   starting with root, ".", immediately below which are top level
>   domain (TLD) names such as ".com" and ".us". In June 1999 RFC2606
>   reserved a small number of TLD names for use in documentation
>   examples, private testing, experiments, and other circumstances in
>   which it is desirable to avoid conflict with current or future
>   actual TLD names in the DNS.
>=20
>   There has been significant evolution of Internet engineering and
>   operation practices since RFC2606 was published. In February 2013
>   RFC6761 defined criteria and procedures for reserving a domain name
>   for special use, and established an IANA registry for such names.
>   This document reserves eight domain name labels for special use in
>   accordance with the criteria and procedures of RFC6761: localdomain,
>   domain, lan, home, host, corp, mail, and exchange.
>=20
>   It is important to note that TLD names may be reserved, in other
>   contexts, for policy, political, or other reasons that are distinct
>   from the IETF's concern with Internet engineering and operations.
>   This document reserves TLD names only for operational and
>   engineering reasons.
>=20
>=20
> The IETF datatracker status page for this draft is:
> =
https://datatracker.ietf.org/doc/draft-chapin-additional-reserved-tlds/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-chapin-additional-reserved-tlds-00
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


--Apple-Mail=_370DB74F-A90D-4504-9579-BECE34DF9105
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Colleagues,<div><br></div><div>This new internet-draft is another =
request for additions to the RFC 6761 special names registry, this time =
motivated by an interest in reserving the names most commonly found in =
recent analysis of TLDs in private name spaces. The special names =
registration would serve to minimize the chances of collision between =
private and public DNS namespaces by keeping these names unassigned in =
the public namespace.</div><div><br></div><div>In addition to discussion =
on the merits of this specific request, I would expect the IESG to be =
interested in any new aspects this request brings up to the discussion =
we were already having on the p2p special names draft, and the usability =
and scalability of the process in RFC =
6761.</div><div><br></div><div>thanks,</div><div>Suzanne</div><div><br><di=
v><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br><=
/span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>Subject: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><b>I-D Action: =
draft-chapin-additional-reserved-tlds-00.txt</b><br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">January 8, 2014 =
10:11:28 AM EST<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><a =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br></span>=
</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Reply-To: =
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br><=
/span></div><br><div><br>A New Internet-Draft is available from the =
on-line Internet-Drafts directories.<br><br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Additional =
Reserved Top Level Domains<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Authors =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Lyman Chapin<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;Mark McFadden<br><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Filename =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-chapin-additional-reserved-tlds-00.txt<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
26<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2014-01-08<br><br>Abstract:<br> &nbsp;&nbsp;The Internet Domain Name =
System (DNS) defines a tree of names<br> &nbsp;&nbsp;starting with root, =
".", immediately below which are top level<br> &nbsp;&nbsp;domain (TLD) =
names such as ".com" and ".us". In June 1999 RFC2606<br> =
&nbsp;&nbsp;reserved a small number of TLD names for use in =
documentation<br> &nbsp;&nbsp;examples, private testing, experiments, =
and other circumstances in<br> &nbsp;&nbsp;which it is desirable to =
avoid conflict with current or future<br> &nbsp;&nbsp;actual TLD names =
in the DNS.<br><br> &nbsp;&nbsp;There has been significant evolution of =
Internet engineering and<br> &nbsp;&nbsp;operation practices since =
RFC2606 was published. In February 2013<br> &nbsp;&nbsp;RFC6761 defined =
criteria and procedures for reserving a domain name<br> &nbsp;&nbsp;for =
special use, and established an IANA registry for such names.<br> =
&nbsp;&nbsp;This document reserves eight domain name labels for special =
use in<br> &nbsp;&nbsp;accordance with the criteria and procedures of =
RFC6761: localdomain,<br> &nbsp;&nbsp;domain, lan, home, host, corp, =
mail, and exchange.<br><br> &nbsp;&nbsp;It is important to note that TLD =
names may be reserved, in other<br> &nbsp;&nbsp;contexts, for policy, =
political, or other reasons that are distinct<br> &nbsp;&nbsp;from the =
IETF's concern with Internet engineering and operations.<br> =
&nbsp;&nbsp;This document reserves TLD names only for operational =
and<br> &nbsp;&nbsp;engineering reasons.<br><br><br>The IETF datatracker =
status page for this draft is:<br><a =
href=3D"https://datatracker.ietf.org/doc/draft-chapin-additional-reserved-=
tlds/">https://datatracker.ietf.org/doc/draft-chapin-additional-reserved-t=
lds/</a><br><br>There's also a htmlized version available =
at:<br>http://tools.ietf.org/html/draft-chapin-additional-reserved-tlds-00=
<br><br><br>Please note that it may take a couple of minutes from the =
time of submission<br>until the htmlized version and diff are available =
at tools.ietf.org.<br><br>Internet-Drafts are also available by =
anonymous FTP =
at:<br>ftp://ftp.ietf.org/internet-drafts/<br><br>________________________=
_______________________<br>I-D-Announce mailing =
list<br>I-D-Announce@ietf.org<br>https://www.ietf.org/mailman/listinfo/i-d=
-announce<br>Internet-Draft directories: =
http://www.ietf.org/shadow.html<br>or =
ftp://ftp.ietf.org/ietf/1shadow-sites.txt<br></div></blockquote></div><br>=
</div></body></html>=

--Apple-Mail=_370DB74F-A90D-4504-9579-BECE34DF9105--

From ogud@ogud.com  Wed Jan  8 20:41:02 2014
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 905311ADF9F for <dnsop@ietfa.amsl.com>; Wed,  8 Jan 2014 20:41:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GxrV_3hwTCOl for <dnsop@ietfa.amsl.com>; Wed,  8 Jan 2014 20:41:01 -0800 (PST)
Received: from smtp125.ord1c.emailsrvr.com (smtp125.ord1c.emailsrvr.com [108.166.43.125]) by ietfa.amsl.com (Postfix) with ESMTP id 50FE11ACCF5 for <dnsop@ietf.org>; Wed,  8 Jan 2014 20:41:00 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 0642F1A057C; Wed,  8 Jan 2014 23:40:51 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp8.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id C3CF51A05DB;  Wed,  8 Jan 2014 23:40:49 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <52CD145E.8060801@nlnetlabs.nl>
Date: Wed, 8 Jan 2014 23:40:49 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <04EA28D3-8186-4743-B66B-1F1C06A57524@ogud.com>
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com> <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com> <20140104235045.GA24696@totoro.home.mukund.org> <28570EA3-CF74-4FD2-95CD-D8672E64C199@ogud.com> <52CD145E.8060801@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1510)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 04:41:02 -0000

On Jan 8, 2014, at 4:03 AM, Matthijs Mekking <matthijs@NLnetLabs.nl> =
wrote:

> On 01/08/2014 05:53 AM, Olafur Gudmundsson wrote:
>> Note;=20
>> This case is one of the reasons I want children to remove the C* =
records after parent performs the update,=20
>> then there is no chance of JoJo updates by parent depending on which =
Nameserver is polled.=20
>=20
> But the parent would still need to deal with the case that the C* is =
the
> same: The child may not yet have removed the record because it had not
> yet come to the conclusion that all DS records at the parent name
> servers are in sync. In this scenario, the parent shall also not take
> action (just like if there was no C* RRset).
>=20
> I think looking at the inception time is a better approach to prevent
> JoJo updates.


So you want an Parental Agent to look inside the RRSIG(s) as tiebreaker =
?

	Olafur



From matthijs@nlnetlabs.nl  Thu Jan  9 01:06:20 2014
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63CFC1ADFFC for <dnsop@ietfa.amsl.com>; Thu,  9 Jan 2014 01:06:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.444
X-Spam-Level: 
X-Spam-Status: No, score=-100.444 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8aAoXHgM0zwH for <dnsop@ietfa.amsl.com>; Thu,  9 Jan 2014 01:06:19 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B76091ADFEF for <dnsop@ietf.org>; Thu,  9 Jan 2014 01:06:18 -0800 (PST)
Received: from [213.154.224.18] (zoidberg.nlnetlabs.nl [213.154.224.18]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id s09963gc085025 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 9 Jan 2014 10:06:05 +0100 (CET) (envelope-from matthijs@nlnetlabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl s09963gc085025
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1389258367; bh=8e8x1emKC4XtWgTy+eFn150pmc8MLH6Kjj1IwzqnaYI=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=bfi6I8k8WLcVlNDk02y7rGtYBF4m9dnZ2Yihfr36rEzFwg01TT71UB0mwm5UzdIs2 kQtZiseGC0OuI6WN66B/6qqelAe5Yenj4QadZ9VyqM7qJJ90qWzqib0ObDG6qf/446 Q1oFZyNN1ZoI9sBGDvJE10En8t7Kbq/IMnrRsXpg=
X-Authentication-Warning: open.nlnetlabs.nl: Host zoidberg.nlnetlabs.nl [213.154.224.18] claimed to be [213.154.224.18]
Message-ID: <52CE667B.7020802@nlnetlabs.nl>
Date: Thu, 09 Jan 2014 10:06:03 +0100
From: Matthijs Mekking <matthijs@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
References: <20140104204035.7446.24984.idtracker@ietfa.amsl.com> <CAHw9_iKbHbt7+j=C2ub=vRR+0rNgU+3P=WjnpV4gnY=y=q4xOQ@mail.gmail.com> <20140104235045.GA24696@totoro.home.mukund.org> <28570EA3-CF74-4FD2-95CD-D8672E64C199@ogud.com> <52CD145E.8060801@nlnetlabs.nl> <04EA28D3-8186-4743-B66B-1F1C06A57524@ogud.com>
In-Reply-To: <04EA28D3-8186-4743-B66B-1F1C06A57524@ogud.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [213.154.224.1]); Thu, 09 Jan 2014 10:06:06 +0100 (CET)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-delegation-trust-maintainance-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 09:06:20 -0000

On 01/09/2014 05:40 AM, Olafur Gudmundsson wrote:
> 
> On Jan 8, 2014, at 4:03 AM, Matthijs Mekking <matthijs@NLnetLabs.nl> wrote:
> 
>> On 01/08/2014 05:53 AM, Olafur Gudmundsson wrote:
>>> Note; 
>>> This case is one of the reasons I want children to remove the C* records after parent performs the update, 
>>> then there is no chance of JoJo updates by parent depending on which Nameserver is polled. 
>>
>> But the parent would still need to deal with the case that the C* is the
>> same: The child may not yet have removed the record because it had not
>> yet come to the conclusion that all DS records at the parent name
>> servers are in sync. In this scenario, the parent shall also not take
>> action (just like if there was no C* RRset).
>>
>> I think looking at the inception time is a better approach to prevent
>> JoJo updates.
> 
> 
> So you want an Parental Agent to look inside the RRSIG(s) as tiebreaker ?

Yes. And I don't see any harm in that: The Parental Agent already has to
check the packet because of the Continuity rule.

Best regards,
  Matthijs

> 
> 	Olafur
> 
> 
> 


From ajs@anvilwalrusden.com  Tue Jan 14 09:22:55 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C79B1AE113 for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 09:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4nC2-zVZkSXX for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 09:22:54 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 0551A1AE0DC for <dnsop@ietf.org>; Tue, 14 Jan 2014 09:22:53 -0800 (PST)
Received: from mx1.yitter.info (nat-02-mht.dyndns.com [216.146.45.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 5DD9F8A031 for <dnsop@ietf.org>; Tue, 14 Jan 2014 17:22:42 +0000 (UTC)
Date: Tue, 14 Jan 2014 12:22:40 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140114172240.GO17198@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 17:22:55 -0000

Dear colleagues,

For my sins, I have been following some of the recent discussions
about "Internet governance".  One of the discussions over on the
"1net" list (http://1net-mail.1net.org/mailman/listinfo/discuss) is
about the control by one particular government of the DNS root zone,
and how uncomfortable that makes some other governments.  The
consequence has been renewed discussion on a somewhat older proposal
for splitting up the management of the root zone keys.  The proposal
can be found at
http://www.internetgovernance.org/wordpress/wp-content/uploads/SecuringTheRoot.pdf.

The proposal has the appealing property that nobody can "hijack" the
root, and if you don't trust any particular actor then the approach
ensures that it is at least technically difficult (or detectable) that
someone has acted alone.  But it has always seemed to me that the
approach would result in a very great increase in the size of the root
key RRset as well as the RRSIGs necessary at least over the DNSKEY
RRset.  One response to this
(http://1net-mail.1net.org/pipermail/discuss/2014-January/001057.html)
is, "So what?  It's the root.  It'll be widely cached, and TCP is a
small price to pay for this on the occasions it's needed."

I am not sure I am so sanguine, but this put in my mind the
draft-ietf-dnsop-respsize draft, which I now realise was never
published as an RFC.

I'd like this thread to discuss the "so what, use TCP!" remark.  I'd
also like to ask either the chairs or the WG whether
draft-ietf-dnsop-respsize-14 needs revision and, if so, what revision
to be publishable, because I think it's needed advice.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jabley@hopcount.ca  Tue Jan 14 10:55:14 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 264FE1ADF8F for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 10:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZPk3zX21z08 for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 10:55:12 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCC91ADF90 for <dnsop@ietf.org>; Tue, 14 Jan 2014 10:55:12 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id ar20so903700iec.22 for <dnsop@ietf.org>; Tue, 14 Jan 2014 10:55:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=C/vHArdgrXFYB8BXVB1DsVx7Rsr0GnGslKXFxpoiQZs=; b=LAI8+N0fuTM3UxzdNGF6/wCi/JMJclwH+3nTm0vbyKGDcI2AjTSqPjsSGQvWZtpYXj Y3nJPIkPPOsAk2hj2mIP8Rdy9/RrPD9kU0m4uqcL4v7qXdBtFENhKs/orqExZoekRrdD 6qZiWYb53GMo8hawuYspvYcI5p5mVrPboC6y0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=C/vHArdgrXFYB8BXVB1DsVx7Rsr0GnGslKXFxpoiQZs=; b=cmJiUZVYD/ycO7gdqXZDhT7sWje0xXnwsyNaJe5mP6U+xpZbE9oLnSsDgcxa3TWExD TcCR8W0VHNT5OF4wI0q/keM8BzSOi0w17rZZivdCOVevinOZcm7se6txKWOi+xUhCV2z VMRuNAjezLwMwOhMz2kKdhI8P7NoYpZ/dqndGnv0aC3mxznrYa7OB+7VwEqm+lZcHDBx kOpIdx1vx2Dmba4lM0WHgIQCHAUeVVtX0EkzJHpRu92PkpT25oV/j2V+ecybZWHmJd2F C9tPgMQOX1Vm2p/j0vk+AqcElUPzm6LUtZ5uW4OGI4rTG9i2NATwQhI4caAO5lVekCaW HQNw==
X-Gm-Message-State: ALoCoQkJABXX3hGWQ2ztuGkn5z7RuyrjfcEg3x3fo+3cdyuREpvfEMcVbyOnbFMXm9tGkRCnt0UP
X-Received: by 10.50.119.4 with SMTP id kq4mr4692821igb.40.1389725700917; Tue, 14 Jan 2014 10:55:00 -0800 (PST)
Received: from [199.212.90.62] (24-52-234-221.cable.teksavvy.com. [24.52.234.221]) by mx.google.com with ESMTPSA id a1sm2513149igo.0.2014.01.14.10.54.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Jan 2014 10:54:59 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_13912D51-09B8-4D13-BC42-F46FF4CEC0AB"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20140114172240.GO17198@mx1.yitter.info>
Date: Tue, 14 Jan 2014 13:54:56 -0500
Message-Id: <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca>
References: <20140114172240.GO17198@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 18:55:14 -0000

--Apple-Mail=_13912D51-09B8-4D13-BC42-F46FF4CEC0AB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 2014-01-14, at 12:22, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

> For my sins, I have been following some of the recent discussions
> about "Internet governance".  One of the discussions over on the
> "1net" list (http://1net-mail.1net.org/mailman/listinfo/discuss) is
> about the control by one particular government of the DNS root zone,
> and how uncomfortable that makes some other governments.  The
> consequence has been renewed discussion on a somewhat older proposal
> for splitting up the management of the root zone keys.  The proposal
> can be found at
> =
http://www.internetgovernance.org/wordpress/wp-content/uploads/SecuringThe=
Root.pdf.

It's interesting to see that what was actually built in 2009/2010 is =
largely compatible (at the high-level diagram level) with what was =
proposed, except that there's only a single RKO and it's called IANA. =
The general framework (as deployed today) whereby KSRs are sent from the =
RZM to the RKO and ceremonies are held at the RKO to process them seems =
eminently extensible, at least in theory.

However, each RKO you add increases the operational risk that an SKR =
from that RKO might not be obtained within the required window, which =
puts zone publication in jeopardy. It also adds points where political =
concerns might lead to a refusal to sign. Since a KSR is not linked to a =
specific set of proposed changes to the root zone, a refusal to sign =
would presumably be on general/philosophical grounds rather than in =
reaction to any particular proposed change to the root zone.

Timing for KSK rollover would have to be carefully managed, since it =
seems like having multiple RKOs roll their KSKs in overlapping windows =
would be a recipe for grand hilarity.

> The proposal has the appealing property that nobody can "hijack" the
> root,

Well, in fact any RKO can hijack the root (by which I mean put its =
publication in jeopardy for people validating against that RKO's trust =
anchor). They can just refuse to process a KSR; during the time window =
corresponding to that KSR, validators depending solely on that RKO's =
trust anchor would see the namespace go dark.

[If validators took the approach of installing trust anchors from each =
and every RKO to mitigate this possibility, then they are effectively =
saying "I'm happy so long as at least one RKO is happy even if all the =
others are deeply miserable", which doesn't sound like it achieves the =
document's objectives.]

In terms of custody of each KSK, multiple RKOs means multiple =
opportunities to compromise private key assets. That's a change to the =
risk profile. Also, one RKO performing key ceremonies is tedious enough, =
imagine if there were five times as many :-)

I realise this wasn't the point you were raising, but I thought it was =
an interesting tangent. To the point you were actually raising:

> I am not sure I am so sanguine, but this put in my mind the
> draft-ietf-dnsop-respsize draft, which I now realise was never
> published as an RFC.
>=20
> I'd like this thread to discuss the "so what, use TCP!" remark.  I'd
> also like to ask either the chairs or the WG whether
> draft-ietf-dnsop-respsize-14 needs revision and, if so, what revision
> to be publishable, because I think it's needed advice.

I also think that draft should be published. I think we have a little =
more operational experience with (and studies that speak to) large =
responses now than we did when Vixie last lifted the pen on that =
document, so I imagine it would benefit from some review.

I would be happy to review and/or contribute.


Joe


--Apple-Mail=_13912D51-09B8-4D13-BC42-F46FF4CEC0AB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlLViAAACgkQNI8MvYZSOiy76QCgqzHoUDdl8IPSKFSp3e/75Koz
GxsAoLTjxE2uEcrNgx1xspD+Vy57rwJS
=cZn/
-----END PGP SIGNATURE-----

--Apple-Mail=_13912D51-09B8-4D13-BC42-F46FF4CEC0AB--

From ajs@anvilwalrusden.com  Tue Jan 14 12:09:07 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1680B1AE210 for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 12:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkhCtf2d5xp6 for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 12:09:05 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id C5A841AE13E for <dnsop@ietf.org>; Tue, 14 Jan 2014 12:09:05 -0800 (PST)
Received: from mx1.yitter.info (nat-02-mht.dyndns.com [216.146.45.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id CE46B8A031 for <dnsop@ietf.org>; Tue, 14 Jan 2014 20:08:53 +0000 (UTC)
Date: Tue, 14 Jan 2014 15:08:49 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140114200849.GA17907@mx1.yitter.info>
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 20:09:07 -0000

On Tue, Jan 14, 2014 at 01:54:56PM -0500, Joe Abley wrote:

> It's interesting to see that what was actually built in 2009/2010 is
> largely compatible (at the high-level diagram level) with what was
> proposed

I thought that was interesting too.

> However, each RKO you add increases the operational risk that an SKR
> from that RKO might not be obtained within the required window,
> which puts zone publication in jeopardy.

Good point.  I think the idea is that this is a feature, because it's
supposed to be the Mutually-Assured Destruction threat that will
prevent the USG from unilaterally removing some country from the root
zone (that seems to be the threat people are worried about.  Why is
left as an exercise for the reader.  Note that I do not promise there
is a solution to this exercise).

> [If validators took the approach of installing trust anchors from
> each and every RKO to mitigate this possibility, then they are
> effectively saying "I'm happy so long as at least one RKO is happy
> even if all the others are deeply miserable", which doesn't sound
> like it achieves the document's objectives.]

It _might_, if the idea were instead that validators used n of m.  Ben
Laurie had a not-completely-dissimilar idea for root TA distribution
entered in the "rollover" competition back in 2006 or so.  See
http://tools.ietf.org/html/draft-laurie-dnssec-key-distribution-02.

Thanks for the observations, which I think are quite helpful.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From ggm@algebras.org  Tue Jan 14 15:04:26 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91461AE22E for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 15:04:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 607hLnIMbdEg for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 15:04:24 -0800 (PST)
Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7D91ADFF3 for <dnsop@ietf.org>; Tue, 14 Jan 2014 15:04:24 -0800 (PST)
Received: by mail-pd0-f171.google.com with SMTP id x10so283666pdj.2 for <dnsop@ietf.org>; Tue, 14 Jan 2014 15:04:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LSLo2JSTmoA5JFV/Fve70CBYtNwwgWLcNy69wg5AZqk=; b=FfPyE10gby0l3qBs85HTeLk+09r0elotEqw9lW+l1Df07dr6R9hLh6Ok100KmluMqD c7KAGaxqdvZ/T38BJ+k7sVeiz/5+ka+V9KUy0ZO651GkD3d+U+Tt9IuTr8Kd+rTbmr1B cH8u8FcD+Ld4tju36ghZtY7Qv8E+Q5drxQX22EximVl9jG7+/YOC1LU7HPV6qX6UYlSm 9sx2iyty6K9PXA6NMlFRP30n3d7Xsf4z0n0SUslcrWhPwTISvQR3TveJtp+j/zOS1LFb UNYBTk8H3k28+X/7MpSL2K6zizc7Y9ifLHx/5ucwSAgJ6lpg8vagca5KeAV5x46SccFY PmAw==
X-Gm-Message-State: ALoCoQmCc5xaYWXGaU7FH6RJuGZlmOnA79w5XWXIlRh7FEs4+m64ZR7F3k8F99hwbfQJsbbq+FTs
MIME-Version: 1.0
X-Received: by 10.66.27.72 with SMTP id r8mr4743301pag.62.1389740652769; Tue, 14 Jan 2014 15:04:12 -0800 (PST)
Received: by 10.70.89.41 with HTTP; Tue, 14 Jan 2014 15:04:12 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:f02e:a876:58e:91ba]
In-Reply-To: <20140114200849.GA17907@mx1.yitter.info>
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca> <20140114200849.GA17907@mx1.yitter.info>
Date: Wed, 15 Jan 2014 09:04:12 +1000
Message-ID: <CAKr6gn0rQa8CeA+5tBYnr2G52-P-qd4V1g=ohQMwgi9osfQYvQ@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=bcaec52bec1ff0474304eff635d7
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 23:04:26 -0000

--bcaec52bec1ff0474304eff635d7
Content-Type: text/plain; charset=ISO-8859-1

If multiple independent entities sign, can't they elect to use shorter
algorithms?

I know 'short can be spoofed' is out there, but since there are now n *
<512> instead of 1 * 2048 is it not theoretically possible that at a cost
of more complexity, it can be demonstrated that as long as 1) the sigs are
all current 2) all the sig agree then the risk of n 512-bit signings is not
necessarily worse than one 2048 or 4096 bit signing, for the specific need
we have: proof of correctness. (n is unstated. 512 is a nonce. I have no
idea what the sweet spot of keysize and number of keys would be.)

therefore, if this is true, trading complexity for keysize might not
increase the initial bootstrap zone transfer size that much.

I am not a cryptographer and do not play one on TV


On Wed, Jan 15, 2014 at 6:08 AM, Andrew Sullivan <ajs@anvilwalrusden.com>wrote:

> On Tue, Jan 14, 2014 at 01:54:56PM -0500, Joe Abley wrote:
>
> > It's interesting to see that what was actually built in 2009/2010 is
> > largely compatible (at the high-level diagram level) with what was
> > proposed
>
> I thought that was interesting too.
>
> > However, each RKO you add increases the operational risk that an SKR
> > from that RKO might not be obtained within the required window,
> > which puts zone publication in jeopardy.
>
> Good point.  I think the idea is that this is a feature, because it's
> supposed to be the Mutually-Assured Destruction threat that will
> prevent the USG from unilaterally removing some country from the root
> zone (that seems to be the threat people are worried about.  Why is
> left as an exercise for the reader.  Note that I do not promise there
> is a solution to this exercise).
>
> > [If validators took the approach of installing trust anchors from
> > each and every RKO to mitigate this possibility, then they are
> > effectively saying "I'm happy so long as at least one RKO is happy
> > even if all the others are deeply miserable", which doesn't sound
> > like it achieves the document's objectives.]
>
> It _might_, if the idea were instead that validators used n of m.  Ben
> Laurie had a not-completely-dissimilar idea for root TA distribution
> entered in the "rollover" competition back in 2006 or so.  See
> http://tools.ietf.org/html/draft-laurie-dnssec-key-distribution-02.
>
> Thanks for the observations, which I think are quite helpful.
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--bcaec52bec1ff0474304eff635d7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If multiple independent entities sign, can&#39;t they elec=
t to use shorter algorithms?<div><br></div><div>I know &#39;short can be sp=
oofed&#39; is out there, but since there are now n * &lt;512&gt; instead of=
 1 * 2048 is it not theoretically possible that at a cost of more complexit=
y, it can be demonstrated that as long as 1) the sigs are all current 2) al=
l the sig agree then the risk of n 512-bit signings is not necessarily wors=
e than one 2048 or 4096 bit signing, for the specific need we have: proof o=
f correctness. (n is unstated. 512 is a nonce. I have no idea what the swee=
t spot of keysize and number of keys would be.)</div>
<div><br></div><div>therefore, if this is true, trading complexity for keys=
ize might not increase the initial bootstrap zone transfer size that much.<=
/div><div><br></div><div>I am not a cryptographer and do not play one on TV=
</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
 Jan 15, 2014 at 6:08 AM, Andrew Sullivan <span dir=3D"ltr">&lt;<a href=3D"=
mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrusden.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Tue, Jan 14, 2014 at 01=
:54:56PM -0500, Joe Abley wrote:<br>
<br>
&gt; It&#39;s interesting to see that what was actually built in 2009/2010 =
is<br>
&gt; largely compatible (at the high-level diagram level) with what was<br>
&gt; proposed<br>
<br>
</div>I thought that was interesting too.<br>
<div class=3D"im"><br>
&gt; However, each RKO you add increases the operational risk that an SKR<b=
r>
&gt; from that RKO might not be obtained within the required window,<br>
&gt; which puts zone publication in jeopardy.<br>
<br>
</div>Good point. =A0I think the idea is that this is a feature, because it=
&#39;s<br>
supposed to be the Mutually-Assured Destruction threat that will<br>
prevent the USG from unilaterally removing some country from the root<br>
zone (that seems to be the threat people are worried about. =A0Why is<br>
left as an exercise for the reader. =A0Note that I do not promise there<br>
is a solution to this exercise).<br>
<div class=3D"im"><br>
&gt; [If validators took the approach of installing trust anchors from<br>
&gt; each and every RKO to mitigate this possibility, then they are<br>
&gt; effectively saying &quot;I&#39;m happy so long as at least one RKO is =
happy<br>
&gt; even if all the others are deeply miserable&quot;, which doesn&#39;t s=
ound<br>
&gt; like it achieves the document&#39;s objectives.]<br>
<br>
</div>It _might_, if the idea were instead that validators used n of m. =A0=
Ben<br>
Laurie had a not-completely-dissimilar idea for root TA distribution<br>
entered in the &quot;rollover&quot; competition back in 2006 or so. =A0See<=
br>
<a href=3D"http://tools.ietf.org/html/draft-laurie-dnssec-key-distribution-=
02" target=3D"_blank">http://tools.ietf.org/html/draft-laurie-dnssec-key-di=
stribution-02</a>.<br>
<br>
Thanks for the observations, which I think are quite helpful.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
A<br>
<br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
_______________________________________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dnsop</a><br>
</div></div></blockquote></div><br></div>

--bcaec52bec1ff0474304eff635d7--

From jabley@hopcount.ca  Tue Jan 14 15:15:25 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA88B1ADFF3 for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 15:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dVKL41Wjs4OV for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 15:15:23 -0800 (PST)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4051A1F1F for <dnsop@ietf.org>; Tue, 14 Jan 2014 15:15:23 -0800 (PST)
Received: by mail-qc0-f170.google.com with SMTP id e9so321096qcy.15 for <dnsop@ietf.org>; Tue, 14 Jan 2014 15:15:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=lj8X8HomOlTHRmfLcc086A5Gh8U+UEykrTIqNN4yIjc=; b=WobcrquzgyzsvFWvrUWQdK4F4TxveM8hp7RXRrVrrLvaHay4U7W+kHDOi21Ctm6zn+ vjQquOdD7VKxx/GBLTS9mqVEkhYCzz24F5L8PzHoyTgOUldDS1GIFn3x/ZUSiuyp2Sfx 4xprg9yGvXy1tecVbFulmCMI2BDNM9RTORKM4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=lj8X8HomOlTHRmfLcc086A5Gh8U+UEykrTIqNN4yIjc=; b=iwUf17iy9oChq/pM6ES5Tvl+pL0wrWneUzuJdPvnLnTzDHsQcli9S4KF3P+GR+QWW2 ik0anKSVd3UulcKeL/0LB5eAG6ynz9WCLmXkmk+jipLXJZDYJlxfnM5hSsSh7pONvuNV tSGZCy95bjnHBzDHo0MZ1gFtOn27Ogh6KbI5PNZ343c82mRdobF/zxGH5Pv1IzbHXZFf 372o8P8TaQCh8rngyYam12VLfLMk9RqZvmY9gqnJmutZKF9wQu/2GBYLsRrka3vXBOZ8 IqVNrqi9WAcVw6/TqOznU6meqObgtUi183a9MlKD1c3+JnDpGhvQB+yWufjWAYJe+gB6 90Aw==
X-Gm-Message-State: ALoCoQldayYGtJqzSSHeJHDuhDb4MNKoJqY/TBOAocw/3wY6reZU9Z3V+6PR7a4JxAxRrnoV63Lq
X-Received: by 10.224.57.148 with SMTP id c20mr7830721qah.59.1389741311544; Tue, 14 Jan 2014 15:15:11 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:85c9:f0d9:4f25:1728? ([2001:4900:1042:1:85c9:f0d9:4f25:1728]) by mx.google.com with ESMTPSA id f8sm3050442qab.19.2014.01.14.15.15.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Jan 2014 15:15:10 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_78557DDA-E7A3-48FE-962B-D9109F1F7FD8"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <CAKr6gn0rQa8CeA+5tBYnr2G52-P-qd4V1g=ohQMwgi9osfQYvQ@mail.gmail.com>
Date: Tue, 14 Jan 2014 18:15:08 -0500
Message-Id: <AA79D9D2-7B30-4418-9C9A-268FF54AC23A@hopcount.ca>
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca> <20140114200849.GA17907@mx1.yitter.info> <CAKr6gn0rQa8CeA+5tBYnr2G52-P-qd4V1g=ohQMwgi9osfQYvQ@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop WG <dnsop@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 23:15:25 -0000

--Apple-Mail=_78557DDA-E7A3-48FE-962B-D9109F1F7FD8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 2014-01-14, at 18:04, George Michaelson <ggm@algebras.org> wrote:

> If multiple independent entities sign, can't they elect to use shorter =
algorithms?
>=20
> I know 'short can be spoofed' is out there, but since there are now n =
* <512> instead of 1 * 2048 is it not theoretically possible that at a =
cost of more complexity, it can be demonstrated that as long as 1) the =
sigs are all current 2) all the sig agree then the risk of n 512-bit =
signings is not necessarily worse than one 2048 or 4096 bit signing, for =
the specific need we have: proof of correctness. (n is unstated. 512 is =
a nonce. I have no idea what the sweet spot of keysize and number of =
keys would be.)

If you sign the DNSKEY RRSet with N KSKs of the same size as the single =
current KSK, then presumably the expected time for one of them to be =
factored is N times lower than the expected time to factor a single key, =
given the same compute resources being available for each key in all =
cases.

This suggests that if multiple KSKs are used, the keys need to be =
longer, not shorter, if the same degree of protection is desired.

I'm assuming that what we're talking about is this:

. IN DNSKEY ZSK0
. IN DNSKEY ZSK1
. IN DNSKEY KSK0
. IN DNSKEY KSK1
. IN DNSKEY ...
. IN DNSKEY KSKn
. IN RRSIG DNSKEY KSK0
. IN RRSIG DNSKEY KSK1
. IN RRSIG DNSKEY ...
. IN RRSIG DNSKEY KSKn

(the size of which makes my hair stand on end) and not this:

. IN DNSKEY ZSK0
. IN DNSKEY ZSK1
. IN DNSKEY KSKnew
. IN RRSIG DNSKEY KSK

where KSKnew is some combinatorial function of {KSK0, KSK1, ..., KSKn} =
since this second approach still requires a single KSKnew to be prepared =
in a single place in order to generate the RRSIG, which would presumably =
be a non-goal of de-centralising control of the keys.

> I am not a cryptographer and do not play one on TV

Me neither.


Joe


--Apple-Mail=_78557DDA-E7A3-48FE-962B-D9109F1F7FD8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlLVxPwACgkQNI8MvYZSOizz4ACgwRnwAYMcCxDyVq+6/2rENysX
TmcAoIBJ4HXMXolFgv8MUfnplI7lXdRL
=u5jU
-----END PGP SIGNATURE-----

--Apple-Mail=_78557DDA-E7A3-48FE-962B-D9109F1F7FD8--

From paul.hoffman@vpnc.org  Tue Jan 14 16:16:17 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 846DD1AE11F for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 16:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJPKr8cuGYa6 for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 16:16:16 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 539011AE0F8 for <dnsop@ietf.org>; Tue, 14 Jan 2014 16:16:16 -0800 (PST)
Received: from [10.20.30.90] (50-1-51-230.dsl.dynamic.fusionbroadband.com [50.1.51.230]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0ENtvZQ039681 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 14 Jan 2014 16:55:58 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-51-230.dsl.dynamic.fusionbroadband.com [50.1.51.230] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAKr6gn0rQa8CeA+5tBYnr2G52-P-qd4V1g=ohQMwgi9osfQYvQ@mail.gmail.com>
Date: Tue, 14 Jan 2014 16:16:00 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACC19E1E-1D30-4A8A-B128-67FBF700EBDE@vpnc.org>
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca> <20140114200849.GA17907@mx1.yitter.info> <CAKr6gn0rQa8CeA+5tBYnr2G52-P-qd4V1g=ohQMwgi9osfQYvQ@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.1827)
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 00:16:17 -0000

On Jan 14, 2014, at 3:04 PM, George Michaelson <ggm@algebras.org> wrote:

> If multiple independent entities sign, can't they elect to use shorter =
algorithms?
>=20
> I know 'short can be spoofed' is out there, but since there are now n =
* <512> instead of 1 * 2048 is it not theoretically possible that at a =
cost of more complexity, it can be demonstrated that as long as 1) the =
sigs are all current 2) all the sig agree then the risk of n 512-bit =
signings is not necessarily worse than one 2048 or 4096 bit signing, for =
the specific need we have: proof of correctness. (n is unstated. 512 is =
a nonce. I have no idea what the sweet spot of keysize and number of =
keys would be.)
>=20
> therefore, if this is true, trading complexity for keysize might not =
increase the initial bootstrap zone transfer size that much.
>=20
> I am not a cryptographer and do not play one on TV

I am not a cryptographer but I *do* play one on television, and that =
proposal is terrible. Breaking asymmetric keys gets logarithmically =
harder as the key size goes up; that's why no one has publicly broken a =
1024-bit RSA key, even though they have had much, much more time (and =
now-faster CPUs) than the earlier breaks.

It would orders of magnitude easier to break 4 512-bit keys than one =
2048-bit key. The work would also parallelize better so that you need =
smaller systems to do the work.

--Paul Hoffman=

From dougb@dougbarton.us  Tue Jan 14 16:44:07 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 181A71AE194 for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 16:44:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPv8QGRqn1GF for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 16:44:06 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 05C801ADF47 for <dnsop@ietf.org>; Tue, 14 Jan 2014 16:44:06 -0800 (PST)
Received: from [IPv6:2001:470:d:5e7:6428:3c09:51ac:eee1] (unknown [IPv6:2001:470:d:5e7:6428:3c09:51ac:eee1]) by dougbarton.us (Postfix) with ESMTPSA id B374222B2C for <dnsop@ietf.org>; Wed, 15 Jan 2014 00:43:53 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1389746633; bh=+ghjNAbVA5E2b5UZzG1LxMNcIDvcbMkx0V/jrrI9znU=; h=Date:From:To:Subject:References:In-Reply-To; b=cUjX55Ed/pWCTWTOkM6zdJlpvErkz0GKv5LMhXg3xTOE0NAh3Xt3t/rJU97yMJtRs otHluEVAMMXnCSfF1ks1rA/AaW/LTKSkYfvOC3Ue1kkUZKq1ZPjumDTZBQlszGWEeh r5X7RH2Kd4ElLI8neTo8igva+3zWrJJ26dJJkzdQ=
Message-ID: <52D5D9C8.6050902@dougbarton.us>
Date: Tue, 14 Jan 2014 16:43:52 -0800
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca> <20140114200849.GA17907@mx1.yitter.info>
In-Reply-To: <20140114200849.GA17907@mx1.yitter.info>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 00:44:07 -0000

On 01/14/2014 12:08 PM, Andrew Sullivan wrote:
> Good point.  I think the idea is that this is a feature, because it's
> supposed to be the Mutually-Assured Destruction threat that will
> prevent the USG from unilaterally removing some country from the root
> zone (that seems to be the threat people are worried about.

It historically has been the main threat that several countries are 
worried about, however DNSSEC doesn't do anything to stop it. Other than 
the DS records (if any) the records associated with a given TLD 
(specifically the NS records) in the root are not signed.

Of course as DNSSEC becomes more important removal of the DS records 
will become correspondingly more important, but that's not the threat 
that these people care about.

Doug

From dougb@dougbarton.us  Tue Jan 14 16:50:45 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B233D1AE1B0 for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 16:50:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fs_b5tJPo1Or for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 16:50:44 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 9E15A1ADF47 for <dnsop@ietf.org>; Tue, 14 Jan 2014 16:50:44 -0800 (PST)
Received: from [IPv6:2001:470:d:5e7:6428:3c09:51ac:eee1] (unknown [IPv6:2001:470:d:5e7:6428:3c09:51ac:eee1]) by dougbarton.us (Postfix) with ESMTPSA id 418B722BC4 for <dnsop@ietf.org>; Wed, 15 Jan 2014 00:50:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1389747033; bh=LfX/AVgtTH8fd/3ocQbFIZmWdjSUayl3E64ZTjx20qA=; h=Date:From:To:Subject:References:In-Reply-To; b=Fo5TMXBlPAddzO2lZims6Bc0p8QEFYNblfmCyWkmN+n+clZ7bWja7SViqYCO0mLOg ZTXfMlE+CBYa3OFTtebuIKtSPgjz+TCqCfRVfvZ0f6FUdOMHn+SISehqJK3kcc41n0 Gtd0Jb4AWZdlR/0hsvbOXYnHgn8vHpL23vJsTaZ8=
Message-ID: <52D5DB58.3040103@dougbarton.us>
Date: Tue, 14 Jan 2014 16:50:32 -0800
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca> <20140114200849.GA17907@mx1.yitter.info> <52D5D9C8.6050902@dougbarton.us>
In-Reply-To: <52D5D9C8.6050902@dougbarton.us>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 00:50:45 -0000

On 01/14/2014 04:43 PM, Doug Barton wrote:
> Other than the DS records (if any) the records associated with a given
> TLD (specifically the NS records) in the root are not signed.

... obviously the glue records are not signed either of course. My point 
was that it's the delegation that some paranoid countries don't want 
removed, and DNSSEC isn't going to help that.

Doug


From ggm@algebras.org  Tue Jan 14 17:48:08 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 409831AE16A for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 17:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FHa1kdja8SOu for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 17:48:06 -0800 (PST)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id D0B3E1AE150 for <dnsop@ietf.org>; Tue, 14 Jan 2014 17:48:06 -0800 (PST)
Received: by mail-pd0-f181.google.com with SMTP id p10so432212pdj.12 for <dnsop@ietf.org>; Tue, 14 Jan 2014 17:47:55 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=87ngRWFQyABc7U/Pz4H5pfv4Ny2KyGjoLFYGlRraFDc=; b=MZCzP/VZgS2+TwY2E/l/P+rLKeyYaQ0m9OoT73Hlf8En00LWvX29RHnANJ85o8Mk5t xPFuq5KqV+b8WbNUuRbeJxVJ7wk86itH7WkvrwumYuMmEJ+/lkTq1o9yuKBUCyLoTCjc 4jc2vAQZJw9VVSa+Mn/LNEn2SV4/prf6duIsEW0g8LBiZzd0/0H0hBjWzNK1t1l0O2wd +pBNoXzveLnhXdFVrd+w1Afyxi1esuzaLpnShXG6dJ0aaR5uOnCoYkbk7N2eQNNDwmZf NgI8Kc5Nsp+pPBHVm8HeoeiRzaQGpVZDj/g5iRqiO1adpkXfUeT1qtisJGPNfMSFAc9+ WM1Q==
X-Gm-Message-State: ALoCoQnE9iHLFa/x38zwnYxGnf6pfpQj2eVOan7HZy59p6HP5wNPiXIMbNhsBgGhpezqloby238Y
MIME-Version: 1.0
X-Received: by 10.66.142.107 with SMTP id rv11mr5382377pab.17.1389750475353; Tue, 14 Jan 2014 17:47:55 -0800 (PST)
Received: by 10.70.89.41 with HTTP; Tue, 14 Jan 2014 17:47:55 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:f02e:a876:58e:91ba]
In-Reply-To: <ACC19E1E-1D30-4A8A-B128-67FBF700EBDE@vpnc.org>
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca> <20140114200849.GA17907@mx1.yitter.info> <CAKr6gn0rQa8CeA+5tBYnr2G52-P-qd4V1g=ohQMwgi9osfQYvQ@mail.gmail.com> <ACC19E1E-1D30-4A8A-B128-67FBF700EBDE@vpnc.org>
Date: Wed, 15 Jan 2014 11:47:55 +1000
Message-ID: <CAKr6gn2s+qdH0HDMZMH=xpJ-m-BWLO6M4exUp-EJ5_CKSXdruw@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=001a11331e466905d104eff87fa8
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 01:48:08 -0000

--001a11331e466905d104eff87fa8
Content-Type: text/plain; charset=ISO-8859-1

thanks for the cluestick hit. so we can't trade multiple sigs for length,
which means for public benefit reasons adding more visible signers at the
top does irredeemably increase the dataset size because the key size has to
stay high.

there are no free lunches for public accountability.


On Wed, Jan 15, 2014 at 10:16 AM, Paul Hoffman <paul.hoffman@vpnc.org>wrote:

> On Jan 14, 2014, at 3:04 PM, George Michaelson <ggm@algebras.org> wrote:
>
> > If multiple independent entities sign, can't they elect to use shorter
> algorithms?
> >
> > I know 'short can be spoofed' is out there, but since there are now n *
> <512> instead of 1 * 2048 is it not theoretically possible that at a cost
> of more complexity, it can be demonstrated that as long as 1) the sigs are
> all current 2) all the sig agree then the risk of n 512-bit signings is not
> necessarily worse than one 2048 or 4096 bit signing, for the specific need
> we have: proof of correctness. (n is unstated. 512 is a nonce. I have no
> idea what the sweet spot of keysize and number of keys would be.)
> >
> > therefore, if this is true, trading complexity for keysize might not
> increase the initial bootstrap zone transfer size that much.
> >
> > I am not a cryptographer and do not play one on TV
>
> I am not a cryptographer but I *do* play one on television, and that
> proposal is terrible. Breaking asymmetric keys gets logarithmically harder
> as the key size goes up; that's why no one has publicly broken a 1024-bit
> RSA key, even though they have had much, much more time (and now-faster
> CPUs) than the earlier breaks.
>
> It would orders of magnitude easier to break 4 512-bit keys than one
> 2048-bit key. The work would also parallelize better so that you need
> smaller systems to do the work.
>
> --Paul Hoffman

--001a11331e466905d104eff87fa8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">thanks for the cluestick hit. so we can&#39;t trade multip=
le sigs for length, which means for public benefit reasons adding more visi=
ble signers at the top does irredeemably increase the dataset size because =
the key size has to stay high.<div>
<br></div><div>there are no free lunches for public accountability.</div></=
div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, J=
an 15, 2014 at 10:16 AM, Paul Hoffman <span dir=3D"ltr">&lt;<a href=3D"mail=
to:paul.hoffman@vpnc.org" target=3D"_blank">paul.hoffman@vpnc.org</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Jan 14, 2014, at 3:04 P=
M, George Michaelson &lt;<a href=3D"mailto:ggm@algebras.org">ggm@algebras.o=
rg</a>&gt; wrote:<br>

<br>
&gt; If multiple independent entities sign, can&#39;t they elect to use sho=
rter algorithms?<br>
&gt;<br>
&gt; I know &#39;short can be spoofed&#39; is out there, but since there ar=
e now n * &lt;512&gt; instead of 1 * 2048 is it not theoretically possible =
that at a cost of more complexity, it can be demonstrated that as long as 1=
) the sigs are all current 2) all the sig agree then the risk of n 512-bit =
signings is not necessarily worse than one 2048 or 4096 bit signing, for th=
e specific need we have: proof of correctness. (n is unstated. 512 is a non=
ce. I have no idea what the sweet spot of keysize and number of keys would =
be.)<br>

&gt;<br>
&gt; therefore, if this is true, trading complexity for keysize might not i=
ncrease the initial bootstrap zone transfer size that much.<br>
&gt;<br>
&gt; I am not a cryptographer and do not play one on TV<br>
<br>
</div>I am not a cryptographer but I *do* play one on television, and that =
proposal is terrible. Breaking asymmetric keys gets logarithmically harder =
as the key size goes up; that&#39;s why no one has publicly broken a 1024-b=
it RSA key, even though they have had much, much more time (and now-faster =
CPUs) than the earlier breaks.<br>

<br>
It would orders of magnitude easier to break 4 512-bit keys than one 2048-b=
it key. The work would also parallelize better so that you need smaller sys=
tems to do the work.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--Paul Hoffman</font></span></blockquote></div><br></div>

--001a11331e466905d104eff87fa8--

From marka@isc.org  Tue Jan 14 17:54:48 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBF51AE10A for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 17:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0pn6IxTTxmn for <dnsop@ietfa.amsl.com>; Tue, 14 Jan 2014 17:54:47 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1851AD8EE for <dnsop@ietf.org>; Tue, 14 Jan 2014 17:54:47 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id D4787C9423; Wed, 15 Jan 2014 01:54:22 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1389750875; bh=ebv4y+HrPO+TGlkZw8XxmBAQMjxUKY8mhfsi7HonSmE=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=VGgFE8KdCA84TYSMVR2Uu8AnkWrehxusMxhU67zRzS4/kk/6nwJro22i1MlmaFtLy FOEARRBQWZ/VJHyS8lyiaAFXWZebKapAWar8HBqFJzFbaknvn4yLQy1OQSJoGskIqF ft3nk6A3PKLMSO1RAtLbrvETgk6Z8i2mGqa2l+t4=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 15 Jan 2014 01:54:22 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 8CB79160459; Wed, 15 Jan 2014 02:05:14 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 5AE3D16032F; Wed, 15 Jan 2014 02:05:14 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 131D8CFC36E; Wed, 15 Jan 2014 12:54:20 +1100 (EST)
To: Doug Barton <dougb@dougbarton.us>
From: Mark Andrews <marka@isc.org>
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca> <20140114200849.GA17907@mx1.yitter.info> <52D5D9C8.6050902@dougbarton.us> <52D5DB58.3040103@dougbarton.us>
In-reply-to: Your message of "Tue, 14 Jan 2014 16:50:32 -0800." <52D5DB58.3040103@dougbarton.us>
Date: Wed, 15 Jan 2014 12:54:19 +1100
Message-Id: <20140115015420.131D8CFC36E@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 01:54:48 -0000

In message <52D5DB58.3040103@dougbarton.us>, Doug Barton writes:
> On 01/14/2014 04:43 PM, Doug Barton wrote:
> > Other than the DS records (if any) the records associated with a given
> > TLD (specifically the NS records) in the root are not signed.
> 
> ... obviously the glue records are not signed either of course. My point 
> was that it's the delegation that some paranoid countries don't want 
> removed, and DNSSEC isn't going to help that.
> 
> Doug

And anyone can take the existing root zone, add a delegation and
sign the result with any key of they control.  If a government was
to remove a ccTLD I would suspect that there would be hundreds of
people offering such zones.

Additionally you can just graft on a tld and associated trust anchor
with existing validators if you don't want to regenerate the root
or if you don't want to trust some random person to sign the root
zone for you you can do it that way.

Removal of a ccTLD would cause short term disruption but the net
as a whole would route around the breakage.  We have seen plenty
of examples of this in the past.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From fanf2@hermes.cam.ac.uk  Wed Jan 15 03:30:42 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885621AE359 for <dnsop@ietfa.amsl.com>; Wed, 15 Jan 2014 03:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Lcyt0ho6oud for <dnsop@ietfa.amsl.com>; Wed, 15 Jan 2014 03:30:39 -0800 (PST)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id BC74C1AE34D for <dnsop@ietf.org>; Wed, 15 Jan 2014 03:30:39 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:48102) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1W3Ofy-0006Kb-hc (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 15 Jan 2014 11:30:26 +0000
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1W3Ofy-0005Vk-FJ (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 15 Jan 2014 11:30:26 +0000
Date: Wed, 15 Jan 2014 11:30:26 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Andrew Sullivan <ajs@anvilwalrusden.com>
In-Reply-To: <20140114200849.GA17907@mx1.yitter.info>
Message-ID: <alpine.LSU.2.00.1401151122550.13642@hermes-2.csi.cam.ac.uk>
References: <20140114172240.GO17198@mx1.yitter.info> <C6EFA413-1FFC-4188-B98A-13C747981FBC@hopcount.ca> <20140114200849.GA17907@mx1.yitter.info>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 11:30:42 -0000

Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
>
> It _might_, if the idea were instead that validators used n of m.

N of M validation also solves the other problems Joe mentioned, to do with
key rollover and failure to sign. That is, if a signer drops out (because
it failed to sign the DNSKEY RRset, or because it rolled its key)
validators will continue to work securely, and can update their trust
anchors at leisure.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From fanf2@hermes.cam.ac.uk  Wed Jan 15 03:41:13 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA1F91AE35E for <dnsop@ietfa.amsl.com>; Wed, 15 Jan 2014 03:41:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MGdP77jwvoML for <dnsop@ietfa.amsl.com>; Wed, 15 Jan 2014 03:41:12 -0800 (PST)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id 464DB1AE35A for <dnsop@ietf.org>; Wed, 15 Jan 2014 03:41:12 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:48590) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1W3OqC-0005BD-gu (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 15 Jan 2014 11:41:00 +0000
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1W3OqC-0006Hg-81 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 15 Jan 2014 11:41:00 +0000
Date: Wed, 15 Jan 2014 11:41:00 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Andrew Sullivan <ajs@anvilwalrusden.com>
In-Reply-To: <20140114172240.GO17198@mx1.yitter.info>
Message-ID: <alpine.LSU.2.00.1401151130490.13642@hermes-2.csi.cam.ac.uk>
References: <20140114172240.GO17198@mx1.yitter.info>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] More keys in the DNSKEY RRset at ., and draft-ietf-dnsop-respsize-nn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 11:41:13 -0000

Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

> I am not sure I am so sanguine, but this put in my mind the
> draft-ietf-dnsop-respsize draft, which I now realise was never
> published as an RFC.
>
> I'd like this thread to discuss the "so what, use TCP!" remark.

Nice idea.

http://www.potaroo.net/ispcol/2013-09/dnstcp.html

> I'd also like to ask either the chairs or the WG whether
> draft-ietf-dnsop-respsize-14 needs revision and, if so, what revision to
> be publishable, because I think it's needed advice.

It needs to cover the effect of EDNS0 pseudo-records on truncation, and
the extra DNSSEC records that appear in secure referrals. What about the
interaction between EDNS buffer size and MTU and middleboxes? Haya Shulman
has some attacks that could be discussed in the security considerations
section.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From paul@redbarn.org  Wed Jan 15 11:25:43 2014
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55AD61AE0FD for <dnsop@ietfa.amsl.com>; Wed, 15 Jan 2014 11:25:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bhn1YnlQrOHJ for <dnsop@ietfa.amsl.com>; Wed, 15 Jan 2014 11:25:41 -0800 (PST)
Received: from ss.vix.su (ss.vix.su [24.104.150.2]) by ietfa.amsl.com (Postfix) with ESMTP id A52161AE373 for <dnsop@ietf.org>; Wed, 15 Jan 2014 11:25:41 -0800 (PST)
Received: from [IPv6:2600:1004:b001:88db:61e8:833d:82b5:49d5] (unknown [IPv6:2600:1004:b001:88db:61e8:833d:82b5:49d5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ss.vix.su (Postfix) with ESMTPSA id 17BB1EBE06 for <dnsop@ietf.org>; Wed, 15 Jan 2014 19:25:28 +0000 (UTC) (envelope-from paul@redbarn.org)
Message-ID: <52D6E0AB.807@redbarn.org>
Date: Wed, 15 Jan 2014 11:25:31 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.8 (Windows/20130427)
MIME-Version: 1.0
To: "dnsop@ietf.org" <dnsop@ietf.org>
References: <52D298FB.3080100@redbarn.org>
In-Reply-To: <52D298FB.3080100@redbarn.org>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/alternative; boundary="------------010506080801040301000401"
Subject: [DNSOP] Passive DNS - Common Output Format (draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 19:25:43 -0000

This is a multi-part message in MIME format.
--------------010506080801040301000401
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

speaking for the authors of the draft below, i request adoption by
dnsop. --vixie

https://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/

Internet Engineering Task Force                              A. Dulaunoy
Internet-Draft                                                     CIRCL
Intended status: Informational                                 A. Kaplan
Expires: July 11, 2014                                           CERT.at
                                                                P. Vixie
                                                                H. Stern
                                                 Farsight Security, Inc.
                                                         January 7, 2014

                   Passive DNS - Common Output Format
                draft-dulaunoy-kaplan-passive-dns-cof-01

Abstract

   This document describes a common output format of Passive DNS Servers
   which clients can query.  The output format description includes also
   in addition a common semantic for each Passive DNS system.  By having
   multiple Passive DNS Systems adhere to the same output format for
   queries, users of multiple Passive DNS servers will be able to
   combine result sets easily.


...



--------------010506080801040301000401
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head><body style="background-color: rgb(255, 255, 255); color: rgb(0, 
0, 0); font-family: tt; font-size: 11pt;" text="#000000" 
bgcolor="#FFFFFF"><div style="font-size: 11pt;font-family: tt;">
<div style="font-size: 11pt;font-family: tt;"><span>speaking for the 
authors of the draft below, i request adoption by dnsop. --vixie<br><br><a
 
href="https://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/">https://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/</a>
 <br><br></span><span><pre style="font-family: monospace; line-height: 1.2em; margin: 0px; color: rgb(0, 0, 0); font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Internet Engineering Task Force                              A. Dulaunoy
Internet-Draft                                                     CIRCL
Intended status: Informational                                 A. Kaplan
Expires: July 11, 2014                                           CERT.at
                                                                P. Vixie
                                                                H. Stern
                                                 Farsight Security, Inc.
                                                         January 7, 2014

                   Passive DNS - Common Output Format
                draft-dulaunoy-kaplan-passive-dns-cof-01

<span class="m_h" style="font-family: arial; font-weight: bold;">Abstract</span>

   This document describes a common output format of Passive DNS Servers
   which clients can query.  The output format description includes also
   in addition a common semantic for each Passive DNS system.  By having
   multiple Passive DNS Systems adhere to the same output format for
   queries, users of multiple Passive DNS servers will be able to
   combine result sets easily.
</pre><br class="Apple-interchange-newline">...<br><br><br></span></div>



</div></body></html>

--------------010506080801040301000401--

From fanf2@hermes.cam.ac.uk  Thu Jan 16 06:27:58 2014
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 054281AE35E for <dnsop@ietfa.amsl.com>; Thu, 16 Jan 2014 06:27:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KSNxljXs5ev6 for <dnsop@ietfa.amsl.com>; Thu, 16 Jan 2014 06:27:56 -0800 (PST)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id CBBCF1AE356 for <dnsop@ietf.org>; Thu, 16 Jan 2014 06:27:55 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:37031) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1W3nv4-0003Xy-23 (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 16 Jan 2014 14:27:42 +0000
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1W3nv4-0007eA-Ji (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 16 Jan 2014 14:27:42 +0000
Date: Thu, 16 Jan 2014 14:27:42 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Paul Vixie <paul@redbarn.org>
In-Reply-To: <52D6E0AB.807@redbarn.org>
Message-ID: <alpine.LSU.2.00.1401161404280.13642@hermes-2.csi.cam.ac.uk>
References: <52D298FB.3080100@redbarn.org> <52D6E0AB.807@redbarn.org>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] Passive DNS - Common Output Format (draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 14:27:58 -0000

Paul Vixie <paul@redbarn.org> wrote:

> speaking for the authors of the draft below, i request adoption by
> dnsop. --vixie
>
> https://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/

A few questions / comments:

The ws non-terminal isn't defined. I guess it is supposed to be

	ws = *( %x10 / %x09 )

i.e. no newlines within a JSON object, which is different from the
definition of ws in RFC 4627. (Maybe use core ABNF WSP instead?)

The ABNF specifies that the field names are not quoted (the quotes are
part of the ABNF metasyntax not part of the language it specifies) which
is incompatible with JSON and disagrees with the examples in the appendix.

The appendix could do with some rubric to explain the backslashes.

Are numeric rrtypes represented as JSON numbers? Or a "TYPEnnn" string?

I guess time stamps are represented as JSON numbers.

How are sensor_id octet strings encoded as JSON strings?

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From gson@araneus.fi  Thu Jan 16 09:54:53 2014
Return-Path: <gson@araneus.fi>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D6D1A1F33 for <dnsop@ietfa.amsl.com>; Thu, 16 Jan 2014 09:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hp4kXxIJnKfb for <dnsop@ietfa.amsl.com>; Thu, 16 Jan 2014 09:54:50 -0800 (PST)
Received: from gunvor.araneus.fi (gunvor.araneus.fi [46.246.126.150]) by ietfa.amsl.com (Postfix) with ESMTP id 4B8451A1EF9 for <dnsop@ietf.org>; Thu, 16 Jan 2014 09:54:49 -0800 (PST)
Received: from guava.gson.org (unknown [10.0.1.240]) by gunvor.araneus.fi (Postfix) with ESMTP id AE373145854; Thu, 16 Jan 2014 17:54:36 +0000 (UTC)
Received: by guava.gson.org (Postfix, from userid 101) id 9A76B75E36; Thu, 16 Jan 2014 19:54:36 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <21208.7388.614870.591922@guava.gson.org>
Date: Thu, 16 Jan 2014 19:54:36 +0200
To: Paul Vixie <paul@redbarn.org>
In-Reply-To: Re: <52D6E0AB.807@redbarn.org>
References: <52D298FB.3080100@redbarn.org> <52D6E0AB.807@redbarn.org>
X-Mailer: VM 8.0.14 under 21.4.1 (i386--netbsdelf)
From: Andreas Gustafsson <gson@araneus.fi>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: [DNSOP] Passive DNS - Common Output Format	(draft-dulaunoy-kaplan-passive-dns-cof-01)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 17:54:53 -0000

Paul Vixie wrote:
> https://datatracker.ietf.org/doc/draft-dulaunoy-kaplan-passive-dns-cof/

I also have some comments on the draft.

Section 3.3, "Mandatory Fields", states:

   rdata MAY be an array as defined in JSON [RFC4627]

If the purpose of such an array is to represent an RRset containing
multiple RRs, the draft should say so.  It should also be clear
whether an implementation MAY represent all RRsets as arrays for
consistency, or MUST treat single-RR RRsets as a special case
and represent them as strings.

Section 3.3.2, "rrtype", states:

    The resource record type can be any values as described by IANA in
    the DNS parameters document in the section 'DNS Label types'

Presumably 'DNS Label types' should read 'Resource Record (RR) TYPEs'.

Section 3.3.3, "rdata", states:

    In general, this is to be interpreted as string.

It's not clear to me what "interpreted as a string" means.  The value
either is a JSON string or it is not; is this saying that non-string
values such as JSON integers, booleans, and objects should somehow be
converted into strings?  And if this is done only "in general", what
are the exceptions?  Or is this just a strange way of saying "This is
either a string or an array of strings"?

    A client MUST be able to interpret any value which is legal as the
    right hand side in a DNS zone file RFC 1035 [RFC1035] and RFC 1034
    [RFC1034].

A reader who follows the reference to RFC1034/RFC1035 and searches for
"zone file" will find nothing, as the term used in those documents is
"master file".

The master file format has the concept of a "current origin" which
affects the interpretation of unqualified domain names and the special
@ token.  I assume the intent is to interpret the value as if a
current origin of "." is in effect; the draft should say so explicitly.

It would also be good to state whether or not the value may
contain grouping parentheses, embedded newlines, and comments.

It would be helpful if Appendix A contained an example of an RRset
containing more than one RR.

To illustrate the interplay between the master file and JSON quoting
mechanisms, it would also be helpful if Appendix A could contain
examples illustrating the encoding of RRs like the following:

    example.com.   RP  john\.smith.example.com. .
    a.example.com. TXT "one string"
    b.example.com. TXT "two" "strings"
    c.example.com. TXT "string with \"embedded\" quotes"

Regards,
-- 
Andreas Gustafsson, gson@araneus.fi

From bortzmeyer@nic.fr  Thu Jan 23 00:47:45 2014
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69E771A02F1 for <dnsop@ietfa.amsl.com>; Thu, 23 Jan 2014 00:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GGoaso2LdGet for <dnsop@ietfa.amsl.com>; Thu, 23 Jan 2014 00:47:43 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by ietfa.amsl.com (Postfix) with ESMTP id A165C1A02ED for <dnsop@ietf.org>; Thu, 23 Jan 2014 00:47:43 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 477A739B56; Thu, 23 Jan 2014 08:47:41 +0000 (UTC)
Received: by tyrion (Postfix, from userid 1000) id A7C11F007B2; Thu, 23 Jan 2014 09:47:06 +0100 (CET)
Date: Thu, 23 Jan 2014 09:47:06 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Suzanne Woolf <suzworldwide@gmail.com>, lyman@interisle.net, markmcfadden@icc-uk.com
Message-ID: <20140123084706.GA25772@laperouse.bortzmeyer.org>
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com> <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 13.10 (saucy)
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 08:47:45 -0000

On Wed, Jan 08, 2014 at 01:18:09PM -0500,
 Suzanne Woolf <suzworldwide@gmail.com> wrote 
 a message of 215 lines which said:

> This new internet-draft is another request for additions to the RFC
> 6761 special names registry, this time motivated by an interest in
> reserving the names most commonly found in recent analysis of TLDs
> in private name spaces. The special names registration would serve
> to minimize the chances of collision between private and public DNS
> namespaces by keeping these names unassigned in the public
> namespace.

I have two technical remarks about this draft (at the end of this
message) and important policy remarks.

1) During the discussion about .onion, .bit and so on, many people on
dnsop were apparently opposed to RFC 6761 (unless the requester was
Apple) and suggested we (the IETF) should not step on ICANN shoes and
do not make an actual use of RFC 6761. What do they think about this
draft?

2) I find no mention of the risk of "reservation through abuse". I
send many requests to many resolvers for "$random.example", then the
root sees a lot of traffic for this TLD, then Interisle flags it as
"hish risk of collisions" then the TLD is added in the special
registry and no longer available. There is nothing about this risk of
"denial of service" in the draft (no Security Considerations) and
nothing about how to prevent it.

3) The suggested behaviour is very demanding: for all the TLD
mentioned, the draft requests that libraries and resolvers treat them
as special. It will mean the modification of a lot of software. If the
goal is only to prevent name collision, delegating these TLD at the
root to AS112 could be sufficient. There is no discussion in the draft
about alternative approaches.

Now the technical remarks:

4) The draft says that libraries and resolvers SHOULD "restrict these
names to local resolution". "Local resolution" is not defined
anywhere. What does it mean? If it means the resolver SHOULD be inside
the organization, how could a library know that 192.0.2.3 is local or
not? Same thing for forwarders of resolvers.

5) The draft says "authoritative domain name server software SHOULD restrict
these names to local resolution and SHOULD NOT allow queries for
strings that use these Special-Use Domain Names to be forwarded to
the public DNS for resolution" I do not understand it at
all. Authoritative name servers are... authoritative, they do not
forward to other servers.


From suzworldwide@gmail.com  Mon Jan 27 11:43:49 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52C161A007C for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2014 11:43:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vWr9rjwukhun for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2014 11:43:46 -0800 (PST)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 425931A024C for <dnsop@ietf.org>; Mon, 27 Jan 2014 11:43:46 -0800 (PST)
Received: by mail-qc0-f174.google.com with SMTP id x13so8524768qcv.5 for <dnsop@ietf.org>; Mon, 27 Jan 2014 11:43:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=lyh/+OocAhJV7OCrU2YmbVNG+J8+BLPnQ2kht8kXX5s=; b=ffSZD7i8WAYq8bP9Juw5prHV5LFkxfJVr4lBcmmw6nEvHUBAkL989TMZsb4/oWUzAP aHez5NbwdGh2P1mA4TW1uJZShVpNmqzGmbfRW+GbadnU/ufy4Jhqc85eDzM16HYfNWWd ek/cDW7zp87ykbpds6Jst6WBHBbS4TRWfsE49EM+XbGX+zeN0I/gIctpJqyAo8lsqWPP fmx/NczFV59P6q4v/7qWy9NQe9zjgKZdYyqmwtVHdDEaRxQrmBGJE+yv+9kv/jY1j9QG jpc59xOg7b1dk8t+4letWqgXbw8xVYMRiTIZssMifbA4UoybTDacp/w59mk3sUEC1Jva 4AGg==
X-Received: by 10.224.87.193 with SMTP id x1mr18224158qal.70.1390851823875; Mon, 27 Jan 2014 11:43:43 -0800 (PST)
Received: from [10.0.0.15] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id u75sm9347950qgd.23.2014.01.27.11.43.42 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Jan 2014 11:43:43 -0800 (PST)
From: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C18FB70F-17C5-49AA-AF6A-02652BC6411D"
Message-Id: <364AE702-56ED-41D6-ACDF-3580539EF5BB@gmail.com>
Date: Mon, 27 Jan 2014 14:43:39 -0500
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [DNSOP] a couple of DNS-related BOFs in London
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:43:49 -0000

--Apple-Mail=_C18FB70F-17C5-49AA-AF6A-02652BC6411D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Colleagues,

We're working on some other updates for London, but these BOFs may be of =
interest, and it certainly sounds like it would be helpful to have =
people knowledgeable about DNS attending. These descriptions are taken =
from the official list at http://trac.tools.ietf.org/bof/trac/wiki; see =
further details there.

best,
Suzanne

DBOUND:

Name: Domain Boundaries (DBound)

Description: Both users and applications make inferences from domain =
names, usually in an effort to make some determination about identity or =
the correct security stance to take. Such inferences, however, are =
usually based on heuristics, rules of thumb, and large static lists =
describing parts of the DNS name space.

The DNS root is expanding rapidly, and the existing mechanisms -- =
primarily the public suffix list (=E2=80=8Bhttp://publicsuffix.org/) and =
related systems -- are unlikely to be sustainable in the medium term. =
Most of the existing mechanisms are managed semi-manually, and there are =
good reasons to suppose that the limits of such management are either =
about to be exceeded, or already have been. Moreover, the existing =
mechanisms are made without regard to the semantics of domain name =
boundaries, and sometimes miss subtle but important parts of those =
semantics (in particular, the public suffix list has sometimes failed to =
take into account so-called empty non-terminals). Perhaps most =
importantly, the public suffix list puts the control of policy =
assertions about a given name outside of the control of the domain =
operator, and in the hands of the operator of the list.
The purpose of this BoF is to identify as completely as we can the cases =
in need of addressing, to identify the necessary lines of work to =
address each case, and to determine whether there is sufficient interest =
and energy to set up a working group to complete that work.


DNSE:

Name: Encryption of DNS requests for confidentiality=20

Description: At the IETF meeting in Vancouver, there have been a lot of =
talk about pervasive monitoring, the attack it is =
(draft-farrell-perpass-attack and draft-barnes-pervasive-problem) and =
the ways to "harden the Internet", to make such mass surveillance more =
difficult and more costly.
Among the protocols that can reveal a lot about the users and their =
activity, the DNS is one of the most widely used =
(draft-bortzmeyer-dnsop-dns-privacy). Existing security solutions (like =
DNSSEC) do not provide confidentiality of the uers's traffic. There have =
been proposals to encrypt DNS requests, to prevent sniffing by a =
third-party, both inside IETF (draft-wijngaards-dnsop-confidentialdns) =
and outside (DNScurve).

Some of the foreseen solutions for DNS confidentiality imply a change in =
the protocol and therefore do no fit well in the existing dnsop working =
group.

So, the idea of the BoF is to start from the problem statements in =
draft-bortzmeyer-dnsop-dns-privacy and =
draft-koch-perpass-dns-confidentiality, and to find out if something can =
be recommended to improve DNS traffic confidentiality against sniffing. =
The recommendation could be an existing solution (such as IPsec) or a =
way to map DNS requests into a general-purpose security solution (such =
as DTLS) or the development a new standard for DNS encryption, possibly =
based on DNScurve/DNScrypt or draft-wijngaards-dnsop-confidentialdns. In =
the last case, it may require a new WG.=20=

--Apple-Mail=_C18FB70F-17C5-49AA-AF6A-02652BC6411D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Colleagues,<div><br></div><div>We're working on some other updates for =
London, but these BOFs may be of interest, and it certainly sounds like =
it would be helpful to have people knowledgeable about DNS attending. =
These descriptions are taken from the official list at <a =
href=3D"http://trac.tools.ietf.org/bof/trac/wiki">http://trac.tools.ietf.o=
rg/bof/trac/wiki</a>; see further details =
there.</div><div><br></div><div>best,</div><div>Suzanne</div><div><br></di=
v><div>DBOUND:</div><div><br></div><div>Name: Domain Boundaries =
(DBound)</div><div><br></div><div>Description: Both users and =
applications make inferences from=20
domain names, usually in an effort to make some determination about=20
identity or the correct security stance to take.  Such inferences,=20
however, are usually based on heuristics, rules of thumb, and large=20
static lists describing parts of the DNS name =
space.</div><div><br></div><div>The DNS root is expanding rapidly, and =
the existing mechanisms -- primarily the public suffix list (<a =
class=3D"ext-link" href=3D"http://publicsuffix.org/"><span =
class=3D"icon">=E2=80=8B</span>http://publicsuffix.org/</a>)
 and related systems -- are unlikely to be sustainable in the medium=20
term.  Most of the existing mechanisms are managed semi-manually, and=20
there are good reasons to suppose that the limits of such management are
 either about to be exceeded, or already have been.  Moreover, the=20
existing mechanisms are made without regard to the semantics of domain=20=

name boundaries, and sometimes miss subtle but important parts of those=20=

semantics (in particular, the public suffix list has sometimes failed to
 take into account so-called empty non-terminals).  Perhaps most=20
importantly, the public suffix list puts the control of policy=20
assertions about a given name outside of the control of the domain=20
operator, and in the hands of the operator of the list.</div><div><p>
The purpose of this BoF is to identify as completely as we can the cases
 in need of addressing, to identify the necessary lines of work to=20
address each case, and to determine whether there is sufficient interest
 and energy to set up a working group to complete that =
work.</p><div><br></div></div><div>DNSE:</div><div><br></div><div>Name: =
Encryption of DNS requests for =
confidentiality&nbsp;</div><div><br></div><div>Description:&nbsp;At the =
IETF meeting in Vancouver, there have been a lot
of talk about pervasive monitoring, the attack it is
(<a href=3D"http://tools.ietf.org/html/draft-farrell-perpass-attack" =
class=3D"wiki">draft-farrell-perpass-attack</a> and <a =
href=3D"http://tools.ietf.org/html/draft-barnes-pervasive-problem" =
class=3D"wiki">draft-barnes-pervasive-problem</a>) and
the ways to "harden the Internet", to make such mass surveillance more
difficult and more costly.</div><div><p>
Among the protocols that can reveal a lot about the users and their
activity, the DNS is one of the most widely used (<a =
href=3D"http://tools.ietf.org/html/draft-bortzmeyer-dnsop-dns-privacy" =
class=3D"wiki">draft-bortzmeyer-dnsop-dns-privacy</a>). Existing
security solutions (like DNSSEC) do not provide confidentiality of the
uers's traffic. There have been proposals to encrypt DNS requests, to
prevent sniffing by a third-party, both inside IETF
(<a =
href=3D"http://tools.ietf.org/html/draft-wijngaards-dnsop-confidentialdns"=
 class=3D"wiki">draft-wijngaards-dnsop-confidentialdns</a>) and outside =
(DNScurve).
</p><p>
Some of the foreseen solutions for DNS confidentiality imply a change
in the protocol and therefore do no fit well in the existing dnsop
working group.
</p><p>
So, the idea of the BoF is to start from the problem statements in
<a href=3D"http://tools.ietf.org/html/draft-bortzmeyer-dnsop-dns-privacy" =
class=3D"wiki">draft-bortzmeyer-dnsop-dns-privacy</a> and
<a =
href=3D"http://tools.ietf.org/html/draft-koch-perpass-dns-confidentiality"=
 class=3D"wiki">draft-koch-perpass-dns-confidentiality</a>, and to find =
out if something
can be recommended to improve DNS traffic confidentiality against
sniffing. The recommendation could be an existing solution (such as
IPsec) or a way to map DNS requests into a general-purpose security
solution (such as DTLS) or the development a new standard for DNS
encryption, possibly based on DNScurve/DNScrypt or
<a =
href=3D"http://tools.ietf.org/html/draft-wijngaards-dnsop-confidentialdns"=
 class=3D"wiki">draft-wijngaards-dnsop-confidentialdns</a>. In the last =
case, it may require a new WG.&nbsp;</p></div></body></html>=

--Apple-Mail=_C18FB70F-17C5-49AA-AF6A-02652BC6411D--

From cheshire@apple.com  Mon Jan 27 20:40:15 2014
Return-Path: <cheshire@apple.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 541B61A016B for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2014 20:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.437
X-Spam-Level: 
X-Spam-Status: No, score=-107.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELsxU7VMlQnY for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2014 20:40:13 -0800 (PST)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 593531A00EE for <dnsop@ietf.org>; Mon, 27 Jan 2014 20:40:13 -0800 (PST)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from relay6.apple.com ([17.128.113.90]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0N0300FD9GYQ3581@mail-out.apple.com> for dnsop@ietf.org; Mon, 27 Jan 2014 20:40:11 -0800 (PST)
X-AuditID: 1180715a-b7f3c6d00000020e-a7-52e734aaaa60
Received: from spicerack.apple.com (spicerack.apple.com [17.128.115.40]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay6.apple.com (Apple SCV relay) with SMTP id 9F.A8.00526.AA437E25; Mon, 27 Jan 2014 20:40:10 -0800 (PST)
Received: from chesh1.apple.com (chesh1.apple.com [17.193.13.41]) by spicerack.apple.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0N0300KI0GYYOB50@spicerack.apple.com> for dnsop@ietf.org; Mon, 27 Jan 2014 20:40:10 -0800 (PST)
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com>
Date: Mon, 27 Jan 2014 20:40:12 -0800
Content-transfer-encoding: quoted-printable
Message-id: <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com>
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com> <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUi2FCsobvK5HmQwbE15hZ331xmcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxqVfN9kLjuhUdM0+wtTAeE6pi5GTQ0LAROLw3x9MELaYxIV7 69m6GLk4hAQmM0n0bH4L5axikni1aT9QFQcHs4CexP2LWiANvEDmzr3bWEFsYYFciWm9y9hA bDYBLYkXn6+A2ZwCthKNixYzg7SyCKhKvH8bCxJmFjjPKDH9SgKErS3x5N0FVoiRNhLTr95i AbGFBEokPq76zAhiiwhoSBya/4Qd4k5ZidPnnrNMYBSYhXDQLCQHzUIydQEj8ypGgaLUnMRK M73EgoKcVL3k/NxNjOCgK4zawdiw3OoQowAHoxIPb0fnsyAh1sSy4srcQ4wSHMxKIrxnpwCF eFMSK6tSi/Lji0pzUosPMUpzsCiJ89o/A0oJpCeWpGanphakFsFkmTg4pRoYAxsCUyU5MuOU 74bEsXDf5Fxjw/350FT/yPVvvt6ZVX2Qt1T4mdruLyJp3ya77GLdNOewdu87qwLDio1WP1Uz BL35q6YIHlc5v+35oV3rbWSddPNcSx90GE/q1V0p6B2mGCwfWLF30VQe6xfbHMqN4xSZPkzY 6iDz/VT9WfGJs7ykVt3tOOGixFKckWioxVxUnAgAViK4PjYCAAA=
Cc: Lyman Chapin <lyman@interisle.net>, Mark McFadden <markmcfadden@icc-uk.com>, Suzanne Woolf <suzworldwide@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 04:40:15 -0000

On 8 Jan, 2014, at 10:18, Suzanne Woolf <suzworldwide@gmail.com> wrote:

> Colleagues,
>=20
> This new internet-draft is another request for additions to the RFC =
6761 special names registry, this time motivated by an interest in =
reserving the names most commonly found in recent analysis of TLDs in =
private name spaces. The special names registration would serve to =
minimize the chances of collision between private and public DNS =
namespaces by keeping these names unassigned in the public namespace.
>=20
> In addition to discussion on the merits of this specific request, I =
would expect the IESG to be interested in any new aspects this request =
brings up to the discussion we were already having on the p2p special =
names draft, and the usability and scalability of the process in RFC =
6761.

I think the goal of the draft is worthy, but there are some details to =
work out:

1. The draft states that eight TLDs are to be designated =93Special =
Use=94, but doesn=92t actually say for any of them *what* the special =
use is. For example, I know what =93localhost=94 means; I know what it =
does and how to use it (it=92s a synonym for 127.0.0.1 and ::1). What is =
=93localdomain=94 and for what would I use it? The intent of RFC 6761 is =
that the seven Domain Name Reservation Considerations are a required =
*part* of any specification that is documenting something that requires =
some special name use, analogous to how all RFC=92s have a =93Security =
Considerations=94 section. But you wouldn=92t write an RFC that was only =
a =93Security Considerations=94 section, and a specification that is =
*only* a =93Domain Name Reservation Considerations=94 section is equally =
lacking. The =93Domain Name Reservation Considerations=94 section is a =
*supplement* to the actual descriptive content of the specification, not =
a *substitute* for it. I apologise that RFC 6761 did not set a good =
precedent in this regard. The examples in RFC 6761, like =93test=94 , =
=93invalid=94 and =93example=94, were all fairly self-evident and =
previously documented elsewhere. In retrospect, RFC 6761 should have =
spelled out more clearly what they are all used for, to set a better =
example to future documents.

2. The actual rules specified in the draft are incorrect. For example, =
for =93.home=94:

   Authors of name resolution APIs and libraries SHOULD restrict these
   names to local resolution and SHOULD NOT allow queries for strings
   that use these Special-Use Domain Names to be forwarded to the
   public DNS for resolution.

Names like =93voyager.home=94 have been used to refer to a user=92s home =
NAT gateway. The user can type =93voyager.home=94 into their web browser =
and connect to their home NAT gateway=92s administration page. If (as =
the draft advocates) the client machine=92s name resolution library =
failed to send the =93voyager.home=94 query to its configured DNS =
server, then this usage would fail.

If we want to formalise the current usage of =93.home=94 rather than =
break it, then I suggest that something more similar to the rules for =
test names would be more appropriate:

6.2.  Domain Name Reservation Considerations for "test."

   The domain "test.", and any names falling within ".test.", are
   special in the following ways:

   1.  Users are free to use these test names as they would any other
       domain names.  However, since there is no central authority
       responsible for use of test names, users SHOULD be aware that
       these names are likely to yield different results on different
       networks.

   2.  Application software SHOULD NOT recognize test names as special,
       and SHOULD use test names as they would other domain names.

   3.  Name resolution APIs and libraries SHOULD NOT recognize test
       names as special and SHOULD NOT treat them differently.  Name
       resolution APIs SHOULD send queries for test names to their
       configured caching DNS server(s).

   4.  Caching DNS servers SHOULD recognize test names as special and
       SHOULD NOT, by default, attempt to look up NS records for them,
       or otherwise query authoritative DNS servers in an attempt to
       resolve test names.  Instead, caching DNS servers SHOULD, by
       default, generate immediate negative responses for all such
       queries.  This is to avoid unnecessary load on the root name
       servers and other name servers.  Caching DNS servers SHOULD offer
       a configuration option (disabled by default) to enable upstream
       resolving of test names, for use in networks where test names are
       known to be handled by an authoritative DNS server in said
       private network.

   5.  Authoritative DNS servers SHOULD recognize test names as special
       and SHOULD, by default, generate immediate negative responses for
       all such queries, unless explicitly configured by the
       administrator to give positive answers for test names.

   6.  DNS server operators SHOULD, if they are using test names,
       configure their authoritative DNS servers to act as authoritative
       for test names.

   7.  DNS Registries/Registrars MUST NOT grant requests to register
       test names in the normal way to any person or entity.  Test names
       are reserved for use in private networks and fall outside the set
       of names available for allocation by registries/registrars.
       Attempting to allocate a test name as if it were a normal DNS
       domain name will probably not work as desired, for reasons 4, 5,
       and 6 above.


Stuart Cheshire=

From ggm@algebras.org  Mon Jan 27 21:15:08 2014
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087431A019B for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2014 21:15:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvHpFx-P_KaL for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2014 21:15:06 -0800 (PST)
Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177]) by ietfa.amsl.com (Postfix) with ESMTP id E430A1A015B for <dnsop@ietf.org>; Mon, 27 Jan 2014 21:15:05 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id at1so7092702iec.36 for <dnsop@ietf.org>; Mon, 27 Jan 2014 21:15:03 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ylAr2vm8w18lFMPLI/qJmm6RlpUFNcImRbvEgatAVdo=; b=ScwFh8gUDzQdLj/XExqiPlIJvhpB4+wlW+1btafrDvg4ddUkiFJtP0Ldsbm2yW06tt mjB7oIBEpCz238mHq6MRaon/0/5BkVfNZ4Gnbwu7L2+IndrdOXFbH5GXCZCcTdapS8Mo hg53DyDhMKXPy+8BcdUx1Nwsf/VPiSWtfe9Wez23/qiQDGgqS97fVHsRdhSKt8y0AIfu WeJErctExjAIqxnVUudqI2SPw5/3fEfQgG97piZDUeggmKtJKrdUaIYHxdYgsfoTDE0u u85ELDTq45w01ZYokExUXFvpHAXWjmqp0aWQl3n6Ra5qBgosxskAEkJ7a8WApaUy1mR0 7gKA==
X-Gm-Message-State: ALoCoQkbgrpi3cjsemUbj6hwok8eOeicDSZJbHX7YXwBy2I+AP888KsR312sbu4f9Fj4b0ZjgbyN
MIME-Version: 1.0
X-Received: by 10.43.153.138 with SMTP id la10mr25035491icc.10.1390886103421;  Mon, 27 Jan 2014 21:15:03 -0800 (PST)
Received: by 10.64.223.47 with HTTP; Mon, 27 Jan 2014 21:15:03 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:55f7:4860:9724:5e4d]
In-Reply-To: <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com>
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com> <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com> <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com>
Date: Tue, 28 Jan 2014 15:15:03 +1000
Message-ID: <CAKr6gn1G3D4Z2RyuSqSpgqT0SY986rBBqhNPYxp1XKieKq+OkQ@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c1d7f41e311c04f100e82a
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 05:15:08 -0000

--001a11c1d7f41e311c04f100e82a
Content-Type: text/plain; charset=ISO-8859-1

I used to get very unhappy when big name IETF attendees would wander into a
room and say "this makes me very uncomfortable" at the mike.

So having said that, and noting I'm nobody special, and certainly not a big
name in IETF, or DNS...

"something about this makes me very uncomfortable"

we are a long way down a path of governance issues in names which makes
reserving a namespace highly politically charged. Look at what .XXX
underwent. Look at the issues around name collisions and potential
interests in names.

I like the aspect that this draft has drawn on observations of what leaks
into the global space, to suggest what might be wise to withhold. thats at
least testable, repeatable.

As to the decisive qualities? I think the IETF could step over a line very
quickly into a place it really doesn't want to be. Inform ICANN? sure. but
decide to formally try and exclude a namespace on technical grounds? Thats
big. That has implications. You'd want to be on remarkably solid ground.

And then theres the future. These are anglo-centric measurements from the
current state. At some future point, one can imagine a language group
embeds a token in name-lookup logic in some domain of activity, and it
winds up hitting the DNS and they come asking for a holdback. Are we tooled
up for that? the I8n side of things.

The jurisdictional qualities around what should or shouldnt be in the DNS
just makes me quake in my boots.

I guess I am going to have to wear come-backs around the "don't over
politicize technology discussions" and "stop trying to have a chilling
effect on a technology discussion" but I have this memory of some very very
cross words being said about .LOCAL a long time ago. and the potential for
value in the real world, and the potential for pain, attempting to reserve
or conserve a label for undoubtedly good technical reasons, in that
context.

BTW, India, Pakistan, South Africa, the Carribean, New Zealand, Australia,
Sri Lanka all understand the word "test" to have a meaning in sports, which
has very high financial value. The assumption the label .TEST has no
financial value in rugby or cricket, when worldwide TV rights negotiate for
billions of dollars seems to me to be .. well.. fraught.

and I can imagine several voices who could capitalize on .LOCAL, your local
supermarket chain amongst them.

--001a11c1d7f41e311c04f100e82a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">I used to get very unhappy when=
 big name IETF attendees would wander into a room and say &quot;this makes =
me very uncomfortable&quot; at the mike.=A0</div><div class=3D"gmail_extra"=
><br>
</div><div class=3D"gmail_extra">So having said that, and noting I&#39;m no=
body special, and certainly not a big name in IETF, or DNS...</div><div cla=
ss=3D"gmail_extra"><br></div><div class=3D"gmail_extra">&quot;something abo=
ut this makes me very uncomfortable&quot;</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">we are a lo=
ng way down a path of governance issues in names which makes reserving a na=
mespace highly politically charged. Look at what .XXX underwent. Look at th=
e issues around name collisions and potential interests in names.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I like the =
aspect that this draft has drawn on observations of what leaks into the glo=
bal space, to suggest what might be wise to withhold. thats at least testab=
le, repeatable.</div>
<div class=3D"gmail_extra"><br>As to the decisive qualities? I think the IE=
TF could step over a line very quickly into a place it really doesn&#39;t w=
ant to be. Inform ICANN? sure. but decide to formally try and exclude a nam=
espace on technical grounds? Thats big. That has implications. You&#39;d wa=
nt to be on remarkably solid ground.</div>
<div class=3D"gmail_extra"><br>And then theres the future. These are anglo-=
centric measurements from the current state. At some future point, one can =
imagine a language group embeds a token in name-lookup logic in some domain=
 of activity, and it winds up hitting the DNS and they come asking for a ho=
ldback. Are we tooled up for that? the I8n side of things.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The jurisdi=
ctional qualities around what should or shouldnt be in the DNS just makes m=
e quake in my boots.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">
I guess I am going to have to wear come-backs around the &quot;don&#39;t ov=
er politicize technology discussions&quot; and &quot;stop trying to have a =
chilling effect on a technology discussion&quot; but I have this memory of =
some very very cross words being said about .LOCAL a long time ago. and the=
 potential for value in the real world, and the potential for pain, attempt=
ing to reserve or conserve a label for undoubtedly good technical reasons, =
in that context.=A0</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">BTW, India,=
 Pakistan, South Africa, the Carribean, New Zealand, Australia, Sri Lanka a=
ll understand the word &quot;test&quot; to have a meaning in sports, which =
has very high financial value. The assumption the label .TEST has no financ=
ial value in rugby or cricket, when worldwide TV rights negotiate for billi=
ons of dollars seems to me to be .. well.. fraught.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">and I can i=
magine several voices who could capitalize on .LOCAL, your local supermarke=
t chain amongst them.</div></div>

--001a11c1d7f41e311c04f100e82a--

From prvs=0098f42702=johnl@iecc.com  Mon Jan 27 21:27:14 2014
Return-Path: <prvs=0098f42702=johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C64E1A0199 for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2014 21:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1VN6p_zyWrE for <dnsop@ietfa.amsl.com>; Mon, 27 Jan 2014 21:27:11 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 25F461A019B for <dnsop@ietf.org>; Mon, 27 Jan 2014 21:27:10 -0800 (PST)
Received: (qmail 99555 invoked from network); 28 Jan 2014 05:27:07 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 28 Jan 2014 05:27:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52e73fab.xn--30v786c.k1401; i=johnl@user.iecc.com; bh=T3q86TUoRlSjZaPB4xeJr8Z6KUYuAmDJLw7Ca/flHTg=; b=ByHoi2gjVDXNT4hTAnh3G+6t0B0cY7E5KWd3rpDQZ8ohzdS6u+X6smmWb9JmJfUL8a7/KAbBnyh4LnEwxBKFNeC9qjPkOTjuN760/hpvbj0UPstI8Q+GSqJgBc6varC9px1hWn1z4G3A8Cm18J5avGVLKhbcT/l+ltWi2yq5wZa+Fa92Nb9xMY/uAFvMi7wy8/IrAxGfx93m8Whq1HHVWadPiWRsSKiA8p8J8n8AokyeXXZ58KgMp8O7U8+DIDyf
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52e73fab.xn--30v786c.k1401; olt=johnl@user.iecc.com; bh=T3q86TUoRlSjZaPB4xeJr8Z6KUYuAmDJLw7Ca/flHTg=; b=thpvuvY0E+c7Mm1WWsG4XmoBtbMjC+TpD7zdAlwlGKpRL6/RREt+CxWPuv9PCHVi+zdOH7PMVFhuQF108Xlok+iaUxtdsEOGE+fU3GorHTec5ohWsUQ4lOdowkUka7dYBF5OMEl3s1ui3LoY7smQ9LGr5WKbLfwKfCtOZ120cN88Sl/E55ezuB+0eKkxfXT+JQIDIecSYGkPPyqbP7drQuLZvM7QtO5DBOddllKAn8TMjNUAKcTz0FnJiWd3iD0c
Date: 28 Jan 2014 05:26:45 -0000
Message-ID: <20140128052645.15660.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: suzworldwide@gmail.com
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 05:27:14 -0000

>This new internet-draft is another request for additions to the RFC 6761 special names registry, this time motivated by an
>interest in reserving the names most commonly found in recent analysis of TLDs in private name spaces.

Several of these names including MAIL, HOME, CORP, and EXCHANGE have
active applications in the ICANN new gTLD round.  Some have such
egregious collisions with existing practice that the applications seem
to be dead, but others such as EXCHANGE aren't.

What, if anything, is the plan for dealing the predictable complaints
from applicants who (not totally unreasonably) would feel that the
rug's been yanked out from under them?

R's,
John

PS: I have some minor technical comments, similar to other people's,
but nothing that's hard to fix if we want to move this ahead.

From jim@rfc1035.com  Tue Jan 28 02:05:56 2014
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399CE1A0361 for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 02:05:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxKlzKdaE33u for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 02:05:54 -0800 (PST)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id BE0D91A023A for <dnsop@ietf.org>; Tue, 28 Jan 2014 02:05:54 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 9E8752421976; Tue, 28 Jan 2014 10:05:48 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <20140128052645.15660.qmail@joyce.lan>
Date: Tue, 28 Jan 2014 10:05:48 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD5E291E-34A0-4AB1-A94A-027848BA553F@rfc1035.com>
References: <20140128052645.15660.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1510)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 10:05:56 -0000

On 28 Jan 2014, at 05:26, John Levine <johnl@taugh.com> wrote:

> What, if anything, is the plan for dealing the predictable complaints
> from applicants who (not totally unreasonably) would feel that the
> rug's been yanked out from under them?

Why would they complain or "have the rug yanked from under them"? [Note =
too that the draft uses SHOULD and not MUST.] Whatever happens with this =
draft is unlikely to have any impact on ICANN's current list of new =
gTLDs. The draft might however become another input into the risk =
mitigation framework that ICANN is now developing. ie There might be =
additional measures in place before .home (say) can proceed to =
delegation. That should not surprise anyone here.


From paul.hoffman@vpnc.org  Tue Jan 28 07:52:07 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738AF1A03CA for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 07:52:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tU7EP5ny56Vr for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 07:52:05 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB3E1A023D for <dnsop@ietf.org>; Tue, 28 Jan 2014 07:52:05 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0SFVlVC001858 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Tue, 28 Jan 2014 08:31:49 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com>
Date: Tue, 28 Jan 2014 07:52:00 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BAF84396-D693-4BE4-A1BF-BB1525AC890D@vpnc.org>
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com> <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com> <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1827)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 15:52:07 -0000

On Jan 27, 2014, at 8:40 PM, Stuart Cheshire <cheshire@apple.com> wrote:

> 1. The draft states that eight TLDs are to be designated =93Special =
Use=94, but doesn=92t actually say for any of them *what* the special =
use is.

It does, but it doesn't call it out very well. It the middle of section =
3, it says that the list is "names that may not be used for top-level =
domains". That is a special use: a label that can be legally used =
everywhere other than at the top level.

> 2. The actual rules specified in the draft are incorrect. For example, =
for =93.home=94:
>=20
>   Authors of name resolution APIs and libraries SHOULD restrict these
>   names to local resolution and SHOULD NOT allow queries for strings
>   that use these Special-Use Domain Names to be forwarded to the
>   public DNS for resolution.
>=20
> Names like =93voyager.home=94 have been used to refer to a user=92s =
home NAT gateway. The user can type =93voyager.home=94 into their web =
browser and connect to their home NAT gateway=92s administration page. =
If (as the draft advocates) the client machine=92s name resolution =
library failed to send the =93voyager.home=94 query to its configured =
DNS server, then this usage would fail.

This document should have the effect you say: allow the query to be sent =
from a host to its configured DNS server. The current wording is wrong.

> If we want to formalise the current usage of =93.home=94 rather than =
break it, then I suggest that something more similar to the rules for =
test names would be more appropriate:
>=20
> 6.2.  Domain Name Reservation Considerations for "test."
>=20
>   The domain "test.", and any names falling within ".test.", are
>   special in the following ways:
>=20
>   1.  Users are free to use these test names as they would any other
>       domain names.  However, since there is no central authority
>       responsible for use of test names, users SHOULD be aware that
>       these names are likely to yield different results on different
>       networks.
>=20
>   2.  Application software SHOULD NOT recognize test names as special,
>       and SHOULD use test names as they would other domain names.
>=20
>   3.  Name resolution APIs and libraries SHOULD NOT recognize test
>       names as special and SHOULD NOT treat them differently.  Name
>       resolution APIs SHOULD send queries for test names to their
>       configured caching DNS server(s).
>=20
>   4.  Caching DNS servers SHOULD recognize test names as special and
>       SHOULD NOT, by default, attempt to look up NS records for them,
>       or otherwise query authoritative DNS servers in an attempt to
>       resolve test names.  Instead, caching DNS servers SHOULD, by
>       default, generate immediate negative responses for all such
>       queries.  This is to avoid unnecessary load on the root name
>       servers and other name servers.  Caching DNS servers SHOULD =
offer
>       a configuration option (disabled by default) to enable upstream
>       resolving of test names, for use in networks where test names =
are
>       known to be handled by an authoritative DNS server in said
>       private network.
>=20
>   5.  Authoritative DNS servers SHOULD recognize test names as special
>       and SHOULD, by default, generate immediate negative responses =
for
>       all such queries, unless explicitly configured by the
>       administrator to give positive answers for test names.
>=20
>   6.  DNS server operators SHOULD, if they are using test names,
>       configure their authoritative DNS servers to act as =
authoritative
>       for test names.
>=20
>   7.  DNS Registries/Registrars MUST NOT grant requests to register
>       test names in the normal way to any person or entity.  Test =
names
>       are reserved for use in private networks and fall outside the =
set
>       of names available for allocation by registries/registrars.
>       Attempting to allocate a test name as if it were a normal DNS
>       domain name will probably not work as desired, for reasons 4, 5,
>       and 6 above.

That seems like a better way to go for all (?) the names in this =
document.

--Paul Hoffman=

From paul.hoffman@vpnc.org  Tue Jan 28 08:05:16 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 722131A026E for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 08:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.647
X-Spam-Level: 
X-Spam-Status: No, score=-3.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HKbBafBUwzfW for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 08:05:14 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by ietfa.amsl.com (Postfix) with ESMTP id 012451A0269 for <dnsop@ietf.org>; Tue, 28 Jan 2014 08:05:13 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0SFhggu002377 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Tue, 28 Jan 2014 08:43:43 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAKr6gn1G3D4Z2RyuSqSpgqT0SY986rBBqhNPYxp1XKieKq+OkQ@mail.gmail.com>
Date: Tue, 28 Jan 2014 08:03:54 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC36E292-C191-43EC-92E1-B75AF371268B@vpnc.org>
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com> <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com> <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com> <CAKr6gn1G3D4Z2RyuSqSpgqT0SY986rBBqhNPYxp1XKieKq+OkQ@mail.gmail.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1827)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 16:05:16 -0000

On Jan 27, 2014, at 9:15 PM, George Michaelson <ggm@algebras.org> wrote:

> I like the aspect that this draft has drawn on observations of what =
leaks into the global space, to suggest what might be wise to withhold. =
thats at least testable, repeatable.
>=20
> As to the decisive qualities? I think the IETF could step over a line =
very quickly into a place it really doesn't want to be. Inform ICANN? =
sure. but decide to formally try and exclude a namespace on technical =
grounds? Thats big. That has implications. You'd want to be on =
remarkably solid ground.

Yes, and this list seems like the most solid ground possible for either =
the IETF or ICANN.

> And then theres the future. These are anglo-centric measurements from =
the current state. At some future point, one can imagine a language =
group embeds a token in name-lookup logic in some domain of activity, =
and it winds up hitting the DNS and they come asking for a holdback.

There is a huge, easily-identifiable difference between adding a token =
*before* the application process that started in 2012 and then later =
asking for a hold-back, and adding it *after*.

> The jurisdictional qualities around what should or shouldnt be in the =
DNS just makes me quake in my boots.

Sure. But re-read section 3 of this draft. This is not "Lyman's and =
Mark's list", it is a list generated by an ICANN standing committee, =
then validated by empirical evidence.

> BTW, India, Pakistan, South Africa, the Carribean, New Zealand, =
Australia, Sri Lanka all understand the word "test" to have a meaning in =
sports, which has very high financial value. The assumption the label =
.TEST has no financial value in rugby or cricket, when worldwide TV =
rights negotiate for billions of dollars seems to me to be .. well.. =
fraught.

The document did not make that assumption. It doesn't talk about finance =
anywhere. For example, there is even financial advantage to owning =
almost any common label and seeing what is returned, even if you cannot =
control what is returned.

--Paul Hoffman=

From paul.hoffman@vpnc.org  Tue Jan 28 08:06:10 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61FDA1A034D for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 08:06:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.647
X-Spam-Level: 
X-Spam-Status: No, score=-3.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mVKkjyabstss for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 08:06:09 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by ietfa.amsl.com (Postfix) with ESMTP id E656E1A027C for <dnsop@ietf.org>; Tue, 28 Jan 2014 08:06:08 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0SFhggv002377 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Tue, 28 Jan 2014 08:44:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140128052645.15660.qmail@joyce.lan>
Date: Tue, 28 Jan 2014 08:04:51 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <88DCC766-224F-4C42-966E-E73202251F38@vpnc.org>
References: <20140128052645.15660.qmail@joyce.lan>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1827)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 16:06:10 -0000

On Jan 27, 2014, at 9:26 PM, John Levine <johnl@taugh.com> wrote:

> What, if anything, is the plan for dealing the predictable complaints
> from applicants who (not totally unreasonably) would feel that the
> rug's been yanked out from under them?

That plan would be for ICANN to design, not us.

--Paul Hoffman

From prvs=009803a606=johnl@taugh.com  Tue Jan 28 08:49:33 2014
Return-Path: <prvs=009803a606=johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8896E1A021B for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 08:49:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LOTS_OF_MONEY=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YDyLrtSep_Kb for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 08:49:32 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CEFC11A0252 for <dnsop@ietf.org>; Tue, 28 Jan 2014 08:49:31 -0800 (PST)
Received: (qmail 93757 invoked from network); 28 Jan 2014 16:49:28 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 28 Jan 2014 16:49:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=5032.52e7df97.k1401; i=johnl%iecc.com@submit.iecc.com; bh=gn9vlXO1nosiJRqknDoRJ6C+Ma5VIgQ2jdqs14iZ1xA=; b=iPz8x9/jAL9iY9iqqdim0WMVrA/MXuKksBHXsF3jyM6RPU5/8wFH+o2vERfbSYYsUoV0MHtYlwZUjYwlzUNyMDKl8gZYZLkVrCLdmJ1svvw5dAHMi6AZbIO1jkaQKjxYrXYGTiqAJqe9VWxRz2GFpGfGcNxm4Bun0usfNzV7XJJEvKyz18F2cAnq7xjDmK6xJCp1M1h2/4+BVyzVkeVNx040n45V7lWGc9XJYhiBpq9S4o6u1pklay/IXGMOc9Dk
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=5032.52e7df97.k1401; olt=johnl%iecc.com@submit.iecc.com; bh=gn9vlXO1nosiJRqknDoRJ6C+Ma5VIgQ2jdqs14iZ1xA=; b=Z73oUGZrDf7sh5KPAXqW5jFbGYP41tDk5/le78VmSUgmUAcYwoEQi32HAx7aisxyomyG12ypzK5IZPKaQ5DUS3rJkH3sQ7nCeP4ijMHp7Grhye6qcmTVNttCleU48wHZOduUk+HNgqL1bwe+h+0zNvyyGrCsXhPB4EEKRURGOWp9bimHzA/yznoQPAzcXo4fKBTck7+lf4cTQZyZfXiXz/N61P2MBTaZuDYZ6iA3t4swP6a3nh/7lY9USR8QC48i
Received: from joyce.lan ([24.59.92.2]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 28 Jan 2014 16:49:27 -0000
Date: 28 Jan 2014 11:49:27 -0500
Message-ID: <alpine.BSF.2.00.1401281147330.27472@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Jim Reid" <jim@rfc1035.com>
In-Reply-To: <AD5E291E-34A0-4AB1-A94A-027848BA553F@rfc1035.com>
References: <20140128052645.15660.qmail@joyce.lan> <AD5E291E-34A0-4AB1-A94A-027848BA553F@rfc1035.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 16:49:33 -0000

>> What, if anything, is the plan for dealing the predictable complaints
>> from applicants who (not totally unreasonably) would feel that the
>> rug's been yanked out from under them?

> Why would they complain or "have the rug yanked from under them"? [Note 
> too that the draft uses SHOULD and not MUST.] Whatever happens with this 
> draft is unlikely to have any impact on ICANN's current list of new 
> gTLDs.

Someone paid $185,000 to apply for .EXCHANGE, which is #567 on the 
priority list.  They haven't signed any contracts yet.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

From lyman@interisle.net  Tue Jan 28 13:56:51 2014
Return-Path: <lyman@interisle.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 707911A034E for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 13:56:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvO0us-PHbAb for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 13:56:49 -0800 (PST)
Received: from mail.shire.net (mail.shire.net [199.102.78.250]) by ietfa.amsl.com (Postfix) with ESMTP id 76DF61A028B for <dnsop@ietf.org>; Tue, 28 Jan 2014 13:56:49 -0800 (PST)
Received: from pool-71-248-175-225.bstnma.fios.verizon.net ([71.248.175.225] helo=[172.24.20.149]) by mail.shire.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from <lyman@interisle.net>) id 1W8GeD-0009Hj-TH; Tue, 28 Jan 2014 14:56:46 -0700
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: Lyman Chapin <lyman@interisle.net>
In-Reply-To: <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com>
Date: Tue, 28 Jan 2014 16:56:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBDA563A-D9C0-4983-8BC9-BF4BADD0B9B9@interisle.net>
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com> <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com> <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com>
To: Stuart Cheshire <cheshire@apple.com>
X-Mailer: Apple Mail (2.1283)
X-SA-Exim-Connect-IP: 71.248.175.225
X-SA-Exim-Mail-From: lyman@interisle.net
X-SA-Exim-Scanned: No (on mail.shire.net); SAEximRunCond expanded to false
Cc: Mark McFadden <markmcfadden@icc-uk.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>, Suzanne Woolf <suzworldwide@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 21:56:51 -0000

On Jan 27, 2014, at 11:40 PM, Stuart Cheshire wrote:

> On 8 Jan, 2014, at 10:18, Suzanne Woolf <suzworldwide@gmail.com> =
wrote:
>=20
>> Colleagues,
>>=20
>> This new internet-draft is another request for additions to the RFC =
6761 special names registry, this time motivated by an interest in =
reserving the names most commonly found in recent analysis of TLDs in =
private name spaces. The special names registration would serve to =
minimize the chances of collision between private and public DNS =
namespaces by keeping these names unassigned in the public namespace.
>>=20
>> In addition to discussion on the merits of this specific request, I =
would expect the IESG to be interested in any new aspects this request =
brings up to the discussion we were already having on the p2p special =
names draft, and the usability and scalability of the process in RFC =
6761.
>=20
> I think the goal of the draft is worthy, but there are some details to =
work out:
>=20
> 1. The draft states that eight TLDs are to be designated =93Special =
Use=94, but doesn=92t actually say for any of them *what* the special =
use is.

Hi Stuart -

The draft was intended to capture existing observed high-volume uses of =
non-delegated TLD names empirically, rather than trying to determine the =
circumstances under which local use of a particular TLD name occurs =
(which might be highly various, depending on the name). Essentially, all =
of these names are proposed for designation as "special use" because =
they are already in widespread "special use" - that is, they are widely =
used as TLDs in name spaces that do not resolve (or do not resolve as =
they were intended to resolve) through the global DNS. I understand that =
this is different from the original intention of RFC 6761, which assumes =
that a name should be reserved for "special use" only when the "special =
use" is well understood and well documented. In this case, the names =
have been observed (see the references in the i-d) in "special use" =
contexts, but the nature of the "special use" in each case is not =
necessarily evident from the data.

The rationale for reserving these names for "special use" is the =
potential for name collision if they are also delegated as resolvable =
entries in the global IANA root, which could disrupt the operation =
and/or compromise the security of networks that are part of the global =
Internet but maintain locally-resolved name spaces. =46rom the IETF =
standpoint, this is an O&M issue. ICANN's interest in selling these =
names to new gTLD applicants is orthogonal to the interest of the IETF =
in ensuring the stability and robustness of the Internet (including the =
DNS) for its users -

- Lyman

> For example, I know what =93localhost=94 means; I know what it does =
and how to use it (it=92s a synonym for 127.0.0.1 and ::1). What is =
=93localdomain=94 and for what would I use it? The intent of RFC 6761 is =
that the seven Domain Name Reservation Considerations are a required =
*part* of any specification that is documenting something that requires =
some special name use, analogous to how all RFC=92s have a =93Security =
Considerations=94 section. But you wouldn=92t write an RFC that was only =
a =93Security Considerations=94 section, and a specification that is =
*only* a =93Domain Name Reservation Considerations=94 section is equally =
lacking. The =93Domain Name Reservation Considerations=94 section is a =
*supplement* to the actual descriptive content of the specification, not =
a *substitute* for it. I apologise that RFC 6761 did not set a good =
precedent in this regard. The examples in RFC 6761, like =93test=94 , =
=93invalid=94 and =93example=94, were all fairly self-evident and =
previously documented elsewhere. In retrospect, RFC 6761 should have =
spelled out more clearly what they are all used for, to set a better =
example to future documents.
>=20
> 2. The actual rules specified in the draft are incorrect. For example, =
for =93.home=94:
>=20
>   Authors of name resolution APIs and libraries SHOULD restrict these
>   names to local resolution and SHOULD NOT allow queries for strings
>   that use these Special-Use Domain Names to be forwarded to the
>   public DNS for resolution.
>=20
> Names like =93voyager.home=94 have been used to refer to a user=92s =
home NAT gateway. The user can type =93voyager.home=94 into their web =
browser and connect to their home NAT gateway=92s administration page. =
If (as the draft advocates) the client machine=92s name resolution =
library failed to send the =93voyager.home=94 query to its configured =
DNS server, then this usage would fail.
>=20
> If we want to formalise the current usage of =93.home=94 rather than =
break it, then I suggest that something more similar to the rules for =
test names would be more appropriate:
>=20
> 6.2.  Domain Name Reservation Considerations for "test."
>=20
>   The domain "test.", and any names falling within ".test.", are
>   special in the following ways:
>=20
>   1.  Users are free to use these test names as they would any other
>       domain names.  However, since there is no central authority
>       responsible for use of test names, users SHOULD be aware that
>       these names are likely to yield different results on different
>       networks.
>=20
>   2.  Application software SHOULD NOT recognize test names as special,
>       and SHOULD use test names as they would other domain names.
>=20
>   3.  Name resolution APIs and libraries SHOULD NOT recognize test
>       names as special and SHOULD NOT treat them differently.  Name
>       resolution APIs SHOULD send queries for test names to their
>       configured caching DNS server(s).
>=20
>   4.  Caching DNS servers SHOULD recognize test names as special and
>       SHOULD NOT, by default, attempt to look up NS records for them,
>       or otherwise query authoritative DNS servers in an attempt to
>       resolve test names.  Instead, caching DNS servers SHOULD, by
>       default, generate immediate negative responses for all such
>       queries.  This is to avoid unnecessary load on the root name
>       servers and other name servers.  Caching DNS servers SHOULD =
offer
>       a configuration option (disabled by default) to enable upstream
>       resolving of test names, for use in networks where test names =
are
>       known to be handled by an authoritative DNS server in said
>       private network.
>=20
>   5.  Authoritative DNS servers SHOULD recognize test names as special
>       and SHOULD, by default, generate immediate negative responses =
for
>       all such queries, unless explicitly configured by the
>       administrator to give positive answers for test names.
>=20
>   6.  DNS server operators SHOULD, if they are using test names,
>       configure their authoritative DNS servers to act as =
authoritative
>       for test names.
>=20
>   7.  DNS Registries/Registrars MUST NOT grant requests to register
>       test names in the normal way to any person or entity.  Test =
names
>       are reserved for use in private networks and fall outside the =
set
>       of names available for allocation by registries/registrars.
>       Attempting to allocate a test name as if it were a normal DNS
>       domain name will probably not work as desired, for reasons 4, 5,
>       and 6 above.
>=20
>=20
> Stuart Cheshire
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From marc.blanchet@viagenie.ca  Tue Jan 28 18:56:58 2014
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7694A1A035E; Tue, 28 Jan 2014 18:56:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJ6Uf0_7_wOc; Tue, 28 Jan 2014 18:56:56 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id D57831A033C; Tue, 28 Jan 2014 18:56:55 -0800 (PST)
Received: from h195.viagenie.ca (h195.viagenie.ca [206.123.31.195]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 9A70B40D17; Tue, 28 Jan 2014 21:56:51 -0500 (EST)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CCD0E480-4C35-4722-9C7A-38ADB49AB9C9"
Date: Tue, 28 Jan 2014 21:56:50 -0500
References: <20140128223101.31170.24891.idtracker@ietfa.amsl.com>
To: apps-discuss@ietf.org, dnsop@ietf.org
Message-Id: <20F732BA-C497-4501-9843-BD2B83DA426A@viagenie.ca>
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
Subject: [DNSOP] Fwd: New Non-WG Mailing List: Dbound -- DNS tree bounds
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 02:56:58 -0000

--Apple-Mail=_CCD0E480-4C35-4722-9C7A-38ADB49AB9C9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

FYI, This new mailing list is to focus the discussion that would lead =
into the dbound BOF in IETF London. Information about the BOF is at: =
http://trac.tools.ietf.org/bof/trac/

Please subscribe.

Regards, Marc.

D=E9but du message r=E9exp=E9di=E9 :

> De: IETF Secretariat <ietf-secretariat@ietf.org>
> Objet: New Non-WG Mailing List: Dbound -- DNS tree bounds
> Date: 28 janvier 2014 17:31:01 HNE
> =C0: IETF Announcement List <ietf-announce@ietf.org>
> Cc: olaf@nlnetlabs.nl, marc.blanchet@viagenie.ca
> R=E9pondre =E0: ietf@ietf.org
>=20
> A new IETF non-working group email list has been created.
>=20
> List address: dbound@ietf.org
> Archive: http://www.ietf.org/mail-archive/web/dbound/
> To subscribe: https://www.ietf.org/mailman/listinfo/dbound
>=20
> Purpose:=20
>=20
> Both users and applications make inferences from domain names, usually=20=

> in an effort to make some determination about identity or the correct=20=

> security stance to take. Such inferences, however, are usually based=20=

> on heuristics, rules of thumb, and large static lists describing parts=20=

> of the DNS name space. The DNS root is expanding rapidly, and the=20
> existing mechanisms -- primarily the public suffix list=20
> (http://publicsuffix.org/) and related systems -- are unlikely to be=20=

> sustainable in the medium term. Most of the existing mechanisms are=20
> managed semi-manually, and there are good reasons to suppose that the=20=

> limits of such management are either about to be exceeded, or already=20=

> have been. Moreover, the existing mechanisms are made without regard=20=

> to the semantics of domain name boundaries, and sometimes miss subtle=20=

> but important parts of those semantics (in particular, the public=20
> suffix list has sometimes failed to take into account so-called empty=20=

> non-terminals). Perhaps most importantly, the public suffix list puts=20=

> the control of policy assertions about a given name outside of the=20
> control of the domain operator, and in the hands of the operator of=20
> the list.=20
>=20
> The purpose of this mailing list is to discuss this issue and to=20
> identify as completely as we can the cases in need of addressing, to=20=

> identify the necessary lines of work to address each case, and to=20
> determine whether there is sufficient interest and energy to set up a=20=

> working group to complete that work.
>=20
> For additional information, please contact the list administrators.


--Apple-Mail=_CCD0E480-4C35-4722-9C7A-38ADB49AB9C9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">FYI, =
This new mailing list is to focus the discussion that would lead into =
the dbound BOF in IETF London. Information about the BOF is at:&nbsp;<a =
href=3D"http://trac.tools.ietf.org/bof/trac/">http://trac.tools.ietf.org/b=
of/trac/</a><div><br></div><div>Please =
subscribe.<div><br></div><div>Regards, Marc.<br><div><br><div>D=E9but du =
message r=E9exp=E9di=E9 :</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; color:rgba(0, =
0, 0, 1.0);"><b>De: </b></span><span =
style=3D"font-family:'Helvetica';">IETF Secretariat &lt;<a =
href=3D"mailto:ietf-secretariat@ietf.org">ietf-secretariat@ietf.org</a>&gt=
;<br></span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Objet: =
</b></span><span style=3D"font-family:'Helvetica';"><b>New Non-WG =
Mailing List: Dbound -- DNS tree bounds</b><br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; color:rgba(0, =
0, 0, 1.0);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica';">28 janvier 2014 17:31:01 =
HNE<br></span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>=C0: =
</b></span><span style=3D"font-family:'Helvetica';">IETF Announcement =
List &lt;<a =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>&gt;<br><=
/span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Cc: =
</b></span><span style=3D"font-family:'Helvetica';"><a =
href=3D"mailto:olaf@nlnetlabs.nl">olaf@nlnetlabs.nl</a>, <a =
href=3D"mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a><br=
></span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>R=E9pondre=
 =E0: </b></span><span style=3D"font-family:'Helvetica';"><a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br></span></div><br><div>A=
 new IETF non-working group email list has been created.<br><br>List =
address: <a =
href=3D"mailto:dbound@ietf.org">dbound@ietf.org</a><br>Archive: <a =
href=3D"http://www.ietf.org/mail-archive/web/dbound/">http://www.ietf.org/=
mail-archive/web/dbound/</a><br>To subscribe: <a =
href=3D"https://www.ietf.org/mailman/listinfo/dbound">https://www.ietf.org=
/mailman/listinfo/dbound</a><br><br>Purpose: <br><br>Both users and =
applications make inferences from domain names, usually <br>in an effort =
to make some determination about identity or the correct <br>security =
stance to take. Such inferences, however, are usually based <br>on =
heuristics, rules of thumb, and large static lists describing parts =
<br>of the DNS name space. The DNS root is expanding rapidly, and the =
<br>existing mechanisms -- primarily the public suffix list <br>(<a =
href=3D"http://publicsuffix.org/">http://publicsuffix.org/</a>) and =
related systems -- are unlikely to be <br>sustainable in the medium =
term. Most of the existing mechanisms are <br>managed semi-manually, and =
there are good reasons to suppose that the <br>limits of such management =
are either about to be exceeded, or already <br>have been. Moreover, the =
existing mechanisms are made without regard <br>to the semantics of =
domain name boundaries, and sometimes miss subtle <br>but important =
parts of those semantics (in particular, the public <br>suffix list has =
sometimes failed to take into account so-called empty =
<br>non-terminals). Perhaps most importantly, the public suffix list =
puts <br>the control of policy assertions about a given name outside of =
the <br>control of the domain operator, and in the hands of the operator =
of <br>the list. <br><br>The purpose of this mailing list is to discuss =
this issue and to <br>identify as completely as we can the cases in need =
of addressing, to <br>identify the necessary lines of work to address =
each case, and to <br>determine whether there is sufficient interest and =
energy to set up a <br>working group to complete that work.<br><br>For =
additional information, please contact the list =
administrators.<br></div></blockquote></div><br></div></div></body></html>=

--Apple-Mail=_CCD0E480-4C35-4722-9C7A-38ADB49AB9C9--

From cheshire@apple.com  Tue Jan 28 19:41:37 2014
Return-Path: <cheshire@apple.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D04871A0366 for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 19:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.437
X-Spam-Level: 
X-Spam-Status: No, score=-107.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1iuqaiC6Wpzh for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 19:41:36 -0800 (PST)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2D6D71A0236 for <dnsop@ietf.org>; Tue, 28 Jan 2014 19:41:36 -0800 (PST)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from relay8.apple.com ([17.128.113.102]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0N050010H8X9N5F1@mail-out.apple.com> for dnsop@ietf.org; Tue, 28 Jan 2014 19:41:33 -0800 (PST)
X-AuditID: 11807166-b7f0b6d00000380b-5d-52e8786d3371
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay8.apple.com (Apple SCV relay) with SMTP id D6.8E.14347.D6878E25; Tue, 28 Jan 2014 19:41:33 -0800 (PST)
Received: from [17.153.21.32] (unknown [17.153.21.32]) by koseret.apple.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0N0500KB68X8NR50@koseret.apple.com> for dnsop@ietf.org; Tue, 28 Jan 2014 19:41:33 -0800 (PST)
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <BAF84396-D693-4BE4-A1BF-BB1525AC890D@vpnc.org>
Date: Tue, 28 Jan 2014 19:41:31 -0800
Content-transfer-encoding: quoted-printable
Message-id: <0915A36B-F411-45F0-BD56-23A2745F434C@apple.com>
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com> <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com> <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com> <BAF84396-D693-4BE4-A1BF-BB1525AC890D@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1827)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUiON1OXTe34kWQwb7nYhZ331xmcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxvGVDSwFD4QrLj+/x9jA+J6/i5GTQ0LAROLTkfMsELaYxIV7 69m6GLk4hARamCR2v7wB5cxhkri/uJO9i5GDg1lAT+L+RS2QBl4gc+O82cwgtrBArsS03mVs IDabgJbEi89XwGxOARuJeQv+gtWwCKhKbL8+AyzOLKAhcfzKGXYIW1viybsLrBAzbSRebXzI ArH3JqPE6jWHGUESIkANFx7uALtBQkBWYv7p0gmMArMQLpqF5KJZSKYuYGRexShQlJqTWGmh l1hQkJOql5yfu4kRFHYNhWk7GJuWWx1iFOBgVOLhXXHxeZAQa2JZcWXuIUYJDmYlEd7pki+C hHhTEiurUovy44tKc1KLDzFKc7AoifM6PHsWJCSQnliSmp2aWpBaBJNl4uCUamDsv/Zt7p0G vWqbu6kndv5azX4nU6TsoKJxZ69o+6xXXlJfuYQVbgvtyq10SlcwlDEvvvXsyuf+T3vmdn/a Hrinmovp8HxfqyNVPzT7b/aapq3UsZnSXrB53VKHPYpiS4/pcSbks+SkCJebz/7zhPXVh5Vu 6hPXacgJXVlys8hvb9Yitidyk3qVWIozEg21mIuKEwH7+v86NwIAAA==
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 03:41:38 -0000

On 28 Jan, 2014, at 07:52, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> It does, but it doesn't call it out very well. It the middle of =
section 3, it says that the list is =93names that may not be used for =
top-level domains".

That doesn=92t describe what the labels are used for. It describes what =
they may *not* be used for. What they *are* used for remains =
unspecified.

If the user types =93www.host=94 into their web browser, the name should =
*not* be resolved in the global DNS. I get that. But what *should* =
happen with that name? Should it result in NXDOMAIN, like =93www.invalid=94=
? Should it result in 127.0.0.1 like =93localhost=94 does? Resolved via =
mDNS, like =93www.local=94? Something else? I have no idea. If it=92s =
the same as one of the other existing special-use TLDs, then an argument =
needs to be made as to why we need another reserved special-use TLD that =
duplicates the functionality of an existing one. These names are not =
supposed to be vanity names. The special-use names are there to trigger =
special behavior by software, and as such we probably don=92t need more =
than one way to trigger each particular special behavior.

The current use of various de facto reserved names like =93.onion=94 =
results from there being no formal IETF mechanism for documenting and =
discussing such uses.

The goal of RFC 6761 was to remedy this omission, and give people who =
feel they need such names a process to apply for such names and initiate =
discussion about whether such use is appropriate. That way the IETF =
community can be involved with these decisions about how names are used, =
instead of it happening outside the IETF with no IETF scrutiny or input.

I think it would be fairly easy to produce a draft documenting what =
=93.onion=94 is for, how it works, and why resolving those names via the =
conventional DNS is not appropriate. I=92d love to see a draft like that =
from one of the people who understands the details.

For some of the other names I don=92t know what those documents would =
say. If people in the IETF community do know what those names are used =
for, having those people write and submit a quick two-page draft =
describing the usage would be a wonderful contribution to greater IETF =
understanding of what=92s going on. Observing that certain weird names =
are hitting the root name servers is a useful first step. Understanding =
*why* that=92s happening would be even better.

Stuart Cheshire


From cheshire@apple.com  Tue Jan 28 19:47:52 2014
Return-Path: <cheshire@apple.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558E91A0366 for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 19:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.437
X-Spam-Level: 
X-Spam-Status: No, score=-107.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mByVXnJwb93n for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 19:47:51 -0800 (PST)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5601A0236 for <dnsop@ietf.org>; Tue, 28 Jan 2014 19:47:51 -0800 (PST)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from relay4.apple.com ([17.128.113.87]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0N0500CYU97G8HL1@mail-out.apple.com> for dnsop@ietf.org; Tue, 28 Jan 2014 19:47:48 -0800 (PST)
X-AuditID: 11807157-b7ff46d000001540-37-52e879e41c22
Received: from kencur (kencur.apple.com [17.151.62.38]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay4.apple.com (Apple SCV relay) with SMTP id 23.E9.05440.4E978E25; Tue, 28 Jan 2014 19:47:48 -0800 (PST)
Received: from [17.153.21.32] (unknown [17.153.21.32]) by kencur.apple.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0N05002ZL97OW540@kencur.apple.com> for dnsop@ietf.org; Tue, 28 Jan 2014 19:47:48 -0800 (PST)
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <DBDA563A-D9C0-4983-8BC9-BF4BADD0B9B9@interisle.net>
Date: Tue, 28 Jan 2014 19:47:47 -0800
Content-transfer-encoding: quoted-printable
Message-id: <E7C51A3E-1F2A-4327-A9C7-E0832A265184@apple.com>
References: <20140108151128.10496.10303.idtracker@ietfa.amsl.com> <EF33329A-2895-4714-8DC1-2E103EF484D9@gmail.com> <2C2D7CBD-98A6-448A-98AD-6E0A1B6B07A1@apple.com> <DBDA563A-D9C0-4983-8BC9-BF4BADD0B9B9@interisle.net>
To: Lyman Chapin <lyman@interisle.net>
X-Mailer: Apple Mail (2.1827)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUiON1OTfdJ5Ysgg545OhZ331xmcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRsuWw0wFC9grjqwuamB8xtrFyMkhIWAisbH1LpQtJnHh3nq2 LkYuDiGBJiaJhgXHWSCcWUwSB6btAnI4OJgF9CTuX9QCaeAFMjfOm80MYgsL5EpM613GBmKz CWhJvPh8hQ2knFPAUeLnFTuQMIuAqsSPizvA5jMLrGOU2HPtFyNIgllAW+LJuwusEDNtJCZ0 nIE64h6jxMdZ68EWiAioSVye+AHsBgkBWYn5p0snMArMQrhoFpKLZiGZuoCReRWjQFFqTmKl iV5iQUFOql5yfu4mRlDQNRSG72D8t8zqEKMAB6MSD++Ki8+DhFgTy4orcw8xSnAwK4nwTpd8 ESTEm5JYWZValB9fVJqTWnyIUZqDRUmc1+7ZsyAhgfTEktTs1NSC1CKYLBMHp1QDo5zThzuz XD3397xTzb9fFWebFzB1o2hgnZNEeeFR6Zd6vGuuHKz7cHPFpOdXukP//Zdcnj5rl/Wp0MLW gx5llgsYQ3zk9lWlzL3zaucHSeNX7QmyR1Oc9VyPbVqdribya8LdRywut38GtW5iiF+8bZZy jWYB/7RdcxeolUgun3y9crp3eZ+8kxJLcUaioRZzUXEiAD02oxk2AgAA
Cc: Mark McFadden <markmcfadden@icc-uk.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>, Suzanne Woolf <suzworldwide@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 03:47:52 -0000

On 28 Jan, 2014, at 13:56, Lyman Chapin <lyman@interisle.net> wrote:

> Hi Stuart -
>=20
> The draft was intended to capture existing observed high-volume uses =
of non-delegated TLD names empirically, rather than trying to determine =
the circumstances under which local use of a particular TLD name occurs =
(which might be highly various, depending on the name).

That=92s a laudable contribution, thank you.

I believe that with the considerable sleuthing abilities of the IETF =
community, we ought to be able to take this initial set of observed data =
and treat it as a call to action for the IETF community, for someone to =
step forward and tell us *why* those names are in use, are leaking out =
to the root name servers, and what the intended use is for these names. =
(I assume that =93leaking out to the root name servers and getting =
NXDOMAIN=94 is *not* the intended use.)

Stuart Cheshire


From prvs=00995a0cdf=johnl@iecc.com  Tue Jan 28 21:55:07 2014
Return-Path: <prvs=00995a0cdf=johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B89A01A0280 for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 21:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ScRpbel10yf for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 21:55:06 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 21C2F1A0193 for <dnsop@ietf.org>; Tue, 28 Jan 2014 21:55:05 -0800 (PST)
Received: (qmail 73226 invoked from network); 29 Jan 2014 05:55:02 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 29 Jan 2014 05:55:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52e897b6.xn--9vv.k1401; i=johnl@user.iecc.com; bh=Sa/ErOPWv4YLrzOlgx12YvrmLQJN7IiRLICYgzuUMa4=; b=dERrP36fA90W8/xiNgNrR00YTnxR7pKQ4KgEvffSvYheI7f6FbK3kIabmhJ5ERz41o0H4DL0+q2hZ7UocHsS1tTqYg+GRHqyS0OgT7d3qd0snJuGJ0Y2Y7DTscsQ96hJTX3iW7iaj9P4aOijRZmiR7pVe2H/xvMPUhOj7r7oZzERrfzXMKIECBj0JjXr2RvKaxlr2DtUbvGs+Db2rh7kOinUKqVJSlx0D+0+Ne00664E4UrN4tndAohJsC7Fd0x7
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52e897b6.xn--9vv.k1401; olt=johnl@user.iecc.com; bh=Sa/ErOPWv4YLrzOlgx12YvrmLQJN7IiRLICYgzuUMa4=; b=aDPaRe3q5w5ZJK2JEZZtsLrR4Oq6/qlfsNQJvZAgw8k96I+GY0zuOXdWpBEGsHOtMt5Yxt86K/trG5gpd+dk3kwXI0fgKf1TJnrf5FcaWPKhEPDNvYtoFt8sBkBf7Jt251vPTg9iNm8je7tTS/SW5Xgus598r1DA+2DF/ee+3RMAaVVG2reT+fSPgfrlRYyTCR0td6uLFaYSpFoQM8aUQsMi32Njc+9SiSr8Cv94iMYmdUDIIVVPQd3IcO+iA313
Date: 29 Jan 2014 05:54:38 -0000
Message-ID: <20140129055438.2402.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <E7C51A3E-1F2A-4327-A9C7-E0832A265184@apple.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: cheshire@apple.com
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 05:55:07 -0000

>I believe that with the considerable sleuthing abilities of the IETF
>community, we ought to be able to take this initial set of observed data
>and treat it as a call to action for the IETF community, for someone to
>step forward and tell us *why* those names are in use, are leaking out
>to the root name servers, and what the intended use is for these names.

Um, we already know.  They're used to name things on private networks,
often behind a NAT, and they leak out for random not particularly
interesting reasons, such as people taking their laptops on trips
which then look for the printer that lives on their office LAN when
they're connected to the wifi at a coffee shop.

On my home network I have a couple of dozen hosts, what with all the
networked printers, phones, tablets, laptops, and so forth, and
because I am a lazy guy, I give them names like kindle.lan rather than
longer global names.  My local DNS cache resolves those names to
addresses in 192.168/16.  I think that's pretty typical of small
business networks.  It's useful, but I don't see anything worth
standardizing other than don't resolve .LAN on the global Internet.

R's,
John



From paul.hoffman@vpnc.org  Wed Jan 29 07:21:31 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1271A03D5 for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 07:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krfpdoeYFymv for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 07:21:30 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id F198B1A028A for <dnsop@ietf.org>; Wed, 29 Jan 2014 07:21:29 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0TF1COe043719 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Wed, 29 Jan 2014 08:01:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140129055438.2402.qmail@joyce.lan>
Date: Wed, 29 Jan 2014 07:21:26 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5B0F7E9-E638-4666-AD84-CE3526FE0A74@vpnc.org>
References: <20140129055438.2402.qmail@joyce.lan>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1827)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 15:21:31 -0000

On Jan 28, 2014, at 9:54 PM, John Levine <johnl@taugh.com> wrote:

>> I believe that with the considerable sleuthing abilities of the IETF
>> community, we ought to be able to take this initial set of observed =
data
>> and treat it as a call to action for the IETF community, for someone =
to
>> step forward and tell us *why* those names are in use, are leaking =
out
>> to the root name servers, and what the intended use is for these =
names.
>=20
> Um, we already know.  They're used to name things on private networks,
> often behind a NAT, and they leak out for random not particularly
> interesting reasons, such as people taking their laptops on trips
> which then look for the printer that lives on their office LAN when
> they're connected to the wifi at a coffee shop.

All that, plus "on their corporate network, there are search lists that =
allow shortened names; when they take their laptop off that network, =
they try to type in the shortened name".

--Paul Hoffman=

From dns@fl1ger.de  Wed Jan 29 07:47:28 2014
Return-Path: <dns@fl1ger.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2B41A024E for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 07:47:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Yin6AuMrXql for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 07:47:26 -0800 (PST)
Received: from nox.guxx.net (nox.guxx.net [78.46.109.173]) by ietfa.amsl.com (Postfix) with ESMTP id 45A6A1A0216 for <dnsop@ietf.org>; Wed, 29 Jan 2014 07:47:26 -0800 (PST)
Received: by nox.guxx.net (Postfix, from userid 65534) id A818CDB830B; Wed, 29 Jan 2014 16:47:22 +0100 (CET)
Received: from porcupinetree.ddns.nominum.com (PorcupineTree.ddns.nominum.com [64.89.225.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nox.guxx.net (Postfix) with ESMTPSA id 17DF2DB811B; Wed, 29 Jan 2014 16:47:20 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ralf Weber <dns@fl1ger.de>
In-Reply-To: <20140129055438.2402.qmail@joyce.lan>
Date: Wed, 29 Jan 2014 07:47:18 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de>
References: <20140129055438.2402.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1827)
Cc: cheshire@apple.com, "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 15:47:28 -0000

Moin!

On 28 Jan 2014, at 21:54, John Levine <johnl@taugh.com> wrote:
> On my home network I have a couple of dozen hosts, what with all the
> networked printers, phones, tablets, laptops, and so forth, and
> because I am a lazy guy, I give them names like kindle.lan rather than
> longer global names.  My local DNS cache resolves those names to
> addresses in 192.168/16.  I think that's pretty typical of small
> business networks.  It's useful, but I don't see anything worth
> standardizing other than don't resolve .LAN on the global Internet.
Where shall this stop? How about .LOKALESNETZWERK (german for .LAN). 
How many domains do we want to treat special? I know this draft only
asks for 8, but some of them are on ICANNs application list.

You setup clearly does something the global DNS namespace was not
intended to do and while I know that this is very common (I worked
in companies that used .companyname) it is not intended to be used
in the global DNS namespace. So the results what happens to this
queries is undefined. That is your problem. We should not make
it (although we already did in some way) make it Internet community
problem.

I also don't think there are risks in delegation these other than
the applicants will get lots of traffic. If devices get an record
back or NXDomain doesn't matter in most cases. We already have seen 
that. We have ISPs  or hotels do NXDomain redirection and some do
it not very intelligent (the redirect every query). While we have
lots of reports that this is bad the world has not fallen over. 
People moved along.

So long
-Ralf



From paul.hoffman@vpnc.org  Wed Jan 29 08:11:04 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 849EB1A036B for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 08:11:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpv5Oh0cgXbV for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 08:10:58 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id E616D1A02C8 for <dnsop@ietf.org>; Wed, 29 Jan 2014 08:10:56 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0TFoarP045218 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 Jan 2014 08:50:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de>
Date: Wed, 29 Jan 2014 08:10:50 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de>
To: Ralf Weber <dns@fl1ger.de>
X-Mailer: Apple Mail (2.1827)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:11:05 -0000

On Jan 29, 2014, at 7:47 AM, Ralf Weber <dns@fl1ger.de> wrote:

> Where shall this stop?

=46rom my earlier message:

> There is a huge, easily-identifiable difference between adding a token =
*before* the application process that started in 2012 and then later =
asking for a hold-back, and adding it *after*.

All names in draft-chapin-additional-reserved-tlds were in widespread =
use before the application process. If someone wants to start using a =
new TLD now, they know where to go ask for it.

> I also don't think there are risks in delegation these other than
> the applicants will get lots of traffic.

Others disagree. ICANN has documented many scenarios where there are =
security problems when what was earlier expected to either get local =
resolution or an NXDOMAIN starts getting real answers.

--Paul Hoffman=

From dns@fl1ger.de  Wed Jan 29 08:40:47 2014
Return-Path: <dns@fl1ger.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62BC51A0356 for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 08:40:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_64=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ORue9HjfmKTq for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 08:40:45 -0800 (PST)
Received: from nox.guxx.net (nox.guxx.net [78.46.109.173]) by ietfa.amsl.com (Postfix) with ESMTP id B61821A02F2 for <dnsop@ietf.org>; Wed, 29 Jan 2014 08:40:45 -0800 (PST)
Received: by nox.guxx.net (Postfix, from userid 65534) id 6F18BDB830B; Wed, 29 Jan 2014 17:40:42 +0100 (CET)
Received: from porcupinetree.ddns.nominum.com (PorcupineTree.ddns.nominum.com [64.89.225.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nox.guxx.net (Postfix) with ESMTPSA id C595CDB811B; Wed, 29 Jan 2014 17:40:40 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ralf Weber <dns@fl1ger.de>
In-Reply-To: <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org>
Date: Wed, 29 Jan 2014 08:40:38 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1827)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:40:47 -0000

Moin!

On 29 Jan 2014, at 08:10, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>> There is a huge, easily-identifiable difference between adding a =
token *before* the application process that started in 2012 and then =
later asking for a hold-back, and adding it *after*.
>=20
> All names in draft-chapin-additional-reserved-tlds were in widespread =
use before the application process. If someone wants to start using a =
new TLD now, they know where to go ask for it.
That they where in use before the new GTLD process doesn't change the =
fact that they were not supposed to be asked on the global DNS =
namespace.

>> I also don't think there are risks in delegation these other than
>> the applicants will get lots of traffic.
>=20
> Others disagree. ICANN has documented many scenarios where there are =
security problems when what was earlier expected to either get local =
resolution or an NXDOMAIN starts getting real answers.
By risks I meant risks to the Internet as a whole. There surely is a =
security problem when you answer with an A record where you before gave =
back NXDomain for the person doing that. But that hasn't stopped people =
deploying NXDomain redirections and again the real problem is that you =
are using something in the global name space that is not supposed to be =
there. There are other uses of DNS where giving out an record instead of =
NXDomain has security implications (NXR redirections, fat finger =
domains, searchlists) and none of them have been treated special here. =
Also there are IMHO currently other more pressing security issues with =
the Internet than people getting an A record back for router.home.

So long
-Ralf


From jabley@hopcount.ca  Wed Jan 29 10:12:17 2014
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF6E1A029B for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 10:12:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6m5k_eKOFbQP for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 10:12:11 -0800 (PST)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id CD98B1A0230 for <dnsop@ietf.org>; Wed, 29 Jan 2014 10:12:11 -0800 (PST)
Received: by mail-ig0-f181.google.com with SMTP id j1so5229061iga.2 for <dnsop@ietf.org>; Wed, 29 Jan 2014 10:12:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=9tvDl6T7YYorEUGo8o/cFYxKLfvCojev4VE2Cv+dPM8=; b=GN3fX78WXLz4VMiV/DyXo897tkgBBjTn5+IkM9wPFTlnaHl1xt2DO1kLqXdAIdNUz3 b50mM6HsCULt0kOmbAIi25zYIIMrOzoxeHaKzeyVAi20fDoqA4Dnu0YNFL69/ood37Xl i4XSvTbgPHOiG3XZxRjt6Ongf/LIOvDwKwNpM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=9tvDl6T7YYorEUGo8o/cFYxKLfvCojev4VE2Cv+dPM8=; b=RDeDLYlyU6tWzhO6oLYBVeNUqAhQDdBdOjx7EaPkMSeU7tJUJvK1uySCsX4+PRK0b2 Fb2mlSZ21YJDI1rSwa4GMwyDi8U27mJn37O72Feqs2wnWhZjJcKgHCUm7WRqeBc679+1 Tek3AAMlkPl21Urt3lw0VisDKT9gNrAe86uLs0qk83wVNcK+R2auCwAmO51LI9V51K3V FAqvEhaNM71XeiyeBAlkI+PuEUqgiimocb5gb67aI8Aio/OtL6nUtinKFnbeU56sHarq H9cqCLrEhDMeiqHMaZHOhjYF8kUYDS543lw8tgnN7lQSPKLbM3CyCztsq78L+74iXRlb 1Fsg==
X-Gm-Message-State: ALoCoQnmpBZze26sGsvS4d0OnauCbc6WPZQRgqPZ4nFkneE1DMiA1UcifMtRQ6BiyQS+xF/s7wL9
X-Received: by 10.50.43.162 with SMTP id x2mr30210307igl.39.1391018824553; Wed, 29 Jan 2014 10:07:04 -0800 (PST)
Received: from [199.212.90.57] (24-52-234-221.cable.teksavvy.com. [24.52.234.221]) by mx.google.com with ESMTPSA id s4sm78796075ige.0.2014.01.29.10.07.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Jan 2014 10:07:03 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_7143F834-75DA-48C1-9F9C-07E311B3B9EB"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de>
Date: Wed, 29 Jan 2014 13:07:01 -0500
Message-Id: <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de>
To: Ralf Weber <dns@fl1ger.de>
X-Mailer: Apple Mail (2.1827)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 18:12:17 -0000

--Apple-Mail=_7143F834-75DA-48C1-9F9C-07E311B3B9EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 2014-01-29, at 11:40, Ralf Weber <dns@fl1ger.de> wrote:

> On 29 Jan 2014, at 08:10, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>>> I also don't think there are risks in delegation these other than
>>> the applicants will get lots of traffic.
>>=20
>> Others disagree. ICANN has documented many scenarios where there are =
security problems when what was earlier expected to either get local =
resolution or an NXDOMAIN starts getting real answers.
> By risks I meant risks to the Internet as a whole.

A risk to the Internet as a whole is that a fragmented namespace (.LAN =
means something different in John's office than it does at the cafe next =
door; .HOME meaning something different to the thirty million =
subscribers of ISP X than it does to others) will restrict communication =
by name between endpoints on the Internet, and changes the fundamental =
assumptions on which protocols and applications rely to an extent that =
is potentially unbounded.

This is the end-to-end principle wearing a DNS t-shirt (the IP t-shirt =
was all cut up by a hundred million NATs, and is no good when it's cold =
out).

The trouble here is not recognising that namespace collisions are bad; =
it's (a) deciding where to draw the line between "bad" and "good enough" =
and (b) dealing with the political headaches of "use it, measure it, =
reserve it at the IETF" which costs $0 and "follow the ICANN new gTLD =
applicant guidebook" which costs substantially more.


Joe


--Apple-Mail=_7143F834-75DA-48C1-9F9C-07E311B3B9EB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlLpQ0UACgkQNI8MvYZSOixArwCgwSSNFgnWuS4eWYyPFpbKM9ee
o18AoKqJ4YsbLRbuzx+lJOJVF1AbcLOZ
=S5DW
-----END PGP SIGNATURE-----

--Apple-Mail=_7143F834-75DA-48C1-9F9C-07E311B3B9EB--

From dns@fl1ger.de  Wed Jan 29 10:45:57 2014
Return-Path: <dns@fl1ger.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B6A01A021B for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 10:45:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mr8vmcIOsaQW for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 10:45:54 -0800 (PST)
Received: from nox.guxx.net (nox.guxx.net [78.46.109.173]) by ietfa.amsl.com (Postfix) with ESMTP id BCAE81A03D4 for <dnsop@ietf.org>; Wed, 29 Jan 2014 10:45:50 -0800 (PST)
Received: by nox.guxx.net (Postfix, from userid 65534) id 1BD3CDB830E; Wed, 29 Jan 2014 19:45:47 +0100 (CET)
Received: from porcupinetree.ddns.nominum.com (PorcupineTree.ddns.nominum.com [64.89.225.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nox.guxx.net (Postfix) with ESMTPSA id BE821DB811B; Wed, 29 Jan 2014 19:45:44 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset=us-ascii
From: Ralf Weber <dns@fl1ger.de>
In-Reply-To: <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca>
Date: Wed, 29 Jan 2014 10:45:40 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1827)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 18:45:57 -0000

Moin!

On 29 Jan 2014, at 10:07, Joe Abley <jabley@hopcount.ca> wrote:
> A risk to the Internet as a whole is that a fragmented namespace (.LAN =
means something different in John's office than it does at the cafe next =
door; .HOME meaning something different to the thirty million =
subscribers of ISP X than it does to others) will restrict communication =
by name between endpoints on the Internet, and changes the fundamental =
assumptions on which protocols and applications rely to an extent that =
is potentially unbounded.
1. The fragmented name space is a reality and has been for some time =
(dns split horizon search on google reveals 500k pages)
2. If endpoints use proper globally registered DNS names they will be =
able to communicate. If they use something else the behaviour is =
undefined.
I think there is more value in thinking about how we can integrate local =
and global naming than in trying to protect people by not allowing =
something to not be registered in the global name space.

> This is the end-to-end principle wearing a DNS t-shirt (the IP t-shirt =
was all cut up by a hundred million NATs, and is no good when it's cold =
out).
I don't think the DNS t-shirt looks better.

> The trouble here is not recognising that namespace collisions are bad; =
it's (a) deciding where to draw the line between "bad" and "good enough" =
and (b) dealing with the political headaches of "use it, measure it, =
reserve it at the IETF" which costs $0 and "follow the ICANN new gTLD =
applicant guidebook" which costs substantially more.
I do recognise them. The data that we have shows that they exists. I =
just think that it is nothing the IETF should invest time in. While the =
IETF cost is significant lower than the ICANN cost I doubt that RFCs =
will get lawyers out of ICANNs back. I think the ship has sailed and it =
now is a political (layer 9) problem who can register what in the global =
DNS name space.

So long
-Ralf


From marka@isc.org  Wed Jan 29 16:45:49 2014
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6851A043F for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 16:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.236
X-Spam-Level: 
X-Spam-Status: No, score=-0.236 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MANGLED_HOME=2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3_beciNRFsTA for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 16:45:48 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 46DF91A0423 for <dnsop@ietf.org>; Wed, 29 Jan 2014 16:45:48 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 739E2C947F; Thu, 30 Jan 2014 00:45:31 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1391042745; bh=GUBMFFmGykHiUeKxhyYg2AItWotPy8cS9p3C0aNKqXY=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=Zh0S8y8xaMQx/axOaspCcKEayddgIHq9ev0KDU0xVZk9SOr520B+ZcKJ6dK2Kc3pP RBlsxu2N/cTZQ5EmjHZRODLqiAHwvMF7Y8sNSiJ0uKl1qpN/bOxSJH5TaADC2B9PA9 Odh/2wFT9E69yrWmJnIi+d/LJv2/8AgctmMLhLC4=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Thu, 30 Jan 2014 00:45:31 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A71CD160470; Thu, 30 Jan 2014 00:57:28 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 45926160389; Thu, 30 Jan 2014 00:57:28 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id C660CE086E0; Thu, 30 Jan 2014 11:45:30 +1100 (EST)
To: Ralf Weber <dns@fl1ger.de>
From: Mark Andrews <marka@isc.org>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de>
In-reply-to: Your message of "Wed, 29 Jan 2014 10:45:40 -0800." <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de>
Date: Thu, 30 Jan 2014 11:45:30 +1100
Message-Id: <20140130004530.C660CE086E0@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 00:45:50 -0000

In message <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de>, Ralf Weber writes:
> Moin!
> 
> On 29 Jan 2014, at 10:07, Joe Abley <jabley@hopcount.ca> wrote:
> > A risk to the Internet as a whole is that a fragmented namespace (.LAN mean
> s something different in John's office than it does at the cafe next door; .H
> OME meaning something different to the thirty million subscribers of ISP X th
> an it does to others) will restrict communication by name between endpoints o
> n the Internet, and changes the fundamental assumptions on which protocols an
> d applications rely to an extent that is potentially unbounded.
> 1. The fragmented name space is a reality and has been for some time (dns spl
> it horizon search on google reveals 500k pages)

And there is a difference between fragmenting namespace that you
control and fragmenting namespace that others control.

I have split horizon namespace (dv.isc.org) but I control the
contents of all versions of that namespace.  Any leaks get answered
by nameservers configured for that zone.

It doesn't have to cost you anything (other than time to setup the
registration) to get a namespace that you have control over.  There
are infrastructure zones which still do free registrations on best
effort basis.

This is about fragmented namespaces where the control is not under
a single party.  This is about pollution of / squatting on the
common namespace ".".

The squatted tld's used by software .onion, .bit etc could be
migrated to a new namespaces.  Just issue new software that looks
/ recognises in the new namespace first then in the old one for X
years.  After X years stop looking in / recognising the old namespace.
Set X to about 10 years and there will be very little old code left
when you turn off support for the namespace.  Set and compile in
the drop dead date.

> 2. If endpoints use proper globally registered DNS names they will be able to
>  communicate. If they use something else the behaviour is undefined.
> I think there is more value in thinking about how we can integrate local and 
> global naming than in trying to protect people by not allowing something to n
> ot be registered in the global name space.
> 
> > This is the end-to-end principle wearing a DNS t-shirt (the IP t-shirt was 
> all cut up by a hundred million NATs, and is no good when it's cold out).
> I don't think the DNS t-shirt looks better.
> 
> > The trouble here is not recognising that namespace collisions are bad; it's
>  (a) deciding where to draw the line between "bad" and "good enough" and (b) 
> dealing with the political headaches of "use it, measure it, reserve it at th
> e IETF" which costs $0 and "follow the ICANN new gTLD applicant guidebook" wh
> ich costs substantially more.
> I do recognise them. The data that we have shows that they exists. I just thi
> nk that it is nothing the IETF should invest time in. While the IETF cost is 
> significant lower than the ICANN cost I doubt that RFCs will get lawyers out 
> of ICANNs back. I think the ship has sailed and it now is a political (layer 
> 9) problem who can register what in the global DNS name space.
> 
> So long
> -Ralf
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
