RFC 5895 on Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008

rfc-editor@rfc-editor.org Tue, 14 September 2010 19:39 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id F0BD33A6B3C for <ietf-announce@core3.amsl.com>; Tue, 14 Sep 2010 12:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.335
X-Spam-Status: No, score=-102.335 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id UfO3Uxqtk9jl for <ietf-announce@core3.amsl.com>; Tue, 14 Sep 2010 12:39:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 6648D3A6B3A for <ietf-announce@ietf.org>; Tue, 14 Sep 2010 12:38:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 814D1E06E5; Tue, 14 Sep 2010 12:38:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5895 on Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008
From: rfc-editor@rfc-editor.org
Message-Id: <20100914193846.814D1E06E5@rfc-editor.org>
Date: Tue, 14 Sep 2010 12:38:46 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 19:40:37 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5895

        Title:      Mapping Characters for Internationalized Domain 
                    Names in Applications (IDNA) 2008 
        Author:     P. Resnick, P. Hoffman
        Status:     Informational
        Stream:     Independent
        Date:       September 2010
        Mailbox:    presnick@qualcomm.com, 
        Pages:      7
        Characters: 16556
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-resman-idna2008-mappings-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5895.txt

In the original version of the Internationalized Domain Names in
Applications (IDNA) protocol, any Unicode code points taken from user
input were mapped into a set of Unicode code points that "made
sense", and then encoded and passed to the domain name system (DNS).
The IDNA2008 protocol (described in RFCs 5890, 5891, 5892, and 5893)
presumes that the input to the protocol comes from a set of
"permitted" code points, which it then encodes and passes to the DNS,
but does not specify what to do with the result of user input.  This
document describes the actions that can be taken by an implementation
between receiving user input and passing permitted code points to the
new IDNA protocol.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC