Re: [precis] spaces in usernames

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 05 March 2012 17:02 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDA6121F882C for <precis@ietfa.amsl.com>; Mon, 5 Mar 2012 09:02:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level:
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, 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 iq+f6bRCWUSj for <precis@ietfa.amsl.com>; Mon, 5 Mar 2012 09:02:07 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id DC8DE21F881E for <precis@ietf.org>; Mon, 5 Mar 2012 09:02:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1330966921; d=isode.com; s=selector; i=@isode.com; bh=ptx9bJeZ+lBUpvioEvUpYNSq6a5Oo55m1CmofnuQyZE=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=M826AZbSlq16yJ8YqL1ceqAWRhp9ImZ1tjrCF5fFfCH7pJOVsrtsCKPHjHzthqED0rd0Xt 4AiEuncAkwag+MFDTIFrHaC0PIpAAhYOCS22vVesfABivl3kz9faWKcvrfm1qmAXfaUoVG yeX5bz2+2hN90hH83GPvRfiC4XU6xOU=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <T1TxhwBhuka=@rufus.isode.com>; Mon, 5 Mar 2012 17:02:01 +0000
Message-ID: <4F54F1AA.4060703@isode.com>
Date: Mon, 05 Mar 2012 17:02:34 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: Alan DeKok <aland@deployingradius.com>
References: <4F51442E.10209@stpeter.im> <4F51D1F0.4010303@deployingradius.com>
In-Reply-To: <4F51D1F0.4010303@deployingradius.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "precis@ietf.org" <precis@ietf.org>
Subject: Re: [precis] spaces in usernames
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/precis>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 17:02:08 -0000

On 03/03/2012 08:10, Alan DeKok wrote:
> Peter Saint-Andre wrote:
>> Alexey and I are working on an I-D to replace SASLprep (RFC 4013). One
>> issue we found is that, in RFC 4013, spaces were allowed in usernames. I
>> know the framework document now allows spaces in passphrases, but I'm
>> wondering if we also want to allow spaces in usernames. Something to
>> discuss in Paris, perhaps...
>    In a theoretical sense, yes.
>
>    Practically, usernames are largely email addresses.  And I've rarely
> seen spaces used in practice.
Spaces are allowed in email addresses, if quoted. Of course no sane 
person would pick an email address with spaces on the left hand side (as 
this is unlikely to work in many places), but at least SMTP allows for that.
(And then there are email addresses used for gatewaying from other 
systems like X.400. Such email addresses can also contain spaces)

I would be happy with discouraging spaces in usernames, but I don't 
think we can just prohibit them.