Changeset 28


Ignore:
Timestamp:
Nov 2, 2010, 2:03:31 AM (9 years ago)
Author:
duerst@…
Message:

Fixing Ticket #29 (include tag ranges in iprivate production):

  • Created text that points out the difference from RFC 3987, 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), 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.
File:
1 edited

Legend:

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

    r27 r28  
    1818<!ENTITY rfc3629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3629.xml">
    1919<!ENTITY rfc3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
     20<!ENTITY rfc3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3987.xml">
    2021<!ENTITY rfc5890 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5890.xml">
    2122<!ENTITY rfc5891 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5891.xml">
     
    23372338</section>
    23382339
     2340<section title="Main Changes Since RFC 3987">
     2341  <t>This section describes the main changes since <xref target="RFC3987"></xref>.</t>
     2342  <section title="Major restructuring of IRI processing model" anchor="forkChanges">
     2343    <t>Major restructuring of IRI processing model to make scheme-specific translation necessary to handle IDNA requirements and for consistency with web implementations. </t>
     2344    <t>Starting with IRI, you want one of:
     2345      <list style="hanging">
     2346        <t hangText="a"> IRI components (IRI parsed into UTF8 pieces)</t>
     2347        <t hangText="b"> URI components (URI parsed into ASCII pieces, encoded correctly) </t>
     2348        <t hangText="c"> whole URI  (for passing on to some other system that wants whole URIs) </t>
     2349      </list></t>
     2350   
     2351    <section title="OLD WAY">
     2352      <t><list style="numbers">
     2353       
     2354        <t>Pct-encoding on the whole thing to a URI.
     2355          (c1) If you want a (maybe broken) whole URI, you might
     2356          stop here.</t>
     2357       
     2358        <t>Parsing the URI into URI components.
     2359          (b1) If you want (maybe broken) URI components, stop here.</t>
     2360       
     2361        <t> Decode the components (undoing the pct-encoding).
     2362          (a) if you want IRI components, stop here.</t>
     2363       
     2364        <t> reencode:  Either using a different encoding some components
     2365          (for domain names, and query components in web pages, which
     2366          depends on the component, scheme and context), and otherwise
     2367          using pct-encoding.
     2368          (b2) if you want (good) URI components, stop here.</t>
     2369       
     2370        <t> reassemble the reencoded components.
     2371          (c2) if you want a (*good*) whole URI stop here.</t>
     2372      </list>
     2373       
     2374      </t>
     2375     
     2376    </section>
     2377   
     2378    <section title="NEW WAY">
     2379      <t>
     2380        <list style="numbers">
     2381         
     2382          <t> Parse the IRI into IRI components using the generic syntax.
     2383            (a) if you want IRI components, stop here.</t>
     2384         
     2385          <t> Encode each components, using pct-encoding, IDN encoding, or
     2386            special query part encoding depending on the component
     2387            scheme or context. (b) If you want URI components, stop here.</t>
     2388          <t> reassemble the a whole URI from URI components.
     2389            (c) if you want a whole URI stop here.</t>
     2390        </list></t>
     2391    </section>
     2392    <section title="Extension of Syntax">
     2393      <t>Added the tag range (U+E0000-E0FFF) to the iprivate production.
     2394        Some IRIs generated with the new syntax may fail to pass very strict checks
     2395        relying on the old syntax. But characters in this range should be extremely infrequent
     2396        anyway.</t>
     2397    </section>
     2398    <section title="More to be added"><t>TODO: There are more main changes that need to be
     2399      documented in this section.</t></section>
     2400</section>
    23392401
    23402402<section title="Change Log">
     
    23422404<t>Note to RFC Editor: Please completely remove this section before publication.</t>
    23432405
     2406<section title='Changes after draft-ietf-iri-3987bis-01'>
     2407    <t>Changes from draft-ietf-iri-3987bis-01 onwards are available as changesets
     2408      in the IETF tools subversion repository at
     2409      http://trac.tools.ietf.org/wg/iri/trac/log/draft-ietf-iri-3987bis/draft-ietf-iri-3987bis.xml.</t>
     2410</section>
     2411 
    23442412<section title='Changes from draft-duerst-iri-bis-07 to draft-ietf-iri-3987bis-00'>
    23452413     <t>Changed draft name, date, last paragraph of abstract, and titles in change log, and added this section
     
    23472415</section>
    23482416
    2349 <section title="Changes from -06 to -07 of draft-duerst-iri-bis" anchor="forkChanges"><t>
    2350 
    2351 Major restructuring of IRI processing model to make scheme-specific translation necessary to handle IDNA requirements and for consistency with web implementations. </t>
    2352 <t>Starting with IRI, you want one of:
    2353 <list style="hanging">
    2354 <t hangText="a"> IRI components (IRI parsed into UTF8 pieces)</t>
    2355 <t hangText="b"> URI components (URI parsed into ASCII pieces, encoded correctly) </t>
    2356 <t hangText="c"> whole URI  (for passing on to some other system that wants whole URIs) </t>
    2357 </list></t>
    2358 
    2359 <section title="OLD WAY">
    2360 <t><list style="numbers">
    2361 
    2362  <t>Pct-encoding on the whole thing to a URI.
    2363  (c1) If you want a (maybe broken) whole URI, you might
    2364         stop here.</t>
    2365 
    2366  <t>Parsing the URI into URI components.
    2367    (b1) If you want (maybe broken) URI components, stop here.</t>
    2368 
    2369  <t> Decode the components (undoing the pct-encoding).
    2370    (a) if you want IRI components, stop here.</t>
    2371 
    2372  <t> reencode:  Either using a different encoding some components
    2373    (for domain names, and query components in web pages, which
    2374    depends on the component, scheme and context), and otherwise
    2375    using pct-encoding.
    2376    (b2) if you want (good) URI components, stop here.</t>
    2377 
    2378  <t> reassemble the reencoded components.
    2379    (c2) if you want a (*good*) whole URI stop here.</t>
    2380 </list>
    2381 
    2382 </t>
    2383 
    2384 </section>
    2385 
    2386 <section title="NEW WAY">
    2387 <t>
    2388 <list style="numbers">
    2389 
    2390 <t> Parse the IRI into IRI components using the generic syntax.
    2391    (a) if you want IRI components, stop here.</t>
    2392 
    2393 <t> Encode each components, using pct-encoding, IDN encoding, or
    2394          special query part encoding depending on the component
    2395          scheme or context. (b) If you want URI components, stop here.</t>
    2396 <t> reassemble the a whole URI from URI components.
    2397    (c) if you want a whole URI stop here.</t>
    2398 </list></t>
     2417<section title="Changes from -06 to -07 of draft-duerst-iri-bis">
     2418  <t>Major restructuring of the processing model, see <xref target="forkChanges"></xref>.</t>
    23992419</section>
    24002420</section>
     
    25852605&rfc1738;
    25862606&rfc2640;
     2607&rfc3987;
    25872608<reference anchor='RFC4395bis'>
    25882609  <front>
Note: See TracChangeset for help on using the changeset viewer.