Re: [nfsv4] Last call for NSDB Protocol for Federated Filesystems (Oct 4 - Oct 22nd)

Nicolas Williams <Nicolas.Williams@oracle.com> Mon, 08 November 2010 17:41 UTC

Return-Path: <Nicolas.Williams@oracle.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B39613A6929 for <nfsv4@core3.amsl.com>; Mon, 8 Nov 2010 09:41:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.273
X-Spam-Level:
X-Spam-Status: No, score=-6.273 tagged_above=-999 required=5 tests=[AWL=0.325, 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 i2onhlUdnWV4 for <nfsv4@core3.amsl.com>; Mon, 8 Nov 2010 09:41:54 -0800 (PST)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id CD04C3A6853 for <nfsv4@ietf.org>; Mon, 8 Nov 2010 09:41:54 -0800 (PST)
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 oA8HgCne009232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Nov 2010 17:42:13 GMT
Received: from acsmt355.oracle.com (acsmt355.oracle.com [141.146.40.155]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id oA82kUTP028123; Mon, 8 Nov 2010 17:42:11 GMT
Received: from abhmt003.oracle.com by acsmt353.oracle.com with ESMTP id 757930971289238127; Mon, 08 Nov 2010 09:42:07 -0800
Received: from oracle.com (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 08 Nov 2010 09:42:07 -0800
Date: Mon, 08 Nov 2010 11:41:58 -0600
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: "Everhart, Craig" <Craig.Everhart@netapp.com>
Message-ID: <20101108174156.GH6536@oracle.com>
References: <E043D9D8EE3B5743B8B174A814FD584F0A6BFD9C@TK5EX14MBXC126.redmond.corp.microsoft.com> <alpine.LFD.2.00.1010221251120.4707@jlentini-linux.nane.netapp.com> <4CD1DFE4.1060004@oracle.com> <20101104193632.GX6536@oracle.com> <alpine.LFD.2.00.1011051500050.14303@jlentini-linux.nane.netapp.com> <20101105205132.GP6536@oracle.com> <AANLkTi=octHZF_Cf0kqbfoL78jOTCfmq_pYDoMW1B2Pr@mail.gmail.com> <20101108165833.GD6536@oracle.com> <E7372E66F45B51429E249BF556CEFFBC0F78E18C@RTPMVEXC1-PRD.hq.netapp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E7372E66F45B51429E249BF556CEFFBC0F78E18C@RTPMVEXC1-PRD.hq.netapp.com>
User-Agent: Mutt/1.5.20 (2010-03-02)
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] Last call for NSDB Protocol for Federated Filesystems (Oct 4 - Oct 22nd)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 17:41:55 -0000

On Mon, Nov 08, 2010 at 12:19:22PM -0500, Everhart, Craig wrote:
> IANA is more than capable of discerning semantic overlap between
> candidates for registration and the existing registrants.  Probably
> they're more than capable of discerning such overlap between multiple
> candidates.

I don't agree.  IANA is good at following simple, clear rules.  For
anything more elaborate you need to require Expert Review or stronger
review.

> Creating yet another registry feels like a big hammer, but perhaps it's
> the way to go.

IANA registries are cheap (to us, WG participants anyways).

I'd rather use LDAP schema for this than an LDAP attribute with
key/value pairs as values.  We might be able to get a sub-namespace of
LDAP attribute/class names (all those starting with "fedFs", say) to
have different rules than LDAP as a whole, if the WG feels that strongly
about preventing semantic overlap.

> I don't know why machines would have problems skipping whitespace.
> Postel's Law would suggest it.

What's that got to do with anything?

Nico
--