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

James Lentini <jlentini@netapp.com> Fri, 05 November 2010 19:15 UTC

Return-Path: <jlentini@netapp.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 6E05E3A6902 for <nfsv4@core3.amsl.com>; Fri, 5 Nov 2010 12:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 wtS9cXqVp4x9 for <nfsv4@core3.amsl.com>; Fri, 5 Nov 2010 12:15:20 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 916043A68C2 for <nfsv4@ietf.org>; Fri, 5 Nov 2010 12:15:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,304,1286175600"; d="scan'208";a="478124513"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 05 Nov 2010 12:15:18 -0700
Received: from jlentini-linux.hq.netapp.com (jlentini-linux.hq.netapp.com [10.97.16.21]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id oA5JFHO9021488; Fri, 5 Nov 2010 12:15:18 -0700 (PDT)
Date: Fri, 05 Nov 2010 15:15:16 -0400
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: Nicolas Williams <Nicolas.Williams@oracle.com>
In-Reply-To: <20101104193632.GX6536@oracle.com>
Message-ID: <alpine.LFD.2.00.1011051500050.14303@jlentini-linux.nane.netapp.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>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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: Fri, 05 Nov 2010 19:15:21 -0000

On Thu, 4 Nov 2010, Nicolas Williams wrote:

> 
> I think we should pre-define an attribute for back pointers, as that
> seems valuable even though it's unreliable.

There isn't interest in this across vendors.
 
> I think a free-form text annotation for sysadmins to make notes is 
> also a good idea.

This is part of the specification. See the fedfsDescr.
 
> I don't think a free-for-all attribute/value namespace is a good 
> idea, as then each vendor will add random things that will then 
> create interop problems (because of collisions, because others will 
> feel pressured to implement the same attributes with 
> undocumented/obscure/unstable semantics, ...).  OTOH, a 
> FedFS-specific attribute/value namespace subject to IANA 
> registration would be fine, and even desirable for the reasons that 
> you state.

Would the registration of vendor-specific attributes be allowed?

-james