IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Mon, 04 August 2014 18:09 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 1B4551A00DC; Mon, 4 Aug 2014 11:09:54 -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 XgkVE6qB-5D3; Mon, 4 Aug 2014 11:09:53 -0700 (PDT)
Received: from homiemail-a64.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id BFCF01A00AE; Mon, 4 Aug 2014 11:09:48 -0700 (PDT)
Received: from homiemail-a64.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTP id 917C0438080; Mon, 4 Aug 2014 11:09:48 -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:content-transfer-encoding; s= cryptonector.com; bh=k8RGyJU1MTrH5kx1JMJexeVI18c=; b=k8mrlrxlrab 1pT52I2yKFGPNV7P5uk6HHxxZyDzAUaaacdY4n/lGGCy6nsPV88qW5VZDI5ibePE CZEnUWgVCPZ9xL3FaZe5XrtbwX6ufYmwLyrX+Jp6KBLLw10s866BRUxb+RIgP2r9 I6U+qSRRCPzTfmCdrYnR9KOHQwCARyQw=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTPA id 2F5AE43807F; Mon, 4 Aug 2014 11:09:48 -0700 (PDT)
Date: Mon, 04 Aug 2014 13:09:47 -0500
From: Nico Williams <nico@cryptonector.com>
To: "Adamson, Andy" <William.Adamson@netapp.com>
Message-ID: <20140804180946.GR3579@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <DDC64AA5-C2B4-404A-A864-212A3A3AECF1@netapp.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/qkg3xk1BemusiKdDwy_UQijWTvw
Cc: "kitten@ietf.org" <kitten@ietf.org>, 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 18:09:54 -0000

On Mon, Aug 04, 2014 at 04:55:57PM +0000, Adamson, Andy wrote:
> On Aug 1, 2014, at 6:15 PM, Nico Williams <nico@cryptonector.com> wrote:
> > (Was "multi-principal" my name for this?  No, I called them compound
> > authentication.  I prefer "compound”.)
> 
> Hi NIco
> 
> I changed the name from ‘compound’ to multi-principal’ in response
> the review comments at IETF 89 where many NFSv4 WG members expressed
> that ‘compound’ had too many meanings (especially in NFSv4.x) and
> led to confusion.

"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?

v2.29.0 | Report a Bug | By Email | System Status