Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD review comments
Nicolas Williams <Nicolas.Williams@sun.com> Wed, 10 October 2007 15:53 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 1IfdsY-0001DO-28; Wed, 10 Oct 2007 11:53:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfdsX-0001DC-6Y for channel-binding@ietf.org; Wed, 10 Oct 2007 11:53:45 -0400
Received: from sca-ea-mail-4.sun.com ([192.18.43.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IfdsR-0006ZI-JM for channel-binding@ietf.org; Wed, 10 Oct 2007 11:53:45 -0400
Received: from centralmail2brm.Central.Sun.COM ([129.147.62.14]) by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9AFrSUO001356 for <channel-binding@ietf.org>; Wed, 10 Oct 2007 15:53:28 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by centralmail2brm.Central.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL, v2.2) with ESMTP id l9AFrSx6005181 for <channel-binding@ietf.org>; Wed, 10 Oct 2007 09:53:28 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id l9AFrRxj026013; Wed, 10 Oct 2007 10:53:27 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id l9AFrRnc026012; Wed, 10 Oct 2007 10:53:27 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 10 Oct 2007 10:53:27 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD review comments
Message-ID: <20071010155327.GC24532@Sun.COM>
Mail-Followup-To: Jeffrey Hutzelman <jhutz@cmu.edu>, Sam Hartman <hartmans-ietf@mit.edu>, channel-binding@ietf.org, ietf-sasl@imc.org
References: <20071010154115.GY24532@Sun.COM> <Pine.LNX.4.33L.0710101142360.5381-100000@minbar.fac.cs.cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33L.0710101142360.5381-100000@minbar.fac.cs.cmu.edu>
User-Agent: Mutt/1.5.7i
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: ietf-sasl@imc.org, channel-binding@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>
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
On Wed, Oct 10, 2007 at 11:51:03AM -0400, Jeffrey Hutzelman wrote: > On Wed, 10 Oct 2007, Nicolas Williams wrote: > > I don't agree. The I-D is clear on channel bindings being a single > > octet string. The prefix is a US-ASCII string prefixed to the raw > > channel binding octet string. After the prefix is added you still have > > a single octet string. > > Ah, but the spec doesn't actually _say_ that. It doesn't actually say > anywhere that the prefix is prepended to the channel-specific binding > data, resulting in a single octet string for the application to transport. > On the other hand, it _does_ say that the application needs to distinguish > channel types based on the prefix, which suggests (but only suggests) that > they are treated as separate items. Well, OK, we can clarify that. > If it's a single string, then you need a separator, for two reasons: > > - Without it, it's not good enough for prefixes to be unique; it must be > the case that no prefix is an initial substring of another. > > - Without a separator, it is difficult for the application (or library) > to separate the prefix from the data, which it must do in order to > determine the channel type, which affects interpretation of the data. > > Of course, one could use another approach, like a counted string, or a > fixed-width field, or a fixed-size integer. I don't care much. Sure. I'll send text this afternoon. Nico -- _______________________________________________ CHANNEL-BINDING mailing list CHANNEL-BINDING@ietf.org https://www1.ietf.org/mailman/listinfo/channel-binding
- [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD revi… Sam Hartman
- [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD revi… Simon Josefsson
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD revi… Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD revi… Simon Josefsson
- [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD revi… Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Simon Josefsson
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Simon Josefsson
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Simon Josefsson
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Nicolas Williams
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Alexey Melnikov
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Simon Josefsson
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Sam Hartman
- Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD … Jeffrey Hutzelman