Re: [DNSOP] I-D Action: draft-ietf-dnsop-sutld-ps-03.txt

Ralph Droms <rdroms.ietf@gmail.com> Tue, 21 March 2017 12:24 UTC

Return-Path: <rdroms.ietf@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 44C391297C4 for <dnsop@ietfa.amsl.com>; Tue, 21 Mar 2017 05:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2ustTIwK_MN3 for <dnsop@ietfa.amsl.com>; Tue, 21 Mar 2017 05:24:01 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D3B21297EC for <dnsop@ietf.org>; Tue, 21 Mar 2017 05:24:01 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id r45so129108842qte.3 for <dnsop@ietf.org>; Tue, 21 Mar 2017 05:24:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5ksQknUbBYCPPOfpL3y8Z3rynoTStprtRYc1tTEqnAY=; b=KaYLoQiYmFCj06+j5o2QSoUDSp2mia6X9LGsWJNtti8JlorXZB9O65U94z3NzE2WNI +9Fvrr/k/vyAQP34yY6Pu3zxGgfYypoPLVSUJXc4EUs0afRYbGcfKPmb+61+BMmCnw7l J/1aaJvTaN7MLj49W8w1pWdjX38YYuqQBb0bJcCYiN0ppzrSD5R+4wGKS7L+XBr8vk0G SS37MH405P1CqoadVbGId1rxaaT214EC8wrEVAzzDHWo1YlFzSAY8IK9Ds0DdL78poUQ xops4m0/4PZXEUE2Ptv1h2h+CzTHTW+I+TvbNjjl1blxF/34J4oSA5RMtIg7qE9v7lZg spYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5ksQknUbBYCPPOfpL3y8Z3rynoTStprtRYc1tTEqnAY=; b=EBPiK5ZeGUUJt4zjJFtBSuuK9NcLO/zG8VTyRVahfqWQL/kraWPSO5/K4Ccvb1Koah 27atqUPbkh1NZ6GJ9b0RBYwSLIct61P3nwZA23viMjfeLKR6J7KBD0RXFdm64LgievOI 7sKVtnAF6Mg37u5CZVRWPvMLD8pyYA7RgrYF1dPimB569RsI3DLaWk88NTt2CegO57p1 bPnzNa5mLVNgV7BNYpQfNFO/JmNjv6HKnG5BTShGVpA/jSXO+aTjI8Z1uFKS22XSUU8T OtyWRjqvM/8RTs8kWWqh7pzIyHjd5vBUW+3lYK0xMEbkt3CHXkgd5NGa34jcVpqGhqxb 4aeA==
X-Gm-Message-State: AFeK/H3F8oBpYi4SZpj2bWvNfzeAls/dHn6Fqlf5uthxWv9KhV/TCBcQwj4o2r0ylZ64gg==
X-Received: by 10.200.52.52 with SMTP id u49mr30186771qtb.101.1490099040230; Tue, 21 Mar 2017 05:24:00 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:d09f:c206:4e94:4051? ([2601:18f:801:600:d09f:c206:4e94:4051]) by smtp.gmail.com with ESMTPSA id r33sm14572903qta.19.2017.03.21.05.23.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Mar 2017 05:23:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <84ab880c-885a-9c4f-7857-5adf7d18b6e1@nic.cz>
Date: Tue, 21 Mar 2017 08:23:47 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA408704-7D85-4FDD-BDF4-BCC34220D657@gmail.com>
References: <148943321331.20401.7762893838737928060@ietfa.amsl.com> <630A7AFE-B9D4-4E77-8744-0D6FD0F5A000@gmail.com> <84ab880c-885a-9c4f-7857-5adf7d18b6e1@nic.cz>
To: Petr Špaček <petr.spacek@nic.cz>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/iYIFVuWYOu0WSmxYn8LOVDtqn2Q>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-sutld-ps-03.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: Tue, 21 Mar 2017 12:24:04 -0000

Petr, thanks for your review and feedback...

> On Mar 15, 2017, at 6:52 AM, Petr Špaček <petr.spacek@nic.cz> wrote:
> 
> On 14.3.2017 12:28, Ralph Droms wrote:
>> draft-ietf-dnsop-sutld-ps-03 includes revised text to address issues raised during the WG last call and other editorial improvements.  The list of issues, discussion and resolution are in GitHub: https://github.com/Abhayakara/draft-tldr-sutld-ps
>> 
>> There is one substantial addition to the list of problems in section 3: the use of DNSSEC with Special-Use Domain Names.
> 
> The 03 version is a very good one.
> 
> I would like to comment on one side-effect of the changes:
> The Summary section was removed and the text moved elsewhere. IMHO this
> makes the document less understandable to a person who was not involved
> with its development.
> 
> For this reason I propose new Summary section, which would be basically
> current 4.1.4.  Liaison Statement on Technical Use of Domain Names.
> 
> The reference to these two I-Ds can be at the same place as current 4.1.4.
> 
> 
> So the new text would look like:
> 
> 4.1.4.  Expired Internet Drafts Relating to SUDN
>   /links to/
>   [I-D.chapin-additional-reserved-tlds]
>   [I-D.grothoff-iesg-special-use-p2p-names]
> 
> 6. Summary
>   As a result of processing requests to add names to the Special-Use
>   Domain Name registry, as documented in
>   [I-D.chapin-additional-reserved-tlds] and
>   [I-D.grothoff-iesg-special-use-p2p-names], the IAB initiated a review
>   of the process defined in RFC 6761 for adding names to the registry.
>   This review was identified as in the charter of the IETF DNSOP
>   working group, and the review has been conducted in that working
>   group.  The Liaison Statement [SDO-IAB-ICANN-LS] notified ICANN of
>   the review, affirmed that the discussion would be "open and
>   transparent to participation by interested parties" and explicitly
>   invited members of the ICANN community to participate.
>   This document is a product of the IETF DNSOP working group review of
>   the registry process in RFC 6761.
> 
> 
> I believe that original 4.1.4 nicely summarizes what this document is about.

I agree that some of the text belongs in a more prominent place, to alert the reader to the process behind the document.  I've opened an issue: draft-ietf-homenet-dot-03

Our proposed solution is to move some of the detail behind this document from section 4.1.4 to the Introduction.

OLD:

1.  Introduction

   [...]

   Special-Use Domain Names [RFC6761] created an IANA registry for
   Special-Use Domain Names [SDO-IANA-SUDR], defined policies for adding
   to the registry, and made some suggestions about how those policies
   might be implemented.  Since the publication of RFC 6761, the IETF
   has been asked to designate several new Special-Use Domain Names in
   this registry.  During the evaluation process for these Special-Use
   Domain Names, the IETF encountered several different sorts of issues.
   Because of this, the IETF has decided to investigate the problem and
   decide if and how the RFC 6761 process can be improved, or whether it
   should be deprecated.

NEW:

1.  Introduction

   [...]

   Special-Use Domain Names [RFC6761] created an IANA registry for
   Special-Use Domain Names [SDO-IANA-SUDR], defined policies for adding
   to the registry, and made some suggestions about how those policies
   might be implemented.  Since the publication of RFC 6761, the IETF
   has been asked to designate several new Special-Use Domain Names in
   this registry.  During the evaluation process for these Special-Use
   Domain Names, the IETF encountered several different sorts of issues.
   Because of this, the IETF has decided to investigate the problem and
   decide if and how the RFC 6761 process can be improved, or whether it
   should be deprecated.  The IETF DSNOP working group charter was
   extended to include conducting a review of the process for adding
   names to the registry that is defined in RFC 6761. This document is a
   product of that review.

OLD:

4.1.4.  Liaison Statement on Technical Use of Domain Names

   As a result of processing requests to add names to the Special-Use
   Domain Name registry, as documented in
   [I-D.chapin-additional-reserved-tlds] and
   [I-D.grothoff-iesg-special-use-p2p-names], the IAB initiated a review
   of the process defined in RFC 6761 for adding names to the registry.
   This review was identified as in the charter of the IETF DNSOP
   working group, and the review has been conducted in that working
   group.  The Liaison Statement [SDO-IAB-ICANN-LS] notified ICANN of
   the review, affirmed that the discussion would be "open and
   transparent to participation by interested parties" and explicitly
   invited members of the ICANN community to participate.

   This document is a product of the IETF DNSOP working group review of
   the registry process in RFC 6761.

NEW:

4.1.4.  Liaison Statement on Technical Use of Domain Names

   As a result of processing requests to add names to the Special-Use
   Domain Name registry, as documented in
   [I-D.chapin-additional-reserved-tlds] and
   [I-D.grothoff-iesg-special-use-p2p-names], a review was chartered
   of the process defined in RFC 6761 for adding names to the registry
   (as explained earlier).  The Liaison Statement [SDO-IAB-ICANN-LS]
   notified ICANN of the review, affirmed that the discussion would be
   "open and transparent to participation by interested parties" and
   explicitly invited members of the ICANN community to participate.

- Ralph


> 
> Petr Špaček  @  CZ.NIC
> 
> 
>> 
>> In the authors' opinion, draft-ietf-dnsop-sutld-ps-03 addresses all of the WG last call issues and the document is ready to be forwarded to the IESG.
>> 
>> - Ralph
>> 
>> 
>>> On Mar 13, 2017, at 3:26 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 of the IETF.
>>> 
>>>       Title           : Special-Use Domain Names Problem Statement
>>>       Authors         : Ted Lemon
>>>                         Ralph Droms
>>>                         Warren Kumari
>>> 	Filename        : draft-ietf-dnsop-sutld-ps-03.txt
>>> 	Pages           : 27
>>> 	Date            : 2017-03-13
>>> 
>>> Abstract:
>>>  The Special-Use Domain Names IANA registry policy defined in RFC 6761
>>>  has been shown through experience to present unanticipated
>>>  challenges.  This memo presents a list, intended to be comprehensive,
>>>  of the problems that have been identified.  In addition it reviews
>>>  the history of Domain Names and summarizes current IETF publications
>>>  and some publications from other organizations relating to Special-
>>>  Use Domain Names.
>>> 
>>> 
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-dnsop-sutld-ps/
>>> 
>>> There's also a htmlized version available at:
>>> https://tools.ietf.org/html/draft-ietf-dnsop-sutld-ps-03
>>> 
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-sutld-ps-03
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>> 
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop