Re: [DNSOP] WG review of draft-ietf-homenet-dot-03

Russ Housley <housley@vigilsec.com> Mon, 20 March 2017 17:08 UTC

Return-Path: <housley@vigilsec.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 CE4AF131501 for <dnsop@ietfa.amsl.com>; Mon, 20 Mar 2017 10:08:15 -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, HTML_MESSAGE=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 zoR_ztYD2aUp for <dnsop@ietfa.amsl.com>; Mon, 20 Mar 2017 10:08:09 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1FCB1314F8 for <dnsop@ietf.org>; Mon, 20 Mar 2017 10:08:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 1B0263004B6 for <dnsop@ietf.org>; Mon, 20 Mar 2017 13:08:03 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 46fWAcRxrNBJ for <dnsop@ietf.org>; Mon, 20 Mar 2017 13:08:01 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id A93F1300433; Mon, 20 Mar 2017 13:08:01 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <AB11455F-7E43-4CB3-9F13-DB6A09F739EB@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9AD35295-F764-4158-8E2F-92A2EBE9F09D"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Mon, 20 Mar 2017 13:08:01 -0400
In-Reply-To: <60C85486-E351-4C42-ADEB-FCBB56F4EA27@fugue.com>
Cc: dnsop <dnsop@ietf.org>, Terry Manderson <terry.manderson@icann.org>
To: Ted Lemon <mellon@fugue.com>
References: <1E14B142-680B-4E30-809B-68E03EB6E326@gmail.com> <61FD3EE3-3043-4AB1-9823-6A9D61B1438C@vigilsec.com> <BE2A3845-D8AA-433A-9F00-1056ECFD335F@fugue.com> <21C8F856-FE3F-42A6-A8ED-888D0797B68B@vigilsec.com> <60C85486-E351-4C42-ADEB-FCBB56F4EA27@fugue.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oJMbdAKOblUfo659uNTx4W_GOpI>
Subject: Re: [DNSOP] WG review of draft-ietf-homenet-dot-03
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, 20 Mar 2017 17:08:16 -0000

> 
>> We have a different view of the intended purpose of the special-use TLD registry.  Sadly, the RFC does not include language that resolves this difference.
> 
> I understand that we have different views.   However, I am asking you specifically to articulate _your_ view.
> 
> You have said that in your opinion special-use names must not be published in the root zone, but that was already obvious from what you said previously.   What I am asking you to do is explain _why_ special-use names must not be published in the root zone.

There are other processes for adding names to the root zone.  In my opinion, using the special-use TLD registry as a means of putting a name, even one that has a different scope and use case, is an end run around that process.

Russ