IETF Logo Mail Archive

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

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 03 March 2014 14:03 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 78BE61A0117 for <dnsop@ietfa.amsl.com>; Mon, 3 Mar 2014 06:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 Pe-GA89JYG_k for <dnsop@ietfa.amsl.com>; Mon, 3 Mar 2014 06:03:26 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id A776F1A0115 for <dnsop@ietf.org>; Mon, 3 Mar 2014 06:03:26 -0800 (PST)
Received: from mx1.yitter.info (dhcp-acb5.meeting.ietf.org [31.133.172.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 27E168A031 for <dnsop@ietf.org>; Mon, 3 Mar 2014 14:03:14 +0000 (UTC)
Date: Mon, 03 Mar 2014 09:03:12 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140303140311.GC5119@mx1.yitter.info>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <53148A04.3050208@sidn.nl>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/oFQEn_n7r59EPhnLa7gKZ9kjhCU
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:03:27 -0000

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.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email