[CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD review comments

Simon Josefsson <simon@josefsson.org> Tue, 09 October 2007 20:51 UTC

Return-path: <channel-binding-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfM3W-0007oX-FK; Tue, 09 Oct 2007 16:51:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfM3U-0007iB-Qw for channel-binding@ietf.org; Tue, 09 Oct 2007 16:51:52 -0400
Received: from yxa.extundo.com ([83.241.177.38]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IfM3U-0006YD-2D for channel-binding@ietf.org; Tue, 09 Oct 2007 16:51:52 -0400
Received: from mocca.josefsson.org (yxa.extundo.com [83.241.177.38]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l99KpiBA011783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Oct 2007 22:51:45 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <tslbqcf8eou.fsf@mit.edu> <871wc46umk.fsf@mocca.josefsson.org> <tsl4ph0vz30.fsf@mit.edu> <20071009203406.GL24532@Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:071009:ietf-sasl@imc.org::gWNXqVjMnXDRiNkf:WxHY
X-Hashcash: 1:22:071009:hartmans-ietf@mit.edu::WkHu1AmaPHL7Vry0:MGS9
X-Hashcash: 1:22:071009:channel-binding@ietf.org::M59V2kxQtiU6Xos5:SH0M
Date: Tue, 09 Oct 2007 22:51:44 +0200
In-Reply-To: <20071009203406.GL24532@Sun.COM> (Nicolas Williams's message of "Tue, 9 Oct 2007 15:34:06 -0500")
Message-ID: <87tzp02eqn.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Status: No, score=-0.0 required=4.0 tests=SPF_PASS autolearn=disabled version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on yxa-iv
X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on yxa.extundo.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: channel-binding@ietf.org, ietf-sasl@imc.org
Subject: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD review comments
X-BeenThere: channel-binding@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of channel binding IANA registry requests and specifications <channel-binding.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/channel-binding>, <mailto:channel-binding-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/channel-binding>
List-Post: <mailto:channel-binding@ietf.org>
List-Help: <mailto:channel-binding-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/channel-binding>, <mailto:channel-binding-request@ietf.org?subject=subscribe>
Errors-To: channel-binding-bounces@ietf.org

Nicolas Williams <Nicolas.Williams@Sun.COM> writes:

> On Tue, Oct 09, 2007 at 03:59:31PM -0400, Sam Hartman wrote:
>>     Simon> I thought that channel binding data had to contain a unique
>>     Simon> prefix which would appears to solve that problem, without
>>     Simon> having to require that protocols encode the channel binding
>>     Simon> type too.  If my assumption is correct, it would be useful
>>     Simon> to clarify this in d-w-on-channel-binding.  No change in
>>     Simon> GS2 seems necessary.  Nico?
>> 
>> I thought it was the responsibility of the application|framework to
>> add the unique prefix.  The channel binding base draft provides a
>> registry for this prefix, but I thought that the channel binding
>> description did not include this prefix and left it up to the
>> application.  If the channel binding format must include the prefix
>> then I think we need to change the channel binding base draft.
>
> Sam is correct.  In any case, I don't think the channel providing the
> bindings should be providing the prefix.

Could you suggest some text that would be appropriate in GS2 section 5?

It would help if on-channel-binding discussed its interface to
authentication protocols.  For example, what should GS2 say about
channel bindings that need confidentiality protection?  Can GS2 use such
a channel binding at all?

/Simon

_______________________________________________
CHANNEL-BINDING mailing list
CHANNEL-BINDING@ietf.org
https://www1.ietf.org/mailman/listinfo/channel-binding