
From matthijs@nlnetlabs.nl  Mon Jul  1 06:26:04 2013
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB5B21F9A3A for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 06:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O3DASUUQn288 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 06:26:03 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0F111E81D2 for <dnsop@ietf.org>; Mon,  1 Jul 2013 06:25:16 -0700 (PDT)
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 r61DPApt037252 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 1 Jul 2013 15:25:11 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.2 open.nlnetlabs.nl r61DPApt037252
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1372685114; bh=xdwVW41mmCVRZndi0wd6KRE1L7WoxNRU0mI8clGbqoE=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=oh0hvJpeHMZtVzKLzmTqu1qUQYX/iOwLhA3CG2rz4r3lrJwfGZiI1Kwb6ZuVN9I+u rTTiL1fsG6JNMorr+Lqqvzi+U67dV0rzgvardubF5ZRUY5RZIwlfnvBDhuj07urnSC JpPVT79MZdAI5Rv4zS6NO8tEWuqXz88wy3kqZlp0=
Message-ID: <51D18336.5010401@nlnetlabs.nl>
Date: Mon, 01 Jul 2013 15:25:10 +0200
From: Matthijs Mekking <matthijs@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com>
In-Reply-To: <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com>
X-Enigmail-Version: 1.4.6
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]); Mon, 01 Jul 2013 15:25:12 +0200 (CEST)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 13:26:04 -0000

Hi Olafur,

On 06/28/2013 08:18 PM, Olafur Gudmundsson wrote:
> 
> On Jun 25, 2013, at 6:05 AM, Matthijs Mekking <matthijs@NLnetLabs.nl> wrote:
> 
>> Hi,
>>
>> On 06/21/2013 11:58 PM, Wes Hardaker wrote:
>>> Paul Wouters <paul@cypherpunks.ca> writes:
>>>
>>>> I am in favour of adopting this draft as a WG item.
>>>
>>> Ditto.
>>
>> Another ditto. I am pleased to see that there is still activity on the
>> topic of automating the synchronization between DNSKEY at the child and
>> the DS at the parent.
>>
>>
> Thanks
> 
>>>> I don't think the CDS record should be able to cause a child domain to
>>>> go from secure to insecure, or from insecure to secure. That
>>>> (infrequent) change should have an additional authentication, eg via EPP
>>>> or otherwise)
>>>
>>> Ditto.  I think the goal of any of the automatic update techniques
>>> should be to make the routine easy but it shouldn't be a goal to handle
>>> the infrequent, and challenging cases.  (infrequent and easy is fine).
>>>
>>> Unless we can show a clear, secured, path for some transition I don't
>>> think it's worth solving.
>>
>> Another ditto. Agreeing with it's not worth solving to deal with the
>> irregular cases. Going unsigned is an irregular case.
>>
>>
>> Also backing a previous made comment by other people:
>>
>> * I prefer to have the CDS wire format to be similar to the DS wire
>> format. With the current draft, it is already possible to automate all
>> possible key rollovers, no need for managerial hooks to say this record
>> is proposed, must be added, deleted, is valid for only this period etc.
>>
>>
> 
>> Comments on the draft (apologies for its length):
> 
> Thanks for the comments. 
> 
>>
>> * Nit: In section 1, it says there may be two interactions with the
>> parent. This could also be only one, this could be more in some freaky
>> rollovers, so I would prefer that it reads: "there may be one ore more
>> interactions with the parent".
> 
> Applied 
> 
>>
>> * Section 3. I appreciate that most ZSK /KSK terminology is carefully
>> replaced with, but in section 3 is still something that itches: "The SEP
>> bit is an optional bit to indicate that the key is allowed to sign the
>> DNSKEY RRset". That is not true. Without the SEP bit, the key may also
>> sign the DNSKEY RRset.
>>
> 
> I agree but still want to bring up the SEP bit, 
> would some thing like this be better: 
> "The SEP bit is an optional bit that indicates that the child expects to sign the
> DNSKEY RRset with that key, while the key is in use." 

This text is better. Still, I want to propose text:

"The SEP bit, if set, indicates that the DNSKEY is intended for use as a
secure entry point, thus are used to sign the DNSKEY RRset, and the
Parental Agent can calculate DS records based on that."

This removes the notion of optional (strictly the bit is not optional,
the setting of it is).


>> * Section 3.1.1. As said above, I don't like the idea of using the CDS
>> record to go unsigned.
>>
> 
> Ack, 
> this is going to be a design point allow or not allow this function. 
> We can remove this part and later propose it as part of an extension, just like 
> any protocol to automate the tickling of the parent. 
>  
>> * Nit: Section 4.1. I think the last paragraph fits better in section
>> 4.2. CDS Consumption.
> 
> Reworked both sections to address this 
>>
>> * Section 4.2. About the polling strategy. I am wondering how well this
>> scales with respect to the number of delegations.
> 
> The next version will indicate that polling has scaling issues, but punt the problem of 
> defining a mechanishm to another document. 
> The thinking is the "parental notification" is the HARDEST part of the proposal, 
> and we might need multiple solutions depending number of delegations and other factors. 
> Having said that in many cases in particular the enterprise and university cases polling is perfectly fine 
> and will scale, thus our thinking is we will document that and start a parallel document on "MAGIC" system 
> that does the notification, along the lines you documented few years back. 
> 
>>
>> * Section 4.2. It is suggested that RFC 5011-like hold down timers are
>> being used, e.g. new keying information must be published for a month
>> before acceptance as a new trust anchor. This makes the duration of key
>> rollovers unnecessary long. The hold down timers in RFC 5011 are there
>> to mitigate against a compromise. The compromise allows the attacker to
>> sign data in the zone.
> 
> I hear you and want other people to chime in, both in the context of 
> compromise and time to perform rollover. If rollover is done by 
> automated systems that perform checks before progressing who cares how long the 
> rollover takes? 

It depends on what you gain with the long wait. I said in my e-mail that
for me it makes sense to do hold down timers in the RFC5011 case, but we
don't need to be that conservative with CDS. But I guess it has to do
with local policy, what checks you require.

I don't have very strong feelings about this. I just want to see it as
fast as possible:). I guess if everything is done automagically, this is
less of a pain.

A nit drawback I see is that during the transition period you have to
deal with a larger DNSKEY and/or DS RRset.


>>
>> Similar we could look at a compromise that allows the attacker to upload
>> a DS/DNSKEY to the parent. However, there are no mechanisms to mitigate
>> against this attack. Why should we have mitigation for the CDS proposal,
>> if there is none for the current mechanism?
>>
>> The difference between CDS and RFC 5011 is the location of the trust
>> anchor your are updating. With CDS, you are updating the DS in the
>> parent. With RFC 5011, you are updating lots of trust anchors in the
>> wild. The latter may indeed require a bit more conservative approach.
>>
>> * Section 4.3. I wonder if the SHOULD in the first sentence should be a
>> MUST.
>>
> I think a better way is to encourage the child to ONLY publish CDS when there is a need to change the DS record and
> remove after parents performs change. 

I prefer the approach where the CDS represents what DS should be in the
parent. You can make checks: if it is the same, we are in sync. If not,
the parental agent still has work to do.

Adding behavior to remove the CDS again after the update has taken place
at all parent name servers, makes the usage at the child unnecessary
complex.



>> * Section 4.4. I dislike the idea of the side effect of parent
>> calculates DS, so I would like to see that only the "augment" mode is
>> supported (where I think it should read: "it will make sure there are
>> CDS records for the digest algorithm(s) it require(s)" (CDS instead of
>> DS)).
>>
> 
> You are not alone, but there are some people in your neighborhood that 
> feel strongly the other way and argued strongly against version 01 because 
> this was outlawed. 

Hm, yes. And I remember that they require the DNSKEY too. Still, I would
still like to see that the CDS should match the "to be calculated DS".


>> The publishing "Future DNSKEYs" does not go well with several rollover
>> scenarios (those based on Double-DS). I am wondering if the policy is
>> "We calculate the DS" or "We decide the digest algorithm". In case of
>> the latter, then augment mode can be used to support this. In case of
>> the first, the future DNSKEY is really required to be published, and
>> Double-DS based rollovers are not possible in combination with CDS.
>>
> 
> exactly 
> 
>> * Section 6. Security Considerations. The last paragraph. Isn't this
>> solved by saying that the Parental Agent MUST ensure that old versions
>> of the CDS RRset do not override newer versions in section 4.3. Usage?
>> There is already a proposed method on how to achieve this there.
>>
> 
> Strictly speaking using RFC5011 will address this as all the signatures in 
> "disjoint" authorative servers wil have expired. 

>> * When implementing a prototype for this in OpenDNSSEC, I questioned
>> myself what value I should use for the TTL. We could consider 0, as this
>> record is not really intended for the resolver. We could also use the
>> TTL to suggest a polling frequency for the parental agent. Just some
>> thoughts.
>>
>>
> I had not thought about guidance on the CDS TTL, nor on the signature lifetime on the record. 
> You have any ideas? 

I just set it to the DNSKEY TTL currently. In OpenDNSSEC you can only
set different signature lifetime for NSEC(3) and the rest, so nothing
special there for CDS either.

I don't think we need special guidance.

The only idea I had, I already mentioned is that we could use the TTL
field to signal a polling frequency.


Best regards,
  Matthijs



> 
> 
>> Best regards,
>>  Matthijs
>>
> Thanks for great review. 
> 
> 	Olafur
> 
> 


From warren@kumari.net  Mon Jul  1 06:52:19 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40C7711E80DC; Mon,  1 Jul 2013 06:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSAIIN0nq-Jn; Mon,  1 Jul 2013 06:52:14 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81B4921F9EAE; Mon,  1 Jul 2013 06:52:05 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id 28A341B40088; Mon,  1 Jul 2013 09:52:04 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net>
Date: Mon, 1 Jul 2013 09:52:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2310CDA9-DFB9-4F57-8DB1-F18B7B5F6874@kumari.net>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net>
To: IETF DNSOP WG <dnsop@ietf.org>, "dnsop-chairs@ietf.org" <dnsop-chairs@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 13:52:19 -0000

On Jun 17, 2013, at 1:32 PM, Warren Kumari <warren@kumari.net> wrote:

> Hi there all,
>=20
> We have just posted a new version of draft-kumari-ogud-dnsop-cds=20
>=20
> This incorporates comments from both the list and in person =
discussions.=20
>=20
> The authors believe this version is ready for WG adoption and request =
the DNSOP chairs to kick off an adoption call.

It has now been 2 weeks since we requested a call for adoption on this.=20=

Chairs?

W

>=20
> W
>=20
>=20
> Begin forwarded message:
>=20
>> From: internet-drafts@ietf.org
>> Subject: New Version Notification for =
draft-kumari-ogud-dnsop-cds-02.txt
>> Date: June 17, 2013 12:58:29 PM EDT
>> To: Olafur Gudmundsson <ogud@ogud.com>, Warren Kumari =
<warren@kumari.net>, George Barwood <george.barwood@blueyonder.co.uk>
>>=20
>>=20
>> A new version of I-D, draft-kumari-ogud-dnsop-cds-02.txt
>> has been successfully submitted by Warren Kumari and posted to the
>> IETF repository.
>>=20
>> Filename:	 draft-kumari-ogud-dnsop-cds
>> Revision:	 02
>> Title:		 Automating DNSSEC delegation trust maintenance
>> Creation date:	 2013-06-17
>> Group:		 Individual Submission
>> Number of pages: 14
>> URL:             =
http://www.ietf.org/internet-drafts/draft-kumari-ogud-dnsop-cds-02.txt
>> Status:          =
http://datatracker.ietf.org/doc/draft-kumari-ogud-dnsop-cds
>> Htmlized:        =
http://tools.ietf.org/html/draft-kumari-ogud-dnsop-cds-02
>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-kumari-ogud-dnsop-cds-02
>>=20
>> 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.
>>=20
>>=20
>>=20
>>=20
>> The IETF Secretariat
>>=20
>=20
> --
> "Let's just say that if complete and utter chaos was lightning, he'd =
be the sort to stand on a hilltop in a thunderstorm wearing wet copper =
armour and shouting 'All gods are bastards'."
>=20
>    -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of =
Magic)
>=20
>=20

--
Hope is not a strategy.
      --  Ben Treynor, Google



From Antoin.Verschuren@sidn.nl  Mon Jul  1 08:17:12 2013
Return-Path: <Antoin.Verschuren@sidn.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00A3411E81B4 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 08:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrZ5P8Jw3zD8 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 08:17:07 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED0911E81A8 for <dnsop@ietf.org>; Mon,  1 Jul 2013 08:17:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=from:to:subject:thread-topic:thread-index:date:message-id:references:in-reply-to:accept-language:content-language:x-ms-has-attach:x-ms-tnef-correlator:x-originating-ip:content-type:content-id:content-transfer-encoding:mime-version; bh=mmLGNRoT6qpK10BGgYFt1+omhAJpsiSJUZ2wK0OmLC4=; b=SuRfWM8FtpWCRw77r3LP5+momTlddhHaeikpUsl7jiX+sshvBlbUqY4cbk+Et1gbbIANUwX9KUnDdgmBDd5eaQX6NEH9tZdGd/oLWdZbmJFPObDbacK4FmJBGMwrn8msPeHf+JoYNweSnY5A0AeUwfYr9ZYYEzla13luepMMxtc=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r61FGqJM004391-r61FGqJO004391 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL) for <dnsop@ietf.org>; Mon, 1 Jul 2013 17:16:52 +0200
Received: from KAHUBCAS1.SIDN.local (192.168.2.41) by kahubcasn02.SIDN.local (192.168.2.74) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 1 Jul 2013 17:16:52 +0200
Received: from KAMBX2.SIDN.local ([fe80::b1fd:88d9:e136:9655]) by kahubcas1.SIDN.local ([fe80::dff:8232:1563:3a16%14]) with mapi id 14.02.0328.009; Mon, 1 Jul 2013 17:16:52 +0200
From: Antoin Verschuren <Antoin.Verschuren@sidn.nl>
To: IETF DNSOP WG <dnsop@ietf.org>
Thread-Topic: draft-hardaker-dnsop-csync-00.txt versus draft-kumari-ogud-dnsop-cds-02.txt
Thread-Index: AQHOdm4CUCdjAIXKTEaZD/7w+hviAA==
Date: Mon, 1 Jul 2013 15:16:50 +0000
Message-ID: <ED84A6DE40A3EE48BFB5CEC46D007D9655586F27@kambx2.SIDN.local>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <2310CDA9-DFB9-4F57-8DB1-F18B7B5F6874@kumari.net>
In-Reply-To: <2310CDA9-DFB9-4F57-8DB1-F18B7B5F6874@kumari.net>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [94.198.152.221]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A75198E84FB3064288FF2E26A96F726F@sidn.nl>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [DNSOP] draft-hardaker-dnsop-csync-00.txt versus draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 15:17:12 -0000

I have read both draft-hardaker-dnsop-csync-00.txt as draft-kumari-ogud-dns=
op-cds-02.txt, and I must say I have a preference for the more general appr=
oach of draft-hardaker-dnsop-csync-00.txt.
Both documents try to accomplish the same, but draft-kumari-ogud-dnsop-cds-=
02.txt only tries to do so for one specific use case, and it seems it's try=
ing to write the problem statement after presenting the sollution.

I esspecially don't agree with the text in paragraphs 1.2, 2.1, 2.2 and 2.4=
 of draft-kumari-ogud-dnsop-cds-02.txt.
They seem to focus only to how registrations and the RRR model is percieved=
, focusses esspecially on the GTLD space, but fails to give a clear definit=
ion.
With most registries, a registrant does not "buy" a domain. it may be perci=
eved as such, but when it is not renewed in the GTLD case, you don't own it=
 anymore, which I don't see as "buying".
In other TLD's, delegations are based on licenses, or in many cases, there =
is a direct contractual relationship between a regisry and registrant.
I would say to not focus on trying to translate what we see in our own expe=
rience, but try to find a good definition, if one is needed at all.
I would like to see a definition that fits all models, be it a TLD or anoth=
er parent. Lets make it more general.
I would formulate a definition like this:

Registry: Entity that is responsible for a parent zone that maintains regis=
trations of delegations in that zone.
Registrant: Entity that is responsible for a child zone that was delegated =
to him by a parent.
Registrar: Administrative entity that represents the parent towards a regis=
trant for administrative maintanance of the registration data of the delega=
tion at the parent.

Let's try to forget everyones personal  frustration with all of the example=
s we know.

The use case we're trying to solve is how to get data from child to parent =
that needs to be part of the delegation.
I think we need to make clear that there is a difference between administra=
tive and technical data.
Technical data usually flows over the administrative channel because a dele=
gation needs bootstrapping, and no delegation yet excists, so no secure cha=
nnel is available.
When we want technical data to flow over DNS from child to parent after boo=
tstrapping, I don't see a difference between DS, DNSKEY, NS or other other =
technical data.
That's why I like draft-hardaker-dnsop-csync-00.txt better, because that's =
the general use case.

In the general use case, we don't need to think on DS versus DNSKEY, SEP bi=
t set or not, etc.
You just publish technical data for the parent to notice.

The question I'm still puzzled with in both proposals is how we're going to=
 migrate from the current "pushing technical data to the parent over the ad=
ministrative channel" towards "pushing technical data over the DNS for the =
parent to pick up". I actually think that this is not as easy as we think, =
and we're sticking our heads in the sand if we say this is "local policy". =
We allways want the administrative channel to be a back-up channel when the=
 delegation breaks, and we need to re-bootstrap the delegation. But this le=
ads to the question which path is authoritative. In simple words, what do I=
 do as a parent (or parental agent) when I recieve information over the DNS=
 that conflicts with data I receive over the administrative channel. Which =
data should I follow.

Some remarks to earlier discussions I saw here on the list:
It was stated that when a parent is requesting DNSKEY instead of DS, and th=
e parent calculates the DS, the disadvantage is that the child cannot choos=
e the digest algorithm. This is not true. The child can send the DNSKEY and=
 signal the desired algorithm by which the parent should calculate the dige=
st. The parent may limit the number of algorithms to choose from, but that =
does not mean there is no choice. The parent may have good reasons to limit=
 the number of digest algorithms. I don't want to go into too much discussi=
on on the DS versus DNSKEY acceptance by the parent, but we recently found =
another issue in provisioning that we could not have solved easily if we as=
 parent only knew the DS.

The second remark I have is that the only use case that seems to favour DS =
over DNSKEY is standby keys where you don't want to publish a standby DNSKE=
Y in your zone.
I fail to see how publishing a DS in a CDS record for your standby key is m=
uch more safer from publishing the DNSKEY of your standby key.
I would say that if you want to publish a DS for your standby key at your p=
arent, you can allways use the administrative bootstapping channel for that=
.
But then still, what's the benefit over only exposing your DS over exposing=
 your DNSKEY, when not a single signature has been created or published wit=
h that standby key?
 =20

- --=20
Antoin Verschuren

Technical Policy Advisor SIDN
Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  F: +31 26 3525505  M: +31 6 23368970
mailto:antoin.verschuren@sidn.nl  xmpp:antoin@jabber.sidn.nl
http://www.sidn.nl/


From jabley@hopcount.ca  Mon Jul  1 10:32:05 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F75511E80E8 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PlW74IHc0tsl for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:32:05 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id EDB4011E80E2 for <dnsop@ietf.org>; Mon,  1 Jul 2013 10:32:04 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so5146737oah.38 for <dnsop@ietf.org>; Mon, 01 Jul 2013 10:32:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer; bh=aJUmhpYxnviulZrlqY+t0cfot/OBk/Pa3DBNmlCU5HM=; b=ZH/PpsphkAHDC0mJduWiMZYdWiKtU9gcB0xWrfzHoEInFguofoWXkg8WUPjmW+U80F Dfu2uV43hBti3UHuKBmcVOozN1l374Zt/8hMxrtb7gHwFDPoB+u04z7w+XDETsKOaYeP XCkAXHuhhLG/BWWe23PoxS7GwCiPpc5q3N4lE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer:x-gm-message-state; bh=aJUmhpYxnviulZrlqY+t0cfot/OBk/Pa3DBNmlCU5HM=; b=Pipc2/IUXZyhrkGCsKLMu+PZ71CpcQpgzfLyVzgRLBGwKg94mj/wu1tw2DvwX/qcdP LKqb+z00JbT86VkgY2jfypM1Mpyc3htcf2joJlJNqo/FXnzaOMOISBhm8QRHmMUO4pp4 +JDnxc1BbvRp1+zBbXp7l58Yj1lXznMnT+GqmJ8BakuGD9++seUmEpm6GZB8O4PbVHgZ +844Al5CliIUCW/WjkE0kQOvzpY6zexdZxE3TNI7STVPDmWE+nDrn+qsLNd610dd/ZHs C7g78wEZyXBWnFP4mPsrMk1z5W8RlrndjqjRS3l7hBBKqYnzx6SxT5sanrOn7yznffIp GLtQ==
X-Received: by 10.182.80.5 with SMTP id n5mr10877165obx.88.1372699924416; Mon, 01 Jul 2013 10:32:04 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:ed46:19c5:426d:99bc? ([2001:4900:1042:100:ed46:19c5:426d:99bc]) by mx.google.com with ESMTPSA id o4sm4416171obl.7.2013.07.01.10.32.03 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 10:32:03 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <A39F2925-137D-41AC-8871-E0CFE2B3B2CE@hopcount.ca>
Date: Mon, 1 Jul 2013 13:32:01 -0400
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQk2jgOtAImiwxo4AAYO4d5DWItt585/dWErDgnBwtcTgVJINwJeI1nO3zjSfqOISoXEFphj
Subject: [DNSOP] AS112 work
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 17:32:05 -0000

Hi all,

We have two drafts on the table relating to extensions to AS112 service, =
in particular to accommodate delegation or redirection of new zones to =
the infrastructure:

  draft-wkumari-dnsop-omniscient-as112
  draft-jabley-dnsop-as112-dname

I suspect that it makes no sense to proceed with both approaches =
(although perhaps someone else here thinks differently).

I have talked to Warren, and the sensible approach seems to be to =
discuss both approaches here, and choose one of them. At that point we =
can merge useful text, authors, etc and proceed with the polish on the =
selected option.

Could we ask the chairs to help facilitate this discussion?

Thanks,


Joe=

From tim.wicinski@teamaol.com  Mon Jul  1 10:43:28 2013
Return-Path: <tim.wicinski@teamaol.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64DA621F9B22 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G3tklft9XGt7 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:43:24 -0700 (PDT)
Received: from omr-m08.mx.aol.com (omr-m08.mx.aol.com [64.12.222.129]) by ietfa.amsl.com (Postfix) with ESMTP id E7D0F11E8160 for <dnsop@ietf.org>; Mon,  1 Jul 2013 10:43:13 -0700 (PDT)
Received: from AOLDTCMEI34.ad.aol.aoltw.net (aoldtcmei34.office.aol.com [10.180.121.151]) by omr-m08.mx.aol.com (Outbound Mail Relay) with ESMTP id EA6A270072E22; Mon,  1 Jul 2013 13:43:12 -0400 (EDT)
Received: from still.local (172.17.8.193) by AOLDTCMEI34.ad.aol.aoltw.net (10.180.121.151) with Microsoft SMTP Server id 14.3.123.3; Mon, 1 Jul 2013 13:43:12 -0400
Message-ID: <51D1BFB0.5030000@teamaol.com>
Date: Mon, 1 Jul 2013 13:43:12 -0400
From: Tim Wicinski <tim.wicinski@teamaol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>, "dnsop@ietf.org WG" <dnsop@ietf.org>
References: <A39F2925-137D-41AC-8871-E0CFE2B3B2CE@hopcount.ca>
In-Reply-To: <A39F2925-137D-41AC-8871-E0CFE2B3B2CE@hopcount.ca>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.17.8.193]
Subject: Re: [DNSOP] AS112 work
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 17:43:28 -0000

We (Peter and I) were going to discuss these coming up this week, but we 
felt the combining was the right direction.

If a disinterested third party would be willing to facilitate please 
step up, otherwise I will be able to (but a little thin on time till 
tomorrow).

tim


On 7/1/13 1:32 PM, Joe Abley wrote:
> Hi all,
>
> We have two drafts on the table relating to extensions to AS112 service, in particular to accommodate delegation or redirection of new zones to the infrastructure:
>
>    draft-wkumari-dnsop-omniscient-as112
>    draft-jabley-dnsop-as112-dname
>
> I suspect that it makes no sense to proceed with both approaches (although perhaps someone else here thinks differently).
>
> I have talked to Warren, and the sensible approach seems to be to discuss both approaches here, and choose one of them. At that point we can merge useful text, authors, etc and proceed with the polish on the selected option.
>
> Could we ask the chairs to help facilitate this discussion?
>
> Thanks,
>
>
> Joe
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From warren@kumari.net  Mon Jul  1 10:45:42 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECFAC11E80D7 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yicajhr59NNh for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:45:26 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F00F11E814E for <dnsop@ietf.org>; Mon,  1 Jul 2013 10:45:26 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id 0C18B1B407A9; Mon,  1 Jul 2013 13:45:24 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <A39F2925-137D-41AC-8871-E0CFE2B3B2CE@hopcount.ca>
Date: Mon, 1 Jul 2013 13:45:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0E13D83-56F9-4795-A070-34E2F60524B5@kumari.net>
References: <A39F2925-137D-41AC-8871-E0CFE2B3B2CE@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1508)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] AS112 work
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 17:45:42 -0000

On Jul 1, 2013, at 1:32 PM, Joe Abley <jabley@hopcount.ca> wrote:

> Hi all,
>=20
> We have two drafts on the table relating to extensions to AS112 =
service, in particular to accommodate delegation or redirection of new =
zones to the infrastructure:
>=20
>  draft-wkumari-dnsop-omniscient-as112
>  draft-jabley-dnsop-as112-dname
>=20
> I suspect that it makes no sense to proceed with both approaches =
(although perhaps someone else here thinks differently).
>=20
> I have talked to Warren, and the sensible approach seems to be to =
discuss both approaches here, and choose one of them. At that point we =
can merge useful text, authors, etc and proceed with the polish on the =
selected option.
>=20
> Could we ask the chairs to help facilitate this discussion?

In the mean time -- assuming that we test DNAME and find out that:
A: it is well supported
B: works well enough.
C: doesn't have any bad side effects
does anyone have any compelling reasons why we wouldn't simply go the =
DNAME route?

W


>=20
> Thanks,
>=20
>=20
> Joe
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20

--
"When it comes to glittering objects, wizards have all the taste and =
self-control of a deranged magpie."
-- Terry Pratchett





From jabley@hopcount.ca  Mon Jul  1 10:54:29 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0128B11E80D7 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOxtBa7TWn1q for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:54:23 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id D881B21F9079 for <dnsop@ietf.org>; Mon,  1 Jul 2013 10:53:42 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd20so4556890obb.5 for <dnsop@ietf.org>; Mon, 01 Jul 2013 10:53:42 -0700 (PDT)
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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=8eD0NROTJccolatEuGK1zSPNYdGsVzrIwikeQRg8ej0=; b=Z/AJwK0RddxFB1wMSrZbj5VANmKAYh9Kg7yhyvn8+FUzsxFG9XClZza4+6WZvK2B/z FL3UG8CKXv+eEznGvcdvAKFr/+h/L7WbPnTd2k24bZEBU9iVji7+Tu91drtd/N6tA/BG fBKapy2VDrKN/E4QAFCzV9fC4RD4OWlGLgJ+c=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=8eD0NROTJccolatEuGK1zSPNYdGsVzrIwikeQRg8ej0=; b=eIxZIAiitu0tKIMl9+529RJr9ls5Y5sq0/aGSiWc/M4Wy0gF/igBW7mtqeY+BBTd+n HwyeVP2CxYXLsp4VT8SNuuaCSyXrq0coMpTx6xsNPMVSUtGQMh1jHk/li/+Kz0Wb4A5i ZiBIHBv89i2fqXfDP1NA5HYP09jWzJom4y302+snc3lVEI+d2Y3k2AgshiJUrP/l8Qe8 cwKYrZZDDnz5kIBBOKt6swNGk3pKPGjfo59lhqPUIBbgBcQsstg3j0yb4i1yTaNe+P1h dAzylO8JvMsv7iBuquhLa/fmVwl0nPbzL50JckRouLDAKYrmsI3Y/TG305bQzCCG0Hbw 4aWg==
X-Received: by 10.60.37.74 with SMTP id w10mr10169628oej.30.1372701222412; Mon, 01 Jul 2013 10:53:42 -0700 (PDT)
Received: from [199.212.90.42] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id o4sm4442888obl.7.2013.07.01.10.53.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 10:53:41 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <C0E13D83-56F9-4795-A070-34E2F60524B5@kumari.net>
Date: Mon, 1 Jul 2013 13:53:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <75C706FB-40A7-4067-B8D1-32253C7D9A4D@hopcount.ca>
References: <A39F2925-137D-41AC-8871-E0CFE2B3B2CE@hopcount.ca> <C0E13D83-56F9-4795-A070-34E2F60524B5@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQlMaRJoFEQo8c2MClI9LSgZPlNDsfHa8F/62Pr27kCNP+5G58zFICV1qUPOZqtCe5s3RL4H
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] AS112 work
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 17:54:29 -0000

On 2013-07-01, at 13:45, Warren Kumari <warren@kumari.net> wrote:

> In the mean time -- assuming that we test DNAME and find out that:
> A: it is well supported

A.5: the interactions between components are not harmful in the event =
that DNAME is not supported (i.e. that CNAME synthesis mitigates the =
lack of support, and that the interactions in that case are benign)

> B: works well enough.
> C: doesn't have any bad side effects
> does anyone have any compelling reasons why we wouldn't simply go the =
DNAME route?


Joe


From warren@kumari.net  Mon Jul  1 10:59:17 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7693C11E8135 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KkWZghTH1kr for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 10:59:12 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDCF21F9B81 for <dnsop@ietf.org>; Mon,  1 Jul 2013 10:58:42 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id B95B01B407A9; Mon,  1 Jul 2013 13:58:40 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51D1BFB0.5030000@teamaol.com>
Date: Mon, 1 Jul 2013 13:58:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CD2D04DE-7435-4E06-8B11-5D39604E9CDA@kumari.net>
References: <A39F2925-137D-41AC-8871-E0CFE2B3B2CE@hopcount.ca> <51D1BFB0.5030000@teamaol.com>
To: Tim Wicinski <tim.wicinski@teamaol.com>
X-Mailer: Apple Mail (2.1508)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] AS112 work
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 17:59:17 -0000

On Jul 1, 2013, at 1:43 PM, Tim Wicinski <tim.wicinski@teamaol.com> =
wrote:

> We (Peter and I) were going to discuss these coming up this week, but =
we felt the combining was the right direction.
>=20
> If a disinterested third party would be willing to facilitate please =
step up, otherwise I will be able to (but a little thin on time till =
tomorrow).

I think that we can try integrate this ourselves. If we run into any =
issues we can come back and ask for chair / mediator help.

I am not really expecting any contentious combining them -- we just want =
the best solution, and so far no-one has spoken out strongly against =
DNAME. Assuming we don't run into any huge road-blocks I (speaking only =
for myself) don't see an issue with using it as the "solution".

W=20


> tim
>=20
>=20
> On 7/1/13 1:32 PM, Joe Abley wrote:
>> Hi all,
>>=20
>> We have two drafts on the table relating to extensions to AS112 =
service, in particular to accommodate delegation or redirection of new =
zones to the infrastructure:
>>=20
>>   draft-wkumari-dnsop-omniscient-as112
>>   draft-jabley-dnsop-as112-dname
>>=20
>> I suspect that it makes no sense to proceed with both approaches =
(although perhaps someone else here thinks differently).
>>=20
>> I have talked to Warren, and the sensible approach seems to be to =
discuss both approaches here, and choose one of them. At that point we =
can merge useful text, authors, etc and proceed with the polish on the =
selected option.
>>=20
>> Could we ask the chairs to help facilitate this discussion?
>>=20
>> Thanks,
>>=20
>>=20
>> Joe
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20

--
"Let's just say that if complete and utter chaos was lightning, he'd be =
the sort to stand on a hilltop in a thunderstorm wearing wet copper =
armour and shouting 'All gods are bastards'."

    -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of =
Magic)



From warren@kumari.net  Mon Jul  1 14:43:36 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 347AF21F9BA8 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 14:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dIDGUs72YrRI for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 14:43:31 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51BAA21F9B88 for <dnsop@ietf.org>; Mon,  1 Jul 2013 14:43:31 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id E88351B40088; Mon,  1 Jul 2013 17:43:29 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
Date: Mon, 1 Jul 2013 17:43:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net>
References: <20130701214044.559.35489.idtracker@ietfa.amsl.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 21:43:36 -0000

Hi there,

We would like to draw your attention to a new draft.=20
If describes a simply optimization that, with minimal to no state, keeps =
popular records in recursive server's caches.=20

W

Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for =
draft-wkumari-dnsop-hammer-00.txt
> Date: July 1, 2013 5:40:44 PM EDT
> To: Roy Arends <roy@nominet.org.uk>, Suzanne Woolf <woolf@isc.org>, =
Warren Kumari <warren@kumari.net>
>=20
>=20
> A new version of I-D, draft-wkumari-dnsop-hammer-00.txt
> has been successfully submitted by Warren Kumari and posted to the
> IETF repository.
>=20
> Filename:	 draft-wkumari-dnsop-hammer
> Revision:	 00
> Title:		 Highly Automated Method for Maintaining =
Expiring Records
> Creation date:	 2013-07-01
> Group:		 Individual Submission
> Number of pages: 5
> URL:             =
http://www.ietf.org/internet-drafts/draft-wkumari-dnsop-hammer-00.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-wkumari-dnsop-hammer
> Htmlized:        =
http://tools.ietf.org/html/draft-wkumari-dnsop-hammer-00
>=20
>=20
> Abstract:
>   This document describes a simple DNS cache optimization which keeps
>   the most popular records in the DNS cache.
>=20
>=20

No man is an island, But if you take a bunch of dead guys and tie them =
together, they make a pretty good raft.
                --Anon.



From johnl@iecc.com  Mon Jul  1 18:45:06 2013
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E267D11E8368 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 18:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.313
X-Spam-Level: 
X-Spam-Status: No, score=-110.313 tagged_above=-999 required=5 tests=[AWL=0.886, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdtK1m0pB54U for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 18:45:02 -0700 (PDT)
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 7214211E834F for <dnsop@ietf.org>; Mon,  1 Jul 2013 18:45:01 -0700 (PDT)
Received: (qmail 80062 invoked from network); 2 Jul 2013 01:45:00 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Jul 2013 01:45:00 -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=51d2309c.xn--i8sz2z.k1307; i=johnl@user.iecc.com; bh=ib9y4bWXYHvv1qM512XJBPUpyW5yKKFjc8ZuybTY/zk=; b=LBckHm3C+3jWgKkb+MoPPPEze24v1IPvcEmroWd3v1E46EkBCjBoSYK7iRTW3YxoF8RVhfAz88nhfjBC0VN92E5l9zrWbp6hDDvUdDSvgi/0LxF1MZH47PGzvCnf5BP5BgFechZ1DiStAPj3ZVHeyYnKD6H2l9bCNxl5gpHkp1tu2zVZSMypueVKsLZ8V69VnBI3liItUsr/xwIk42C3PC4plhQl4jN/ZOYXn+YeCg041YoWNZ9oROniu6BYrTT1
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=51d2309c.xn--i8sz2z.k1307; olt=johnl@user.iecc.com; bh=ib9y4bWXYHvv1qM512XJBPUpyW5yKKFjc8ZuybTY/zk=; b=OabUWK8RuUYlX/N2IAHoCcLMbZNDKrteyIfVWQRRCFG6OiYSiCJuiTs3eleXHZcPG2+2AvChyvF2X1NpbTTHkJTodHD7BRdNYUzZA/me1VU29LgrVyWCBRlZPR/PkGr1qUsfUJoq16iD9fzJ7rKow2266GHvZHwPTFrFhELBOg7sejAaQhPwtB5k24EjRU09TTPBqUX8w2vTnA8q4VUVcgoJos1dyAVHO5Fpsa6yXlMInysBkisSka8vZ5cLT7KL
Date: 2 Jul 2013 01:44:38 -0000
Message-ID: <20130702014438.15013.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 01:45:07 -0000

>We would like to draw your attention to a new draft. 

It looks like it should work, assuming that your cache uses the
existing logic to remember queries in progress so it doesn't hammer a
record that's already in the process of being refetched.

My main observation is that I have no idea what the tradeoffs are
between the increased DNS traffic and faster responses to clients.
Have you done simulations or live experiments?

R's,
John

From matthijs@nlnetlabs.nl  Mon Jul  1 22:58:29 2013
Return-Path: <matthijs@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9D7E11E82A2 for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 22:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GH33Rt6NQGso for <dnsop@ietfa.amsl.com>; Mon,  1 Jul 2013 22:58:29 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC8711E8299 for <dnsop@ietf.org>; Mon,  1 Jul 2013 22:58:28 -0700 (PDT)
Received: from [IPv6:2001:981:19be:1:7cd4:ec7c:700d:c21f] ([IPv6:2001:981:19be:1:7cd4:ec7c:700d:c21f]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r625wP6D075886 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Tue, 2 Jul 2013 07:58:26 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.2 open.nlnetlabs.nl r625wP6D075886
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1372744707; bh=DwEmfT8qVNs7qX5pvmXcEnV7dvX5eYlk2Jo+4raLCZM=; h=Date:From:To:Subject:References:In-Reply-To; b=yVFjcxpkKx4Wy7siBdULOQ+HXoFpV5Hyl8sRKxJKQH5j2jMDLvmqRVuxpAtkq4dnv KWGOWQ1uv7SCVD1J3wQxCEA9UYctZykcShfWpUKyvstiGQh29OdKOXJNXXYLbE2mTm JspcsH+73ZYf5reARXEuf1JhNjZIuWzKW+fcpT+E=
Message-ID: <51D26C01.1010508@nlnetlabs.nl>
Date: Tue, 02 Jul 2013 07:58:25 +0200
From: Matthijs Mekking <matthijs@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20130702014438.15013.qmail@joyce.lan>
In-Reply-To: <20130702014438.15013.qmail@joyce.lan>
X-Enigmail-Version: 1.4.6
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, 02 Jul 2013 07:58:26 +0200 (CEST)
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 05:58:30 -0000

This sounds a lot like prefetch in unbound, and the configuration option
gives some analysis on increased traffic.

prefetch: <yes or no>
     If yes, message cache elements are prefetched before they expire
     to  keep  the  cache  up to date.  Default is no.  Turning it on
     gives about 10 percent more traffic and load on the machine, but
     popular items do not expire from the cache.


Also, if the original TTL of the RR is less than STOP * HAMMER_TIME then
the cache entry, it cannot be used anymore and the resolver should
"Break it down".

Best regards,
 Matthijs

On 07/02/2013 03:44 AM, John Levine wrote:
>> We would like to draw your attention to a new draft. 
> 
> It looks like it should work, assuming that your cache uses the
> existing logic to remember queries in progress so it doesn't hammer a
> record that's already in the process of being refetched.
> 
> My main observation is that I have no idea what the tradeoffs are
> between the increased DNS traffic and faster responses to clients.
> Have you done simulations or live experiments?
> 
> R's,
> John
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
> 


From wouter@nlnetlabs.nl  Tue Jul  2 00:53:43 2013
Return-Path: <wouter@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5AF111E8406 for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 00:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkWs0YXjLR-P for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 00:53:42 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FEA911E8400 for <dnsop@ietf.org>; Tue,  2 Jul 2013 00:53:42 -0700 (PDT)
Received: from axiom.nlnetlabs.nl (axiom.nlnetlabs.nl [IPv6:2001:7b8:206:1:222:4dff:fe55:4d46]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r627rdbj001634 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Tue, 2 Jul 2013 09:53:40 +0200 (CEST) (envelope-from wouter@nlnetlabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.2 open.nlnetlabs.nl r627rdbj001634
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1372751621; bh=HUMQTbYHsEL6+dUjVpbsVLDGOCYiurKpCy07qMXAhL4=; h=Date:From:To:Subject:References:In-Reply-To; b=WCLby2UP9NwHd0wajxZOjOwWu+Cr1liNlFeFHQQEAvXbWwi11hRl+cuQAWwXPM9Y/ qJajY4FRErkzVMThpZ80/IUNR5oow2IdsI4483mVIAXcA2v8l5qSBz6m2aFaYQWcxO oXhTMFPyHt+hKMXh0+yrzpfuJGx8Mc3VK77mlQNM=
Message-ID: <51D28703.4020006@nlnetlabs.nl>
Date: Tue, 02 Jul 2013 09:53:39 +0200
From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20130702014438.15013.qmail@joyce.lan> <51D26C01.1010508@nlnetlabs.nl>
In-Reply-To: <51D26C01.1010508@nlnetlabs.nl>
X-Enigmail-Version: 1.5.1
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::1]); Tue, 02 Jul 2013 09:53:40 +0200 (CEST)
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 07:53:44 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

It is exactly that option.  With some small changes.  The draft has a
fixed time HAMMER_TIME.  Unbound has a hard-coded percentage, 10%,
which is not configurable (by choice, no option that hurts).  This
setting causes an upper bound on the extra work of about 10% and about
10% more traffic towards nameservers (so the prefetch option is not
deleterious to others).  Authority server owners can influence their
prefetch behaviour via the TTL (a larger TTL has a larger
'hammer-time' of 10% of TTL, but also still a larger cache-TTL as
well, and also the relative popularity that is necessary to be
prefetched goes down as you only need queries inside of a longer time
period to be prefetched).

We tested this in a large production resolver and found that the
benefits are small.  Likely when the cache expires there is no more
spike in latency for a couple of customers.  The cache hits increase
modestly, but not spectacularly; some percents more cache hits.

In the draft the "touch this" phrase is very funny, however I would
prefer implementation-independent phrasing, i.e. 'do not perform
prefetch for this element'.

Is a draft necessary for this?

Best regards,
   Wouter

On 07/02/2013 07:58 AM, Matthijs Mekking wrote:
> This sounds a lot like prefetch in unbound, and the configuration
> option gives some analysis on increased traffic.
> 
> prefetch: <yes or no> If yes, message cache elements are prefetched
> before they expire to  keep  the  cache  up to date.  Default is
> no.  Turning it on gives about 10 percent more traffic and load on
> the machine, but popular items do not expire from the cache.
> 
> 
> Also, if the original TTL of the RR is less than STOP * HAMMER_TIME
> then the cache entry, it cannot be used anymore and the resolver
> should "Break it down".
> 
> Best regards, Matthijs
> 
> On 07/02/2013 03:44 AM, John Levine wrote:
>>> We would like to draw your attention to a new draft.
>> 
>> It looks like it should work, assuming that your cache uses the 
>> existing logic to remember queries in progress so it doesn't
>> hammer a record that's already in the process of being
>> refetched.
>> 
>> My main observation is that I have no idea what the tradeoffs
>> are between the increased DNS traffic and faster responses to
>> clients. Have you done simulations or live experiments?
>> 
>> R's, John _______________________________________________ DNSOP
>> mailing list DNSOP@ietf.org 
>> https://www.ietf.org/mailman/listinfo/dnsop
>> 
> 
> _______________________________________________ DNSOP mailing list 
> DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR0ob/AAoJEJ9vHC1+BF+NKMYP/jyEaMqmE4UFWpl8wxHX5QIy
aFDIL7Un8Rk9S9ZRR/laLUpo9b4Stfq21lgQeYR75h5MIycSYVX9x8zR3YOXEQsM
wsBcA0VxS0J1+4fwJZn1yJ/ZqtdPEIjpP1CD+tKl7sErqkGpcsRQaN5ib62Sayrw
eD++QZusEZvtWVG3PjZV7g7PEn2tH7iaoRFhVhqhzc13bzMjp9GahzxrZvgLfnGC
0sDdB1BY8V7GCqfJEMyUEGIeeojlguqu5JXhIMphGW2Chyc8uZguDd/tMwkCVKJc
O/NFYf731mg72BpcaY+n2r2bEYrDVEycbYiTblTiEVtyRjdIBxygZaMdKRH0JtaG
6xzbWuRgvFkvd//yGvYvHZi8MuFKEw8TA6OFjjm1x1acGYkq4QNJ7bSqnUK0S1i3
O+Bxw4wfZ2Xz4/Er0r8XDi/iUhBr8f7WVg+X5pBCAXhb9JPhA+AIiZXwoJUI6FTF
kiafBu+DPUgpcTJ4Db3MUnedNtAY11FK6QCBLcMnBOxQWZiL7dp+GUO63mRkfkt6
OYfbWn3eEWgYD3tw8iq8RoESQ54cf1X8QzL0kkLeOG2oAxQIrqv/AsMLuKpjGTqJ
cEKF3OrqIeG7H0mwNZIW8v3Av2JSICsuOSYYARyGBkvYOt+tBAivlYNaSq/OJLWo
GCD2F9UJIVYkHw3V+xaj
=dXxa
-----END PGP SIGNATURE-----

From Antoin.Verschuren@sidn.nl  Tue Jul  2 03:07:56 2013
Return-Path: <Antoin.Verschuren@sidn.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E9F211E8471 for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 03:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.882
X-Spam-Level: 
X-Spam-Status: No, score=-0.882 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqWqFlvZRbIK for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 03:07:51 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 635EC11E8461 for <dnsop@ietf.org>; Tue,  2 Jul 2013 03:07:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=4I7XQJTpRLzEh8UxTIJWs2rwQCnGRtb1MKNQlHxrdyU=; b=SOLfhEitjTS/CTHTRhRV1dBgvop98qu5rtsO7+KPs8jiD7ZuHys/NyRTeL4XEjTDkHGFyY2jiLbOsgh+usU/cyPJor1Dk4zO2vSfQ3dkDkkO2niJRAB60X67cChk11jmEpWuCYVJYHdQkaHRT2mWA8d1M++/3IFxmkPPHsqcjm0=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r62A7o1U027795-r62A7o1W027795 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL) for <dnsop@ietf.org>; Tue, 2 Jul 2013 12:07:50 +0200
Received: from KAHUBCAS1.SIDN.local (192.168.2.41) by kahubcasn02.SIDN.local (192.168.2.74) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 2 Jul 2013 12:07:49 +0200
Received: from [94.198.152.214] (94.198.152.214) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 2 Jul 2013 12:07:49 +0200
Message-ID: <51D2A674.4040002@sidn.nl>
Date: Tue, 2 Jul 2013 12:07:48 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: <dnsop@ietf.org>
References: <20130701214044.559.35489.idtracker@ietfa.amsl.com> <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net>
In-Reply-To: <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 10:07:56 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 01-07-13 23:43, Warren Kumari schreef:
> Hi there,
> 
> We would like to draw your attention to a new draft.

I like this draft and concept, but how new is it?
It's good to be documented though.

I feel like when a recursive resolver has implemented HAMMER, and
HAMMER_TIME is set to zero, we have an existing sticky resolver.

One thing that fails though for this analogy to be complete, is how
iterative the "cache fill" query will be.
If a record from a zone is about to expire, but it still has a valid
NS set for that zone in it's cache, will it ignore or use that NS set
to issue the iterative query?
If it does use it, thereby being a full sticky resolver, it will
create less DNS traffic for static delegated zones, as it does not hit
the parent again.
If it doesn't, and ignores the NS set for the zone in it's cache, and
re-queries the parent, it will hit the parent harder than when it did
not implement HAMMER, and probably create more DNS traffic than
without HAMMER.

I feel this needs to be clarified in the draft.


- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  M: +31 6 23368970
Mailto: antoin.verschuren@sidn.nl
XMPP: antoin.verschuren@jabber.sidn.nl
HTTP://www.sidn.nl/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJR0qZwAAoJEDqHrM883AgnjXwH/1iXPQM8YGj1AlZ13OSaRReC
5yPkzpOz0mnP3gGI9KBjM6iu8W2xUn1urxU3P0i0Ix4L7IXm1tu5T4U5L+YlkdRD
XYqWD/RzPObQqeyZ9YnMZRXXAtf2jXOhTYmFyQNgCkyjRTKsxJ8lEGU9OXLzptLU
fE1536L+65+h+4XXeJ4OCYcVb3QA0TnMofjurWg/TM8zbtx11/COO63EbTAh1fnx
xevpFO7ZQl5a2XNFZMlL3suPhuAwMH9drfr1QGXPS+w4b6HPwSuV6FSs1V2y+Uq0
8iESFnCGCc1qM7+3hFZoOhdiyniJv/tGt+HvzrpHGJrnYzZMjz/CLyTlzPxPyq0=
=SCyx
-----END PGP SIGNATURE-----

From woolf@isc.org  Tue Jul  2 06:10:40 2013
Return-Path: <woolf@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C48AC21F9BBF for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 06:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCkAYJJRezkd for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 06:10:34 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id E031821F9A98 for <dnsop@ietf.org>; Tue,  2 Jul 2013 06:10:33 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 2DFD7C94AF; Tue,  2 Jul 2013 13:10:20 +0000 (UTC) (envelope-from woolf@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1372770627; bh=zwH88wgOd+NExpDOyddNXR2dxNtAI3yVSlrd9H7Oqm0=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=PVYpm+VYcpn1P7L0B+p32FY+xKCvtQNrVAm9wLD8ENWZpE5+/tnBL5yGCanzrZqmx o1ZJvroMmkJP8yGVd2LaYymFz//DPt5lhkA7GRgciL6ojhangqsN0aSGwHH2rD96dN zUD3C2hR2sp2PvrBwXaczPGYQmXOJa+K6OhVN8Ak=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Tue,  2 Jul 2013 13:10:20 +0000 (UTC) (envelope-from woolf@isc.org)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id AFBDF1600DC; Tue,  2 Jul 2013 13:11:58 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 7Hj1TvW_1Vhx; Tue,  2 Jul 2013 13:11:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 390971600DB; Tue,  2 Jul 2013 13:11:58 +0000 (UTC)
X-Virus-Scanned: amavisd-new at zmx1.isc.org
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id NmOPjKCHb1YJ; Tue,  2 Jul 2013 13:11:58 +0000 (UTC)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net [24.63.89.87]) by zmx1.isc.org (Postfix) with ESMTPSA id D4DA7160082; Tue,  2 Jul 2013 13:11:57 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Suzanne Woolf <woolf@isc.org>
In-Reply-To: <51D2A674.4040002@sidn.nl>
Date: Tue, 2 Jul 2013 09:10:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CA24CD2-910E-460B-AD1C-8316A44E53E7@isc.org>
References: <20130701214044.559.35489.idtracker@ietfa.amsl.com> <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net> <51D2A674.4040002@sidn.nl>
To: Antoin Verschuren <antoin.verschuren@sidn.nl>
X-Mailer: Apple Mail (2.1508)
X-DCC--Metrics: post.isc.org; whitelist
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 13:10:40 -0000

Hi Antoin,

On Jul 2, 2013, at 6:07 AM, Antoin Verschuren =
<antoin.verschuren@sidn.nl> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Op 01-07-13 23:43, Warren Kumari schreef:
>> Hi there,
>>=20
>> We would like to draw your attention to a new draft.
>=20
> I like this draft and concept, but how new is it?
> It's good to be documented though.

Not to speak for Warren, but this is why I was willing to work on a =
draft.

> I feel like when a recursive resolver has implemented HAMMER, and
> HAMMER_TIME is set to zero, we have an existing sticky resolver.
>=20

This is the idea, yes.=20

> One thing that fails though for this analogy to be complete, is how
> iterative the "cache fill" query will be.
> If a record from a zone is about to expire, but it still has a valid
> NS set for that zone in it's cache, will it ignore or use that NS set
> to issue the iterative query?
> If it does use it, thereby being a full sticky resolver, it will
> create less DNS traffic for static delegated zones, as it does not hit
> the parent again.
> If it doesn't, and ignores the NS set for the zone in it's cache, and
> re-queries the parent, it will hit the parent harder than when it did
> not implement HAMMER, and probably create more DNS traffic than
> without HAMMER.
>=20
> I feel this needs to be clarified in the draft.

This is the other reason for a draft :)=20

I know this has been in the field in various forms, but AFAIK those =
questions haven't really
been asked across teams of implementors or groups of operators.

If they have, I'm happy to reduce my own ignorance and others' by =
documenting accordingly.


Suzanne



From ed.lewis@neustar.biz  Tue Jul  2 06:44:12 2013
Return-Path: <ed.lewis@neustar.biz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BE821F90DC for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 06:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.868
X-Spam-Level: 
X-Spam-Status: No, score=-101.868 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFDgUrS2M2bO for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 06:44:08 -0700 (PDT)
Received: from smtp205.dfw.emailsrvr.com (smtp205.dfw.emailsrvr.com [67.192.241.205]) by ietfa.amsl.com (Postfix) with ESMTP id E607D21F9057 for <dnsop@ietf.org>; Tue,  2 Jul 2013 06:44:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp20.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id A98E7258222; Tue,  2 Jul 2013 09:44:06 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp20.relay.dfw1a.emailsrvr.com (Authenticated sender: edlewis-AT-ogud.com) with ESMTPSA id 293FD258134;  Tue,  2 Jul 2013 09:44:05 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A240F3C7-03BD-4F86-910D-5AD46A751A63"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net>
Date: Tue, 2 Jul 2013 09:44:12 -0400
Message-Id: <2F6C8A31-75B6-44F6-8CCD-F6EA7FEECB5C@neustar.biz>
References: <20130701214044.559.35489.idtracker@ietfa.amsl.com> <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1283)
Cc: Edward Lewis <ed.lewis@neustar.biz>
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 13:44:12 -0000

--Apple-Mail=_A240F3C7-03BD-4F86-910D-5AD46A751A63
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

First, I don't see why this draft exists in the IETF.  How does this =
impact interoperability?

Further, this draft is hinting at a mixed signal.  In an era where =
operators are rushing to deploy RRL because of what appears on the =
surface to be overly aggressive clients, the document is telling cache =
servers that they ought to be (slightly) overly aggressive.  I get that =
this is *slightly* overly aggressive and that the use here is "benign" =
(chuckle if you want), but, well, 131 is still over the limit (of 130 =
kph).  And intent is immaterial when I see a query thrown my way.

Why is this important?  I looked at one popular name, just to pick one =
for the sake of an email message (not a whitepaper).  The TTL on an A =
record is 300 and my dig reported it took 19ms to get a response from an =
authoritative server.  I.e., the domain wants to change the A frequently =
but also has a fast authoritative infrastructure.  19ms is less than =
one-half of one percent of one percent of 300, if I plug that into an =
"efficiency" I'm dividing:

300 / 300.019 =3D 99.993%

I don't see the real-world benefit of this.

On Jul 1, 2013, at 17:43, Warren Kumari wrote:

> Hi there,
>=20
> We would like to draw your attention to a new draft.=20
> If describes a simply optimization that, with minimal to no state, =
keeps popular records in recursive server's caches.=20
>=20
> W
>=20
> Begin forwarded message:
>=20
>> From: internet-drafts@ietf.org
>> Subject: New Version Notification for =
draft-wkumari-dnsop-hammer-00.txt
>> Date: July 1, 2013 5:40:44 PM EDT
>> To: Roy Arends <roy@nominet.org.uk>, Suzanne Woolf <woolf@isc.org>, =
Warren Kumari <warren@kumari.net>
>>=20
>>=20
>> A new version of I-D, draft-wkumari-dnsop-hammer-00.txt
>> has been successfully submitted by Warren Kumari and posted to the
>> IETF repository.
>>=20
>> Filename:	 draft-wkumari-dnsop-hammer
>> Revision:	 00
>> Title:		 Highly Automated Method for Maintaining =
Expiring Records
>> Creation date:	 2013-07-01
>> Group:		 Individual Submission
>> Number of pages: 5
>> URL:             =
http://www.ietf.org/internet-drafts/draft-wkumari-dnsop-hammer-00.txt
>> Status:          =
http://datatracker.ietf.org/doc/draft-wkumari-dnsop-hammer
>> Htmlized:        =
http://tools.ietf.org/html/draft-wkumari-dnsop-hammer-00
>>=20
>>=20
>> Abstract:
>>  This document describes a simple DNS cache optimization which keeps
>>  the most popular records in the DNS cache.
>>=20
>>=20
>=20
> No man is an island, But if you take a bunch of dead guys and tie them =
together, they make a pretty good raft.
>                --Anon.
>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_A240F3C7-03BD-4F86-910D-5AD46A751A63
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>First, I don't see why this draft exists in the IETF. &nbsp;How =
does this impact interoperability?</div><div><br></div><div>Further, =
this draft is hinting at a mixed signal. &nbsp;In an era where operators =
are rushing to deploy RRL because of what appears on the surface to be =
overly aggressive clients, the document is telling cache servers that =
they ought to be (slightly) overly aggressive. &nbsp;I get that this is =
*slightly* overly aggressive and that the use here is "benign" (chuckle =
if you want), but, well, 131 is still over the limit (of 130 kph). =
&nbsp;And intent is immaterial when I see a query thrown my =
way.</div><div><br></div><div>Why is this important? &nbsp;I looked at =
one popular name, just to pick one for the sake of an email message (not =
a whitepaper). &nbsp;The TTL on an A record is 300 and my dig reported =
it took 19ms to get a response from an authoritative server. &nbsp;I.e., =
the domain wants to change the A frequently but also has a fast =
authoritative infrastructure. &nbsp;19ms is less than one-half of one =
percent of one percent of 300, if I plug that into an "efficiency" I'm =
dividing:</div><div><br></div><div>300 / 300.019 =3D =
99.993%</div><div><br></div><div>I don't see the real-world benefit of =
this.</div><div><br></div><div><div><div><div>On Jul 1, 2013, at 17:43, =
Warren Kumari wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Hi =
there,<br><br>We would like to draw your attention to a new draft. =
<br>If describes a simply optimization that, with minimal to no state, =
keeps popular records in recursive server's caches. =
<br><br>W<br><br>Begin forwarded message:<br><br><blockquote =
type=3D"cite">From: <a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br><=
/blockquote><blockquote type=3D"cite">Subject: New Version Notification =
for draft-wkumari-dnsop-hammer-00.txt<br></blockquote><blockquote =
type=3D"cite">Date: July 1, 2013 5:40:44 PM =
EDT<br></blockquote><blockquote type=3D"cite">To: Roy Arends &lt;<a =
href=3D"mailto:roy@nominet.org.uk">roy@nominet.org.uk</a>&gt;, Suzanne =
Woolf &lt;<a href=3D"mailto:woolf@isc.org">woolf@isc.org</a>&gt;, Warren =
Kumari &lt;<a =
href=3D"mailto:warren@kumari.net">warren@kumari.net</a>&gt;<br></blockquot=
e><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">A new version =
of I-D, draft-wkumari-dnsop-hammer-00.txt<br></blockquote><blockquote =
type=3D"cite">has been successfully submitted by Warren Kumari and =
posted to the<br></blockquote><blockquote type=3D"cite">IETF =
repository.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Filename:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
draft-wkumari-dnsop-hammer<br></blockquote><blockquote =
type=3D"cite">Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> 00<br></blockquote><blockquote =
type=3D"cite">Title:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> Highly Automated Method for =
Maintaining Expiring Records<br></blockquote><blockquote =
type=3D"cite">Creation date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> =
2013-07-01<br></blockquote><blockquote type=3D"cite">Group:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
Individual Submission<br></blockquote><blockquote type=3D"cite">Number =
of pages: 5<br></blockquote><blockquote type=3D"cite">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a=
 =
href=3D"http://www.ietf.org/internet-drafts/draft-wkumari-dnsop-hammer-00.=
txt">http://www.ietf.org/internet-drafts/draft-wkumari-dnsop-hammer-00.txt=
</a><br></blockquote><blockquote type=3D"cite">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-wkumari-dnsop-hammer">http:/=
/datatracker.ietf.org/doc/draft-wkumari-dnsop-hammer</a><br></blockquote><=
blockquote type=3D"cite">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-wkumari-dnsop-hammer-00">http://t=
ools.ietf.org/html/draft-wkumari-dnsop-hammer-00</a><br></blockquote><bloc=
kquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Abstract:<br></blockquote><blockquote type=3D"cite"> =
&nbsp;This document describes a simple DNS cache optimization which =
keeps<br></blockquote><blockquote type=3D"cite"> &nbsp;the most popular =
records in the DNS cache.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>No man is an island, But if you take =
a bunch of dead guys and tie them together, they make a pretty good =
raft.<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;--Anon.<br><br><br>_______________________________________=
________<br>DNSOP mailing list<br><a =
href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/dnsop<br></div></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></div></div></body></html>=

--Apple-Mail=_A240F3C7-03BD-4F86-910D-5AD46A751A63--

From paul.hoffman@vpnc.org  Tue Jul  2 07:06:34 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB6F21F9DD0 for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 07:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bGTEV5PIwajb for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 07:06:34 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1507121F9D4D for <dnsop@ietf.org>; Tue,  2 Jul 2013 07:06:34 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r62E6MM0003923 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Jul 2013 07:06:23 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51D26C01.1010508@nlnetlabs.nl>
Date: Tue, 2 Jul 2013 07:06:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F47CAF1F-7D27-43BC-819A-970FDAC19417@vpnc.org>
References: <20130702014438.15013.qmail@joyce.lan> <51D26C01.1010508@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 14:06:34 -0000

On Jul 1, 2013, at 10:58 PM, Matthijs Mekking <matthijs@NLnetLabs.nl> =
wrote:

> This sounds a lot like prefetch in unbound, and the configuration =
option
> gives some analysis on increased traffic.
>=20
> prefetch: <yes or no>
>     If yes, message cache elements are prefetched before they expire
>     to  keep  the  cache  up to date.  Default is no.  Turning it on
>     gives about 10 percent more traffic and load on the machine, but
>     popular items do not expire from the cache.

I thought unbound's prefetch kept the cache full all the time, not just =
when a nearly-expired name is gotten from the cache. HAMMER specifically =
grabs only when a name is used again close to its expiration. Or am I =
misunderstanding the unbound documentation?

--Paul Hoffman=

From paul.hoffman@vpnc.org  Tue Jul  2 08:06:43 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E82221F9F7D for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 08:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BmlkuGZ3ZkMB for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 08:06:42 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6E27421F9F73 for <dnsop@ietf.org>; Tue,  2 Jul 2013 08:06:42 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r62F6cZo005400 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Jul 2013 08:06:39 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <2F6C8A31-75B6-44F6-8CCD-F6EA7FEECB5C@neustar.biz>
Date: Tue, 2 Jul 2013 08:06:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF9C5CB4-0C0F-4732-A5E0-CFFEBD1565F1@vpnc.org>
References: <20130701214044.559.35489.idtracker@ietfa.amsl.com> <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net> <2F6C8A31-75B6-44F6-8CCD-F6EA7FEECB5C@neustar.biz>
To: Edward Lewis <Ed.Lewis@neustar.biz>
X-Mailer: Apple Mail (2.1508)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 15:06:43 -0000

On Jul 2, 2013, at 6:44 AM, Edward Lewis <Ed.Lewis@neustar.biz> wrote:

> First, I don't see why this draft exists in the IETF.  How does this =
impact interoperability?

There are many drafts and RFCs produced by the IETF that do not "impact =
interoperability". This document describes an operational issue. That =
seems kind of appropriate for the DNSOP WG, yes?

> Further, this draft is hinting at a mixed signal.  In an era where =
operators are rushing to deploy RRL because of what appears on the =
surface to be overly aggressive clients, the document is telling cache =
servers that they ought to be (slightly) overly aggressive.  I get that =
this is *slightly* overly aggressive and that the use here is "benign" =
(chuckle if you want), but, well, 131 is still over the limit (of 130 =
kph).  And intent is immaterial when I see a query thrown my way.

RRL is being deployed because of botnets, which are not clients at all: =
they simply use the DNS protocol. The draft is not for things that are =
overly aggressive at all.

> Why is this important?  I looked at one popular name, just to pick one =
for the sake of an email message (not a whitepaper).  The TTL on an A =
record is 300 and my dig reported it took 19ms to get a response from an =
authoritative server.  I.e., the domain wants to change the A frequently =
but also has a fast authoritative infrastructure.  19ms is less than =
one-half of one percent of one percent of 300, if I plug that into an =
"efficiency" I'm dividing:
>=20
> 300 / 300.019 =3D 99.993%
>=20
> I don't see the real-world benefit of this.

Fine: you don't need implement it. There are enterprise environments =
where the round-trip times are more significant to them than they seem =
to you in your enterprise environment.

--Paul Hoffman=

From ed.lewis@neustar.biz  Tue Jul  2 08:59:25 2013
Return-Path: <ed.lewis@neustar.biz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 262A221F925A for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 08:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.202
X-Spam-Level: 
X-Spam-Status: No, score=-101.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEw7rr3yjkMS for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 08:59:20 -0700 (PDT)
Received: from smtp109.ord1c.emailsrvr.com (smtp109.ord1c.emailsrvr.com [108.166.43.109]) by ietfa.amsl.com (Postfix) with ESMTP id 1444821F9246 for <dnsop@ietf.org>; Tue,  2 Jul 2013 08:59:20 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 9C368980C5; Tue,  2 Jul 2013 11:59:19 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: edlewis-AT-ogud.com) with ESMTPSA id B1399981D9;  Tue,  2 Jul 2013 11:59:10 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_BF3C2EDD-7A6B-4EA4-8454-44B4FAFDB800"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <CF9C5CB4-0C0F-4732-A5E0-CFFEBD1565F1@vpnc.org>
Date: Tue, 2 Jul 2013 11:59:19 -0400
Message-Id: <6B8BBBCD-EE4E-439E-94DB-6E15CDA8477F@neustar.biz>
References: <20130701214044.559.35489.idtracker@ietfa.amsl.com> <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net> <2F6C8A31-75B6-44F6-8CCD-F6EA7FEECB5C@neustar.biz> <CF9C5CB4-0C0F-4732-A5E0-CFFEBD1565F1@vpnc.org>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1283)
Cc: Edward Lewis <ed.lewis@neustar.biz>
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 15:59:25 -0000

--Apple-Mail=_BF3C2EDD-7A6B-4EA4-8454-44B4FAFDB800
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 2, 2013, at 11:06, Paul Hoffman wrote:
> There are many drafts and RFCs produced by the IETF that do not =
"impact interoperability". This document describes an operational issue. =
That seems kind of appropriate for the DNSOP WG, yes?


Since you asked, no.  [0]

I don't see an operational issue, not in the DNS operational sense.  If =
there is an application that is so sensitive to delay, it can pre-fetch =
data as it needs, this doesn't need to be pressed into the =
infrastructure.

As other messages indicate, implementations already do this.  It's fine =
for an individual submission to document what they do, what's the need =
for a WG review/development/stamp of approval?

[0] The charter is wide open to this, still I would say no.  It's worth =
noting that the charter's latest milestone is February 2008.

=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_BF3C2EDD-7A6B-4EA4-8454-44B4FAFDB800
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 2, 2013, at 11:06, Paul Hoffman =
wrote:</div><blockquote type=3D"cite"><div>There are many drafts and =
RFCs produced by the IETF that do not "impact interoperability". This =
document describes an operational issue. That seems kind of appropriate =
for the DNSOP WG, yes?<br></div></blockquote></div><div><br></div>Since =
you asked, no. &nbsp;[0]<div><br></div><div>I don't see an operational =
issue, not in the DNS operational sense. &nbsp;If there is an =
application that is so sensitive to delay, it can pre-fetch data as it =
needs, this doesn't need to be pressed into the =
infrastructure.<br><div><br></div><div>As other messages indicate, =
implementations already do this. &nbsp;It's fine for an individual =
submission to document what they do, what's the need for a WG =
review/development/stamp of approval?</div><div><div><br></div><div>[0] =
The charter is wide open to this, still I would say no. &nbsp;It's worth =
noting that the charter's latest milestone is February =
2008.</div><div><br></div><div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></div></div></div></body></html>=

--Apple-Mail=_BF3C2EDD-7A6B-4EA4-8454-44B4FAFDB800--

From hsantos@isdg.net  Tue Jul  2 11:28:21 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF87D21F9BEB for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 11:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.951
X-Spam-Level: 
X-Spam-Status: No, score=-102.951 tagged_above=-999 required=5 tests=[AWL=-1.216, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DbIrKavF8koP for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 11:28:16 -0700 (PDT)
Received: from ntbbs.santronics.com (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 543E621F9BCF for <dnsop@ietf.org>; Tue,  2 Jul 2013 11:28:15 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2434; t=1372789688; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=eqiby/V ujRYVbCwhTVw/6gyjj1Y=; b=NFC8+hJfJYZMZUOcnIwTEaNDg7U2n/yL5nGxiSM htYHaq5DEE0mnMB4bx7/XDRTft1UJY2dNRxDPJgxsnuDQVIMIIzaj1EBbTLZQN43 MU1gX8R7ETDRsuUNPs+NLSN+mz0o4aShOT3mYf6xGoFoYH1nhcYif6EuqXzInwoD LSNE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for dnsop@ietf.org; Tue, 02 Jul 2013 14:28:08 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3547220029.642.3884; Tue, 02 Jul 2013 14:28:07 -0400
Message-ID: <51D31B0E.2060506@isdg.net>
Date: Tue, 02 Jul 2013 14:25:18 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
References: <20130701214044.559.35489.idtracker@ietfa.amsl.com> <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net>
In-Reply-To: <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 18:28:21 -0000

I like the idea. A fews ago we needed to write a local cache for our 
total system framework to create a single source API query for all of 
our apps within the framework using DNS.  The cache database was 
prepared with a query frequency field (QFF) with the idea in the future 
to come up with come correlation where an TTL override can be used.

In other words, if the QFF is low, then we just follow the TTL time to 
requery an expired recording. If the QFF was high, then this is where a 
"HAMMER" time idea would kick in.

I would venture that the efficiency or payoff of a HAMMER time is lower 
when the TTL is high.  So its payoff comes into play when there are low 
TTL values.

So possibly, what the HAMMER draft can include is a set of boundary 
conditions or TTL range for when the HAMMER time is applicable.  I think 
a formula can be created.

--
HLS


On 7/1/2013 5:43 PM, Warren Kumari wrote:
> Hi there,
>
> We would like to draw your attention to a new draft.
> If describes a simply optimization that, with minimal to no state, keeps popular records in recursive server's caches.
>
> W
>
> Begin forwarded message:
>
>> From: internet-drafts@ietf.org
>> Subject: New Version Notification for draft-wkumari-dnsop-hammer-00.txt
>> Date: July 1, 2013 5:40:44 PM EDT
>> To: Roy Arends <roy@nominet.org.uk>, Suzanne Woolf <woolf@isc.org>, Warren Kumari <warren@kumari.net>
>>
>>
>> A new version of I-D, draft-wkumari-dnsop-hammer-00.txt
>> has been successfully submitted by Warren Kumari and posted to the
>> IETF repository.
>>
>> Filename:	 draft-wkumari-dnsop-hammer
>> Revision:	 00
>> Title:		 Highly Automated Method for Maintaining Expiring Records
>> Creation date:	 2013-07-01
>> Group:		 Individual Submission
>> Number of pages: 5
>> URL:             http://www.ietf.org/internet-drafts/draft-wkumari-dnsop-hammer-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-wkumari-dnsop-hammer
>> Htmlized:        http://tools.ietf.org/html/draft-wkumari-dnsop-hammer-00
>>
>>
>> Abstract:
>>    This document describes a simple DNS cache optimization which keeps
>>    the most popular records in the DNS cache.
>>
>>
>
> No man is an island, But if you take a bunch of dead guys and tie them together, they make a pretty good raft.
>                  --Anon.
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>


From johnl@iecc.com  Tue Jul  2 22:25:44 2013
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E77421F9282 for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 22:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.67
X-Spam-Level: 
X-Spam-Status: No, score=-110.67 tagged_above=-999 required=5 tests=[AWL=0.529, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HlCv9NGLJ8yu for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 22:25:40 -0700 (PDT)
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 EC5DE21F926E for <dnsop@ietf.org>; Tue,  2 Jul 2013 22:25:39 -0700 (PDT)
Received: (qmail 41012 invoked from network); 3 Jul 2013 05:25:39 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Jul 2013 05:25:39 -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=51d3b5d2.xn--btvx9d.k1307; i=johnl@user.iecc.com; bh=pvbA1/ibFUEad9tqovxjZLGW4IHjqxMvnpZddD5Pcys=; b=3E6bXcB0pH1/LIWTjsQDVJaXwnbq5weH5QjU3AZrRpDXvQtFX/5MiDkiybR9joJULJkR9LYltAE9Msq5WHybL0JCEItmFn+esoYTTzoXiYBYXD0XRNgjW8l3fBqzFBuWlrTohAscz1RIPP3vI5Dlb83H9J+UvUa2ekW/s4Ve/1K7Kg+VMBflcsPY4cZvQCZy24+GUXsXfyVsQf1u+7yHpwA6JV1qK752k3D2PL+djmoU8eE8s0qRsSrLj1G4fUiS
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=51d3b5d2.xn--btvx9d.k1307; olt=johnl@user.iecc.com; bh=pvbA1/ibFUEad9tqovxjZLGW4IHjqxMvnpZddD5Pcys=; b=KoO1zgs1sb2mwwsnjGJH5FrKlr1S0M87FU8gfOeg86pN8aqtafuUhMb3tDJyLHgzP7ffx0THR/+/9R6j/HIzG1ySPJNS7R/l8GHxjvaz2HRh0v4KJpaH9MXrc5Hw2oDmHX6KSjkLJXnW4f9oaZvWBQr6SKMJlCPcGhKssWRTCRtJhMr8QaKXNbZN6AO+EdHboy3t7VTA9wPkeczFSrDpMlcYw72I3KN2eNEktOpUz0OADNdpC34QblHzjNadJnnk
Date: 3 Jul 2013 05:25:16 -0000
Message-ID: <20130703052516.23932.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <CF9C5CB4-0C0F-4732-A5E0-CFFEBD1565F1@vpnc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: paul.hoffman@vpnc.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 05:25:44 -0000

>> I don't see the real-world benefit of this.
>
>Fine: you don't need implement it. There are enterprise environments where the round-trip times are more
>significant to them than they seem to you in your enterprise environment.

I'm still trying to figure out how I could tell whether prefetch makes
things better or worse, since the main thing I've learned from the few
DNS cache simulations I've done is that intuition is not a good guide.

I'm running unbound with verbosity 1 logging.  Any suggestions?




From dougb@dougbarton.us  Tue Jul  2 22:53:25 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E676E21F9CE8 for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 22:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.29
X-Spam-Level: 
X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECwhC3FWhgWt for <dnsop@ietfa.amsl.com>; Tue,  2 Jul 2013 22:53:25 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDD921F9CE1 for <dnsop@ietf.org>; Tue,  2 Jul 2013 22:53:25 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id D5E3C22B13; Wed,  3 Jul 2013 05:53:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1372830804; bh=PWwgdyn8Max8ldSW/r9cUukvqgAE2Vqe0FYnKXcLKCY=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=lPO65KktU7RXRGPBxNKzAFluKdaGWtsvrTfi0edbmVk6ZOBioWfuj6mCIuHjLLi0l JpvWgjzTWg5rBe7GoB97YfRJdONZrQo0RQNuLTcSqUhbl3J5sERJGH0zhhLANNZOjD v1EPf8j4ZkZmfraSyHJFJNF1QVaCc0e8r0DFMepw=
Message-ID: <51D3BC53.1090000@dougbarton.us>
Date: Tue, 02 Jul 2013 22:53:23 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
References: <20130703052516.23932.qmail@joyce.lan>
In-Reply-To: <20130703052516.23932.qmail@joyce.lan>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dnsop@ietf.org, paul.hoffman@vpnc.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 05:53:26 -0000

On 07/02/2013 10:25 PM, John Levine wrote:
>>> I don't see the real-world benefit of this.
>>
>> Fine: you don't need implement it. There are enterprise environments where the round-trip times are more
>> significant to them than they seem to you in your enterprise environment.
>
> I'm still trying to figure out how I could tell whether prefetch makes
> things better or worse, since the main thing I've learned from the few
> DNS cache simulations I've done is that intuition is not a good guide.
>
> I'm running unbound with verbosity 1 logging.  Any suggestions?

Well, first you have to define "better" and "worse" for your 
environment. :)  (And no, I'm not being snarky.)




From jaap@NLnetLabs.nl  Wed Jul  3 01:04:08 2013
Return-Path: <jaap@NLnetLabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A295B21F9CC8 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 01:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P6zV84KpUdT8 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 01:04:08 -0700 (PDT)
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2001:7b8:206:1:222:4dff:fe55:4ccb]) by ietfa.amsl.com (Postfix) with ESMTP id EF45A21F9CC7 for <dnsop@ietf.org>; Wed,  3 Jul 2013 01:04:07 -0700 (PDT)
Received: from bela.nlnetlabs.nl (localhost [IPv6:::1]) by bela.nlnetlabs.nl (8.14.7/8.14.7) with ESMTP id r63844RB065998; Wed, 3 Jul 2013 10:04:05 +0200 (CEST) (envelope-from jaap@NLnetLabs.nl)
Authentication-Results: bela.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
Message-Id: <201307030804.r63844RB065998@bela.nlnetlabs.nl>
To: "John Levine" <johnl@taugh.com>
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
In-reply-to: <20130703052516.23932.qmail@joyce.lan>
References: <20130703052516.23932.qmail@joyce.lan>
Comments: In-reply-to "John Levine" <johnl@taugh.com> message dated "03 Jul 2013 05:25:16 -0000."
Date: Wed, 03 Jul 2013 10:04:04 +0200
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.4.3 (bela.nlnetlabs.nl [IPv6:::1]); Wed, 03 Jul 2013 10:04:06 +0200 (CEST)
Cc: dnsop@ietf.org, paul.hoffman@vpnc.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 08:04:08 -0000

    I'm still trying to figure out how I could tell whether prefetch
    makes things better or worse, since the main thing I've learned
    from the few DNS cache simulations I've done is that intuition is
    not a good guide.

The net effect it will have is that the average latency querying for
the prefetched domains will be lower at the cost of a (max 10% with
current values) bigger cache size and added traffic.

    I'm running unbound with verbosity 1 logging. Any suggestions?

Verbosity 4 will give details and lots of debugging info as well so
you don't really want to run like that for a long time.

My intuition was (based on experiences from measurements on caches)
that the effect wouldn't been spectacular. That was confirmed by the
people who asked us for it.

	jaap

From bdickson@verisign.com  Wed Jul  3 08:44:49 2013
Return-Path: <bdickson@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1794011E80D9 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 08:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9JparOWJO8FK for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 08:44:43 -0700 (PDT)
Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29]) by ietfa.amsl.com (Postfix) with ESMTP id 3EFB011E81F2 for <dnsop@ietf.org>; Wed,  3 Jul 2013 08:44:13 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob112.postini.com ([64.18.5.12]) with SMTP ID DSNKUdRGyXyyVS+5H1LtxVu2KWlHMMfK6bbp@postini.com; Wed, 03 Jul 2013 08:44:40 PDT
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id r63Fi5W2021515 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Jul 2013 11:44:05 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 3 Jul 2013 11:44:05 -0400
From: "Dickson, Brian" <bdickson@verisign.com>
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>, John Levine <johnl@taugh.com>
Thread-Topic: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
Thread-Index: AQHOeAQljPJLaEaaBkGRt+EDPjX57Q==
Date: Wed, 3 Jul 2013 15:44:04 +0000
Message-ID: <CDF9B069.B6C0%bdickson@verisign.com>
In-Reply-To: <201307030804.r63844RB065998@bela.nlnetlabs.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0E403C69D7549D42AE2AE49E4F7C04C1@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, "paul.hoffman@vpnc.org" <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 15:44:50 -0000

On 7/3/13 4:04 AM, "Jaap Akkerhuis" <jaap@NLnetLabs.nl> wrote:

>
>
>    I'm still trying to figure out how I could tell whether prefetch
>    makes things better or worse, since the main thing I've learned
>    from the few DNS cache simulations I've done is that intuition is
>    not a good guide.
>
>The net effect it will have is that the average latency querying for
>the prefetched domains will be lower

I've seen at least one other comment about average latency.

Two observations on this:
(1) Average is probably not a useful measure here (nor what users
experience - they either get a cache hit or a miss.)
(2) Comparing anecdotal data isn't likely meaningful in the context of
this discussion.

The effect of implementing & using HAMMER is that pre-re-fetch of
sufficiently popular domains will occur.

However, it should be noted that (a) there are a lot of resolvers on the
planet, and (b) what is popular does not necessarily correspond to
topological proximity.

In other words, for a given resolver, there is no guarantee that any
particular popular domain will have low latency (and thus that the latency
to the user will be low).

The impact of pre-re-fetch will be to constrain the upper limit on client
resolution latency, and thus to flatten the client latency distribution
curve.

Additionally, the likelihood of having to retry is reduced (because the
only possible loss would be client-resolver, rather than both
client-resolver and resolver-authority), further flattening the curve
(regardless of how little, the upper bound of latency is reduced).

So, I am in favor of this being implemented, and in favor of it being
memorialized in an RFC (regardless of WG or individual, standard or
informational).

Brian


From wjhns1@hardakers.net  Wed Jul  3 09:02:19 2013
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 339F911E81CA for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 09:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l2Fh5OTyOU+M for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 09:02:18 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3319011E81E4 for <dnsop@ietf.org>; Wed,  3 Jul 2013 09:01:52 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:48d8:a8e1:e3ed:504b]) by mail.hardakers.net (Postfix) with ESMTPSA id 6F4482BC51; Wed,  3 Jul 2013 09:01:51 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Antoin Verschuren <Antoin.Verschuren@sidn.nl>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <2310CDA9-DFB9-4F57-8DB1-F18B7B5F6874@kumari.net> <ED84A6DE40A3EE48BFB5CEC46D007D9655586F27@kambx2.SIDN.local>
Date: Wed, 03 Jul 2013 09:01:50 -0700
In-Reply-To: <ED84A6DE40A3EE48BFB5CEC46D007D9655586F27@kambx2.SIDN.local> (Antoin Verschuren's message of "Mon, 1 Jul 2013 15:16:50 +0000")
Message-ID: <0lmwq3hbtd.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] draft-hardaker-dnsop-csync-00.txt versus draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 16:02:19 -0000

Antoin Verschuren <Antoin.Verschuren@sidn.nl> writes:

> In simple words, what do I do as a parent (or parental agent) when I
> recieve information over the DNS that conflicts with data I receive
> over the administrative channel. Which data should I follow.

Well, ordering really matters for that, right?  I mean there are two
choices:

1) I detect a change in DNS data and then receive an operational change
   via HTTP or some other mechanism.

   In this case, I think it's fairly clear that the out-of-band HTTP
   configuration should always supersede.

2) I receive the HTTP request and then notice a DNS change.

   This case also looks fairly straight forward (but keep reading), as
   clearly you act on the HTTP request and then a second request (via
   DNS) comes in second.  So you act then on it.

   The only problem with this approach is when an admin really isn't
   thinking, publishing something in DNS to make a change, realizes he
   wants to act immediately and publishes something through the HTTP
   form interface that *conflicts* with the DNS publish.  The HTTP poke
   goes through immediately, because it's client initiated, so the DNS
   pull from the parent could come *after* the http submission even
   though it was published first.  If the admin failed to revoke the DNS
   CSYNC (or whatever) request when in the process of updating over
   http, that's a mistake on their part (if it conflicts at least).

   I'd argue that we shouldn't worry about solving this case, as it's
   clearly a publication of conflict of information.  We could warn
   against it in the operational guidance section though.

> It was stated that when a parent is requesting DNSKEY instead of DS,
> and the parent calculates the DS, the disadvantage is that the child
> cannot choose the digest algorithm.

You're right the parent can offer static preferences configured
elsewhere.  But it's not done in-band.  There are rumors (which I
haven't verified) that some parents dictate what algorithms they use and
the child has no choice.  I'm sure there are others that have a set of
checkboxes, which lets the child configure the parent's engine too.

(and many more parents, of course, allow for DS uploading leaving
everything in the hands of the child).

> I fail to see how publishing a DS in a CDS record for your standby key
> is much more safer from publishing the DNSKEY of your standby key.

I agree with you, assuming you can publish your DNSKEY as a separate
record (or else people may read it, cache it, memorize it, run tests
with it, etc).  But no matter how much I agree with you it won't stop
others from wanting an oxymoron: "the private public key".
-- 
Wes Hardaker
Parsons

From warren@kumari.net  Wed Jul  3 10:30:35 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A447F21F9A29 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 10:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XCN7mmFAEq9z for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 10:30:25 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7021221F8952 for <dnsop@ietf.org>; Wed,  3 Jul 2013 10:30:24 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id C5CBB1B407D8; Wed,  3 Jul 2013 13:30:23 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51D26C01.1010508@nlnetlabs.nl>
Date: Wed, 3 Jul 2013 13:30:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F47366EE-A6D0-4041-ADC0-8D7369D7E0C7@kumari.net>
References: <20130702014438.15013.qmail@joyce.lan> <51D26C01.1010508@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@nlnetlabs.nl>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 17:30:35 -0000

On Jul 2, 2013, at 1:58 AM, Matthijs Mekking <matthijs@nlnetlabs.nl> =
wrote:

> This sounds a lot like prefetch in unbound, and the configuration =
option
> gives some analysis on increased traffic.
> prefetch: <yes or no>
>     If yes, message cache elements are prefetched before they expire
>     to  keep  the  cache  up to date.  Default is no.  Turning it on
>     gives about 10 percent more traffic and load on the machine, but
>     popular items do not expire from the cache.

Doh, sorry, I was not aware that Unbound did this. I'd like to recognize =
this in the draft, any idea who actually suggested it / added it to the =
code?
>=20
>=20
> Also, if the original TTL of the RR is less than STOP * HAMMER_TIME =
then
> the cache entry, it cannot be used anymore and the resolver should
> "Break it down".
>=20

I got a few off-list questions asking about the odd naming (and I also =
remember the IETF Diversity thread on Discuss).=20
For folk who have no idea what the hell we are on about:
http://www.youtube.com/watch?v=3DGbKAaSf6e10
http://www.youtube.com/watch?v=3DotCpCn0l4Wo



> Best regards,
> Matthijs
>=20
> On 07/02/2013 03:44 AM, John Levine wrote:
>>> We would like to draw your attention to a new draft.=20
>>=20
>> It looks like it should work, assuming that your cache uses the
>> existing logic to remember queries in progress so it doesn't hammer a
>> record that's already in the process of being refetched.

Hmm. Probably worth mentioning.

>>=20
>> My main observation is that I have no idea what the tradeoffs are
>> between the increased DNS traffic and faster responses to clients.
>> Have you done simulations or live experiments?
Nope.

This doesn't really change the average very much, but it should help =
decrease the jitter / spikes for the unlucky few who hit the resolver =
just as the cache entry expires.
The draft specified HAMMER_TIME as a time, not a percentage because:
A: I wanted to use the phrase HAMMER_TIME (and STOP HAMMER_TIME!) :-P
B: The main "issue" that the draft tries to solve is increased =
resolution times for the unlucky few who hit the resolver when the =
record has just expired. In order to decrease the added load caused by =
this, I chose a default that is somewhat longer than a "bad" resolution =
experience with a few failures along the way.
C: STOP was added to prevent doing a cache-fill request on every =
recursive request for records that have TTL of < HAMMER_TIME.
D: I was (tilting at windmills and) trying to get folk to not use TTLs =
of < a few seconds in the records :-)

=46rom reading the unbound prefetch thing, I suspect maybe a better =
solution would be:
HAMMER_TIME defaults to 2 (or 1 or something) seconds
If the original TTL is < HAMMER_TIME, then only do the cache-fill when =
the TTL is 10% of the original TTL.

This means that:
if HAMMER_TIME is 2 and the original TTL is 600 seconds -- the auth =
servers will see approximately 0.3% additional traffic.
if HAMMER_TIME is 2 and the original TTL is 60 seconds -- the auth =
servers will see approximately 3.3% additional traffic.
if HAMMER_TIME is 2 and the original TTL is 1 seconds -- the auth =
servers will see approximately 10% additional traffic.


W


>>=20
>> R's,
>> John
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20

--
"Go on, prove me wrong. Destroy the fabric of the universe. See if I =
care."  -- Terry Prachett=20



From warren@kumari.net  Wed Jul  3 10:36:12 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D7421F9CD7 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 10:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P15PJu3RQ+VB for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 10:36:07 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id A374121F9CD4 for <dnsop@ietf.org>; Wed,  3 Jul 2013 10:36:02 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id 4FE611B407D8; Wed,  3 Jul 2013 13:36:01 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_1C4C485A-8167-4736-92B7-DF172F04A068"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51D2A674.4040002@sidn.nl>
Date: Wed, 3 Jul 2013 13:35:52 -0400
Message-Id: <24605594-9FF5-4DB1-BD25-998173B35521@kumari.net>
References: <20130701214044.559.35489.idtracker@ietfa.amsl.com> <13014C34-CAC8-4B5C-BF8C-C16A3770536C@kumari.net> <51D2A674.4040002@sidn.nl>
To: Antoin Verschuren <antoin.verschuren@sidn.nl>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 17:36:12 -0000

--Apple-Mail=_1C4C485A-8167-4736-92B7-DF172F04A068
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 2, 2013, at 6:07 AM, Antoin Verschuren =
<antoin.verschuren@sidn.nl> wrote:

> Signed PGP part
> Op 01-07-13 23:43, Warren Kumari schreef:
> > Hi there,
> >=20
> > We would like to draw your attention to a new draft.
>=20
> I like this draft and concept, but how new is it?

Not very :-)

> It's good to be documented though.
>=20

Thank you! INd a(and RFCs) to me seem like a reasonable place to =
document implementation advice, warnings, etc, regardless of if they =
require protocol change or affect interoperability.

> I feel like when a recursive resolver has implemented HAMMER, and
> HAMMER_TIME is set to zero, we have an existing sticky resolver.

Yup.=20

>=20
> One thing that fails though for this analogy to be complete, is how
> iterative the "cache fill" query will be.
> If a record from a zone is about to expire, but it still has a valid
> NS set for that zone in it's cache, will it ignore or use that NS set
> to issue the iterative query?
> If it does use it, thereby being a full sticky resolver, it will
> create less DNS traffic for static delegated zones, as it does not hit
> the parent again.
> If it doesn't, and ignores the NS set for the zone in it's cache, and
> re-queries the parent, it will hit the parent harder than when it did
> not implement HAMMER, and probably create more DNS traffic than
> without HAMMER.
>=20
> I feel this needs to be clarified in the draft.

Yup, good point.
W

>=20
>=20
> - --=20
> Antoin Verschuren
>=20
> Technical Policy Advisor SIDN
> Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands
>=20
> P: +31 26 3525500  M: +31 6 23368970
> Mailto: antoin.verschuren@sidn.nl
> XMPP: antoin.verschuren@jabber.sidn.nl
> HTTP://www.sidn.nl/
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20

--
I don't think the execution is relevant when it was obviously a bad idea =
in the first place.
This is like putting rabid weasels in your pants, and later expressing =
regret at having chosen those particular rabid weasels and that pair of =
pants.=20
   ---maf

Warren Kumari
warren@kumari.net



--Apple-Mail=_1C4C485A-8167-4736-92B7-DF172F04A068
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-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)

iEYEARECAAYFAlHUYQAACgkQ/sGA6gkxszjO1QCgneBVAo+lK5BFb8wOHLFaQUwd
O6MAnivrP059Yb6ddh1GGx5pW/q8zYvb
=5vqw
-----END PGP SIGNATURE-----

--Apple-Mail=_1C4C485A-8167-4736-92B7-DF172F04A068--

From hsantos@isdg.net  Wed Jul  3 11:02:43 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C580E21F9D78 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 11:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=-0.811, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O54UurpCpkvd for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 11:02:39 -0700 (PDT)
Received: from mail.santronics.com (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id BB48721F9D7C for <dnsop@ietf.org>; Wed,  3 Jul 2013 11:02:36 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4010; t=1372874541; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=3/X3KxH lX+I5VcqeAXSNRNmnN3Q=; b=wIwMvk31RjHGMoozmmnmRKQicbLDXiguUbzUd7L Q/sfz43QUtw84LIxy2/86OnWqRKdX4fqIj3UvjIweT1EKisi57va9HcS2T/enTG4 F/0Kmrk+nWNHDtgsFnruhF/E9II78cjNOmFOZK4oQd+g0146HOTT1JUWwQ5Wyzwe Gq04=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for dnsop@ietf.org; Wed, 03 Jul 2013 14:02:21 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3632072327.1690.5904; Wed, 03 Jul 2013 14:02:20 -0400
Message-ID: <51D46683.2010400@isdg.net>
Date: Wed, 03 Jul 2013 13:59:31 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
References: <20130702014438.15013.qmail@joyce.lan> <51D26C01.1010508@nlnetlabs.nl> <F47366EE-A6D0-4041-ADC0-8D7369D7E0C7@kumari.net>
In-Reply-To: <F47366EE-A6D0-4041-ADC0-8D7369D7E0C7@kumari.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dnsop@ietf.org, Matthijs Mekking <matthijs@nlnetlabs.nl>
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 18:02:43 -0000

well, for a moment, I did have to think about this draft being a joke or 
not.  But the acronym was perfect. :)

On 7/3/2013 1:30 PM, Warren Kumari wrote:
>
> On Jul 2, 2013, at 1:58 AM, Matthijs Mekking <matthijs@nlnetlabs.nl> wrote:
>
>> This sounds a lot like prefetch in unbound, and the configuration option
>> gives some analysis on increased traffic.
>> prefetch: <yes or no>
>>      If yes, message cache elements are prefetched before they expire
>>      to  keep  the  cache  up to date.  Default is no.  Turning it on
>>      gives about 10 percent more traffic and load on the machine, but
>>      popular items do not expire from the cache.
>
> Doh, sorry, I was not aware that Unbound did this. I'd like to recognize this in the draft, any idea who actually suggested it / added it to the code?
>>
>>
>> Also, if the original TTL of the RR is less than STOP * HAMMER_TIME then
>> the cache entry, it cannot be used anymore and the resolver should
>> "Break it down".
>>
>
> I got a few off-list questions asking about the odd naming (and I also remember the IETF Diversity thread on Discuss).
> For folk who have no idea what the hell we are on about:
> http://www.youtube.com/watch?v=GbKAaSf6e10
> http://www.youtube.com/watch?v=otCpCn0l4Wo
>
>
>
>> Best regards,
>> Matthijs
>>
>> On 07/02/2013 03:44 AM, John Levine wrote:
>>>> We would like to draw your attention to a new draft.
>>>
>>> It looks like it should work, assuming that your cache uses the
>>> existing logic to remember queries in progress so it doesn't hammer a
>>> record that's already in the process of being refetched.
>
> Hmm. Probably worth mentioning.
>
>>>
>>> My main observation is that I have no idea what the tradeoffs are
>>> between the increased DNS traffic and faster responses to clients.
>>> Have you done simulations or live experiments?
> Nope.
>
> This doesn't really change the average very much, but it should help decrease the jitter / spikes for the unlucky few who hit the resolver just as the cache entry expires.
> The draft specified HAMMER_TIME as a time, not a percentage because:
> A: I wanted to use the phrase HAMMER_TIME (and STOP HAMMER_TIME!) :-P
> B: The main "issue" that the draft tries to solve is increased resolution times for the unlucky few who hit the resolver when the record has just expired. In order to decrease the added load caused by this, I chose a default that is somewhat longer than a "bad" resolution experience with a few failures along the way.
> C: STOP was added to prevent doing a cache-fill request on every recursive request for records that have TTL of < HAMMER_TIME.
> D: I was (tilting at windmills and) trying to get folk to not use TTLs of < a few seconds in the records :-)
>
>>From reading the unbound prefetch thing, I suspect maybe a better solution would be:
> HAMMER_TIME defaults to 2 (or 1 or something) seconds
> If the original TTL is < HAMMER_TIME, then only do the cache-fill when the TTL is 10% of the original TTL.
>
> This means that:
> if HAMMER_TIME is 2 and the original TTL is 600 seconds -- the auth servers will see approximately 0.3% additional traffic.
> if HAMMER_TIME is 2 and the original TTL is 60 seconds -- the auth servers will see approximately 3.3% additional traffic.
> if HAMMER_TIME is 2 and the original TTL is 1 seconds -- the auth servers will see approximately 10% additional traffic.
>
>
> W
>
>
>>>
>>> R's,
>>> John
>>> _______________________________________________
>>> DNSOP mailing list
>>> DNSOP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dnsop
>>>
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>
> --
> "Go on, prove me wrong. Destroy the fabric of the universe. See if I care."  -- Terry Prachett
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>


From paul.hoffman@vpnc.org  Wed Jul  3 11:41:13 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44F9B11E81F8 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 11:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZtOlagbC7XpD for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 11:41:12 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CBA4011E81F3 for <dnsop@ietf.org>; Wed,  3 Jul 2013 11:41:12 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r63If6oQ058437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 3 Jul 2013 11:41:06 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <F47366EE-A6D0-4041-ADC0-8D7369D7E0C7@kumari.net>
Date: Wed, 3 Jul 2013 11:41:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <011BF8D4-7C92-45C0-B3A4-984FD04729A3@vpnc.org>
References: <20130702014438.15013.qmail@joyce.lan> <51D26C01.1010508@nlnetlabs.nl> <F47366EE-A6D0-4041-ADC0-8D7369D7E0C7@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org, Matthijs Mekking <matthijs@nlnetlabs.nl>
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 18:41:13 -0000

On Jul 3, 2013, at 10:30 AM, Warren Kumari <warren@kumari.net> wrote:

>=20
> On Jul 2, 2013, at 1:58 AM, Matthijs Mekking <matthijs@nlnetlabs.nl> =
wrote:
>=20
>> This sounds a lot like prefetch in unbound, and the configuration =
option
>> gives some analysis on increased traffic.
>> prefetch: <yes or no>
>>    If yes, message cache elements are prefetched before they expire
>>    to  keep  the  cache  up to date.  Default is no.  Turning it on
>>    gives about 10 percent more traffic and load on the machine, but
>>    popular items do not expire from the cache.
>=20
> Doh, sorry, I was not aware that Unbound did this. I'd like to =
recognize this in the draft, any idea who actually suggested it / added =
it to the code?

My question earlier still stands: does Unbound do what HAMMER says =
(waits for a request before refreshing the cache) or does it just =
refresh the cache automatically? The Unbound doc is unclear (at least to =
me).

--Paul Hoffman=

From johnl@iecc.com  Wed Jul  3 14:02:14 2013
Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8138B11E80E1 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 14:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.72
X-Spam-Level: 
X-Spam-Status: No, score=-110.72 tagged_above=-999 required=5 tests=[AWL=0.479, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2CHHwnQS+YvG for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 14:02:10 -0700 (PDT)
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 40BE111E80D3 for <dnsop@ietf.org>; Wed,  3 Jul 2013 14:02:10 -0700 (PDT)
Received: (qmail 62584 invoked from network); 3 Jul 2013 21:02:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Jul 2013 21:02:09 -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=51d49151.xn--3zv.k1307; i=johnl@user.iecc.com; bh=4H2c7fm3I6K7LlUq7mOJahWtk2evBd9GMpmKQGMrUoc=; b=gsWCeOAdoV3+4JY1YphJcKCZQqSCy6HNz8vrsGObQoRadnFDWKzO+EM63mFqxnAAlQPyCZXM8xIfQsY4vQnZB7aOTXFquuUrlC+cja1T7/KcMpPAAwQ/emUzO6Xu5WV63kqXzS4wHrH8ma1gZRAGmlIPIxRmu0yDSRcNXT/17TpzTcAnF22T74LP2gC2BT6ilBcH3rIEoF60Am0pnFj5vkuBJGiEfUWBkHEPbNVnm3hpLWQ6nrmLyKftMR1l/8c8
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=51d49151.xn--3zv.k1307; olt=johnl@user.iecc.com; bh=4H2c7fm3I6K7LlUq7mOJahWtk2evBd9GMpmKQGMrUoc=; b=BAyFk8WWQrbOW1XXJrrhID6OTupgrSvp4IYMVYNA98ELEsKmr0Ue0T+CwBNdYziJjrgPmctJy8pH1qN0Z7+DYMoosdn9p4gRES0BRW7zWVkZ5w8PKJOaAdW5/j28bupw/BhnXWnNBx9Z4w/6lTAiFflzWZC5UD/TR39VBM4Fg6fSjd8niUE68EXU8TyfGgMGNyOPrRtce7uLSYAPS/jra0Q9fig9rnVyE4G+0ME6+Ev6yH12KPCNaKcozp7K15/u
Date: 3 Jul 2013 21:01:47 -0000
Message-ID: <20130703210147.69996.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <011BF8D4-7C92-45C0-B3A4-984FD04729A3@vpnc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: paul.hoffman@vpnc.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 21:02:14 -0000

>>>    If yes, message cache elements are prefetched before they expire
>>>    to  keep  the  cache  up to date.  Default is no.  Turning it on
>>>    gives about 10 percent more traffic and load on the machine, but
>>>    popular items do not expire from the cache.

>My question earlier still stands: does Unbound do what HAMMER says
>(waits for a request before refreshing the cache) or does it just
>refresh the cache automatically? The Unbound doc is unclear (at least
>to me).

If it did it automatically, I'd expect a lot more than 10% more
traffic.  I enabled it on my not terribly busy server and I see
numbers that look like they're in the 1% range:

Jul 03 14:23:21 unbound[40669:0] info: server stats for thread 0: 47798 queries, 20108 answers from cache, 27690 recursions, 242 prefetch
Jul 03 15:23:21 unbound[40669:0] info: server stats for thread 0: 53322 queries, 20319 answers from cache, 33003 recursions, 291 prefetch
Jul 03 16:23:21 unbound[40669:0] info: server stats for thread 0: 55260 queries, 20697 answers from cache, 34563 recursions, 272 prefetch


From paul.hoffman@vpnc.org  Wed Jul  3 14:14:28 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCB721F8904 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 14:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QfrbLjF4Ukme for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 14:14:27 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id E209221F8994 for <dnsop@ietf.org>; Wed,  3 Jul 2013 14:14:16 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r63LEFAI066736 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 3 Jul 2013 14:14:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20130703210147.69996.qmail@joyce.lan>
Date: Wed, 3 Jul 2013 14:14:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFD28A69-40DC-4A6C-B3E7-B35BC655AF7F@vpnc.org>
References: <20130703210147.69996.qmail@joyce.lan>
To: "John Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 21:14:28 -0000

On Jul 3, 2013, at 2:01 PM, "John Levine" <johnl@taugh.com> wrote:

>>>>   If yes, message cache elements are prefetched before they expire
>>>>   to  keep  the  cache  up to date.  Default is no.  Turning it on
>>>>   gives about 10 percent more traffic and load on the machine, but
>>>>   popular items do not expire from the cache.
>=20
>> My question earlier still stands: does Unbound do what HAMMER says
>> (waits for a request before refreshing the cache) or does it just
>> refresh the cache automatically? The Unbound doc is unclear (at least
>> to me).
>=20
> If it did it automatically, I'd expect a lot more than 10% more
> traffic.  I enabled it on my not terribly busy server and I see
> numbers that look like they're in the 1% range:
>=20
> Jul 03 14:23:21 unbound[40669:0] info: server stats for thread 0: =
47798 queries, 20108 answers from cache, 27690 recursions, 242 prefetch
> Jul 03 15:23:21 unbound[40669:0] info: server stats for thread 0: =
53322 queries, 20319 answers from cache, 33003 recursions, 291 prefetch
> Jul 03 16:23:21 unbound[40669:0] info: server stats for thread 0: =
55260 queries, 20697 answers from cache, 34563 recursions, 272 prefetch
>=20

Those are pictures. Source code, or developer assurance, or it didn't =
happen ( to badly bastardize a phrase that the kids these days use ).


From johnl@taugh.com  Wed Jul  3 14:28:22 2013
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B7A211E823D for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 14:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZrPPYaNu5tkh for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 14:28:22 -0700 (PDT)
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 A091911E80F5 for <dnsop@ietf.org>; Wed,  3 Jul 2013 14:28:17 -0700 (PDT)
Received: (qmail 71291 invoked from network); 3 Jul 2013 21:28:17 -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=11678.51d49771.k1307; bh=RDlSYMo0AWX1w4eD4Y1JBuOTNGEHjN4pFyEaLh7sLDU=; b=kNhhHMIGSmKujx2d7pO653SHlHApCw1MN+obEhsalAJVzS5/iUQfD9CLaj2Q0dtrpFjaGTr+E59cfu7hir/fhhMSIK5NfozpUYOCqwtTXD1A8d5ORYIZUCVoa+hjwFCT5ij6BAG+Z4IAq07PmnD1vEIcF/gRDeVP+C4gx90ZnjcTLq0VZstp5JrkqAPNXk//DiDBhOF33D+kU24auWBvNBhuH9ENQmBguqxKx+1Y4tciPDNzjtC+gGewRFj+Dbdz
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=11678.51d49771.k1307; bh=RDlSYMo0AWX1w4eD4Y1JBuOTNGEHjN4pFyEaLh7sLDU=; b=UksvDCm7EHqTUwfH+gwHP9JHreXgX8YquYku96D4JB06ImuC1UH7e2Tgd0UX5bmGVxYc30BU/A2zKZyDMgRbN2MC1Pj2OiHBAWQDnSH+pfF5sdubqCryfcy16KxIpx4VzxMtqeN8/jn/1JdH/ypifMJ2zzo1EW1ruibFBYNu8As44OZ3NOBt42ZNa4NGnvZZ1vMjQP36P3Bm51MBz8QmtxonWMjri/vo39LbmCh4//lhIBHbo56xAi+YaW6Cltc5
Received: (ofmipd 127.0.0.1); 3 Jul 2013 21:27:55 -0000
Date: 3 Jul 2013 17:28:16 -0400
Message-ID: <alpine.BSF.2.00.1307031725370.33980@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>
In-Reply-To: <EFD28A69-40DC-4A6C-B3E7-B35BC655AF7F@vpnc.org>
References: <20130703210147.69996.qmail@joyce.lan> <EFD28A69-40DC-4A6C-B3E7-B35BC655AF7F@vpnc.org>
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] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 21:28:22 -0000

> Those are pictures. Source code, or developer assurance, or it didn't happen ( to badly bastardize a phrase that the kids these days use ).

I looked at the unbound source code.  It prefetches when it's responding 
to a query, code in daemon/worker.c.  The code is considerably complicated 
by defensive code to deal with the situation where the parent of the 
record to be prefetched has changed since the record was originally 
fetched.  (Feel free to check my work.)  That's probably worth mentioning 
in the I-D.

There is a separate option to prefetch DNSSEC key records.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From warren@kumari.net  Wed Jul  3 14:56:40 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F4411E8219 for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 14:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.228
X-Spam-Level: 
X-Spam-Status: No, score=-102.228 tagged_above=-999 required=5 tests=[AWL=-0.229, BAYES_00=-2.599, J_CHICKENPOX_73=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXZVX57GlSTz for <dnsop@ietfa.amsl.com>; Wed,  3 Jul 2013 14:56:34 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D9B11E80EF for <dnsop@ietf.org>; Wed,  3 Jul 2013 14:56:25 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id E602B1B403E8; Wed,  3 Jul 2013 17:56:20 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <EFD28A69-40DC-4A6C-B3E7-B35BC655AF7F@vpnc.org>
Date: Wed, 3 Jul 2013 17:56:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAFC3938-13F8-44FD-8AD9-5D71D68E1A1A@kumari.net>
References: <20130703210147.69996.qmail@joyce.lan> <EFD28A69-40DC-4A6C-B3E7-B35BC655AF7F@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1508)
Cc: John Levine <johnl@taugh.com>, dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jul 2013 21:56:40 -0000

On Jul 3, 2013, at 5:14 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Jul 3, 2013, at 2:01 PM, "John Levine" <johnl@taugh.com> wrote:
>=20
>>>>>  If yes, message cache elements are prefetched before they expire
>>>>>  to  keep  the  cache  up to date.  Default is no.  Turning it on
>>>>>  gives about 10 percent more traffic and load on the machine, but
>>>>>  popular items do not expire from the cache.
>>=20
>>> My question earlier still stands: does Unbound do what HAMMER says
>>> (waits for a request before refreshing the cache) or does it just
>>> refresh the cache automatically? The Unbound doc is unclear (at =
least
>>> to me).
>>=20
>> If it did it automatically, I'd expect a lot more than 10% more
>> traffic.  I enabled it on my not terribly busy server and I see
>> numbers that look like they're in the 1% range:
>>=20
>> Jul 03 14:23:21 unbound[40669:0] info: server stats for thread 0: =
47798 queries, 20108 answers from cache, 27690 recursions, 242 prefetch
>> Jul 03 15:23:21 unbound[40669:0] info: server stats for thread 0: =
53322 queries, 20319 answers from cache, 33003 recursions, 291 prefetch
>> Jul 03 16:23:21 unbound[40669:0] info: server stats for thread 0: =
55260 queries, 20697 answers from cache, 34563 recursions, 272 prefetch
>>=20
>=20
> Those are pictures. Source code, or developer assurance, or it didn't =
happen ( to badly bastardize a phrase that the kids these days use ).

It *appears* to me from looking at the source that Unbound triggers upon =
an incoming query (basically what HAMMER suggests).
I should note that this is the first time I have looked at the Unbound =
source, and so it is entirely possible that I'm missing something.

It seems that worker_handle_request() in worker.c has the interesting =
bits.
=46rom what I can tell, the worker will only have this sort of request =
if it was initiated by an incoming query.

Horrendous pseudocode seems like:
worker_handle_request()
 if answer_from_cache:
    if prefetch_ttl_expired:
       reply_and_prefetch()


/** Reply to client and perform prefetch to keep cache up to date */
reply_and_prefetch()=20
  reply()
    /* create the prefetch in the mesh as a normal lookup without
	 * client addrs waiting, which has the cache blacklisted (to =
bypass
	 * the cache and go to the network for the data). */
	/* this (potentially) runs the mesh for the new query */
    	mesh_new_prefetch(worker->env.mesh, qinfo, flags, leeway +=20
		PREFETCH_EXPIRY_ADD);


There is also a PREFETCH_EXPIRY_ADD which I don't really understand:

/**=20
 * seconds to add to prefetch leeway.  This is a TTL that expires old =
rrsets
 * earlier than they should in order to put the new update into the =
cache.
 * This additional value is to make sure that if not all TTLs are equal =
in
 * the message to be updated(and replaced), that rrsets with up to this =
much
 * extra TTL are also replaced.  This means that the resulting new =
message
 * will have (most likely) this TTL at least, avoiding very small 'split
 * second' TTLs due to operators choosing relative primes for TTLs (or =
so).
 * Also has to be at least one to break ties (and overwrite cached =
entry).
 */
#define PREFETCH_EXPIRY_ADD 60

I must admit that I'm somewhat shaky on much of the above, it would be =
great if someone who is more familiar with the architecture / code could =
comment/


W




>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20

--=20
Do not meddle in the affairs of wizards, for they are subtle and quick =
to anger. =20
    -- J.R.R. Tolkien



From wouter@nlnetlabs.nl  Thu Jul  4 01:25:20 2013
Return-Path: <wouter@nlnetlabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6246621F9F50 for <dnsop@ietfa.amsl.com>; Thu,  4 Jul 2013 01:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_73=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EznfXeQeFjuO for <dnsop@ietfa.amsl.com>; Thu,  4 Jul 2013 01:25:19 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 22E3B21F9AD3 for <dnsop@ietf.org>; Thu,  4 Jul 2013 01:25:18 -0700 (PDT)
Received: from axiom.nlnetlabs.nl (axiom.nlnetlabs.nl [IPv6:2001:7b8:206:1:222:4dff:fe55:4d46]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r648PBJ4037898 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Thu, 4 Jul 2013 10:25:15 +0200 (CEST) (envelope-from wouter@nlnetlabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.2 open.nlnetlabs.nl r648PBJ4037898
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1372926316; bh=jPpfuSjvMBimg9ahbOJQaFYvBpdP1hBWelgmG/5dduE=; h=Date:From:To:Subject:References:In-Reply-To; b=Gkl5/lXXsF7ECTlFurFMaXtOdbUAtxWqlf2kWDM+w6jxo12xwAbhKuwspew0acv4c dkiQIZeFaTWH0pasknRlMmQz70NmOyP529ruI14axZ9FW9wBP6r9BKHclBpLL/5Jra +uH+EjP7jQ6++VQgXDM90sSvz41adVYfTmI1YWao=
Message-ID: <51D53167.9090906@nlnetlabs.nl>
Date: Thu, 04 Jul 2013 10:25:11 +0200
From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20130703210147.69996.qmail@joyce.lan> <EFD28A69-40DC-4A6C-B3E7-B35BC655AF7F@vpnc.org> <FAFC3938-13F8-44FD-8AD9-5D71D68E1A1A@kumari.net>
In-Reply-To: <FAFC3938-13F8-44FD-8AD9-5D71D68E1A1A@kumari.net>
X-Enigmail-Version: 1.5.1
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::1]); Thu, 04 Jul 2013 10:25:15 +0200 (CEST)
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Jul 2013 08:25:20 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On 07/03/2013 11:56 PM, Warren Kumari wrote:
>>>> My question earlier still stands: does Unbound do what HAMMER
>>>> says (waits for a request before refreshing the cache) or
>>>> does it just refresh the cache automatically? The Unbound doc
>>>> is unclear (at least to me).

Yes, it waits for a request before refreshing the cache.  The request
is the excuse to bother the authority server, since it could pretend
the entry had fallen out of the cache.  And also the request indicates
a continued interest (the item is still popular).  It was also simpler
to implement :-)

So, prefetch also prefetches fairly impopular names, that have about
10 queries per TTL.  And one query hits the 10% last of the TTL.  For
a TTL of 3600, getting about 10 queries in 3600 seconds would
statistically make you hit one query in the last 10% (a little) often.
 And that is one query per 360 seconds, which is fairly impopular, but
it is prefetched.

>> Those are pictures. Source code, or developer assurance, or it
>> didn't happen ( to badly bastardize a phrase that the kids these
>> days use ).

Yes I wrote the code and say so.  (Not sure how that is better than
reading the source).  Results, anecdotally, are very modest.  It does
remove latency spikes for popular names.

> It *appears* to me from looking at the source that Unbound triggers
> upon an incoming query (basically what HAMMER suggests). I should
> note that this is the first time I have looked at the Unbound
> source, and so it is entirely possible that I'm missing something.

Yes, it trigger upon an incoming query.

> There is also a PREFETCH_EXPIRY_ADD which I don't really
> understand:
> 
> /** * seconds to add to prefetch leeway.  This is a TTL that
> expires old rrsets * earlier than they should in order to put the
> new update into the cache. * This additional value is to make sure
> that if not all TTLs are equal in * the message to be updated(and
> replaced), that rrsets with up to this much * extra TTL are also
> replaced.  This means that the resulting new message * will have
> (most likely) this TTL at least, avoiding very small 'split *
> second' TTLs due to operators choosing relative primes for TTLs (or
> so). * Also has to be at least one to break ties (and overwrite
> cached entry). */ #define PREFETCH_EXPIRY_ADD 60
> 
> I must admit that I'm somewhat shaky on much of the above, it would
> be great if someone who is more familiar with the architecture /
> code could comment/

Prefetch happens before the TTL expires, x seconds before.  You can
determine x in many different ways, a fixed value works for very
highly popular names (i.e. draft submitter's employer), but for less
popular ones (i.e. my employer :-) ), prefetch can also work but needs
a bigger value, that is why I chose a fraction instead of absolute
value.  Unbound uses x + 60 to replace 'old' RRsets when the new reply
comes in.  This x+60 is subtracted from the TTL in the cache for
RRsets to determine if they are 'old' (with respect to the reply for
this prefetch).  Because if it used exactly x, then the cache could
contain a remaining cache TTL x+1 for another RRset that forms up the
reply from cache that we would use for further queries.  So we could
only answer for 1 second extra because we refused to update some RRs
that make up the response (but we updated the RR that was about to
expire).   The value 60 is one that I picked with a similar idea as
when you talked about tilting at the windmills of small TTLs, but it
does not actually prevent the zone operator from choosing small TTLs,
it stops the hammer system from generating such small TTLs in the
cache from the larger TTLs that the authority system sends.  The
defensive code about NS records you refer to is to make sure that this
system can handle a zone operator change without 'sticking' to the old
operator; e.g. 'if x+60 > remaining cache TTL of NS RRset' then we
must go up to the parent operator, even though the child NS has not
expired yet.

Aside, I agree that prefetching before the TTL expires is overly
aggressive.  But lengthening the TTL is worse (for DNSSEC rollovers
TTLs MUST expire, or the signatures become bogus).

Best regards,
   Wouter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR1TFiAAoJEJ9vHC1+BF+NcuUP/1u6cB9LVEwoEHmucXoPE8Tt
z5frpV0xbfn6BaR0dvilorOHFr3KUe7HLa9ZRYHSaTDGqsYGqwmQC8HPx55r3sPn
9znMMxvAuX46BaAiLA1+7BEjKe96ubRkGZT6Lgt7C0UYcZfICG2U+CHOUVlPUJhU
pBDRq+o0fwhrP4Wx9L8aGtQwy+cFoxMi1sgQNSwji3QXZjzw+5ioV43CGx8HnAFM
09triotHJtD/weHWbk5RksQ9Fh0ncWXXFwiIPbKFwAKs28UDqP+fCWBwG5CeooNM
ruxuHRuJ7TEpWmPpB0WZfiCS6eIkGxr1ZaH0YKzni1+EC9qkpw7ziaUo19svZEEU
QxSWKOfBXOgWbJQvFj9BBKmKojv7ShVfzpe20czmsPdXuZsVwqWfOPeVtuV7lqJQ
6SP38LZvBE9qs4rZiXvvROYZyU3yqtyhp9i5K2aMncR64gsAtWCScR1diJWPLpWP
P55mHEmGaeu4xUsrvu49JMihDdxgSZYmZM4HdcUlShlzKYYOTuqKRh8C5Kzk7Ybq
FK5OOSyc4r8+kSRAmPtzj4pNf1cR/Te1/MR5o8yc8ZAVIjJvATGbKJEk5qq4jxrK
OukryH5g15wLAwJkC7M82fW4ua5PECwceeTkwAd+XETo/GZ4XPzZLBv9A8McWzF9
nnGDcxbx9rija3NTMv6A
=8l0m
-----END PGP SIGNATURE-----

From regnauld@x0.dk  Thu Jul  4 03:57:20 2013
Return-Path: <regnauld@x0.dk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92BD521F9E72 for <dnsop@ietfa.amsl.com>; Thu,  4 Jul 2013 03:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNYecR165Q3I for <dnsop@ietfa.amsl.com>; Thu,  4 Jul 2013 03:57:14 -0700 (PDT)
Received: from moof.catpipe.net (moof.catpipe.net [194.28.252.64]) by ietfa.amsl.com (Postfix) with ESMTP id A72C621F9E6D for <dnsop@ietf.org>; Thu,  4 Jul 2013 03:57:13 -0700 (PDT)
Received: from localhost (moof.catpipe.net [194.28.252.64]) by localhost.catpipe.net (Postfix) with ESMTP id 281AD4CE9F7; Thu,  4 Jul 2013 12:57:12 +0200 (CEST)
Received: from moof.catpipe.net ([194.28.252.64]) by localhost (moof.catpipe.net [194.28.252.64]) (amavisd-new, port 10024) with ESMTP id De2FKJRnv50Q; Thu,  4 Jul 2013 12:57:11 +0200 (CEST)
Received: from macbook.bluepipe.net (macbook.bluepipe.net [195.249.214.179]) (Authenticated sender: relayuser) by moof.catpipe.net (Postfix) with ESMTPA id B2B004CE996; Thu,  4 Jul 2013 12:57:11 +0200 (CEST)
Received: by macbook.bluepipe.net (Postfix, from userid 1001) id 58B659B161D; Thu,  4 Jul 2013 12:57:13 +0200 (CEST)
Date: Thu, 4 Jul 2013 12:57:13 +0200
From: Phil Regnauld <regnauld@nsrc.org>
To: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
Message-ID: <20130704105713.GC59704@macbook.bluepipe.net>
References: <20130703210147.69996.qmail@joyce.lan> <EFD28A69-40DC-4A6C-B3E7-B35BC655AF7F@vpnc.org> <FAFC3938-13F8-44FD-8AD9-5D71D68E1A1A@kumari.net> <51D53167.9090906@nlnetlabs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51D53167.9090906@nlnetlabs.nl>
X-Operating-System: Darwin 12.4.0 x86_64
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Jul 2013 10:57:20 -0000

W.C.A. Wijngaards (wouter) writes:
> 
> Yes I wrote the code and say so.  (Not sure how that is better than
> reading the source).  Results, anecdotally, are very modest.  It does
> remove latency spikes for popular names.

	What does the latency spike translate to in terms of extra traffic
	(clients) ? A thundering herd effect ? Congestion ? Considering
	how many tricks modern browsers have up their sleeves (including
	prefetching data linked on a page), I'm wondering how the two
	interact. I've always mentioned the expiring RR prefetch option
	to be a cool feature of Unbound, but in reality, what does it mean
	for users ?

> Aside, I agree that prefetching before the TTL expires is overly
> aggressive.

	If it mitigates other issues...

> But lengthening the TTL is worse (for DNSSEC rollovers
> TTLs MUST expire, or the signatures become bogus).

	:)

	P.

From ogud@ogud.com  Fri Jul  5 10:14:35 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C9E821F9A79 for <dnsop@ietfa.amsl.com>; Fri,  5 Jul 2013 10:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIyIPl0AT0gc for <dnsop@ietfa.amsl.com>; Fri,  5 Jul 2013 10:14:30 -0700 (PDT)
Received: from smtp85.ord1c.emailsrvr.com (smtp85.ord1c.emailsrvr.com [108.166.43.85]) by ietfa.amsl.com (Postfix) with ESMTP id 25C4321F9AD3 for <dnsop@ietf.org>; Fri,  5 Jul 2013 10:14:30 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id CCBEC500A7; Fri,  5 Jul 2013 13:14:28 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 7B4F6500D1;  Fri,  5 Jul 2013 13:14:27 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <51D18336.5010401@nlnetlabs.nl>
Date: Fri, 5 Jul 2013 13:14:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl>
To: Matthijs Mekking <matthijs@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 05 Jul 2013 17:14:35 -0000

On Jul 1, 2013, at 9:25 AM, Matthijs Mekking <matthijs@NLnetLabs.nl> =
wrote:

> Hi Olafur,
>=20
> On 06/28/2013 08:18 PM, Olafur Gudmundsson wrote:
>>=20
>> On Jun 25, 2013, at 6:05 AM, Matthijs Mekking <matthijs@NLnetLabs.nl> =
wrote:
>>=20
>>>=20
>>> * Nit: In section 1, it says there may be two interactions with the
>>> parent. This could also be only one, this could be more in some =
freaky
>>> rollovers, so I would prefer that it reads: "there may be one ore =
more
>>> interactions with the parent".
>>=20
>> Applied=20
>>=20
>>>=20
>>> * Section 3. I appreciate that most ZSK /KSK terminology is =
carefully
>>> replaced with, but in section 3 is still something that itches: "The =
SEP
>>> bit is an optional bit to indicate that the key is allowed to sign =
the
>>> DNSKEY RRset". That is not true. Without the SEP bit, the key may =
also
>>> sign the DNSKEY RRset.
>>>=20
>>=20
>> I agree but still want to bring up the SEP bit,=20
>> would some thing like this be better:=20
>> "The SEP bit is an optional bit that indicates that the child expects =
to sign the
>> DNSKEY RRset with that key, while the key is in use."=20
>=20
> This text is better. Still, I want to propose text:
>=20
> "The SEP bit, if set, indicates that the DNSKEY is intended for use as =
a
> secure entry point, thus are used to sign the DNSKEY RRset, and the
> Parental Agent can calculate DS records based on that."
>=20

I applied this text with the change "used to sign" --> "expected to =
sign"=20

> This removes the notion of optional (strictly the bit is not optional,
> the setting of it is).
>=20
>>=20
>>>=20
>>> * Section 4.2. It is suggested that RFC 5011-like hold down timers =
are
>>> being used, e.g. new keying information must be published for a =
month
>>> before acceptance as a new trust anchor. This makes the duration of =
key
>>> rollovers unnecessary long. The hold down timers in RFC 5011 are =
there
>>> to mitigate against a compromise. The compromise allows the attacker =
to
>>> sign data in the zone.
>>=20
>> I hear you and want other people to chime in, both in the context of=20=

>> compromise and time to perform rollover. If rollover is done by=20
>> automated systems that perform checks before progressing who cares =
how long the=20
>> rollover takes?=20
>=20
> It depends on what you gain with the long wait. I said in my e-mail =
that
> for me it makes sense to do hold down timers in the RFC5011 case, but =
we
> don't need to be that conservative with CDS. But I guess it has to do
> with local policy, what checks you require.
>=20
> I don't have very strong feelings about this. I just want to see it as
> fast as possible:). I guess if everything is done automagically, this =
is
> less of a pain.
>=20
> A nit drawback I see is that during the transition period you have to
> deal with a larger DNSKEY and/or DS RRset.
>=20
>=20

I understand when a Human is involved in key rollover you want it to =
happen as=20
fast as possible to minimize the chance of her forgetting a step.=20
When this is fully automated in tools why is fast needed ?=20

>>>=20
>>> Similar we could look at a compromise that allows the attacker to =
upload
>>> a DS/DNSKEY to the parent. However, there are no mechanisms to =
mitigate
>>> against this attack. Why should we have mitigation for the CDS =
proposal,
>>> if there is none for the current mechanism?
>>>=20
>>> The difference between CDS and RFC 5011 is the location of the trust
>>> anchor your are updating. With CDS, you are updating the DS in the
>>> parent. With RFC 5011, you are updating lots of trust anchors in the
>>> wild. The latter may indeed require a bit more conservative =
approach.
>>>=20
>>> * Section 4.3. I wonder if the SHOULD in the first sentence should =
be a
>>> MUST.
>>>=20
>> I think a better way is to encourage the child to ONLY publish CDS =
when there is a need to change the DS record and
>> remove after parents performs change.=20
>=20
> I prefer the approach where the CDS represents what DS should be in =
the
> parent. You can make checks: if it is the same, we are in sync. If =
not,
> the parental agent still has work to do.
>=20
> Adding behavior to remove the CDS again after the update has taken =
place
> at all parent name servers, makes the usage at the child unnecessary
> complex.
>=20

I got a comment off-line saying it is better for Parents that Mandating =
CDS removal as then there is no=20
question at parent side as what to do. When CDS is present parent needs =
to perform checks it is in sync.=20
For now I will leave this as an open issue,=20

>=20
>=20
>>> * Section 4.4. I dislike the idea of the side effect of parent
>>> calculates DS, so I would like to see that only the "augment" mode =
is
>>> supported (where I think it should read: "it will make sure there =
are
>>> CDS records for the digest algorithm(s) it require(s)" (CDS instead =
of
>>> DS)).
>>>=20
>>=20
>> You are not alone, but there are some people in your neighborhood =
that=20
>> feel strongly the other way and argued strongly against version 01 =
because=20
>> this was outlawed.=20
>=20
> Hm, yes. And I remember that they require the DNSKEY too. Still, I =
would
> still like to see that the CDS should match the "to be calculated DS".
>=20

>=20
>>> The publishing "Future DNSKEYs" does not go well with several =
rollover
>>> scenarios (those based on Double-DS). I am wondering if the policy =
is
>>> "We calculate the DS" or "We decide the digest algorithm". In case =
of
>>> the latter, then augment mode can be used to support this. In case =
of
>>> the first, the future DNSKEY is really required to be published, and
>>> Double-DS based rollovers are not possible in combination with CDS.
>>>=20
>>=20
>> exactly=20
>>=20
>>> * Section 6. Security Considerations. The last paragraph. Isn't this
>>> solved by saying that the Parental Agent MUST ensure that old =
versions
>>> of the CDS RRset do not override newer versions in section 4.3. =
Usage?
>>> There is already a proposed method on how to achieve this there.
>>>=20
>>=20
>> Strictly speaking using RFC5011 will address this as all the =
signatures in=20
>> "disjoint" authorative servers wil have expired.=20
>=20
>>> * When implementing a prototype for this in OpenDNSSEC, I questioned
>>> myself what value I should use for the TTL. We could consider 0, as =
this
>>> record is not really intended for the resolver. We could also use =
the
>>> TTL to suggest a polling frequency for the parental agent. Just some
>>> thoughts.
>>>=20
>>>=20
>> I had not thought about guidance on the CDS TTL, nor on the signature =
lifetime on the record.=20
>> You have any ideas?=20
>=20
> I just set it to the DNSKEY TTL currently. In OpenDNSSEC you can only
> set different signature lifetime for NSEC(3) and the rest, so nothing
> special there for CDS either.
>=20
> I don't think we need special guidance.
>=20
> The only idea I had, I already mentioned is that we could use the TTL
> field to signal a polling frequency.
>=20
RFC5011 sets polling frequency based on TTL and Signature Lifetime.=20

Thanks for your comments.=20

	Olafur

>=20
> Best regards,
>  Matthijs
>=20
>=20
>=20
>>=20
>>=20
>>> Best regards,
>>> Matthijs
>>>=20
>> Thanks for great review.=20
>>=20
>> 	Olafur
>>=20
>>=20
>=20


From florian@inet.tu-berlin.de  Mon Jul  8 01:42:21 2013
Return-Path: <florian@inet.tu-berlin.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C74E921F85E0 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 01:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3IzMQmcCoG23 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 01:42:17 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id 634CE21F84DC for <dnsop@ietf.org>; Mon,  8 Jul 2013 01:40:19 -0700 (PDT)
Received: from fls-nb.lan.streibelt.net (91-64-122-25-dynip.superkabel.de [91.64.122.25]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 321084C0E18 for <dnsop@ietf.org>; Mon,  8 Jul 2013 10:40:17 +0200 (CEST)
Date: Mon, 8 Jul 2013 10:40:15 +0200
From: Florian Streibelt <florian@inet.tu-berlin.de>
To: dnsop@ietf.org
Message-ID: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net>
Organization: FG INET, T-Labs
X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.18; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 08:42:21 -0000

My mail from Wed, 26 Jun 2013 18:01:31 +0200 did not came through:

Hello,

in our work with the EDNS-Client-Subnet extension we noticed that it offers=
 unique measurement
opportunities. Below you find the abstract to our paper on "Unintended Cons=
equences:
Exploring EDNS-Client-Subnet Adopters in your Free Time" where we used the =
client IP
extension to explore the mapping of client-IP's to server-IP's in CDNs incl=
uding google and
edgcast.

We mentioned this to Ted Lemon and Andrew Sullivan, who suggested that this=
 work may be of interest to
the wider audience of both DNS related working groups (sorry for cross post=
ing).

As the next IETF meeting is in Berlin (and we are based in Berlin) I would =
be happy taking
the chance of presenting the paper at the upcoming meeting. Any comments?


cheers,
  Florian


Abstract of "Unintended Consequences: Exploring EDNS-Client-Subnet Adopters=
 in your Free Time";

The recently proposed DNS extension, EDNS-Client-Subnet (ECS), has been qui=
ckly
adopted by major Internet companies such as Google to better assign user
requests to their servers and improve end-user experience. =20
In this paper, we show that the adoption of ECS also offers unique, but lik=
ely
unintended, opportunities to uncover details about these companies' operati=
onal
practices at almost no cost.  A key observation is that ECS allows everyone=
 to
resolve domain names of ECS adopters on behalf of any arbitrary IP/prefix i=
n the
Internet. In fact, by utilizing only a single residential vantage point and
relying solely on publicly available information, we are able to (i) uncover
the global footprint of ECS adopters with very little effort, (ii) infer the
DNS response cacheability and end-user clustering of ECS adopters for an ar=
bitrary
network in the Internet, and (iii) reveal the mapping of users to server
locations as practiced by major ECS adopters.  While pointing out such new
measurement opportunities, our work is also intended to make current and fu=
ture
ECS adopters aware of which operational information gets exposed when utili=
zing
this recent DNS extension.


--=20
Florian Streibelt
Chair "Intelligent Networks" (INET)
TEL 16
Technische Universit=C3=A4t Berlin
Ernst-Reuter-Platz 7
10587 Berlin
GERMANY

From bortzmeyer@nic.fr  Mon Jul  8 02:38:30 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B322111E819D for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 02:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLrwqlsT1sQF for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 02:38:23 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id C823C11E81A1 for <dnsop@ietf.org>; Mon,  8 Jul 2013 02:38:20 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 9AC4D280293; Mon,  8 Jul 2013 11:37:44 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 963E7280283; Mon,  8 Jul 2013 11:37:44 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:113]) by relay1.nic.fr (Postfix) with ESMTP id 8B2534C0053; Mon,  8 Jul 2013 11:37:14 +0200 (CEST)
Date: Mon, 8 Jul 2013 11:37:14 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Florian Streibelt <florian@inet.tu-berlin.de>
Message-ID: <20130708093714.GA21377@nic.fr>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net>
X-Operating-System: Debian GNU/Linux 7.1
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] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 09:38:30 -0000

On Mon, Jul 08, 2013 at 10:40:15AM +0200,
 Florian Streibelt <florian@inet.tu-berlin.de> wrote 
 a message of 42 lines which said:

> The recently proposed DNS extension, EDNS-Client-Subnet (ECS), has
> been quickly adopted by major Internet companies such as Google to
> better assign user requests to their servers and improve end-user
> experience.

I just parsed the requests of a TLD authoritative name server and I
find very little use of EDNS options and none of option 8. Is it
because I do not understand how this option is supposed to work?



From florian@inet.tu-berlin.de  Mon Jul  8 02:51:49 2013
Return-Path: <florian@inet.tu-berlin.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8B321F8D0D for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 02:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0xc8xDvtxOdU for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 02:51:48 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0FF21F8BCE for <dnsop@ietf.org>; Mon,  8 Jul 2013 02:51:47 -0700 (PDT)
Received: from fls-nb.lan.streibelt.net (91-64-122-25-dynip.superkabel.de [91.64.122.25]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 2AF864C00C1 for <dnsop@ietf.org>; Mon,  8 Jul 2013 11:51:45 +0200 (CEST)
Date: Mon, 8 Jul 2013 11:51:43 +0200
From: Florian Streibelt <florian@inet.tu-berlin.de>
To: dnsop@ietf.org
Message-ID: <20130708115143.05b3b834@fls-nb.lan.streibelt.net>
In-Reply-To: <20130708093714.GA21377@nic.fr>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net> <20130708093714.GA21377@nic.fr>
Organization: FG INET, T-Labs
X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.18; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 09:51:49 -0000

Am Mo, 08.07.13 um 11:37:14 Uhr 
schrieb Stephane Bortzmeyer <bortzmeyer@nic.fr>:

> I just parsed the requests of a TLD authoritative name server and I
> find very little use of EDNS options and none of option 8. Is it
> because I do not understand how this option is supposed to work?
> 
> 

The extention is only visible when you query an authorative server using an ECS capable client, like a patched dig. The server will then notice you are using that extention and reply accordingly.
The TLD servers make - as far as I know - no use of this but the authoritative server for google.com for example does.


From bortzmeyer@nic.fr  Mon Jul  8 02:56:18 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF60D21F9ED3 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 02:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T1jk35RxL6-Y for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 02:56:12 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 76EF721F9EAD for <dnsop@ietf.org>; Mon,  8 Jul 2013 02:56:11 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id BBD9F2802C7; Mon,  8 Jul 2013 11:55:40 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id B74FD280293; Mon,  8 Jul 2013 11:55:40 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:113]) by relay1.nic.fr (Postfix) with ESMTP id AB0394C007C; Mon,  8 Jul 2013 11:55:10 +0200 (CEST)
Date: Mon, 8 Jul 2013 11:55:10 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Florian Streibelt <florian@inet.tu-berlin.de>
Message-ID: <20130708095510.GA29226@nic.fr>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net> <20130708093714.GA21377@nic.fr> <20130708115143.05b3b834@fls-nb.lan.streibelt.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130708115143.05b3b834@fls-nb.lan.streibelt.net>
X-Operating-System: Debian GNU/Linux 7.1
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] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 09:56:18 -0000

On Mon, Jul 08, 2013 at 11:51:43AM +0200,
 Florian Streibelt <florian@inet.tu-berlin.de> wrote 
 a message of 16 lines which said:

> The extention is only visible when you query an authorative server
> using an ECS capable client, like a patched dig. 

Yes, that's what I thought. So you confirm no software resolver today
sets this option? If so, it is not really deployed.

From florian@inet.tu-berlin.de  Mon Jul  8 03:03:31 2013
Return-Path: <florian@inet.tu-berlin.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6327711E819F for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 03:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pFyJT6hIB9uB for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 03:03:31 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id 2402411E819D for <dnsop@ietf.org>; Mon,  8 Jul 2013 03:03:30 -0700 (PDT)
Received: from fls-nb.lan.streibelt.net (91-64-122-25-dynip.superkabel.de [91.64.122.25]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 650F44C0E18 for <dnsop@ietf.org>; Mon,  8 Jul 2013 12:03:29 +0200 (CEST)
Date: Mon, 8 Jul 2013 12:03:28 +0200
From: Florian Streibelt <florian@inet.tu-berlin.de>
To: dnsop@ietf.org
Message-ID: <20130708120328.34c7d0a5@fls-nb.lan.streibelt.net>
In-Reply-To: <20130708095510.GA29226@nic.fr>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net> <20130708093714.GA21377@nic.fr> <20130708115143.05b3b834@fls-nb.lan.streibelt.net> <20130708095510.GA29226@nic.fr>
Organization: FG INET, T-Labs
X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.18; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 10:03:31 -0000

On Mon, 8 Jul 2013 11:55:10 +0200
 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:

> > The extention is only visible when you query an authorative server
> > using an ECS capable client, like a patched dig. 
> 
> Yes, that's what I thought. So you confirm no software resolver today
> sets this option? If so, it is not really deployed.

ah, now I get your question. 

Indeed, it is not deployed on the "client side" but public dns providers like google rely on it heavily by using this to transport the client IP address, or parts of it, from the frontend servers - reachable as 8.8.8.8 - to the backend servers and whitelisted third party authoritative resolvers.

By this the authoritative server sees the subnet of the client that is using google as forwarder, although it is only contacted by a google backend server.

From jewforice@gmail.com  Mon Jul  8 03:15:29 2013
Return-Path: <jewforice@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77AB721F99BB for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 03:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5S95ywullZs for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 03:15:29 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2CEB321F968B for <dnsop@ietf.org>; Mon,  8 Jul 2013 03:15:23 -0700 (PDT)
Received: by mail-lb0-f169.google.com with SMTP id d10so3590069lbj.0 for <dnsop@ietf.org>; Mon, 08 Jul 2013 03:15:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D9SOXPgtljSxNsS5tkmG4RFuRrzeakMM5gBsU9zElUM=; b=F3r2oWL4/nFl80z5YyjSJhZc0UlSYelLLGXBwXF8T/PMFruDQk3S6TQOjM6UXHx/2N jnTetA9ywbBXRXGZJSRo4Jm3hf4KD3cu6noZqZTn4YK0R6mIq7bt61fNZzE1YaS5y0vo CT5CGkzR+8Lm5EUUeZ6DO+1sGXdJcngqEYRxBSFRi8Gmqx4LqzjjTQs1RqGQOofaKaUF Nb2iYhuIL3VNyYUnEnnvCJEOg9xRjNOUc0fTZc+1OWQMQtz5ih1uOpCBefG8nmTk6/aS FlGZwC/UifVAzk2q1PO0I0SS4rs70P1QCuUjr0NpQDNEtefUso9O82ZK3aKUKn9yypZy sPvw==
MIME-Version: 1.0
X-Received: by 10.112.50.236 with SMTP id f12mr10313681lbo.15.1373278520749; Mon, 08 Jul 2013 03:15:20 -0700 (PDT)
Received: by 10.114.174.200 with HTTP; Mon, 8 Jul 2013 03:15:20 -0700 (PDT)
Received: by 10.114.174.200 with HTTP; Mon, 8 Jul 2013 03:15:20 -0700 (PDT)
In-Reply-To: <20130708095510.GA29226@nic.fr>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net> <20130708093714.GA21377@nic.fr> <20130708115143.05b3b834@fls-nb.lan.streibelt.net> <20130708095510.GA29226@nic.fr>
Date: Mon, 8 Jul 2013 18:15:20 +0800
Message-ID: <CAB3ZD+=hqrK_Yx+6RDb21jv78+4-5kMqb_4e2aPpm+fVwEc7EA@mail.gmail.com>
From: ice jew <jewforice@gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=001a1133b42a6833a104e0fd52d1
Cc: dnsop <dnsop@ietf.org>, Florian Streibelt <florian@inet.tu-berlin.de>
Subject: Re: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 10:15:29 -0000

--001a1133b42a6833a104e0fd52d1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

There is 2 questions about deployment.
1,Is there any other  recursive resolver that adopts ECS  except Google and
OpenDNS?
2,Is there any open source solution of recursive resolver that supports ECS=
?
=E5=9C=A8 2013-7-8 =E4=B8=8B=E5=8D=885:56=EF=BC=8C"Stephane Bortzmeyer" <bo=
rtzmeyer@nic.fr>=E5=86=99=E9=81=93=EF=BC=9A

> On Mon, Jul 08, 2013 at 11:51:43AM +0200,
>  Florian Streibelt <florian@inet.tu-berlin.de> wrote
>  a message of 16 lines which said:
>
> > The extention is only visible when you query an authorative server
> > using an ECS capable client, like a patched dig.
>
> Yes, that's what I thought. So you confirm no software resolver today
> sets this option? If so, it is not really deployed.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--001a1133b42a6833a104e0fd52d1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">There is 2 questions about deployment. <br>
1,Is there any other=C2=A0 recursive resolver that adopts ECS=C2=A0 except =
Google and OpenDNS?<br>
 2,Is there any open source solution of recursive resolver that supports EC=
S?</p>
<div class=3D"gmail_quote">=E5=9C=A8 2013-7-8 =E4=B8=8B=E5=8D=885:56=EF=BC=
=8C&quot;Stephane Bortzmeyer&quot; &lt;<a href=3D"mailto:bortzmeyer@nic.fr"=
>bortzmeyer@nic.fr</a>&gt;=E5=86=99=E9=81=93=EF=BC=9A<br type=3D"attributio=
n"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
On Mon, Jul 08, 2013 at 11:51:43AM +0200,<br>
=C2=A0Florian Streibelt &lt;<a href=3D"mailto:florian@inet.tu-berlin.de">fl=
orian@inet.tu-berlin.de</a>&gt; wrote<br>
=C2=A0a message of 16 lines which said:<br>
<br>
&gt; The extention is only visible when you query an authorative server<br>
&gt; using an ECS capable client, like a patched dig.<br>
<br>
Yes, that&#39;s what I thought. So you confirm no software resolver today<b=
r>
sets this option? If so, it is not really deployed.<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>

--001a1133b42a6833a104e0fd52d1--

From florian@inet.tu-berlin.de  Mon Jul  8 03:44:06 2013
Return-Path: <florian@inet.tu-berlin.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4913121F99B8 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 03:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gmbufXQVE0JQ for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 03:44:05 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id BEB7421F9994 for <dnsop@ietf.org>; Mon,  8 Jul 2013 03:44:05 -0700 (PDT)
Received: from fls-nb.lan.streibelt.net (91-64-122-25-dynip.superkabel.de [91.64.122.25]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id A03C84C0E18 for <dnsop@ietf.org>; Mon,  8 Jul 2013 12:44:04 +0200 (CEST)
Date: Mon, 8 Jul 2013 12:44:03 +0200
From: Florian Streibelt <florian@inet.tu-berlin.de>
To: dnsop <dnsop@ietf.org>
Message-ID: <20130708124403.41ad8f53@fls-nb.lan.streibelt.net>
In-Reply-To: <CAB3ZD+=hqrK_Yx+6RDb21jv78+4-5kMqb_4e2aPpm+fVwEc7EA@mail.gmail.com>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net> <20130708093714.GA21377@nic.fr> <20130708115143.05b3b834@fls-nb.lan.streibelt.net> <20130708095510.GA29226@nic.fr> <CAB3ZD+=hqrK_Yx+6RDb21jv78+4-5kMqb_4e2aPpm+fVwEc7EA@mail.gmail.com>
Organization: FG INET, T-Labs
X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.18; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 10:44:06 -0000

On Mon, 8 Jul 2013 18:15:20 +0800
 ice jew <jewforice@gmail.com> wrote:

> There is 2 questions about deployment.
> 1,Is there any other  recursive resolver that adopts ECS  except Google and
> OpenDNS?

That is not easy to tell. In the paper we focused on the authoritative NS.
The reason is that e.g. google and opendns manually whitelist the authoritative nameservers they send ECS enabled queries to prevent failures in name resolution.
(Some resolvers seem to behave quite strangly if they don't understand the extention.)

> 2,Is there any open source solution of recursive resolver that supports ECS?

I am not aware of any - for testing purposes I did a rough patch against a dns proxy but thats only usable for debuggging and not public.
This makes it especially hard to get whitelisted to find answers to your first question.

From jewforice@gmail.com  Mon Jul  8 03:57:51 2013
Return-Path: <jewforice@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57E511E81D1 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 03:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IzkVUr+B4ZU6 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 03:57:51 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BC21B11E819F for <dnsop@ietf.org>; Mon,  8 Jul 2013 03:57:50 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id eb20so3701640lab.15 for <dnsop@ietf.org>; Mon, 08 Jul 2013 03:57:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bUxgcHKzYS2Hp/zCplN54rhzIZFDqi4UAA3xzTMxIHA=; b=vwJffDGfrKI73HPwb1lZMI7swAiPdEDZqOZlVLm/xOmYkHi4YTjmwBPyYDWUPIzcKu D6pT5WHnDC5QQ20lDWzsLHb/eVQyeO/fdFOMHv3JzWMlbrBFqW2ICf5w+auSYmlolqDz bkq2HCTvZlVos105Q6fUTrHCxIWFqIi2t6/QhR528cJ22dbmZpA6Aif+fAqVPO33CdOr A5ScmDcaKUP4znL0Tmq9zFJhOf8cyTqeITq285yZh29h34MUJ1AG8/5CHvm6Yv7ITfHr /URc5B3JuE7Walqa4zZfnjTCcf15vvpkBHW7t6BA566622ekkRiZb8GwyyoQI7fDVcwB fORQ==
MIME-Version: 1.0
X-Received: by 10.112.11.162 with SMTP id r2mr10480187lbb.41.1373281069648; Mon, 08 Jul 2013 03:57:49 -0700 (PDT)
Received: by 10.114.174.200 with HTTP; Mon, 8 Jul 2013 03:57:49 -0700 (PDT)
In-Reply-To: <20130708124403.41ad8f53@fls-nb.lan.streibelt.net>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net> <20130708093714.GA21377@nic.fr> <20130708115143.05b3b834@fls-nb.lan.streibelt.net> <20130708095510.GA29226@nic.fr> <CAB3ZD+=hqrK_Yx+6RDb21jv78+4-5kMqb_4e2aPpm+fVwEc7EA@mail.gmail.com> <20130708124403.41ad8f53@fls-nb.lan.streibelt.net>
Date: Mon, 8 Jul 2013 18:57:49 +0800
Message-ID: <CAB3ZD+=RzRa=+ktQzgTZTXoC+AZPCjXAuu3qx8QaKiZ+UdCCxQ@mail.gmail.com>
From: ice jew <jewforice@gmail.com>
To: Florian Streibelt <florian@inet.tu-berlin.de>
Content-Type: multipart/alternative; boundary=001a11c3d7b655507404e0fdeabc
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 10:57:52 -0000

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

I think ECS is good for CDNs. But it brings such a great extra load to both
the recursive resolver and the authoritative name servers.
The first question is to check if there're any other public recursive
resolver that supports ECS so I could ask it to enable the ESC white list
for our domain names.
The second question is to check if there is any research on how to increase
the popularity of ECS and how to make ECS higher performance.

Anyway ,thanks for your answer.



On Mon, Jul 8, 2013 at 6:44 PM, Florian Streibelt <florian@inet.tu-berlin.de
> wrote:

> On Mon, 8 Jul 2013 18:15:20 +0800
>  ice jew <jewforice@gmail.com> wrote:
>
> > There is 2 questions about deployment.
> > 1,Is there any other  recursive resolver that adopts ECS  except Google
> and
> > OpenDNS?
>
> That is not easy to tell. In the paper we focused on the authoritative NS.
> The reason is that e.g. google and opendns manually whitelist the
> authoritative nameservers they send ECS enabled queries to prevent failures
> in name resolution.
> (Some resolvers seem to behave quite strangly if they don't understand the
> extention.)
>
> > 2,Is there any open source solution of recursive resolver that supports
> ECS?
>
> I am not aware of any - for testing purposes I did a rough patch against a
> dns proxy but thats only usable for debuggging and not public.
> This makes it especially hard to get whitelisted to find answers to your
> first question.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

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

<div dir=3D"ltr">I think ECS is good for CDNs. But it brings such a great e=
xtra load to both the recursive resolver and the authoritative name servers=
.=A0<div>The first question is to check if there&#39;re any other public re=
cursive resolver that supports ECS so I could ask it to enable the ESC whit=
e list for our domain names.</div>
<div style>The second question is to check if there is any research on how =
to increase the popularity of ECS and how to make ECS higher performance.</=
div><div style><br></div><div style>Anyway ,thanks for your answer.</div>
<div style><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Mon, Jul 8, 2013 at 6:44 PM, Florian Streibelt <span dir=
=3D"ltr">&lt;<a href=3D"mailto:florian@inet.tu-berlin.de" target=3D"_blank"=
>florian@inet.tu-berlin.de</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 Mon, 8 Jul 2013 18:15:2=
0 +0800<br>
=A0ice jew &lt;<a href=3D"mailto:jewforice@gmail.com">jewforice@gmail.com</=
a>&gt; wrote:<br>
<br>
&gt; There is 2 questions about deployment.<br>
&gt; 1,Is there any other =A0recursive resolver that adopts ECS =A0except G=
oogle and<br>
&gt; OpenDNS?<br>
<br>
</div>That is not easy to tell. In the paper we focused on the authoritativ=
e NS.<br>
The reason is that e.g. google and opendns manually whitelist the authorita=
tive nameservers they send ECS enabled queries to prevent failures in name =
resolution.<br>
(Some resolvers seem to behave quite strangly if they don&#39;t understand =
the extention.)<br>
<div class=3D"im"><br>
&gt; 2,Is there any open source solution of recursive resolver that support=
s ECS?<br>
<br>
</div>I am not aware of any - for testing purposes I did a rough patch agai=
nst a dns proxy but thats only usable for debuggging and not public.<br>
This makes it especially hard to get whitelisted to find answers to your fi=
rst question.<br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<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>

--001a11c3d7b655507404e0fdeabc--

From jad@sinodun.com  Mon Jul  8 05:04:34 2013
Return-Path: <jad@sinodun.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F129A21F93B9 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 05:04:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTW+GVKaLG8h for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 05:04:28 -0700 (PDT)
Received: from cpanelsmarthost2.zen.co.uk (cpanelsmarthost2.zen.co.uk [82.71.204.226]) by ietfa.amsl.com (Postfix) with ESMTP id 2B56321F9E7B for <dnsop@ietf.org>; Mon,  8 Jul 2013 05:04:27 -0700 (PDT)
Received: from [88.98.24.67] (helo=shcp01.hosting.zen.net.uk) by cpanelsmarthost2.zen.co.uk with esmtp (Exim 4.72) (envelope-from <jad@sinodun.com>) id 1UwAB8-00070j-Fv for dnsop@ietf.org; Mon, 08 Jul 2013 12:04:26 +0000
Received: from 82-68-198-190.dsl.in-addr.zen.co.uk ([82.68.198.190]:16009 helo=[192.168.1.34]) by shcp01.hosting.zen.net.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <jad@sinodun.com>) id 1UwA1k-0002AB-SI for dnsop@ietf.org; Mon, 08 Jul 2013 12:54:45 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Dickinson <jad@sinodun.com>
In-Reply-To: <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com>
Date: Mon, 8 Jul 2013 11:54:47 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - shcp01.hosting.zen.net.uk
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - sinodun.com
X-Get-Message-Sender-Via: shcp01.hosting.zen.net.uk: authenticated_id: jad+sinodun.com/only user confirmed/virtual account not confirmed
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 12:04:34 -0000

Hi,

I have read draft draft-kumari-ogud-dnsop-cds-02. (Unfortunately, I have =
not=20
had time to read all the on list discussion, so apologies if I duplicate=20=

comments)

IMHO:

Section 1.2 and 2.2.1 (Highlighted roles) should be combined and used=20
consistently through-out.

Section 2.1 refers to parties, section 2.2 refers to entities. One =
should be=20
chosen and added to 1.2/2.2.1.

2.2:=20
- last instance of the word organization should be plural
- s/same as operates the enterprises DNS servers/same as that which =
operates=20
the enterprises DNS servers/
- "A domain name holder (child)" - It is not immediately obvious if this =
is the
child defined in the subsequent section.=20

2.2.1:
- Remove the "word" DNS from the end of both DNS operator definitions.
- s/clutural/cultural/
- s/child delegation/Child/


2.3:
- s/In number/In a number/
- s/A further complication is when the DNS Operation is separate from =
the
   Registrant./A further complication is when the Child DNS operator is =
not the
    Child./
- The sentence, "There are two common cases of this, registrar handles
   the DNS operation and a third party takes care of the DNS operation." =
would=20
   be clearer if it read something like "There are two common cases of =
this=20
   a) the registrar handles the DNS operation or b) a third party takes =
care of=20
   the DNS operation."
- reorder the following sentences to reflect the order a,b above.
- "the Registrant either needs to relay changes in DNS delegation" are =
we=20
   changing the delegation (implies NS to me)?
- "we will use the word "Child Operator", is this the same as Child DNS =
operator
   defined in 2.2.1? Also s/word/phrase/

2.4:
- "After a DNS operator first signs its zone" whose zone, which DNS =
operator?

3:
- First paragraph has nothing to do with the CDS (Child DS) record =
definition=20
   and should be (re-)moved.

3.1:
- Add a reference to the DS wire and presentation format. Also is there =
a need=20
   to give a reference for the RR code?

3.1.1:
- Given the difficulties that can occur with going unsigned, I think =
this=20
   section should be removed.

4.1
- much of the text in this section is not really about CDS Publication. =
The first=20
  sentence talks about consumption as does the final paragraph. Remove =
all text
  except the Location, Signer and Continuity sections. Keep the text =
"the=20
  absence of CDS record signals "No change" in the current DS set.  The =
use of=20
  CDS is optional."  Remove the MUST from Continuity - You can not tell =
a child=20
  DNS operator not to break their or their customers own zone - It might =
be a=20
  bad idea, but if that is what they want to do then so be it. It might =
be=20
  better if Continuity was at least in part the parents responsibility

4.2 and 4.3
- Move the final paragraph of 4.2 to section 4.1
- Move the third paragraph of 4.3 to section 4.1
- I dislike the wording in these 2 sections especially the=20
   term, "Parental Agent" who is this in 1.2/2.2.1?=20
   I suggest the following text:
=
--------------------------------------------------------------------------=
------
4.2.  CDS Consumption

4.2.1 Detecting a changed CDS
   How the Parent DNS operator (or registrar??? I will just use the term=20=

   Parent DNS operator from now on) detects changes to a CDS record may =
differ,=20
   below are two examples of how this can take place.

   Polling  The Parent DNS operator operates a tool that=20
            periodically checks each delegation that has a DS record to =
see=20
            if there is a CDS record.

   Pushing  The Parent DNS operator in its user interface has a button=20=

            {Fetch DS} that when pushed initiates the CDS processing. If =
the=20
            Parent zone does not contain a DS for this delegation then =
the=20
            "push" MUST be ignored.

   In either case the Parent DNS operator may apply additional rules
   that defer the acceptance of a CDS change, these rules may include a=20=

   condition that the CDS must remain in place and valid for some time =
period=20
   before it is accepted. It may be appropriate in the "Pushing" case to =
assume
   that the Child is ready and thus accept changes without delay.

   If the CDS RRset does not exist, the parent MUST take no action.
   Specifically it MUST NOT delete or alter the existing DS RRset.

4.2.2 Using the new CDS
   Regardless of how the Parent DNS operator detected changes to a CDS =
RR, the=20
   Parent DNS operator MUST use a DNSSEC validator to obtain a validated =
CDS=20
   RRset from the Child zone. It would be a good idea if the Parent DNS =
operator=20
   checked all NS RRs listed at the delegation. However, due to the use =
of=20
   technologies such as load balancing and anycast, this should not be =
taken as=20
   proof that the new CDS is present on all nodes serving the Child =
zone.

   The Parent DNS operator MUST ensure that old versions of the CDS =
RRset
   do not overwrite newer versions.  This MAY be accomplished by =
checking that=20
   the signature inception in the RRSIG for CDS is newer and/or the =
serial=20
   number on the child's SOA is greater. This may require the Parent DNS=20=

   operator to maintain some state information.

   The Parent DNS operator MAY take extra security measures. For =
example, to=20
   mitigate the possibility that a Child's key signing key has been =
compromised.
   The Parent DNS operator may, for example, inform ( by email or other=20=

   methods ) the Child DNS operator of the change.  However the precise=20=

   out-of-band measures that a parent zone SHOULD take are outside the=20=

   scope of this document.

   Once the Parent DNS operator has obtained a valid CDS it=20
   MAY double check the publication rules from section 4.1. In =
particular the=20
   Parent DNS operator MUST double check the Continuity rule and do its =
best not
   to invalidate the Child zone. Once checked and if the CDS and DS =
``differ''=20
   it may apply the changes to the parent zone.=20

=
--------------------------------------------------------------------------=
------

section 4.3 no longer exists

4.4
- Again terminology is a bit inconsistent

General Comments:
1. How will a "Child" know that the "Parent" is 'doing" CDS?
2. Section 4.4 makes this situation worse in requiring The DNS Parent to =
publish
   guidelines for the children as to what digest algorithms are =
acceptable=20
   in the CDS record
3. Given the vast range of possible interactions described in 2.2.1 I am =
not=20
   sure that this is any better than a child sending an "update".
4. Maybe I have missed this discussion, but, would it be better if=20
   the "Child" published a "CDS" containing the DNSKEY and left it up to=20=

   the "Parent" to digest?
5. I know I am biased! There is no discussion of key timing. I think=20
   that 4.1 should contain at least a reference to at least one of=20
   the excellent (expired but could be resurrected) drafts on the =
subject.



regards
John

---
jad@sinodun.com

http://sinodun.com

Sinodun Internet Technologies Ltd.
Stables 4, Suite 11,
Howbery Park,
Wallingford,
Oxfordshire,
OX10 8BA,
U.K.

+44 (0)1491 834957


From ogud@ogud.com  Mon Jul  8 11:04:12 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF50221F9C16 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 11:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N4lmRI7wdkIq for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 11:04:08 -0700 (PDT)
Received: from smtp85.ord1c.emailsrvr.com (smtp85.ord1c.emailsrvr.com [108.166.43.85]) by ietfa.amsl.com (Postfix) with ESMTP id 9687C21F9C0B for <dnsop@ietf.org>; Mon,  8 Jul 2013 11:04:08 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 31C4D50127; Mon,  8 Jul 2013 14:03:46 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id E1E8C50093;  Mon,  8 Jul 2013 14:03:43 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com>
Date: Mon, 8 Jul 2013 14:03:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com>
To: John Dickinson <jad@sinodun.com>
X-Mailer: Apple Mail (2.1508)
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 18:04:12 -0000

John,

Thanks for a excellent and timely review we just about pushing out a new =
version when it arrived.=20

We have accepted most of your edits and suggestions except when the text =
was already removed/reworded.=20

Instead I want to focus on your Q1: "How will a ``Child'' know if the =
``Parent'' is doing CDS?"=20
IMHO, we need to figure out how/if to place a flag in parent saying what =
kinds of "sync" it is willing to do from signed children.=20

	Olafur=20
On Jul 8, 2013, at 7:54 AM, John Dickinson <jad@sinodun.com> wrote:


> Hi,
>=20
> I have read draft draft-kumari-ogud-dnsop-cds-02. (Unfortunately, I =
have not=20
> had time to read all the on list discussion, so apologies if I =
duplicate=20
> comments)
>=20
> IMHO:
>=20
> Section 1.2 and 2.2.1 (Highlighted roles) should be combined and used=20=

> consistently through-out.
>=20
> Section 2.1 refers to parties, section 2.2 refers to entities. One =
should be=20
> chosen and added to 1.2/2.2.1.
>=20
> 2.2:=20
> - last instance of the word organization should be plural
> - s/same as operates the enterprises DNS servers/same as that which =
operates=20
> the enterprises DNS servers/
> - "A domain name holder (child)" - It is not immediately obvious if =
this is the
> child defined in the subsequent section.=20
>=20
> 2.2.1:
> - Remove the "word" DNS from the end of both DNS operator definitions.
> - s/clutural/cultural/
> - s/child delegation/Child/
>=20
>=20
> 2.3:
> - s/In number/In a number/
> - s/A further complication is when the DNS Operation is separate from =
the
>   Registrant./A further complication is when the Child DNS operator is =
not the
>    Child./
> - The sentence, "There are two common cases of this, registrar handles
>   the DNS operation and a third party takes care of the DNS =
operation." would=20
>   be clearer if it read something like "There are two common cases of =
this=20
>   a) the registrar handles the DNS operation or b) a third party takes =
care of=20
>   the DNS operation."
> - reorder the following sentences to reflect the order a,b above.
> - "the Registrant either needs to relay changes in DNS delegation" are =
we=20
>   changing the delegation (implies NS to me)?
> - "we will use the word "Child Operator", is this the same as Child =
DNS operator
>   defined in 2.2.1? Also s/word/phrase/
>=20
> 2.4:
> - "After a DNS operator first signs its zone" whose zone, which DNS =
operator?
>=20
> 3:
> - First paragraph has nothing to do with the CDS (Child DS) record =
definition=20
>   and should be (re-)moved.
>=20
This paragraph was moved to background section.=20

> 3.1:
> - Add a reference to the DS wire and presentation format. Also is =
there a need=20
>   to give a reference for the RR code?
>=20
> 3.1.1:
> - Given the difficulties that can occur with going unsigned, I think =
this=20
>   section should be removed.
>=20
> 4.1
> - much of the text in this section is not really about CDS =
Publication. The first=20
>  sentence talks about consumption as does the final paragraph. Remove =
all text
>  except the Location, Signer and Continuity sections. Keep the text =
"the=20
>  absence of CDS record signals "No change" in the current DS set.  The =
use of=20
>  CDS is optional."  Remove the MUST from Continuity - You can not tell =
a child=20
>  DNS operator not to break their or their customers own zone - It =
might be a=20
>  bad idea, but if that is what they want to do then so be it. It might =
be=20
>  better if Continuity was at least in part the parents responsibility
>=20
> 4.2 and 4.3
> - Move the final paragraph of 4.2 to section 4.1
> - Move the third paragraph of 4.3 to section 4.1
> - I dislike the wording in these 2 sections especially the=20
>   term, "Parental Agent" who is this in 1.2/2.2.1?=20
>   I suggest the following text:
> =
--------------------------------------------------------------------------=
------
> 4.2.  CDS Consumption
>=20
> 4.2.1 Detecting a changed CDS
>   How the Parent DNS operator (or registrar??? I will just use the =
term=20
>   Parent DNS operator from now on) detects changes to a CDS record may =
differ,=20
>   below are two examples of how this can take place.
>=20
>   Polling  The Parent DNS operator operates a tool that=20
>            periodically checks each delegation that has a DS record to =
see=20
>            if there is a CDS record.
>=20
>   Pushing  The Parent DNS operator in its user interface has a button=20=

>            {Fetch DS} that when pushed initiates the CDS processing. =
If the=20
>            Parent zone does not contain a DS for this delegation then =
the=20
>            "push" MUST be ignored.
>=20
>   In either case the Parent DNS operator may apply additional rules
>   that defer the acceptance of a CDS change, these rules may include a=20=

>   condition that the CDS must remain in place and valid for some time =
period=20
>   before it is accepted. It may be appropriate in the "Pushing" case =
to assume
>   that the Child is ready and thus accept changes without delay.
>=20
>   If the CDS RRset does not exist, the parent MUST take no action.
>   Specifically it MUST NOT delete or alter the existing DS RRset.
>=20
> 4.2.2 Using the new CDS
>   Regardless of how the Parent DNS operator detected changes to a CDS =
RR, the=20
>   Parent DNS operator MUST use a DNSSEC validator to obtain a =
validated CDS=20
>   RRset from the Child zone. It would be a good idea if the Parent DNS =
operator=20
>   checked all NS RRs listed at the delegation. However, due to the use =
of=20
>   technologies such as load balancing and anycast, this should not be =
taken as=20
>   proof that the new CDS is present on all nodes serving the Child =
zone.
>=20
>   The Parent DNS operator MUST ensure that old versions of the CDS =
RRset
>   do not overwrite newer versions.  This MAY be accomplished by =
checking that=20
>   the signature inception in the RRSIG for CDS is newer and/or the =
serial=20
>   number on the child's SOA is greater. This may require the Parent =
DNS=20
>   operator to maintain some state information.
>=20
>   The Parent DNS operator MAY take extra security measures. For =
example, to=20
>   mitigate the possibility that a Child's key signing key has been =
compromised.
>   The Parent DNS operator may, for example, inform ( by email or other=20=

>   methods ) the Child DNS operator of the change.  However the precise=20=

>   out-of-band measures that a parent zone SHOULD take are outside the=20=

>   scope of this document.
>=20
>   Once the Parent DNS operator has obtained a valid CDS it=20
>   MAY double check the publication rules from section 4.1. In =
particular the=20
>   Parent DNS operator MUST double check the Continuity rule and do its =
best not
>   to invalidate the Child zone. Once checked and if the CDS and DS =
``differ''=20
>   it may apply the changes to the parent zone.=20
>=20
> =
--------------------------------------------------------------------------=
------
>=20
> section 4.3 no longer exists
>=20
> 4.4
> - Again terminology is a bit inconsistent
>=20
> General Comments:
> 1. How will a "Child" know that the "Parent" is 'doing" CDS?
> 2. Section 4.4 makes this situation worse in requiring The DNS Parent =
to publish
>   guidelines for the children as to what digest algorithms are =
acceptable=20
>   in the CDS record

see above.=20
> 3. Given the vast range of possible interactions described in 2.2.1 I =
am not=20
>   sure that this is any better than a child sending an "update".

Open issue "where to send update to?"

> 4. Maybe I have missed this discussion, but, would it be better if=20
>   the "Child" published a "CDS" containing the DNSKEY and left it up =
to=20
>   the "Parent" to digest?

Religion issue, CDS is 'easier' to compare than DNSKEY=20
> 5. I know I am biased! There is no discussion of key timing. I think=20=

>   that 4.1 should contain at least a reference to at least one of=20
>   the excellent (expired but could be resurrected) drafts on the =
subject.
>=20
good suggestion, added reference=20

>=20
>=20
> regards
> John
>=20
> ---
> jad@sinodun.com
>=20
> http://sinodun.com
>=20
> Sinodun Internet Technologies Ltd.
> Stables 4, Suite 11,
> Howbery Park,
> Wallingford,
> Oxfordshire,
> OX10 8BA,
> U.K.
>=20
> +44 (0)1491 834957
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From paf@frobbit.se  Mon Jul  8 11:29:03 2013
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51CCE21F9C86 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 11:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y+4Lfv4m-uI6 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 11:28:59 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id D04E321F9C85 for <dnsop@ietf.org>; Mon,  8 Jul 2013 11:28:50 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::14] (unknown [IPv6:2a02:80:3ffc::14]) by mail.frobbit.se (Postfix) with ESMTPSA id D53D423F63; Mon,  8 Jul 2013 20:28:41 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com>
Date: Mon, 8 Jul 2013 20:28:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>, John Dickinson <jad@sinodun.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 18:29:03 -0000

I have also had a look at this document which I in general do believe is =
sound, although there are a few events I would like to have described in =
the document. Reason for this is that I see it being really important =
that it is implemented the same way in all usage scenarios.

One such situation is what is to happen when NS records changes in the =
parent zone.

An immediate reaction is that change of NS records should trigger fetch =
of CDS record from the child zone so that the new DS can be included in =
the new version of the zone that have the new NS records. Careful =
thinking should say whether that is a correct thinking of me.

Another situation is what to do (by the parent) when inconsistent CDS =
records are found from the authoritative servers for the zone (with and =
without identical serial numbers in the SOA).

And a third if the auth servers queried at should be the ones that there =
are NS records for in the parent zone or the NS records that exists in =
the child zone.

This to resolve inconsistencies between information in parent and child =
zones and between auth servers.

Lastly, I think it should be very clear not only what the priority is =
between different versions of CDS records, but also between CDS records =
and epp commands. If different registries implement different policies =
here, the world might risk being much messier than what we want.

Hope this helps.

   Patrik


From bdickson@verisign.com  Mon Jul  8 11:50:14 2013
Return-Path: <bdickson@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9963B21F9590 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 11:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8o+bQ7zN7io3 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 11:50:08 -0700 (PDT)
Received: from exprod6og123.obsmtp.com (exprod6og123.obsmtp.com [64.18.1.241]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5CB21F9D39 for <dnsop@ietf.org>; Mon,  8 Jul 2013 11:50:03 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob123.postini.com ([64.18.5.12]) with SMTP ID DSNKUdsJ2lK+RTPX+UY9wBEXxr2kiRC61RW1@postini.com; Mon, 08 Jul 2013 11:50:08 PDT
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id r68Insal002808 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 8 Jul 2013 14:49:58 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Mon, 8 Jul 2013 14:49:54 -0400
From: "Dickson, Brian" <bdickson@verisign.com>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, Olafur Gudmundsson <ogud@ogud.com>, John Dickinson <jad@sinodun.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Thread-Topic: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
Thread-Index: AQHOfAvuWrMAm5DHG0e1RfsSfo7aNQ==
Date: Mon, 8 Jul 2013 18:49:53 +0000
Message-ID: <CE0080AE.B7C0%bdickson@verisign.com>
In-Reply-To: <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <36A7349490ADBB40B0DDAA946E6E3DDB@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 18:50:14 -0000

On 7/8/13 2:28 PM, "Patrik F=E4ltstr=F6m" <paf@frobbit.se> wrote:

>I have also had a look at this document which I in general do believe is
>sound, although there are a few events I would like to have described in
>the document. Reason for this is that I see it being really important
>that it is implemented the same way in all usage scenarios.
>
>One such situation is what is to happen when NS records changes in the
>parent zone.


I think, perhaps, that a corresponding mechanism for NS change (or change
validation), will be what we eventually conclude is also a good idea (or
even necessary to provide some means of protection/validation to an
otherwise unprotected-but-critical element).

For the same kinds of reasons as parent/child DS vs DNSKEY "mismatch"
(pre-publication of DS without publication of DNSKEY), there are reasons
that parent and child NS sets are not always the same.

So, using the child NS set to directly validate the parent NS set is a
non-starter.

However, maybe something like a "PNS" (parent NS) in the child, where the
child is authoritative for the data, could signal {change | validation}
(depending on the RRR requirements), would do the trick?

Upon receiving a change request for the NS set, the zone publisher could
check the child for matching PNS records.

Facilitates automation, just as CDS would.

Thoughts?

Brian


>
>An immediate reaction is that change of NS records should trigger fetch
>of CDS record from the child zone so that the new DS can be included in
>the new version of the zone that have the new NS records. Careful
>thinking should say whether that is a correct thinking of me.
>
>Another situation is what to do (by the parent) when inconsistent CDS
>records are found from the authoritative servers for the zone (with and
>without identical serial numbers in the SOA).
>
>And a third if the auth servers queried at should be the ones that there
>are NS records for in the parent zone or the NS records that exists in
>the child zone.
>
>This to resolve inconsistencies between information in parent and child
>zones and between auth servers.
>
>Lastly, I think it should be very clear not only what the priority is
>between different versions of CDS records, but also between CDS records
>and epp commands. If different registries implement different policies
>here, the world might risk being much messier than what we want.
>
>Hope this helps.
>
>   Patrik
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop


From paf@frobbit.se  Mon Jul  8 12:32:23 2013
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E41421F9C55 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 12:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y7dOwmrDYsSs for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 12:32:21 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 5334821F9C53 for <dnsop@ietf.org>; Mon,  8 Jul 2013 12:32:21 -0700 (PDT)
Received: from vpn-client-208.netnod.se (vpn-client-208.netnod.se [192.71.80.208]) by mail.frobbit.se (Postfix) with ESMTPSA id 9C4C923F8D; Mon,  8 Jul 2013 21:32:19 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <CE0080AE.B7C0%bdickson@verisign.com>
Date: Mon, 8 Jul 2013 21:32:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3DDD5D2-D59E-4026-BF99-2820281788B6@frobbit.se>
References: <CE0080AE.B7C0%bdickson@verisign.com>
To: "Dickson, Brian" <bdickson@verisign.com>
X-Mailer: Apple Mail (2.1508)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Jul 2013 19:32:23 -0000

On 8 jul 2013, at 20:49, "Dickson, Brian" <bdickson@verisign.com> wrote:

> However, maybe something like a "PNS" (parent NS) in the child, where =
the
> child is authoritative for the data, could signal {change | =
validation}
> (depending on the RRR requirements), would do the trick?

Might solve some events, but I do not think it solves the most important =
situation, that DNS is moved from one DNS provider to another. The old =
DNS provider can not be asked to enter NS records for the gaining =
provider... And using NS (in reality, as you look for auth servers) to =
fetch NS data seems to me be a bit...fishy... ;-) The attack vector =
against such a situation is very complicated.

   Patrik


From ajs@anvilwalrusden.com  Mon Jul  8 18:40:08 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E107921F8651 for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 18:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zRGO48H20Oyz for <dnsop@ietfa.amsl.com>; Mon,  8 Jul 2013 18:40:03 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 221F121F9A38 for <dnsop@ietf.org>; Mon,  8 Jul 2013 18:40:02 -0700 (PDT)
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 8A5698A031 for <dnsop@ietf.org>; Tue,  9 Jul 2013 01:40:00 +0000 (UTC)
Date: Mon, 8 Jul 2013 21:39:58 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20130709013958.GD20597@mx1.yitter.info>
References: <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se> <CE0080AE.B7C0%bdickson@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CE0080AE.B7C0%bdickson@verisign.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 01:40:09 -0000

On Mon, Jul 08, 2013 at 06:49:53PM +0000, Dickson, Brian wrote:
> 
> Thoughts?

My immediate thought is, "What problem is this trying to solve?"

In the DNSSSEC case, the problem is that you're trying not to break
the chain of trust, and you need a mechanism that is cryptographically
securable to make the communication.  This is made harder in some
sense by the fact that the DS and DNSKEY RRsets are authoritative on
different sides of the zone cut.

In the NS case, because the child side RRset is the really
authoritative one, that's the one that generally gets cached.  Since
both sides of the cut have the same RRTYPE, and since only one of the
RRsets can be cached, you end up with only one such set and it's the
one that gets used.

It's it possible to bollocks this so that resolution fails?  Yes.  But
that's not a result of disagreement between two different RRsets, so
in this case having the additional communication path (especially
inside the DNS) is less necessary.

Best,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Antoin.Verschuren@sidn.nl  Tue Jul  9 00:46:13 2013
Return-Path: <Antoin.Verschuren@sidn.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4709321F9ECA for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 00:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.798
X-Spam-Level: 
X-Spam-Status: No, score=-0.798 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uu3lb5ETgW3C for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 00:46:09 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 95A0B21F9D35 for <dnsop@ietf.org>; Tue,  9 Jul 2013 00:46:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=q3gFXIa7Vi1vir/NkahMcx6JTlMFEaP/arTB8Rg6DSc=; b=EhOZWYbehk6Uxg4dl/eNRGyoS+uIRylZaVKJn/wDpNgFQlYP8sRp8daBcBVsjHbcOduW9uvY9E3fKzyhtoio6ETXc8bT9hBta2ZERgbqDnYaQFS4SfzxQRZ9YhQTgSXhBb35yz5s3QivVHPJ4pvXFEwyCn5/SZKCvVfPrLBwhw8=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r697k6pX018141-r697k6pZ018141 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL) for <dnsop@ietf.org>; Tue, 9 Jul 2013 09:46:06 +0200
Received: from KAHUBCAS1.SIDN.local (192.168.2.41) by kahubcasn02.SIDN.local (192.168.2.74) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 9 Jul 2013 09:46:01 +0200
Received: from [94.198.152.214] (94.198.152.214) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 9 Jul 2013 09:46:06 +0200
Message-ID: <51DBBFBD.5020300@sidn.nl>
Date: Tue, 9 Jul 2013 09:46:05 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: <dnsop@ietf.org>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com> <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se>
In-Reply-To: <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [94.198.152.214]
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 07:46:13 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 08-07-13 20:28, Patrik Fältström schreef:

> One such situation is what is to happen when NS records changes in
> the parent zone.
> 
> An immediate reaction is that change of NS records should trigger
> fetch of CDS record from the child zone so that the new DS can be
> included in the new version of the zone that have the new NS
> records. Careful thinking should say whether that is a correct
> thinking of me.

Why would DS records change when NS records change?
I guess you're thinking only one scenario here, and that is when NS
records change, the DNS operator of the master changes and the zone
will get different key material. But this is not the general case,
only the most difficult one to solve. Only changing one slave NS by
another does not change the operator maintaining the key material.

Changing the operator maintaining the key material does happen, and
when it does, changing the DS after changing the NS will not help you
autoprovision. The zone will get bogus if you change the DS after
changing the NS, and so no CDS change can be validated at all.
Changing the key material operator needs pre-publishing of the new key
material in the zone of the losing operator for the NS change to be
validated. The new NS RRset in the child is signed with the new key
material only.
I know you all wish the world was simpler, but it isn't, We've tried.

> And a third if the auth servers queried at should be the ones that
> there are NS records for in the parent zone or the NS records that
> exists in the child zone.

I agree with Andrew here that the NS RRset in the child zone is
authoritative, but it can only be used if validated.

> Lastly, I think it should be very clear not only what the priority
> is between different versions of CDS records, but also between CDS
> records and epp commands. If different registries implement
> different policies here, the world might risk being much messier
> than what we want.

Exactly my statement.


- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  M: +31 6 23368970
Mailto: antoin.verschuren@sidn.nl
XMPP: antoin.verschuren@jabber.sidn.nl
HTTP://www.sidn.nl/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJR27+5AAoJEDqHrM883Agn4wsH/1xXv9FkndogVEbzUQdLZhLD
XB7JqT1QmKATKf+Ec6Rp1RLsA6QgA8XvyZOSzlUM/jEGARtldp1YncPsue/FO7an
oRaTi/vk4o1rR+e8A/LKZvl0Ix0RbVZ+yA2NS+TtXCKm/eMJOjZy5TA9oNwINhfA
55d+V+jVro5rdfNO8yRflpe+Np3M9AOWmPdTgLTlw6axwvh8bZeJJ4jHjmrxpQWm
GhXpVuRztG1+TJP+zBStKNNvvnMFps7oL3fdb+UlbI67f7KSpSfG4eyw3GSO/poA
0XF6nOfWZD/QFQoBIq8gWi4od2J9ImOcgsrCofnT+CdOP9+IBzQiYQqKxZHeDH0=
=34D4
-----END PGP SIGNATURE-----

From Antoin.Verschuren@sidn.nl  Tue Jul  9 00:51:54 2013
Return-Path: <Antoin.Verschuren@sidn.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADE3B21F9F6B for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 00:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.771
X-Spam-Level: 
X-Spam-Status: No, score=-0.771 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXeO+SmSIgzP for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 00:51:50 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 02D7721F9F4C for <dnsop@ietf.org>; Tue,  9 Jul 2013 00:51:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=05KrD6N0bfqnK/mELJguKGnk9Qd2DKXYQw8TbiJ0Az8=; b=f6ttiVPee4Iz43lW2J5wz3nWTudQV0w36SIpiYRAzRZZ64oflY1F9d15nA8wRjcWegBAfFCeMAH4HuiNPAJhcLzON2ANMx5ISaBaZ6LRM+7bkjLt4Y87TMFnRQVB23Yhhsdwdud4txWJGz5xNTxuyoTjmb4fbxq3JfTl+jRIceY=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r697pnI4018441-r697pnI6018441 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL) for <dnsop@ietf.org>; Tue, 9 Jul 2013 09:51:49 +0200
Received: from KAHUBCAS1.SIDN.local (192.168.2.41) by kahubcasn02.SIDN.local (192.168.2.74) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 9 Jul 2013 09:51:44 +0200
Received: from [94.198.152.214] (94.198.152.214) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 9 Jul 2013 09:51:49 +0200
Message-ID: <51DBC114.6000407@sidn.nl>
Date: Tue, 9 Jul 2013 09:51:48 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: <dnsop@ietf.org>
References: <CE0080AE.B7C0%bdickson@verisign.com>
In-Reply-To: <CE0080AE.B7C0%bdickson@verisign.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 07:51:54 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 08-07-13 20:49, Dickson, Brian schreef:

> Upon receiving a change request for the NS set, the zone publisher
> could check the child for matching PNS records.
> 
> Facilitates automation, just as CDS would.
> 
> Thoughts?

That's why I said I liked draft-hardaker-dnsop-csync-00.txt better, as
it tries to solve the more general case of sending technical
delegation data from child to parent, whether it is NS, DS, DNSKEY, or
any other records we might need in the future to maintain a delegation.

- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  M: +31 6 23368970
Mailto: antoin.verschuren@sidn.nl
XMPP: antoin.verschuren@jabber.sidn.nl
HTTP://www.sidn.nl/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJR28EUAAoJEDqHrM883AgnzTgH/RjGNu4DL23dJP1SCPkqbRLc
SmdzbHHqOgszK7gb+x4crWzpo6w5WhFZNonrod1UXyXpLapJuzezSBlTAdboWgAi
0ZPUPwEaEeoe+Ser+5oj68PWC1WJE0HP8pLAowy6QOJ4Umg24iwAo4OH8PjyIPVR
LSibZU0gB1TdK4KcXIOll8JEvx9tfncy45lHXjf3f58I+8t3+1jb5yACQHEMIRd3
y8b5FxmphppQ/X67uumhAcDLtCBKsX0oEYRAH1FF2+hn8vaabat7J+u6EhH6E/+6
Qc+CC2hNm9+lR32Ecl437EEeW0s6SDmxWUGShqq6A6zMfOgKaAKJICipnJ5+CNg=
=iPqi
-----END PGP SIGNATURE-----

From paf@frobbit.se  Tue Jul  9 01:05:19 2013
Return-Path: <paf@frobbit.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97CF821F9AA7 for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 01:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4LRBl0Yc4RI for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 01:05:19 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id C8B4821F9AA2 for <dnsop@ietf.org>; Tue,  9 Jul 2013 01:05:18 -0700 (PDT)
Received: from [192.165.72.14] (unknown [192.165.72.14]) by mail.frobbit.se (Postfix) with ESMTPSA id 5F9FA22003; Tue,  9 Jul 2013 10:05:17 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_60D6E87C-3D4A-4C3F-A05B-6140696AE292"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <51DBBFBD.5020300@sidn.nl>
Date: Tue, 9 Jul 2013 10:05:17 +0200
Message-Id: <791FD3EC-91F6-448E-80D7-DC607A02AA2B@frobbit.se>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com> <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se> <51DBBFBD.5020300@sidn.nl>
To: Antoin Verschuren <antoin.verschuren@sidn.nl>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 08:05:19 -0000

--Apple-Mail=_60D6E87C-3D4A-4C3F-A05B-6140696AE292
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 9 jul 2013, at 09:46, Antoin Verschuren <antoin.verschuren@sidn.nl> =
wrote:

> Signed PGP part
> Op 08-07-13 20:28, Patrik F=E4ltstr=F6m schreef:
>=20
> > One such situation is what is to happen when NS records changes in
> > the parent zone.
> >=20
> > An immediate reaction is that change of NS records should trigger
> > fetch of CDS record from the child zone so that the new DS can be
> > included in the new version of the zone that have the new NS
> > records. Careful thinking should say whether that is a correct
> > thinking of me.
>=20
> Why would DS records change when NS records change?
> I guess you're thinking only one scenario here, and that is when NS
> records change, the DNS operator of the master changes and the zone
> will get different key material. But this is not the general case,
> only the most difficult one to solve. Only changing one slave NS by
> another does not change the operator maintaining the key material.

I am only saying change of the NS record should _trigger_ a fetch of the =
CDS. If the CDS has not changed, then the DNSSEC data in the parent =
should not change.

> Changing the operator maintaining the key material does happen, and
> when it does, changing the DS after changing the NS will not help you
> autoprovision. The zone will get bogus if you change the DS after
> changing the NS, and so no CDS change can be validated at all.

The registry get an EPP update via a secure channel to change the NS. =
They can at that time (before the new zone is published) issue queries =
for CDS at the suggested new target of the NS, and if the CDS exists =
there they can fetch the CDS, see if key material changed, and =
incorporate the data in the zone that is to be published.

> Changing the key material operator needs pre-publishing of the new key
> material in the zone of the losing operator for the NS change to be
> validated. The new NS RRset in the child is signed with the new key
> material only.
> I know you all wish the world was simpler, but it isn't, We've tried.

For newcomers to this discussion, Antoin and myself is in the middle of =
this discussion about how to do a change of DNS operator (and because of =
that change of maintainer of key material) in reality. We have, as you =
can see, different opinion on the topic :-)

> > And a third if the auth servers queried at should be the ones that
> > there are NS records for in the parent zone or the NS records that
> > exists in the child zone.
>=20
> I agree with Andrew here that the NS RRset in the child zone is
> authoritative, but it can only be used if validated.

But it can be validated thanks to the trust in the epp channel.

> > Lastly, I think it should be very clear not only what the priority
> > is between different versions of CDS records, but also between CDS
> > records and epp commands. If different registries implement
> > different policies here, the world might risk being much messier
> > than what we want.
>=20
> Exactly my statement.

   Patrik


--Apple-Mail=_60D6E87C-3D4A-4C3F-A05B-6140696AE292
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-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)

iD8DBQFR28Q9rMabGguI180RAm97AKCM/s/n/zIrSEwWNKizrbjU4tYrVgCfX37s
edxKol0b+OSRZJDcjSTOHzM=
=5niQ
-----END PGP SIGNATURE-----

--Apple-Mail=_60D6E87C-3D4A-4C3F-A05B-6140696AE292--

From Antoin.Verschuren@sidn.nl  Tue Jul  9 02:57:10 2013
Return-Path: <Antoin.Verschuren@sidn.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB16E21F9F81 for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 02:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.607
X-Spam-Level: 
X-Spam-Status: No, score=-0.607 tagged_above=-999 required=5 tests=[AWL=-0.192, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GlfrmbbjSLA1 for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 02:57:06 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id E0C6321F9F8D for <dnsop@ietf.org>; Tue,  9 Jul 2013 02:56:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=CUpLxCRl1vw092LHH77+SDxwVJFaVwvwWElrlQlGMpg=; b=cJxMr9F/qnueDyii/CBLfD6/cy7jrXg81cevWfMdd+9+aLHoqJ/S+F7YkjP0mkj9LhKfB3dqzuTcyLkYDTAwECKPiLxl40I4gueKtiSRl+BOr0ixhIVGGK+YwaQqqFAo2fuvbNLcBW9Sta3KqSyRB1XHE9Jh0I2Hw5e21BQbzTE=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r699ul5h024269-r699ul5j024269 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Tue, 9 Jul 2013 11:56:47 +0200
Received: from KAHUBCAS1.SIDN.local (192.168.2.41) by kahubcasn02.SIDN.local (192.168.2.74) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 9 Jul 2013 11:56:42 +0200
Received: from [94.198.152.214] (94.198.152.214) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 9 Jul 2013 11:56:48 +0200
Message-ID: <51DBDE5E.9070805@sidn.nl>
Date: Tue, 9 Jul 2013 11:56:46 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com> <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se> <51DBBFBD.5020300@sidn.nl> <791FD3EC-91F6-448E-80D7-DC607A02AA2B@frobbit.se>
In-Reply-To: <791FD3EC-91F6-448E-80D7-DC607A02AA2B@frobbit.se>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [94.198.152.214]
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 09:57:10 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 09-07-13 10:05, Patrik Fältström schreef:
> 
> The registry get an EPP update via a secure channel to change the
> NS. They can at that time (before the new zone is published) issue
> queries for CDS at the suggested new target of the NS, and if the
> CDS exists there they can fetch the CDS, see if key material
> changed, and incorporate the data in the zone that is to be
> published.

That CDS record will not validate at that point in time, so it will
always be ignored.
The pre-requisite for CDS is that the record can be validated, and the
new zone is not yet in the chain of trust if the DNSKEY RRset that is
present in the validating resolver does not contain the key by which
the CDS record in the new zone is signed.

You could do a theoretical validation of that record with the assumed
future state of the zone and delegation at the parent, but all
validating resolvers in the real world will have a DNSKEY RRset cached
from the past, and are not aware of any future change until after it
has happened. So during the DNSKEY TTL all records that should
validate against the DNSKEY RRset will have a chance of being bogus,
depending on from which zone the signatures come and which DNSKEY
RRset is cached..
Unless you have pre-published a DNSKEY RRset that contains the ZSK's
of both zones, so both signatures validate.

But then there is no need to query the CDS record, because you cannot
do a simultaneous second key rollover during a key maintainer change.
You'll have to wait at least one child NS TTL after the NS change at
the parent until it's safe to remove the old key and do another key
rollover, so querying CDS immediately after changing the NS at the
parent will always result in zero changes if you want your zone to work.


- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  M: +31 6 23368970
Mailto: antoin.verschuren@sidn.nl
XMPP: antoin.verschuren@jabber.sidn.nl
HTTP://www.sidn.nl/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJR295eAAoJEDqHrM883AgnFC4IANZXG6Rl8HB3U6U7UZS3URxf
ham8o3+5hi9nx1s1KN4zljBWjnL0O0N2jBK+keSWLHLmmWzinFMjtHEv4RFaE9Ho
++jC0kZT2Z0Re65A2ZOh9lewpSvzBul9axcrD10w/yehVJhm5L4mAOhoL29dsegv
PMsHpqDy1DJ0MvWrx+wdzGKTCG0S79SAbUedt0kLPt8tH0FFMAFUON1yFj3cYp2W
ovpWGN1R0ex7g66CCSBWcx5otp8GJx1wIs1pra1xt3QmhOHTxKzGkuRIUjRRpMf7
AoogKu6i1LnxFVwGmlZab2Gebkx0g5aY3whrxZ65g30Wn1kPcFS1QBeHrQO+vDI=
=A5ER
-----END PGP SIGNATURE-----

From ogud@ogud.com  Tue Jul  9 06:47:22 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB4CE21F9A98 for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 06:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gsnQ6Gtp9q3y for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 06:47:17 -0700 (PDT)
Received: from smtp85.ord1c.emailsrvr.com (smtp85.ord1c.emailsrvr.com [108.166.43.85]) by ietfa.amsl.com (Postfix) with ESMTP id BCEDF21F9930 for <dnsop@ietf.org>; Tue,  9 Jul 2013 06:47:17 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 71978500DD; Tue,  9 Jul 2013 09:47:16 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 8163A500AE;  Tue,  9 Jul 2013 09:47:14 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <51DBDE5E.9070805@sidn.nl>
Date: Tue, 9 Jul 2013 09:47:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E4D91F9-6D76-4677-9257-1470FD60E19F@ogud.com>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com> <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se> <51DBBFBD.5020300@sidn.nl> <791FD3EC-91F6-448E-80D7-DC607A02AA2B@frobbit.se> <51DBDE5E.9070805@sidn.nl>
To: Antoin Verschuren <Antoin.Verschuren@sidn.nl>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 13:47:22 -0000

On Jul 9, 2013, at 5:56 AM, Antoin Verschuren =
<Antoin.Verschuren@sidn.nl> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Op 09-07-13 10:05, Patrik F=E4ltstr=F6m schreef:
>>=20
>> The registry get an EPP update via a secure channel to change the
>> NS. They can at that time (before the new zone is published) issue
>> queries for CDS at the suggested new target of the NS, and if the
>> CDS exists there they can fetch the CDS, see if key material
>> changed, and incorporate the data in the zone that is to be
>> published.
>=20
> That CDS record will not validate at that point in time, so it will
> always be ignored.
> The pre-requisite for CDS is that the record can be validated, and the
> new zone is not yet in the chain of trust if the DNSKEY RRset that is
> present in the validating resolver does not contain the key by which
> the CDS record in the new zone is signed.

Antion,  is right  CDS or CSYNC can only help with operator change
when the OLD operator is highly cooperative.=20
Old Operator has to be  willing and able to publish change information =
about the new operator=20
in its copy of the zone and it has to publish it long enough for the=20
parent to pick it up.

	Olafur


From warren@kumari.net  Tue Jul  9 14:38:06 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F8D21F9CD7 for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 14:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uishzETQCw0K for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 14:38:01 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5937711E817B for <dnsop@ietf.org>; Tue,  9 Jul 2013 14:37:52 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 81A611B405D8; Tue,  9 Jul 2013 17:37:43 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
Date: Tue, 9 Jul 2013 17:37:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8A9D451-9EB1-4ECB-A679-B3F79351599B@kumari.net>
References: <20130709211952.6456.4774.idtracker@ietfa.amsl.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: [DNSOP] Fwd: Confirmation for Auto-Post of I-D draft-kumari-ogud-dnsop-cds
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 21:38:06 -0000

Hi there all,

We have just submitted a new version of this draft.

We have incorporates most of the comments received (thanks to everyone =
who submitted them).
It has also undergone an fairly large re-factorization to improve =
readability / understandability.=20


Here are the diffs from the previous version:  =
http://tools.ietf.org/rfcdiff?url2=3Ddraft-kumari-ogud-dnsop-cds-02.txt

W

Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Subject: Confirmation for Auto-Post of I-D draft-kumari-ogud-dnsop-cds
> Date: July 9, 2013 5:19:52 PM EDT
> To: Olafur Gudmundsson <ogud@ogud.com>, Warren Kumari =
<warren@kumari.net>, George Barwood <george.barwood@blueyonder.co.uk>
>=20
>=20
> Hi,
>=20
> The IETF datatracker draft submission service has received your draft
> draft-kumari-ogud-dnsop-cds-03, and requires a
> confirmation step in order to be able to complete the posting of
> the draft.
>=20
> Please follow this link to the page where you can confirm the posting:
> Confirmation URL: =
http://datatracker.ietf.org/submit/status/52062/confirm/901c134f53dbef28c7=
c7fe6811cc6a7320d5f1a2/
>=20
>=20
> Best regards,
>=20
> 	The IETF Secretariat
> 	through the draft submission service
>=20
>=20

--=20
Eagles soar but a weasel will never get sucked into a jet engine=20



From bdickson@verisign.com  Tue Jul  9 16:06:24 2013
Return-Path: <bdickson@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE8511E8195 for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 16:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fzsb7YnHoqTZ for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 16:06:19 -0700 (PDT)
Received: from exprod6og127.obsmtp.com (exprod6og127.obsmtp.com [64.18.1.78]) by ietfa.amsl.com (Postfix) with ESMTP id DD1CD11E80C5 for <dnsop@ietf.org>; Tue,  9 Jul 2013 16:06:17 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob127.postini.com ([64.18.5.12]) with SMTP ID DSNKUdyXaSZ76pHLN03W4fPK3H5GPpoFw8Ui@postini.com; Tue, 09 Jul 2013 16:06:18 PDT
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id r69N6Cm5008918 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Jul 2013 19:06:12 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Tue, 9 Jul 2013 19:06:12 -0400
From: "Dickson, Brian" <bdickson@verisign.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
Thread-Index: AQHOfAvuWrMAm5DHG0e1RfsSfo7aNZlb1WYAgAEkTgA=
Date: Tue, 9 Jul 2013 23:06:11 +0000
Message-ID: <CE020CA5.B81E%bdickson@verisign.com>
In-Reply-To: <20130709013958.GD20597@mx1.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A6C6C4827C29824FB21551CAC24D646B@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 09 Jul 2013 23:06:25 -0000

On 7/8/13 9:39 PM, "Andrew Sullivan" <ajs@anvilwalrusden.com> wrote:

>On Mon, Jul 08, 2013 at 06:49:53PM +0000, Dickson, Brian wrote:
>>=20
>> Thoughts?
>
>My immediate thought is, "What problem is this trying to solve?"

Automating NS changes on the parent side, via child-signed-and-signalled
in-zone data. If the CDS keys are needed for a change of DNS provider,
it implies a new NS set on the parent (as well as the apex of the child).

E.g. if someone needs to move a bunch of domains from one set of name
servers
to a different set, tools are likely better than doing it manually. CDS
addresses the DS/DNSKEY part, but leaves the NS part unchanged.


It's a problem which I presume exists or might exist, which goes along
with the CDS problem: how do you automate "X", where "X" is currently
done via web form? ("Automate" might merely be "integrate into a
provisioning
system").

I don't know if the problem actually exists, so until someone says,
"Yeah, it is a problem", it is probably premature.

It would really only make sense (or add value) if the domains were
already DNSSEC delegations, and already doing CDS.

If the key roll is being prompted by NS changes, then tying (loosely or
tightly) the NS move with the CDS change, then the process reduces the
probability of resolution breaking for any of the bunch.

It would make sense basically only if the "PNS" RRset was signed, and
would provide cryptographic protection on it, allowing for an in-band
method of changing the NS on the parent side.

It's not necessary, merely a convenience, or a way of facilitating better
provisioning tools.

Brian


From florian@inet.tu-berlin.de  Tue Jul  9 18:20:02 2013
Return-Path: <florian@inet.tu-berlin.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CFD521F9BD8 for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 18:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TuwCyQDJhgPs for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 18:20:01 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id D31FE21F9BD4 for <dnsop@ietf.org>; Tue,  9 Jul 2013 18:20:00 -0700 (PDT)
Received: from fls-nb.lan.streibelt.net (91-64-122-25-dynip.superkabel.de [91.64.122.25]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 98E8A4C628C for <dnsop@ietf.org>; Wed, 10 Jul 2013 03:19:55 +0200 (CEST)
Date: Wed, 10 Jul 2013 03:19:54 +0200
From: Florian Streibelt <florian@inet.tu-berlin.de>
To: dnsop <dnsop@ietf.org>
Message-ID: <20130710031954.5ed55d0c@fls-nb.lan.streibelt.net>
In-Reply-To: <20130708124403.41ad8f53@fls-nb.lan.streibelt.net>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net> <20130708093714.GA21377@nic.fr> <20130708115143.05b3b834@fls-nb.lan.streibelt.net> <20130708095510.GA29226@nic.fr> <CAB3ZD+=hqrK_Yx+6RDb21jv78+4-5kMqb_4e2aPpm+fVwEc7EA@mail.gmail.com> <20130708124403.41ad8f53@fls-nb.lan.streibelt.net>
Organization: FG INET, T-Labs
X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.18; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Jul 2013 01:20:02 -0000

On Mon, 8 Jul 2013 12:44:03 +0200
 Florian Streibelt <florian@inet.tu-berlin.de> wrote:

> On Mon, 8 Jul 2013 18:15:20 +0800
>  ice jew <jewforice@gmail.com> wrote:

> > 2,Is there any open source solution of recursive resolver that supports ECS?
> 
> I am not aware of any - [...]

It seems I was not right, from the PowerDNS Release notes at http://doc.powerdns.com/html/changelog.html#changelog-auth-3-2 in the paragraph "3.10. PowerDNS Authoritative Server 3.0" it reads:

"Add support for EDNS option 'edns-subnet', based on draft-vandergaast-edns-client-subnet (commit 2226, commit 2228, commit 2229, commit 2230, commit 2231, commit 2233)."

From jewforice@gmail.com  Tue Jul  9 20:02:22 2013
Return-Path: <jewforice@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A39F221F9AFD for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 20:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id evp1+d70Bdmn for <dnsop@ietfa.amsl.com>; Tue,  9 Jul 2013 20:02:21 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id BEE5421F9B08 for <dnsop@ietf.org>; Tue,  9 Jul 2013 20:02:19 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id fo12so5242406lab.25 for <dnsop@ietf.org>; Tue, 09 Jul 2013 20:02:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8UxWXIIjrHjL09L72NCY5RF0MbJ53kR2RyLZ9aRZ+wI=; b=Q6YxTr50VzTnr/IRZJUWgdnzBk79bPx4jgmAK0p1JF0oeFetY8bLpqtRCsVnPtU5ac fMAgiPRKmyt+sHTu1A5OvbN9OvkTBMsr+wuQOBV20to1HHJd6S3AhvAWqhlvy5wcT7h4 oKwtACtceq6sNjsU7JG9UQyC1cSvfIO14PKEs0/x0a2DJTKWtJYtIUD1XAyJEoZOaFRv tcZwHpxzAiNxTvgA6TZAw4WmgPjvavDHFjA4DR1On36i7vgpZy4zgF+aWb3JexvF9l8y isX2xlTl3mVYunDgopkVW6WL9AlFb4hOJq8aQC/iJ+RBbS+wYw1Vwlc2YdNtXBEJfdFK o3ng==
MIME-Version: 1.0
X-Received: by 10.152.44.133 with SMTP id e5mr14317127lam.15.1373425338584; Tue, 09 Jul 2013 20:02:18 -0700 (PDT)
Received: by 10.114.174.200 with HTTP; Tue, 9 Jul 2013 20:02:18 -0700 (PDT)
Received: by 10.114.174.200 with HTTP; Tue, 9 Jul 2013 20:02:18 -0700 (PDT)
In-Reply-To: <20130710031954.5ed55d0c@fls-nb.lan.streibelt.net>
References: <20130708104015.2b8a3a0a@fls-nb.lan.streibelt.net> <20130708093714.GA21377@nic.fr> <20130708115143.05b3b834@fls-nb.lan.streibelt.net> <20130708095510.GA29226@nic.fr> <CAB3ZD+=hqrK_Yx+6RDb21jv78+4-5kMqb_4e2aPpm+fVwEc7EA@mail.gmail.com> <20130708124403.41ad8f53@fls-nb.lan.streibelt.net> <20130710031954.5ed55d0c@fls-nb.lan.streibelt.net>
Date: Wed, 10 Jul 2013 11:02:18 +0800
Message-ID: <CAB3ZD+m4wiX9DXLQeYBxpdNhgjx1=oXGSRVa_e=b2LLhU2iN=w@mail.gmail.com>
From: ice jew <jewforice@gmail.com>
To: Florian Streibelt <florian@inet.tu-berlin.de>
Content-Type: multipart/alternative; boundary=089e0160a4786e940104e11f81cd
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Jul 2013 03:02:22 -0000

--089e0160a4786e940104e11f81cd
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Well  this seems to be an authoritative version but not a recursive version=
.
=E5=9C=A8 2013-7-10 =E4=B8=8A=E5=8D=889:20=EF=BC=8C"Florian Streibelt" <flo=
rian@inet.tu-berlin.de>=E5=86=99=E9=81=93=EF=BC=9A

> On Mon, 8 Jul 2013 12:44:03 +0200
>  Florian Streibelt <florian@inet.tu-berlin.de> wrote:
>
> > On Mon, 8 Jul 2013 18:15:20 +0800
> >  ice jew <jewforice@gmail.com> wrote:
>
> > > 2,Is there any open source solution of recursive resolver that
> supports ECS?
> >
> > I am not aware of any - [...]
>
> It seems I was not right, from the PowerDNS Release notes at
> http://doc.powerdns.com/html/changelog.html#changelog-auth-3-2 in the
> paragraph "3.10. PowerDNS Authoritative Server 3.0" it reads:
>
> "Add support for EDNS option 'edns-subnet', based on
> draft-vandergaast-edns-client-subnet (commit 2226, commit 2228, commit
> 2229, commit 2230, commit 2231, commit 2233)."
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--089e0160a4786e940104e11f81cd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Well=C2=A0 this seems to be an authoritative version but not=
 a recursive version.</p>
<div class=3D"gmail_quote">=E5=9C=A8 2013-7-10 =E4=B8=8A=E5=8D=889:20=EF=BC=
=8C&quot;Florian Streibelt&quot; &lt;<a href=3D"mailto:florian@inet.tu-berl=
in.de">florian@inet.tu-berlin.de</a>&gt;=E5=86=99=E9=81=93=EF=BC=9A<br type=
=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, 8 Jul 2013 12:44:03 +0200<br>
=C2=A0Florian Streibelt &lt;<a href=3D"mailto:florian@inet.tu-berlin.de">fl=
orian@inet.tu-berlin.de</a>&gt; wrote:<br>
<br>
&gt; On Mon, 8 Jul 2013 18:15:20 +0800<br>
&gt; =C2=A0ice jew &lt;<a href=3D"mailto:jewforice@gmail.com">jewforice@gma=
il.com</a>&gt; wrote:<br>
<br>
&gt; &gt; 2,Is there any open source solution of recursive resolver that su=
pports ECS?<br>
&gt;<br>
&gt; I am not aware of any - [...]<br>
<br>
It seems I was not right, from the PowerDNS Release notes at <a href=3D"htt=
p://doc.powerdns.com/html/changelog.html#changelog-auth-3-2" target=3D"_bla=
nk">http://doc.powerdns.com/html/changelog.html#changelog-auth-3-2</a> in t=
he paragraph &quot;3.10. PowerDNS Authoritative Server 3.0&quot; it reads:<=
br>

<br>
&quot;Add support for EDNS option &#39;edns-subnet&#39;, based on draft-van=
dergaast-edns-client-subnet (commit 2226, commit 2228, commit 2229, commit =
2230, commit 2231, commit 2233).&quot;<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>

--089e0160a4786e940104e11f81cd--

From ed.lewis@neustar.biz  Wed Jul 10 06:19:21 2013
Return-Path: <ed.lewis@neustar.biz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9F9211E8197 for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2013 06:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.868
X-Spam-Level: 
X-Spam-Status: No, score=-101.868 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mnNjuR-6XOZ5 for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2013 06:19:16 -0700 (PDT)
Received: from smtp125.dfw.emailsrvr.com (smtp125.dfw.emailsrvr.com [67.192.241.125]) by ietfa.amsl.com (Postfix) with ESMTP id A335411E8180 for <dnsop@ietf.org>; Wed, 10 Jul 2013 06:19:16 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 519597819F; Wed, 10 Jul 2013 09:19:15 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp2.relay.dfw1a.emailsrvr.com (Authenticated sender: edlewis-AT-ogud.com) with ESMTPSA id D96FA7819A;  Wed, 10 Jul 2013 09:19:14 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_EFABB397-4B8E-4B1E-B09C-DEC00431B68E"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <51DBBFBD.5020300@sidn.nl>
Date: Wed, 10 Jul 2013 09:19:17 -0400
Message-Id: <84BD536A-9096-47C7-AE3B-1AEE7A8D0393@neustar.biz>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com> <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se> <51DBBFBD.5020300@sidn.nl>
To: Antoin Verschuren <Antoin.Verschuren@sidn.nl>
X-Mailer: Apple Mail (2.1283)
Cc: dnsop@ietf.org, Edward Lewis <ed.lewis@neustar.biz>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Jul 2013 13:19:22 -0000

--Apple-Mail=_EFABB397-4B8E-4B1E-B09C-DEC00431B68E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Jul 9, 2013, at 3:46, Antoin Verschuren wrote:

> I know you all wish the world was simpler, but it isn't, We've tried.


I'd voiced support for CDS before and have even gone as far as visiting =
with Olafur and Warren to work on the mechanism.

But since the last conversation, I'm not as optimistic.  In part because =
of what Antoin wrote above.

I wish that we could have something done only in-band but I also think =
it will be impossible to achieve this.

The CDS proposal is fine for answering the question of how data is =
marshalled, but it doesn't answer other factors.  I haven't been able to =
draw a circle around the other factors - is what we are trying to =
achieve a "transaction" or a version of a "remote procedure call" or =
something else.

That the child has no information about the parent - in the sense that =
some parents have cutpoints deeper than 1 and that the child zone has no =
information about the parent name servers, knowing where how to locate =
the service is difficult.  (I'm leaving out the possibility of using a =
recursive server to discover the parent because that's a function that =
you really don't want in a key management system or an authoritative =
server.

There is also no "semaphore" system in place that will inform the parent =
and child what state of the DS transfer is in.  The draft assumes a poll =
cycle on the parent and detection by the client - but what if there's a =
race condition?  Or one side gets stuck in a state (of the protocol =
state machine) and leaves the other side spinning?

These are concerns that are not well defined and I've off and on tried =
to find a more rigorous framework from which to hang them.  But Antoin =
sums up the "operator" view that - the world is more complicated than a =
simple solution away from completeness.

I said "I'm not as optimistic."  This doesn't mean I'm pessimistic nor =
withdrawing support for working on this in the working group.  There's a =
need to make DS management easier but a simple solution is no longer =
what I envision.

=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_EFABB397-4B8E-4B1E-B09C-DEC00431B68E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jul 9, 2013, at 3:46, Antoin Verschuren =
wrote:</div><br><blockquote type=3D"cite"><div>I know you all wish the =
world was simpler, but it isn't, We've =
tried.<br></div></blockquote></div><div><br></div>I'd voiced support for =
CDS before and have even gone as far as visiting with Olafur and Warren =
to work on the mechanism.<div><br></div><div>But since the last =
conversation, I'm not as optimistic. &nbsp;In part because of what =
Antoin wrote above.</div><div><br></div><div>I wish that we could have =
something done only in-band but I also think it will be impossible to =
achieve this.</div><div><br></div><div>The CDS proposal is fine for =
answering the question of how data is marshalled, but it doesn't answer =
other factors. &nbsp;I haven't been able to draw a circle around the =
other factors - is what we are trying to achieve a "transaction" or a =
version of a "remote procedure call" or something =
else.</div><div><br></div><div>That the child has no information about =
the parent - in the sense that some parents have cutpoints deeper than 1 =
and that the child zone has no information about the parent name =
servers, knowing where how to locate the service is difficult. =
&nbsp;(I'm leaving out the possibility of using a recursive server to =
discover the parent because that's a function that you really don't want =
in a key management system or an authoritative =
server.</div><div><br></div><div>There is also no "semaphore" system in =
place that will inform the parent and child what state of the DS =
transfer is in. &nbsp;The draft assumes a poll cycle on the parent and =
detection by the client - but what if there's a race condition? &nbsp;Or =
one side gets stuck in a state (of the protocol state machine) and =
leaves the other side spinning?</div><div><br></div><div>These are =
concerns that are not well defined and I've off and on tried to find a =
more rigorous framework from which to hang them. &nbsp;But Antoin sums =
up the "operator" view that - the world is more complicated than a =
simple solution away from completeness.</div><div><br></div><div>I said =
"I'm not as optimistic." &nbsp;This doesn't mean I'm pessimistic nor =
withdrawing support for working on this in the working group. =
&nbsp;There's a need to make DS management easier but a simple solution =
is no longer what I envision.</div><div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></div></body></html>=

--Apple-Mail=_EFABB397-4B8E-4B1E-B09C-DEC00431B68E--

From cathy.zhou@huawei.com  Wed Jul 10 19:16:27 2013
Return-Path: <cathy.zhou@huawei.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F07111E80A2 for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2013 19:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUvX4IitPgLE for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2013 19:16:17 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8220D11E80AE for <dnsop@ietf.org>; Wed, 10 Jul 2013 19:16:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATI15493; Thu, 11 Jul 2013 02:16:11 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 03:15:44 +0100
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 03:16:04 +0100
Received: from SZXEML513-MBS.china.huawei.com ([169.254.8.100]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.007; Thu, 11 Jul 2013 10:16:02 +0800
From: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: draft-deng-pcp-ddns
Thread-Index: Ac593Ja5kBOo4xlESe2gNxbXfMzzJQ==
Date: Thu, 11 Jul 2013 02:16:01 +0000
Message-ID: <A6A061BEE5DDC94A9692D9D81AF776DF3263198F@szxeml513-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.76.105]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "draft-deng-pcp-ddns@tools.ietf.org" <draft-deng-pcp-ddns@tools.ietf.org>
Subject: [DNSOP] draft-deng-pcp-ddns
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Jul 2013 02:16:27 -0000

Dear all,=20
We submitted a document to PCP working group on how to use PCP to update dy=
namic DNS before: http://tools.ietf.org/id/draft-deng-pcp-ddns-02.txt.
This document focuses on the problems encountered when using dynamic DNS in=
 address sharing contexts (e.g., DS-Lite, NAT64, A+P). This document requir=
es no changes to PCP protocol or dynamic updates in the standard domain nam=
e system [RFC2136], but is rather an operational document to make the curre=
nt DDNS service providers be aware of the impacts and issues that the IPv6 =
transitioning and IPv4 address sharing will bring to them, and gives soluti=
ons and implementation examples to address the forthcoming issues.

After presentation in PCP, the feedback is that " This is important work, b=
ut not PCP-specific" and the PCP chair suggested we socialize this in dnsop=
.
So we'd like to share this document here for your valuable comments.
To dnsop chairs: can we ask for a 10 minutes slot to present this document =
in IETF 87 meeting?

Thanks,
Cathy



From paul@nohats.ca  Wed Jul 10 19:47:03 2013
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C91A21F9B53 for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2013 19:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9kRSLPatHiX for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2013 19:46:57 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8565421F9B45 for <dnsop@ietf.org>; Wed, 10 Jul 2013 19:46:56 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3brM9S4BPYz73H; Wed, 10 Jul 2013 22:46:52 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id G75Wf7vJzlRB; Wed, 10 Jul 2013 22:46:51 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Wed, 10 Jul 2013 22:46:51 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 37AFC817A5; Wed, 10 Jul 2013 22:46:51 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 281428179E; Wed, 10 Jul 2013 22:46:51 -0400 (EDT)
Date: Wed, 10 Jul 2013 22:46:51 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <84BD536A-9096-47C7-AE3B-1AEE7A8D0393@neustar.biz>
Message-ID: <alpine.LFD.2.10.1307102243040.14276@bofh.nohats.ca>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com> <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se> <51DBBFBD.5020300@sidn.nl> <84BD536A-9096-47C7-AE3B-1AEE7A8D0393@neustar.biz>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Jul 2013 02:47:03 -0000

On Wed, 10 Jul 2013, Edward Lewis wrote:

> These are concerns that are not well defined and I've off and on tried to find a more rigorous framework from which to hang them.  But Antoin sums up the "operator"
> view that - the world is more complicated than a simple solution away from completeness.
> 
> I said "I'm not as optimistic."  This doesn't mean I'm pessimistic nor withdrawing support for working on this in the working group.  There's a need to make DS
> management easier but a simple solution is no longer what I envision.

Then maybe we should split it in draft-kumari-ogud-dnsop-cds-no-rrr and draft-kumari-ogud-dnsop-cds-secure-kitchensink-2015

Paul

From paul@nohats.ca  Wed Jul 10 19:49:46 2013
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC7D721F9B45 for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2013 19:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J66usZ8pNnKA for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2013 19:49:41 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id F2AF011E8107 for <dnsop@ietf.org>; Wed, 10 Jul 2013 19:49:40 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3brMDd4yVsz73H; Wed, 10 Jul 2013 22:49:37 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id rwgs127W9ymJ; Wed, 10 Jul 2013 22:49:37 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Wed, 10 Jul 2013 22:49:37 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id E5B1E817A5; Wed, 10 Jul 2013 22:49:37 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id D30B18179E; Wed, 10 Jul 2013 22:49:37 -0400 (EDT)
Date: Wed, 10 Jul 2013 22:49:37 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: "Dickson, Brian" <bdickson@verisign.com>
In-Reply-To: <CE020CA5.B81E%bdickson@verisign.com>
Message-ID: <alpine.LFD.2.10.1307102248510.14276@bofh.nohats.ca>
References: <CE020CA5.B81E%bdickson@verisign.com>
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@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Jul 2013 02:49:47 -0000

On Tue, 9 Jul 2013, Dickson, Brian wrote:

> to a different set, tools are likely better than doing it manually. CDS
> addresses the DS/DNSKEY part, but leaves the NS part unchanged.
>
> It's a problem which I presume exists or might exist, which goes along
> with the CDS problem: how do you automate "X", where "X" is currently
> done via web form? ("Automate" might merely be "integrate into a
> provisioning
> system").
>
> I don't know if the problem actually exists, so until someone says,
> "Yeah, it is a problem", it is probably premature.

You mean all the lame delegations in the world doesn't show an actual
problem? I'm not sure I'm understanding you.

Paul

From Antoin.Verschuren@sidn.nl  Thu Jul 11 03:55:05 2013
Return-Path: <Antoin.Verschuren@sidn.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7F521F9F6A for <dnsop@ietfa.amsl.com>; Thu, 11 Jul 2013 03:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.718
X-Spam-Level: 
X-Spam-Status: No, score=-0.718 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Of1mpwGpDi0g for <dnsop@ietfa.amsl.com>; Thu, 11 Jul 2013 03:55:00 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 8D24321F9F65 for <dnsop@ietf.org>; Thu, 11 Jul 2013 03:55:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=qACJ6GJpV0tP4SYTa4O+nNClYpOz2Am0iEhusfLsbek=; b=DUkPoBUoA26BrEbU9AodOdzL8cQwnhlufkv0q2Fnixmdl0Kxxw8xm9qlbNQrK+EH2SIy7vT6pcgWjIvffg45+tYYWnEhhvjMQE8pENWtcKJ1VrzMon5NzxBBo35fJlaX2KrnyxJwlwFRC+umQ4Qia3K59QGNOqzM5QZ0Wz5fMnI=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r6BAswgN022104-r6BAswgP022104 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Thu, 11 Jul 2013 12:54:58 +0200
Received: from KAHUBCAS1.SIDN.local (192.168.2.41) by kahubcasn02.SIDN.local (192.168.2.74) with Microsoft SMTP Server (TLS) id 14.2.328.9; Thu, 11 Jul 2013 12:54:58 +0200
Received: from [94.198.152.214] (94.198.152.214) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.2.328.9; Thu, 11 Jul 2013 12:54:58 +0200
Message-ID: <51DE8F01.7080600@sidn.nl>
Date: Thu, 11 Jul 2013 12:54:57 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Edward Lewis <ed.lewis@neustar.biz>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com> <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se> <51DBBFBD.5020300@sidn.nl> <84BD536A-9096-47C7-AE3B-1AEE7A8D0393@neustar.biz>
In-Reply-To: <84BD536A-9096-47C7-AE3B-1AEE7A8D0393@neustar.biz>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Jul 2013 10:55:05 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 10-07-13 15:19, Edward Lewis schreef:

> These are concerns that are not well defined and I've off and on
> tried to find a more rigorous framework from which to hang them.
> But Antoin sums up the "operator" view that - the world is more
> complicated than a simple solution away from completeness.

I've given Ed's words a really good thought, and slept a night over it.
I think the reason why some of us don't feel comfortable  with many of
the assumptions in our requirements is because we try to avoid a
framework we as technicians are not comfortable with, and that is trust.
Trust is more a layer's thing. As sysadmins we expect trust is
evident, and we all try to do "the good thing" so why would anyone
doubt us at some point. We don't realize trust is something that needs
to be gained by convincing somebody else to express it, it cannot be
self-proclaimed.

In the CDS discussion, we have already identified some situations
where even for us it is evident CDS does not work, and I'm trying to
translate that to a more generic definition in stead of "a gut feeling".
We've said that CDS, or CSYNC to be more generic, is not useful for
bootstrapping a delegation, i.e. registering a delegation for the
first time. It also does not work when the delegation path is broken,
f.e. when a key is compromised. And the most recent case is when one
of the roles in the process of maintaining a delegation changes. These
are all situations where initial trust needs to be build-up,
re-established, or re-initialized. CSYNC and CDS try to solve a
problem for a static operational state where technical information
needs to travel from child to parent to maintain that relationship.
And in that static state, it can work fine, and as Ed, I'm all for it.

So defining where CSYNC cannot work because of a lack of trust is the
first thing we need to do, and I'll give it a try:

1. Bootstrapping
The initial appointment of trusted roles in a delegation must be set
up over an out-of-bound channel, and therefor CSYNC cannot be used for
bootstrapping the initial delegation. So registration of the initial
technical parameters of a delegation must take place over an
out-of-bound secure channel. In simple words: Registering a domain for
the first time is done over EPP, not over DNS.
2. Re-bootstrapping
When one of the roles in the out-of-bound channel is changed, a
renewed trust must be expressed. The roles we know of that are present
in the out-of-bound channel are:
Registry-Registrar-Reseller-Registrant-DNS operator-key maintainer.
When one of these roles is changed to another entity, the delegation
needs to be re-bootstrapped over the out-of-bound channel for everyone
in that out-of-bound channel to be aware of it's new trust
relationship. In simple words: Changing a Registrar, Registrant,
Reseller, DNS-operator, or DNSSEC key maintainer for a zone cannot be
communicated over DNS, but it must use EPP.
3. Re-initialising a bootstrap
When a (secure) delegation fails, because of a lame delegation, key
compromise, or misconfiguration of any other technical parameter
causing the delegation to break or trust to be absent, restoration of
that trust needs to be established over the out-of-band channel. In
simple words: Emergency keyrollovers in case of key compromise, or
restoration of lame delegations cannot use DNS but must be done over EPP.

So CDS and CSYNC only have a use case for the maintenance of a static
delegation, and I really think this is not a waisted effort. I
personally would like to solve the more generic question of a
technical parameter to travel from child to parent as in the CSYNC
draft, as opposed to the only one use case one scenario of getting a
DS renewed at the parent as focused on in the CDS draft.

> That the child has no information about the parent

I don't have an answer for Ed's question about how to identify the
entry point at the parent for a child.
I really liked the concept of a "parental agent" in the CDS draft, but
that is a role definition in the administrative out-of-bound channel.
I really think we need to separate roles in the administrative and
technical model for a delegation for our concepts to work.
So "parental agent" is an excellent term to describe who is above you
in the administrative out-of-bound channel, but it does not have any
synonym or responsibility in the technical DNS model.
I know we invented this because it's hard to change the ICANN lawyers
minds that registrars are responsible for administration and
bootstrapping technical parameters for a delegation only. Perhaps when
we add the list above to the responsibility of registrars, and clearly
define that CSYNC or CDS is for technical maintenance of a static
delegation, we can convince them that it is ok for a (DNS) child to
talk directly to the (DNS) parent, and then identification of a parent
can fairly easy be done in the DNS.

Thoughts, additions?

- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  M: +31 6 23368970
Mailto: antoin.verschuren@sidn.nl
XMPP: antoin.verschuren@jabber.sidn.nl
HTTP://www.sidn.nl/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJR3o79AAoJEDqHrM883AgnAlkH/2f3LWHVziH0F6epKc35MTY1
H8hsolkp0Y859JmnuQ5m6koy+YKV20DzCtSjZsBMCafkiBfXeIMeW7o33XWurHKG
pPku6iP5rf3BZCAi9kZ25z+jmThnU0+r2fVZKTyh5jpTnzI65HtKTknqGOyAlPC7
sTeqAXAn5Vb4RrxIUyCl9w4BkalRp7LbN7m5L81B3EdfGDm9L6myLkPi/pkbFG7P
k7fJK9+Kl9yCUsQdfaFSvE+cuNtRASSoAKhDvYRIOB726ylF5u5xNP89ROr8XyC8
rgniyyiL4KUjQ7jABdmppGw4aMbKJRRA5yfIGt6MEWCpgGv3rK6DODWi402zeNY=
=fxKD
-----END PGP SIGNATURE-----

From paul.hoffman@vpnc.org  Thu Jul 11 07:29:01 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3179A11E817A for <dnsop@ietfa.amsl.com>; Thu, 11 Jul 2013 07:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id inmNzSZ9eE7r for <dnsop@ietfa.amsl.com>; Thu, 11 Jul 2013 07:29:00 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id AF50711E816E for <dnsop@ietf.org>; Thu, 11 Jul 2013 07:29:00 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r6BESwgc092568 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Jul 2013 07:28:59 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51DE8F01.7080600@sidn.nl>
Date: Thu, 11 Jul 2013 07:28:59 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <866AF25D-1439-4EA2-AD92-ED53F8A6FB66@vpnc.org>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com> <33496ED6-4D88-485B-8369-566B2A1FC7C0@frobbit.se> <51DBBFBD.5020300@sidn.nl> <84BD536A-9096-47C7-AE3B-1AEE7A8D0393@neustar.biz> <51DE8F01.7080600@sidn.nl>
To: Antoin Verschuren <Antoin.Verschuren@sidn.nl>
X-Mailer: Apple Mail (2.1508)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Jul 2013 14:29:01 -0000

On Jul 11, 2013, at 3:54 AM, Antoin Verschuren =
<Antoin.Verschuren@sidn.nl> wrote:

> I've given Ed's words a really good thought, and slept a night over =
it.
> I think the reason why some of us don't feel comfortable  with many of
> the assumptions in our requirements is because we try to avoid a
> framework we as technicians are not comfortable with, and that is =
trust.
> Trust is more a layer's thing. As sysadmins we expect trust is
> evident, and we all try to do "the good thing" so why would anyone
> doubt us at some point. We don't realize trust is something that needs
> to be gained by convincing somebody else to express it, it cannot be
> self-proclaimed.

Quite right. But there is a second reason: the proposals are trying to =
use the DNS protocol to transmit the data and, seeing the limitations of =
doing so, adjust their requirements. A different way to design the =
protocol would be to list the real requirements and stick to them. This =
would very likely involve using a different communications protocol, =
such as RESTful-HTTP-over-TLS.=20

--Paul Hoffman=

From jad@sinodun.com  Thu Jul 11 08:35:08 2013
Return-Path: <jad@sinodun.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33BC921F9AC2 for <dnsop@ietfa.amsl.com>; Thu, 11 Jul 2013 08:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRTOtkeiDUGS for <dnsop@ietfa.amsl.com>; Thu, 11 Jul 2013 08:35:02 -0700 (PDT)
Received: from cpanelsmarthost1.zen.co.uk (cpanelsmarthost1.zen.co.uk [82.71.204.225]) by ietfa.amsl.com (Postfix) with ESMTP id 867D421F9DBA for <dnsop@ietf.org>; Thu, 11 Jul 2013 08:35:01 -0700 (PDT)
Received: from [88.98.24.67] (helo=shcp01.hosting.zen.net.uk) by cpanelsmarthost1.zen.co.uk with esmtp (Exim 4.72) (envelope-from <jad@sinodun.com>) id 1UxItY-0000ni-M9 for dnsop@ietf.org; Thu, 11 Jul 2013 15:35:00 +0000
Received: from 82-68-198-190.dsl.in-addr.zen.co.uk ([82.68.198.190]:29546 helo=[192.168.1.34]) by shcp01.hosting.zen.net.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <jad@sinodun.com>) id 1UxItQ-00026h-FS; Thu, 11 Jul 2013 16:34:52 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Dickinson <jad@sinodun.com>
In-Reply-To: <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com>
Date: Thu, 11 Jul 2013 15:34:53 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE353BD0-17FD-426B-BDFA-AAF647EFFA8E@sinodun.com>
References: <20130617165829.2638.88322.idtracker@ietfa.amsl.com> <DD7454F5-6B16-4EBA-A380-C51E2302E5E9@kumari.net> <alpine.LFD.2.10.1306171417150.18979@bofh.nohats.ca> <0lsj0b2kk5.fsf@wjh.hardakers.net> <51C96B62.9030401@nlnetlabs.nl> <2350A43B-088E-4BEA-9317-98B8372C74BE@ogud.com> <51D18336.5010401@nlnetlabs.nl> <9245734C-D614-41C4-B2FC-C39D6DAAA5C3@ogud.com> <8E20305A-4B51-4714-B339-0C5703E75828@sinodun.com> <A82661B1-414B-435C-B359-53BC0F17EEA3@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1508)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - shcp01.hosting.zen.net.uk
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - sinodun.com
X-Get-Message-Sender-Via: shcp01.hosting.zen.net.uk: authenticated_id: jad+sinodun.com/only user confirmed/virtual account not confirmed
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Jul 2013 15:35:08 -0000

On 8 Jul 2013, at 18:03, Olafur Gudmundsson <ogud@ogud.com> wrote:

> John,
>=20
> Thanks for a excellent and timely review we just about pushing out a =
new version when it arrived.=20
>=20
> We have accepted most of your edits and suggestions except when the =
text was already removed/reworded.=20
>=20
> Instead I want to focus on your Q1: "How will a ``Child'' know if the =
``Parent'' is doing CDS?"=20
> IMHO, we need to figure out how/if to place a flag in parent saying =
what kinds of "sync" it is willing to do from signed children.=20

I don't see the point of a flag. Since the auth servers for the child =
and parent never talk to each other the child would have to set up some =
tool to see the flag. It seems likely to me that the parent would have =
to give info about  such a flag on a web page somewhere so the web page =
might as well be the flag.

regards
John

---
jad@sinodun.com

http://sinodun.com

Sinodun Internet Technologies Ltd.
Stables 4, Suite 11,
Howbery Park,
Wallingford,
Oxfordshire,
OX10 8BA,
U.K.

+44 (0)1491 834957


From jim_lahey@outlook.com  Thu Jul 11 15:00:50 2013
Return-Path: <jim_lahey@outlook.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0A9921F85EE for <dnsop@ietfa.amsl.com>; Thu, 11 Jul 2013 15:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RpGnM++0WkE2 for <dnsop@ietfa.amsl.com>; Thu, 11 Jul 2013 15:00:41 -0700 (PDT)
Received: from blu0-omc4-s35.blu0.hotmail.com (blu0-omc4-s35.blu0.hotmail.com [65.55.111.174]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8F821F9FFC for <dnsop@ietf.org>; Thu, 11 Jul 2013 15:00:40 -0700 (PDT)
Received: from BLU178-W13 ([65.55.111.137]) by blu0-omc4-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 11 Jul 2013 15:00:39 -0700
X-TMN: [OSvHmhMqPy462ASB0SjZlPKVRetGVDeT]
X-Originating-Email: [jim_lahey@outlook.com]
Message-ID: <BLU178-W13F8614A0768F03E704778947B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_3925e715-9006-47ff-9772-7e5e579a6c35_"
From: Jim Lahey <jim_lahey@outlook.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Date: Thu, 11 Jul 2013 18:00:40 -0400
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 11 Jul 2013 22:00:39.0968 (UTC) FILETIME=[14C5D200:01CE7E82]
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Jul 2013 22:03:22 -0000

--_3925e715-9006-47ff-9772-7e5e579a6c35_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hello for the first time!

I'm a bit new to this IETF stuff=2C but a=0A=
 long time "participant" in the world of DNS.  I was pointed to this =0A=
list by a friend=2C and in reading some of the more recent threads I felt =
=0A=
compelled to jump in (I hope this sort of participation is copacetic).

On Tue=2C 9 Jul 2013=2C Dickson=2C Brian wrote:
>=20
> to a different set=2C tools are likely better than doing it manually. CDS
> addresses the DS/DNSKEY part=2C but leaves the NS part unchanged.
>=20
> It's a problem which I presume exists or might exist=2C which goes along
> with the CDS problem: how do you automate "X"=2C where "X" is currently
> done via web form? ("Automate" might merely be "integrate into a
> provisioning
> system").
>=20
> I don't know if the problem actually exists=2C so until someone says=2C
> "Yeah=2C it is a problem"=2C it is probably premature.
>=20
> You mean all the lame delegations in the world doesn't show an actual
> problem? I'm not sure I'm understanding you.

Why would this not be a problem?  I feel that Paul seems exactly right.  Lo=
sing synchronization between the NS set and the crypto RRs (DS/DNSKEYs) see=
ms like an alarming prospect (if I read Mr. Dickson's response right).  In =
other words=2C "Yeah=2C it is a problem."

jl
 		 	   		  =

--_3925e715-9006-47ff-9772-7e5e579a6c35_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'><br>Hello for the first time!<br=
><br>I'm a bit new to this IETF stuff=2C but a=0A=
 long time "participant" in the world of DNS.&nbsp=3B I was pointed to this=
 =0A=
list by a friend=2C and in reading some of the more recent threads I felt =
=0A=
compelled to jump in (I hope this sort of participation is copacetic).<br><=
br>On Tue=2C 9 Jul 2013=2C Dickson=2C Brian wrote:<br>&gt=3B <br>&gt=3B to =
a different set=2C tools are likely better than doing it manually. CDS<br>&=
gt=3B addresses the DS/DNSKEY part=2C but leaves the NS part unchanged.<br>=
&gt=3B <br>&gt=3B It's a problem which I presume exists or might exist=2C w=
hich goes along<br>&gt=3B with the CDS problem: how do you automate "X"=2C =
where "X" is currently<br>&gt=3B done via web form? ("Automate" might merel=
y be "integrate into a<br>&gt=3B provisioning<br>&gt=3B system").<br>&gt=3B=
 <br>&gt=3B I don't know if the problem actually exists=2C so until someone=
 says=2C<br>&gt=3B "Yeah=2C it is a problem"=2C it is probably premature.<b=
r>&gt=3B <br>&gt=3B You mean all the lame delegations in the world doesn't =
show an actual<br>&gt=3B problem? I'm not sure I'm understanding you.<br><b=
r>Why would this not be a problem?&nbsp=3B I feel that Paul seems exactly r=
ight.&nbsp=3B Losing synchronization between the NS set and the crypto RRs =
(DS/DNSKEYs) seems like an alarming prospect (if I read Mr. Dickson's respo=
nse right).&nbsp=3B In other words=2C "Yeah=2C it is a problem."<br><br>jl<=
br> 		 	   		  </div></body>
</html>=

--_3925e715-9006-47ff-9772-7e5e579a6c35_--

From fujiwara@jprs.co.jp  Fri Jul 12 00:06:56 2013
Return-Path: <fujiwara@jprs.co.jp>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7D511E8210 for <dnsop@ietfa.amsl.com>; Fri, 12 Jul 2013 00:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63Ziv9Akvu46 for <dnsop@ietfa.amsl.com>; Fri, 12 Jul 2013 00:06:56 -0700 (PDT)
Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) by ietfa.amsl.com (Postfix) with ESMTP id 0A7C311E8218 for <dnsop@ietf.org>; Fri, 12 Jul 2013 00:06:45 -0700 (PDT)
Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id r6C76h0v032719; Fri, 12 Jul 2013 16:06:43 +0900
X-AuditID: ac120820-b7f306d00000490a-5f-51dfab0322d9
Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 79.DE.18698.30BAFD15; Fri, 12 Jul 2013 16:06:43 +0900 (JST)
Date: Fri, 12 Jul 2013 16:06:43 +0900 (JST)
Message-Id: <20130712.160643.241430847.fujiwara@jprs.co.jp>
To: ed.lewis@neustar.biz
From: fujiwara@jprs.co.jp
In-Reply-To: <A948312D-9EA0-45EB-945F-FA9F57BD655B@neustar.biz>
References: <20130607.153740.02261936.fujiwara@jprs.co.jp> <A948312D-9EA0-45EB-945F-FA9F57BD655B@neustar.biz>
X-Mailer: Mew version 6.5 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrEIsWRmVeSWpSXmKPExsWyRoiFT5d59f1AgxdNghZ331xmsVh2Zgq7 A5PHkiU/mTx2NDxnDmCK4rJJSc3JLEst0rdL4MpoOXqOueA5X8Wf724NjPe5uxg5OCQETCTu X4rqYuQEMsUkLtxbz9bFyMUhJHCSUWLK4RPsIAkWAW2J43cesYDYvALWEjs7PjCB2CICEhJX b30DizMLCEncbjzKBmILCzhJTJn1mhHEZhOQlNj8uZUZxOYUsJe4vv4cK4gtJJAvMeHyYnaI xdYSh678ZAK5h1dAUOLvDmGIkVoSPTMes0PY8hLb385hnsDIPwuhahaSqllIqhYwMq9ilMlP S9MtTs1LKc5NNzDUK6nM18sqKCrWSwbRmxjBQcihsINxximDQ4wCHIxKPLzN5+8FCrEmlhVX 5h5ilORgUhLl3brifqAQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd6bZkA53pTEyqrUonyYlDQH i5I47/E/ZwKFBNITS1KzU1MLUotgsjIcHEoSvFtXAjUKFqWmp1akZeaUIKSZODhBhvMADV8I spi3uCAxtzgzHSJ/ilFSSpy3FqRZACSRUZoH1/uKURzoBWHe2SBZHmBCget6BTSQCWjgnpQ7 IANLEhFSUg2MMXOr3+hdaqp/bsFsuKW4T1DlwVebfTuW5nce5mRxD/+vOOdNv86lNRekm5WO JwubTHINdHn2Myt3d8zVAP+0fxcKFQ7ddvrFvSJR7/fZ/1b7397WUDqsN0k8r6rt8ifvhw1M vqJq8T1eUz1/7A+9PumGs7RMVsQHWbFOY2tWp7htG2Kvr9ZTYinOSDTUYi4qTgQA1BeKqOUC AAA=
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] draft-fujiwara-dnsop-ds-query-increase-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 12 Jul 2013 07:06:56 -0000

Thanks, Ed, and sorry too late response.

> From: Edward Lewis <ed.lewis@neustar.biz>
> Date: Fri, 7 Jun 2013 07:33:57 -0400
> 
> Yes, this is a problem.  But I don't like any of the discussed solutions.  I don't think that is surprising, I figure they are just ideas and unfortunately they all have bad side effects.

I agree. All solutions are not good.

> 4 -  Add a dummy DS won't work because that kills opt-out.  You can throw scaling to 100% out the window.
> 
> My thoughts, based on the DNS-OARC presentation, was that this can be better treated at the "client" side.
> 
> The trouble is we caved in and allowed recursive servers to use the NSEC{3} record to infer when they can send back an NXDOMAIN.  Instead of allowing a cache to only use the NSEC(3) proof for the (name,class,type) - which is what it should be for - we allow recursives to make use is the span in the NSEC{3) to say that nothing would be there so I'm not going to ask.
> 
> What I would suggest is restricting recursive servers to only using the proof for the name/class/type and in the case of the DS, in this rare case, boost the TTL used for the DS ncache'd answer to that of the NS set.  And I mean the remaining TTL of the NS set already in the cache (elsewhere).

It is different from DNS/DNSSEC protocol.
Authoritative side cannot control validator implementations.

> Listening to the talk, I quickly realized that we have no degrees of freedom on the authority side, this has to be solved on the caching side.  In the spirit of a quick response, the above is offered as a suggestion, it might have holes in it.

So, I happened to have thought dummy DS idea.

It is not good, but may solve this issue without changing DNS/DNSSEC
protocols and existing validators.

I will update the draft to add your suggestion.

Regards,

--
Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>

From warren@kumari.net  Fri Jul 12 05:19:42 2013
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76BC421E8053 for <dnsop@ietfa.amsl.com>; Fri, 12 Jul 2013 05:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhpRi00hInrC for <dnsop@ietfa.amsl.com>; Fri, 12 Jul 2013 05:19:37 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEA1221E804E for <dnsop@ietf.org>; Fri, 12 Jul 2013 05:19:37 -0700 (PDT)
Received: from [192.168.1.201] (unknown [196.38.31.134]) by vimes.kumari.net (Postfix) with ESMTPSA id D381B1B407D8; Fri, 12 Jul 2013 08:19:34 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <C3DDD5D2-D59E-4026-BF99-2820281788B6@frobbit.se>
Date: Fri, 12 Jul 2013 08:19:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <998B82B2-4CF1-471F-A791-96D6F6D9DE93@kumari.net>
References: <CE0080AE.B7C0%bdickson@verisign.com> <C3DDD5D2-D59E-4026-BF99-2820281788B6@frobbit.se>
To: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1508)
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, "Dickson, Brian" <bdickson@verisign.com>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 12 Jul 2013 12:19:42 -0000

On Jul 8, 2013, at 3:32 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:

>=20
> On 8 jul 2013, at 20:49, "Dickson, Brian" <bdickson@verisign.com> =
wrote:
>=20
>> However, maybe something like a "PNS" (parent NS) in the child, where =
the
>> child is authoritative for the data, could signal {change | =
validation}
>> (depending on the RRR requirements), would do the trick?
>=20
> Might solve some events, but I do not think it solves the most =
important situation, that DNS is moved from one DNS provider to another. =
The old DNS provider can not be asked to enter NS records for the =
gaining provider... And using NS (in reality, as you look for auth =
servers) to fetch NS data seems to me be a bit...fishy... ;-) The attack =
vector against such a situation is very complicated.

And is *precisely* why this document / technique is not trying to =
"solve" it.

CDS is specifically only for rolling your DNSKEY. It is specifically NOT =
for:
establishing trust.
recovering from a key compromise.
changing operators.
changing your NS.
a duck.

It is designed to be easy to clean, simple and easy to implement. It is =
designed to solve the "common case" -- there are a whole slew of cases =
that it simply rules out of scope.

This is designed to be the answer to "I feel like I should roll my keys =
because XXX, but I'm simply too lazy / likely to screw it up with the =
current interface" -- where XXX is something related to age, some =
policy, etc, NOT because I wandered into the directory where I store =
keys and found a file called exploit.php=85

If I need to move DNS hosting folk, change my NS records, transfer my =
domain to another registrar,  revoke all keys, etc I'll go "old skool" =
and do the out of band / web dance.

We want to make this annoying (probably repetitive) bit easier, ocean =
boiling is left for later=85.

[ Please note: I'm currently sitting in a hotel in South Africa, with =
less than stellar Internet access, and a funny timezone. Replies may be =
terse and delayed. ]

W


>=20
>   Patrik
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>=20

--
"Let's just say that if complete and utter chaos was lightning, he'd be =
the sort to stand on a hilltop in a thunderstorm wearing wet copper =
armour and shouting 'All gods are bastards'."

    -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of =
Magic)



From tim.wicinski@teamaol.com  Fri Jul 12 05:27:28 2013
Return-Path: <tim.wicinski@teamaol.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 746D921F9C89 for <dnsop@ietfa.amsl.com>; Fri, 12 Jul 2013 05:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yYXTktBmKgGA for <dnsop@ietfa.amsl.com>; Fri, 12 Jul 2013 05:27:23 -0700 (PDT)
Received: from omr-m07.mx.aol.com (omr-m07.mx.aol.com [64.12.143.81]) by ietfa.amsl.com (Postfix) with ESMTP id 65BC521F9C88 for <dnsop@ietf.org>; Fri, 12 Jul 2013 05:27:23 -0700 (PDT)
Received: from aoldtcmei32.ad.aol.aoltw.net (aoldtcmei32.office.aol.com [10.180.121.111]) by omr-m07.mx.aol.com (Outbound Mail Relay) with ESMTP id 04F4970036476; Fri, 12 Jul 2013 08:27:22 -0400 (EDT)
Received: from still.local (172.17.8.193) by aoldtcmei32.ad.aol.aoltw.net (10.180.121.111) with Microsoft SMTP Server id 14.3.123.3; Fri, 12 Jul 2013 08:27:21 -0400
Message-ID: <51DFF628.7010608@teamaol.com>
Date: Fri, 12 Jul 2013 08:27:20 -0400
From: Tim Wicinski <tim.wicinski@teamaol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>, =?windows-1252?Q?Patrik_F=E4ltst?= =?windows-1252?Q?r=F6m?= <paf@frobbit.se>
References: <CE0080AE.B7C0%bdickson@verisign.com>	<C3DDD5D2-D59E-4026-BF99-2820281788B6@frobbit.se> <998B82B2-4CF1-471F-A791-96D6F6D9DE93@kumari.net>
In-Reply-To: <998B82B2-4CF1-471F-A791-96D6F6D9DE93@kumari.net>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.17.8.193]
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>, "Dickson, Brian" <bdickson@verisign.com>
Subject: Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 12 Jul 2013 12:27:28 -0000

On 7/12/13 8:19 AM, Warren Kumari wrote:
> On Jul 8, 2013, at 3:32 PM, Patrik Fältström <paf@frobbit.se> wrote:
>
>> On 8 jul 2013, at 20:49, "Dickson, Brian" <bdickson@verisign.com> wrote:
>>
>>> However, maybe something like a "PNS" (parent NS) in the child, where the
>>> child is authoritative for the data, could signal {change | validation}
>>> (depending on the RRR requirements), would do the trick?
>> Might solve some events, but I do not think it solves the most important situation, that DNS is moved from one DNS provider to another. The old DNS provider can not be asked to enter NS records for the gaining provider... And using NS (in reality, as you look for auth servers) to fetch NS data seems to me be a bit...fishy... ;-) The attack vector against such a situation is very complicated.
> And is *precisely* why this document / technique is not trying to "solve" it.

This is why this is a good idea to me.


From paul@cypherpunks.ca  Sat Jul 13 16:27:55 2013
Return-Path: <paul@cypherpunks.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7440D21F9CF5 for <dnsop@ietfa.amsl.com>; Sat, 13 Jul 2013 16:27:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QY+9h5R-n0-m for <dnsop@ietfa.amsl.com>; Sat, 13 Jul 2013 16:27:49 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB3521F9AF3 for <dnsop@ietf.org>; Sat, 13 Jul 2013 16:27:49 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3bt6cG4LW1z7D9; Sat, 13 Jul 2013 19:27:42 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id ZSwz5i4E-xaT; Sat, 13 Jul 2013 19:27:39 -0400 (EDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by mx.nohats.ca (Postfix) with ESMTP; Sat, 13 Jul 2013 19:27:39 -0400 (EDT)
Received: by bofh.nohats.ca (Postfix, from userid 500) id 6A880817D5; Sat, 13 Jul 2013 19:27:39 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 5B450817D2; Sat, 13 Jul 2013 19:27:39 -0400 (EDT)
Date: Sat, 13 Jul 2013 19:27:39 -0400 (EDT)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: Warren Kumari <warren@kumari.net>
In-Reply-To: <F47366EE-A6D0-4041-ADC0-8D7369D7E0C7@kumari.net>
Message-ID: <alpine.LFD.2.10.1307131922410.21352@bofh.nohats.ca>
References: <20130702014438.15013.qmail@joyce.lan> <51D26C01.1010508@nlnetlabs.nl> <F47366EE-A6D0-4041-ADC0-8D7369D7E0C7@kumari.net>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: dnsop <dnsop@ietf.org>, Matthijs Mekking <matthijs@nlnetlabs.nl>
Subject: Re: [DNSOP] New Version Notification for draft-wkumari-dnsop-hammer-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Jul 2013 23:27:55 -0000

On Wed, 3 Jul 2013, Warren Kumari wrote:

>> prefetch: <yes or no>
>>     If yes, message cache elements are prefetched before they expire
>>     to  keep  the  cache  up to date.  Default is no.  Turning it on
>>     gives about 10 percent more traffic and load on the machine, but
>>     popular items do not expire from the cache.
>
> Doh, sorry, I was not aware that Unbound did this. I'd like to recognize this in the draft, any idea who actually suggested it / added it to the code?

I'm pretty sure Wouter added the code, but I'm not sure who came up with
the idea. Probably multiple people. It's a feature you really need when
running DNS(SEC) on the stub or else you're continuously dealing with
waiting on DNS.

I believe the option was added to unbound 1.4.2 released around march 2010,
and the RHEL and Fedora packages enabled prefetching then as well. So
it's been there for over three years!

Paul

From wjhns1@hardakers.net  Sun Jul 14 07:34:40 2013
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 493C311E8124 for <dnsop@ietfa.amsl.com>; Sun, 14 Jul 2013 07:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0CN06vqJqSVN for <dnsop@ietfa.amsl.com>; Sun, 14 Jul 2013 07:34:33 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7DD21F9A2E for <dnsop@ietf.org>; Sun, 14 Jul 2013 07:34:33 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:9c81:3501:fc02:feb1]) by mail.hardakers.net (Postfix) with ESMTPSA id A05A9249BD; Sun, 14 Jul 2013 07:34:31 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Wouters <paul@cypherpunks.ca>
References: <0lzjutsxiw.fsf@wjh.hardakers.net> <alpine.LFD.2.10.1306181346230.30796@bofh.nohats.ca>
Date: Sun, 14 Jul 2013 07:34:31 -0700
In-Reply-To: <alpine.LFD.2.10.1306181346230.30796@bofh.nohats.ca> (Paul Wouters's message of "Tue, 18 Jun 2013 14:14:44 -0400 (EDT)")
Message-ID: <0l1u71b47c.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: dnsop <dnsop@ietf.org>, Wes Hardaker <wjhns1@hardakers.net>
Subject: Re: [DNSOP] request draft-hardaker-dnsop-csync be adopted as a WG item
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Jul 2013 14:34:40 -0000

Paul Wouters <paul@cypherpunks.ca> writes:

> Comments:

Sorry for the late response; working no too many drafts at once.

> 2.1.1.1 talks about the serial in the CSYNC record. Why did you prefer a
> "soft" link between that and the SOA serial, instead of a "hard" link?
> Or why is there is a need for a serial? Shouldn't it directly relate to
> the SOA serial? You seem to think one would need a "minimal SOA serial"
> to process the CSYNC record, but wouldn't the CSYNC record always be
> correctin the _current_ zonefile? I don't see how prepublishing a CSYNC
> with a current serial + 1 would be of any benefit.

Because I was envisioning tools that manage the CSYNC record
independently of the zone itself being managed.  EG, for zones that
update their SOA regularly (say hourly) for data additions and removal,
they don't need to be concerned with always making sure the CSYNC SOA is
updated too.  They can if they want, but using a > clause means the
site-specific data management tools don't need to be rewritten.  Only
the CSYNC tool and/or signing tools need to deal with that.
 
>    The following CSYNC RR shows an example entry for "example.com" that
>    indicates the NS, A and AAAA records should be processed for the zone
>    using a minimum SOA serial number of 66.
>
>    example.com. 3600 IN CSYNC 73 1 A NS AAAA
>
> Did you mean to write "66" in the RRDATA? Or did I misunderstand
> something? Since you later write 0x42, I think you mean 66 here.

Yep.  Thanks.

(huh; I had already fixed it in my text.  And here I didn't think I had
edited it since publication!)

> 2.2.1 talks about fetching the SOA, CSYNC, data and again SOA record. I
> think you need to state that you should also aboard if the CSYNC/SOA
> serial obtained is lower then a previously processed CSYNC/SOA action.

Good point; added and thanks.

> This will prevent flipflopping when one NS server is out of sync and
> presenting old data.

Note that there is a state-keeping choice on behalf of the parental
agent, though...  So choose a parental agent that advertises themselves
as keeping state.

> This section should also indicate processing MUST be aborted if there
> was no full path of trust from the parent to the child (ie. we need
> DNSSEC authenticated data)

Added that all data needs to be validated as "secure".

> 2.2.2.1.  The NS type
>
> It should note that parent policy might result in rejecting the proposed
> change at the child, for example if only 1 NS record would be left.

Added:

	<t>Parental agents MAY refuse to perform NS updates if the
	replacement records fail to meet NS record policies required
	by the parent zone (e.g. "every child zone must have at least
	2 NS records").</t>

> 2.2.2.4.  The DS type
>
> I kinda lost track here. It's pretty confusing. Also because the "DS
> type" would really need to query DNSKEY, as the child is not publishing
> DS records. (eg "Queries should be sent to the child zone for all the DS
> records" is wrong)

Actually, no it's right.  If you notice above that it says the child has
published DS records for their own zone below the cut point.  It's
functionally "CDS" without the "C" because there is an external bit
saying to look for real DS records in the child.  Obviously, these
records are never used during normal processing.

Although, that brings up a good point to people that were considering
wanting to use DS records in the child at the first place: if the
authoritative child zone server is also a recursive server for some
clients behind it (heavily discouraged, but still seen very commonly in
practice), there is no way for a validating stub resolver using the
recursive resolver to get the real DS records signed by the parent.  So
I don't think we can actually do what the draft states at this point.

(but then, I'm not sure that doing DS/DNSKEY bits is the right choice
when compared to CDS)

> In some sense, perhaps to facilitate parents that insist on creating
> the DS from DNSKEY, and parents that insist on getting a DS RRdata
> from child, to split the DS type here into CDS and DNSKEY type, where
> the latter means "create DS from DNSKEY". Although that would mean
> large parts of the CDS draft would not really be used, if the CSYNC
> scheduling part is used.

Well, the CSYNC draft does exactly that: splits the choice between two
bits so parents and children can get the job done using either DS or
DNSKEY.  You're right, however, that we could use the CSYNC DS bit to
indicate "do CDS" instead.  However, the existence of the CDS record
alone, since it's special, doesn't really require an external bit to
indicate "go forth and copy" like the other record types.  The existence
of the CDS record is the "go forth and copy" bit.

> 2.3.3. support at parent.
>
> If it is important that we know if the parent supoprts CSYNC and with
> what parameters, should be define a RRtype for that which the parent
> can publish? I'm hesitant to state in a protocol document that we need
> something and suggest adding a human/manual procedure for that, when it
> can be avoided.

Well, there is so much out-of-band startup that is required to register
a new zone anyway, I don't think that we're adding anything substantial
to that.  All registrars should have a policy and practice statement (if
not that, at least a reputation) that is seen when the child comes to
register a new zone.  I don't think it's possible to easily encode
policy into a record, so I'm somewhat against even trying.  It's a very
slippery slope, as there are many many other policy statements that need
publishing too.
-- 
Wes Hardaker
Parsons

From wjhns1@hardakers.net  Sun Jul 14 21:11:13 2013
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0E6121F8FAF for <dnsop@ietfa.amsl.com>; Sun, 14 Jul 2013 21:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XlLELCHm65ep for <dnsop@ietfa.amsl.com>; Sun, 14 Jul 2013 21:11:13 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3166C21F88FB for <dnsop@ietf.org>; Sun, 14 Jul 2013 21:11:13 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:9c81:3501:fc02:feb1]) by mail.hardakers.net (Postfix) with ESMTPSA id 17C9825804; Sun, 14 Jul 2013 21:11:08 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: dnsop@ietf.org
References: <20130714144229.26066.66395.idtracker@ietfa.amsl.com>
Date: Sun, 14 Jul 2013 21:11:09 -0700
In-Reply-To: <20130714144229.26066.66395.idtracker@ietfa.amsl.com> (internet-drafts@ietf.org's message of "Sun, 14 Jul 2013 07:42:29 -0700")
Message-ID: <0lsizg8ntu.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: Wes Hardaker <ietf@hardakers.net>
Subject: Re: [DNSOP] New Version Notification for draft-hardaker-dnsop-csync-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Jul 2013 04:11:13 -0000

internet-drafts@ietf.org writes:

> A new version of I-D, draft-hardaker-dnsop-csync-01.txt
> has been successfully submitted by Wes Hardaker and posted to the
> IETF repository.
>
> Filename:	 draft-hardaker-dnsop-csync
> Revision:	 01
> Title:		 Child To Parent Synchronization in DNS
> Creation date:	 2013-07-14
> Group:		 Individual Submission
> Number of pages: 13
> URL:             http://www.ietf.org/internet-drafts/draft-hardaker-dnsop-csync-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-hardaker-dnsop-csync
> Htmlized:        http://tools.ietf.org/html/draft-hardaker-dnsop-csync-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-hardaker-dnsop-csync-01
>
> Abstract:
>    This document specifies how a child zone in the DNS can publish a
>    record that can indicate that a parental agent may copy and process
>    certain records from the child zone.  The existence and change of the
>    record may be monitored by a parental agent to either assist in
>    transferring or automatically transfer data from the child to the
>    parent.
>
>
>
>
> The IETF Secretariat
>

-- 
Wes Hardaker
Parsons

From tim.wicinski@teamaol.com  Mon Jul 15 10:02:08 2013
Return-Path: <tim.wicinski@teamaol.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEEFF21F9A81 for <dnsop@ietfa.amsl.com>; Mon, 15 Jul 2013 10:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rzu1t9Gwvzhp for <dnsop@ietfa.amsl.com>; Mon, 15 Jul 2013 10:02:04 -0700 (PDT)
Received: from omr-d02.mx.aol.com (omr-d02.mx.aol.com [205.188.109.194]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA7811E81AD for <dnsop@ietf.org>; Mon, 15 Jul 2013 10:01:25 -0700 (PDT)
Received: from aoldtcmei32.ad.aol.aoltw.net (aoldtcmei32.office.aol.com [10.180.121.111]) by omr-d02.mx.aol.com (Outbound Mail Relay) with ESMTP id 393A1700C2E8E for <dnsop@ietf.org>; Mon, 15 Jul 2013 13:01:24 -0400 (EDT)
Received: from still.local (172.17.8.193) by aoldtcmei32.ad.aol.aoltw.net (10.180.121.111) with Microsoft SMTP Server id 14.3.123.3; Mon, 15 Jul 2013 13:01:24 -0400
Message-ID: <51E42AE3.3070504@teamaol.com>
Date: Mon, 15 Jul 2013 13:01:23 -0400
From: Tim Wicinski <tim.wicinski@teamaol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="------------040006060503020606030104"
X-Originating-IP: [172.17.8.193]
Subject: [DNSOP] Draft Agenda for IETF 87
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Jul 2013 17:02:08 -0000

--------------040006060503020606030104
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit


Hello,

I've put together a first draft of the Agenda for Berlin.  You can find 
it here:

     http://www.ietf.org/proceedings/87/agenda/agenda-87-dnsop


I'll include it below for those of us who can't focus long enough to 
click.  It seems that the first two items (AS112 and the CDS/CSYNC 
discussion) will be presented jointly.  The third item on DNS Cache 
Mechanisms are attempting to solve different problems.

If there is anything I've left out, or if someone wants to discuss 
something additional, let me know.

thanks
tim



-------

WG:         DNS Operations (dnsop)
Meeting:    IETF 87, Berlin
Location:   Intercontinental, Bellevue
Date:       Thursday, 1 August 2013
Time:       17:30 - 18:30 (UTC-04:00)
Chairs:     Peter Koch     <pk@denic.de>
             Tim Wicinski <tim.wicinski@teamaol.com>


0) Introduction

1) Administrivia

2) Status Updates

3) Open Items
    3.1) AS112 discussion  (20 minutes)
      <draft-wkumari-dnsop-omniscient-as112-03>
           Warren Kumari
      <draft-jabley-dnsop-as112-dname-00>
           Joe Abley
      Both will present their ideas, and the outcome will be a combined draft with the group's decision

    3.2) Automating DNSSEC Delegation  (20 minutes)
      <draft-kumari-ogud-dnsop-cds-03>
           Warrem Kumari
      <draft-hardaker-dnsop-csync-01>
           Wes Hardaker
      Joint presentation on CDS and CSYNC, with 'where do we go from here' direction.


    3.3) DNS Cache Updating Mechanisms  (15 minutes)
      <draft-jabley-dnsop-dns-flush-00>
           Joe Abley


      <draft-wkumari-dnsop-hammer-00>
           Warren Kumari

      These are attempting to solve two different problems, but there is a need to discuss these.

4) Issues evolving form other WGs' drafts (10 minutes)


5) AOB





--------------040006060503020606030104
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 bgcolor="#FFFFFF" text="#000000">
    <br>
    Hello,<br>
    <br>
    I've put together a first draft of the Agenda for Berlin.&nbsp; You can
    find it here:<br>
    <br>
    <tt>&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-freetext" href="http://www.ietf.org/proceedings/87/agenda/agenda-87-dnsop">http://www.ietf.org/proceedings/87/agenda/agenda-87-dnsop</a><br>
      <br>
      <br>
      I'll include it below for those of us who can't focus long enough
      to click.&nbsp; It seems that the first two items (AS112 and the
      CDS/CSYNC discussion) will be presented jointly.&nbsp; The third item
      on DNS Cache Mechanisms are attempting to solve different
      problems. <br>
      <br>
      If there is anything I've left out, or if someone wants to discuss
      something additional, let me know. <br>
      <br>
      thanks<br>
      tim<br>
      <br>
      <br>
      <br>
    </tt>-------<br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre>WG:         DNS Operations (dnsop)
Meeting:    IETF 87, Berlin
Location:   Intercontinental, Bellevue
Date:       Thursday, 1 August 2013
Time:       17:30 - 18:30 (UTC-04:00)
Chairs:     Peter Koch     <a class="moz-txt-link-rfc2396E" href="mailto:pk@denic.de">&lt;pk@denic.de&gt;</a>
            Tim Wicinski <a class="moz-txt-link-rfc2396E" href="mailto:tim.wicinski@teamaol.com">&lt;tim.wicinski@teamaol.com&gt;</a>


0) Introduction

1) Administrivia

2) Status Updates

3) Open Items
   3.1) AS112 discussion  (20 minutes)
     &lt;draft-wkumari-dnsop-omniscient-as112-03&gt;
          Warren Kumari
     &lt;draft-jabley-dnsop-as112-dname-00&gt;
          Joe Abley
     Both will present their ideas, and the outcome will be a combined draft with the group's decision

   3.2) Automating DNSSEC Delegation  (20 minutes)
     &lt;draft-kumari-ogud-dnsop-cds-03&gt;
          Warrem Kumari
     &lt;draft-hardaker-dnsop-csync-01&gt;
          Wes Hardaker
     Joint presentation on CDS and CSYNC, with 'where do we go from here' direction.


   3.3) DNS Cache Updating Mechanisms  (15 minutes)
     &lt;draft-jabley-dnsop-dns-flush-00&gt;
          Joe Abley


     &lt;draft-wkumari-dnsop-hammer-00&gt;
          Warren Kumari

     These are attempting to solve two different problems, but there is a need to discuss these.

4) Issues evolving form other WGs' drafts (10 minutes)


5) AOB




</pre>
  </body>
</html>

--------------040006060503020606030104--

From internet-drafts@ietf.org  Mon Jul 15 12:16:13 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEF3E21E8143; Mon, 15 Jul 2013 12:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+X5V9vtr1jt; Mon, 15 Jul 2013 12:16:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC50121E8146; Mon, 15 Jul 2013 12:16:11 -0700 (PDT)
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.51.p2
Message-ID: <20130715191611.8848.92319.idtracker@ietfa.amsl.com>
Date: Mon, 15 Jul 2013 12:16:11 -0700
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-resolver-priming-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Jul 2013 19:16:13 -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           : Initializing a DNS Resolver with Priming Queries
	Author(s)       : Peter Koch
                          Matt Larson
	Filename        : draft-ietf-dnsop-resolver-priming-03.txt
	Pages           : 8
	Date            : 2013-07-15

Abstract:
   This document describes the initial queries a DNS resolver is
   supposed to emit to initialize its cache with a current NS RRSet for
   the root zone as well as the necessary address information.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-priming

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dnsop-resolver-priming-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dnsop-resolver-priming-03


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


From peter@denic.de  Mon Jul 15 12:25:34 2013
Return-Path: <peter@denic.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB29B11E8220 for <dnsop@ietfa.amsl.com>; Mon, 15 Jul 2013 12:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZF8eMiU2lMl8 for <dnsop@ietfa.amsl.com>; Mon, 15 Jul 2013 12:25:34 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3242921E8157 for <dnsop@ietf.org>; Mon, 15 Jul 2013 12:25:19 -0700 (PDT)
Received: from x27.adm.denic.de (x28.fra2.if.denic.de [10.122.64.17]) by office.denic.de with esmtp   id 1UyoOc-0007To-0n; Mon, 15 Jul 2013 21:25:18 +0200
Received: from localhost by x27.adm.denic.de with local  id 1UyoOb-0000qe-TY; Mon, 15 Jul 2013 21:25:17 +0200
Date: Mon, 15 Jul 2013 21:25:17 +0200
From: Peter Koch <pk@DENIC.DE>
To: dnsop@ietf.org
Message-ID: <20130715192517.GE14489@x28.adm.denic.de>
References: <20130715191611.8848.92319.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130715191611.8848.92319.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-resolver-priming-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Jul 2013 19:25:34 -0000

On Mon, Jul 15, 2013 at 12:16:11PM -0700, internet-drafts@ietf.org wrote:

> 	Filename        : draft-ietf-dnsop-resolver-priming-03.txt

revived after a long time, incorporating changes from the latest WG
discussion.  Two issues still open, do not expect discussion time for
this in Berlin, feedback of course appreciated.

-Peter

From wjhns1@hardakers.net  Mon Jul 15 14:33:05 2013
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F5A11E8178 for <dnsop@ietfa.amsl.com>; Mon, 15 Jul 2013 14:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5EhdG8Tk+aM for <dnsop@ietfa.amsl.com>; Mon, 15 Jul 2013 14:32:57 -0700 (PDT)
Received: from mail.hardakers.net (unknown [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6D211E8130 for <dnsop@ietf.org>; Mon, 15 Jul 2013 14:32:45 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:9c81:3501:fc02:feb1]) by mail.hardakers.net (Postfix) with ESMTPSA id CEE9D22D4F for <dnsop@ietf.org>; Mon, 15 Jul 2013 14:32:41 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: dnsop@ietf.org
Date: Mon, 15 Jul 2013 14:32:41 -0700
Message-ID: <0lwqor1pc6.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Subject: [DNSOP] [internet-drafts@ietf.org] New Version Notification for draft-hardaker-dnsop-dnssec-roadblock-avoidance-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Jul 2013 21:33:05 -0000

--=-=-=
Content-Type: text/plain


We've written a draft that is intended to describe ways that a
validating host resolver can test a nearby resolver for use as a caching
resource if it is DNSSEC-aware.  The document describes tests that can
be done, as well as mitigation techniques that can be used in "less than
ideal situations" (*cough* hotels *cough*).

Our goal is to document how various test suites act, and how various
avoidance techniques are used in various libraries in order to document
existing practice and help future implementations.


--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <internet-drafts@ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dawn.hardakers.net
X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,
	SPF_PASS autolearn=ham version=3.3.2
X-Spam-Level: 
X-Spam-Flag: NO
X-Original-To: ietf@hardakers.net
Delivered-To: ietf@hardakers.net
Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:123a::1:1e])
	by mail.hardakers.net (Postfix) with ESMTP id 6ACF325F2F
	for <ietf@hardakers.net>; Mon, 15 Jul 2013 13:02:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id 00C4D11E823D;
	Mon, 15 Jul 2013 13:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([12.22.58.30])
	by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id S19r5kvU1T4I; Mon, 15 Jul 2013 13:02:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 5C4D421E815D;
	Mon, 15 Jul 2013 13:02:27 -0700 (PDT)
From: internet-drafts@ietf.org
To: Suresh Krishnaswamy <suresh@tislabs.com>, Wes Hardaker <ietf@hardakers.net>,
	Wesley Hardaker <ietf@hardakers.net>, Olafur Gudmundsson <ogud@ogud.com>
Subject: New Version Notification for
	draft-hardaker-dnsop-dnssec-roadblock-avoidance-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130715200227.2582.76256.idtracker@ietfa.amsl.com>
Date: Mon, 15 Jul 2013 13:02:27 -0700
MIME-Version: 1.0
Content-Type: text/plain


A new version of I-D, draft-hardaker-dnsop-dnssec-roadblock-avoidance-00.txt
has been successfully submitted by Wes Hardaker and posted to the
IETF repository.

Filename:	 draft-hardaker-dnsop-dnssec-roadblock-avoidance
Revision:	 00
Title:		 DNSSEC Roadblock Avoidance
Creation date:	 2013-07-15
Group:		 Individual Submission
Number of pages: 16
URL:             http://www.ietf.org/internet-drafts/draft-hardaker-dnsop-dnssec-roadblock-avoidance-00.txt
Status:          http://datatracker.ietf.org/doc/draft-hardaker-dnsop-dnssec-roadblock-avoidance
Htmlized:        http://tools.ietf.org/html/draft-hardaker-dnsop-dnssec-roadblock-avoidance-00


Abstract:
   This document describes problems that a DNSSEC aware resolver/
   application might run into to non-compliant infrastructure.  It poses
   potential detection and mitigation techniques.  The scope of the
   document is to create a shared approaches to detect and overcome
   network issues that a DNSSEC software/system may face.

                                                                                  


The IETF Secretariat


--=-=-=
Content-Type: text/plain



-- 
Wes Hardaker
Parsons

--=-=-=--

From peter@denic.de  Wed Jul 17 08:24:56 2013
Return-Path: <peter@denic.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A703521F9D1C for <dnsop@ietfa.amsl.com>; Wed, 17 Jul 2013 08:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pmmqSy49+TaC for <dnsop@ietfa.amsl.com>; Wed, 17 Jul 2013 08:24:55 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id F089D21F9CD7 for <dnsop@ietf.org>; Wed, 17 Jul 2013 08:24:52 -0700 (PDT)
Received: from x27.adm.denic.de (x28.fra2.if.denic.de [10.122.64.17]) by office.denic.de with esmtp   id 1UzTb1-0006yW-Ik; Wed, 17 Jul 2013 17:24:51 +0200
Received: from localhost by x27.adm.denic.de with local  id 1UzTb1-0000mF-FW; Wed, 17 Jul 2013 17:24:51 +0200
Date: Wed, 17 Jul 2013 17:24:51 +0200
From: Peter Koch <pk@DENIC.DE>
To: dnsop@ietf.org
Message-ID: <20130717152451.GG30100@x28.adm.denic.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: [DNSOP] Fwd: [[Geopriv] Last Call: <draft-ietf-geopriv-res-gw-lis-discovery-05.txt> (Location?Information Server (LIS) Discovery using IP address and Reverse?DNS) to Informational RFC]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jul 2013 15:24:56 -0000

I am sure the participants of this WG can contribute an informed opinion
to the last call.

-Peter

----- Forwarded message from The IESG <iesg-secretary@ietf.org> -----

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: geopriv@ietf.org
Subject: [Geopriv] Last Call:
	<draft-ietf-geopriv-res-gw-lis-discovery-05.txt>
	(Location	Information Server (LIS) Discovery using IP address
	and Reverse	DNS) to Informational RFC
Date: Wed, 17 Jul 2013 08:14:39 -0700

The IESG has received a request from the Geographic Location/Privacy WG
(geopriv) to consider the following document:
- 'Location Information Server (LIS) Discovery using IP address and
   Reverse DNS'
  <draft-ietf-geopriv-res-gw-lis-discovery-05.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-07-31. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The residential gateway is a device that has become an integral part
   of home networking equipment.  Discovering a Location Information
   Server (LIS) is a necessary part of acquiring location information
   for location-based services.  However, discovering a LIS when a
   residential gateway is present poses a configuration challenge,
   requiring a method that is able to work around the obstacle presented
   by the gateway.

   This document describes a solution to this problem.  The solution
   provides alternative domain names as input to the LIS discovery
   process based on the network addresses assigned to a Device.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-discovery/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-discovery/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv

----- End forwarded message -----

From jtatuya@infoblox.com  Wed Jul 24 19:03:31 2013
Return-Path: <jtatuya@infoblox.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA0221F9993 for <dnsop@ietfa.amsl.com>; Wed, 24 Jul 2013 19:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.744
X-Spam-Level: 
X-Spam-Status: No, score=-1.744 tagged_above=-999 required=5 tests=[AWL=0.555,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTURrBfj+4yg for <dnsop@ietfa.amsl.com>; Wed, 24 Jul 2013 19:03:25 -0700 (PDT)
Received: from mx2.infoblox.com (mx2.infoblox.com [205.234.19.214]) by ietfa.amsl.com (Postfix) with ESMTP id 86CBB21F848A for <dnsop@ietf.org>; Wed, 24 Jul 2013 19:03:25 -0700 (PDT)
X-ASG-Debug-ID: 1374717803-0640d710c9995b70001-lPZdTi
Received: from x2008hub1.infoblox.com (x2008hub1.infoblox.com [205.234.19.248]) by mx2.infoblox.com with ESMTP id EVVRgBMIm3JEk83v; Wed, 24 Jul 2013 19:03:23 -0700 (PDT)
X-Barracuda-Envelope-From: jtatuya@infoblox.com
X-Barracuda-Apparent-Source-IP: 205.234.19.248
Received: from jinmei-mbp.infoblox.com (10.102.29.200) by x2008hub1.infoblox.com (10.120.3.105) with Microsoft SMTP Server (TLS) id 14.2.298.4; Wed, 24 Jul 2013 19:03:23 -0700
Date: Wed, 24 Jul 2013 19:03:21 -0700
Message-ID: <m1r4enbdli.wl%jtatuya@infoblox.com>
From: JINMEI Tatuya / =?UTF-8?B?56We5piO6YGU5ZOJ?= <jtatuya@infoblox.com>
To: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca>
X-ASG-Orig-Subj: Re: [DNSOP] Fwd: New Version Notification for	draft-jabley-dnsop-dns-flush-00.txt
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com> <806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
X-Originating-IP: [10.102.29.200]
X-Barracuda-Connect: x2008hub1.infoblox.com[205.234.19.248]
X-Barracuda-Start-Time: 1374717803
X-Barracuda-URL: http://205.234.19.214:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at infoblox.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.137284 Rule breakdown below pts rule name              description ---- ---------------------- --------------------------------------------------
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for	draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Jul 2013 02:03:31 -0000

At Mon, 24 Jun 2013 15:32:45 -0400,
Joe Abley <jabley@hopcount.ca> wrote:

> I just exhumed the below-mentioned draft and recruited a co-author, since it seems like a timely topic for discussion.
> 
> This draft proposes a mechanism whereby an authority-server operator can signal to one or more recursive servers that the recursive server should flush a section of its cache. It's an in-band mechanism using TSIG-secured NOTIFY.

I have a few comments on the draft:

- A meta level comment: this proposal seems to me to be a protocol
  extension, and couldn't normally be handled in places like dnsop.
  I'm not an IETF procedure police, though, so if others think it's
  okay and should be able to convince the police (aka IESG), that's
  fine to me.

- despite the explicit terminology section, there is a mixture
  of "Authoritative" (server) and "Authority" (server).  "Resolver"
  (without the word "stub") and "Recursive Server" also seem to be
  mixed.

- the draft mentions UPDATE in several places, such as in Section 2:

   This document defines no new protocol elements and makes no changes
   to the existing specification for DNS UPDATE.  Rather, this document

  shouldn't these be NOTIFY?  If they are really UPDATE, I'm afraid
  the draft should explain more about how to use UPDATE...

- The use case described in Section 3.2 doesn't seem to be realistic
  (or I don't understand it correctly).  (Unlike the example of 3.1)
  it seems that the expected recursive servers are arbitrary ones, but
  that won't scale as the NOTIFY should be secured with TSIG.  If the
  intent is to do it for some limited set of recursive servers, I
  think the draft should explicitly say so, with what are such
  expected servers.

--
JINMEI, Tatuya
Infoblox Inc.

From jabley@hopcount.ca  Thu Jul 25 09:35:09 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70C1F21F862B for <dnsop@ietfa.amsl.com>; Thu, 25 Jul 2013 09:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N-4XOJhc8bzy for <dnsop@ietfa.amsl.com>; Thu, 25 Jul 2013 09:35:08 -0700 (PDT)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 02F2021F8617 for <dnsop@ietf.org>; Thu, 25 Jul 2013 09:35:06 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id a11so456933qen.10 for <dnsop@ietf.org>; Thu, 25 Jul 2013 09:35:06 -0700 (PDT)
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 :content-transfer-encoding:message-id:references:to:x-mailer; bh=fK/A6DN0EhMWi3vWOSCFjlfcmEYA+FPVuDjzaqsy5b4=; b=bW8i8FfBP6ysBwLUbmFWjmLFX+KJTG+OxfGj9fDs4x0icaWMsiElfbZ2wH+Ht0zBcF t/sOPBKfdP78wdOG11xUGwyxNNM0hxOD2mFdH9Qk3Ap/i5322Sry7ujAItTrj/qZpMVR RcD4+XBzZpzx3DFsd3U07nHW4IU75f1w+0R2g=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=fK/A6DN0EhMWi3vWOSCFjlfcmEYA+FPVuDjzaqsy5b4=; b=VyZ3ylH0+etbkUWCghfqDnkjjbqld7Vi2QQyHSc0G/HRu4vyDTOTjjkZcZkpUVWYr1 oBQbO3QH6fyoLdraEePRyI8L3436ojseY5ARrtOOgMAyoYyDmvqBQcC4dkI+B2qTveZG /QF1tOV8B20iVUVaqD8UPwBOV/DAUL2S0RChunmTid6AnFn1wJlgruEK+ymkUYuee7ee Bcv6DNAFgUq+9x4BpKmGzGDk1XbCcEZDP7tFuZUMZ5k5yLCcWSBd/OyDT7IRvrsSSY5P YIvTCv8cDOwsE4AZ16t3A4F6GCUwB1Ep3uguH/A9gKalMfFrazfEZ6tbP1cKDrg7AMo3 0NoQ==
X-Received: by 10.49.71.141 with SMTP id v13mr50604697qeu.36.1374770106332; Thu, 25 Jul 2013 09:35:06 -0700 (PDT)
Received: from dh26.r1.hopcount.ca (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id y4sm57875431qai.5.2013.07.25.09.35.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 25 Jul 2013 09:35:05 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <m1r4enbdli.wl%jtatuya@infoblox.com>
Date: Thu, 25 Jul 2013 12:35:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <432FC0E3-AA4F-4D5C-81FD-6CF0CD1361E5@hopcount.ca>
References: <20130624191629.32573.1412.idtracker@ietfa.amsl.com> <806E4545-E2AD-4A0D-B1D3-29C32989CA15@hopcount.ca> <m1r4enbdli.wl%jtatuya@infoblox.com>
To: =?utf-8?Q?JINMEI_Tatuya_/_=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89?= <jtatuya@infoblox.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQmc+IOJKZJUjVnSfJiMxieWF68MYrPOpB3zrFivSdAGYqO2q21DkjutRg3iow4jQCHKWhWx
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-jabley-dnsop-dns-flush-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Jul 2013 16:35:09 -0000

Hi Jinmei,

Many thanks for the review.

On 2013-07-24, at 22:03, JINMEI Tatuya / =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=
=89 <jtatuya@infoblox.com> wrote:

> At Mon, 24 Jun 2013 15:32:45 -0400,
> Joe Abley <jabley@hopcount.ca> wrote:
>=20
>> I just exhumed the below-mentioned draft and recruited a co-author, =
since it seems like a timely topic for discussion.
>>=20
>> This draft proposes a mechanism whereby an authority-server operator =
can signal to one or more recursive servers that the recursive server =
should flush a section of its cache. It's an in-band mechanism using =
TSIG-secured NOTIFY.
>=20
> I have a few comments on the draft:
>=20
> - A meta level comment: this proposal seems to me to be a protocol
>  extension, and couldn't normally be handled in places like dnsop.
>  I'm not an IETF procedure police, though, so if others think it's
>  okay and should be able to convince the police (aka IESG), that's
>  fine to me.

I agree this is a shaky line that we're walking.

> - despite the explicit terminology section, there is a mixture
>  of "Authoritative" (server) and "Authority" (server).  "Resolver"
>  (without the word "stub") and "Recursive Server" also seem to be
>  mixed.

I will fix that.

> - the draft mentions UPDATE in several places, such as in Section 2:
>=20
>   This document defines no new protocol elements and makes no changes
>   to the existing specification for DNS UPDATE.  Rather, this document
>=20
>  shouldn't these be NOTIFY?  If they are really UPDATE, I'm afraid
>  the draft should explain more about how to use UPDATE...

It should be NOTIFY. I must have been having a particularly weird day =
when I wrote that.

> - The use case described in Section 3.2 doesn't seem to be realistic
>  (or I don't understand it correctly).  (Unlike the example of 3.1)
>  it seems that the expected recursive servers are arbitrary ones, but
>  that won't scale as the NOTIFY should be secured with TSIG.  If the
>  intent is to do it for some limited set of recursive servers, I
>  think the draft should explicitly say so, with what are such
>  expected servers.

The observed phenomenon that I think is worth improving upon is that =
whereby every now and then the operator of some important zone (a TLD, a =
web property that is particularly important to end users, etc) has a bad =
problem, finds that they will not go into space today, and then spends =
two days sending increasingly desperate mail to operations lists asking =
people to flush their caches. This manual process is ad-hoc and =
unreliable.

The goal was to define a convention (mechanism, whatever) that would =
allow an authoritative server operator to make arrangements with =
particular recursive server operators to allow caches to be =
automatically flushed in the event that the authoritative server =
operator has such a bad problem.

The convention would also enable a mediation layer, where (for example) =
DNS Facilitators, Inc. could build relationships with recursive server =
operators and authoritative server operators and could funnel the =
authenticated directions to flush appropriately.

I will review the text again and see if I can make this clearer.


Joe=

From crawlder@gmail.com  Thu Jul 25 11:41:36 2013
Return-Path: <crawlder@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8EFB21F972C for <dnsop@ietfa.amsl.com>; Thu, 25 Jul 2013 11:41:36 -0700 (PDT)
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=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FSO2RomQnswK for <dnsop@ietfa.amsl.com>; Thu, 25 Jul 2013 11:41:36 -0700 (PDT)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id F178421F8F4F for <dnsop@ietf.org>; Thu, 25 Jul 2013 11:41:35 -0700 (PDT)
Received: by mail-ve0-f173.google.com with SMTP id jw11so688817veb.4 for <dnsop@ietf.org>; Thu, 25 Jul 2013 11:41:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=GuVaJyKOnLfiEZR0kW9/kLXcy/LVXXuro10PAIrvyvk=; b=Wdn2TvqQo4rD81Z5dbUzMD1X241NHKOGxM5hi0ZWfe8bDv31iN7QoK5GzUm15bKvl6 M1vOsgC1h1b/UJqCLZC4p/Dm57hmcBGwWW18ZHa/ZosEJZnpeDptSycDe6qoNP5s8aSS ScZ9Qkn563VFRh6SUyOfxICXjsbVejRVDuGh49MEzHY+zPftm0CgLQlQMvnCcgyypqfJ yApM+qKwRqbTrtY27vfjSOlV9nwF2yjdGV50O93NqyUZs/yXS6zubmfFx5kVji7DYdxK EONWItUb2HEQ+DaOKL54U7zOklt6LeSPmNqvffUWwJr5Eqxaw6ycn88+M0ZtQON5GUpp aTOg==
X-Received: by 10.220.167.2 with SMTP id o2mr1323024vcy.61.1374777695362; Thu, 25 Jul 2013 11:41:35 -0700 (PDT)
MIME-Version: 1.0
Sender: crawlder@gmail.com
Received: by 10.221.12.197 with HTTP; Thu, 25 Jul 2013 11:41:15 -0700 (PDT)
From: Matt Calder <calderm@usc.edu>
Date: Thu, 25 Jul 2013 11:41:15 -0700
X-Google-Sender-Auth: OMIaYWQbDKsJE6neXSQcuOTk2cw
Message-ID: <CAAQ8yQ9DbEzGiVYa3PiwdLo89UW3j5jEPdiOX9=uq+6z3dsKUQ@mail.gmail.com>
To: dnsop@ietf.org
Content-Type: multipart/alternative; boundary=089e011618ce2d94c304e25a6052
Subject: Re: [DNSOP] measurements using the EDNS-Client-Subnet extension
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Jul 2013 23:53:55 -0000

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

Apologies for not being able to post in the original thread.

A few weeks ago, Florian Streibelt posted his research paper using the EDNS
client subnet extension. I am a PhD student at USC and have been doing
similar work. Using EDNS and techniques we developed, we found Google has
been rapidly expanding where is serves search from:
http://nsl.cs.usc.edu/~mcalder/animatedmap.gif (10 MB).
For data and more details, see project page http://mappinggoogle.cs.usc.edu and
tech report available at http://www.cs.usc.edu/assets/006/86340.pdf.
I believe that updated versions of both papers will be appearing at the
Internet Measurement Conference in the fall. We'd love any feedback from
you or from anyone on dnsop as we revise the paper for IMC and as we
continue related work going forward.

As a follow up to a question in the original thread, there are also number
of smaller CDNs which have invested in ECS such as CDN77, ChinaCache,
CacheFly and EdgeCast. There is a decent intro to edns-client-subnet at
http://www.cdnplanet.com/blog/which-cdns-support-edns-client-subnet/.

Cheers!
Matt

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

<div dir=3D"ltr"><div>Apologies for not being able to post in the original =
thread.</div><div><br></div><div><span style=3D"font-family:arial,sans-seri=
f;font-size:13.333333969116211px">A few weeks ago, Florian Streibelt posted=
 his research paper using the EDNS client subnet extension. I am a PhD stud=
ent at USC and have been doing similar work</span>. Using EDNS and techniqu=
es we developed, we found Google has been rapidly expanding where is serves=
 search from:=A0<a href=3D"http://nsl.cs.usc.edu/~mcalder/animatedmap.gif">=
http://nsl.cs.usc.edu/~mcalder/animatedmap.gif</a> (10 MB).=A0</div>

<div>For data and more details, see project page <a href=3D"http://mappingg=
oogle.cs.usc.edu/" target=3D"_blank">http://mappinggoogle.cs.usc.edu</a>=A0=
and tech report available at=A0<a href=3D"http://www.cs.usc.edu/assets/006/=
86340.pdf" target=3D"_blank">http://www.cs.usc.edu/assets/006/86340.pdf</a>=
. I=A0believe that updated versions of both papers will be appearing at the=
 Internet Measurement Conference in the fall. We&#39;d love any feedback fr=
om you or from anyone on dnsop as we revise the paper for IMC and as we con=
tinue related work going forward.</div>


<div>
<br></div><div>As a follow up to a question in the original thread, there a=
re also number of smaller CDNs which have invested in ECS such as CDN77, Ch=
inaCache, CacheFly and EdgeCast. There is a decent intro to edns-client-sub=
net at=A0<a href=3D"http://www.cdnplanet.com/blog/which-cdns-support-edns-c=
lient-subnet/" target=3D"_blank">http://www.cdnplanet.com/blog/which-cdns-s=
upport-edns-client-subnet/</a>.=A0</div>



<div><br></div><div>Cheers!</div><div>Matt</div></div>

--089e011618ce2d94c304e25a6052--

From jay@nzrs.net.nz  Tue Jul 30 17:05:47 2013
Return-Path: <jay@nzrs.net.nz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5931C11E8130 for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2013 17:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2vCQN+UAzCL for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2013 17:05:43 -0700 (PDT)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id 0E13B21E8096 for <dnsop@ietf.org>; Tue, 30 Jul 2013 17:05:31 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id 7BF934B24EA for <dnsop@ietf.org>; Wed, 31 Jul 2013 12:05:30 +1200 (NZST)
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QNml17mbvf7n for <dnsop@ietf.org>; Wed, 31 Jul 2013 12:05:30 +1200 (NZST)
Received: from [192.168.22.173] (unknown [202.46.183.35]) (Authenticated sender: jay) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id 61D984B195A for <dnsop@ietf.org>; Wed, 31 Jul 2013 12:05:30 +1200 (NZST)
From: Jay Daley <jay@nzrs.net.nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
Date: Wed, 31 Jul 2013 12:05:33 +1200
To: dnsop WG <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Subject: [DNSOP] dnsxml - A standard XML representation of DNS data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 00:05:47 -0000

Hi All

The title says it all.  I would be interested in your views and any =
support that might exist for this.  Apologies but I have yet to see how =
this fits with Stephane's work on a JSON representation of DNS as this =
has taken quite a few years to write.

cheers
Jay


A new version of I-D, draft-daley-dnsxml-00.txt
has been successfully submitted by Jay Daley and posted to the
IETF repository.

Filename:	 draft-daley-dnsxml
Revision:	 00
Title:		 dnsxml - A standard XML representation of DNS data
Creation date:	 2013-07-31
Group:		 Individual Submission
Number of pages: 54
URL:             =
http://www.ietf.org/internet-drafts/draft-daley-dnsxml-00.txt
Status:          http://datatracker.ietf.org/doc/draft-daley-dnsxml
Htmlized:        http://tools.ietf.org/html/draft-daley-dnsxml-00


Abstract:
  This memo describes a syntax for encoding DNS Resource Records in
  XML, and a schema to define that syntax written in XML Schema.  It
  can be used to represent all DNS RDATA.  This can be used by diverse
  applications as a common format.

  DNS Resource Records are represented as XML elements with the name of
  the element taken from the mnemonic used to represent the DNS
  Resource Record in presentation format.  The RDATA is represented as
  XML attributes or content of the element.  The attribute names are
  taken from the RDATA field names specified in the normative RFC.

--=20
Jay Daley
Chief Executive
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 931 6977
mobile: +64 21 678840
linkedin: www.linkedin.com/in/jaydaley


From tim.wicinski@teamaol.com  Tue Jul 30 23:05:51 2013
Return-Path: <tim.wicinski@teamaol.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7470221F9F70 for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2013 23:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQ387+mTN1BF for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2013 23:05:47 -0700 (PDT)
Received: from omr-m07.mx.aol.com (omr-m07.mx.aol.com [64.12.143.81]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5EA21F9F6C for <dnsop@ietf.org>; Tue, 30 Jul 2013 23:05:47 -0700 (PDT)
Received: from aoldtcmei32.ad.aol.aoltw.net (aoldtcmei32.office.aol.com [10.180.121.111]) by omr-m07.mx.aol.com (Outbound Mail Relay) with ESMTP id 7EFD370000097; Wed, 31 Jul 2013 02:05:44 -0400 (EDT)
Received: from tjw.local (172.17.8.193) by aoldtcmei32.ad.aol.aoltw.net (10.180.121.111) with Microsoft SMTP Server id 14.3.123.3; Wed, 31 Jul 2013 02:05:44 -0400
Message-ID: <51F8A937.5060007@teamaol.com>
Date: Wed, 31 Jul 2013 08:05:43 +0200
From: Tim Wicinski <tim.wicinski@teamaol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Jay Daley <jay@nzrs.net.nz>, dnsop WG <dnsop@ietf.org>
References: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
In-Reply-To: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.17.8.193]
Subject: Re: [DNSOP] dnsxml - A standard XML representation of DNS data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 06:05:51 -0000

Jay

Couple of things here:  It's a little last minute to throw it onto the 
agenda, and we'll need to have some of that discussion. Second, there is 
another document floating out there on rDNS 
http://tools.ietf.org/html/draft-manderson-rdns-xml-01

I would suspect that we'll need to break down how each one document 
affects the other (are the complimentary or overlapping, etc.).  Then 
there is the entire "if XML is the answer in 2013, what really is the 
question?" question.

If you're in town, I've been hunkered down in the Terminal Room 
hammering on several different things.

tim

On 7/31/13 2:05 AM, Jay Daley wrote:
> Hi All
>
> The title says it all.  I would be interested in your views and any support that might exist for this.  Apologies but I have yet to see how this fits with Stephane's work on a JSON representation of DNS as this has taken quite a few years to write.
>
> cheers
> Jay
>
>
> A new version of I-D, draft-daley-dnsxml-00.txt
> has been successfully submitted by Jay Daley and posted to the
> IETF repository.
>
> Filename:	 draft-daley-dnsxml
> Revision:	 00
> Title:		 dnsxml - A standard XML representation of DNS data
> Creation date:	 2013-07-31
> Group:		 Individual Submission
> Number of pages: 54
> URL:             http://www.ietf.org/internet-drafts/draft-daley-dnsxml-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-daley-dnsxml
> Htmlized:        http://tools.ietf.org/html/draft-daley-dnsxml-00
>
>
> Abstract:
>    This memo describes a syntax for encoding DNS Resource Records in
>    XML, and a schema to define that syntax written in XML Schema.  It
>    can be used to represent all DNS RDATA.  This can be used by diverse
>    applications as a common format.
>
>    DNS Resource Records are represented as XML elements with the name of
>    the element taken from the mnemonic used to represent the DNS
>    Resource Record in presentation format.  The RDATA is represented as
>    XML attributes or content of the element.  The attribute names are
>    taken from the RDATA field names specified in the normative RFC.
>


From jay@nzrs.net.nz  Wed Jul 31 00:10:32 2013
Return-Path: <jay@nzrs.net.nz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6B9E21F9E13 for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 00:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEqLqZabFRpw for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 00:10:28 -0700 (PDT)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id 8358D21F9F9A for <dnsop@ietf.org>; Wed, 31 Jul 2013 00:10:25 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id A84DF4B2291; Wed, 31 Jul 2013 19:10:23 +1200 (NZST)
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LPVMCzs7gaDm; Wed, 31 Jul 2013 19:10:23 +1200 (NZST)
Received: from [192.168.1.230] (121-74-100-115.telstraclear.net [121.74.100.115]) (Authenticated sender: jay) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id 56A504AEF3C; Wed, 31 Jul 2013 19:10:23 +1200 (NZST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jay Daley <jay@nzrs.net.nz>
In-Reply-To: <51F8A937.5060007@teamaol.com>
Date: Wed, 31 Jul 2013 19:10:19 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AAE2D591-DEFB-4B65-BD09-AAFD74483505@nzrs.net.nz>
References: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz> <51F8A937.5060007@teamaol.com>
To: Tim Wicinski <tim.wicinski@teamaol.com>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] dnsxml - A standard XML representation of DNS data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 07:10:32 -0000

Hi Tim

On 31/07/2013, at 6:05 PM, Tim Wicinski <tim.wicinski@teamaol.com> =
wrote:

> Jay
>=20
> Couple of things here:  It's a little last minute to throw it onto the =
agenda, and we'll need to have some of that discussion.

I'm not there and don't worry I wasn't trying to get it onto the agenda. =
 I've sat on this for so long I just had to get it out this week or it =
would have been another year.

> Second, there is another document floating out there on rDNS =
http://tools.ietf.org/html/draft-manderson-rdns-xml-01

Thanks, I'll take a read.

> I would suspect that we'll need to break down how each one document =
affects the other (are the complimentary or overlapping, etc.). =20

Agreed.  Mine is very much targeted at representing DNS data in the best =
way possible and not any protocol that wraps around it.

> Then there is the entire "if XML is the answer in 2013, what really is =
the question?" question.

My own view is that XML is already being used for DNS data in a number =
of places (e.g. control of Nominum servers) that the question has =
already been asked and answered.

cheers
Jay

>=20
> If you're in town, I've been hunkered down in the Terminal Room =
hammering on several different things.
>=20
> tim
>=20
> On 7/31/13 2:05 AM, Jay Daley wrote:
>> Hi All
>>=20
>> The title says it all.  I would be interested in your views and any =
support that might exist for this.  Apologies but I have yet to see how =
this fits with Stephane's work on a JSON representation of DNS as this =
has taken quite a few years to write.
>>=20
>> cheers
>> Jay
>>=20
>>=20
>> A new version of I-D, draft-daley-dnsxml-00.txt
>> has been successfully submitted by Jay Daley and posted to the
>> IETF repository.
>>=20
>> Filename:	 draft-daley-dnsxml
>> Revision:	 00
>> Title:		 dnsxml - A standard XML representation of DNS =
data
>> Creation date:	 2013-07-31
>> Group:		 Individual Submission
>> Number of pages: 54
>> URL:             =
http://www.ietf.org/internet-drafts/draft-daley-dnsxml-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-daley-dnsxml
>> Htmlized:        http://tools.ietf.org/html/draft-daley-dnsxml-00
>>=20
>>=20
>> Abstract:
>>   This memo describes a syntax for encoding DNS Resource Records in
>>   XML, and a schema to define that syntax written in XML Schema.  It
>>   can be used to represent all DNS RDATA.  This can be used by =
diverse
>>   applications as a common format.
>>=20
>>   DNS Resource Records are represented as XML elements with the name =
of
>>   the element taken from the mnemonic used to represent the DNS
>>   Resource Record in presentation format.  The RDATA is represented =
as
>>   XML attributes or content of the element.  The attribute names are
>>   taken from the RDATA field names specified in the normative RFC.
>>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--=20
Jay Daley
Chief Executive
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 931 6977
mobile: +64 21 678840
linkedin: www.linkedin.com/in/jaydaley


From paul.hoffman@vpnc.org  Wed Jul 31 00:54:05 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D71C711E8165 for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 00:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dKYxXsso5eV6 for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 00:54:04 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id AF82621F9FE1 for <dnsop@ietf.org>; Wed, 31 Jul 2013 00:54:04 -0700 (PDT)
Received: from dhcp-64c3.meeting.ietf.org (dhcp-64c3.meeting.ietf.org [130.129.100.195]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r6V7rsSf046367 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 31 Jul 2013 00:53:57 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
Date: Wed, 31 Jul 2013 09:53:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B662C88-D969-4586-A01F-5D36E5B8DA53@vpnc.org>
References: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
To: Jay Daley <jay@nzrs.net.nz>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] dnsxml - A standard XML representation of DNS data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 07:54:06 -0000

Please also see draft-bortzmeyer-dns-json. JSON encoders and parsers are =
lighter-weight than XML ones, and for the data in question (everything =
DNS), it seems like JSON might be a better text format for the use cases =
(particularly logging).

--Paul Hoffman=

From jay@nzrs.net.nz  Wed Jul 31 01:01:42 2013
Return-Path: <jay@nzrs.net.nz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 353F011E8165 for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 01:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tA0cvTaf+KTV for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 01:01:33 -0700 (PDT)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id A2B6121F9F9D for <dnsop@ietf.org>; Wed, 31 Jul 2013 01:01:30 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id CBBB44B244C; Wed, 31 Jul 2013 20:01:29 +1200 (NZST)
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xI+kNCHOCxOR; Wed, 31 Jul 2013 20:01:29 +1200 (NZST)
Received: from [192.168.1.230] (121-74-100-115.telstraclear.net [121.74.100.115]) (Authenticated sender: jay) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id 67A6E4B22B5; Wed, 31 Jul 2013 20:01:29 +1200 (NZST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jay Daley <jay@nzrs.net.nz>
In-Reply-To: <7B662C88-D969-4586-A01F-5D36E5B8DA53@vpnc.org>
Date: Wed, 31 Jul 2013 20:01:27 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <58D17552-D4DD-45FC-9975-236D61635347@nzrs.net.nz>
References: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz> <7B662C88-D969-4586-A01F-5D36E5B8DA53@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] dnsxml - A standard XML representation of DNS data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 08:01:42 -0000

Hi Paul

On 31/07/2013, at 7:53 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> Please also see draft-bortzmeyer-dns-json. JSON encoders and parsers =
are lighter-weight than XML ones, and for the data in question =
(everything DNS), it seems like JSON might be a better text format for =
the use cases (particularly logging).

I'm aware of Stephane's draft as noted in my original email but I =
haven't had a chance to read it.  I will though.

Rather than picking a winner between JSON and XML I've always found it =
prudent to recognise that the two have different characteristics that =
support different uses.  Not only can JSON and XML co-exist but also, if =
needed, the JSON can be derived from the XML via XSLT:

	http://controlfreak.net/xml-to-json-in-xslt-a-toolkit/

cheers
Jay

>=20
> --Paul Hoffman
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--=20
Jay Daley
Chief Executive
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 931 6977
mobile: +64 21 678840
linkedin: www.linkedin.com/in/jaydaley


From jay@nzrs.net.nz  Wed Jul 31 02:30:37 2013
Return-Path: <jay@nzrs.net.nz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD09F21F9EEE for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 02:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EF-RXWRR9TQC for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 02:30:06 -0700 (PDT)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id 9A24321F99AB for <dnsop@ietf.org>; Wed, 31 Jul 2013 02:30:05 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id 6AFE44B2469 for <dnsop@ietf.org>; Wed, 31 Jul 2013 21:30:03 +1200 (NZST)
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rBcFMZw1AXH for <dnsop@ietf.org>; Wed, 31 Jul 2013 21:30:03 +1200 (NZST)
Received: from [192.168.1.230] (121-74-100-115.telstraclear.net [121.74.100.115]) (Authenticated sender: jay) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id 256124B2454 for <dnsop@ietf.org>; Wed, 31 Jul 2013 21:30:03 +1200 (NZST)
From: Jay Daley <jay@nzrs.net.nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AD202E6-14DF-4403-9530-39ACBE8EC697@nzrs.net.nz>
Date: Wed, 31 Jul 2013 21:30:02 +1200
To: dnsop WG <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Subject: [DNSOP] Comparison of XML/JSON DNS drafts
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 09:30:37 -0000

For this I looked at three drafts:

	draft-manderson-rdns-xml-01
	draft-bortzmeyer-dns-json
	draft-daley-dnsxml

The comparison looked a the following criteria:

0.  XML or JSON
1.  Coverage of RR types
2.  What is covered - specifically is it just RRs or also any parts of =
the DNS protocol or other.
3.  Are RDATA fields and the contents of the RDATA fields described.
4.  Use of consistent data types for RDATA and support for semantic =
equivalence.
5.  The level of validation available.=20
6.  Extensibility.


draft-manderson-rdns-xml-01 :

0.  XML
1.  Only covers one two RR types - DS and NS
2.  These two RRs are defined are part of a provisioning protocol =
separate from DNS.
3.  The RDATA is provided as a single text string that is parsed by the =
receiving applications and so can contain any fields with any content.
4.  No data types specified for RDATA and therefore no support for =
semantic equivalence.
5.  No validation of RDATA takes place though protocol itself is =
validated using RelaxNG.
6.  No specific support for extensibility.


draft-bortzmeyer-dns-json :

0. JSON
1.  Covers 16 RR types
2.  Defines both the RRs, the DNS message and zone files.
3.  Field names are defined but as this is unvalidated, fields could be =
omitted and additional fields added and it would be for the application =
to determine this.  Field contents are not defined.
4.  No data types specified for RDATA  and therefore no support for =
semantic equivalence.
5.  No validation. =20
6.  No specific support for extensibility.


draft-daley-dnsxml :

0. XML
1.  Covers 47 RR types and the unknown type (Only NB and NBSTAT are not =
included)
2.  Only defines RRs.
3.  All fields are defined and all field contents are defined.
4.  Standard field contents defined wherever possible including =
standards tables of mnemonics, algorithms, time durations, unions of =
mutliple type, etc.  Full support for semantic equivalence.
5.  Full XML-Schema validation.  RDATA fields are validated so mandatory =
fields must be present, optional fields may be present and additional =
fields cannot be present for validation to succeed.  RDATA field =
contents validated to any possible wire format to allow for broken data =
that could be transmitted on the wire. =20
6.  Specific support for extensibility so a new DNS type could be =
defined separately and work seamlessly.


So to summarise:

draft-manderson-rdns-xml-01 is a short and fixed provisioning protocol =
that includes a small bit of DNS.
draft-bortzmeyer-dns-json is the start of a process to create a standard =
representation but a long way to go.
draft-daley-dnsxml is the end of that process - a standard =
representation and fully validatable.

cheers
Jay

--=20
Jay Daley
Chief Executive
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 931 6977
mobile: +64 21 678840
linkedin: www.linkedin.com/in/jaydaley


From bortzmeyer@nic.fr  Wed Jul 31 03:15:04 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1085E21E80B3 for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 03:15:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7-xx56DnryTh for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 03:14:59 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id F3D8721E8055 for <dnsop@ietf.org>; Wed, 31 Jul 2013 03:14:55 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id C53162804E4; Wed, 31 Jul 2013 12:14:21 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id C0B3228015A; Wed, 31 Jul 2013 12:14:21 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id B57E8B38066; Wed, 31 Jul 2013 12:13:51 +0200 (CEST)
Date: Wed, 31 Jul 2013 12:13:51 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Jay Daley <jay@nzrs.net.nz>
Message-ID: <20130731101351.GB2874@nic.fr>
References: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
X-Operating-System: Debian GNU/Linux 7.1
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 WG <dnsop@ietf.org>
Subject: Re: [DNSOP] dnsxml - A standard XML representation of DNS data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 10:15:04 -0000

On Wed, Jul 31, 2013 at 12:05:33PM +1200,
 Jay Daley <jay@nzrs.net.nz> wrote 
 a message of 47 lines which said:

> Filename:	 draft-daley-dnsxml
> Revision:	 00
> Title:		 dnsxml - A standard XML representation of DNS data

Note that there is an implementation, based on a (earlier,
non-released) version of the draft:

http://www.bortzmeyer.org/dns-lg-usage.html


From bortzmeyer@nic.fr  Wed Jul 31 03:17:26 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F013F21F9DBA for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 03:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CxrHoyDyzWak for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 03:17:20 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 06C4821F9EA3 for <dnsop@ietf.org>; Wed, 31 Jul 2013 03:17:20 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 610382806E8; Wed, 31 Jul 2013 12:16:49 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 5CA962804E4; Wed, 31 Jul 2013 12:16:49 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id 5191EB3806A; Wed, 31 Jul 2013 12:16:19 +0200 (CEST)
Date: Wed, 31 Jul 2013 12:16:19 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Jay Daley <jay@nzrs.net.nz>
Message-ID: <20130731101619.GC2874@nic.fr>
References: <3AD202E6-14DF-4403-9530-39ACBE8EC697@nzrs.net.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3AD202E6-14DF-4403-9530-39ACBE8EC697@nzrs.net.nz>
X-Operating-System: Debian GNU/Linux 7.1
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 WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Comparison of XML/JSON DNS drafts
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 10:17:26 -0000

On Wed, Jul 31, 2013 at 09:30:02PM +1200,
 Jay Daley <jay@nzrs.net.nz> wrote 
 a message of 71 lines which said:

> 	draft-bortzmeyer-dns-json

Presented in Orlando but unmaintained afterwards (sorry). I plan to
resume it at the autumn.

> draft-bortzmeyer-dns-json :
> 
> 0. JSON
> 1.  Covers 16 RR types

In Orlando, there was clear consensus that a better way to define the
RR (rather than by enumerating all the possible RRs) would be a good
thigng. New RR type appear from time to time. How would you handle
that? By publishing a new version of the RFC?


From jay@nzrs.net.nz  Wed Jul 31 03:27:23 2013
Return-Path: <jay@nzrs.net.nz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB8A11E80F4 for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 03:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mZ0TqPpC+AUn for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 03:27:16 -0700 (PDT)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id ECF9521F9F5B for <dnsop@ietf.org>; Wed, 31 Jul 2013 03:27:14 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id 157D94B2469; Wed, 31 Jul 2013 22:27:14 +1200 (NZST)
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bHyxaUReMmd; Wed, 31 Jul 2013 22:27:14 +1200 (NZST)
Received: from [192.168.1.230] (121-74-100-115.telstraclear.net [121.74.100.115]) (Authenticated sender: jay) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id B860F4B2466; Wed, 31 Jul 2013 22:27:13 +1200 (NZST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jay Daley <jay@nzrs.net.nz>
In-Reply-To: <20130731101619.GC2874@nic.fr>
Date: Wed, 31 Jul 2013 22:27:12 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7035F1CB-F4EB-4467-91F5-7F9B121AF78B@nzrs.net.nz>
References: <3AD202E6-14DF-4403-9530-39ACBE8EC697@nzrs.net.nz> <20130731101619.GC2874@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1508)
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Comparison of XML/JSON DNS drafts
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 10:27:23 -0000

On 31/07/2013, at 10:16 PM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:

> In Orlando, there was clear consensus that a better way to define the
> RR (rather than by enumerating all the possible RRs) would be a good
> thigng. New RR type appear from time to time. How would you handle
> that? By publishing a new version of the RFC?

No, by the mechanism described in section 3.4 =
(http://tools.ietf.org/html/draft-daley-dnsxml-00#page-18).  This shows =
how to create an extension that defines the XML for a new RR.  This =
could either be in a new RFC or the RFC that defines the RR could =
include the dnsxml for it if required. =20

The extension feature uses the xml-schema feature of substitutionGroup =
that ensures that the new XML RR is exactly equivalent to an existing =
XML RR.  In other words this is different from EPP where extensions go =
into a different section.

A full example is provided in the draft.

cheers
Jay

>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--=20
Jay Daley
Chief Executive
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 931 6977
mobile: +64 21 678840
linkedin: www.linkedin.com/in/jaydaley


From each@isc.org  Wed Jul 31 08:58:03 2013
Return-Path: <each@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45F2B21F9CB1 for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 08:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mdlXiftaZzMp for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 08:58:02 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id AC9D621F97E6 for <dnsop@ietf.org>; Wed, 31 Jul 2013 08:58:02 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id EE518C9425 for <dnsop@ietf.org>; Wed, 31 Jul 2013 15:57:50 +0000 (UTC) (envelope-from each@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1375286282; bh=N6y7NbjeCdQfsqE6brA3ymUQdOlmkIm8PZUOwECDpCk=; h=Date:From:To:Subject; b=DL54mDX/6zNDl7dIpM5Ea6MWHkyOp60mCOr7l2jAwDJFGN6DX/i9n575ciaUn4FRQ Z7IivqvD9I3JdNLt0yVTgJWE8lEf+3909h5oyiwS/VH09XfEjMbU+7ZE/RDSuSf3NU /WJJdT6oufSTHk3qI0SrOCncnhgkGn19CFZaVdPA=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS for <dnsop@ietf.org>; Wed, 31 Jul 2013 15:57:50 +0000 (UTC) (envelope-from each@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id DD346216C25; Wed, 31 Jul 2013 15:57:50 +0000 (UTC)
Date: Wed, 31 Jul 2013 15:57:50 +0000
From: Evan Hunt <each@isc.org>
To: dnsop@ietf.org
Message-ID: <20130731155750.GA18546@isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
X-DCC--Metrics: post.isc.org; whitelist
Subject: [DNSOP] informal review request: server diagnostics option
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 15:58:03 -0000

Greetings,

I've been working for a while on a draft describing a DNS protocol
extention that would allow a server (e.g. a validating resolver) to
return, upon request, additional diagnostic information along with
SERVFAIL responses, providing more transparency into the reasons for
failures.  The work has been on hold for a while, waiting until I was
free to attend another IETF, but at the urging of Francis Dupont, I've
gone ahead and submitted it today.

This is an individual contribution: as a protocol extension, I believe
it falls outside dnsop's charter.  However, it may be of interest to
members of this working group, and certainly could use your input; I'd
appreciate any suggestions and corrections people may wish to offer.

Thanks,

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.

From each@isc.org  Wed Jul 31 09:19:30 2013
Return-Path: <each@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D62821E804E for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 09:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0EJADFf3xgG for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 09:19:29 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 867CD21F8925 for <dnsop@ietf.org>; Wed, 31 Jul 2013 09:19:29 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 0526DC94F7 for <dnsop@ietf.org>; Wed, 31 Jul 2013 16:19:17 +0000 (UTC) (envelope-from each@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1375287569; bh=wmGgZyfC4+q0Q25+Zt9T2kntzA65rds2H/9invCfNPQ=; h=Date:From:To:Subject:References:In-Reply-To; b=HUk+NO6uvpRKg2rz4jfUpOWijgIuTYCqZmv2nhJCXlgHKJMHms1wkrK7z/SrURgY4 C9sGHD2H2STeF6gGzrK8SUuvOrvLOx6JaEYyTvTL13Q9nAaXXx4TgGNGEbO3aHc5Hm CoOtP2t4oM+40KeZxpZLDMi+KgWhPKQDGPTSz+PM=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS for <dnsop@ietf.org>; Wed, 31 Jul 2013 16:19:17 +0000 (UTC) (envelope-from each@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id E8284216C25; Wed, 31 Jul 2013 16:19:16 +0000 (UTC)
Date: Wed, 31 Jul 2013 16:19:16 +0000
From: Evan Hunt <each@isc.org>
To: dnsop@ietf.org
Message-ID: <20130731161916.GA19148@isc.org>
References: <20130731155750.GA18546@isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130731155750.GA18546@isc.org>
User-Agent: Mutt/1.4.2.3i
X-DCC--Metrics: post.isc.org; whitelist
Subject: Re: [DNSOP] informal review request: server diagnostics option
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 16:19:30 -0000

> I've been working for a while on a draft describing a DNS protocol
> extention that would allow a server (e.g. a validating resolver) to
> return, upon request, additional diagnostic information along with
> SERVFAIL responses, providing more transparency into the reasons for
> failures.

Also, apparently I'm an idiot, because I neglected to mention the URL:
http://www.ietf.org/internet-drafts/draft-hunt-dns-server-diagnostics-00.txt

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.
