Re: [kitten] spaces in SASL user names

Peter Saint-Andre <stpeter@stpeter.im> Wed, 11 April 2012 17:52 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 511A011E8089 for <kitten@ietfa.amsl.com>; Wed, 11 Apr 2012 10:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.669
X-Spam-Level:
X-Spam-Status: No, score=-102.669 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aUINm+hwpqzK for <kitten@ietfa.amsl.com>; Wed, 11 Apr 2012 10:52:51 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 91C2821F8504 for <kitten@ietf.org>; Wed, 11 Apr 2012 10:52:49 -0700 (PDT)
Received: from dhcp-64-101-72-235.cisco.com (unknown [64.101.72.235]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 99DFB40058; Wed, 11 Apr 2012 12:06:40 -0600 (MDT)
Message-ID: <4F85C4EE.2020901@stpeter.im>
Date: Wed, 11 Apr 2012 11:52:46 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Chris Newman <chris.newman@oracle.com>
References: <4F84AAA5.3030104@stpeter.im> <4ED1D634F0E26CDC51B61127@[192.168.15.131]>
In-Reply-To: <4ED1D634F0E26CDC51B61127@[192.168.15.131]>
X-Enigmail-Version: 1.4
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: kitten@ietf.org
Subject: Re: [kitten] spaces in SASL user names
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 17:52:53 -0000

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

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?).

Peter

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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+FxO4ACgkQNL8k5A2w/vwPkQCg0taqYm1blZ2WuHDkFjLa2rNs
ElYAoIK7mZBI8chbHj/R5GysmrZtHdMh
=moOP
-----END PGP SIGNATURE-----