Problem Statement: DNS Resolution of Aliased Names
draft-ietf-dnsext-aliasing-requirements-01

Document Type Expired Internet-Draft (dnsext WG)
Last updated 2011-03-14
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Andrew Sullivan
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-dnsext-aliasing-requirements-01.txt

Abstract

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.

Authors

Suzanne Woolf (woolf@isc.org)
XiaoDong Lee (lee@cnnic.cn)
Jiankang Yao (yaojk@cnnic.cn)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)