Re: [DNSOP] extended deadline Re: WGLC for draft-ietf-dnsop-alt-tld

"Paul Hoffman" <paul.hoffman@vpnc.org> Mon, 10 April 2017 17:35 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 BA11F120227 for <dnsop@ietfa.amsl.com>; Mon, 10 Apr 2017 10:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 UTMQlWu0aJe0 for <dnsop@ietfa.amsl.com>; Mon, 10 Apr 2017 10:35:17 -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 81E6B129A9D for <dnsop@ietf.org>; Mon, 10 Apr 2017 10:35:15 -0700 (PDT)
Received: from [169.254.150.39] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v3AHYwKI026490 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Apr 2017 10:34:59 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [169.254.150.39]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Ralph Droms" <rdroms.ietf@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Date: Mon, 10 Apr 2017 10:35:12 -0700
Message-ID: <A2F22AAF-6FC4-40AB-A96D-599F5C2F4E41@vpnc.org>
In-Reply-To: <2CB23C57-AB73-483B-AE9F-834A933D3EC6@gmail.com>
References: <333CCE99-82E2-44C9-97ED-2222540097ED@gmail.com> <20170401201727.GA5948@laperouse.bortzmeyer.org> <D3AA90CF-667A-4C4D-8ABF-DB8242E31A1D@gmail.com> <2CB23C57-AB73-483B-AE9F-834A933D3EC6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2cStxMy1oOCHf8t4DjPbjF1lBGA>
Subject: Re: [DNSOP] extended deadline Re: WGLC for draft-ietf-dnsop-alt-tld
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: Mon, 10 Apr 2017 17:35:20 -0000

On 10 Apr 2017, at 7:38, Ralph Droms wrote:

> I see that draft-ietf-dnsop-alt-tld-08 gives the intended status of 
> the document as Informational, while it is listed in the datatracker 
> as "In WG Last Call: Proposed Standard".
>
> There are arguments in favor of each status.  The relevant text is in 
> section 5 of RFC 6761:
>
>    An IETF "Standards Action" or "IESG Approval" document specifying
>    some new naming behaviour, which requires a Special-Use Domain Name
>    be reserved to implement this desired new behaviour, needs to 
> contain
>    a subsection of the "IANA Considerations" section titled "Domain 
> Name
>    Reservation Considerations" giving answers in the seven categories
>    listed below.
>
> Publishing draft-ietf-dnsop-alt-tld-08 as Proposed Standard meets the 
> "Standards Action" requirement.  However, Proposed Standard may not be 
> appropriate for draft-ietf-dnsop-alt-tld-08, as the document does not 
> specify a new protocol, as such.  draft-ietf-dnsop-alt-tld-08 does 
> specify certain behaviors for components of the Internet, which could 
> be thought of as providing for interoperability so that Proposed 
> Standard status would be appropriate.
>
> On the other hand, publishing draft-ietf-dnsop-alt-tld-08 as 
> Informational would require an "IESG Approval" document to meet the 
> requirements of RFC 6761.  A short sentence added to 
> draft-ietf-dnsop-alt-tld-08 is likely all that would be needed, to the 
> effect of "The IESG has reviewed this document and approves of the 
> request to add .alt to the Special Use Domain Names registry."
>
> In any event, in my opinion the WG needs to express its explicit 
> consensus about its choice of intended status for 
> draft-ietf-dnsop-alt-tld-08.

Given that most people don't understand the difference between levels, 
it would take less explanation to make this Standards Track to meet 
"Standards Action" in RFC 6761. But if people want to leave this as 
Informational, I agree with Ralph that a sentence like he has given 
(probably at the end of the Introduction) would be needed for clarity.

--Paul Hoffman