Re: [kitten] spaces in SASL user names

Simon Josefsson <> Wed, 11 April 2012 19:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 794D421F850F for <>; Wed, 11 Apr 2012 12:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -100.499
X-Spam-Status: No, score=-100.499 tagged_above=-999 required=5 tests=[AWL=0.810, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, J_CHICKENPOX_92=0.6, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id anLYMqviesNa for <>; Wed, 11 Apr 2012 12:20:43 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 9236521F851A for <>; Wed, 11 Apr 2012 12:20:42 -0700 (PDT)
Received: from ( []) (authenticated bits=0) by (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q3BJKGt5000734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 11 Apr 2012 21:20:22 +0200
From: Simon Josefsson <>
To: Peter Saint-Andre <>
References: <4F84AAA5.3030104__43291.804000228$1334094511$gmane$> <> <4F85A5DF.9050701__25300.7611529485$1334160852$gmane$>
OpenPGP: id=B565716F; url=
Date: Wed, 11 Apr 2012 21:20:05 +0200
In-Reply-To: <4F85A5DF.9050701__25300.7611529485$1334160852$gmane$> (Peter Saint-Andre's message of "Wed, 11 Apr 2012 09:40:15 -0600")
Message-ID: <>
User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: "" <>
Subject: Re: [kitten] spaces in SASL user names
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Apr 2012 19:20:44 -0000

Peter Saint-Andre <> writes:

> On 4/11/12 1:01 AM, Simon Josefsson wrote:
>> Peter Saint-Andre <> writes:
>>> 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?
>> I have seen real human names used for authentication identifiers
>> more than once, so I believe the answer is yes.
>> /Simon
> Thanks for the input. So my next question is:
>>> 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.
> Feedback is welcome. :)

I believe there is some serious terminology issue if there is resistance
to including space into a class of characters defined like this:

   NameClass:  a sequence of letters, numbers, and symbols that is used
      to identify or address a network entity such as a user account, a
      venue (e.g., a chatroom), an information source (e.g., a data
      feed), or a collection of data (e.g., a file).

Reflecting on my own usage, I have used SP in most of these types of
identifiers.  Some I use daily (user accounts and filenames).