IETF Logo Mail Archive

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

Paul Vixie <paul@redbarn.org> Mon, 20 March 2017 18:17 UTC

Return-Path: <paul@redbarn.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 A7374131626 for <dnsop@ietfa.amsl.com>; Mon, 20 Mar 2017 11:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 5fKG0lCr4t6f for <dnsop@ietfa.amsl.com>; Mon, 20 Mar 2017 11:17:16 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 309B3131628 for <dnsop@ietf.org>; Mon, 20 Mar 2017 11:16:57 -0700 (PDT)
Received: from linux-hs2j.localnet (dhcp-148.access.lah1.vix.su [24.104.150.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 0BC8861F96; Mon, 20 Mar 2017 18:16:57 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: dnsop@ietf.org
Date: Mon, 20 Mar 2017 18:16:56 +0000
Message-ID: <2761653.If01A9zrq2@linux-hs2j>
Organization: Vixie Freehold
In-Reply-To: <AB11455F-7E43-4CB3-9F13-DB6A09F739EB@vigilsec.com>
References: <1E14B142-680B-4E30-809B-68E03EB6E326@gmail.com> <60C85486-E351-4C42-ADEB-FCBB56F4EA27@fugue.com> <AB11455F-7E43-4CB3-9F13-DB6A09F739EB@vigilsec.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/MUtz5xSDh240faJmVw60sOHOumA>
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 18:17:18 -0000

On Monday, March 20, 2017 5:08:01 PM GMT Russ Housley wrote:
> 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.

as much as i'd like to see "localhost IN AAAA ::1" added to the root zone, i 
agree with russ's position here-- reservations are in IETF-land, whereas 
actual content is in ICANN-land.

v2.23.0 | Report a Bug | By Email