IETF Logo Mail Archive

Re: [Fwd: FW: last call comments: draft-ietf-kitten-gssapi-channel-bindings-04.txt]

Nicolas Williams <Nicolas.Williams@sun.com> Fri, 14 March 2008 08:00 UTC

Return-Path: <kitten-bounces@ietf.org>
X-Original-To: ietfarch-kitten-archive@core3.amsl.com
Delivered-To: ietfarch-kitten-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE00028C70C; Fri, 14 Mar 2008 01:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.742
X-Spam-Level:
X-Spam-Status: No, score=-101.742 tagged_above=-999 required=5 tests=[AWL=-1.304, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WywI6yZGtBrj; Fri, 14 Mar 2008 01:00:12 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EEDB28C33E; Fri, 14 Mar 2008 01:00:12 -0700 (PDT)
X-Original-To: kitten@core3.amsl.com
Delivered-To: kitten@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34E9F28C33E for <kitten@core3.amsl.com>; Fri, 14 Mar 2008 01:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18gqu-O4DjXI for <kitten@core3.amsl.com>; Fri, 14 Mar 2008 01:00:10 -0700 (PDT)
Received: from sca-ea-mail-4.sun.com (sca-ea-mail-4.Sun.COM [192.18.43.22]) by core3.amsl.com (Postfix) with ESMTP id 7C29B3A6806 for <kitten@ietf.org>; Fri, 14 Mar 2008 01:00:10 -0700 (PDT)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m2E7vrV0022262 for <kitten@ietf.org>; Fri, 14 Mar 2008 07:57:53 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id m2E7vqcB056059 for <kitten@ietf.org>; Fri, 14 Mar 2008 01:57:52 -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 m2E7vqfN013167; Fri, 14 Mar 2008 02:57:52 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m2E7vqfi013166; Fri, 14 Mar 2008 02:57:52 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Fri, 14 Mar 2008 02:57:52 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: "Shawn M. Emery" <Shawn.Emery@sun.com>
Subject: Re: [Fwd: FW: last call comments: draft-ietf-kitten-gssapi-channel-bindings-04.txt]
Message-ID: <20080314075752.GD986@Sun.COM>
Mail-Followup-To: "Shawn M. Emery" <Shawn.Emery@Sun.COM>, kitten@ietf.org
References: <47D9F601.8040905@sun.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <47D9F601.8040905@sun.com>
User-Agent: Mutt/1.5.7i
Cc: kitten@ietf.org
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: kitten-bounces@ietf.org
Errors-To: kitten-bounces@ietf.org

On Thu, Mar 13, 2008 at 09:50:25PM -0600, Shawn M. Emery wrote:
> 
> -----Original Message-----
> From: Larry Zhu
> Sent: Thursday, March 13, 2008 8:41 PM
> To: 'kitten@lists.ietf.org'
> Subject: last call comments: draft-ietf-kitten-gssapi-channel-bindings-04.txt
> 
> 1. With regarding the following statement:
> 
>  GSS-API mechanisms MAY use the [RFC1964] encoding of channel
>    bindings.
> 
> RPC1964 is updated by RFC4121, why does this document reference 1964
> instead of 4121?

I'd forgotten that RFC4121 updates this part of RFC1964.  I'll make this
change.

> And what does "MAY" imply, does it imply there are incompatibilities
> in the structure definitions? Please clarify.

It means that another mechanism, say, PKU2U or SCRAM, can use the text
in RFC4121, section 4.1.1.2, items (1) through (3), as an encoding of
the generic channel binding structure given in this I-D/

> 2. nits. On the definition of GSS-CHANNEL-BINDINGS, ":=" should be
> "::=", the last comma should be removed.

True, but in my defense, I did write "pseudo-ASN.1" :) :)

> 3. initiator-address-type and acceptor-address-type are
> underspecified, I cannot figure out what to do these at all.

"
   The values for the address fields are described in [RFC2744].
"

Nico
-- 
_______________________________________________
Kitten mailing list
Kitten@ietf.org
https://www.ietf.org/mailman/listinfo/kitten

v2.23.0 | Report a Bug | By Email