Re: [iri] #91: Mapping of <ireg-name>: preferred way?

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: [iri] #91: Mapping of <ireg-name>: preferred way?

iri issue tracker
#91: Mapping of <ireg-name>: preferred way?

Changes (by masinter@…):

 * owner:  draft-ietf-iri-3987bis@… => masinter@…


 I propose resolving this by being more specific about exactly when
 punicode encoding is acceptable, by changing

   <t>The ireg-name component MAY also be converted as follows:</t>


  <t>In situations where it is certain that the ireg-name is intended to be
 used as a domain name to be processed by Domain Name Lookup (as per <xref
 target="RFC53891"/>, an alternative method MAY may be used for converting
 the ireg-name component as follows:  </t>

 Is this OK?

 Reporter:  evnikita2@…  |       Owner:  masinter@…
     Type:  defect       |      Status:  new
 Priority:  critical     |   Milestone:
Component:  3987bis      |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |

Ticket URL: <>
iri <>