Changeset 53


Ignore:
Timestamp:
Mar 28, 2011, 10:18:24 PM (9 years ago)
Author:
duerst@…
Message:

removed detailed discussion of spoofing on lookalikes and for percent-encoding

File:
1 edited

Legend:

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

    r52 r53  
    22862286users to create resources in the same sub area have to be careful.
    22872287Details are discussed in <xref target="selection"/>.</t>
    2288 
    2289 <t>Spoofing can occur because in the UCS many characters look very similar. Details are discussed in <xref target="selection"/>.
    2290 Again, this is very similar to spoofing possibilities on US-ASCII,
    2291 e.g., using "br0ken" or "1ame" URIs.</t>
    2292 
    2293 <t>Spoofing can occur when URIs with percent-encodings based on various
    2294 character encodings are accepted to deal with older user agents. In some
    2295 cases, particularly for Latin-based resource names, this is usually easy to
    2296 detect because UTF-8-encoded names, when interpreted and viewed as
    2297 legacy character encodings, produce mostly garbage.</t><t>When
    2298 concurrently used character encodings have a similar structure but there
    2299 are no characters that have exactly the same encoding, detection is more
    2300 difficult.</t>
    23012288
    23022289<t>Spoofing can occur with bidirectional IRIs, if the restrictions
Note: See TracChangeset for help on using the changeset viewer.