Changeset 106


Ignore:
Timestamp:
Mar 11, 2012, 11:45:43 PM (8 years ago)
Author:
duerst@…
Message:

Updated mailto: reference from RFC2368 to RFC6068. Removed mention of mailto: as an example of highly scheme-specific provisions for the encoding of non-ASCII characters. Added reference to RFC 6068 and RFC 5122 (XMPP URLs) to list of schemes that already use UTF-8.

File:
1 edited

Legend:

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

    r105 r106  
    66<!ENTITY rfc2192 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2192.xml">
    77<!ENTITY rfc2277 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2277.xml">
    8 <!ENTITY rfc2368 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2368.xml">
    98<!ENTITY rfc2384 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2384.xml">
    109<!ENTITY rfc2396 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2396.xml">
     
    1615<!ENTITY rfc3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
    1716<!ENTITY rfc3987 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3987.xml">
     17<!ENTITY rfc5122 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5122.xml">
    1818<!ENTITY rfc5890 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5890.xml">
    1919<!ENTITY rfc5891 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5891.xml">
    2020<!ENTITY rfc5892 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5892.xml">
    2121<!ENTITY rfc6055 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6055.xml">
     22<!ENTITY rfc6068 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6068.xml">
    2223]>
    2324<?rfc strict='yes'?>
     
    10121013target="RFC4395bis"/>.  Examples where UTF-8 is already used are the URN
    10131014syntax <xref target="RFC2141"/>, IMAP URLs <xref target="RFC2192"/>,
    1014 and POP URLs <xref target="RFC2384"/>.  On the other hand, because the
     1015POP URLs <xref target="RFC2384"/>, XMPP URLs <xref target='RFC5122'/>,
     1016and the 'mailto:' scheme <xref target='RFC6068'/>. On the other hand, because the
    10151017HTTP URI scheme does not specify how to encode original characters,
    10161018only some HTTP URLs can have corresponding but different IRIs.</t>
     
    10341036characters with no provision to include non-ASCII characters/octets
    10351037via percent-encoding, or if a scheme definition currently uses highly
    1036 scheme-specific provisions for the encoding of non-ASCII characters.
    1037 An example of this is the mailto: scheme <xref target="RFC2368"/>.</t>
     1038scheme-specific provisions for the encoding of non-ASCII characters.</t>
    10381039
    10391040<t>This specification updates the IANA registry of URI schemes to note
     
    18191820&rfc2192;
    18201821&rfc2277;
    1821 &rfc2368;
    18221822&rfc2384;
    18231823&rfc2396;
     
    18261826&rfc2640;
    18271827&rfc3987;
     1828&rfc5122;
    18281829&rfc6055;
     1830&rfc6068;
    18291831
    18301832<reference anchor='Bidi'>
Note: See TracChangeset for help on using the changeset viewer.