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

Sam Hartman <hartmans-ietf@mit.edu> Wed, 10 October 2007 15:54 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 1Ifdsu-0001Wa-Km; Wed, 10 Oct 2007 11:54:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ifdss-0001TV-V3 for channel-binding@ietf.org; Wed, 10 Oct 2007 11:54:06 -0400
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ifdsm-0006Zj-PD for channel-binding@ietf.org; Wed, 10 Oct 2007 11:54:06 -0400
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 32D9E48C4; Wed, 10 Oct 2007 11:53:50 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: [CHANNEL-BINDING] Re: draft-ietf-sasl-gs2 AD review comments
References: <tslbqcf8eou.fsf@mit.edu> <871wc46umk.fsf@mocca.josefsson.org> <tsl4ph0vz30.fsf@mit.edu> <20071009203406.GL24532@Sun.COM> <tslk5pwugzz.fsf@mit.edu> <20071009212516.GP24532@Sun.COM> <73A1D8BFF0B322B71283BF6B@sirius.fac.cs.cmu.edu> <20071010143650.GT24532@Sun.COM> <tslmyurnhmv.fsf@mit.edu> <20071010154115.GY24532@Sun.COM>
Date: Wed, 10 Oct 2007 11:53:50 -0400
In-Reply-To: <20071010154115.GY24532@Sun.COM> (Nicolas Williams's message of "Wed, 10 Oct 2007 10:41:16 -0500")
Message-ID: <tsld4vnj78x.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: 93238566e09e6e262849b4f805833007
Cc: channel-binding@ietf.org, ietf-sasl@imc.org
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" == Nicolas Williams <Nicolas.Williams@sun.com> writes:

    Nicolas> On Wed, Oct 10, 2007 at 10:55:52AM -0400, Sam Hartman
    Nicolas> wrote: I believe the text of the I-D is clear on the
    Nicolas> above.  Thus your protocol issues are taken care of.
    >>  Well, my reading of the ID is that the protocol needs two
    >> slots--one for a prefix and one for a channel binding octec
    >> string.  Simon is arguing that we only want to have one slot.
    >> I'm fine with that if we want to make that change.

    Nicolas> I don't agree.  The I-D is clear on channel bindings
    Nicolas> being a single octet string.  The prefix is a US-ASCII
    Nicolas> string prefixed to the raw channel binding octet string.
    Nicolas> After the prefix is added you still have a single octet
    Nicolas> string.

O, I think Simon and I thought it was called a prefix because we
expected it to be prefixed in a lot of protocols.  I don't read the
current text that way at all.

I think Simon, Jeff and I would be happy if the draft did actually say
that.
Simon, would you be willing to propose a change?


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