Re: [sasl] Clarification on the use of e= in SCRAM SASL/GS2

Paul Aurich <paul@darkrain42.org> Mon, 07 June 2010 21:35 UTC

Return-Path: <paul@darkrain42.org>
X-Original-To: sasl@core3.amsl.com
Delivered-To: sasl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 654E03A687C for <sasl@core3.amsl.com>; Mon, 7 Jun 2010 14:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikShWVeMFL0m for <sasl@core3.amsl.com>; Mon, 7 Jun 2010 14:34:47 -0700 (PDT)
Received: from mail.darkrain42.org (o-chul.darkrain42.org [IPv6:2001:470:1f05:d58::1]) by core3.amsl.com (Postfix) with ESMTP id 2BDC63A6879 for <sasl@ietf.org>; Mon, 7 Jun 2010 14:34:31 -0700 (PDT)
Received: from [192.168.0.8] (97-126-71-241.tukw.qwest.net [97.126.71.241]) by mail.darkrain42.org (mail.darkrain42.org) with ESMTPSA id 2A29A8065 for <sasl@ietf.org>; Mon, 7 Jun 2010 14:34:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=darkrain42.org; s=a; t=1275946467; bh=eMALhUK2+WhJWp5HD9fqmO8eGyAVdydXI7zu4/rmC40=; l=2638; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type; b=X5YuWBQtQwDnQGEUFa2G/gBkn5rvirp7+1iSs+l8B4mkZqKc2gGElYiXrDT//fTJ1 agfut7JaVYnXAH5Yef8o7DPB/lrRUXEhl5rpY6YlXGuZJfgIgNubx0bcD9owXSZObE 3PKJvRmebXIZ3wPLZZuXigjEGIuru4ftRJF3OaybV7vsCRW8sIpwXnzwNtf8XvtFKK veodbzE3f0BBdzIKbSWSPIVZDoceWSujxQnsr85g/kbI5L+2rzOSjCWpf3DMyOW/YY FOQIDePtf2UIEbmyOrMC3u297ybOseq/IC6QxrfhXn2w3f5VhGCaypYiFohBE8b2qD EXy6dIbGQp7iA==
Message-ID: <4C0D65D8.4010401@darkrain42.org>
Date: Mon, 07 Jun 2010 14:34:16 -0700
From: Paul Aurich <paul@darkrain42.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: SASL WG <sasl@ietf.org>
References: <4BCC5BD0.7060100@isode.com> <4BD900E0.1000103@darkrain42.org>
In-Reply-To: <4BD900E0.1000103@darkrain42.org>
X-Enigmail-Version: 1.0.1
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------enig8770D70202ADBF231308EBA7"
Subject: Re: [sasl] Clarification on the use of e= in SCRAM SASL/GS2
X-BeenThere: sasl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SASL Working Group <sasl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sasl>, <mailto:sasl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sasl>
List-Post: <mailto:sasl@ietf.org>
List-Help: <mailto:sasl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sasl>, <mailto:sasl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2010 21:35:12 -0000

On 2010-04-28 20:45, Paul Aurich wrote:
> I have no problem with the changes, but in looking at the ABNF value of the
> error, I'm confused by the meaning of the
> "server-does-support-channel-binding" error:
>                   "server-does-support-channel-binding" /
>                     ; server does not support channel binding
>                   "channel-binding-not-supported" /
> 
> In what case is this used, and are the text value/comment in conflict or is
> there something I'm missing?  (Should the comment come after the
> channel-binding-not-supported value, perhaps?)
> 
> Thanks,
> ~Paul

Since SCRAM is still in AUTH48, I thought I'd bring this up once more.

It's a simple case of "do comments bind to the thing above or below
them", but, considering that the two errors in question are "hey, I do
support channel binding" and "I don't support channel binding", clearing
this up would be great.

For reference, I think the comment is in the wrong place here (it should
appear *after* "channel-binding-not-supported") because the comment
comes after the error in question for these two:
                  "extensions-not-supported" /  ; unrecognized 'm' value
and
                  "invalid-username-encoding" /
                    ; invalid username encoding (invalid UTF-8 or
                    ; SASLprep failed)

Thanks,
~Paul