Re: [nfsv4] I-D Action:draft-ietf-nfsv4-federated-fs-protocol-10.txt

James Lentini <jlentini@netapp.com> Fri, 19 November 2010 16:05 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 E180B28C12B for <nfsv4@core3.amsl.com>; Fri, 19 Nov 2010 08:05:19 -0800 (PST)
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 POwTYtqyauth for <nfsv4@core3.amsl.com>; Fri, 19 Nov 2010 08:05:18 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 0BD4928C12C for <nfsv4@ietf.org>; Fri, 19 Nov 2010 08:05:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.59,223,1288594800"; d="scan'208";a="484536870"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 19 Nov 2010 08:05:55 -0800
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 oAJG5slw001152 for <nfsv4@ietf.org>; Fri, 19 Nov 2010 08:05:54 -0800 (PST)
Date: Fri, 19 Nov 2010 11:05:54 -0500
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: nfsv4@ietf.org
In-Reply-To: <20101119160001.19261.44004.idtracker@localhost>
Message-ID: <alpine.LFD.2.00.1011191104470.27239@jlentini-linux.nane.netapp.com>
References: <20101119160001.19261.44004.idtracker@localhost>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: Re: [nfsv4] I-D Action:draft-ietf-nfsv4-federated-fs-protocol-10.txt
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, 19 Nov 2010 16:05:20 -0000

On Fri, 19 Nov 2010, Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network File System Version 4 Working Group of the IETF.
> 
> 
> 	Title           : NSDB Protocol for Federated Filesystems
> 	Author(s)       : J. Lentini, et al.
> 	Filename        : draft-ietf-nfsv4-federated-fs-protocol-10.txt
> 	Pages           : 61
> 	Date            : 2010-11-19
> 
> This document describes a filesystem federation protocol that enables
> file access and namespace traversal across collections of
> independently administered fileservers.  The protocol specifies a set
> of interfaces by which fileservers with different administrators can
> form a fileserver federation that provides a namespace composed of
> the filesystems physically hosted on and exported by the constituent
> fileservers.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-federated-fs-protocol-10.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 

Hi folks,
 
This update incorporates the feedback from WG last call for the NSDB 
specification. In particular, it includes the following changes:

 1. Added the license as extractable text so that code
    extracted from the document automatically meets the
    "Status of this Memo" section's license requirements.
 
 2. Added an note highlighting use of the time-based UUID to
    the fedfsUuid description.

 3. Removed the option of using invalid UUIDs for debugging purposes 
    from the fedfsUuid description since such UUID strings are not 
    supported in the ONC RPC Admin protocol.

 4. Updated the fedfsAnnotation description with ABNF rules defining the
    attribute's format.

After the completion of WG last call, there was some discussion 
about whether fedfsAnnotation keys must be unique. We'll wait to see 
if there are more opinions on this topic before making any changes 
in that area.

-james