Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-02.txt

Jim Lahey <jim_lahey@outlook.com> Thu, 11 July 2013 22:00 UTC

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

Hello for the first time!

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

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

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

jl