Re: [kitten] spaces in SASL user names

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 16 April 2012 10:52 UTC

Message-ID: <4F89AB89.8050303@isode.com>
Date: Sat, 14 Apr 2012 17:53:29 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4F84AAA5.3030104@stpeter.im> <4ED1D634F0E26CDC51B61127@[192.168.15.131]> <4F85C4EE.2020901@stpeter.im>
In-Reply-To: <4F85C4EE.2020901@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: kitten@ietf.org
Subject: Re: [kitten] spaces in SASL user names
Precedence: list

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
>> <stpeter@stpeter.im>  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] spaces in SASL user names Peter Saint-Andre
Re: [kitten] spaces in SASL user names Simon Josefsson
Re: [kitten] spaces in SASL user names Nico Williams
Re: [kitten] spaces in SASL user names Peter Saint-Andre
Re: [kitten] spaces in SASL user names Peter Saint-Andre
Re: [kitten] spaces in SASL user names Chris Newman
Re: [kitten] spaces in SASL user names Peter Saint-Andre
Re: [kitten] spaces in SASL user names Simon Josefsson
Re: [kitten] spaces in SASL user names Alexey Melnikov
Re: [kitten] spaces in SASL user names William Mills
Re: [kitten] spaces in SASL user names Peter Saint-Andre