Re: [kitten] spaces in SASL user names

[William Mills <[e-mail]>]

It should be noted that SMTP allows "domain specific usernames" with an extremely broad syntax that includes spaces.




>________________________________
> From: Alexey Melnikov <[e-mail]>
>To: Peter Saint-Andre <[e-mail]> 
>Cc: [e-mail] 
>Sent: Saturday, April 14, 2012 9:53 AM
>Subject: Re: [kitten] spaces in SASL user names
> 
>On 11/04/2012 18:52, Peter Saint-Andre wrote:
>> On 4/11/12 9:48 AM, Chris Newman wrote:
>>> --On April 10, 2012 15:48:21 -0600 Peter Saint-Andre
>>> <[e-mail]>  wrote: At the PRECIS WG session in Paris, we
>>> had quite a discussion about spaces in user names. Alexey
>>> maintained that this must have been included in SASLprep (RFC 4013)
>>> for a good reason, but the reason wasn't clear to folks in the
>>> meeting. So I have a few questions:
>>>
>>> 1. Do SASL user names really need to include spaces?
>>>
>>>> Absolutely yes. My correct name is "Chris Newman" (with a space).
>>>> A user friendly interface would use my correct name. Protocol
>>>> design should never unnecessarily obstruct the creation of user
>>>> friendly interfaces.
>>> 2. If SASL user names do *not* need to include spaces, would it be
>>> fine to re-use the PRECIS NameClass for simple user names in SASL?
>>>
>>> 3. If SASL user names *do* need to include spaces, would it be fine
>>> to define simple user names in SASL as a space-separated list of
>>> NameClass entities?
>>>
>>>> I am opposed to changing to the SASL user name ABNF in the
>>>> mechanisms, with RFC 4616 being the simplest example of that
>>>> ABNF. Given that constraint, I have little opinion about how
>>>> PRECIS is used. So the proposal sounds feasible as long as we're
>>>> not making ABNF changes to the underlying protocol.
>> The document that Alexey and I are working on will not override the
>> ABNF in any given mechanism spec (e.g., RFC 4616). However, we'll
>> probably want to look at how this work interacts with existing
>> mechanisms (e.g., would we need to update those mechanism specs to use
>> the PRECIS approach instead of the stringprep approach?).
>Yes. But hopefully several SASL mechanisms can be updated by a single 
>document.
>
>_______________________________________________
>Kitten mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/kitten
>
>
>