Re: [dns-dir] Draft requesting reservation of special-use domain names

Erik Nordmark <nordmark@acm.org> Wed, 27 November 2013 19:10 UTC

Return-Path: <nordmark@acm.org>
X-Original-To: dns-dir@ietfa.amsl.com
Delivered-To: dns-dir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 916001AD8F7 for <dns-dir@ietfa.amsl.com>; Wed, 27 Nov 2013 11:10:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=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 ikzaFtTtzS_s for <dns-dir@ietfa.amsl.com>; Wed, 27 Nov 2013 11:10:46 -0800 (PST)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3EA1AD8DA for <dns-dir@ietf.org>; Wed, 27 Nov 2013 11:10:46 -0800 (PST)
Received: from [10.0.1.44] (184-23-158-201.dsl.dynamic.sonic.net [184.23.158.201]) (authenticated bits=0) by c.mail.sonic.net (8.14.4/8.14.4) with ESMTP id rARJAgNX004943 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 27 Nov 2013 11:10:43 -0800
Message-ID: <529643B1.1050506@acm.org>
Date: Wed, 27 Nov 2013 11:10:41 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Olaf Kolkman <olaf@NLnetLabs.nl>
References: <5286231D.4030104@innovationslab.net> <52863898.5080100@innovationslab.net> <8F0B436C-85D2-4566-A80B-40710DF9D476@ogud.com> <B6B47E1A-678D-4856-BE54-E34ADC7E98F8@townsley.net> <73C44405-6048-4031-9FA5-BCDFA70160A4@frobbit.se> <84D57F70-CCA3-4412-989E-0FAB089ECEEF@gmail.com> <31C42EE0-8D1F-4D7C-8E8C-43ACE5F61B04@frobbit.se> <528D2782.4070208@sonic.net> <B42C50EA-39CE-415E-9CBA-0F0471CAC519@NLnetLabs.nl>
In-Reply-To: <B42C50EA-39CE-415E-9CBA-0F0471CAC519@NLnetLabs.nl>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Sonic-ID: C;5FGLnJdX4xGfBLR06sd3kQ== M;et69nJdX4xGfBLR06sd3kQ==
Cc: IETF DNS Directorate <dns-dir@ietf.org>
Subject: Re: [dns-dir] Draft requesting reservation of special-use domain names
X-BeenThere: dns-dir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNS directorate discussion list <dns-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-dir>, <mailto:dns-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dns-dir/>
List-Post: <mailto:dns-dir@ietf.org>
List-Help: <mailto:dns-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-dir>, <mailto:dns-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2013 19:10:47 -0000

On 11/27/13 9:29 AM, Olaf Kolkman wrote:

>> Thus from my reading of appendix G its status is quite clear. It
>> doesn't say anything about future use of the suggested intranet labels.
>
>
> But people who are not IETF close readers might have interpreted this
> paragraph as being normative and an indication of ‘safe to use’.

Olaf,

I can see how a statement along the lines of
	don't use "localhost" - folks seem to be using "X" instead
can be read as an endorsement of X as opposed to X being less bad than 
localhost.

Anyhow ...

> In any case the question is whether we should clarify. If we do we can
> go two ways:
> 1 Using these labels: your own dumb fault, you should have know better
> 2 These labels are reserved for private use, because we have been
> confusing, and because of wide public use suggested by various forms of
> documentation. The will be banned for delegation from the root: beware
> of collisions and undefined behavior.
>
> I’d opt for writing such document and I’d opt for version 2.

In light of new gTLDs it does make sense to produce a clarification, and 
#2 makes sense to me.

Question is whether that document will be strictly limited to the names 
listed in RFC 6762 or open up the door to consider other names.

    Erik