Re: [DNSOP] Request to DNSOP chairs for a WGLC on draft-ietf-dnsop-kskroll-sentinel-11.txt

"Paul Hoffman" <paul.hoffman@vpnc.org> Thu, 05 April 2018 11:30 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9F2F12711E; Thu, 5 Apr 2018 04:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WgsaMT7Gc6Fb; Thu, 5 Apr 2018 04:30:11 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F88B126CD8; Thu, 5 Apr 2018 04:30:11 -0700 (PDT)
Received: from [10.47.60.116] (107-181-97-2.i95.net [107.181.97.2] (may be forged)) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id w35BSLXg094376 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Apr 2018 04:29:18 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 107-181-97-2.i95.net [107.181.97.2] (may be forged) claimed to be [10.47.60.116]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Job Snijders <job@ntt.net>
Cc: Geoff Huston <gih902@gmail.com>, dnsop-chairs@ietf.org, dnsop <dnsop@ietf.org>
Date: Thu, 05 Apr 2018 07:25:30 -0400
X-Mailer: MailMate (1.11r5462)
Message-ID: <3BCEB42E-7B78-4B6D-A448-26A87B0D8427@vpnc.org>
In-Reply-To: <20180405094458.GH1327@hanna.meerval.net>
References: <152288329070.25818.12838172797356007039@ietfa.amsl.com> <09A2491B-270E-4D98-B696-E9023558E0DC@gmail.com> <20180405094458.GH1327@hanna.meerval.net>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0DpscGENK-WKNAYtD2uLlpcOqcw>
Subject: Re: [DNSOP] Request to DNSOP chairs for a WGLC on draft-ietf-dnsop-kskroll-sentinel-11.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Apr 2018 11:30:13 -0000

On 5 Apr 2018, at 5:44, Job Snijders wrote:

> Dear kskroll sentinel authors, working group,
>
> On Thu, Apr 05, 2018 at 11:45:18AM +1000, Geoff Huston wrote:
>> With the submission of the -11 version of this draft the authors are
>> of the view that all WG comments have been discussed, and we think we
>> are now ready for a WG Last Call on this document.
>
> I believe that a crucial step in the advancement of any document in
> DNSOP, including this one, is to demonstrate the specification is 
> fully
> understood by ensuring multiple implementations exist.
>
> a) I recommend adding a RFC 7942 section to the document. Optionally
> this section can be removed upon publication.
>
> b) Implementations should document their compliance with this
> specification at 
> https://trac.ietf.org/trac/dnsop/wiki/draft-ietf-dnsop-kskroll-sentinel
>
> For each normative term there should be an appropiate interop /
> compliance test.
>
> For instance section 3.1 in essence is a test description. The last
> paragraph of Section 3.2 also contains what hints to a specific test
> scenario.
>
> c) 2119 was updated by 8174, i see must/should in lower case and 
> wonder
> whether there were normative intentions. Reviewing the lower cases 
> 2119
> terms may yield additional test cases.
>
> My personal view is that if no implemenation reports are readily
> available, it may be too early for WGLC.

In addition, the draft still has Section 2 at the front of the document 
instead in an appendix, but it also says that it will be an appendix 
when published. If the authors expect implementers to be able to 
implement with that section as an appendix, it should be moved there 
now, not later; otherwise, take out the text that says it will be an 
appendix.

--Paul Hoffman