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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Sat, 01 April 2017 20:56 UTC

Return-Path: <bortzmeyer@nic.fr>
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 7909E127077 for <dnsop@ietfa.amsl.com>; Sat, 1 Apr 2017 13:56:10 -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 7ZTJo5_NsmDD for <dnsop@ietfa.amsl.com>; Sat, 1 Apr 2017 13:56:08 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (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 BE2D2129692 for <dnsop@ietf.org>; Sat, 1 Apr 2017 13:56:06 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 9EEDF31C7D; Sat, 1 Apr 2017 22:56:04 +0200 (CEST)
Received: by godin (Postfix, from userid 1000) id C240FEC0E0F; Sat, 1 Apr 2017 22:17:27 +0200 (CEST)
Date: Sat, 1 Apr 2017 15:17:27 -0500
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Suzanne Woolf <suzworldwide@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Message-ID: <20170401201727.GA5948@laperouse.bortzmeyer.org>
References: <333CCE99-82E2-44C9-97ED-2222540097ED@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <333CCE99-82E2-44C9-97ED-2222540097ED@gmail.com>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/AZ5HqrFS0bQh4Bug_eK-9LVBTFQ>
Subject: Re: [DNSOP] 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: Sat, 01 Apr 2017 20:56:10 -0000

On Sun, Mar 12, 2017 at 07:20:55PM -0400,
 Suzanne Woolf <suzworldwide@gmail.com> wrote 
 a message of 92 lines which said:

> This message opens a Working Group Last Call for:
> 
> "The ALT Special Use Top Level Domain"
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/ <https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/>

I've read -08 and I believe I understand this draft. I'm not convinced
it's useful (most users of alternative resolution systems won't use it
and, anyway, I'm not even sure it will be added in the Special-Use
registry, which was wrongly frozen by the IESG) but I don't see big
issues with the draft, it seems to me it correctly describes the new
TLD.

Editorial :

Section 1:

"and that should not be resolved" I cannot parse it. Missing "it"?

Section 5 :

After "and anyone watching queries along the path", add a reference to
RFC 7626?

Normative references:

Why is RFC 6303 a normative reference? It is no longer used.

Why is RFC 7686 a normative reference? It is just an example.