Opened 10 years ago

Closed 9 years ago

#16 closed defect (fixed)

reference IDNABIS, not IDNA

Reported by: lmm@… Owned by: duerst@…
Priority: major Milestone:
Component: 3987bis Version:
Severity: - Keywords:

Description (last modified by addison@…)

< Some IRI schemes may allow the usage of Internationalized Domain
< Names (IDN) <xref target="RFC3490"></xref> either in their ireg-name
< part or elsewhere. When in use in IRIs, those names SHOULD be
< validated by using the ToASCII operation defined in <xref
< target="RFC3490"></xref>, with the flags "UseSTD3ASCIIRules" and
< "AllowUnassigned?". An IRI containing an invalid IDN cannot
< successfully be resolved. Validated IDN components of IRIs SHOULD be
< character normalized by using the Nameprep process <xref
< target="RFC3491"></xref>; however, for legibility purposes, they
< SHOULD NOT be converted into ASCII Compatible Encoding (ACE).</t>

<t>Some IRI schemes allow the usage of non-ASCII characters in the
ireg-name portion of the IRI. In almost all cases, these strings are
intended to be treated as Internationalized Domain Names (IDN) <xref
target="IDNABIS"/>. When used in an IRI, a string might be invalid
as a domain name.

Attachments (1)

patch16a.txt (1.5 KB) - added by duerst@… 9 years ago.
Replacing "ToASCII" by requirement to have an U-Label.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 9 years ago by duerst@…

Discussion of details, in particular the right replacement for ToASCII, starting at

Changed 9 years ago by duerst@…

Replacing "ToASCII" by requirement to have an U-Label.

comment:2 Changed 9 years ago by duerst@…

  • Owner set to duerst@…

comment:3 Changed 9 years ago by duerst@…

comment:4 Changed 9 years ago by addison@…

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

I have marked this item as 'fixed' because the proposed text appears in draft-02. Please comment on list if you object.

Note: See TracTickets for help on using tickets.