Fwd: RFC 6452 on The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) - Unicode 6.0

[Paul Hoffman]

Begin forwarded message:

> From: rfc-editor at rfc-editor.org
> Subject: RFC 6452 on The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) - Unicode 6.0
> Date: November 13, 2011 2:11:47 PM GMT+08:00
> To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
> Cc: apps-discuss at ietf.org, rfc-editor at rfc-editor.org
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 6452
> 
>        Title:      The Unicode Code Points and 
>                    Internationalized Domain Names for Applications (IDNA) 
>                    - Unicode 6.0 
>        Author:     P. Faltstrom, Ed.,
>                    P. Hoffman, Ed.
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       November 2011
>        Mailbox:    paf at cisco.com, 
>                    paul.hoffman at vpnc.org
>        Pages:      4
>        Characters: 6817
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-faltstrom-5892bis-05.txt
> 
>        URL:        http://www.rfc-editor.org/rfc/rfc6452.txt
> 
> This memo documents IETF consensus for Internationalized Domain Names
> for Applications (IDNA) derived character properties related to the
> three code points, existing in Unicode 5.2, that changed property
> values when version 6.0 was released.  The consensus is that no
> update is needed to RFC 5892 based on the changes made in Unicode
> 6.0.  [STANDARDS-TRACK]
> 
> This document is a product of the Applications Area Working Group 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 at 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
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce at ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce