Last Call: <draft-faltstrom-unicode11-07.txt> (IDNA2008 and Unicode 11.0.0) to Proposed Standard

The IESG <> Tue, 05 February 2019 14:31 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 8B6FB1294D0; Tue, 5 Feb 2019 06:31:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-faltstrom-unicode11-07.txt> (IDNA2008 and Unicode 11.0.0) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
CC:,,, Russ Housley <>
Sender: <>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <>
Date: Tue, 05 Feb 2019 06:31:14 -0800
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Feb 2019 14:31:14 -0000

The IESG has received a request from an individual submitter to consider the
following document: - 'IDNA2008 and Unicode 11.0.0'
  <draft-faltstrom-unicode11-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the mailing lists by 2019-03-05. Exceptionally, comments may be
sent to instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.


   This document describes the changes between Unicode 6.3.0 and Unicode
   11.0.0 in the context of IDNA2008.  It further suggests a path
   forward for the IETF to ensure IDNA2008 follows the evolution of the
   Unicode Standard.

   Some changes have been made in the Unicode Standard related to the
   algorithm IDNA2008 specifies.  IDNA2008 allows adding exceptions to
   the algorithm for backward compatibility; however, this document
   makes no such changes.  Thus this document requests that IANA update
   the tables to Unicode 11.

   The document also recomments that all DNS registries continue the
   practice of calculating a repertoire using conservatism and inclusion


   This document is discussed on the mailing list of the

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc6912: Principles for Unicode Code Point Inclusion in Labels in the DNS (Informational - IAB stream)
    draft-freytag-troublesome-characters: Those Troublesome Characters: A Registry of Unicode Code Points Needing Special Consideration When Used in Network Identifiers (None - )
    rfc5894: Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale (Informational - IETF stream)
    rfc5895: Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008 (Informational - Independent Submission Editor stream)