Re: Last Call: <draft-iab-2870bis-01.txt> (DNS Root Name Service Protocol and Deployment Requirements) to Best Current Practice

SM <sm+ietf@elandsys.com> Thu, 22 May 2014 19:04 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 347271A02EE for <ietf@ietfa.amsl.com>; Thu, 22 May 2014 12:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level:
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IuGEDU94goVI for <ietf@ietfa.amsl.com>; Thu, 22 May 2014 12:04:43 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F671A02D5 for <ietf@ietf.org>; Thu, 22 May 2014 12:04:43 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.142.195]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s4MJ4GQc029463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 May 2014 12:04:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1400785470; bh=jXKkHz1p5uujAVLQfF/uqCPFsWKSyoSqWhJtZ7i97gA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xAzZgtoK84aNScHGM7xiuo3i1zp1gDIaCUw03RNkZivK31NS3x6Yy0XY0ZR6a91if R0kdicngQ6rnaEPNm58YiC6H8arrSPBQAHiYyLhDtWtxW4a6PBq/y9LgvKoBYOTp0L fsvUBjv6cpDk/VwnfVRSdJcoq5XotIQopzyH41Mw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1400785470; i=@elandsys.com; bh=jXKkHz1p5uujAVLQfF/uqCPFsWKSyoSqWhJtZ7i97gA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hBfqUAayXbwby58M+/TkZLlGGfe3IkmV76LNH0YF3DjoXVBzpzWoR/tszS6dMihzz glVBk+oxBcBgzwD8uLp+8qpOB08hj2Bt3DuJnkzamT8we7HbRsg1TH1fkl8a5DJY/q gDJm2aoXIKGl9PfbuBJOfU9fQRHaupzL90UcBHKY=
Message-Id: <6.2.5.6.2.20140522095317.0c5fd648@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 22 May 2014 11:56:47 -0700
To: Joe Abley <jabley@hopcount.ca>
From: SM <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-iab-2870bis-01.txt> (DNS Root Name Service Protocol and Deployment Requirements) to Best Current Practice
In-Reply-To: <1111FB79-012A-414B-B8CD-0BBDAE8BD6A8@hopcount.ca>
References: <20140520204238.21772.64347.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140521194638.06eaf508@resistor.net> <1111FB79-012A-414B-B8CD-0BBDAE8BD6A8@hopcount.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DG24jfB2GdVDlk1cGbVQHzZ0SWw
Cc: ietf@ietf.org, liman@netnod.se
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 19:04:44 -0000

Hi Joe,
At 09:34 22-05-2014, Joe Abley wrote:
>Some reaction to your comments below, plus a comment of my own. I'll 
>note that I am not a root server operator, although in the past I 
>have played one on TV. My comments on your

Ok. :-)

>I understand that RSSAC have made recent progress on that document, 
>and that it will appear soon. I would presume that the RFC Editor 
>would hold final publication of this document, once approved, until 
>that reference showed up, as is the case for references to IETF 
>documents. I don't know whether that's a good presumption though. I 
>just thought I'd mention it as a plausible workflow.

I would usually be okay with the workflow.  The referenced document 
is currently a forward-looking statement.  I suggest delaying the 
IESG approval until that document is available or else changing the 
text in the draft to reflect the current state of affairs.

>At any time many parts of the Internet are unreachable from other 
>parts of the Internet, for many reasons unrelated to specifications 
>(national issues, cable breaks, failures in particular networks, 
>peering disputes, etc.)
>
>I'll note that the document describes requirements for the 
>*service*, not for any particular component of the service.

Yes.

>So I think this concern is orthogonal to the purpose and contents of 
>this document.

I mentioned this as long-running problems provides material for 
non-technical arguments.

>I actually think that it makes sense to separate the requirements 
>for the root name *service* from the contents of the root zone that 
>is being served. The document requires the service to support DNSSEC 
>(which I think is right and proper), and has nothing to say about 
>the contents of the root zone (which again, I think is right and proper).

Section 3 broaches the topic of "contents of the Root Zone".  I read 
some past comments from the IAB about DNSSEC.  The terms used were 
"implementation" and "deployment".  It looks like the requirement 
fits in this draft.

Regards,
S. Moonesamy