IETF Logo Mail Archive

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

Sam Hartman <hartmans-ietf@mit.edu> Mon, 22 October 2007 23:26 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 1Ik6fS-0001s0-Tt; Mon, 22 Oct 2007 19:26:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ik6fQ-0001hg-AG for channel-binding@ietf.org; Mon, 22 Oct 2007 19:26:41 -0400
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ik6fL-0004az-US for channel-binding@ietf.org; Mon, 22 Oct 2007 19:26:36 -0400
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id EDFA64A45; Mon, 22 Oct 2007 19:26:04 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Simon Josefsson <simon@josefsson.org>
Subject: Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD review comments
References: <20071011173152.GR24532@Sun.COM> <Pine.LNX.4.33L.0710111343440.8820-100000@minbar.fac.cs.cmu.edu> <87ir5cy7dd.fsf@mocca.josefsson.org>
Date: Mon, 22 Oct 2007 19:26:04 -0400
In-Reply-To: <87ir5cy7dd.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Fri, 12 Oct 2007 12:06:38 +0200")
Message-ID: <tsl1wbm68ab.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: channel-binding@ietf.org, ietf-sasl@imc.org, Nicolas Williams <Nicolas.Williams@sun.com>
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

I just had a quick phone call with Nico.


He's still been thinking about this from the API standpoint.  I was
asking him why we wanted to support separate slots in the protocol for
channel binding type and channel binding data.I didn't understand the
complexity.  During the conversation it became clear that Nico
believed that at the end of the day you want to end up with a channel
binding type, a colon and some stuff.  I like that too.  I don't care
how it works in the API at all.


I propose  we accomplish this by adding the following requirement:

"Under this framework, channel bindings MUST start with the channel
binding unique prefix followed by a colon (ASCII 0x3A).
"

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

v2.23.0 | Report a Bug | By Email