One document matched: draft-faltstrom-5892bis-04.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc3454 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3454.xml">
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc3491 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3491.xml">
<!ENTITY rfc1035 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml">
<!ENTITY rfc4690 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4690.xml">
<!ENTITY rfc4713 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4713.xml">
<!ENTITY rfc5892 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5892.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc compact="yes"?>
<?rfc subcompact="yes"?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<!-- Expand crefs and put them inline -->
<?rfc comments='yes' ?>
<?rfc inline='yes' ?>
<rfc category="std" docName="draft-faltstrom-5892bis-04.txt" ipr="trust200902">
<front>
<title abbrev="IDNA Codepoints">The Unicode code points and IDNA - Unicode 6.0</title>
<author fullname="Patrik Faltstrom" initials="P." role="editor"
surname="Faltstrom">
<organization abbrev="Cisco">Cisco</organization>
<address>
<email>paf@cisco.com</email>
</address>
</author>
<author fullname="Paul Hoffman" initials="P." role="editor"
surname="Hoffman">
<organization abbrev="VPN Consortium">VPN Consortium</organization>
<address>
<email>paul.hoffman@vpnc.org</email>
</address>
</author>
<date day="6" month="March" year="2011" />
<keyword>IDNA</keyword>
<keyword>DNS</keyword>
<keyword>IDN</keyword>
<keyword>Unicode</keyword>
<keyword>RFC</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<abstract>
<t>This document specifies IETF consensus for 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.
</t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<t><xref target="RFC5892">RFC 5892</xref> specifies an algorithm that was defined
when <xref target="Unicode5.2">The
Unicode Standard</xref> was the current version of Unicode, and it defines a derived property value.
Unicode 6.0 has changed GeneralCategory of three code points that where allocated in
Unicode 5.2 or earlier. This imply the
derived property value differs depending on whether the property definitions
used are from Unicode 5.2 or 6.0.
</t>
<t>
The three code points are:
</t>
<section anchor="U+0CF1" title="U+0CF1 KANNADA SIGN JIHVAMULIYA">
<t>
The GeneralCategory for this character changes from So to Lo. This
implies that the derived property value changes from DISALLOWED to
PVALID.
</t>
</section>
<section anchor="U+0CF2" title="U+0CF2 KANNADA SIGN UPADHMANIYA">
<t>
The GeneralCategory for this character changes from So to Lo. This
implies that the derived property value changes from DISALLOWED to
PVALID.
</t>
</section>
<section anchor="U+19DA" title="U+19DA NEW TAI LUE THAM DIGIT ONE">
<t>
The GeneralCategory for this character changes from Nd to No. This
implies that the derived property value changes from PVALID to
DISALLOWED.
</t>
</section>
</section>
<section anchor="conclusion" title="IETF Consensus">
<t>
No change to RFC 5892 is needed based on the changes made in Unicode 6.0.
</t>
<t>
This consensus does not imply that no changes will be made to RFC 5892
for all future updates of The Unicode Standard.
</t>
<t>
This RFC is being produced because 6.0 is the first version of Unicode to be
released since IDNA2008 was published.
</t>
</section>
<section title="IANA Considerations">
<t>
IANA is to update the derived property value registry according to RFC 5892
and property values as defined in The Unicode Standard version 6.0.
</t>
</section>
<section title="Security Considerations">
<t>
When the algorithm presented in RFC 5892 is applied using the property
definitions of Unicode Standard Version 6.0, the result will be different from when
it is applied using the property definitions of Unicode 5.2 for
the three code points discussed in this document in addition to the changes for code points
being unassigned in Unicode 5.2. The three code points are unlikely to occur
in internationalized domain names, however, so the security implications of the
changes are minor.
</t>
</section>
<section title="Acknowledgements">
<t>
The main contributors are (in alphabetical order)
Eric Brunner-Williams, Vint Cerf, Tina Dam,
Martin Duerst, John Klensin, Mark Davis,
Pete Resnick, Markus Scherer,
Andrew Sullivan, Kenneth Whistler and Nicholas Williams.
</t>
<t>
Not all contributors believe the
solution for the issues discussed in this document is optimal.
</t>
</section>
</middle>
<back>
<references title="Normative References">
&rfc5892;
<reference anchor="Unicode5.2"
target="http://www.unicode.org/versions/Unicode5.2.0/">
<front>
<title>The Unicode Standard, Version 5.2.0</title>
<author>
<organization>The Unicode Consortium</organization>
</author>
<date year="2009" />
</front>
<seriesInfo name="Unicode 5.0.0, Boston, MA, Addison-Wesley"
value="ISBN 0-321-48091-0" />
<seriesInfo name="as amended by"
value="Unicode 5.2.0 http://www.unicode.org/versions/Unicode5.2.0/" />
</reference>
<reference anchor="Unicode6">
<front>
<title>The Unicode Standard, Version 6.0.0</title>
<author>
<organization>The Unicode Consortium</organization>
</author>
<date month="October" year="2010" />
</front>
</reference>
</references>
<references title="Informative References">
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 02:59:20 |