IETF Logo Mail Archive

Re: [precis] Review of draft-melnikov-precis-saslprepbis-03

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 17 September 2012 18:20 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 A2E2621F8700 for <precis@ietfa.amsl.com>; Mon, 17 Sep 2012 11:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level:
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36O4fdX6lk+l for <precis@ietfa.amsl.com>; Mon, 17 Sep 2012 11:20:21 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id C98D421F86EA for <precis@ietf.org>; Mon, 17 Sep 2012 11:20:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1347906019; d=isode.com; s=selector; i=@isode.com; bh=jd55oOh/qJcO3zd6NLmgMdsKKb9nPa5ogYVmgOrcMOc=; 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=PR5efSw+d5ZT+OvHGA58wk4KRJPiL1Ldg5gLb7JI6xkRwWDcjfw731YYjbGQ4PArn2lO/h IQumbrdiLmqb1yyRzWc+to3an2FPc1j8iy3WzYoOnkiAXJulh2PStYbrtdNwsbB+PZYcKz KY9J78p9zsSAbLyFCpglUvabSfrbs0M=;
Received: from [192.168.1.3] ((unknown) [94.29.63.162]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <UFdp4gBIr4Uo@statler.isode.com>; Mon, 17 Sep 2012 19:20:19 +0100
X-SMTP-Protocol-Errors: NORDNS
References: <20120914162208.30845.65648.idtracker@ietfa.amsl.com> <50535A6B.8010702@stpeter.im> <8FD6CBCE-60CD-4049-A0E6-B2388D6919DF@cisco.com>
In-Reply-To: <8FD6CBCE-60CD-4049-A0E6-B2388D6919DF@cisco.com>
Message-Id: <817D19D4-1615-440A-8F75-DEAEFE0BEA58@isode.com>
X-Mailer: iPad Mail (9B206)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Mon, 17 Sep 2012 19:21:57 +0100
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
Cc: "precis@ietf.org" <precis@ietf.org>
Subject: Re: [precis] Review of draft-melnikov-precis-saslprepbis-03
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, 17 Sep 2012 18:20:21 -0000

Hi Matt,

Sent from my iPad

On 17 Sep 2012, at 19:09, "Matt Miller (mamille2)" <mamille2@cisco.com> wrote:

> * 3.2 (Passwords - Preparation) :: I do wonder about the rationale for step 2) (map all non-ASCII space to ASCII space).  I myself have not run into conditions where this would matter, but I mostly deal with US-based consumers with passwords almost exclusively in the ASCII range.  On the surface, it seems a bit contradictory in principle to the "no bidi rule" rationale that is included. I'm not advocating for retention or removal of step 2), but rather for providing a rationale (one way or the other).

This rule was always in SASLPrep, so this is trying to preserve some sort of backward compatibility. Whether it is a good enough reason to keep the rule - I don't know.

v2.23.0 | Report a Bug | By Email