Changeset 63


Ignore:
Timestamp:
Mar 29, 2011, 7:56:06 PM (9 years ago)
Author:
duerst@…
Message:

Replace "ToASCII" operation with corresponding text for IDNA 2008.

File:
1 edited

Legend:

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

    r62 r63  
    692692  <t>For example, the IRI
    693693    <vspace/>"http://r&amp;#xE9;sum&amp;#xE9;.example.org"<vspace/> will be
    694     converted to <vspace/>"http://r%C3%A9sum%C3%A9.example.org". </t>
     694    converted to <vspace/>"http://r%C3%A9sum%C3%A9.example.org".</t>
    695695
    696696
     
    698698
    699699<t>Replace the ireg-name part of the IRI by the part converted using
    700 the ToASCII operation specified in Section 4.1 of <xref
    701 target="RFC3490"/> on each dot-separated label, and by using U+002E
    702 (FULL STOP) as a label separator, with the flag UseSTD3ASCIIRules set
    703 to FALSE, and with the flag AllowUnassigned set to FALSE.
    704 The ToASCII operation may
    705 fail, but this would mean that the IRI cannot be resolved.
     700the Domain Name Lookup procedure (Subsections 5.3 to 5.5) of <xref target="RFC5891"/>.
     701  on each dot-separated label, and by using U+002E
     702(FULL STOP) as a label separator.
     703This procedure may fail, but this would mean that the IRI cannot be resolved.
    706704In such cases, if the domain name conversion fails, then the
    707705entire IRI conversion fails. Processors that have no mechanism for
    708706signalling a failure MAY instead substitute an otherwise
    709 invalid host name, although such processing SHOULD be avoided.
    710  </t>
     707invalid host name, although such processing SHOULD be avoided.</t>
    711708
    712709<t>For example, the IRI
     
    14451442
    14461443<t>Various IRI schemes may allow the usage of Internationalized Domain
    1447 Names (IDN) <xref target="RFC3490"></xref> either in the ireg-name
     1444Names (IDN) <xref target="RFC5890"/> either in the ireg-name
    14481445part or elsewhere. Character Normalization also applies to IDNs, as
    1449 discussed in <xref target="schemecomp"></xref>.</t>
     1446discussed in <xref target="schemecomp"/>.</t>
    14501447</section> <!-- charnorm -->
    14511448
Note: See TracChangeset for help on using the changeset viewer.