Re: nickname length

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

My conclusion is: let the XMPP folks set a limit of 1023 bytes in
their use of the nickname spec, and let the MSRP folks do what they
please. This really isn't a matter for the nickname spec itself, I
think...

Peter

On 10/2/12 5:32 AM, Miguel A. Garcia wrote:
> Hi Peter:
> 
> It is true we don't have a limit in the nickname, for the same
> reason we don't have a limit in MSRP URIs, SIP URIs, Display-Names
> in SIP, etc.
> 
> I don't mind setting the limit to 1023 bytes as you mentioned.
> 
> /Miguel
> 
> On 22/09/2012 5:18, Peter Saint-Andre wrote: The more I think about
> this, the more I realize that nickname length is best left up to
> protocol specifications for MSRP and XMPP, not the nickname spec
> itself. Unless there are objections, I plan to remove the relevant
> paragraph from draft-ietf-precis-nickname.
> 
> On 9/21/12 2:30 PM, Peter Saint-Andre wrote:
>>>> Are there any limits on the length of a nickname in 
>>>> draft-ietf-simple-chat? I don't see any, nor do I see any on 
>>>> quoted-string in RFC 4975. In draft-ietf-precis-nickname, I
>>>> have a limit of 1023 bytes, which comes from RFC 6122 and is
>>>> probably longer than most people will ever use. I received
>>>> one comment that the nickname spec is the wrong place to be
>>>> imposing such limits, and that makes sense (XMPP can impose
>>>> one limit and MSRP can impose another limit, etc.). But I
>>>> figured it would be good to check here before making a change
>>>> to draft-ietf-precis-nickname on this point.
>>>> 
>>>> Thanks!
>>>> 
>>>> Peter
>>>> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBzE20ACgkQNL8k5A2w/vybbQCePFLYiinpbJLQGehczQMBkyhS
IssAnRv0uJYYQehKerSMxoDwp1Dx0p6C
=RgJe
-----END PGP SIGNATURE-----