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

Internet-Drafts@ietf.org Mon, 14 March 2011 22:15 UTC

Return-Path: <Internet-Drafts@ietf.org>
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 90AC43A6B24; Mon, 14 Mar 2011 15:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level:
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 96fSNr8rJiBj; Mon, 14 Mar 2011 15:15:02 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF2223A6BC2; Mon, 14 Mar 2011 15:15:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314221502.9641.83886.idtracker@localhost>
Date: Mon, 14 Mar 2011 15:15:02 -0700
Cc: dnsext@ietf.org
Subject: [dnsext] I-D Action:draft-ietf-dnsext-aliasing-requirements-01.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: Mon, 14 Mar 2011 22:15:03 -0000

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, et al.
	Filename        : draft-ietf-dnsext-aliasing-requirements-01.txt
	Pages           : 22
	Date            : 2011-03-14

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-01.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.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsext-aliasing-requirements-01.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsext-aliasing-requirements-01.txt>