Re: [iri] 3987bis #29 (new): include tag ranges in iprivate production

#29: include tag ranges in iprivate production


Comment(by duerst@…):

 I have verified that the overall tag range (U+E0000-E0FFF) is already
 added in the syntax (this was done in draft-duerst-iri-bis-02).
 I have created text that points out the difference, as requested by Larry.
 The text reads:
 Added the tag range (U+E0000-E0FFF) to the iprivate production. Some IRIs
 generated with the new syntax may fail to pass very strict checks relying
 on the old syntax.

 To keep this text (the "Change Log" section is to be removed by the RFC
 editor), I have created a new section just above the "Change Log" section,
 entitled "Main Changes Since RFC 3987".

 Moved Larry's OLD/NEW text about the processing model to this section (It
 may need some more tweaking.) from the Change Log section.

 Added a dummy subsection to the "Major Changes" section to indicate that
 there are other major changes that need to go in this section.

 Added a reference to RFC 3987.

 Chairs: In my opinion, this issue can be closed.

-- 
------------------------------------+---------------------------------------
 Reporter:  duerst@…                |       Owner:  duerst@…              
     Type:  defect                  |      Status:  new                   
 Priority:  major                   |   Milestone:                        
Component:  3987bis                 |     Version:                        
 Severity:  -                       |    Keywords:                        
------------------------------------+---------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/29#comment:2>
iri <http://tools.ietf.org/bof/iri/>

Received on Tuesday, 2 November 2010 09:04:05 UTC