RFC 5891 on Internationalized Domain Names in Applications (IDNA): Protocol
rfc-editor@rfc-editor.org Wed, 04 August 2010 15: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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57C5A3A6BF6 for <ietf-announce@core3.amsl.com>; Wed, 4 Aug 2010 08:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level:
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3sIPkuRiGz3 for <ietf-announce@core3.amsl.com>; Wed, 4 Aug 2010 08:39:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 69D623A6C02 for <ietf-announce@ietf.org>; Wed, 4 Aug 2010 08:37:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 49FD6E06DA; Wed, 4 Aug 2010 08:37:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5891 on Internationalized Domain Names in Applications (IDNA): Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20100804153730.49FD6E06DA@rfc-editor.org>
Date: Wed, 04 Aug 2010 08:37:30 -0700
Cc: idna-update@alvestrand.no, 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: Wed, 04 Aug 2010 15:39:38 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5891 Title: Internationalized Domain Names in Applications (IDNA): Protocol Author: J. Klensin Status: Standards Track Stream: IETF Date: August 2010 Mailbox: john+ietf@jck.com Pages: 17 Characters: 38105 Obsoletes: RFC3490, RFC3491 Updates: RFC3492 I-D Tag: draft-ietf-idnabis-protocol-18.txt URL: http://www.rfc-editor.org/rfc/rfc5891.txt This document is the revised protocol definition for Internationalized Domain Names (IDNs). The rationale for changes, the relationship to the older specification, and important terminology are provided in other documents. This document specifies the protocol mechanism, called Internationalized Domain Names in Applications (IDNA), for registering and looking up IDNs in a way that does not require changes to the DNS itself. IDNA is only meant for processing domain names, not free text. [STANDARDS TRACK] This document is a product of the Internationalized Domain Names in Applications (Revised) Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist 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