Principles for Unicode Code Point Inclusion in Labels in the DNS Root
draft-sullivan-dns-zone-codepoint-pples-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Andrew Sullivan , Dave Thaler , Olaf Kolkman | ||
| Last updated | 2012-12-07 (Latest revision 2012-06-05) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Traditionally, the management of the DNS root zone permitted only "alphabetic" labels. As long as the root zone included only ASCII characters, and as long as there was only one form of a label, the restriction plainly meant that only the letters A-Z and a-z were permitted. The advent of internationalized labels using IDNA2008 presents some complications for the restriction. One of the complications is the meaning of the term "alphabetic" when applied to the Unicode code points in U-labels. This memo presents a set of principles that can be used to determine whether a Unicode code point may be wisely included in the repertoire of permissible code points in a U-label in a zone.
Authors
Andrew Sullivan
Dave Thaler
Olaf Kolkman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)