Changeset 15


Ignore:
Timestamp:
Sep 21, 2010, 2:58:06 AM (9 years ago)
Author:
duerst@…
Message:

removed an open issue in the draft because it was moved to the tracker as http://trac.tools.ietf.org/wg/iri/trac/ticket/43.

File:
1 edited

Legend:

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

    r14 r15  
    23422342<list style="hanging">
    23432343
    2344 <t hangText="dealing with disallowed IRI characters"> </t>
    2345 
    2346 <t hangText="handling illegal characters">
    2347 
    2348 <xref target="compmapping" /> used to apply only to characters in
    2349 either 'ucschar' or 'iprivate', but then later said that systems
    2350 accepting IRIs MAY also deal with the printable characters in US-ASCII
    2351 that are not allowed in URIs, namely "&lt;", "&gt;", '"', space, "{",
    2352 "}", "|", "\", "^", and "`".  Larry felt that this a MAY would result
    2353 in non-uniform behavior, because some systems would produce valid URI
    2354 components and others wouldn't.  Non-printable US-ASCII characters
    2355 should be stripped by most software, so if they get to if they're
    2356 passed on somewhere as IRI characters, encoding them makes sense.
    2357 
    2358 The section also used to say "If these characters are found
    2359 but are not converted, then the conversion SHOULD fail." but there is
    2360 no notion of conversion failing -- every string is converted.  Please
    2361 note that the number sign ("#"), the percent sign ("%"), and the
    2362 square bracket characters ("[", "]") are not part of the above list
    2363 and MUST NOT be converted.
    2364  </t>
    23652344
    23662345</list></t>
Note: See TracChangeset for help on using the changeset viewer.