Principles for Unicode Code Point Inclusion in Labels in the DNS
draft-iab-dns-zone-codepoint-pples-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-12-04
Stream IAB
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream IAB state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
Network Working Group                                        A. Sullivan
Internet-Draft                                                 Dyn, Inc.
Intended status: Informational                                 D. Thaler
Expires: June 7, 2013                                          Microsoft
                                                              J. Klensin

                                                              O. Kolkman
                                                              NLnet Labs
                                                        December 4, 2012

    Principles for Unicode Code Point Inclusion in Labels in the DNS
                 draft-iab-dns-zone-codepoint-pples-01

Abstract

   IDNA makes available to DNS zone administrators a very wide range of
   Unicode code points.  Most operators of zones should probably not
   permit registration of U-labels using the entire range.  This is
   especially true of zones that accept registrations across
   organizational boundaries, such as top-level domains and, most
   importantly, the root.  It is unfortunately not possible to generate
   algorithms to determine whether permitting a code point presents a
   low risk.  This memo presents a set of principles that can be used to
   guide the decision of whether a Unicode code point may be wisely
   included in the repertoire of permissible code points in a U-label in
   a zone.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 7, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the

Sullivan, et al.          Expires June 7, 2013                  [Page 1]
Internet-Draft       DNS Zone Code Point Principles        December 2012

   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Background . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  More-Restrictive Rules Going Up the DNS Tree . . . . . . .  5
   3.  Principles Applicable to All Zones . . . . . . . . . . . . . .  6
     3.1.  Longevity Principle  . . . . . . . . . . . . . . . . . . .  6
     3.2.  Least Astonishment Principle . . . . . . . . . . . . . . .  6
     3.3.  Contextual Safety Principle  . . . . . . . . . . . . . . .  6
   4.  Principles Applicable to All Public Zones  . . . . . . . . . .  7
     4.1.  Conservatism Principle . . . . . . . . . . . . . . . . . .  7
     4.2.  Inclusion Principle  . . . . . . . . . . . . . . . . . . .  7
     4.3.  Simplicity Principle . . . . . . . . . . . . . . . . . . .  7
     4.4.  Predictability Principle . . . . . . . . . . . . . . . . .  8
     4.5.  Stability Principle  . . . . . . . . . . . . . . . . . . .  8
   5.  Principle Specific to the Root Zone  . . . . . . . . . . . . .  8
     5.1.  Letter Principle . . . . . . . . . . . . . . . . . . . . .  8
   6.  Confusion and Context  . . . . . . . . . . . . . . . . . . . .  9
   7.  Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
   11. IAB Members at the Time of This Writing  . . . . . . . . . . . 10
   12. Informative References . . . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Sullivan, et al.          Expires June 7, 2013                  [Page 2]
Internet-Draft       DNS Zone Code Point Principles        December 2012

1.  Introduction

   Operators of a DNS zone need to set policies around what Unicode code
Show full document text