IETF Logo Mail Archive

Re: Last Call: draft-ietf-kitten-gssapi-naming-exts (GSS-API Naming Extensions) to Proposed Standard

Nicolas Williams <Nicolas.Williams@oracle.com> Thu, 22 July 2010 23:15 UTC

Return-Path: <Nicolas.Williams@oracle.com>
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 07F213A6A92; Thu, 22 Jul 2010 16:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.526
X-Spam-Level:
X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 DPhUt30BNKnL; Thu, 22 Jul 2010 16:15:25 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 79A953A6A8F; Thu, 22 Jul 2010 16:15:25 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o6MNFa5N032637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Jul 2010 23:15:38 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o6MFJf5C017680; Thu, 22 Jul 2010 23:15:35 GMT
Received: from abhmt021.oracle.com by acsmt355.oracle.com with ESMTP id 429161961279840459; Thu, 22 Jul 2010 16:14:19 -0700
Received: from oracle.com (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 22 Jul 2010 16:14:19 -0700
Date: Thu, 22 Jul 2010 18:14:47 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Last Call: draft-ietf-kitten-gssapi-naming-exts (GSS-API Naming Extensions) to Proposed Standard
Message-ID: <20100722231446.GN23748@oracle.com>
References: <20100709151413.E7F943A6AB7@core3.amsl.com> <tsllj9gwg1n.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <tsllj9gwg1n.fsf@mit.edu>
User-Agent: Mutt/1.5.20 (2010-03-02)
X-Source-IP: acsmt354.oracle.com [141.146.40.154]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090203.4C48D118.00AA:SCFMA4539814,ss=1,fgs=0
Cc: kitten@ietf.org, ietf@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/mail-archive/web/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>
X-List-Received-Date: Thu, 22 Jul 2010 23:15:30 -0000

On Mon, Jul 12, 2010 at 05:23:16PM -0400, Sam Hartman wrote:
> Recently I've tried to use draft-ietf-kitten-gssapi-naming-exts in the
> design of a GSS-API mechanism.
> I think this is a good start but is not quite done yet.

I agree.  I'm not sure whether it's best to proceed to publication then
later publish another RFC, or if it'd be best to cancel the IETF LC and
improve this I-D.

> draft-hartman-gss-eap-naming-00 discusses a couple of problems with
> naming extensions:
> 
> * The format of attribute names proposed in this specification is
>   incompatible with several of the things you'd like to name, in my case
>   including SAML attributes.
> * The description of how to name SAML attributes currently in the
>   document is inconsistent with the SAML base specification
> * The approach of naming things like SAML attributes entirely with a
> * The approach of letting a mechanism create authenticated attributes
>   with an arbitrary URI  makes the application's life really hard

One or more of your bullet points is incomplete, Sam.

> In addition, there is no way to get the identity of the issuer of a name
> attribute.

This is a big deal, IMO.

> I've discussed these concerns with one of the authors, Nico Williams. I
> have also requested time to present my concerns at the kitten meeting at
> IETF 78.

We should definitely discuss this next week.

> I'm happy to help resolve these concerns up to and including becoming an
> author of the document and writing significant text.

I think that's a good idea, however I'll let my co-author comment on
this as well, given that he's the primary author now :)

Nico
--

v2.23.0 | Report a Bug | By Email