
From peter@denic.de  Mon Jul  4 08:49:57 2011
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 7992F21F8699 for <dnsop@ietfa.amsl.com>; Mon,  4 Jul 2011 08:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jpegOemcaVzI for <dnsop@ietfa.amsl.com>; Mon,  4 Jul 2011 08:49:56 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA6D21F8698 for <dnsop@ietf.org>; Mon,  4 Jul 2011 08:49:56 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QdlPH-0003Ut-08; Mon, 04 Jul 2011 17:49:55 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QdlPG-0002w7-Sh; Mon, 04 Jul 2011 17:49:54 +0200
Date: Mon, 4 Jul 2011 17:49:54 +0200
From: Peter Koch <pk@DENIC.DE>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20110704154954.GL10707@x27.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] DNSOP session scheduled for Quebec (IETF81)
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, 04 Jul 2011 15:49:57 -0000

Dear WG,

the DNSOP slot for Quebec has been (re-)scheduled to Tuesday, 1300
<http://tools.ietf.org/agenda/81/#2011-07-28_1300>.  The main agenda is
still in flux, so the list of parallel sessions may change.

We've been assigned a two hour slot, which is a bit longer than what we asked
for. Please watch (and help) the agenda grow at

	<http://www.ietf.org/proceedings/81/agenda/dnsop.txt>

In terms of I/O with other WGs, there are two BOFs members of this WG
might want to have a look at <http://trac.tools.ietf.org/bof/trac/wiki/WikiStart>,

  o Homenet (aka "fun"), with a draft charter discussed in a thread starting at
    <http://www.ietf.org/mail-archive/web/fun/current/msg00002.html>

  o Repute
    <http://www.blackops.org/~msk/domainrep/repute-charter.txt>

Please let Stephen and me know if you have proposals for agenda items.

-Peter

From cet1@hermes.cam.ac.uk  Tue Jul  5 12:48:11 2011
Return-Path: <cet1@hermes.cam.ac.uk>
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 C3DD421F88C5 for <dnsop@ietfa.amsl.com>; Tue,  5 Jul 2011 12:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.74
X-Spam-Level: 
X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QWee4UKSIpbG for <dnsop@ietfa.amsl.com>; Tue,  5 Jul 2011 12:48:10 -0700 (PDT)
Received: from ppsw-52.csi.cam.ac.uk (ppsw-52.csi.cam.ac.uk [131.111.8.152]) by ietfa.amsl.com (Postfix) with ESMTP id 1154A21F88C4 for <dnsop@ietf.org>; Tue,  5 Jul 2011 12:48:10 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:59474) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:cet1) id 1QeBbM-00071o-Fa (Exim 4.72) (return-path <cet1@hermes.cam.ac.uk>); Tue, 05 Jul 2011 20:48:08 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:cet1) id 1QeBbM-00061g-Qb (Exim 4.67) (return-path <cet1@hermes.cam.ac.uk>); Tue, 05 Jul 2011 20:48:08 +0100
Received: from [131.111.11.47] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.4); 05 Jul 2011 20:48:08 +0100
Date: 05 Jul 2011 20:48:08 +0100
From: Chris Thompson <cet1@cam.ac.uk>
To: Olafur Gudmundsson <ogud@ogud.com>
Message-ID: <Prayer.1.3.4.1107052048080.12617@hermes-2.csi.cam.ac.uk>
In-Reply-To: <4E0CA4AD.4020703@ogud.com>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <4E0C88EA.8050909@googlemail.com> <4E0CA4AD.4020703@ogud.com>
X-Mailer: Prayer v1.3.4
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Chris Thompson <cet1@hermes.cam.ac.uk>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cet1@cam.ac.uk
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, 05 Jul 2011 19:48:11 -0000

On Jun 30 2011, Olafur Gudmundsson wrote:
[... snip ...]
>It would be nice, and make the system more robust. FWIW I think NS can 
>be automatically maintained after we have DNSSEC by having the parent 
>copy what the child publishes.

At first sight this looks as though it only involves the parent and
child, but there could be problems with automatically updating glue.
The authoritative value of "required glue" may come from a grandchild
zone which is not signed, even if the child is, and "sibling glue"
could similarly involve unsigned zones.

-- 
Chris Thompson               University of Cambridge Computing Service,
Email: cet1@ucs.cam.ac.uk    New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715       United Kingdom.

From cet1@hermes.cam.ac.uk  Tue Jul  5 13:09:23 2011
Return-Path: <cet1@hermes.cam.ac.uk>
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 76C3121F85DD for <dnsop@ietfa.amsl.com>; Tue,  5 Jul 2011 13:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A2VgS9sIY84O for <dnsop@ietfa.amsl.com>; Tue,  5 Jul 2011 13:09:21 -0700 (PDT)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 6641821F8591 for <dnsop@ietf.org>; Tue,  5 Jul 2011 13:09:21 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:51000) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:cet1) id 1QeBvs-0002ik-qU (Exim 4.72) (return-path <cet1@hermes.cam.ac.uk>); Tue, 05 Jul 2011 21:09:20 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:cet1) id 1QeBvs-0000BW-8B (Exim 4.67) (return-path <cet1@hermes.cam.ac.uk>); Tue, 05 Jul 2011 21:09:20 +0100
Received: from [131.111.11.47] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.4); 05 Jul 2011 21:09:20 +0100
Date: 05 Jul 2011 21:09:20 +0100
From: Chris Thompson <cet1@cam.ac.uk>
To: George Barwood <george.barwood@blueyonder.co.uk>
Message-ID: <Prayer.1.3.4.1107052109200.12617@hermes-2.csi.cam.ac.uk>
In-Reply-To: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local>
X-Mailer: Prayer v1.3.4
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Chris Thompson <cet1@hermes.cam.ac.uk>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cet1@cam.ac.uk
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, 05 Jul 2011 20:09:23 -0000

On Jun 12 2011, George Barwood wrote:

>I have updated the draft
>
>http://www.ietf.org/id/draft-barwood-dnsop-ds-publish-02.txt
>
>I have added an appendix with an exampler KSK rollover, and made
>various generally minor changes.
>
>IANA have now assigned type code 59 for the CDS RRtype.
>
>I'd like to request that the WG adopt this document.

While everyone else is discussing policy issues, can I raise a
technical one?

| The CDS record MUST be signed with a key that has the Secure Entry
| Point flag set.
[...]
| The parent zone SHOULD check that the signing key(s) have the Secure
| Entry Point flag set.

This is changed from the first draft, replacing "KSK" by "SEP flag".
but it still doesn't make sense to me. The draft doesn't seem to
contain any indication as to why this is desirable.

Not all signed zones have a key with the SEP flag set. I don't see why
they should be excluded from using this mechanism.

Obviously, the intent isn't that that the CDS *refer* to a key with the
SEP flag set, as this is unenforceable if the key hasn't even been
published yet (as suggested in section 1).

If the intent is to minimise the length of the chain of trust being
used, then "MUST be signed with a key for which the parent already
holds a DS record" would be the appropriate modification. But is
this really necessary?

-- 
Chris Thompson               University of Cambridge Computing Service,
Email: cet1@ucs.cam.ac.uk    New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715       United Kingdom.

From george.barwood@blueyonder.co.uk  Tue Jul  5 14:22:56 2011
Return-Path: <george.barwood@blueyonder.co.uk>
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 F2BDF21F89D4 for <dnsop@ietfa.amsl.com>; Tue,  5 Jul 2011 14:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.846
X-Spam-Level: 
X-Spam-Status: No, score=-0.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4HRJn6GE3Z1 for <dnsop@ietfa.amsl.com>; Tue,  5 Jul 2011 14:22:54 -0700 (PDT)
Received: from mtaout03-winn.ispmail.ntl.com (mtaout03-winn.ispmail.ntl.com [81.103.221.49]) by ietfa.amsl.com (Postfix) with ESMTP id 39B3A21F8981 for <dnsop@ietf.org>; Tue,  5 Jul 2011 14:22:53 -0700 (PDT)
Received: from know-smtpout-4.server.virginmedia.net ([62.254.123.4]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20110705212246.IEGW5301.mtaout03-winn.ispmail.ntl.com@know-smtpout-4.server.virginmedia.net>; Tue, 5 Jul 2011 22:22:46 +0100
Received: from [82.46.65.24] (helo=GeorgeLaptop) by know-smtpout-4.server.virginmedia.net with smtp (Exim 4.63) (envelope-from <george.barwood@blueyonder.co.uk>) id 1QeD4t-0006T2-Nh; Tue, 05 Jul 2011 22:22:43 +0100
Message-ID: <F48DC712030345AEB66B0F497406D14C@local>
From: "George Barwood" <george.barwood@blueyonder.co.uk>
To: <cet1@cam.ac.uk>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <Prayer.1.3.4.1107052109200.12617@hermes-2.csi.cam.ac.uk>
Date: Tue, 5 Jul 2011 22:22:09 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Cloudmark-Analysis: v=1.1 cv=R50lirqlHffDPPkwUlkuVa99MrvKdVWo//yz83qex8g= c=1 sm=0 a=NvRijEmkbiIA:10 a=3NElcqgl2aoA:10 a=8nJEP1OIZ-IA:10 a=B6GvL0XKAAAA:8 a=a5Gf7U6LAAAA:8 a=48vgC7mUAAAA:8 a=5oSU3fHApfSUEHb3Q4IA:9 a=rNP2ggXG-7qUOw3TBEgA:7 a=wPNLvfGTeEIA:10 a=940B4WtYyt0A:10 a=yHIqe9kG5mgA:10 a=lZB815dzVvQA:10 a=MqMq0s_f3wtgwNR3:21 a=WnzX8gbfpqaHOVhv:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
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, 05 Jul 2011 21:22:56 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkNocmlzIFRob21wc29uIiA8
Y2V0MUBjYW0uYWMudWs+DQpUbzogIkdlb3JnZSBCYXJ3b29kIiA8Z2VvcmdlLmJhcndvb2RAYmx1
ZXlvbmRlci5jby51az4NCkNjOiA8ZG5zb3BAaWV0Zi5vcmc+DQpTZW50OiBUdWVzZGF5LCBKdWx5
IDA1LCAyMDExIDk6MDkgUE0NClN1YmplY3Q6IFJlOiBbRE5TT1BdIENEUyBSUnR5cGUgLSBhdXRv
bWF0ZWQgS1NLIHJvbGxvdmVyDQoNCg0KPiBPbiBKdW4gMTIgMjAxMSwgR2VvcmdlIEJhcndvb2Qg
d3JvdGU6DQo+IA0KPj5JIGhhdmUgdXBkYXRlZCB0aGUgZHJhZnQNCj4+DQo+Pmh0dHA6Ly93d3cu
aWV0Zi5vcmcvaWQvZHJhZnQtYmFyd29vZC1kbnNvcC1kcy1wdWJsaXNoLTAyLnR4dA0KPj4NCj4+
SSBoYXZlIGFkZGVkIGFuIGFwcGVuZGl4IHdpdGggYW4gZXhhbXBsZXIgS1NLIHJvbGxvdmVyLCBh
bmQgbWFkZQ0KPj52YXJpb3VzIGdlbmVyYWxseSBtaW5vciBjaGFuZ2VzLg0KPj4NCj4+SUFOQSBo
YXZlIG5vdyBhc3NpZ25lZCB0eXBlIGNvZGUgNTkgZm9yIHRoZSBDRFMgUlJ0eXBlLg0KPj4NCj4+
SSdkIGxpa2UgdG8gcmVxdWVzdCB0aGF0IHRoZSBXRyBhZG9wdCB0aGlzIGRvY3VtZW50Lg0KPiAN
Cj4gV2hpbGUgZXZlcnlvbmUgZWxzZSBpcyBkaXNjdXNzaW5nIHBvbGljeSBpc3N1ZXMsIGNhbiBJ
IHJhaXNlIGENCj4gdGVjaG5pY2FsIG9uZT8NCj4gDQo+IHwgVGhlIENEUyByZWNvcmQgTVVTVCBi
ZSBzaWduZWQgd2l0aCBhIGtleSB0aGF0IGhhcyB0aGUgU2VjdXJlIEVudHJ5DQo+IHwgUG9pbnQg
ZmxhZyBzZXQuDQo+IFsuLi5dDQo+IHwgVGhlIHBhcmVudCB6b25lIFNIT1VMRCBjaGVjayB0aGF0
IHRoZSBzaWduaW5nIGtleShzKSBoYXZlIHRoZSBTZWN1cmUNCj4gfCBFbnRyeSBQb2ludCBmbGFn
IHNldC4NCj4gDQo+IFRoaXMgaXMgY2hhbmdlZCBmcm9tIHRoZSBmaXJzdCBkcmFmdCwgcmVwbGFj
aW5nICJLU0siIGJ5ICJTRVAgZmxhZyIuDQo+IGJ1dCBpdCBzdGlsbCBkb2Vzbid0IG1ha2Ugc2Vu
c2UgdG8gbWUuIFRoZSBkcmFmdCBkb2Vzbid0IHNlZW0gdG8NCj4gY29udGFpbiBhbnkgaW5kaWNh
dGlvbiBhcyB0byB3aHkgdGhpcyBpcyBkZXNpcmFibGUuDQo+IA0KPiBOb3QgYWxsIHNpZ25lZCB6
b25lcyBoYXZlIGEga2V5IHdpdGggdGhlIFNFUCBmbGFnIHNldC4gSSBkb24ndCBzZWUgd2h5DQo+
IHRoZXkgc2hvdWxkIGJlIGV4Y2x1ZGVkIGZyb20gdXNpbmcgdGhpcyBtZWNoYW5pc20uDQo+IA0K
PiBPYnZpb3VzbHksIHRoZSBpbnRlbnQgaXNuJ3QgdGhhdCB0aGF0IHRoZSBDRFMgKnJlZmVyKiB0
byBhIGtleSB3aXRoIHRoZQ0KPiBTRVAgZmxhZyBzZXQsIGFzIHRoaXMgaXMgdW5lbmZvcmNlYWJs
ZSBpZiB0aGUga2V5IGhhc24ndCBldmVuIGJlZW4NCj4gcHVibGlzaGVkIHlldCAoYXMgc3VnZ2Vz
dGVkIGluIHNlY3Rpb24gMSkuDQo+IA0KPiBJZiB0aGUgaW50ZW50IGlzIHRvIG1pbmltaXNlIHRo
ZSBsZW5ndGggb2YgdGhlIGNoYWluIG9mIHRydXN0IGJlaW5nDQo+IHVzZWQsIHRoZW4gIk1VU1Qg
YmUgc2lnbmVkIHdpdGggYSBrZXkgZm9yIHdoaWNoIHRoZSBwYXJlbnQgYWxyZWFkeQ0KPiBob2xk
cyBhIERTIHJlY29yZCIgd291bGQgYmUgdGhlIGFwcHJvcHJpYXRlIG1vZGlmaWNhdGlvbi4gQnV0
IGlzDQo+IHRoaXMgcmVhbGx5IG5lY2Vzc2FyeT8NCg0KVGhlIGludGVudCBpcyB0byByZXN0cmlj
dCB0aGUgYWJpbGl0eSB0byB1cGRhdGUgdGhlIHBhcmVudCBEUyB0byB0aG9zZSB3aG8gaGF2ZQ0K
YWNjZXNzIHRvIGtleSBzaWduaW5nIGtleXMuIFRodXMgd2hlcmUgdGhlcmUgaXMgYSBzcGxpdCBy
ZXNwb25zaWJpbGl0eSAoIHNpbWlsYXIgdG8NCnRoZSByb290IHpvbmUgd2hlcmUgSUFOQSBoYXMg
dGhlIEtTSyBwcml2YXRlIGtleSwgYW5kIFZlcmlzaWduIGhhcyBvbmx5IHRoZQ0KWlNLIHByaXZh
dGUga2V5ICksIG9ubHkgdGhlIHNlbmlvciBwYXJ0eSBjYW4gdXBkYXRlIHRoZSBwYXJlbnQgRFMu
DQpUaGUgcGFydHkgdGhhdCBvbmx5IGhvbGRzIHRoZSBaU0sgcHJpdmF0ZSBrZXkgY2Fubm90IHVw
ZGF0ZSB0aGUgcGFyZW50IGFuZA0KdGFrZSBvdmVyIHRoZSB6b25lLiANCg0KR2VvcmdlIA0KDQo+
IC0tIA0KPiBDaHJpcyBUaG9tcHNvbiAgICAgICAgICAgICAgIFVuaXZlcnNpdHkgb2YgQ2FtYnJp
ZGdlIENvbXB1dGluZyBTZXJ2aWNlLA0KPiBFbWFpbDogY2V0MUB1Y3MuY2FtLmFjLnVrICAgIE5l
dyBNdXNldW1zIFNpdGUsIENhbWJyaWRnZSBDQjIgM1FILA0KPiBQaG9uZTogKzQ0IDEyMjMgMzM0
NzE1ICAgICAgIFVuaXRlZCBLaW5nZG9tLg==


From ogud@ogud.com  Tue Jul  5 14:42:10 2011
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 E958221F8849 for <dnsop@ietfa.amsl.com>; Tue,  5 Jul 2011 14:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.289
X-Spam-Level: 
X-Spam-Status: No, score=-106.289 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVhEXUSpmbmf for <dnsop@ietfa.amsl.com>; Tue,  5 Jul 2011 14:42:10 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 341C821F881F for <dnsop@ietf.org>; Tue,  5 Jul 2011 14:42:10 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p65Lg6YJ022926; Tue, 5 Jul 2011 17:42:06 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4E13852E.7020400@ogud.com>
Date: Tue, 05 Jul 2011 17:42:06 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: cet1@cam.ac.uk
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <4E0C88EA.8050909@googlemail.com> <4E0CA4AD.4020703@ogud.com> <Prayer.1.3.4.1107052048080.12617@hermes-2.csi.cam.ac.uk>
In-Reply-To: <Prayer.1.3.4.1107052048080.12617@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
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, 05 Jul 2011 21:42:11 -0000

On 05/07/2011 3:48 PM, Chris Thompson wrote:
> On Jun 30 2011, Olafur Gudmundsson wrote:
> [... snip ...]
>> It would be nice, and make the system more robust. FWIW I think NS can
>> be automatically maintained after we have DNSSEC by having the parent
>> copy what the child publishes.
>
> At first sight this looks as though it only involves the parent and
> child, but there could be problems with automatically updating glue.
> The authoritative value of "required glue" may come from a grandchild
> zone which is not signed, even if the child is, and "sibling glue"
> could similarly involve unsigned zones.
>

Well is this any worse than what we have today with 
stale/unneeded/forged glue ?

It is not just grand child glue we need to worry about it is sibling 
glue and glue loops.

I do not know what is the right answer :-)

	Olafur

From cet1@hermes.cam.ac.uk  Wed Jul  6 09:25:30 2011
Return-Path: <cet1@hermes.cam.ac.uk>
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 852A221F87F3 for <dnsop@ietfa.amsl.com>; Wed,  6 Jul 2011 09:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.134
X-Spam-Level: 
X-Spam-Status: No, score=-6.134 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mpcVoWeTEHC3 for <dnsop@ietfa.amsl.com>; Wed,  6 Jul 2011 09:25:30 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfa.amsl.com (Postfix) with ESMTP id F016E21F87EF for <dnsop@ietf.org>; Wed,  6 Jul 2011 09:25:29 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:58382) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:cet1) id 1QeUum-0002AF-Rw (Exim 4.72) (return-path <cet1@hermes.cam.ac.uk>); Wed, 06 Jul 2011 17:25:28 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:cet1) id 1QeUum-00087P-L2 (Exim 4.67) (return-path <cet1@hermes.cam.ac.uk>); Wed, 06 Jul 2011 17:25:28 +0100
Received: from [131.111.11.47] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.4); 06 Jul 2011 17:25:28 +0100
Date: 06 Jul 2011 17:25:28 +0100
From: Chris Thompson <cet1@cam.ac.uk>
To: George Barwood <george.barwood@blueyonder.co.uk>
Message-ID: <Prayer.1.3.4.1107061725280.1393@hermes-2.csi.cam.ac.uk>
In-Reply-To: <F48DC712030345AEB66B0F497406D14C@local>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <Prayer.1.3.4.1107052109200.12617@hermes-2.csi.cam.ac.uk> <F48DC712030345AEB66B0F497406D14C@local>
X-Mailer: Prayer v1.3.4
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Chris Thompson <cet1@hermes.cam.ac.uk>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cet1@cam.ac.uk
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, 06 Jul 2011 16:25:30 -0000

On Jul 5 2011, George Barwood wrote:

>The intent is to restrict the ability to update the parent DS to those who have
>access to key signing keys. Thus where there is a split responsibility (similar
>to the root zone where IANA has the KSK private key, and Verisign has only the
>ZSK private key ), only the senior party can update the parent DS.
>The party that only holds the ZSK private key cannot update the parent and
>take over the zone.

OK - maybe I should have thought of that, but I think it does need to be made
clear in the draft.

But it remains the case that not all signed zones have this division of
responsibilities[*], or even have separate KSKs and ZSKs. Maybe this
ought to be a policy matter for each parent-child pair, rather than a
protocol MUST/SHOULD.

[*] and to have them in separate *organisations* is pretty much unique to
    the root zone - where we certainly don't have to worry about how to
    update the DS records in the parent zone :-)

-- 
Chris Thompson               University of Cambridge Computing Service,
Email: cet1@ucs.cam.ac.uk    New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715       United Kingdom.

From peter@denic.de  Wed Jul  6 21:59:31 2011
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 B01E521F899D for <dnsop@ietfa.amsl.com>; Wed,  6 Jul 2011 21:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u3OsWgjYapHZ for <dnsop@ietfa.amsl.com>; Wed,  6 Jul 2011 21:59:31 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id 1C57521F899B for <dnsop@ietf.org>; Wed,  6 Jul 2011 21:59:30 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QeggS-0005im-Si; Thu, 07 Jul 2011 06:59:28 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QeggS-0006KN-OJ; Thu, 07 Jul 2011 06:59:28 +0200
Date: Thu, 7 Jul 2011 06:59:28 +0200
From: Peter Koch <pk@DENIC.DE>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20110707045928.GN10707@x27.adm.denic.de>
References: <20110704154954.GL10707@x27.adm.denic.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110704154954.GL10707@x27.adm.denic.de>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: Re: [DNSOP] DNSOP session scheduled for Quebec (IETF81)
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, 07 Jul 2011 04:59:31 -0000

Dear WG,

> the DNSOP slot for Quebec has been (re-)scheduled to Tuesday, 1300
> <http://tools.ietf.org/agenda/81/#2011-07-28_1300>.  The main agenda is
> still in flux, so the list of parallel sessions may change.

this has now happened.  While we otherwise maintained our slot assignment,
netext was replaced by pcp.

The agenda has been updated at

> 	<http://www.ietf.org/proceedings/81/agenda/dnsop.txt>


-Peter

From matthijs@nlnetlabs.nl  Fri Jul  8 02:52:48 2011
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 E408721F8906 for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 02:52:48 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f-4+LlHRGpW6 for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 02:52:48 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AC57621F861B for <dnsop@ietf.org>; Fri,  8 Jul 2011 02:52:47 -0700 (PDT)
Received: from [192.168.1.13] (ip123-112-174-82.adsl2.static.versatel.nl [82.174.112.123]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p689qi1A094285 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Fri, 8 Jul 2011 11:52:45 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4E16D36C.4090409@nlnetlabs.nl>
Date: Fri, 08 Jul 2011 11:52:44 +0200
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: "'IETF DNSOP WG'" <dnsop@ietf.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Fri, 08 Jul 2011 11:52:46 +0200 (CEST)
Subject: [DNSOP] Fwd: New Version Notification for	draft-mekking-dnsop-dnssec-key-timing-bis-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, 08 Jul 2011 09:52:49 -0000

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

Hi,

I posted a new version of this document. It's a rather small change
compared to the -01, see the rfcdiff:

	http://tools.ietf.org/rfcdiff?url2=draft-mekking-dnsop-dnssec-key-timing-bis-02.txt

I would like to take the opportunity to initiate a discussion on the
differences between the current key-timing document and this proposed
bis document, and ask the wg if they think these differences make sense.

Thanks and regards,
  Matthijs


Key States
- ----------
My biggest concern is, something that I have mentioned repeatedly,
the definition of key states are overloaded. This issue is introduced by
the term "associated information". A good example of that imo is the key
state Published: In some rollover methods it means the DNSKEY record is
published in the zone and in other methods it reflects the publishing of
RRSIG or DS records. However, if RRSIG records are being published, the
key is being used for signing as well. According to the key state
definitions, the key could have been in the state Active as well. I
expect that it will become worse when we try to use the key states to
define STSS/CSK rollovers.

That's why I proposed to unravel the key states, so that the state of
all "associated information" is representated separately. This is
described in section 2.2 of the key-timing-bis document.

The new set of key states are presented in section 2.3. As a consequence
of unraveling the key states, there are now more states,
but their descriptions are more precise.

Key-centric logic vs Rollover-centric logic
- -------------------------------------------
The timelines in the key-timing document show the events in the lifetime
of a key. Those events are different per key type and rollover method.
However, any key rollover can be thought more or less of the same
following sequence of stages. This concept is described in section 3.1.

Instead of showing timelines that follow the the lifetime of a single
key, now the timelines of a single rollover process is shown. The
timeline starts with an already active key and the diagram shows the
steps how that key is being replaced by its successor key.

Additional rollover methods
- ---------------------------
With the new introduced terminology, I have described STSS rollovers
(section 3.4), and started text on Policy rollover (section 4), where
changes in the DNSSEC policy trigger changes to be made in the DNSKEY
RRset. This includes enabling/disabling DNSSEC, Algorithm Rollover and
switching from ZSK-KSK Split signing scheme and STSS. I am aware that
section 4 needs more text.


- -------- Original Message --------
Subject: New Version Notification for
draft-mekking-dnsop-dnssec-key-timing-bis-02.txt
Date: Fri, 08 Jul 2011 02:07:08 -0700
From: internet-drafts@ietf.org
To: matthijs@nlnetlabs.nl
CC: matthijs@nlnetlabs.nl

A new version of I-D, draft-mekking-dnsop-dnssec-key-timing-bis-02.txt
has been successfully submitted by Willem Matthijs Mekking and posted to
the IETF repository.

Filename:	 draft-mekking-dnsop-dnssec-key-timing-bis
Revision:	 02
Title:		 DNSSEC Key Timing Considerations Follow-Up
Creation date:	 2011-07-08
WG ID:		 Individual Submission
Number of pages: 46

Abstract:
   This document describes issues surrounding the timing of events
   related to DNSSEC policy.  It presents timelines for various key
   rollovers and DNSSEC policy changes regarding the key signing scheme.
   It explicitly identifies the relationships between the various
   parameters affecting the rollover process.

   This document updates [draft-ietf-dnsop-dnssec-key-timing] [MM: If
   approved] as it covers timelines for key rollovers in more detail and
   it covers additional key rollover scenarios, including algorithm
   rollover and single type key rollovers.





The IETF Secretariat

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOFtNsAAoJEA8yVCPsQCW59qMH/1SGikfsRJWrw66nfQscGe/1
P+2diVWVwSVj6atk3d6LhBl5AJFBaVKkYr2NR4Ub+ZRQkugcu2XLarjZE13A0uXF
Qse5jhvVJXz6Las6cxnBzrYUlJcNg2ueu2Vq46NP67Lh4eXnjjFJW2wFqbWfzTdg
Cg806XGELnsXQHDtIdvYBnwlZidIZOqVBG2abfeVynbFT39Y3o25rOIo4xluBuEn
F/GII1WJO9YIiUv+hEAHyLbsAeVCn7PWMfN3u09YT2ucmh9wnvod3XNAGYhZdPGF
NLwXDNe7Q2xx6OC5jpmMN+3NLt9qX9N7sZEnyk9OptLpgmy1sEmBQifCpUiMPM0=
=1myT
-----END PGP SIGNATURE-----

From sa.morris7@googlemail.com  Fri Jul  8 11:03:46 2011
Return-Path: <sa.morris7@googlemail.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 3B22321F89EB for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 11:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eNU17Fo-5PFk for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 11:03:45 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id A14D321F8A19 for <dnsop@ietf.org>; Fri,  8 Jul 2011 11:03:44 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1487129wwe.13 for <dnsop@ietf.org>; Fri, 08 Jul 2011 11:03:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=zRMYiU+l2w02Ku87KrH1FupOGR2mnvK3YDaYA7e0TGA=; b=f58RjAwMvEShLUHaFGlutcOzbRj7U4TrcbVAJ9+CuWTh+ZXXuPTSFs062IVomU0gRf hEWyeoiz2GY6DGbGXiGYY5GuFj4AZIYWrx2ycog9t/WOL4+WqXENRpOJCp3FckjhC+IT sk4CFn7ZOemfKsFfj7FWWjUr9PbSt/hwf86LM=
Received: by 10.227.169.139 with SMTP id z11mr2003159wby.60.1310148223822; Fri, 08 Jul 2011 11:03:43 -0700 (PDT)
Received: from stephen-morriss-macbook-pro.local ([217.155.47.50]) by mx.google.com with ESMTPS id gg16sm7876432wbb.34.2011.07.08.11.03.42 (version=SSLv3 cipher=OTHER); Fri, 08 Jul 2011 11:03:42 -0700 (PDT)
Message-ID: <4E17467D.9080409@googlemail.com>
Date: Fri, 08 Jul 2011 19:03:41 +0100
From: Stephen Morris <sa.morris7@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: george.barwood@blueyonder.co.uk
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <4E0C88EA.8050909@googlemail.com> <95A982B76E864EB795A5B322A50EAD32@local>
In-Reply-To: <95A982B76E864EB795A5B322A50EAD32@local>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
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, 08 Jul 2011 18:03:46 -0000

On 30/06/2011 23:33, George Barwood wrote:

> Is the earlier requirements draft from 2005 (linked above) substantially incomplete in some way?
> I think that would be a reasonable basis to measure, I would claim that the CDS
> record is capable of satisfying the requirements expressed there in a natural way. 
> I also think the requirement is actually fairly clear - when implementing KSK rollover,
> you reach a point where it's clear that something is needed ( other than asking
> the operator to start cutting and pasting / interfacing with some out-of-band system / whatever).
> I doubt another cycle of requirements would be productive - we might be here again in 6 years time!

I think Olafur summarised it quite succinctly:

"So maybe we should be having a different discussion:
Does DNSSEC obsolete updating NS and DS information via EPP/Web/Email ?"

If the answer is yes, then the CDS approach is certainly one to be
looked at.  The answer also suggests that we should be looking at an
equivalent mechanism for updating NS (and possibly glue) information in
the parent zone.  Perhaps all can be done under a single framework?

If the answer is no, then along with publishing a mechanism for the
automatic update of DS records, should we be providing guidance on when
to use that and when to use EPP/Web/Email?

Don't get me wrong, I don't want any unnecessary delay.  But if it turns
out that what is being addressed is part of a larger problem, it's worth
looking first to see if there is a general solution.

Stephen

From jabley@hopcount.ca  Fri Jul  8 14:18:51 2011
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 29F8B21F8CCA for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 14:18:51 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9T80Qgc7jdHk for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 14:18:50 -0700 (PDT)
Received: from monster.hopcount.ca (monster.hopcount.ca [IPv6:2001:4900:1:392:213:20ff:fe1b:3bfe]) by ietfa.amsl.com (Postfix) with ESMTP id 90C7A21F8CC7 for <dnsop@ietf.org>; Fri,  8 Jul 2011 14:18:50 -0700 (PDT)
Received: from [2001:4900:1042:100:5a55:caff:feec:96bf] (helo=krill.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1QfIRh-000MkF-2m; Fri, 08 Jul 2011 21:18:45 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <4E17467D.9080409@googlemail.com>
Date: Fri, 8 Jul 2011 17:18:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <78E3D021-A820-488C-B3A3-C5CF4086A83E@hopcount.ca>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <4E0C88EA.8050909@googlemail.com> <95A982B76E864EB795A5B322A50EAD32@local> <4E17467D.9080409@googlemail.com>
To: Stephen Morris <sa.morris7@googlemail.com>
X-Mailer: Apple Mail (2.1084)
X-SA-Exim-Connect-IP: 2001:4900:1042:100:5a55:caff:feec:96bf
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Cc: george.barwood@blueyonder.co.uk, dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
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, 08 Jul 2011 21:18:51 -0000

On 2011-07-08, at 14:03, Stephen Morris wrote:

> If the answer is yes, then the CDS approach is certainly one to be
> looked at.  The answer also suggests that we should be looking at an
> equivalent mechanism for updating NS (and possibly glue) information =
in
> the parent zone.  Perhaps all can be done under a single framework?

If that's the direction we're looking in, then delegation scaffolding =
(NS and DS) seems like just the beginning; perhaps we need to consider =
the possibility of zone managers pushing signed registry ("whois") =
metadata from the DNS back into the registry as well. I'm not convinced =
that's sensible, but it seems helpful to find out how deep the rabbit =
hole goes if we want to properly scope the problem space.

A zone -> registry data flow might at least provide some incentive for =
DNSSEC deployment, if it represented a simplification for the registry =
interaction required by DNS service providers.

On the other hand, if this is an effect a short-cut between registry and =
registrant (or by the registrant's agent, in the case of third-party =
signing/hosting of zones) then we might discover that it's contractually =
infeasible for any gTLD registry to support.

> If the answer is no, then along with publishing a mechanism for the
> automatic update of DS records, should we be providing guidance on =
when
> to use that and when to use EPP/Web/Email?
>=20
> Don't get me wrong, I don't want any unnecessary delay.  But if it =
turns
> out that what is being addressed is part of a larger problem, it's =
worth
> looking first to see if there is a general solution.

+1


Joe


From ogud@ogud.com  Fri Jul  8 15:23:40 2011
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 DC78421F8C60 for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 15:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.51
X-Spam-Level: 
X-Spam-Status: No, score=-106.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pFmWhe-nBuya for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 15:23:40 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB3A21F8AD9 for <dnsop@ietf.org>; Fri,  8 Jul 2011 15:23:40 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p68MNZig091397; Fri, 8 Jul 2011 18:23:35 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4E178365.1010407@ogud.com>
Date: Fri, 08 Jul 2011 18:23:33 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>, dnsop WG <dnsop@ietf.org>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local>	<4E0C88EA.8050909@googlemail.com>	<95A982B76E864EB795A5B322A50EAD32@local>	<4E17467D.9080409@googlemail.com> <78E3D021-A820-488C-B3A3-C5CF4086A83E@hopcount.ca>
In-Reply-To: <78E3D021-A820-488C-B3A3-C5CF4086A83E@hopcount.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
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, 08 Jul 2011 22:23:41 -0000

On 08/07/2011 5:18 PM, Joe Abley wrote:
>
> On 2011-07-08, at 14:03, Stephen Morris wrote:
>
>> If the answer is yes, then the CDS approach is certainly one to be
>> looked at.  The answer also suggests that we should be looking at an
>> equivalent mechanism for updating NS (and possibly glue) information in
>> the parent zone.  Perhaps all can be done under a single framework?
>
> If that's the direction we're looking in, then delegation scaffolding (NS and DS) seems like just the beginning; perhaps we need to consider the possibility of zone managers pushing signed registry ("whois") metadata from the DNS back into the registry as well. I'm not convinced that's sensible, but it seems helpful to find out how deep the rabbit hole goes if we want to properly scope the problem space.

Just let Whois die a peaceful death, it serves no purpose other than 
make work.
>
> A zone ->  registry data flow might at least provide some incentive for DNSSEC deployment, if it represented a simplification for the registry interaction required by DNS service providers.
>
> On the other hand, if this is an effect a short-cut between registry and registrant (or by the registrant's agent, in the case of third-party signing/hosting of zones) then we might discover that it's contractually infeasible for any gTLD registry to support.
>

As I mentioned in my prior post to dnsop,
Parent != Registry in the RRR world.

There is no reason why the registrar can not perform this "scan"
and update the registration information.
The biggest beneficiary in the RRR world is the external DNS operator 
that currently has to funnel DNS information via the registrant.


>> If the answer is no, then along with publishing a mechanism for the
>> automatic update of DS records, should we be providing guidance on when
>> to use that and when to use EPP/Web/Email?
>>
>> Don't get me wrong, I don't want any unnecessary delay.  But if it turns
>> out that what is being addressed is part of a larger problem, it's worth
>> looking first to see if there is a general solution.
>
> +1
>
+1
IMHO this is a no-brainer once we agree on few constraints:
	a) only applies to normal changes
	b) delay of few days/weeks is acceptable

Thus:
	New registration is not covered.
	Emergency operations are not supported
	Transfer is not explicitly supported, but at the same time not prevented.

	Olafur

From jabley@hopcount.ca  Fri Jul  8 16:40:21 2011
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 BCA6921F8C39 for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 16:40:21 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1GXngvt1-7O for <dnsop@ietfa.amsl.com>; Fri,  8 Jul 2011 16:40:21 -0700 (PDT)
Received: from monster.hopcount.ca (monster.hopcount.ca [IPv6:2001:4900:1:392:213:20ff:fe1b:3bfe]) by ietfa.amsl.com (Postfix) with ESMTP id 54ED321F88DD for <dnsop@ietf.org>; Fri,  8 Jul 2011 16:40:21 -0700 (PDT)
Received: from [2001:4900:1042:100:5a55:caff:feec:96bf] (helo=krill.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1QfKeh-000Pkp-Kd; Fri, 08 Jul 2011 23:40:20 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <4E178365.1010407@ogud.com>
Date: Fri, 8 Jul 2011 19:40:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB9FCE27-900E-4C12-8124-0C97B06D3361@hopcount.ca>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local>	<4E0C88EA.8050909@googlemail.com>	<95A982B76E864EB795A5B322A50EAD32@local>	<4E17467D.9080409@googlemail.com> <78E3D021-A820-488C-B3A3-C5CF4086A83E@hopcount.ca> <4E178365.1010407@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1084)
X-SA-Exim-Connect-IP: 2001:4900:1042:100:5a55:caff:feec:96bf
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
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, 08 Jul 2011 23:40:21 -0000

On 2011-07-08, at 18:23, Olafur Gudmundsson wrote:

> Just let Whois die a peaceful death, it serves no purpose other than =
make work.

Other people are working on the death of whois; I was just trying to =
clarify the type of data I was talking about.


Joe


From marc.lampo@eurid.eu  Mon Jul 11 03:02:37 2011
Return-Path: <marc.lampo@eurid.eu>
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 13DBF21F8AB0 for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2011 03:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.736
X-Spam-Level: 
X-Spam-Status: No, score=-6.736 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, MSGID_MULTIPLE_AT=1.449, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qIXhQXhIVFea for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2011 03:02:36 -0700 (PDT)
Received: from barra.eurid.eu (mx.eurid.eu [212.190.206.103]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1E521F88AB for <dnsop@ietf.org>; Mon, 11 Jul 2011 03:02:35 -0700 (PDT)
X-ASG-Debug-ID: 1310378553-0369494a361b740001-lPZdTi
Received: from zimbra.eurid.eu (zcs-master.vt.eurid.eu [10.19.100.121]) by barra.eurid.eu with ESMTP id rknbGiVvVMONfDO3 for <dnsop@ietf.org>; Mon, 11 Jul 2011 12:02:33 +0200 (CEST)
X-Barracuda-Envelope-From: marc.lampo@eurid.eu
X-ASG-Whitelist: Client
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.eurid.eu (Postfix) with ESMTP id 78B76E4054; Mon, 11 Jul 2011 11:51:34 +0200 (CEST)
X-Virus-Scanned: amavisd-new at techmail.eurid.eu
Received: from zimbra.eurid.eu ([127.0.0.1]) by localhost (zimbra.eurid.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9cmfH1YX6Nw; Mon, 11 Jul 2011 11:51:34 +0200 (CEST)
Received: from zimbra.eurid.eu (zimbra.eurid.eu [10.19.100.120]) by zimbra.eurid.eu (Postfix) with ESMTP id 67A8FE4053; Mon, 11 Jul 2011 11:51:34 +0200 (CEST)
From: "Marc Lampo" <marc.lampo@eurid.eu>
To: "'IETF DNSOP WG'" <dnsop@ietf.org>
Date: Mon, 11 Jul 2011 11:51:34 +0200 (CEST)
X-ASG-Orig-Subj: feedback/feelings around : draft-barwood-dnsop-ds-publish-02.txt ?
Message-ID: <020701cc3fb1$a7aa5120$f6fef360$@lampo@eurid.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Mailer: Microsoft Office Outlook 12.0
X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraConnectorForOutlook/5.0.3064.18)
Thread-Index: Acw/sadS7+qdogZOQtGi3tEc1IEEWQ==
Content-Language: en-za
X-Originating-IP: [172.20.1.97]
X-Barracuda-Connect: zcs-master.vt.eurid.eu[10.19.100.121]
X-Barracuda-Start-Time: 1310378553
X-Barracuda-URL: http://172.20.1.190:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at eurid.eu
Cc: 'Marc Lampo' <marc.lampo@eurid.eu>
Subject: [DNSOP] feedback/feelings around : draft-barwood-dnsop-ds-publish-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, 11 Jul 2011 10:02:37 -0000

Dear all,

http://tools.ietf.org/id/draft-barwood-dnsop-ds-publish-02.txt

There does not seem to be a lot of feedback on this draft ?
 (some comments on version 01 only)

Yet, couldn’t this lead to better acceptance of DNSSEC deployment ?

Personally I had two questions/remarks when I (only) just read this version 
:
1) First paragraph of “Usage” :
“Child zone MAY send a NOTIFY message”
→ if this is a regular DNS Notiry message to make a slave check SOA on a 
slave,
     secure configuration of the master would surely block notify messages !
     (the “parent” of a domain is not guaranteed to be slave for it !)
2) “Usage” paragraph 3 : parent should check SEP flag is set.
This would mean only DS’s corresponding to KSK’s can be in the parent zone ?
Isn’t this contradictory with other statements to use only one type of 
DNSKEY ?
(not that I am in favour of that – I already contributed I am not,
 but I accept that some may prefer only one type)

Kind regards,


Marc Lampo
Security Officer

    EURid
    Woluwelaan 150
    1831 Diegem - Belgium
    TEL.: +32 (0) 2 401 3030
    MOB.:+32 (0)476 984 391
    marc.lampo@eurid.eu
    http://www.eurid.eu



Want a .eu web address in your own language? Find out how so you don’t miss 
out!


From internet-drafts@ietf.org  Mon Jul 11 05:07:36 2011
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 13F4921F8B49; Mon, 11 Jul 2011 05:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level: 
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Lf16P0Pgdaj; Mon, 11 Jul 2011 05:07:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A680521F8B20; Mon, 11 Jul 2011 05:07:35 -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: 3.55
Message-ID: <20110711120735.4641.2887.idtracker@ietfa.amsl.com>
Date: Mon, 11 Jul 2011 05:07:35 -0700
Cc: dnsop@ietf.org
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-rfc4641bis-07.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, 11 Jul 2011 12:07:36 -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=
 Group of the IETF.

	Title           : DNSSEC Operational Practices, Version 2
	Author(s)       : Olaf M. Kolkman
	Filename        : draft-ietf-dnsop-rfc4641bis-07.txt
	Pages           : 67
	Date            : 2011-07-11

   This document describes a set of practices for operating the DNS with
   security extensions (DNSSEC).  The target audience is zone
   administrators deploying DNSSEC.

   The document discusses operational aspects of using keys and
   signatures in the DNS.  It discusses issues of key generation, key
   storage, signature generation, key rollover, and related policies.

   This document obsoletes RFC 4641 as it covers more operational ground
   and gives more up-to-date requirements with respect to key sizes and
   the DNSSEC operations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-rfc4641bis-07.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsop-rfc4641bis-07.txt

From matthijs@nlnetlabs.nl  Mon Jul 11 05:16:35 2011
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 EE0B921F8B22 for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2011 05:16:35 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gt5AmZLBaSlx for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2011 05:16:35 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DC16121F8B1E for <dnsop@ietf.org>; Mon, 11 Jul 2011 05:16:34 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:219:d1ff:feb1:85e8] (zoidberg.nlnetlabs.nl [IPv6:2001:7b8:206:1:219:d1ff:feb1:85e8]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p6BCGXMZ072598 for <dnsop@ietf.org>; Mon, 11 Jul 2011 14:16:33 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Message-ID: <4E1AE9A1.4040107@nlnetlabs.nl>
Date: Mon, 11 Jul 2011 14:16:33 +0200
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20110711120735.4641.2887.idtracker@ietfa.amsl.com>
In-Reply-To: <20110711120735.4641.2887.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Mon, 11 Jul 2011 14:16:33 +0200 (CEST)
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-rfc4641bis-07.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, 11 Jul 2011 12:16:36 -0000

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

Hi,

I have posted a -07 version of draft-ietf-dnsop-rfc4641bis that
incorporates the comments received during the WGLC.
The changelog can be viewed in section D.8. The rfcdiff:


http://tools.ietf.org/rfcdiff?url2=http://tools.ietf.org/id/draft-ietf-dnsop-rfc4641bis-07.txt

Most important changes are:
- - Some more clarifying text in 4.1.4. Rollover for a Single Type Signing
Key rollover.
- - Some more clarifyint text in  4.3.5.1. Cooperating DNS operators.
- - Editorial changes in the Rollover Figures.

I would like to ask the reviewers to take a look at the rfcdiff and tell
if they could live with these changes.
In other words, do you think the changes are in line with the outcome of
the discussion on the mailing list?

Thanks,

Matthijs


On 07/11/2011 02:07 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations Working Group of the IETF.
> 
> 	Title           : DNSSEC Operational Practices, Version 2
> 	Author(s)       : Olaf M. Kolkman
> 	Filename        : draft-ietf-dnsop-rfc4641bis-07.txt
> 	Pages           : 67
> 	Date            : 2011-07-11
> 
>    This document describes a set of practices for operating the DNS with
>    security extensions (DNSSEC).  The target audience is zone
>    administrators deploying DNSSEC.
> 
>    The document discusses operational aspects of using keys and
>    signatures in the DNS.  It discusses issues of key generation, key
>    storage, signature generation, key rollover, and related policies.
> 
>    This document obsoletes RFC 4641 as it covers more operational ground
>    and gives more up-to-date requirements with respect to key sizes and
>    the DNSSEC operations.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-dnsop-rfc4641bis-07.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsop-rfc4641bis-07.txt
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOGumhAAoJEA8yVCPsQCW5g6sIAKJxzZlOOGTi9d3XmdCriTUg
sHwUgyf6crPfV6k4uXE0ZtUjh2uPI8tj3OoJLI25S5UxTrt2MirEZappRCDExsf4
f/WM713/Zq6fCU3WFGTaODWLFSWNik45Pn5WYX5vvw2CbU0KRfH2W1M51/tBf7Wr
RpiaCJGxA9P/Zw1H2wWmLDbPTmvAq8og/hkRAqR08/kAOt+W/sd0tR/3E9SVxK6y
HlPHM3g7cQihexQuWdXdrfM1soVN/kWCBHra1TjTj9HN1AyaNTgiI3t6nxSg/dwg
oNv1UJK7+77QXME7t5uDb9BljYFi3JAT5KHoCYhuaj7jI5d0/AV5l6aQjtmFh6c=
=T58u
-----END PGP SIGNATURE-----

From yngve@opera.com  Mon Jul 11 15:23:51 2011
Return-Path: <yngve@opera.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 4E63811E8334 for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2011 15:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMnd3dXYYb7S for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2011 15:23:49 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id A7EE711E8327 for <dnsop@ietf.org>; Mon, 11 Jul 2011 15:23:48 -0700 (PDT)
Received: from acorna.invalid.invalid (211.133.189.109.customer.cdi.no [109.189.133.211]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p6BMNhb8000990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dnsop@ietf.org>; Mon, 11 Jul 2011 22:23:47 GMT
Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes
References: <20110711213847.10149.73731.idtracker@ietfa.amsl.com>
Date: Tue, 12 Jul 2011 00:23:45 +0200
To: "dnsop@ietf.org" <dnsop@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Yngve N. Pettersen (Developer Opera Software ASA)" <yngve@opera.com>
Organization: Opera Software AS
Message-ID: <op.vyg65vlkqrq7tp@acorna.invalid.invalid>
In-Reply-To: <20110711213847.10149.73731.idtracker@ietfa.amsl.com>
User-Agent: Opera Mail/10.63 (Win32)
Subject: [DNSOP] Fwd: New Version Notification for draft-pettersen-subtld-structure-08.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, 11 Jul 2011 22:23:51 -0000

Hi,

This is a slightly refocused version of my earlier draft, now focusing on  
defining "Public Suffix", as it is used in RFC 6265

------- Forwarded message -------
From: internet-drafts@ietf.org
To: yngve@opera.com
Cc: yngve@opera.com
Subject: New Version Notification for  
draft-pettersen-subtld-structure-08.txt
Date: Mon, 11 Jul 2011 23:38:47 +0200

A new version of I-D, draft-pettersen-subtld-structure-08.txt has been
successfully submitted by Yngve Pettersen and posted to the IETF
repository.

Filename:	 draft-pettersen-subtld-structure
Revision:	 08
Title:		 The Public Suffix Structure file format and its use for Cookie
domain validation
Creation date:	 2011-07-11
WG ID:		 Individual Submission
Number of pages: 15

Abstract:
     This document defines the term "Public Suffix" as meaning a domain
     under which multiple parties that are unaffiliated with the owner may
     register subdomains.  Examples of Public Suffixes include "org",
     "co.uk" and "k12.wa.us".  It also defines a fileformat that can be
     used to distribute information about such Public Suffixes to relying
     parties.  As an example, this information is then used to limit which
     domains an Internet service can set cookies for, strengthening the
     rules already defined by the cookie specifications.  This
     specification updates RFC 6265 [RFC6265] by defining the term
     "Public Suffix".



The IETF Secretariat


-- 
Sincerely,
Yngve N. Pettersen
********************************************************************
Senior Developer		     Email: yngve@opera.com
Opera Software ASA                   http://www.opera.com/
Phone:  +47 23 69 32 60              Fax:    +47 23 69 24 01
********************************************************************

From Ed.Lewis@neustar.biz  Tue Jul 12 08:06:50 2011
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 99E5921F84DD for <dnsop@ietfa.amsl.com>; Tue, 12 Jul 2011 08:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.932
X-Spam-Level: 
X-Spam-Status: No, score=-106.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tNOQKxwAx6xw for <dnsop@ietfa.amsl.com>; Tue, 12 Jul 2011 08:06:49 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5BADB21F8F70 for <dnsop@ietf.org>; Tue, 12 Jul 2011 08:06:46 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p6CF6aif023959; Tue, 12 Jul 2011 11:06:37 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.201.21] by Work-Laptop-2.local (PGP Universal service); Tue, 12 Jul 2011 11:06:38 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Tue, 12 Jul 2011 11:06:38 -0400
Mime-Version: 1.0
Message-Id: <a06240800ca41ffe6894f@[192.168.1.108]>
In-Reply-To: <4E17467D.9080409@googlemail.com>
References: <3C049373F5284CB7BCD4BEAA0EF0D0DE@local> <4E0C88EA.8050909@googlemail.com> <95A982B76E864EB795A5B322A50EAD32@local> <4E17467D.9080409@googlemail.com>
Date: Tue, 12 Jul 2011 11:05:39 -0400
To: Stephen Morris <sa.morris7@googlemail.com>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: george.barwood@blueyonder.co.uk, dnsop@ietf.org
Subject: Re: [DNSOP] CDS RRtype - automated KSK rollover
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, 12 Jul 2011 15:06:50 -0000

At 19:03 +0100 7/8/11, Stephen Morris wrote:

>Don't get me wrong, I don't want any unnecessary delay.  But if it turns
>out that what is being addressed is part of a larger problem, it's worth
>looking first to see if there is a general solution.

I sent a response to the chairs and to George earlier because, and 
I'll explain, I've been purposely ignoring the CDS proposal.  After a 
quick back and forth, I figured I should post to the list.

I have been ignoring CDS because both of the angles I have on DNS 
would find record to be useless.  I do not feel it is worthwhile to 
suppress work in the IETF that is of no consequence, so I haven't 
objected.

My angles include ICANN contracted TLD operator and a managed DNS 
provider.  In the former, we have to address the Shared Registry 
Model whether it is universal or not.  As a managed DNS provider, we 
don't have to beckon to the SRM but the (what I estimate to be) vast 
majority of our customers do.

I understand that my angles are not the only ones.  There are 
situations in which an direct parent-child exchange of information 
makes sense.  But it doesn't for me and doesn't for, I'll put it this 
way, a significant portion of the domain name management market.

A snide person would ask "does the IETF want to invent cool gadgets 
or useful gadgets?"  Cool would be something that is direct, useful 
is something that is acceptable to the SRM.

One more caveat.  It's not an open-and-shut case that CDS would be 
"in violation" of the SRM.  Perhaps a direct parent-child solution 
could be hammered out.  But given other priorities, I just have spent 
any time on CDS because I think it is unlikely.

I don't believe we need a single, one-size fits all solution.  I 
think that sometimes that goal is a huge deterrent in finding a 
workable set of solutions.

These are two questions asked in a side conversation and figured I 
might as reply on the list.

>(a) if a child zone requests through the proper channels that its DS
>record in the parent be updated, under what circumstances would the
>parent refuse the update?

Authorization checks failing.  I don't have specifics, but 
conventional wisdom holds that if a registrar tries to designate a 
dns operator with a registry, things still don't work so well. 
Perhaps it's an industry legend, but I think there are folks 
reluctant to try this.

>(b) could publication of a CDS record in a signed child zone constitute
>an authorised request?

I kind of doubt that the practice would be accepted widely.

There's a wide array of concerns in running registries.  In some, 
tracking transactions is one, so that any changes can be audited.  In 
these, one would pretty much be forced to funnel all requests into 
one channel for tagging.  Out of band communications (relative to the 
registry) would be discouraged.

What I've posted are general, fuzzy, hand-waving reasons why CDS 
wouldn't be a general solution.  Arguing the other way, that CDS 
would be general, is like arguing a negative which is fraught with 
logic problems.  This is why I wouldn't fight "against" CDS but just 
won't dedicate time to examine it closely.

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

I'm overly entertained.

From wwwrun@rfc-editor.org  Wed Jul 13 17:58:42 2011
Return-Path: <wwwrun@rfc-editor.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 A4AF311E81EA; Wed, 13 Jul 2011 17:58:42 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fp-glOLssN7J; Wed, 13 Jul 2011 17:58:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEBD11E81BC; Wed, 13 Jul 2011 17:58:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 268B898C542; Wed, 13 Jul 2011 17:58:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110714005836.268B898C542@rfc-editor.org>
Date: Wed, 13 Jul 2011 17:58:35 -0700 (PDT)
Cc: dnsop@ietf.org, rfc-editor@rfc-editor.org
Subject: [DNSOP] BCP 163, RFC 6303 on Locally Served DNS Zones
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, 14 Jul 2011 00:58:42 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 163        
        RFC 6303

        Title:      Locally Served DNS Zones 
        Author:     M. Andrews
        Status:     Best Current Practice
        Stream:     IETF
        Date:       July 2011
        Mailbox:    marka@isc.org
        Pages:      10
        Characters: 22503
        See Also:   BCP0163

        I-D Tag:    draft-ietf-dnsop-default-local-zones-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6303.txt

Experience with the Domain Name System (DNS) has shown that there are
a number of DNS zones that all iterative resolvers and recursive
nameservers should automatically serve, unless configured otherwise.
RFC 4193 specifies that this should occur for D.F.IP6.ARPA.  This
document extends the practice to cover the IN-ADDR.ARPA zones for RFC
1918 address space and other well-known zones with similar
characteristics.  This memo documents an Internet Best Current Practice.

This document is a product of the Domain Name System Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Wed Jul 13 17:58:57 2011
Return-Path: <wwwrun@rfc-editor.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 6070611E8092; Wed, 13 Jul 2011 17:58:57 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0UQ9BBlAyOTs; Wed, 13 Jul 2011 17:58:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id CDF5311E81F1; Wed, 13 Jul 2011 17:58:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AB2C998C549; Wed, 13 Jul 2011 17:58:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110714005852.AB2C998C549@rfc-editor.org>
Date: Wed, 13 Jul 2011 17:58:52 -0700 (PDT)
Cc: dnsop@ietf.org, rfc-editor@rfc-editor.org
Subject: [DNSOP] RFC 6304 on AS112 Nameserver Operations
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, 14 Jul 2011 00:58:57 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6304

        Title:      AS112 Nameserver Operations 
        Author:     J. Abley, W. Maton
        Status:     Informational
        Stream:     IETF
        Date:       July 2011
        Mailbox:    joe.abley@icann.org, 
                    wmaton@ryouko.imsb.nrc.ca
        Pages:      18
        Characters: 34002
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-as112-ops-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6304.txt

Many sites connected to the Internet make use of IPv4 addresses that
are not globally unique.  Examples are the addresses designated in
RFC 1918 for private use within individual sites.

Devices in such environments may occasionally originate Domain Name
System (DNS) queries (so-called "reverse lookups") corresponding to
those private-use addresses.  Since the addresses concerned have only
local significance, it is good practice for site administrators to
ensure that such queries are answered locally.  However, it is not
uncommon for such queries to follow the normal delegation path in the
public DNS instead of being answered within the site.

It is not possible for public DNS servers to give useful answers to
such queries.  In addition, due to the wide deployment of private-use
addresses and the continuing growth of the Internet, the volume of
such queries is large and growing.  The AS112 project aims to provide
a distributed sink for such queries in order to reduce the load on
the IN-ADDR.ARPA authoritative servers.  The AS112 project is named
after the Autonomous System Number (ASN) that was assigned to it.

This document describes the steps required to install a new AS112
node and offers advice relating to such a node's operation.  This 
document is not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product of the Domain Name System Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Wed Jul 13 17:59:18 2011
Return-Path: <wwwrun@rfc-editor.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 31C151F0C5E; Wed, 13 Jul 2011 17:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.211
X-Spam-Level: 
X-Spam-Status: No, score=-104.211 tagged_above=-999 required=5 tests=[AWL=1.465, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DV+OPqYbWeP8; Wed, 13 Jul 2011 17:59:14 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [64.170.98.47]) by ietfa.amsl.com (Postfix) with ESMTP id 88AE821F8895; Wed, 13 Jul 2011 17:59:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 72E7198C553; Wed, 13 Jul 2011 17:59:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110714005908.72E7198C553@rfc-editor.org>
Date: Wed, 13 Jul 2011 17:59:08 -0700 (PDT)
Cc: dnsop@ietf.org, rfc-editor@rfc-editor.org
Subject: [DNSOP] RFC 6305 on I'm Being Attacked by PRISONER.IANA.ORG!
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, 14 Jul 2011 00:59:18 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6305

        Title:      I'm Being Attacked by PRISONER.IANA.ORG! 
        Author:     J. Abley, W. Maton
        Status:     Informational
        Stream:     IETF
        Date:       July 2011
        Mailbox:    joe.abley@icann.org, 
                    wmaton@ryouko.imsb.nrc.ca
        Pages:      8
        Characters: 15287
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-as112-under-attack-help-help-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6305.txt

Many sites connected to the Internet make use of IPv4 addresses that
are not globally unique.  Examples are the addresses designated in
RFC 1918 for private use within individual sites.

Hosts should never normally send DNS reverse-mapping queries for
those addresses on the public Internet.  However, such queries are
frequently observed.  Authoritative servers are deployed to provide
authoritative answers to such queries as part of a loosely
coordinated effort known as the AS112 project.

Since queries sent to AS112 servers are usually not intentional, the
replies received back from those servers are typically unexpected.
Unexpected inbound traffic can trigger alarms on intrusion detection
systems and firewalls, and operators of such systems often mistakenly
believe that they are being attacked.

This document provides background information and technical advice to
those firewall operators.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

This document is a product of the Domain Name System Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From peter@denic.de  Thu Jul 14 09:02:52 2011
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 B3EED21F8CC6 for <dnsop@ietfa.amsl.com>; Thu, 14 Jul 2011 09:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gP5SYhlPt8j for <dnsop@ietfa.amsl.com>; Thu, 14 Jul 2011 09:02:52 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id A9C8021F8CF4 for <dnsop@ietf.org>; Thu, 14 Jul 2011 09:02:51 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QhONG-00030O-3d; Thu, 14 Jul 2011 18:02:50 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QhONG-0000k9-05; Thu, 14 Jul 2011 18:02:50 +0200
Date: Thu, 14 Jul 2011 18:02:49 +0200
From: Peter Koch <pk@DENIC.DE>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20110714160249.GC29765@x27.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] AS112/local zones documents published -- and next steps
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, 14 Jul 2011 16:02:52 -0000

Dear WG,

with the recent advent of

        RFC 6303, Locally Served DNS Zones       [BCP0163]
        RFC 6304, AS112 Nameserver Operations
        RFC 6305, I'm Being Attacked by PRISONER.IANA.ORG!

I'd like to express thanks for the hard work to Mark, Joe, and William as the
editors of these three documents and everybody involved in getting these
reviewed and published.

While the first RFC received BCP status as desired, RFC 6305, intended
for end user consumption, did not make it to FYI. The reason is that during
processing the IESG decided to refrain from issuing new FYI numbers.
Discussion of the conclusion of the FYI series is happening on the RFC-Interest
and the main IETF lists.
Still, the document will be a useful reference to point concerned operators
to, independent of formal status.

With the trilogy published, there is new work in front of us.  Stephen and
me have reserved space on the Quebec agenda for a closer look at

        <draft-michaelson-as112-ipv6-00.txt>
        <draft-sotomayor-as112-ipv4-cull-00.txt>

Both drafts strive to extend the AS112 service and we'd like to ask for
reviews here.  The audience in Prague was already sympathetic to George's
and Geoff's proposal, but it seems prudent to look into this in a combined
way and then distribute or combine work as appropriate.  Please help
getting things forward by reviewing the documents and making suggestions
for how to address the topic.

-Peter

From jabley@hopcount.ca  Thu Jul 14 10:53:46 2011
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 E438611E80A8 for <dnsop@ietfa.amsl.com>; Thu, 14 Jul 2011 10:53:46 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEXxYD8z8-Hq for <dnsop@ietfa.amsl.com>; Thu, 14 Jul 2011 10:53:42 -0700 (PDT)
Received: from monster.hopcount.ca (monster.hopcount.ca [IPv6:2001:4900:1:392:213:20ff:fe1b:3bfe]) by ietfa.amsl.com (Postfix) with ESMTP id B673911E8098 for <dnsop@ietf.org>; Thu, 14 Jul 2011 10:53:41 -0700 (PDT)
Received: from [2001:4900:1042:100:5a55:caff:feec:96bf] (helo=krill.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1QhQ6T-000D90-Jj; Thu, 14 Jul 2011 17:53:39 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20110714160249.GC29765@x27.adm.denic.de>
Date: Thu, 14 Jul 2011 13:53:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB4B3E98-26E8-4B95-89F1-1D2BB79003F6@hopcount.ca>
References: <20110714160249.GC29765@x27.adm.denic.de>
To: Peter Koch <pk@DENIC.DE>
X-Mailer: Apple Mail (2.1084)
X-SA-Exim-Connect-IP: 2001:4900:1042:100:5a55:caff:feec:96bf
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] AS112/local zones documents published -- and next steps
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, 14 Jul 2011 17:53:47 -0000

On 2011-07-14, at 12:02, Peter Koch wrote:

> With the trilogy published, there is new work in front of us.  Stephen =
and
> me have reserved space on the Quebec agenda for a closer look at
>=20
>        <draft-michaelson-as112-ipv6-00.txt>

So, it seems to me that there are various aspects to consider in the =
general area of extending the AS112 project for IPv6. These include:

 (a) IPv6 transport for AS112 nameservers (some work is already being =
done on this)
 (b) Inclusion of IPv6-related RFC6303-style zones on AS112 servers

The open issues on ggm's draft I think include:

 (1) whether this is the right draft to document (a) above
 (2) whether the list of zones specified is complete and accurate

In addition to these process questions there are some improvements that =
I could think be made to the IANA Considerations section, but those are =
largely editorial and non-substantive in this context.

(b) and (2) above also prompt the question of how we (more generally) =
might manage the zones served by AS112 nodes, given that there is only =
loose coordination between AS112 node operators and potentially a =
significant deployment of (globally) invisible AS112 nodes which serve =
captive audiences (enterprises, ISPs own customers, etc). There is a =
risk, depending on the update mechanism, that additional zones delegated =
to the existing AS112 servers might be lame on a significant number of =
servers, and the impact of that lameness ought to be assessed.

>        <draft-sotomayor-as112-ipv4-cull-00.txt>

wfm's draft (above) contains an analogous proposal to (b) above, but for =
various new v4-related reverse zones.

In addition we now have a registry of locally-served zones, per RFC6303, =
and we might consider mechanisms to update AS112 nodes from that =
registry (or constrain the procedures for updating that registry also to =
consider AS112 support for the zones, as they are added).

Finally, Stuart Cheshire's draft draft-cheshire-dnsext-special-names-01 =
proposes the creation of a registry of special-use names, and =
draft-cheshire-dnsext-multicastdns-14 requests that that the IANA =
reserves other domains such as ".local" and "254.169.in-addr.arpa" which =
(like the zones currently delegated to the AS112 servers) have only =
local significance.

It feels like there's an opportunity here to align these various =
registries and knit in some process relating to the AS112 project. What =
exists right now, together with what is proposed to exist, is a little =
messy.


Joe=

From regnauld@bluepipe.net  Fri Jul 15 08:40:26 2011
Return-Path: <regnauld@bluepipe.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 9426821F888A for <dnsop@ietfa.amsl.com>; Fri, 15 Jul 2011 08:40:26 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szx1en++SwOO for <dnsop@ietfa.amsl.com>; Fri, 15 Jul 2011 08:40:26 -0700 (PDT)
Received: from moof.catpipe.net (moof.catpipe.net [194.28.252.64]) by ietfa.amsl.com (Postfix) with ESMTP id EA39A21F8893 for <dnsop@ietf.org>; Fri, 15 Jul 2011 08:40:25 -0700 (PDT)
Received: from localhost (moof.catpipe.net [194.28.252.64]) by localhost.catpipe.net (Postfix) with ESMTP id 917E04D1CFF; Fri, 15 Jul 2011 17:40:23 +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 YvaJ8gd+M6Mj; Fri, 15 Jul 2011 17:40:23 +0200 (CEST)
Received: from macbook.catpipe.net (flow.bluepipe.dk [195.249.214.179]) (Authenticated sender: relayuser) by moof.catpipe.net (Postfix) with ESMTPA id C78924D1B98; Fri, 15 Jul 2011 17:40:22 +0200 (CEST)
Received: by macbook.catpipe.net (Postfix, from userid 1001) id 569BA403D4ED; Fri, 15 Jul 2011 17:40:22 +0200 (CEST)
Date: Fri, 15 Jul 2011 17:40:22 +0200
From: Phil Regnauld <regnauld@nsrc.org>
To: Joe Abley <jabley@hopcount.ca>
Message-ID: <20110715154022.GI13810@macbook.catpipe.net>
References: <20110714160249.GC29765@x27.adm.denic.de> <FB4B3E98-26E8-4B95-89F1-1D2BB79003F6@hopcount.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FB4B3E98-26E8-4B95-89F1-1D2BB79003F6@hopcount.ca>
X-Operating-System: Darwin 10.8.0 i386
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] AS112/local zones documents published -- and next steps
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, 15 Jul 2011 15:40:26 -0000

Joe Abley (jabley) writes:
> 
>  (b) Inclusion of IPv6-related RFC6303-style zones on AS112 servers
>  (2) whether the list of zones specified is complete and accurate

	[...]

> (b) and (2) above also prompt the question of how we (more generally)
> might manage the zones served by AS112 nodes, given that there is
> only loose coordination between AS112 node operators and potentially
> a significant deployment of (globally) invisible AS112 nodes which
> serve captive audiences (enterprises, ISPs own customers, etc).

	... all of whom may have a voluntarily incomplete implementation
	of AS112 zones on, or upstream of, their recursive servers - not
	the least because they may themselves be using the networks that
	the reverse zones provide reverse information for.

> There is a risk, depending on the update mechanism, that additional
> zones delegated to the existing AS112 servers might be lame on a
> significant number of servers, and the impact of that lameness ought
> to be assessed.

	With regards to private AS112 announcement leaking from these
	servers ?  Or did you have other things in mind ?
	Would make sense to dig a bit deeper on the effect.

> In addition we now have a registry of locally-served zones, per
> RFC6303, and we might consider mechanisms to update AS112 nodes from
> that registry (or constrain the procedures for updating that registry
> also to consider AS112 support for the zones, as they are added).

	Got any ideas on that front already ?  And, where would the the "official"
	list of locally-served zones reside ?  draft-cheshire-dnsext-special-names-01
	suggest that "IANA needs to create a new registry of Special-Use Domain
	Names."

> It feels like there's an opportunity here to align these various
> registries and knit in some process relating to the AS112 project.
> What exists right now, together with what is proposed to exist, is a
> little messy.

	Sounds like a plan :)

From peter@denic.de  Tue Jul 19 02:23:57 2011
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 3F96421F8784 for <dnsop@ietfa.amsl.com>; Tue, 19 Jul 2011 02:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.51
X-Spam-Level: 
X-Spam-Status: No, score=-2.51 tagged_above=-999 required=5 tests=[AWL=0.089,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v5yu3XmG899T for <dnsop@ietfa.amsl.com>; Tue, 19 Jul 2011 02:23:53 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id B16C321F8764 for <dnsop@ietf.org>; Tue, 19 Jul 2011 02:23:52 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1Qj6Wt-0003lA-8M; Tue, 19 Jul 2011 11:23:51 +0200
Received: from localhost by x27.adm.denic.de with local  id 1Qj6Wt-0002HJ-4o; Tue, 19 Jul 2011 11:23:51 +0200
Date: Tue, 19 Jul 2011 11:23:51 +0200
From: Peter Koch <pk@DENIC.DE>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20110719092351.GK30334@x27.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] Final Draft Agenda for Quebec/IETF 81
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, 19 Jul 2011 09:23:57 -0000

Dear WG,

the agenda at <http://www.ietf.org/proceedings/81/agenda/dnsop.txt>
has been updated to what you find further down in this message (for
archival purposes).

Best regards,
  Peter and Stephen

-----------------------------------------------------------------------------
WG:        DNS Operations (dnsop)
Meeting:   IETF 81, Quebec
Location:  Quebec City Convention Centre, 206A
Date:      Tuesday, 28 July 2011
Time:      13:00 - 15:00 (UTC-4)	// alto, emu, netmod, paws, pcp, pim, rtcweb
Chairs:	   Peter Koch     <pk@denic.de>      <pk@isoc.de>
	   Stephen Morris <stephen@isc.org>  <sa.morris7@googlemail.com>>
Jabber:    xmpp:dnsop@jabber.ietf.org
WG URL:    http://tools.ietf.org/wg/dnsop/
WG URL:    https://datatracker.ietf.org/wg/dnsop/
Agenda:    http://tools.ietf.org/agenda/81/#dnsop
Agenda:    https://datatracker.ietf.org/meeting/81/agenda.html#dnsop
Agenda:    http://www.ietf.org/proceedings/81/agenda/dnsop.txt
Material:  https://datatracker.ietf.org/meeting/81/materials.html#wg-dnsop
Version:   $Revision: 1.4 $
-----------------------------------------------------------------------------

1) Administrivia
   [chairs][5 min][13:00]
   <http://www.ietf.org/proceedings/81/slides/dnsop-0.pdf>

   - minutes scribe	{volunteers welcome in advance!}
   - jabber scribe	{volunteers welcome in advance!}
   - blue sheets
   - agenda bashing

2) Status Update
   [chairs][5 min][13:05]
   Status will be distributed to the mailing list

3) Active Drafts
   [chairs][15 min][13:10]

   3.1) <draft-ietf-dnsop-rfc4641bis-07.txt>		[5 min]
	little support/review during WGLC
	issues resolved in -07

   3.2) <draft-ietf-dnsop-dnssec-dps-framework-04.txt>	[5 min]
	>5 people voiced support
	issues raised, -05 version needed
	will be updated after Quebec
	scheduled for "publication request" in Sep
	
   3.3) <draft-ietf-dnsop-dnssec-key-timing-02.txt>	[3 min]
	editors will publish -03 after the meeting
	apparently ready for WGLC

   3.4) <draft-ietf-dnsop-respsize-12.txt>		[2 min]
	needs new review and WGLC

4) Other (non WG) Internet-Drafts
   [chairs][45 min][13:25]

   4.1) AS112 future work, preliminary reading list	[15 min]
        <draft-michaelson-as112-ipv6-00.txt>
        <draft-sotomayor-as112-ipv4-cull-00.txt>

   4.2) Key timing future work				[15 min]
        <draft-mekking-dnsop-dnssec-key-timing-bis-02.txt>

   4.3)  Automated KSK rollover support problem statement,	[15 min]
	 pending mailing list discussion
         <http://www.ietf.org/mail-archive/web/dnsop/current/msg09137.html>
   
5) Future WG direction
   [chairs][15 min][14:10]

   See additional mail to the WG list

6) I/O with other WGs
   [chairs][5 min][14:25]

   No slot assigned, but wg attendees may want to review these:

   o Homenet (aka "fun") with a draft charter discussed in a thread starting
     at <http://www.ietf.org/mail-archive/web/fun/current/msg00002.html>

   o Repute
     <http://www.blackops.org/~msk/domainrep/repute-charter.txt>

7) A.O.B.
   [N.N.][0 min][14:30]

   {please identify additional issues in advance}

-----------------------------------------------------------------------------

From peter@denic.de  Tue Jul 19 09:06:01 2011
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 2ABC65E8003 for <dnsop@ietfa.amsl.com>; Tue, 19 Jul 2011 09:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2phLqAt+3b8 for <dnsop@ietfa.amsl.com>; Tue, 19 Jul 2011 09:06:00 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id 94A221F0C3A for <dnsop@ietf.org>; Tue, 19 Jul 2011 09:05:59 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QjCo1-0006D9-DA; Tue, 19 Jul 2011 18:05:57 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QjCo1-0008Jc-9P; Tue, 19 Jul 2011 18:05:57 +0200
Date: Tue, 19 Jul 2011 18:05:57 +0200
From: Peter Koch <pk@DENIC.DE>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20110719160557.GD25368@x27.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] DNSOP future direction (agenda item 5 for Quebec)
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, 19 Jul 2011 16:06:01 -0000

Dear WG,

With four, admittedly long lasting, drafts now published as RFCs
and several others in or approaching WGLC, it is time to look at
the remaining action items or milestones for the DNSOP WG.
Your chairs would like to devote some time in Quebec to gauge
interest in future work. We'd like to identify DNS operations related
topics that would call for IETF action _and_ can get enough traction for
something to be delivered.

So, here are topics that have been raised in the recent or not so
recent past, in no particular order:

o AS112 next steps
  The AS112 operations community, supported by OARC, is thinking about
  expansion in the direction of IPv6 and automated adjustments to the
  list of zones served by the AS112 nodes

o Trust history
  See recent discussion on the list.

o Child-/Parent- Key (Material) exchange
  Also recently reappeared in the form of a concrete proposal for a solution.
  Most of the problem descriptions and/or solutions have in common that
  the signalling and/or data transport happens in-band as opposed to through
  a dedicated provisioning protocol.
 
o DNS Operator Change under DNSSEC
  Apparently identified as a real world problem in the registry-registrar-
  operator world, part of this has been addressed in RFC4641bis. Part of
  the solution might be more a provisioning protocol issue than a DNS one.

o A/AAAA multiple queries issue
  Over the years several suggestions have been made to optimize the lookup
  of A and AAAA RRs for the same QNAME in an attempt to ease or encourage
  IPv6 deployment.  While protocol changes haven't found support (and are
  out of the scope of DNSOP), it was often enough challenged that there
  was a problem in the first place.  Is there room or need to document
  current practice and the affect on resolution and server infrastructure?

o Updating RFC 1912
  RFC 1912 has been a landmark in documenting operational issues and is
  believed to carry the primary reference to what a "lame delegation" is,
  amongst other useful things.  However, since its publication the
  DNS operational environment has made significant progress that might
  
o Benchmarking and Performance Measurements
  Measurements of DNS server software usually report "queries per second"
  values to judge speed and performance. However, there is no agreed upon
  set of queries, neither for authoritative nor for recursive servers.

o Operational Reality Check for use of DNS in other protocols
  Several protocols, mostly in the applications area, make, sometimes tacit,
  assumptions about the DNS, the way "a domain" works or the proximity of
  "domains" and "networks".  Review, Guidance or Reacting to operational
  challenges might be future routes.

o DNS "Signing as a Service"
  Multiple vendors have started to announce DNSSEC signing services for
  remote DNSSEC zones, including fetching and pushing zones from and to
  the customers' DNS infrastructure and also including key management
  and key material handling (in the direction of the parent). Is there
  demand for standardization and how much of this is a DNS rather than
  a provisioning issue?

o Name Server Control Protocol
  Work addressing the requirements as discussed in RFC 6168.

Please take this as food for thought, not as an exhaustive list or work
proposal. All items would have to pass the admission tests:

0) Is there a problem to solve (or document)?
1) Is there enough momentum to get work done?
   This includes both editors _and_ reviewers!
2) Is there a reasonable chance to reach consensus while still having
   a useful result?
3) Is the work item in scope for the IETF and DNSOP?

Looking forward to a lively discussion in Quebec!

-Peter and Stephen

From Antoin.Verschuren@sidn.nl  Thu Jul 21 03:50:42 2011
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 CB35A21F8B18 for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 03:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.504
X-Spam-Level: 
X-Spam-Status: No, score=-4.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4D7j+X5ZMBRi for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 03:50:41 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [94.198.152.69]) by ietfa.amsl.com (Postfix) with ESMTP id E0E9521F8B16 for <dnsop@ietf.org>; Thu, 21 Jul 2011 03:50:38 -0700 (PDT)
Received: from KAHUBCAS1.SIDN.local ([192.168.2.41]) by ede1-kamx.sidn.nl  with ESMTP id p6LAoasa004301 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=CAFAIL) for <dnsop@ietf.org>; Thu, 21 Jul 2011 12:50:36 +0200
Received: from [192.168.129.125] (192.168.129.125) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.1.289.1; Thu, 21 Jul 2011 12:50:36 +0200
Message-ID: <4E28047E.9050103@sidn.nl>
Date: Thu, 21 Jul 2011 12:50:38 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: <dnsop@ietf.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [192.168.129.125]
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-rfc4641bis-07.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, 21 Jul 2011 10:50:43 -0000

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

Unfortunately I deleted the original email message so I lost the thread,
but I'd like to state I read version 07 of the 4641bis draft, and I can
live with the changes made to the document.
I have no further comments.

See you in Quebec,

- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Utrechtseweg 310, 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/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJOKAR+AAoJEDqHrM883Agn0Q8H/0iRVqv0Tv3Po2Wp4Um4ZtSQ
E3H5jxnUI+YTz1c/XhWiCrBjrzoMjrCyAdExnL5xG9CJc0/qxFFy6jtlKeiDKJHR
GA6bdO3MfSSiGzXasA4430TMhlHM5M1YdKrmUVti9ThVOA4x15ZK0r47j1VvM5tc
c49FijXfl0wt+Nv0rkhdrGSFihcK6L1vRrDtwBhWvQwPn+btBhm70fvENbwzBQUY
wtH0ZmbdwwfaSfGiL8am7uGNJxAqARVM4MedqtDnGT4FDy4vidukdgUjNl/tkkqp
A9ZMTFKFWdph2wmZbffdboWxJLjboyn3y5gWf5RylvA3dSsLrOsGSYGwWkQr9fI=
=GUl/
-----END PGP SIGNATURE-----

From Antoin.Verschuren@sidn.nl  Thu Jul 21 04:39:23 2011
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 D381921F89BA for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 04:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.504
X-Spam-Level: 
X-Spam-Status: No, score=-4.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KWcapEf3kZ5e for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 04:39:19 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [94.198.152.69]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAF121F874F for <dnsop@ietf.org>; Thu, 21 Jul 2011 04:39:19 -0700 (PDT)
Received: from KAHUBCAS1.SIDN.local ([192.168.2.41]) by ede1-kamx.sidn.nl  with ESMTP id p6LBdHGj006873 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=CAFAIL) for <dnsop@ietf.org>; Thu, 21 Jul 2011 13:39:17 +0200
Received: from [192.168.129.125] (192.168.129.125) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.1.289.1; Thu, 21 Jul 2011 13:39:17 +0200
Message-ID: <4E280FE7.50400@sidn.nl>
Date: Thu, 21 Jul 2011 13:39:19 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: <dnsop@ietf.org>
References: <020701cc3fb1$a7aa5120$f6fef360$@lampo@eurid.eu>
In-Reply-To: <020701cc3fb1$a7aa5120$f6fef360$@lampo@eurid.eu>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [192.168.129.125]
Subject: Re: [DNSOP] feedback/feelings around :	draft-barwood-dnsop-ds-publish-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, 21 Jul 2011 11:39:23 -0000

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

On 11-07-11 11:51, Marc Lampo wrote:
> Dear all,
> 
> http://tools.ietf.org/id/draft-barwood-dnsop-ds-publish-02.txt
> 
> There does not seem to be a lot of feedback on this draft ?
>  (some comments on version 01 only)

I have read the draft, and I have given it some thought.
Though I advocate a child-parent signalling method for key roll-overs, I
think this is not the correct way forward, and I'll explain why.

As a registry for .nl we have decided not to accept DS records from
childs, but DNSKEY instead, and calculate the DS ourselves.
The reason for this is multiple, but the major considerations are that
since the DS is on the parent side of the zone cut, we want to be able
to control the supported hashing algorithm for the DS in our zone, and
be able to change to a new algorithm without child interaction.

The major reason however is that when supporting a secure DNSSEC
dns-operator change, the registry will act as a relay for the DNSKEY
from the losing dns-operator to the new one, so in this process we need
to request the DNSKEY anyway. We don't want to request the DS and only
in the dns-operator change case request the DNSKEY as well or instead.

So since we don't accept DS, we will not support the CDS signalling.

What we think is a way forward is a way for the child to signal that a
new DNSKEY has appeared in the child zone that needs a DS at the parent,
or a way to signal a DNSKEY set that should have a corresponding DS at
the parent.
Some thoughts:
The SEP bit could be used for this but then not all keys with the SEP
bit may need a DS at the parent.
Perhaps we need another bit for this ?
I realise the SEP bit does not have this meaning right now, but I see no
hindrance in changing that definition.
A NOTIFY from child to parent may then be sufficient for the parent to
determine which keys need a DS.
But how does the child identify which parent server to send the NOTIFY to ?
And how does the receiving server at the parent know what to do with the
NOTIFY ?
And does a child always want to publish a DNSKEY in the zone before a DS
should be present at the parent, or should it be able to request a DS
for a DNSKEY before the DNSKEY is present in the zone ?
In the dns-operator change case, the DNSKEY's with this bit set should
therefore also be present in both zones, so not only both ZSK's (in a
KSK/ZSK case). This may change 4641bis again...

hope to have discussions next week

- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Utrechtseweg 310, 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/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJOKA/nAAoJEDqHrM883AgndQ4H/3GcJstvRElwkOKPv2ctEPBe
OeU6pb0Jfbr8pxfy72u21834pBZGs0ucH6/cdpXxS4wpPXxqJ8Mb5yMWlFIxU1kL
SbpWJLHDVge64f3Hy4pf67tCLCcCkFgTaTwIxMNaphbRuIoPE5AKYsfTlscP8Ii5
FUYV3tUBuWirygcSD/jQyxQWAtv2lOe0zFNSmAWK59pDr3HlF4tOrzpiZCZNZzUO
pQdmV8BySy9fY5l9VMOPHXoNpoFelHm8bA+Yh8WShyWYKQOcpCY5kh778bLOmU31
OPdi6Nb9/bovki2+UiKGuDwROKcBBVfLojHkTZCqt2/q4daHHxxbH2b84vo23Ig=
=7zLv
-----END PGP SIGNATURE-----

From stephan.lagerholm@secure64.com  Thu Jul 21 05:16:08 2011
Return-Path: <stephan.lagerholm@secure64.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 60BB721F854A for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 05:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80wZ5QZO0iRU for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 05:16:04 -0700 (PDT)
Received: from zimbra.secure64.com (unknown [64.92.221.189]) by ietfa.amsl.com (Postfix) with ESMTP id D2D8621F86EB for <dnsop@ietf.org>; Thu, 21 Jul 2011 05:16:03 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.secure64.com (Postfix) with ESMTP id 51507B83CE; Thu, 21 Jul 2011 06:16:01 -0600 (MDT)
X-Virus-Scanned: amavisd-new at secure64.com
Received: from zimbra.secure64.com ([127.0.0.1]) by localhost (zimbra.secure64.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jsyu8wWhSDjz; Thu, 21 Jul 2011 06:15:56 -0600 (MDT)
Received: from exchange.secure64.com (exchange.secure64.com [192.168.254.250]) by zimbra.secure64.com (Postfix) with ESMTPSA id BCD93B839D; Thu, 21 Jul 2011 06:15:55 -0600 (MDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=secure64.com; s=2010; t=1311250555; bh=Ekv6C3kNNpbJCEwxnSxcAfp1Zkys3x/9sI0eNCLO1XQ=; h=MIME-Version:Subject:Date:Content-Type:Message-ID:In-Reply-To: References:From:To; b=q+JZWOXDRmjJz3gh20j7x+W48DRzpZw8Rjsj+l+vcL1e 6Q7EoxWU6TZ8RnhjyMwfTVgG3iHv3vIToR6dayIx/uUUB5wZFlBGfYN49m7XXAqpylr JVE6AxA9eNOk2xC6L1q6ImEsKGdKxYB0ET9nxaO55RsEzAI/pTrardtQ+q18=
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 21 Jul 2011 06:15:55 -0600
Content-Type: multipart/signed; micalg=SHA1; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0000_01CC4786.CB974520"
Message-ID: <DD056A31A84CFC4AB501BD56D1E14BBBA78B22@exchange.secure64.com>
In-Reply-To: <4E280FE7.50400@sidn.nl>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [DNSOP] feedback/feelings around :	draft-barwood-dnsop-ds-publish-02.txt ?
Thread-Index: AcxHmu4vasuWc1fgSFGT94Vz8O+YNAAAjnCw
References: <020701cc3fb1$a7aa5120$f6fef360$@lampo@eurid.eu> <4E280FE7.50400@sidn.nl>
From: "Stephan Lagerholm" <stephan.lagerholm@secure64.com>
To: "Antoin Verschuren" <antoin.verschuren@sidn.nl>, <dnsop@ietf.org>
Subject: Re: [DNSOP] feedback/feelings around :	draft-barwood-dnsop-ds-publish-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, 21 Jul 2011 12:16:08 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01CC4786.CB974520
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


Antoin Verschuren wrote: 
> I have read the draft, and I have given it some thought.
> Though I advocate a child-parent signalling method for key roll-overs,
> I
> think this is not the correct way forward, and I'll explain why.
> 
> As a registry for .nl we have decided not to accept DS records from
> childs, but DNSKEY instead, and calculate the DS ourselves.
> The reason for this is multiple, but the major considerations are that
> since the DS is on the parent side of the zone cut, we want to be able
> to control the supported hashing algorithm for the DS in our zone, and
> be able to change to a new algorithm without child interaction.
Agree, this draft is not covering such scenario. And .NL is not alone doing
this. For example, .GOV is also asking for DNSKEYs instead of DS.

> The major reason however is that when supporting a secure DNSSEC
> dns-operator change, the registry will act as a relay for the DNSKEY
> from the losing dns-operator to the new one, so in this process we need
> to request the DNSKEY anyway. We don't want to request the DS and only
> in the dns-operator change case request the DNSKEY as well or instead.
> 
> So since we don't accept DS, we will not support the CDS signalling.
> 
> What we think is a way forward is a way for the child to signal that a
> new DNSKEY has appeared in the child zone that needs a DS at the
> parent,
> or a way to signal a DNSKEY set that should have a corresponding DS at
> the parent.
> Some thoughts:
> The SEP bit could be used for this but then not all keys with the SEP
> bit may need a DS at the parent.
> Perhaps we need another bit for this ?
I suggested to use another flag for the DNSKEY a few months ago here. The
reaction from the list was that it was too complicated because the key-id
would change during the lifetime of the DNSKEY. 

> I realise the SEP bit does not have this meaning right now, but I see
> no hindrance in changing that definition.
Doesn't work. There are scenarios when you want to have the DS record
published prior to publish the DNSKEY. For example, algorithm rollovers or
double DS rollover. A new record or a new flag to the DNSKEY is required.

> A NOTIFY from child to parent may then be sufficient for the parent to
> determine which keys need a DS.
> But how does the child identify which parent server to send the NOTIFY
> to ?
> And how does the receiving server at the parent know what to do with
> the NOTIFY ?
> And does a child always want to publish a DNSKEY in the zone before a
> DS should be present at the parent, or should it be able to request a DS
> for a DNSKEY before the DNSKEY is present in the zone ?
I Agree that the draft is missing the whole signaling piece. But it is still
a step in the right direction to try to define how the RR should look like.
The definition of the signaling can actually be defined later. 

/Stephan

------=_NextPart_000_0000_01CC4786.CB974520
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITKDCCBDYw
ggMeoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UEBhMCU0UxFDASBgNVBAoTC0FkZFRy
dXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBUVFAgTmV0d29yazEiMCAGA1UEAxMZ
QWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0wMDA1MzAxMDQ4MzhaFw0yMDA1MzAxMDQ4Mzha
MG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3Qg
RXh0ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC39xoz5vIABC054E5b7R+8bA/Ntfojts7e
mxEzl6QpTH2Tn71KvJPtAxrjj8/lbVBa1pcplFqAsEl62y6V/bjKvzc4LR4+kUGtcFbH8E8/6DKe
dMrIkFTpxl8PeJ2aQDwOrGGqXhSPnoehalDc15pOrwWzpnGUnHGzUGAKxxOdOAeGAqjpqGkmGJCr
TLBPI6s6T4TY386f4Wlvu9dC12tE5Met7m1BX3JacQg3s3llpFmglDf3AC8NwpJy2tA4ctsUqEXE
XSp9t7TWxO6szRNEt8kr3UMAJfphuWlqWCMRt6czj1Z1WfXNKddGtworZbbTQm8Vsrh7++/pXVPV
NFonAgMBAAGjgdwwgdkwHQYDVR0OBBYEFK29mHo0tCb3+sQmVO8DveAky1QaMAsGA1UdDwQEAwIB
BjAPBgNVHRMBAf8EBTADAQH/MIGZBgNVHSMEgZEwgY6AFK29mHo0tCb3+sQmVO8DveAky1QaoXOk
cTBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0
IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
ggEBMA0GCSqGSIb3DQEBBQUAA4IBAQCwm+CFJcLWI+IPlgaSnUGYnNmEeYHZHlsUByM2ZY+w2He7
rEFsR2CDUbD5Mj3n/PYmE8eAFqW/WvyHz3h5iSGa4kwHCoY1vPLeUcTSlrfcfk7ucP0cOesMAlEU
LY69FuDB30Z15ySt7PRCtIWTcBBnup0GNUoY0yt6zFFCoXpj0ea7ocUrwja+Ew3mvWN+eXunCQ1A
q2rdj4rD9vaMGkIFUdRF9Z+nYiFoFSBDPJnnfL0k2KmRF3OIP1YbMTgYtHEPms3IDp6OLhvhjJiD
yx8x8URMxgRzSXZgD8f4vReAay7pzEwOWpp5DyAKLtWeYyYeVZKU2IIXWnvQvMePToYEMIIEijCC
A3KgAwIBAgIQJ/TqEfR6hsRunbtuqRcHBzANBgkqhkiG9w0BAQUFADBvMQswCQYDVQQGEwJTRTEU
MBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3
b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290MB4XDTA1MDYwNzA4MDkxMFoX
DTIwMDUzMDEwNDgzOFowga4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2Fs
dCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0
cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRo
ZW50aWNhdGlvbiBhbmQgRW1haWwwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCyOYWk
8n2rQTtiRjeuzcFgdbw5ZflKGkeiucxIzGqY1U01GbmkQuXOSeKKLx580jEHx060g2SdLinVomTE
hb2FUTV5pE5okHsceqSSqBfymBXyk8zJpDKVuwxPML2YoAuL5W4bokb6eLyib6tZXqUvz8rabaov
66yhs2qqty5nNYt54R5piOLmRs2gpeq+C852OnoOm+r82idbPXMfIuZIYcZM82mxqC4bttQxICy8
goqOpA6l14lD/BZarx1x1xFZ2rqHDa/68+HC8KTFZ4zW1lQ63gqkugN3s2XI/R7TdGKqGMpokx6h
hX71R2XL+E1XKHTSNP8wtu72YjAUjCzrAgMBAAGjgeEwgd4wHwYDVR0jBBgwFoAUrb2YejS0Jvf6
xCZU7wO94CTLVBowHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59MA4GA1UdDwEB/wQEAwIB
BjAPBgNVHRMBAf8EBTADAQH/MHsGA1UdHwR0MHIwOKA2oDSGMmh0dHA6Ly9jcmwuY29tb2RvY2Eu
Y29tL0FkZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMDagNKAyhjBodHRwOi8vY3JsLmNvbW9kby5u
ZXQvQWRkVHJ1c3RFeHRlcm5hbENBUm9vdC5jcmwwDQYJKoZIhvcNAQEFBQADggEBABnYiRFvKKym
AKLnh8GbkAPbfqES/R7z4vABqZRUQmuaCcSgbdeQkgQDZnlDcfz4b6/bdkXiNxo93eRZBHisHPSD
RvN6z1uEci3lRsG6GBEp88tJeYc8um0FnaRtaE+tchQ2qLmx/b/Pf/CkapQ1UI/PgW1Vsd1ZMErf
baCcZB9JfO82u/TjafT4OY9arUuFOrcO7dPPDUSi+wS/5C9wjiX7WlQGs9DEvG2N+3MyLOmbhCQt
1n+RemgCUB8OP03pzPW7Z+jcHC47/E7N/gKO46gTCqUmRGXpEPJNUqeu3D7KazJcQWz+9V2g6v/R
+puGWG09lkfl/i6VBMIAzI6h8rswggUaMIIEAqADAgECAhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqG
SIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFr
ZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93
d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGlj
YXRpb24gYW5kIEVtYWlsMB4XDTExMDQyODAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNV
BAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAY
BgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQCShIRbS1eY1F4vi6ThQMijU1hfZmXxMk73nzJ9VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdW
Yn8XtXFpruUgG+TLY15gyqJB9mrho/+43x9IbWVDjCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1
+uVUgK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLSTNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/
FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsyfuNK4aVScmQmkU6lkg//4LFg/RpvaFGZY40a
i6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//BAgMBAAGjggFLMIIBRzAfBgNVHSMEGDAWgBSJ
gmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQUehNOAHRbxnhjZCfBL+KgW7x5xXswDgYDVR0P
AQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAwEQYDVR0gBAowCDAGBgRVHSAAMFgGA1UdHwRR
ME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1
dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsGAQUFBwEBBGgwZjA9BggrBgEFBQcwAoYxaHR0
cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRydXN0Q2xpZW50X0NBLmNydDAlBggrBgEFBQcw
AYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/
RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3NuPukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbR
oZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5yv7ikR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyY
PaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080zX5vQvWBqszv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1F
Tahp2oAbHj3SGl18R5mlmwhtEpmG1l1XBxunML5LSUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV
4ENAQjC+6qXnlNKw/vN1+X9u5zCCBT4wggQmoAMCAQICEQCqieXbTb+XECyYs28RwSsEMA0GCSqG
SIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAw
DgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09N
T0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDYxNDAw
MDAwMFoXDTEyMDYxMzIzNTk1OVowLzEtMCsGCSqGSIb3DQEJARYec3RlcGhhbi5sYWdlcmhvbG1A
c2VjdXJlNjQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnAdEdMkddn0GQ+ok
OKJod3Hv35ivPSQArj96FGL0mPtsotACZkiitt/DQmfZO3qS9lCxFsnTFbO956Vj3EiUyijpSCrm
Um3VAIIM1QEtzS3zEfUg8YMH0iECf2eKjIFb5MfsCBtT8i6FPBbgkcJaAJCYDNAsqxixxF118tR/
0s4u0+veG/sWWjFcA1n3bRMY1Fc6b/3OXZL5l7ExylQAPyyQUaOSrPWY083th5M8PuLdLfkdlk5y
nX5RUXDLScH4DhitC7JZMn5DDw+ynhnig9qYKFbE8//HcnFvqdv0YRC4fhrIQ2BeMykpM3O6HXiA
GQkgnn9DJCIbi7zsPlYaqQIDAQABo4IB7jCCAeowHwYDVR0jBBgwFoAUehNOAHRbxnhjZCfBL+Kg
W7x5xXswHQYDVR0OBBYEFLeP6hXrxLxWn2DV69jWEtwA0aA2MA4GA1UdDwEB/wQEAwIFoDAMBgNV
HRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEE
BAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9z
ZWN1cmUuY29tb2RvLm5ldC9DUFMwVwYDVR0fBFAwTjBMoEqgSIZGaHR0cDovL2NybC5jb21vZG9j
YS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBiAYI
KwYBBQUHAQEEfDB6MFIGCCsGAQUFBzAChkZodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9D
bGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUFBzABhhhodHRw
Oi8vb2NzcC5jb21vZG9jYS5jb20wKQYDVR0RBCIwIIEec3RlcGhhbi5sYWdlcmhvbG1Ac2VjdXJl
NjQuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQAX25FQTFsTPhS2D6jKzH+vguHy4xsHonYZPWn97O/J
HS+HsjeMejxrW1xRS937oAKW+nMtDBjRQ2yvT7rHYopk6hJUTB1GnoNWJbRRXJLQCkyKAeRl5Zwh
7OY5h3PQgxLxHXlyCBzf4G4RfIjm07bor+fpV30Y2g9SdPiQPiLI3NdKJTS65BGpXMEUOEfiugtY
AM0jMQc/JWrR1RY3oYPIqBPTwauuOXBraVguy7nPjxbWntaSvRQkW593LoCRBCQYCg1bM2w83J4n
PUAWqmOxRoWjvfHGfqlrFDTIuc7Dy3loqBEPZJHgg5kONUJCu3v6yC26aRjI9to6NjNNbwu+MYIE
aDCCBGQCAQEwgakwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBD
T01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEQCqieXbTb+X
ECyYs28RwSsEMAkGBSsOAwIaBQCgggKTMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTExMDcyMTEyMTU1NVowIwYJKoZIhvcNAQkEMRYEFC4uy/NIrwX1FlE5WDLs00g0
H9oeMIG3BgkqhkiG9w0BCQ8xgakwgaYwCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBFjAKBggqhkiG
9w0DBzALBglghkgBZQMEAQIwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFA
MA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAsGCWCGSAFlAwQCAzALBglghkgBZQMEAgIwCwYJYIZI
AWUDBAIBMAoGCCqGSIb3DQIFMIG6BgkrBgEEAYI3EAQxgawwgakwgZMxCzAJBgNVBAYTAkdCMRsw
GQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFu
ZCBTZWN1cmUgRW1haWwgQ0ECEQCqieXbTb+XECyYs28RwSsEMIG8BgsqhkiG9w0BCRACCzGBrKCB
qTCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMH
U2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIRAKqJ5dtNv5cQLJizbxHBKwQw
DQYJKoZIhvcNAQEBBQAEggEAX+F2Sq5umnJfn2FTzWjiiU3z7HhrAPna7dF8IsfFEaTKDExjbDDM
IZPWQmAQrsiY1QHcFhInyoZqKt/6z6yhDF+gg1yQfBcx+oLb48rVZbzeDwftIocuMmRe5U184tko
N6CjDEWX4OoKEYbvyZh1Y5EN6d5/Snk2eZ5nBTOIK5YzNRcH1mlIYm1bTtkNc4NEpiz0CS74fbQX
7ICVwh7K/eEdiPSCUZFjuUPqMRPxB6OvFw87NYBeCAbNhOAenMylv/HLPDA6lbAEA56ZpPN+q8aU
trsVkZZPzTAtQeiJO5Bfha2TgURMUHWSLPgpmESV+OuuHtIKrLPKWziI8bC2ywAAAAAAAA==

------=_NextPart_000_0000_01CC4786.CB974520--

From Antoin.Verschuren@sidn.nl  Thu Jul 21 05:35:35 2011
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 5286721F8B56 for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 05:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.504
X-Spam-Level: 
X-Spam-Status: No, score=-4.504 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,  RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBsQ5aoXMm2Q for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 05:35:30 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [94.198.152.69]) by ietfa.amsl.com (Postfix) with ESMTP id 903DB21F8B4C for <dnsop@ietf.org>; Thu, 21 Jul 2011 05:35:30 -0700 (PDT)
Received: from KAHUBCAS1.SIDN.local ([192.168.2.41]) by ede1-kamx.sidn.nl  with ESMTP id p6LCZTXR009314 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=CAFAIL) for <dnsop@ietf.org>; Thu, 21 Jul 2011 14:35:29 +0200
Received: from [192.168.129.125] (192.168.129.125) by KAHUBCAS1.SIDN.local (192.168.2.41) with Microsoft SMTP Server (TLS) id 14.1.289.1; Thu, 21 Jul 2011 14:35:28 +0200
Message-ID: <4E281D13.6020104@sidn.nl>
Date: Thu, 21 Jul 2011 14:35:31 +0200
From: Antoin Verschuren <antoin.verschuren@sidn.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: <dnsop@ietf.org>
References: <020701cc3fb1$a7aa5120$f6fef360$@lampo@eurid.eu> <4E280FE7.50400@sidn.nl> <DD056A31A84CFC4AB501BD56D1E14BBBA78B22@exchange.secure64.com>
In-Reply-To: <DD056A31A84CFC4AB501BD56D1E14BBBA78B22@exchange.secure64.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [192.168.129.125]
Subject: Re: [DNSOP] feedback/feelings around :	draft-barwood-dnsop-ds-publish-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, 21 Jul 2011 12:35:35 -0000

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

On 21-07-11 14:15, Stephan Lagerholm wrote:
> 
> I suggested to use another flag for the DNSKEY a few months ago here. The
> reaction from the list was that it was too complicated because the key-id
> would change during the lifetime of the DNSKEY. 

Why would you look at the key-id ?
If as a parent I get a notify, I (securely) look up the DNSKEY set,
select the keys with a SEP bit and hash them to DS. What does the key-id
do in that ?
If the key-id changes during the DNSKEY lifetime, doesn't it mean the DS
at the parent should change too ?
Or do you mean there's a point in time you set the flag, and that causes
the key-id to change ? Yes, sure. But then I see that as a key change,
and you have to signal the parent anyway.

>> I realise the SEP bit does not have this meaning right now, but I see
>> no hindrance in changing that definition.
> Doesn't work. There are scenarios when you want to have the DS record
> published prior to publish the DNSKEY. For example, algorithm rollovers or
> double DS rollover. A new record or a new flag to the DNSKEY is required.

I wonder if this is a practice that needs to be reconsidered.
I can imagine you don't sign with a new key yet, but can publishing it
in the zone do harm ? Even if it's a bogus key ?
And perhaps the many roll-over scenario's we have now can be brought
back to just the ones that work in such an automated fashion.

> I Agree that the draft is missing the whole signaling piece. But it is still
> a step in the right direction to try to define how the RR should look like.
> The definition of the signaling can actually be defined later. 

Agree, that is a next step.

- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Utrechtseweg 310, 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/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJOKB0SAAoJEDqHrM883AgnA5MH/AuqVYyIr/fkA6uamMG2iOJe
eNGZe4kA15wX6YC5gODP9mA2B+VCvITh1kQ4UItthxWoWQpGiDaYMFYsbnmZTh20
P8A66mJ8sZ3qYFTB2ZwrEQp26vHCTfhh+LZHJjRRRdKbT3zhvR5y+0mEdWAavbF4
j/u218/qoNKJcdI/QRNOP3l1NFDMRgVymy3ui6f7d5p1rwjJT6jRad5b4CVr6uQl
RGHBXCbM9l32e+SfSUH6QR4EwlwncKZdEHUsgt27BFzaO/962Q88+j864cak6vxQ
HCre5nIecc8shN3gpaquADK3ny2ePfxhxOhyux+XlRL2lvdm/qMt0oiySYHjoik=
=KJXm
-----END PGP SIGNATURE-----

From dhc2@dcrocker.net  Thu Jul 21 06:22:38 2011
Return-Path: <dhc2@dcrocker.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 27A1421F87A4 for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 06:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rdpS8Cy1zD4M for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 06:22:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 54A3021F85B5 for <dnsop@ietf.org>; Thu, 21 Jul 2011 06:22:34 -0700 (PDT)
Received: from [128.237.113.156] (CMU-466665.WV.CC.CMU.EDU [128.237.113.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p6LDMRES010102 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Thu, 21 Jul 2011 06:22:34 -0700
Message-ID: <4E28280D.2020509@dcrocker.net>
Date: Thu, 21 Jul 2011 09:22:21 -0400
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: dnsop@ietf.org
X-Priority: 2 (High)
References: <20110719160557.GD25368@x27.adm.denic.de>
In-Reply-To: <20110719160557.GD25368@x27.adm.denic.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 21 Jul 2011 06:22:34 -0700 (PDT)
Subject: Re: [DNSOP] DNSOP future direction (agenda item 5 for Quebec)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 21 Jul 2011 13:22:38 -0000

Dear WG,

Howdy.


On 7/19/2011 12:05 PM, Peter Koch wrote:
> So, here are topics that have been raised in the recent or not so
> recent past, in no particular order:


Some years ago, this working group formally took on a task that it did not 
pursue, concerning the emerging convention of using node names that begin with 
an underscore.

The original work was based on a preliminary specification that I wrote and that 
received some discussion.

Recently, I have twice posted queries about a revised specification but there 
has been no followup at all, in spite of additional, offline queries.

The current draft is:

      DNS Scoped Data Through Attribute Leaves
      <https://datatracker.ietf.org/doc/draft-crocker-dns-attrleaf/>

There is existing /and incompatible/ work that has produced a series of 
independent registries, for a single namespace(!)  Take a look at Section 5 of 
the draft and you will see a rather long list of specs that have defined their 
own registries for this namespace, either implicitly or explicitly.

It's difficult to imagine a stronger basis for working towards a common 
registration mechanism.

This group is the natural home for this work.

I would like to receive an explicit decision from this working group about 
whether it will take the task on or won't.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From stephan.lagerholm@secure64.com  Thu Jul 21 06:47:41 2011
Return-Path: <stephan.lagerholm@secure64.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 384AD21F85B9 for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 06:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+pZr3Uq57th for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 06:47:36 -0700 (PDT)
Received: from zimbra.secure64.com (unknown [64.92.221.189]) by ietfa.amsl.com (Postfix) with ESMTP id BDC9921F85BB for <dnsop@ietf.org>; Thu, 21 Jul 2011 06:47:36 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.secure64.com (Postfix) with ESMTP id 4EDF2B83BF; Thu, 21 Jul 2011 07:47:36 -0600 (MDT)
X-Virus-Scanned: amavisd-new at secure64.com
Received: from zimbra.secure64.com ([127.0.0.1]) by localhost (zimbra.secure64.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSfO8TTfAEiy; Thu, 21 Jul 2011 07:47:31 -0600 (MDT)
Received: from exchange.secure64.com (exchange.secure64.com [192.168.254.250]) by zimbra.secure64.com (Postfix) with ESMTPSA id 11066B81C0; Thu, 21 Jul 2011 07:47:31 -0600 (MDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=secure64.com; s=2010; t=1311256051; bh=R7cd/c178HDrL6UFDLd6ZLVPyTtfYvD8qVQ8PZFHPWM=; h=MIME-Version:Subject:Date:Content-Type:Message-ID:In-Reply-To: References:From:To; b=Ttq8sWeq/w5br7IY1GhnpFFI+D766pEty6076+V3q3GE TxTOLog7VZnyd4+0irnxU/VjVgelc0/7BglS/VgTANfQFQHdeJj1ljyeFKirdCGD9B2 XzsuxN5iZ5CDRUnf9J4rxx2Yh+KOdFY/S0k9iho4DVU9MnBu4X7NiVsoJ23I=
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 21 Jul 2011 07:47:31 -0600
Content-Type: multipart/signed; micalg=SHA1; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0000_01CC4793.97BDBA60"
Message-ID: <DD056A31A84CFC4AB501BD56D1E14BBBA78B25@exchange.secure64.com>
In-Reply-To: <4E281D13.6020104@sidn.nl>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [DNSOP] feedback/feelings around :	draft-barwood-dnsop-ds-publish-02.txt ?
Thread-Index: AcxHosGJy69ebR0eSAaLRUHLBmyLaQAB3cHA
References: <020701cc3fb1$a7aa5120$f6fef360$@lampo@eurid.eu><4E280FE7.50400@sidn.nl><DD056A31A84CFC4AB501BD56D1E14BBBA78B22@exchange.secure64.com> <4E281D13.6020104@sidn.nl>
From: "Stephan Lagerholm" <stephan.lagerholm@secure64.com>
To: "Antoin Verschuren" <antoin.verschuren@sidn.nl>, <dnsop@ietf.org>
Subject: Re: [DNSOP] feedback/feelings around :	draft-barwood-dnsop-ds-publish-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, 21 Jul 2011 13:47:41 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01CC4793.97BDBA60
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


On Thursday, July 21, 2011 9:36 AM Antoin Verschuren wrote:
> On 21-07-11 14:15, Stephan Lagerholm wrote:
> >
> > I suggested to use another flag for the DNSKEY a few months ago here.
> The
> > reaction from the list was that it was too complicated because the
> key-id
> > would change during the lifetime of the DNSKEY.
> 
> Why would you look at the key-id ?
I wouldn't, but the feedback was that we shouldn't mess with the flag field
of the DNSKEY, RFC5011 did that and it created a lot of confusion for
operators because the key-id changes.

> If as a parent I get a notify, I (securely) look up the DNSKEY set,
> select the keys with a SEP bit and hash them to DS. What does the key-
> id do in that ?
Nothing, but the SEP = DS doesn't work. Some zones (.NU) doesn't even have
the SEP bit.

> If the key-id changes during the DNSKEY lifetime, doesn't it mean the
> DS at the parent should change too ?
> Or do you mean there's a point in time you set the flag, and that
> causes the key-id to change ? Yes, sure. But then I see that as a key
change,
> and you have to signal the parent anyway.
The idea was to have an embryonic flag. For example, if the embryonic flag
was in position 10 in the flag field (512):
The child operator would publish a key with flag 769 (257 + 512) signaling
the intention to soon add a DNSKEY with flag field 257.
The parent would pick up the DNSKEY and create a DS but without including
the embryonic flag in the DS calculation.
The after the child sees the DS at the parent, it would remove the embryonic
flag from the DNSKEY.

During the lifetime of the key it would have different flag fields and
different key-ids.
769 -> 257 -> 385 (if RFC5011 rollovers are used, the revoked bit could
perhaps also be extended mean that the DS should be removed from the parent)

/S

------=_NextPart_000_0000_01CC4793.97BDBA60
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITKDCCBDYw
ggMeoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UEBhMCU0UxFDASBgNVBAoTC0FkZFRy
dXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBUVFAgTmV0d29yazEiMCAGA1UEAxMZ
QWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0wMDA1MzAxMDQ4MzhaFw0yMDA1MzAxMDQ4Mzha
MG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3Qg
RXh0ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC39xoz5vIABC054E5b7R+8bA/Ntfojts7e
mxEzl6QpTH2Tn71KvJPtAxrjj8/lbVBa1pcplFqAsEl62y6V/bjKvzc4LR4+kUGtcFbH8E8/6DKe
dMrIkFTpxl8PeJ2aQDwOrGGqXhSPnoehalDc15pOrwWzpnGUnHGzUGAKxxOdOAeGAqjpqGkmGJCr
TLBPI6s6T4TY386f4Wlvu9dC12tE5Met7m1BX3JacQg3s3llpFmglDf3AC8NwpJy2tA4ctsUqEXE
XSp9t7TWxO6szRNEt8kr3UMAJfphuWlqWCMRt6czj1Z1WfXNKddGtworZbbTQm8Vsrh7++/pXVPV
NFonAgMBAAGjgdwwgdkwHQYDVR0OBBYEFK29mHo0tCb3+sQmVO8DveAky1QaMAsGA1UdDwQEAwIB
BjAPBgNVHRMBAf8EBTADAQH/MIGZBgNVHSMEgZEwgY6AFK29mHo0tCb3+sQmVO8DveAky1QaoXOk
cTBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0
IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
ggEBMA0GCSqGSIb3DQEBBQUAA4IBAQCwm+CFJcLWI+IPlgaSnUGYnNmEeYHZHlsUByM2ZY+w2He7
rEFsR2CDUbD5Mj3n/PYmE8eAFqW/WvyHz3h5iSGa4kwHCoY1vPLeUcTSlrfcfk7ucP0cOesMAlEU
LY69FuDB30Z15ySt7PRCtIWTcBBnup0GNUoY0yt6zFFCoXpj0ea7ocUrwja+Ew3mvWN+eXunCQ1A
q2rdj4rD9vaMGkIFUdRF9Z+nYiFoFSBDPJnnfL0k2KmRF3OIP1YbMTgYtHEPms3IDp6OLhvhjJiD
yx8x8URMxgRzSXZgD8f4vReAay7pzEwOWpp5DyAKLtWeYyYeVZKU2IIXWnvQvMePToYEMIIEijCC
A3KgAwIBAgIQJ/TqEfR6hsRunbtuqRcHBzANBgkqhkiG9w0BAQUFADBvMQswCQYDVQQGEwJTRTEU
MBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3
b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290MB4XDTA1MDYwNzA4MDkxMFoX
DTIwMDUzMDEwNDgzOFowga4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2Fs
dCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0
cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRo
ZW50aWNhdGlvbiBhbmQgRW1haWwwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCyOYWk
8n2rQTtiRjeuzcFgdbw5ZflKGkeiucxIzGqY1U01GbmkQuXOSeKKLx580jEHx060g2SdLinVomTE
hb2FUTV5pE5okHsceqSSqBfymBXyk8zJpDKVuwxPML2YoAuL5W4bokb6eLyib6tZXqUvz8rabaov
66yhs2qqty5nNYt54R5piOLmRs2gpeq+C852OnoOm+r82idbPXMfIuZIYcZM82mxqC4bttQxICy8
goqOpA6l14lD/BZarx1x1xFZ2rqHDa/68+HC8KTFZ4zW1lQ63gqkugN3s2XI/R7TdGKqGMpokx6h
hX71R2XL+E1XKHTSNP8wtu72YjAUjCzrAgMBAAGjgeEwgd4wHwYDVR0jBBgwFoAUrb2YejS0Jvf6
xCZU7wO94CTLVBowHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59MA4GA1UdDwEB/wQEAwIB
BjAPBgNVHRMBAf8EBTADAQH/MHsGA1UdHwR0MHIwOKA2oDSGMmh0dHA6Ly9jcmwuY29tb2RvY2Eu
Y29tL0FkZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMDagNKAyhjBodHRwOi8vY3JsLmNvbW9kby5u
ZXQvQWRkVHJ1c3RFeHRlcm5hbENBUm9vdC5jcmwwDQYJKoZIhvcNAQEFBQADggEBABnYiRFvKKym
AKLnh8GbkAPbfqES/R7z4vABqZRUQmuaCcSgbdeQkgQDZnlDcfz4b6/bdkXiNxo93eRZBHisHPSD
RvN6z1uEci3lRsG6GBEp88tJeYc8um0FnaRtaE+tchQ2qLmx/b/Pf/CkapQ1UI/PgW1Vsd1ZMErf
baCcZB9JfO82u/TjafT4OY9arUuFOrcO7dPPDUSi+wS/5C9wjiX7WlQGs9DEvG2N+3MyLOmbhCQt
1n+RemgCUB8OP03pzPW7Z+jcHC47/E7N/gKO46gTCqUmRGXpEPJNUqeu3D7KazJcQWz+9V2g6v/R
+puGWG09lkfl/i6VBMIAzI6h8rswggUaMIIEAqADAgECAhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqG
SIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFr
ZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93
d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGlj
YXRpb24gYW5kIEVtYWlsMB4XDTExMDQyODAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNV
BAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAY
BgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQCShIRbS1eY1F4vi6ThQMijU1hfZmXxMk73nzJ9VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdW
Yn8XtXFpruUgG+TLY15gyqJB9mrho/+43x9IbWVDjCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1
+uVUgK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLSTNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/
FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsyfuNK4aVScmQmkU6lkg//4LFg/RpvaFGZY40a
i6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//BAgMBAAGjggFLMIIBRzAfBgNVHSMEGDAWgBSJ
gmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQUehNOAHRbxnhjZCfBL+KgW7x5xXswDgYDVR0P
AQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAwEQYDVR0gBAowCDAGBgRVHSAAMFgGA1UdHwRR
ME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1
dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsGAQUFBwEBBGgwZjA9BggrBgEFBQcwAoYxaHR0
cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRydXN0Q2xpZW50X0NBLmNydDAlBggrBgEFBQcw
AYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/
RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3NuPukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbR
oZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5yv7ikR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyY
PaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080zX5vQvWBqszv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1F
Tahp2oAbHj3SGl18R5mlmwhtEpmG1l1XBxunML5LSUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV
4ENAQjC+6qXnlNKw/vN1+X9u5zCCBT4wggQmoAMCAQICEQCqieXbTb+XECyYs28RwSsEMA0GCSqG
SIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAw
DgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09N
T0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDYxNDAw
MDAwMFoXDTEyMDYxMzIzNTk1OVowLzEtMCsGCSqGSIb3DQEJARYec3RlcGhhbi5sYWdlcmhvbG1A
c2VjdXJlNjQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnAdEdMkddn0GQ+ok
OKJod3Hv35ivPSQArj96FGL0mPtsotACZkiitt/DQmfZO3qS9lCxFsnTFbO956Vj3EiUyijpSCrm
Um3VAIIM1QEtzS3zEfUg8YMH0iECf2eKjIFb5MfsCBtT8i6FPBbgkcJaAJCYDNAsqxixxF118tR/
0s4u0+veG/sWWjFcA1n3bRMY1Fc6b/3OXZL5l7ExylQAPyyQUaOSrPWY083th5M8PuLdLfkdlk5y
nX5RUXDLScH4DhitC7JZMn5DDw+ynhnig9qYKFbE8//HcnFvqdv0YRC4fhrIQ2BeMykpM3O6HXiA
GQkgnn9DJCIbi7zsPlYaqQIDAQABo4IB7jCCAeowHwYDVR0jBBgwFoAUehNOAHRbxnhjZCfBL+Kg
W7x5xXswHQYDVR0OBBYEFLeP6hXrxLxWn2DV69jWEtwA0aA2MA4GA1UdDwEB/wQEAwIFoDAMBgNV
HRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEE
BAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0cHM6Ly9z
ZWN1cmUuY29tb2RvLm5ldC9DUFMwVwYDVR0fBFAwTjBMoEqgSIZGaHR0cDovL2NybC5jb21vZG9j
YS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBiAYI
KwYBBQUHAQEEfDB6MFIGCCsGAQUFBzAChkZodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9D
bGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUFBzABhhhodHRw
Oi8vb2NzcC5jb21vZG9jYS5jb20wKQYDVR0RBCIwIIEec3RlcGhhbi5sYWdlcmhvbG1Ac2VjdXJl
NjQuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQAX25FQTFsTPhS2D6jKzH+vguHy4xsHonYZPWn97O/J
HS+HsjeMejxrW1xRS937oAKW+nMtDBjRQ2yvT7rHYopk6hJUTB1GnoNWJbRRXJLQCkyKAeRl5Zwh
7OY5h3PQgxLxHXlyCBzf4G4RfIjm07bor+fpV30Y2g9SdPiQPiLI3NdKJTS65BGpXMEUOEfiugtY
AM0jMQc/JWrR1RY3oYPIqBPTwauuOXBraVguy7nPjxbWntaSvRQkW593LoCRBCQYCg1bM2w83J4n
PUAWqmOxRoWjvfHGfqlrFDTIuc7Dy3loqBEPZJHgg5kONUJCu3v6yC26aRjI9to6NjNNbwu+MYIE
aDCCBGQCAQEwgakwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBD
T01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEQCqieXbTb+X
ECyYs28RwSsEMAkGBSsOAwIaBQCgggKTMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTExMDcyMTEzNDczMVowIwYJKoZIhvcNAQkEMRYEFD4Pv6D0235/QBkLg3WHnuo2
oRb5MIG3BgkqhkiG9w0BCQ8xgakwgaYwCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBFjAKBggqhkiG
9w0DBzALBglghkgBZQMEAQIwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFA
MA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAsGCWCGSAFlAwQCAzALBglghkgBZQMEAgIwCwYJYIZI
AWUDBAIBMAoGCCqGSIb3DQIFMIG6BgkrBgEEAYI3EAQxgawwgakwgZMxCzAJBgNVBAYTAkdCMRsw
GQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP
TU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFu
ZCBTZWN1cmUgRW1haWwgQ0ECEQCqieXbTb+XECyYs28RwSsEMIG8BgsqhkiG9w0BCRACCzGBrKCB
qTCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMH
U2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIRAKqJ5dtNv5cQLJizbxHBKwQw
DQYJKoZIhvcNAQEBBQAEggEAHqDthAup5V/F3fXuzfhlCvpviSjsMs7VdowmJ+qySnm4FviMxe6m
XnAJhZ1XkTvqKva5XBcyffnBU1OUC5nUQPhpSDDpUu90mrH3G35tOPEgQ70R6BzthKlwAoRLemKA
E8DXKvfTEb1D7WStKepvaTy42yty7FXUUkwMy38MS7wBMGH+Os5SozOCSl/4H/5KQ0Xi/kv3MWtl
XIWELLIZRojJnmYu/6BwI0qXXE9E9Yhf15liqv+LlFMlbypA72Lg3ZaYusJz0klLuQs08oBCDfUS
W9hqMLmrY+bK4I6ZMJ697byewMd95hq38nkQZYT4BBf4tpsXBU9nYIXpMmHoAgAAAAAAAA==

------=_NextPart_000_0000_01CC4793.97BDBA60--

From mohta@necom830.hpcl.titech.ac.jp  Thu Jul 21 06:58:22 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.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 3DC0721F8B2D for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 06:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cYL-inWOaprY for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 06:58:21 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 6CF2721F89BA for <dnsop@ietf.org>; Thu, 21 Jul 2011 06:58:21 -0700 (PDT)
Received: (qmail 12219 invoked from network); 21 Jul 2011 14:16:37 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 21 Jul 2011 14:16:37 -0000
Message-ID: <4E28304D.6090101@necom830.hpcl.titech.ac.jp>
Date: Thu, 21 Jul 2011 22:57:33 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20110719160557.GD25368@x27.adm.denic.de> <4E28280D.2020509@dcrocker.net>
In-Reply-To: <4E28280D.2020509@dcrocker.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] DNSOP future direction (agenda item 5 for Quebec)
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, 21 Jul 2011 13:58:22 -0000

Dave CROCKER wrote:

> Take a look at Section 
> 5 of the draft and you will see a rather long list of specs that have 
> defined their own registries for this namespace, either implicitly or 
> explicitly.

That's definitely what we should not do.

> It's difficult to imagine a stronger basis for working towards a common
> registration mechanism.

We already have more than enough registration mechanisms.

> This group is the natural home for this work.

You'd better worry about registration mechanisms for file name
extensions.

							Masataka Ohta

From ogud@ogud.com  Thu Jul 21 07:16:45 2011
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 2B98721F8876 for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 07:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.522
X-Spam-Level: 
X-Spam-Status: No, score=-106.522 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJlTE0ILFC3m for <dnsop@ietfa.amsl.com>; Thu, 21 Jul 2011 07:16:40 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 29E8221F8764 for <dnsop@ietf.org>; Thu, 21 Jul 2011 07:16:40 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p6LEGabj032887 for <dnsop@ietf.org>; Thu, 21 Jul 2011 10:16:36 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4E2834BF.7040108@ogud.com>
Date: Thu, 21 Jul 2011 10:16:31 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: dnsop@ietf.org
References: <020701cc3fb1$a7aa5120$f6fef360$@lampo@eurid.eu> <4E280FE7.50400@sidn.nl>
In-Reply-To: <4E280FE7.50400@sidn.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Subject: Re: [DNSOP] feedback/feelings around :	draft-barwood-dnsop-ds-publish-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, 21 Jul 2011 14:16:45 -0000

On 21/07/2011 7:39 AM, Antoin Verschuren wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11-07-11 11:51, Marc Lampo wrote:
>> Dear all,
>>
>> http://tools.ietf.org/id/draft-barwood-dnsop-ds-publish-02.txt
>>
>> There does not seem to be a lot of feedback on this draft ?
>>   (some comments on version 01 only)
>
> I have read the draft, and I have given it some thought.
> Though I advocate a child-parent signalling method for key roll-overs, I
> think this is not the correct way forward, and I'll explain why.
>
> As a registry for .nl we have decided not to accept DS records from
> childs, but DNSKEY instead, and calculate the DS ourselves.
> The reason for this is multiple, but the major considerations are that
> since the DS is on the parent side of the zone cut, we want to be able
> to control the supported hashing algorithm for the DS in our zone, and
> be able to change to a new algorithm without child interaction.

This is a non arguments, even if the child list CDS with the 
identification of the DNSKEY's that it wants represented in the DS set,
if you can look up CDS then you can follow that with a DNSKEY query and 
pull out the appropriate keys.

The second argument as you want to control the hash algorithms, I 
understand that but at the same time think that is not reasonable unless 
you handle corner cases, like if embassy-russia.nl wants digest 3 will 
you support that?

>
> The major reason however is that when supporting a secure DNSSEC
> dns-operator change, the registry will act as a relay for the DNSKEY
> from the losing dns-operator to the new one, so in this process we need
> to request the DNSKEY anyway. We don't want to request the DS and only
> in the dns-operator change case request the DNSKEY as well or instead.
>
See above you ask for it after asking for CDS.


> So since we don't accept DS, we will not support the CDS signalling.

Sounds like you want CKEY-to-DS record i.e. record that has the keys 
that the child wants to to chash?

>
> What we think is a way forward is a way for the child to signal that a
> new DNSKEY has appeared in the child zone that needs a DS at the parent,
> or a way to signal a DNSKEY set that should have a corresponding DS at
> the parent.

This does not work in all cases, unless the child can control when/if 
the parent checks. (think algorithm introduction/retirement)

> Some thoughts:
> The SEP bit could be used for this but then not all keys with the SEP
> bit may need a DS at the parent.
> Perhaps we need another bit for this ?
> I realise the SEP bit does not have this meaning right now, but I see no
> hindrance in changing that definition.

A new bit would be better, but you need to think about the semantics.
IMHO CKEY-to-DS  is what you want.

> A NOTIFY from child to parent may then be sufficient for the parent to
> determine which keys need a DS.

The tricky question is: How does a child to tell the parent that keys 
for alg X are to be removed from DS ?
As the DS is the first place the delete takes place, then you remove the 
DNSKEY record, followed by purging the signatures.

> But how does the child identify which parent server to send the NOTIFY to ?

This is a good open question, in particular when you have the RRR model 
and the middle R demands to be in the middle of all transactions.

> And how does the receiving server at the parent know what to do with the
> NOTIFY ?

(new protocol)

> And does a child always want to publish a DNSKEY in the zone before a DS
> should be present at the parent, or should it be able to request a DS
> for a DNSKEY before the DNSKEY is present in the zone ?

This is the crux of the matter, for the reason that what is in DS does 
not have to mirror what is in DNSKEY a new type is IMHO the way to go.
A further advantage of a new type is that way the child can explicitly 
opt-in to automatic rollover of DS records. (and possibly of NS as well)

> In the dns-operator change case, the DNSKEY's with this bit set should
> therefore also be present in both zones, so not only both ZSK's (in a
> KSK/ZSK case). This may change 4641bis again...
>
> hope to have discussions next week
>

In this case the parent combines the content of the CDS records from 
both operators for a while.

	Olafur

From wmaton@ryouko.imsb.nrc.ca  Tue Jul 26 10:48:36 2011
Return-Path: <wmaton@ryouko.imsb.nrc.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 5808D21F88DD for <dnsop@ietfa.amsl.com>; Tue, 26 Jul 2011 10:48:36 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cuj4IBaRlqMa for <dnsop@ietfa.amsl.com>; Tue, 26 Jul 2011 10:48:36 -0700 (PDT)
Received: from ryouko.imsb.nrc.ca (ryouko.imsb.nrc.ca [IPv6:2604:8400:0:127::10]) by ietfa.amsl.com (Postfix) with ESMTP id B327821F88DC for <dnsop@ietf.org>; Tue, 26 Jul 2011 10:48:35 -0700 (PDT)
Received: from ryouko.imsb.nrc.ca (localhost [127.0.0.1]) by ryouko.imsb.nrc.ca (8.14.4/8.14.4) with ESMTP id p6QHmTg6016224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Tue, 26 Jul 2011 13:48:34 -0400
Received: from localhost (wmaton@localhost) by ryouko.imsb.nrc.ca (8.14.4/8.14.4/Submit) with ESMTP id p6QHmTYA016221 for <dnsop@ietf.org>; Tue, 26 Jul 2011 13:48:29 -0400
Date: Tue, 26 Jul 2011 13:48:29 -0400 (EDT)
From: "William F. Maton Sotomayor" <wmaton@ryouko.imsb.nrc.ca>
To: dnsop@ietf.org
Message-ID: <Pine.LNX.4.64.1107261343260.5948@ryouko.imsb.nrc.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: [DNSOP] Further observationon AS112 ipv4 cull
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: wmaton@ryouko.imsb.nrc.ca
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, 26 Jul 2011 17:48:36 -0000

All,
 	As a data point, the original draft of -00 really started life as 
a straight copy of George's and Geoff's draft.  I was looking for a way to 
establish a procedure for sending instructions to IANA for new delegations 
to AS112 nodes, so they paved the way.  That said, I also don't have a 
problem with splitting my draft into 2:  One with the original set of 
instructions and another that could possibly either lead to a 'bis' for 
6303 or become another document in a series of AS112 RFCs - much like RFC 
6305 seems to be.

(I'm more pragmatic in the sense that I'd like to see the instructions go 
forward faster than another Informational RFC/bis. :-) )

Thanks,

wfms

From ggm+ietf@apnic.net  Tue Jul 26 10:53:21 2011
Return-Path: <ggm+ietf@apnic.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 78C4D21F8AA8 for <dnsop@ietfa.amsl.com>; Tue, 26 Jul 2011 10:53:21 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DOsNWRMhnC6 for <dnsop@ietfa.amsl.com>; Tue, 26 Jul 2011 10:53:21 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 0B09A21F8A66 for <dnsop@ietf.org>; Tue, 26 Jul 2011 10:53:21 -0700 (PDT)
Received: from dhcp-53cd.meeting.ietf.org (unknown [130.129.83.205]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 8E045B689A; Wed, 27 Jul 2011 03:53:18 +1000 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <Pine.LNX.4.64.1107261343260.5948@ryouko.imsb.nrc.ca>
Date: Tue, 26 Jul 2011 13:53:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC39BC85-FC4B-4800-8805-C871D1525703@apnic.net>
References: <Pine.LNX.4.64.1107261343260.5948@ryouko.imsb.nrc.ca>
To: wmaton@ryouko.imsb.nrc.ca
X-Mailer: Apple Mail (2.1084)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Further observationon AS112 ipv4 cull
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, 26 Jul 2011 17:53:21 -0000

On 26/07/2011, at 1:48 PM, William F. Maton Sotomayor wrote:

>=20
> All,
> 	As a data point, the original draft of -00 really started life =
as a straight copy of George's and Geoff's draft.  I was looking for a =
way to establish a procedure for sending instructions to IANA for new =
delegations to AS112 nodes, so they paved the way.  That said, I also =
don't have a problem with splitting my draft into 2:  One with the =
original set of instructions and another that could possibly either lead =
to a 'bis' for 6303 or become another document in a series of AS112 RFCs =
- much like RFC 6305 seems to be.
>=20
> (I'm more pragmatic in the sense that I'd like to see the instructions =
go forward faster than another Informational RFC/bis. :-) )
>=20
> Thanks,
>=20
> wfms

I would support this latter approach William: I think we should seek WG =
adoption of three drafts

1) the michaelson as112-ipv6 draft, aiming for at least one 01 spin to a =
small set of non-controversial V6 delegations, moving to WGLC and IANA =
asap.

2) your as112-ipv4-cull draft, but shorn of the operational aspects, =
likewise rapid movement to WGLC and IANA

3) an AS112 operational draft more in the nature of 6304/5/bis

I would like to ask for WG adoption of AS112-IPv6 on that basis.

cheers

-George


From geeohgeegeeoh@gmail.com  Tue Jul 26 10:52:55 2011
Return-Path: <geeohgeegeeoh@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 EE03321F8AB8 for <dnsop@ietfa.amsl.com>; Tue, 26 Jul 2011 10:52:55 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKhpbOv6xJSD for <dnsop@ietfa.amsl.com>; Tue, 26 Jul 2011 10:52:55 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id 56FF611E8124 for <dnsop@ietf.org>; Tue, 26 Jul 2011 10:52:52 -0700 (PDT)
Received: by pzk6 with SMTP id 6so1128695pzk.26 for <dnsop@ietf.org>; Tue, 26 Jul 2011 10:52:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=BzLYoJdtm+EtP6BH7yrub7YAxW3YFVBFcjbbveeBO48=; b=BUVpf/aLxooKug2DYZzFYi+dUNWunPo3Ojkc40ZAUXybSXoA7glLxOPaqDVXDtx7im v6XG6YQjMvtyv2qMAMlTMUeg/kuuHhcOvvl3DeOpvDhXCVrcrDjgICOJo/q2+UFFJYrw FLHC2o+E8S16p2xMI4gZrqf+0C9mEISUC0Qoc=
Received: by 10.68.50.41 with SMTP id z9mr1593082pbn.416.1311702770339; Tue, 26 Jul 2011 10:52:50 -0700 (PDT)
Received: from ?IPv6:2001:df8::80:e2f8:47ff:fe37:cff8? ([2001:df8:0:80:e2f8:47ff:fe37:cff8]) by mx.google.com with ESMTPS id l7sm782180pbh.26.2011.07.26.10.52.48 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jul 2011 10:52:48 -0700 (PDT)
Sender: George Michaelson <geeohgeegeeoh@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: George Michaelson <ggm@pobox.com>
In-Reply-To: <Pine.LNX.4.64.1107261343260.5948@ryouko.imsb.nrc.ca>
Date: Tue, 26 Jul 2011 13:52:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <14A9E773-6832-4E29-AA05-F6474B3FE708@algebras.org>
References: <Pine.LNX.4.64.1107261343260.5948@ryouko.imsb.nrc.ca>
To: wmaton@ryouko.imsb.nrc.ca
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 26 Jul 2011 15:03:35 -0700
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Further observationon AS112 ipv4 cull
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, 26 Jul 2011 17:52:56 -0000

On 26/07/2011, at 1:48 PM, William F. Maton Sotomayor wrote:

>=20
> All,
> 	As a data point, the original draft of -00 really started life =
as a straight copy of George's and Geoff's draft.  I was looking for a =
way to establish a procedure for sending instructions to IANA for new =
delegations to AS112 nodes, so they paved the way.  That said, I also =
don't have a problem with splitting my draft into 2:  One with the =
original set of instructions and another that could possibly either lead =
to a 'bis' for 6303 or become another document in a series of AS112 RFCs =
- much like RFC 6305 seems to be.
>=20
> (I'm more pragmatic in the sense that I'd like to see the instructions =
go forward faster than another Informational RFC/bis. :-) )
>=20
> Thanks,
>=20
> wfms

I would support this latter approach William: I think we should seek WG =
adoption of three drafts

1) the michaelson as112-ipv6 draft, aiming for at least one 01 spin to a =
small set of non-controversial V6 delegations, moving to WGLC and IANA =
asap.

2) your as112-ipv4-cull draft, but shorn of the operational aspects, =
likewise rapid movement to WGLC and IANA

3) an AS112 operational draft more in the nature of 6304/5/bis

I would like to ask for WG adoption of AS112-IPv6 on that basis.

cheers

-George


From gall@switch.ch  Wed Jul 27 08:19:23 2011
Return-Path: <gall@switch.ch>
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 0B56721F8A7B for <dnsop@ietfa.amsl.com>; Wed, 27 Jul 2011 08:19:23 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CuoUCDNQoQI7 for <dnsop@ietfa.amsl.com>; Wed, 27 Jul 2011 08:19:22 -0700 (PDT)
Received: from hadron.switch.ch (hadron.switch.ch [IPv6:2001:620:0:4:203:baff:fe4c:d99b]) by ietfa.amsl.com (Postfix) with ESMTP id 17C4D21F85F6 for <dnsop@ietf.org>; Wed, 27 Jul 2011 08:19:21 -0700 (PDT)
Received: from hadron.switch.ch (localhost [IPv6:::1]) by hadron.switch.ch (8.14.4+Sun/8.14.4) with ESMTP id p6RFJKrx002993 for <dnsop@ietf.org>; Wed, 27 Jul 2011 17:19:20 +0200 (CEST)
From: Alexander Gall <gall@switch.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <20016.11384.6998.748354@switch.ch>
Date: Wed, 27 Jul 2011 17:19:20 +0200
To: dnsop@ietf.org
X-Mailer: VM 7.18 under Emacs 22.1.1
Subject: [DNSOP] rfc4641bis algorithm rollover corner cases
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, 27 Jul 2011 15:19:23 -0000

I'm about to implement algorithm rollover according to section 4.1.5
of rfc4641bis into our homegrown DNSSEC key management system. In the
step named "new RRSIGs", the zone is supposed to include the signature
of DNSKEY_K_2 over the DNSKEY RRset containing DNSKEY_Z_1 and
DNSKEY_K_1.  The explanation for this is given as

  new RRSIGs:  The signatures made with the new key over all records in
      the zone are added, but the key itself is not.  This includes the
      signature for the DNSKEY RRset.  While in theory, the signatures
      of the keyset should always be synchronized with the keyset
      itself, it can be possible that RRSIGS are requested separately,
      so it is prudent to also sign the DNSKEY set with the new
      signature.

[Editorial: the last sentence should read "...to also sign the DNSKEY
set with the new key"]

I don't understand which corner case this is supposed to cover. The
relevant section of RFC4035 quoted in the draft says

    There MUST be an RRSIG for each RRset using at least one DNSKEY of
    each algorithm in the zone apex DNSKEY RRset.  The apex DNSKEY RRset
    itself MUST be signed by each algorithm appearing in the DS RRset
    located at the delegating parent (if any).

My understanding of this is that there is no requirement for the
existence of the signature over the DNSKEY RRset by K_2 until the end
of the step "new DNSKEY", because up to that point, the DS doesn't
refer to algorithm 2 yet.

The same reasoning appears to me to apply to the step "DNSKEY
removal".  At that point, the DS record refers only to algorithm 2 and
the old DS record has expired. Therefore, RRSIG_K_1(DNSKEY) should not
be needed either.

What am I missing?

-- 
Alex

From matthijs@NLnetLabs.nl  Wed Jul 27 09:04:14 2011
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 7D14211E8098 for <dnsop@ietfa.amsl.com>; Wed, 27 Jul 2011 09:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.375
X-Spam-Level: 
X-Spam-Status: No, score=-102.375 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oz6mFXoCYl5L for <dnsop@ietfa.amsl.com>; Wed, 27 Jul 2011 09:04:13 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 774B911E807E for <dnsop@ietf.org>; Wed, 27 Jul 2011 09:04:13 -0700 (PDT)
Received: from [2001:df8:0:16:215:afff:fed2:e121] ([IPv6:2001:df8:0:16:215:afff:fed2:e121]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p6RG3Xtw053107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jul 2011 18:04:10 +0200 (CEST) (envelope-from matthijs@NLnetLabs.nl)
Date: Wed, 27 Jul 2011 18:03:30 +0200 (CEST)
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
X-X-Sender: matje@minimeee
To: Alexander Gall <gall@switch.ch>
In-Reply-To: <alpine.DEB.2.00.1107271748560.1383@minimeee>
Message-ID: <alpine.DEB.2.00.1107271801500.1383@minimeee>
References: <20016.11384.6998.748354@switch.ch> <alpine.DEB.2.00.1107271748560.1383@minimeee>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Wed, 27 Jul 2011 18:04:10 +0200 (CEST)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] rfc4641bis algorithm rollover corner cases
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, 27 Jul 2011 16:04:14 -0000

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

Hi Alexander,

On Wed, 27 Jul 2011, Alexander Gall wrote:
>> I'm about to implement algorithm rollover according to section 4.1.5
>> of rfc4641bis into our homegrown DNSSEC key management system. In the
>> step named "new RRSIGs", the zone is supposed to include the signature
>> of DNSKEY_K_2 over the DNSKEY RRset containing DNSKEY_Z_1 and
>> DNSKEY_K_1.  The explanation for this is given as
>>
>>  new RRSIGs:  The signatures made with the new key over all records in
>>      the zone are added, but the key itself is not.  This includes the
>>      signature for the DNSKEY RRset.  While in theory, the signatures
>>      of the keyset should always be synchronized with the keyset
>>      itself, it can be possible that RRSIGS are requested separately,
>>      so it is prudent to also sign the DNSKEY set with the new
>>      signature.
>>
>> [Editorial: the last sentence should read "...to also sign the DNSKEY
>> set with the new key"]

Thanks.

>> I don't understand which corner case this is supposed to cover. The
>> relevant section of RFC4035 quoted in the draft says
>>
>>    There MUST be an RRSIG for each RRset using at least one DNSKEY of
>>    each algorithm in the zone apex DNSKEY RRset.  The apex DNSKEY RRset
>>    itself MUST be signed by each algorithm appearing in the DS RRset
>>    located at the delegating parent (if any).
>>
>> My understanding of this is that there is no requirement for the
>> existence of the signature over the DNSKEY RRset by K_2 until the end
>> of the step "new DNSKEY", because up to that point, the DS doesn't
>> refer to algorithm 2 yet.

My understanding of this paragraph is that there MUST be an RRSIG for
each RRset using at least one key of each algorithm in the DNSKEY RRset.
So that includes the DNSKEY RRset itself. *In addition*, the DNSKEY RRset 
MUST be signed with the algorithms appearing in the DS RRset.

The corner case tries to make clear that a DNSKEY RRset can be
treated as part of the chain of trust, but also can be treated as zone
content. In the latter case you want to make sure that the signatures
of the new algorithm are propagated before introducing the new DNSKEY.

Best regards,

Matthijs

>>
>> The same reasoning appears to me to apply to the step "DNSKEY
>> removal".  At that point, the DS record refers only to algorithm 2 and
>> the old DS record has expired. Therefore, RRSIG_K_1(DNSKEY) should not
>> be needed either.
>>
>> What am I missing?
>>
>> --
>> Alex
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJOMDbSAAoJEA8yVCPsQCW5eggH+wUOgX2l16gHGZjrQJpgshTh
ZRl8qF8NSyDrBXZB1/DVy57UWRhyP/lpAiQ/MFmwO+Y6ZnA+huxJAG8rb5VvmdNn
x5eJOjBkx/DHKVxKX89ove0m6oX92ollURuZmwX+QU6neD308aIdsD2jMgRosIdD
31Pv7DYyuL/X3BcbfK1Xyj2j3D93YpumLpeTgMdZePJwh50rAwvNw5oo2qmtvM2f
+3LnlsnlOZxCJbzMbkiEYqBOmozGg07mTrbMl5DQC8v3thcwc/Vl77G6M94ctPXE
sSjwygrQsZiTnr9KzAOUJrrHxsrpNi3/O31C64UGqRfVGu6Q4+mBRqdMf+utl58=
=zTXN
-----END PGP SIGNATURE-----

From gall@switch.ch  Wed Jul 27 11:58:28 2011
Return-Path: <gall@switch.ch>
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 3201A11E812F for <dnsop@ietfa.amsl.com>; Wed, 27 Jul 2011 11:58:28 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11jp385eYl+K for <dnsop@ietfa.amsl.com>; Wed, 27 Jul 2011 11:58:27 -0700 (PDT)
Received: from hadron.switch.ch (hadron.switch.ch [IPv6:2001:620:0:4:203:baff:fe4c:d99b]) by ietfa.amsl.com (Postfix) with ESMTP id 5B3BA11E80AD for <dnsop@ietf.org>; Wed, 27 Jul 2011 11:58:25 -0700 (PDT)
Received: from hadron.switch.ch (localhost [IPv6:::1]) by hadron.switch.ch (8.14.4+Sun/8.14.4) with ESMTP id p6RIwNhZ003383; Wed, 27 Jul 2011 20:58:23 +0200 (CEST)
To: Matthijs Mekking <matthijs@NLnetLabs.nl>
References: <20016.11384.6998.748354@switch.ch> <alpine.DEB.2.00.1107271748560.1383@minimeee> <alpine.DEB.2.00.1107271801500.1383@minimeee>
From: Alexander Gall <gall@switch.ch>
Date: Wed, 27 Jul 2011 20:58:23 +0200
In-Reply-To: <alpine.DEB.2.00.1107271801500.1383@minimeee> (Matthijs Mekking's message of "Wed\, 27 Jul 2011 18\:03\:30 +0200 \(CEST\)")
Message-ID: <9p8vrj5z5c.fsf@switch.ch>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (usg-unix-v)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] rfc4641bis algorithm rollover corner cases
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, 27 Jul 2011 18:58:28 -0000

Matthjis,

On Wed, 27 Jul 2011 18:03:30 +0200 (CEST), Matthijs Mekking <matthijs@NLnetLabs.nl> said:

> On Wed, 27 Jul 2011, Alexander Gall wrote:

>>> I don't understand which corner case this is supposed to cover. The
>>> relevant section of RFC4035 quoted in the draft says
>>> 
>>> There MUST be an RRSIG for each RRset using at least one DNSKEY of
>>> each algorithm in the zone apex DNSKEY RRset.  The apex DNSKEY RRset
>>> itself MUST be signed by each algorithm appearing in the DS RRset
>>> located at the delegating parent (if any).
>>> 
>>> My understanding of this is that there is no requirement for the
>>> existence of the signature over the DNSKEY RRset by K_2 until the end
>>> of the step "new DNSKEY", because up to that point, the DS doesn't
>>> refer to algorithm 2 yet.

> My understanding of this paragraph is that there MUST be an RRSIG for
> each RRset using at least one key of each algorithm in the DNSKEY RRset.
> So that includes the DNSKEY RRset itself. *In addition*, the DNSKEY RRset 
> MUST be signed with the algorithms appearing in the DS RRset.

Ok, so the snippet from 4035 alone appears to be ambigous to me.  Is
this clarified somewhere?

> The corner case tries to make clear that a DNSKEY RRset can be
> treated as part of the chain of trust, but also can be treated as zone
> content. In the latter case you want to make sure that the signatures
> of the new algorithm are propagated before introducing the new DNSKEY.

I sort of understand the intention.  But how *exactly* would it work?
Note that the "pre-published" signature in zone SOA_1 will differ from
that in zone SOA_2, because the DNSKEY RRset is not the same (this is
different from pre-published signatures by the ZSK, because the RRsets
themselves do not change). Suppose a validator happens to fetch the
DNSKEY RRset from SOA_2 but still has RRSIG_K_2(DNSKEY) from SOA_1 in
its cache.  I guess this is one of the corner cases, right? However,
wouldn't the validator be unable to verify that RRSIG because it
covers a different DNSKEY RRset (the one without Z_2 and K_2)?

It seems like to cover this case, you'd have to pre-publish the
signature of the DNSKEY RRset that will appear in SOA_2.  It's not
obvious to me whether this doesn't create problems of its own.

-- 
Alex

From wmaton@ryouko.imsb.nrc.ca  Wed Jul 27 19:08:33 2011
Return-Path: <wmaton@ryouko.imsb.nrc.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 3762C11E80FD for <dnsop@ietfa.amsl.com>; Wed, 27 Jul 2011 19:08: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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSQbUG0Js4Ol for <dnsop@ietfa.amsl.com>; Wed, 27 Jul 2011 19:08:32 -0700 (PDT)
Received: from ryouko.imsb.nrc.ca (ryouko.imsb.nrc.ca [IPv6:2604:8400:0:127::10]) by ietfa.amsl.com (Postfix) with ESMTP id 9555011E808E for <dnsop@ietf.org>; Wed, 27 Jul 2011 19:08:32 -0700 (PDT)
Received: from ryouko.imsb.nrc.ca (localhost [127.0.0.1]) by ryouko.imsb.nrc.ca (8.14.4/8.14.4) with ESMTP id p6S28Ekd030855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jul 2011 22:08:19 -0400
Received: from localhost (wmaton@localhost) by ryouko.imsb.nrc.ca (8.14.4/8.14.4/Submit) with ESMTP id p6S28ER7030852; Wed, 27 Jul 2011 22:08:14 -0400
Date: Wed, 27 Jul 2011 22:08:14 -0400 (EDT)
From: "William F. Maton Sotomayor" <wmaton@ryouko.imsb.nrc.ca>
To: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <EC39BC85-FC4B-4800-8805-C871D1525703@apnic.net>
Message-ID: <Pine.LNX.4.64.1107272205280.27844@ryouko.imsb.nrc.ca>
References: <Pine.LNX.4.64.1107261343260.5948@ryouko.imsb.nrc.ca> <EC39BC85-FC4B-4800-8805-C871D1525703@apnic.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Further observationon AS112 ipv4 cull
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: wmaton@ryouko.imsb.nrc.ca
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, 28 Jul 2011 02:08:33 -0000

On Tue, 26 Jul 2011, George Michaelson wrote:

> I would support this latter approach William: I think we should seek WG adoption of three drafts
>
> 1) the michaelson as112-ipv6 draft, aiming for at least one 01 spin to a small set of non-controversial V6 delegations, moving to WGLC and IANA asap.
>
> 2) your as112-ipv4-cull draft, but shorn of the operational aspects, likewise rapid movement to WGLC and IANA

For the consideration of members of DNSOP to adopt as a working group 
item, -01 of my draft has been submitted.

> 3) an AS112 operational draft more in the nature of 6304/5/bis

This one will follow a little later, I suspect more expanded than before.

> I would like to ask for WG adoption of AS112-IPv6 on that basis.

+1, especially since some as112 natives are getting restless.

Thanks,

wfms

From matthijs@NLnetLabs.nl  Thu Jul 28 10:29:49 2011
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 7246611E80E5 for <dnsop@ietfa.amsl.com>; Thu, 28 Jul 2011 10:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.42
X-Spam-Level: 
X-Spam-Status: No, score=-102.42 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IKe5pXQMjscD for <dnsop@ietfa.amsl.com>; Thu, 28 Jul 2011 10:29:48 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A9911E80D0 for <dnsop@ietf.org>; Thu, 28 Jul 2011 10:29:48 -0700 (PDT)
Received: from [2001:df8:0:16:215:afff:fed2:e121] ([IPv6:2001:df8:0:16:215:afff:fed2:e121]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p6SHTYBq093860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2011 19:29:46 +0200 (CEST) (envelope-from matthijs@NLnetLabs.nl)
Date: Thu, 28 Jul 2011 19:29:31 +0200 (CEST)
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
X-X-Sender: matje@minimeee
To: Alexander Gall <gall@switch.ch>
In-Reply-To: <9p8vrj5z5c.fsf@switch.ch>
Message-ID: <alpine.DEB.2.00.1107272122170.1357@minimeee>
References: <20016.11384.6998.748354@switch.ch> <alpine.DEB.2.00.1107271748560.1383@minimeee> <alpine.DEB.2.00.1107271801500.1383@minimeee> <9p8vrj5z5c.fsf@switch.ch>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 28 Jul 2011 19:29:46 +0200 (CEST)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] rfc4641bis algorithm rollover corner cases
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, 28 Jul 2011 17:29:49 -0000

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


On Wed, 27 Jul 2011, Alexander Gall wrote:

> Matthjis,
>
> On Wed, 27 Jul 2011 18:03:30 +0200 (CEST), Matthijs Mekking <matthijs@NLnetLabs.nl> said:
>
>> On Wed, 27 Jul 2011, Alexander Gall wrote:
>
>>>> I don't understand which corner case this is supposed to cover. The
>>>> relevant section of RFC4035 quoted in the draft says
>>>>
>>>> There MUST be an RRSIG for each RRset using at least one DNSKEY of
>>>> each algorithm in the zone apex DNSKEY RRset.  The apex DNSKEY RRset
>>>> itself MUST be signed by each algorithm appearing in the DS RRset
>>>> located at the delegating parent (if any).
>>>>
>>>> My understanding of this is that there is no requirement for the
>>>> existence of the signature over the DNSKEY RRset by K_2 until the end
>>>> of the step "new DNSKEY", because up to that point, the DS doesn't
>>>> refer to algorithm 2 yet.
>
>> My understanding of this paragraph is that there MUST be an RRSIG for
>> each RRset using at least one key of each algorithm in the DNSKEY RRset.
>> So that includes the DNSKEY RRset itself. *In addition*, the DNSKEY RRset
>> MUST be signed with the algorithms appearing in the DS RRset.
>
> Ok, so the snippet from 4035 alone appears to be ambigous to me.  Is
> this clarified somewhere?

Perhaps draft-ietf-dnsext-dnssec-bis-updates can add that clarification, 
if appropriate.

>
>> The corner case tries to make clear that a DNSKEY RRset can be
>> treated as part of the chain of trust, but also can be treated as zone
>> content. In the latter case you want to make sure that the signatures
>> of the new algorithm are propagated before introducing the new DNSKEY.
>
> I sort of understand the intention.  But how *exactly* would it work?
> Note that the "pre-published" signature in zone SOA_1 will differ from
> that in zone SOA_2, because the DNSKEY RRset is not the same (this is
> different from pre-published signatures by the ZSK, because the RRsets
> themselves do not change).

It's about pre-publishing the algorithm. But I now see what you mean and 
I think you are right. The corner case does not actually need these 
special considerations. The algorithm rollover described as it is now is 
not wrong, it just adds a redundant signature in the 'new RRSIGs' step.

Thanks for the catch.

> Suppose a validator happens to fetch the
> DNSKEY RRset from SOA_2 but still has RRSIG_K_2(DNSKEY) from SOA_1 in
> its cache.

Can this even happen? It is my understanding that if you have to fetch a 
new copy of the DNSKEY RRset, you automatically would get the 
corresponding signatures.

> I guess this is one of the corner cases, right? However,
> wouldn't the validator be unable to verify that RRSIG because it
> covers a different DNSKEY RRset (the one without Z_2 and K_2)?

If a validator would be able to get in this situation, yes. But I don't 
think this is possible.

> It seems like to cover this case, you'd have to pre-publish the
> signature of the DNSKEY RRset that will appear in SOA_2.  It's not
> obvious to me whether this doesn't create problems of its own.

That sounds very complex to me too.

I think in order to fix the document, the text about the corner case 
should be removed, as well as the redundant signature in the rollover 
figure.


Best regards,

Matthijs

>
> -- 
> Alex
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJOMZx7AAoJEA8yVCPsQCW5HdoIAI/z7o/0A3+PYMifE/kakdYE
LdM2080SQ590kTHXWKzWUdBGL8GJKmqGdDVGNbTn0W0njK9gEHDx4A1FQHr4EPj9
Ze464ZbGmkcyGKxaqvVVAYvj6JI+/spXH0UZNvQOCT73NZYL/IHAJeRx0xXjF1oq
R8g4Y7gepN424092bET91m7BJDBYzhQ5spBAlT6zHR8XvKnTHZM02gx8Zp95CEAq
BuxWd7ZJVE+Du1nimaeCmvK1DgWUCv6+4m81ICtXFECo+ER3ROmiGUFGDcsso6qa
W5s8lm4PKphr0KIg5pRsOjn5NLnn2XDqJ5ZEDZyimDhj4xeFf7JdCg2pUOE3XNg=
=9XvF
-----END PGP SIGNATURE-----

From matthijs@NLnetLabs.nl  Thu Jul 28 10:32:56 2011
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 DA55C21F8C2A for <dnsop@ietfa.amsl.com>; Thu, 28 Jul 2011 10:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGEa7+q1A3kn for <dnsop@ietfa.amsl.com>; Thu, 28 Jul 2011 10:32:56 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0CC21F8C13 for <dnsop@ietf.org>; Thu, 28 Jul 2011 10:32:51 -0700 (PDT)
Received: from [2001:df8:0:16:215:afff:fed2:e121] ([IPv6:2001:df8:0:16:215:afff:fed2:e121]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p6SHWlxJ099531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2011 19:32:49 +0200 (CEST) (envelope-from matthijs@NLnetLabs.nl)
Date: Thu, 28 Jul 2011 19:32:42 +0200 (CEST)
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
X-X-Sender: matje@minimeee
To: dnsop@ietf.org
Message-ID: <alpine.DEB.2.00.1107272155480.1357@minimeee>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 28 Jul 2011 19:32:50 +0200 (CEST)
Cc: Michael StJohns <msj@nthpermutation.com>
Subject: [DNSOP] <draft-ietf-dnsop-dnssec-key-timing-02> Interaction with Configured Trust Anchors
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, 28 Jul 2011 17:32:57 -0000

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

Hi,

I am questioning if the duration of 30 days with respect to adding a KSK 
is the absolute correct value. The 30 days is a validator parameter that 
says a trust anchor must stay in the AddPend state for that amount of time 
before it may actually be used as trust anchor. The new KSK must 
be pre-published two times the Active Refresh, as defined in RFC 5011. 
Roughly, this is indeed 30 days at most.

However, one does not know whether the validator failed to do an 
Active Refresh. If you take into account the retryTime (which is at most 
an hour), the Active Refresh can go up more than 15 days. Suppose a query 
fails just once, the maximum value of the Active Refresh is 15d 1h.

A more accurate value for the add hold-down time at the server side would
be 2 times Active Refresh:

 	Active Refresh = (queryInterval + x * retryTime)

where x is the the number of queries failed. Perhaps adding a Dta, the 
delay between the query and the trust anchor set is actually updated, for 
additional safety.

Also, the remove hold-down time is a validator parameter that can't be 
taken exactly as a value for the server side. Actually, the validator only 
has to see the revoked key once in order to remove it from the set of 
trust anchors. So the remove hold-down time at the server side would be 
only one time the Active Refresh.

By the way, why RFC 5011 says the server needs to keep the revoked key for 
remove hold-down time in the zone, I don't know.

Best regards,

Matthijs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJOMZ06AAoJEA8yVCPsQCW544oH/RnCjsrVQHDbAD5X6cYPeNHF
xWdYDu+5d/28NnY9qt8UxVZ05125ZkKYgZ/3JZQlwpHH6+l4txnnT/3sbkFhRG/X
8NS8XdUf70yYd3aZp3jRAC6zseUyZJ1P232SOLjlUDu1Z/mgtZ1M2m/pAVrcgyBR
n0IBOrb2Ay4z2PJ2EixxcM0ehdsglDkdV7lCrIWKNb1MCfU4u5RdCbehiuouvtiv
a26C9y66xC9bGvh4vmp/+KbKToUvPoDWp1mhBWG3Kn8CKka7cO8Eb5cyea5ktck0
wXvPZUrxyWmO6DoE6ZDYuVa1YjKKJUWpt2IpWevNQKMZ9aYDFZz8X1AHloyCH/Y=
=ge57
-----END PGP SIGNATURE-----

From warren@kumari.net  Thu Jul 28 11:12:00 2011
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 A80F711E8121 for <dnsop@ietfa.amsl.com>; Thu, 28 Jul 2011 11:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhv7vblmZ+at for <dnsop@ietfa.amsl.com>; Thu, 28 Jul 2011 11:12:00 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id EC4AC11E811F for <dnsop@ietf.org>; Thu, 28 Jul 2011 11:11:49 -0700 (PDT)
Received: from dhcp-227f.meeting.ietf.org (dhcp-227f.meeting.ietf.org [130.129.34.127]) by vimes.kumari.net (Postfix) with ESMTPSA id 670781B4169F; Thu, 28 Jul 2011 14:11:42 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <Pine.LNX.4.64.1107272205280.27844@ryouko.imsb.nrc.ca>
Date: Thu, 28 Jul 2011 14:11:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A57E061-CBA4-431C-B2A4-0C148EA44A9C@kumari.net>
References: <Pine.LNX.4.64.1107261343260.5948@ryouko.imsb.nrc.ca> <EC39BC85-FC4B-4800-8805-C871D1525703@apnic.net> <Pine.LNX.4.64.1107272205280.27844@ryouko.imsb.nrc.ca>
To: wmaton@ryouko.imsb.nrc.ca
X-Mailer: Apple Mail (2.1084)
Cc: dnsop@ietf.org, George Michaelson <ggm+ietf@apnic.net>
Subject: Re: [DNSOP] Further observationon AS112 ipv4 cull
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, 28 Jul 2011 18:12:00 -0000

On Jul 27, 2011, at 10:08 PM, William F. Maton Sotomayor wrote:

> On Tue, 26 Jul 2011, George Michaelson wrote:
>=20
>> I would support this latter approach William: I think we should seek =
WG adoption of three drafts
>>=20
>> 1) the michaelson as112-ipv6 draft, aiming for at least one 01 spin =
to a small set of non-controversial V6 delegations, moving to WGLC and =
IANA asap.
>>=20
>> 2) your as112-ipv4-cull draft, but shorn of the operational aspects, =
likewise rapid movement to WGLC and IANA
>=20
> For the consideration of members of DNSOP to adopt as a working group =
item, -01 of my draft has been submitted.
>=20
>> 3) an AS112 operational draft more in the nature of 6304/5/bis
>=20
> This one will follow a little later, I suspect more expanded than =
before.
>=20
>> I would like to ask for WG adoption of AS112-IPv6 on that basis.
>=20
> +1, especially since some as112 natives are getting restless.
>=20

I made a suggestion at the mic in the f2f meeting, and then on the as112 =
operators list -- there seems to be some support for it there, so I'm =
now doing it onlist=85

How about simply making AS112 omniscient (know the answers for *all* =
space)? As decisions to have AS112 answer / not answer for zones get =
made, delegations can simply be added and removed.=20

Obviously this would require synthesizing answers[0], and these servers =
cannot be used for answering recursive queries (and a few other minor =
issues) but this will (as far as I can see) solve the lameness / =
coordination issues...


W

[0]: Yes, yes i *did* feel dirty writing that=85.


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


From bmanning@karoshi.com  Thu Jul 28 11:30:28 2011
Return-Path: <bmanning@karoshi.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 A2AAB21F896E for <dnsop@ietfa.amsl.com>; Thu, 28 Jul 2011 11:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.609
X-Spam-Level: 
X-Spam-Status: No, score=-4.609 tagged_above=-999 required=5 tests=[AWL=-1.935, BAYES_00=-2.599, MIME_ASCII0=1.5, NULL_IN_BODY=2.425, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqP-qVZkNQ4E for <dnsop@ietfa.amsl.com>; Thu, 28 Jul 2011 11:30:28 -0700 (PDT)
Received: from vacation.karoshi.com (vacation.karoshi.com [198.32.6.68]) by ietfa.amsl.com (Postfix) with ESMTP id 15E6321F8507 for <dnsop@ietf.org>; Thu, 28 Jul 2011 11:30:28 -0700 (PDT)
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id p6SITAmw002369; Thu, 28 Jul 2011 18:29:10 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id p6SIT9Z4002368; Thu, 28 Jul 2011 18:29:09 GMT
Date: Thu, 28 Jul 2011 18:29:09 +0000
From: bmanning@vacation.karoshi.com
To: Warren Kumari <warren@kumari.net>
Message-ID: <20110728182909.GA2349@vacation.karoshi.com.>
References: <Pine.LNX.4.64.1107261343260.5948@ryouko.imsb.nrc.ca> <EC39BC85-FC4B-4800-8805-C871D1525703@apnic.net> <Pine.LNX.4.64.1107272205280.27844@ryouko.imsb.nrc.ca> <7A57E061-CBA4-431C-B2A4-0C148EA44A9C@kumari.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <7A57E061-CBA4-431C-B2A4-0C148EA44A9C@kumari.net>
User-Agent: Mutt/1.4.1i
Cc: George Michaelson <ggm+ietf@apnic.net>, dnsop@ietf.org
Subject: Re: [DNSOP] Further observationon AS112 ipv4 cull
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, 28 Jul 2011 18:30:28 -0000

On Thu, Jul 28, 2011 at 02:11:41PM -0400, Warren Kumari wrote:
> 
> On Jul 27, 2011, at 10:08 PM, William F. Maton Sotomayor wrote:
> 
> > On Tue, 26 Jul 2011, George Michaelson wrote:
> > 
> >> I would support this latter approach William: I think we should seek WG adoption of three drafts
> >> 
> >> 1) the michaelson as112-ipv6 draft, aiming for at least one 01 spin to a small set of non-controversial V6 delegations, moving to WGLC and IANA asap.
> >> 
> >> 2) your as112-ipv4-cull draft, but shorn of the operational aspects, likewise rapid movement to WGLC and IANA
> > 
> > For the consideration of members of DNSOP to adopt as a working group item, -01 of my draft has been submitted.
> > 
> >> 3) an AS112 operational draft more in the nature of 6304/5/bis
> > 
> > This one will follow a little later, I suspect more expanded than before.
> > 
> >> I would like to ask for WG adoption of AS112-IPv6 on that basis.
> > 
> > +1, especially since some as112 natives are getting restless.
> > 
> 
> I made a suggestion at the mic in the f2f meeting, and then on the as112 operators list -- there seems to be some support for it there, so I'm now doing it onlistb &
> 
> How about simply making AS112 omniscient (know the answers for *all* space)? As decisions to have AS112 answer / not answer for zones get made, delegations can simply be added and removed. 
> 
> Obviously this would require synthesizing answers[0], and these servers cannot be used for answering recursive queries (and a few other minor issues) but this will (as far as I can see) solve the lameness / coordination issues...
> 
> 
> W
> 
> [0]: Yes, yes i *did* feel dirty writing thatb &.
> 
> 
> > Thanks,
> > 
> > wfms
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
> > 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
>



	been there, done that.  before ICANN existed, I ran the RFC 1918 auth servers.
	put in a wild card TXT "Please read RFC 1918" to any/every query.  20min later
	after the university pres had fielded calls fm industry about being hacked- we removed
	the wildcard...  until leaking DNS queris fm private netsinto the Internetcan
be stopped, you can't reliably anwer the queries.

/bill

From gall@switch.ch  Fri Jul 29 00:24:08 2011
Return-Path: <gall@switch.ch>
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 2A6D821F877F for <dnsop@ietfa.amsl.com>; Fri, 29 Jul 2011 00:24: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIgvApPdpTnM for <dnsop@ietfa.amsl.com>; Fri, 29 Jul 2011 00:24:07 -0700 (PDT)
Received: from hadron.switch.ch (hadron.switch.ch [IPv6:2001:620:0:4:203:baff:fe4c:d99b]) by ietfa.amsl.com (Postfix) with ESMTP id 30DC721F877D for <dnsop@ietf.org>; Fri, 29 Jul 2011 00:24:06 -0700 (PDT)
Received: from hadron.switch.ch (localhost [IPv6:::1]) by hadron.switch.ch (8.14.4+Sun/8.14.4) with ESMTP id p6T7O45U014163; Fri, 29 Jul 2011 09:24:04 +0200 (CEST)
From: Alexander Gall <gall@switch.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <20018.24596.413763.513556@switch.ch>
Date: Fri, 29 Jul 2011 09:24:04 +0200
To: Matthijs Mekking <matthijs@NLnetLabs.nl>
In-Reply-To: <alpine.DEB.2.00.1107272122170.1357@minimeee>
References: <20016.11384.6998.748354@switch.ch> <alpine.DEB.2.00.1107271748560.1383@minimeee> <alpine.DEB.2.00.1107271801500.1383@minimeee> <9p8vrj5z5c.fsf@switch.ch> <alpine.DEB.2.00.1107272122170.1357@minimeee>
X-Mailer: VM 7.18 under Emacs 22.1.1
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] rfc4641bis algorithm rollover corner cases
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, 29 Jul 2011 07:24:08 -0000

On Thu, 28 Jul 2011 19:29:31 +0200 (CEST), Matthijs Mekking <matthijs@NLnetLabs.nl> said:

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


> On Wed, 27 Jul 2011, Alexander Gall wrote:

>> Matthjis,
>> 
>> On Wed, 27 Jul 2011 18:03:30 +0200 (CEST), Matthijs Mekking <matthijs@NLnetLabs.nl> said:
>> 
>>> On Wed, 27 Jul 2011, Alexander Gall wrote:
>> 
>> 
>>> The corner case tries to make clear that a DNSKEY RRset can be
>>> treated as part of the chain of trust, but also can be treated as zone
>>> content. In the latter case you want to make sure that the signatures
>>> of the new algorithm are propagated before introducing the new DNSKEY.
>> 
>> I sort of understand the intention.  But how *exactly* would it work?
>> Note that the "pre-published" signature in zone SOA_1 will differ from
>> that in zone SOA_2, because the DNSKEY RRset is not the same (this is
>> different from pre-published signatures by the ZSK, because the RRsets
>> themselves do not change).

> It's about pre-publishing the algorithm. But I now see what you mean and 
> I think you are right. The corner case does not actually need these 
> special considerations. The algorithm rollover described as it is now is 
> not wrong, it just adds a redundant signature in the 'new RRSIGs' step.

Ok. In other words, there is no point in publishing signatures over
the DNSKEY RRset by a key that is not part of that RRset itself,
right? Seems to me that RRSIG_K_1(DNSKEY) should be removed from the
"DNSKEY removal" step as well.

-- 
Alex

From matthijs@NLnetLabs.nl  Fri Jul 29 08:15:05 2011
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 B1F0121F8C88 for <dnsop@ietfa.amsl.com>; Fri, 29 Jul 2011 08:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEck+vrHsjfJ for <dnsop@ietfa.amsl.com>; Fri, 29 Jul 2011 08:15:04 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D16921F8BF3 for <dnsop@ietf.org>; Fri, 29 Jul 2011 08:15:04 -0700 (PDT)
Received: from [2001:df8:0:16:215:afff:fed2:e121] ([IPv6:2001:df8:0:16:215:afff:fed2:e121]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p6TFEoPr083002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jul 2011 17:15:01 +0200 (CEST) (envelope-from matthijs@NLnetLabs.nl)
Date: Fri, 29 Jul 2011 17:14:44 +0200 (CEST)
From: Matthijs Mekking <matthijs@NLnetLabs.nl>
X-X-Sender: matje@minimeee
To: Alexander Gall <gall@switch.ch>
In-Reply-To: <20018.24596.413763.513556@switch.ch>
Message-ID: <alpine.DEB.2.00.1107291713390.1441@minimeee>
References: <20016.11384.6998.748354@switch.ch> <alpine.DEB.2.00.1107271748560.1383@minimeee> <alpine.DEB.2.00.1107271801500.1383@minimeee> <9p8vrj5z5c.fsf@switch.ch> <alpine.DEB.2.00.1107272122170.1357@minimeee> <20018.24596.413763.513556@switch.ch>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Fri, 29 Jul 2011 17:15:02 +0200 (CEST)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] rfc4641bis algorithm rollover corner cases
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, 29 Jul 2011 15:15:05 -0000

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



On Fri, 29 Jul 2011, Alexander Gall wrote:

> On Thu, 28 Jul 2011 19:29:31 +0200 (CEST), Matthijs Mekking <matthijs@NLnetLabs.nl> said:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>
>
>> On Wed, 27 Jul 2011, Alexander Gall wrote:
>
>>> Matthjis,
>>>
>>> On Wed, 27 Jul 2011 18:03:30 +0200 (CEST), Matthijs Mekking <matthijs@NLnetLabs.nl> said:
>>>
>>>> On Wed, 27 Jul 2011, Alexander Gall wrote:
>>>
>>>
>>>> The corner case tries to make clear that a DNSKEY RRset can be
>>>> treated as part of the chain of trust, but also can be treated as zone
>>>> content. In the latter case you want to make sure that the signatures
>>>> of the new algorithm are propagated before introducing the new DNSKEY.
>>>
>>> I sort of understand the intention.  But how *exactly* would it work?
>>> Note that the "pre-published" signature in zone SOA_1 will differ from
>>> that in zone SOA_2, because the DNSKEY RRset is not the same (this is
>>> different from pre-published signatures by the ZSK, because the RRsets
>>> themselves do not change).
>
>> It's about pre-publishing the algorithm. But I now see what you mean and
>> I think you are right. The corner case does not actually need these
>> special considerations. The algorithm rollover described as it is now is
>> not wrong, it just adds a redundant signature in the 'new RRSIGs' step.
>
> Ok. In other words, there is no point in publishing signatures over
> the DNSKEY RRset by a key that is not part of that RRset itself,
> right? Seems to me that RRSIG_K_1(DNSKEY) should be removed from the
> "DNSKEY removal" step as well.

Yes, I have proposed pending changes here:

http://tools.ietf.org//rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-dnsop-rfc4641bis-07.txt&url2=http://www.nlnetlabs.nl/~matje/draft-ietf-dnsop-rfc4641bis.txt

>
> -- 
> Alex
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJOMs5kAAoJEA8yVCPsQCW5U6UH/2DwgaI66rQstxLAlbfXAJQH
LZ95u9oCVCoz7QhPRmgB+hnIGrthX9hOZ9+UYimw7J7YTw37lb2hWFhA+xIasW0M
B+UsGJUUhTl+GceTebTscAs+i/JKWqcFZ/EFwpAEAGrlmdRsEGFblsYXUSLnEe0k
uayS4nSrNfhhBIqtZWW5uExR7giWzcA5kVlgR1X0NPK1OM+/RW7yGNgIumucVWPT
Uukz19QzI5WiwtkBrXI6JmVpTeCUrIRyOGaarJYMq0195Zece0wZRPzw6ACP7uzh
p41ULzHt41HmYCosGPcIXkSuBetY9Grws0J290Sk/x/nQ8XmprXNk5fhFustN+A=
=vmMM
-----END PGP SIGNATURE-----
