Changeset 20


Ignore:
Timestamp:
Oct 16, 2010, 8:54:46 PM (9 years ago)
Author:
duerst@…
Message:

applied patch for issues #16
(http://trac.tools.ietf.org/wg/iri/trac/attachment/ticket/16/patch16a.txt)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-iri-3987bis/draft-ietf-iri-3987bis.xml

    r19 r20  
    15251525differ only by the suffix "#" are considered different regardless of
    15261526the scheme.</t>
    1527 
    1528 <t>((NOTE: THIS NEEDS TO BE UPDATED TO DEAL WITH IDNA8))
    1529 Some IRI schemes may allow the usage of Internationalized Domain
    1530 Names (IDN) <xref target="RFC3490"></xref> either in their ireg-name
    1531 part or elsewhere. When in use in IRIs, those names SHOULD be
    1532 validated by using the ToASCII operation defined in <xref
    1533 target="RFC3490"></xref>, with the flags "UseSTD3ASCIIRules" and
    1534 "AllowUnassigned". An IRI containing an invalid IDN cannot
    1535 successfully be resolved.  Validated IDN components of IRIs SHOULD be
    1536 character normalized by using the Nameprep process <xref
    1537 target="RFC3491"></xref>; however, for legibility purposes, they
     1527 
     1528<t>Some IRI schemes allow the usage of Internationalized Domain
     1529Names (IDN) <xref target='RFC5890'></xref> either in their ireg-name
     1530part or elswhere. When in use in IRIs, those names SHOULD
     1531conform to the definition of U-Label in <xref
     1532target='RFC5890'></xref>. An IRI containing an invalid IDN cannot
     1533successfully be resolved. For legibility purposes, they
    15381534SHOULD NOT be converted into ASCII Compatible Encoding (ACE).</t>
    15391535
Note: See TracChangeset for help on using the changeset viewer.