IETF Logo Mail Archive

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

Nicolas Williams <Nicolas.Williams@oracle.com> Mon, 08 November 2010 19:47 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 C52633A688D for <nfsv4@core3.amsl.com>; Mon, 8 Nov 2010 11:47:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.362
X-Spam-Level:
X-Spam-Status: No, score=-6.362 tagged_above=-999 required=5 tests=[AWL=0.236, 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 9Oy+05H+1zKd for <nfsv4@core3.amsl.com>; Mon, 8 Nov 2010 11:47:20 -0800 (PST)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 0E0693A6800 for <nfsv4@ietf.org>; Mon, 8 Nov 2010 11:47:20 -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 oA8Jld8r005687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Nov 2010 19:47:41 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 oA8BSkuD015012; Mon, 8 Nov 2010 19:47:38 GMT
Received: from abhmt003.oracle.com by acsmt354.oracle.com with ESMTP id 758375591289245657; Mon, 08 Nov 2010 11:47:37 -0800
Received: from oracle.com (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 08 Nov 2010 11:47:37 -0800
Date: Mon, 08 Nov 2010 13:47:32 -0600
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: James Lentini <jlentini@netapp.com>
Message-ID: <20101108194732.GM6536@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> <alpine.LFD.2.00.1011080950260.14303@jlentini-linux.nane.netapp.com> <20101108164205.GB6536@oracle.com> <alpine.LFD.2.00.1011081407490.21456@jlentini-linux.nane.netapp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.00.1011081407490.21456@jlentini-linux.nane.netapp.com>
User-Agent: Mutt/1.5.20 (2010-03-02)
Cc: Robert Thurlow <Robert.Thurlow@oracle.com>, "nfsv4@ietf.org" <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 19:47:20 -0000

On Mon, Nov 08, 2010 at 02:12:28PM -0500, James Lentini wrote:
> On Mon, 8 Nov 2010, Nicolas Williams wrote:
> > > Are you confusing the subject of this thread, the fedfsAnnotation 
> > > attribute, with the fedfsDescr attribute? I don't remember any posts 
> > > from you or Rob on using the fedfsDescr attribute for a purpose 
> > > incompatible with free-form text.
> > 
> > fedfsAnnotation is a free-form key/value space.  I think that's a bit
> > silly, this being LDAP and all...  But also, without a registry, what's
> > to prevent collisions?
> 
> Our signals are getting crossed.
> 
> I'm pointing out that the "free-form text annotation for sysadmins to 
> make notes" that you suggested is already part of the specification. 
> It is called a fedfsDesc, not to be confused with a fedfsAnnotation.

I understood what you said.  I may have been a bit sloppy in referring
to fedfsAnnotation as free-form, but, then again, it practically is that
-- fedfsAnnotation is only slightly less free-form than fedfsDesc.

v2.23.0 | Report a Bug | By Email