-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/1/12 5:45 PM, "Martin J. Dürst" wrote:
> What about other spaces? With just ASCII spaces being removed,
> couldn't I spoof a nickname with e.g. a full-width space (U+3000)?
> Or is this already taken care by mapping or removing these?

Rule 3 in that section is:

   3.  Non-ASCII space characters from the "N" category defined under
       Section 6.14 of [I-D.ietf-precis-framework] MUST be mapped to
       U+0020 SPACE.

The rules are applied in order, so non-ASCII space character will have
already been mapped to ASCII space by the time the new rules I
proposed are applied.

Peter

> 
> Regards,   Martin.
> 
> On 2012/11/02 7:44, Peter Saint-Andre wrote: On 11/1/12 9:28 AM,
> Salvatore Loreto wrote:
>>>> On 11/1/12 4:27 PM, Joe Hildebrand (jhildebr) wrote:
>>>>> On 11/1/12 9:22 AM, "Alexey
>>>>> Melnikov"<[email protected]> wrote:
>>>>> 
>>>>>> +1 (both leading and trailing whitespaces are already 
>>>>>> disallowed in usernames).
>>>>> +1
>>>>> 
>>>> +1
> 
> OK, I propose adding the following rules to Section 2:
> 
> 4.  Leading and trailing whitespace (i.e., one or more instances
> of the ASCII space character at the beginning or end of a
> nickname) MUST be removed.
> 
> 5.  Interior sequences of more than one ASCII space character MUST
> be mapped to a single ASCII space character.
> 
> Peter
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCTE4MACgkQNL8k5A2w/vwPtACg0EYTTIXSiRLCs0SzbNSQKfxI
aLUAn1YJT3ffv1QjTlLWo0XrOB6b4gb5
=/9lN
-----END PGP SIGNATURE-----
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis

Reply via email to