IETF Logo Mail Archive

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

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 23 October 2007 08:48 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 1IkFRP-0008EI-N8; Tue, 23 Oct 2007 04:48:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkFRO-0008DR-7u for channel-binding@ietf.org; Tue, 23 Oct 2007 04:48:46 -0400
Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkFRH-0004S0-UG for channel-binding@ietf.org; Tue, 23 Oct 2007 04:48:46 -0400
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <Rx21ZQBLTgOG@rufus.isode.com>; Tue, 23 Oct 2007 09:48:38 +0100
Message-ID: <471DB564.5080805@isode.com>
Date: Tue, 23 Oct 2007 09:48:36 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Sam Hartman <hartmans-ietf@mit.edu>
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> <tsl1wbm68ab.fsf@mit.edu>
In-Reply-To: <tsl1wbm68ab.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

Sam Hartman wrote:

>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).
>"
>  
>
I like this.


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

v2.23.0 | Report a Bug | By Email