Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt

Jelte Jansen <jelte.jansen@sidn.nl> Mon, 03 March 2014 14:14 UTC

Return-Path: <Jelte.Jansen@sidn.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A61AE1A00F5 for <dnsop@ietfa.amsl.com>; Mon, 3 Mar 2014 06:14:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.453
X-Spam-Level:
X-Spam-Status: No, score=-0.453 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] 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 zHQNT_foeBS9 for <dnsop@ietfa.amsl.com>; Mon, 3 Mar 2014 06:14:27 -0800 (PST)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id D389F1A0112 for <dnsop@ietf.org>; Mon, 3 Mar 2014 06:14:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=B5cU9cGELKxqv/MYSLDorz/mvirjF+u5jAdLGRuUcwE=; b=N6V8DPMdkWoiu+6W+dJVi7axxsH8urV4tjOFshjcCCYCzbv6x1JHMSarauQ6wUZx/4unmY3z790GYt8PVeOF0F/7uw1i/LIA5qm1G9LyOBE0EyrWL3Cxph7rg0sAdAc2bcrBb2q60nNRxIE4yE15CaxWtb/Vz1VovMHvYgIZqns=
Received: from kahubcasn01.SIDN.local ([192.168.2.73]) by arn2-kamx.sidn.nl with ESMTP id s23EEF8O001442-s23EEF8Q001442 (version=TLSv1.0 cipher=AES128-SHA bits=128 verify=CAFAIL); Mon, 3 Mar 2014 15:14:15 +0100
Received: from [94.198.152.219] (94.198.152.219) by kahubcasn01.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 3 Mar 2014 15:14:12 +0100
Message-ID: <53148E33.3010906@sidn.nl>
Date: Mon, 3 Mar 2014 14:14:11 +0000
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
References: <20140226100311.E73CA1069B39@rock.dv.isc.org> <8FEAF0FC-2AC3-4F39-9825-7068AAA6E40D@hopcount.ca> <CAHw9_iJa_OhzHVCQ4L0Aj+m=zAp6w=mJpAV-_ueh9iukhb3bnA@mail.gmail.com> <20140303102535.6f276963@quill> <531450A1.8010507@bogus.com> <917146C3-BC38-4D10-AA14-C3B7A02B1193@hopcount.ca> <2C463623-6483-45E2-B299-75BF7C8A1A3B@nominum.com> <alpine.LSU.2.00.1403031329540.18502@hermes-1.csi.cam.ac.uk> <BDE4E26A-0D61-4DDE-B2E2-031A02E2BA96@nominum.com> <53148A04.3050208@sidn.nl> <20140303140311.GC5119@mx1.yitter.info>
In-Reply-To: <20140303140311.GC5119@mx1.yitter.info>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.219]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/YnlaD1ON1homlSLXhS1h6O4Lm7M
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 03 Mar 2014 14:14:28 -0000

On 03/03/2014 02:03 PM, Andrew Sullivan wrote:
> On Mon, Mar 03, 2014 at 01:56:20PM +0000, Jelte Jansen wrote:
>> I'd think that a domain name is only a domain name when whatever
>> protocol it is defined in defines it as a domain name (or whatever
>> undefined protocol uses it in actual dns resolution). What a non-domain
>> name looks like shouldn't matter.
> 
> Are NetBIOS names domain names?  How about mDNS names?  I think yes,
> but neither is part of the DNS as such.
> 

I was wondering whether I should have stated that a bit more carefully,
but 'part of the DNS' might be a different thing than 'could use DNS'.

I wasn't suggesting there shouldn't be any reservations, but 'looks like
a domain name' is way, way too wide a definition. In that case we need
to reserve any possible TLD. Including all existing gTLD and ccTLD's.

As for mDNS, I do not know; you tell me :) Is there a problem in
anything that is *not* either a definite bug in a program or a user
copy-pasting the name in a browser window?

Jelte