Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnsext-special-names-01.txt> (Special-Use Domain Names) to Proposed Standard
Joe Abley <jabley@hopcount.ca> Fri, 04 February 2011 13:53 UTC
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74C083A6949 for <dnsext@core3.amsl.com>; Fri, 4 Feb 2011 05:53:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level:
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nS7UXfQyicYk for <dnsext@core3.amsl.com>; Fri, 4 Feb 2011 05:53:55 -0800 (PST)
Received: from monster.hopcount.ca (monster.hopcount.ca [216.235.14.38]) by core3.amsl.com (Postfix) with ESMTP id BA36D3A6941 for <dnsext@ietf.org>; Fri, 4 Feb 2011 05:53:54 -0800 (PST)
Received: from [199.212.90.21] (helo=dh21.r2.owls.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1PlME0-0008Hm-JQ; Fri, 04 Feb 2011 14:01:25 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <82hbckhsyx.fsf@mid.bfk.de>
Date: Fri, 04 Feb 2011 08:57:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D67EB007-2322-43FB-87F4-E28642B82BBB@hopcount.ca>
References: <20110117230048.26192.84056.idtracker@localhost> <2A149A97-3B0A-49AA-88CA-9741F88B9274@gmail.com> <alpine.BSF.2.00.1102011628070.14850@fledge.watson.org> <82hbckhsyx.fsf@mid.bfk.de>
To: Florian Weimer <fweimer@bfk.de>
X-Mailer: Apple Mail (2.1082)
X-SA-Exim-Connect-IP: 199.212.90.21
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Cc: Samuel Weiler <weiler@watson.org>, Ralph Droms <rdroms.ietf@gmail.com>, dnsext@ietf.org
Subject: Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnsext-special-names-01.txt> (Special-Use Domain Names) to Proposed Standard
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 13:53:56 -0000
On 2011-02-04, at 07:41, Florian Weimer wrote: > LOCAL. If understand things correctly, it's widely used to trigger > Multicast DNS resolution in combined DNS/Multicast DNS environments. In draft-jabley-reserved-domain-names-00, my initial registry was specified as: +-------------+-----------------------------------------+-----------+ | Domain Name | Description | Reference | +-------------+-----------------------------------------+-----------+ | TEST | Recommended for use in testing of | [RFC2606] | | | current or new DNS related code | | | | | | | EXAMPLE | Recommended for use in documentation or | [RFC2606] | | | as examples | | | | | | | INVALID | Recommended for use in documentation or | [RFC2606] | | | as examples | | | | | | | LOCALHOST | Traditionally statically defined in | [RFC2606] | | | host DNS implementations as having an A | | | | record pointing to the loop back IP | | | | address, and reserved for such use | | | | | | | EXAMPLE.COM | Available for use as examples | [RFC2606] | | | | | | EXAMPLE.NET | Available for use as examples | [RFC2606] | | | | | | EXAMPLE.ORG | Available for use as examples | [RFC2606] | +-------------+-----------------------------------------+-----------+ I didn't include LOCAL because there wasn't a suitable published document for it, and the registry I defined had registration procedures specified as "document published with iab approval". However, if this registry existed, I would expect that Stuart's bonjour draft would be extended with an IANA Considerations section that specified relevant names be added to the registry. I never submitted draft-jabley-reserved-domain-names-00 when I wrote it, but since I've referred to it a couple of times I will now do so in case that's of any use to anybody. I continue to think that Stuart's discussion of the issues is valuable, but I think the registry creation would benefit from more concise direction. Joe
- [dnsext] Fwd: Last Call: <draft-cheshire-dnsext-s… Ralph Droms
- Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnse… Joe Abley
- Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnse… Florian Weimer
- Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnse… Joe Abley
- Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnse… John Levine
- Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnse… Samuel Weiler
- Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnse… Florian Weimer
- Re: [dnsext] Last Call: <draft-cheshire-dnsext-sp… Stephane Bortzmeyer
- Re: [dnsext] Last Call: <draft-cheshire-dnsext-sp… Florian Weimer
- Re: [dnsext] Fwd: Last Call: <draft-cheshire-dnse… Joe Abley