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

Sam Hartman <hartmans-ietf@mit.edu> Tue, 23 October 2007 13:17 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 1IkJdT-0000Yf-QB; Tue, 23 Oct 2007 09:17:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkJdS-0000Mh-L5 for channel-binding@ietf.org; Tue, 23 Oct 2007 09:17:30 -0400
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IkJdM-0005sL-Mf for channel-binding@ietf.org; Tue, 23 Oct 2007 09:17:25 -0400
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C7CEC4A45; Tue, 23 Oct 2007 09:17:22 -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> <tsl1wbm68ab.fsf@mit.edu> <87ve8y2mpb.fsf@mocca.josefsson.org>
Date: Tue, 23 Oct 2007 09:17:22 -0400
In-Reply-To: <87ve8y2mpb.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Tue, 23 Oct 2007 11:40:32 +0200")
Message-ID: <tslmyuax95p.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: ea4ac80f790299f943f0a53be7e1a21a
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

>>>>> "Simon" == Simon Josefsson <simon@josefsson.org> writes:

    Simon> Sam Hartman <hartmans-ietf@mit.edu> writes:
    >> 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).
    >> "

    Simon> I like it.

    Simon> Is it specified that the channel binding unique prefix
    Simon> cannot contain ASCII 0x3a?

Yes.
alphanum plus '.' and '-'

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