[kitten] spaces in SASL user names

Peter Saint-Andre <stpeter@stpeter.im> Tue, 10 April 2012 21:48 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 B4C3F21F867B for <kitten@ietfa.amsl.com>; Tue, 10 Apr 2012 14:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.384
X-Spam-Level:
X-Spam-Status: No, score=-102.384 tagged_above=-999 required=5 tests=[AWL=-0.385, BAYES_00=-2.599, J_CHICKENPOX_92=0.6, 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 rPzalmJY-4-k for <kitten@ietfa.amsl.com>; Tue, 10 Apr 2012 14:48:23 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 9F41D21F84DC for <kitten@ietf.org>; Tue, 10 Apr 2012 14:48:22 -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 18EBB40058 for <kitten@ietf.org>; Tue, 10 Apr 2012 16:02:11 -0600 (MDT)
Message-ID: <4F84AAA5.3030104@stpeter.im>
Date: Tue, 10 Apr 2012 15:48:21 -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: "kitten@ietf.org" <kitten@ietf.org>
X-Enigmail-Version: 1.4
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [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: Tue, 10 Apr 2012 21:48:23 -0000

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

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?

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?

Option #3 seems preferable to (a) specifying that the PRECIS NameClass
needs to include space (to which there was a lot of resistance during
the PRECIS WG session), (b) enabling folks to superclass PRECIS string
classes (to which there was also a lot of resistance), or (c) severely
subclassing the PRECIS FreeClass to be something like NameClass+SP.

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+EqqUACgkQNL8k5A2w/vzHeQCfTX6rF+MAqj05uz/ojJpPDkMT
RaMAn2AWoWO3lRiDgxfPmDZy7B4wyawX
=xNtO
-----END PGP SIGNATURE-----