Internationalized Domain Names in Applications (IDNA): Registry Restrictions and Recommendations
draft-klensin-idna-rfc5891bis-00

Document Type Active Internet-Draft (individual in art area)
Last updated 2017-03-14 (latest revision 2017-03-11)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state AD is watching
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to (None)
Network Working Group                                         J. Klensin
Internet-Draft
Updates: 5890, 5891 (if approved)                             A. Freytag
Intended status: Standards Track                             ASMUS, Inc.
Expires: September 12, 2017                               March 11, 2017

    Internationalized Domain Names in Applications (IDNA): Registry
                    Restrictions and Recommendations
                  draft-klensin-idna-rfc5891bis-00.txt

Abstract

   The IDNA specifications for internationalized domain names combine
   rules that determine the labels that are allowed in the DNS without
   violating the protocol itself and an assignment of responsibility,
   consistent with earlier specifications, for determining the labels
   that are allowed in particular zones.  Conformance to IDNA by
   registries and other implementations requires both parts.  Experience
   strongly suggests that the language describing those responsibility
   was insufficiently clear to promote safe and interoperable use of the
   specifications and that more details and some specific examples would
   have been helpful.  This specification updates the earlier ones to
   provide that guidance and to correct some technical errors in the
   descriptions.  It does not alter the protocols and rules themselves
   in any way.

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 September 12, 2017.

Klensin & Freytag      Expires September 12, 2017               [Page 1]
Internet-Draft         IDNA: Registry Restrictions            March 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Registry Restrictions in IDNA2008 . . . . . . . . . . . . . .   3
   3.  Progressive Subsets of Allowed Characters . . . . . . . . . .   4
   4.  Other corrections and updates . . . . . . . . . . . . . . . .   7
     4.1.  Updates to RFC 5890 . . . . . . . . . . . . . . . . . . .   7
     4.2.  Updates to RFC 5891 . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Parts of the specifications for Internationalized Domain Names in
   Applications (IDNA) [RFC5890] [RFC5891] [RFC5894] (collectively
   known, along with RFC 5892 [RFC5892], RFC 5893 [RFC5893] and updates
   to them, as "IDNA2008" (or just "IDNA") impose a requirement that
   domain name system (DNS) registries restrict the characters they
   allow in domain name labels (see Section 2 below), and the contents
   and structure of those labels.  That requirement and restriction are
   consistent with the "trustee for the community" requirements of the
   original specification for DNS naming and authority [RFC1591].  The
   restrictions are intended to limit the permitted characters and
   strings to those for which the registries or their advisers have a
   thorough understanding and for which they are willing to take
   responsibility.

Klensin & Freytag      Expires September 12, 2017               [Page 2]
Show full document text