IETF Logo Mail Archive

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

Nicolas Williams <Nicolas.Williams@sun.com> Thu, 11 October 2007 17:32 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 1Ig1tS-0007cB-5y; Thu, 11 Oct 2007 13:32:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ig1tQ-0007bA-HE for channel-binding@ietf.org; Thu, 11 Oct 2007 13:32:16 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ig1tK-0004Jv-M7 for channel-binding@ietf.org; Thu, 11 Oct 2007 13:32:16 -0400
Received: from centralmail1brm.Central.Sun.COM ([129.147.62.1]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9BHVs8W015793 for <channel-binding@ietf.org>; Thu, 11 Oct 2007 17:31:54 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by centralmail1brm.Central.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL, v2.2) with ESMTP id l9BHVsEL014666 for <channel-binding@ietf.org>; Thu, 11 Oct 2007 11:31:54 -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 l9BHVsn9027087; Thu, 11 Oct 2007 12:31:54 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id l9BHVrh4027086; Thu, 11 Oct 2007 12:31:53 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Thu, 11 Oct 2007 12:31:53 -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: <20071011173152.GR24532@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: <20071011171012.GP24532@Sun.COM> <Pine.LNX.4.33L.0710111317040.8820-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.0710111317040.8820-100000@minbar.fac.cs.cmu.edu>
User-Agent: Mutt/1.5.7i
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
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 Thu, Oct 11, 2007 at 01:28:07PM -0400, Jeffrey Hutzelman wrote:
> This sort of assumes that the "obvious" thing to do is prfix the name to
> the data, rather than treating them separately.  That sssumption seems
> flawed to me, and the source of much confusion.

Did you miss this part of my reply to Sam:

Nico> I propose the following addition to that requirement:  "Where the
Nico> authentication interfaces provide a slot for channel binding data but no
Nico> slot for channel binfing type, then the application MUST prefix the
Nico> US-ASCII name of the channel binding type ("prefix"), and a separator
Nico> character, ':', to the channel binding data an octet string."

?

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

v2.8.7 | Report a Bug | By Email