Re: [kitten] [nfsv4] draft-ietf-nfsv4-rpcsec-gssv3: request for review

Nico Williams <nico@cryptonector.com> Mon, 04 August 2014 20:40 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9FE51A0308; Mon, 4 Aug 2014 13:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4D3AuoqAAP-9; Mon, 4 Aug 2014 13:40:18 -0700 (PDT)
Received: from homiemail-a26.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 09E2B1A02F4; Mon, 4 Aug 2014 13:40:18 -0700 (PDT)
Received: from homiemail-a26.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a26.g.dreamhost.com (Postfix) with ESMTP id DF6A1B805B; Mon, 4 Aug 2014 13:40:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=b5sST64KSHXWOC KWc04K5MjFnYA=; b=e/gRjiZRnJ5zlob7ekxcn6wXUEaDZwcWbdjV0WK+vI0+f7 lyPNQjsKJsDlP2DKOIKUkc8xJF029p/mdqXWV27NUXOHWoh2a9K46+MInHd5HFYM V3KOrxTRF2mku7piBO0mR6pv/eqhxEW2Kobr1Z08iabedz5wNs8tlVS1IXMqU=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a26.g.dreamhost.com (Postfix) with ESMTPA id 763E9B805C; Mon, 4 Aug 2014 13:40:17 -0700 (PDT)
Date: Mon, 04 Aug 2014 15:40:17 -0500
From: Nico Williams <nico@cryptonector.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Message-ID: <20140804204007.GE3579@localhost>
References: <DC941FEB-725A-49E1-8C38-FF765454827C@netapp.com> <alpine.GSO.1.10.1407301239260.21571@multics.mit.edu> <20140801055401.GA7409@localhost> <8FD0C272-6FD3-44FE-BD3D-BAB220E0FF13@netapp.com> <20140801221535.GA3579@localhost> <DDC64AA5-C2B4-404A-A864-212A3A3AECF1@netapp.com> <20140804180946.GR3579@localhost> <alpine.GSO.1.10.1408041555210.21571@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.GSO.1.10.1408041555210.21571@multics.mit.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/RYPDwIU-2-jMWWq1uobtwPYd300
Cc: "kitten@ietf.org" <kitten@ietf.org>, "Adamson, Andy" <William.Adamson@netapp.com>, NFSv4 <nfsv4@ietf.org>
Subject: Re: [kitten] [nfsv4] draft-ietf-nfsv4-rpcsec-gssv3: request for review
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 04 Aug 2014 20:40:19 -0000

On Mon, Aug 04, 2014 at 04:01:15PM -0400, Benjamin Kaduk wrote:
> On Mon, 4 Aug 2014, Nico Williams wrote:
> >"Compound" is used as an adjective in all cases.  I don't see how
> >"compound authentication" (or "compound context handle", ...) is
> >confusable with "compound RPC".  But this isn't important enough to me;
> >aligning the terminology with AFS' rxgk is.  Ben, what does rxgk call
> >this?
> 
> If I remember correclty from the talk from Toronto, Andy was not
> quite so keen to align with rxgk, but that may have been based on
> incomplete data.

Well, it'd be nice to have that, but it isn't required.  rxgk's use of
"combine" is very specific to what it does, which is very different from
what RPCSEC_GSSv3 does in specifics though effectively the same, so
perhaps alignment with rxgk as to terminology would not be usefule
anyways.