[rfc-i] Pagination requirements

Peter Saint-Andre stpeter at stpeter.im
Tue May 15 15:04:21 PDT 2012


On 5/15/12 4:02 PM, Julian Reschke wrote:
> On 2012-05-16 00:00, Peter Saint-Andre wrote:
>> ...
>> P.S. Here's a relevant paragraph from a discussion about visually
>> similar characters in the security considerations of an I-D I'm working
>> on (draft-ietf-precis-framework)...
>>
>>     However, the problem is made more serious by introducing the full
>>     range of Unicode code points into protocol strings.  For example, the
>>     characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 from the
>>     Cherokee block look similar to the US-ASCII characters "STPETER" as
>>     they might look when presented in a "creative" font.
>>
>> It would be helpful to include the actual characters, not just the
>> Unicode codepoint numbers:
>>
>>     However, the problem is made more serious by introducing the full
>>     range of Unicode code points into protocol strings.  For example, the
>>     characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 from the
>>     Cherokee block, i.e., "ᏚᎢᎵᏋᎢᏋᏒ", look similar to the US-ASCII
>>     characters "STPETER" as they might look when presented in a
>>     "creative" font.
>> ...
> 
> +1
> 
> And hey, it even works in email ;-)

My point exactly. It works in the media that we use for various kinds of
discussion: email, jabber rooms, presentations at meetings, etc. But it
doesn't work in our publication medium. And that's a shame.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/




More information about the rfc-interest mailing list