Re: [dnsext] I-D Action:draft-ietf-dnsext-aliasing-requirements-00.txt

Doug Barton <dougb@dougbarton.us> Thu, 24 February 2011 08:35 UTC

Return-Path: <dougb@dougbarton.us>
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 6B7C43A6A15 for <dnsext@core3.amsl.com>; Thu, 24 Feb 2011 00:35:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 wt7o8lVgP42U for <dnsext@core3.amsl.com>; Thu, 24 Feb 2011 00:35:37 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by core3.amsl.com (Postfix) with ESMTP id E8C203A69E4 for <dnsext@ietf.org>; Thu, 24 Feb 2011 00:35:36 -0800 (PST)
Received: (qmail 24098 invoked by uid 399); 24 Feb 2011 08:36:20 -0000
Received: from router.ka9q.net (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 24 Feb 2011 08:36:20 -0000
X-Originating-IP: 75.60.237.91
X-Sender: dougb@dougbarton.us
Message-ID: <4D661882.2020403@dougbarton.us>
Date: Thu, 24 Feb 2011 00:36:18 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110129 Thunderbird/3.1.7
MIME-Version: 1.0
To: dnsext@ietf.org
References: <20110223001502.31614.56353.idtracker@localhost>
In-Reply-To: <20110223001502.31614.56353.idtracker@localhost>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [dnsext] I-D Action:draft-ietf-dnsext-aliasing-requirements-00.txt
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: Thu, 24 Feb 2011 08:35:38 -0000

I think this is a great draft, and it expresses both the parameters of 
the problem and the requirements for a solution in the way that I 
understand them (for whatever that's worth).


Doug


On 02/22/2011 16:15, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the DNS Extensions Working Group of the IETF.
>
>
> 	Title           : Problem Statement: DNS Resolution of Aliased Names
> 	Author(s)       : S. Woolf, X. Lee
> 	Filename        : draft-ietf-dnsext-aliasing-requirements-00.txt
> 	Pages           : 20
> 	Date            : 2011-02-22
>
> This document attempts to describe a set of issues that arises from
> the desire to treat a set or group of names as "aliases" of each
> other, "bundled," "variants," or "the same," which is problematic in
> terms of corresponding behavior for DNS labels and FQDNs.
>
> With the emergence of internationalized domain names, among other
> potential use cases, two or more names that users will regard as
> having identical meaning may sometimes require corresponding behavior
> in the underlying infrastructure, possibly in the DNS itself.  It's
> not clear how to accommodate this required behavior of such names in
> DNS resolution; in particular, it's not clear when they are best
> accommodated in registry practices for generating names for lookup in
> the DNS, existing DNS protocol elements and behavior, existing
> application-layer mechanisms and practices, or some set of protocol
> elements or behavior not yet defined.  This document attempts to
> describe some of these cases and the behavior of some of the possible
> solutions discussed to date.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-dnsext-aliasing-requirements-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
>
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext



-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/