Protocol Action: 'NSDB Protocol for Federated Filesystems' to Proposed Standard (draft-ietf-nfsv4-federated-fs-protocol-15.txt)

The IESG <iesg-secretary@ietf.org> Fri, 21 December 2012 17:22 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660F721F8AE3; Fri, 21 Dec 2012 09:22:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level:
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T-fhyN5dsaOE; Fri, 21 Dec 2012 09:22:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F9721F8AF8; Fri, 21 Dec 2012 09:22:25 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'NSDB Protocol for Federated Filesystems' to Proposed Standard (draft-ietf-nfsv4-federated-fs-protocol-15.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20121221172225.15428.976.idtracker@ietfa.amsl.com>
Date: Fri, 21 Dec 2012 09:22:25 -0800
Cc: nfsv4 chair <nfsv4-chairs@tools.ietf.org>, nfsv4 mailing list <nfsv4@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 17:22:26 -0000

The IESG has approved the following document:
- 'NSDB Protocol for Federated Filesystems'
  (draft-ietf-nfsv4-federated-fs-protocol-15.txt) as Proposed Standard

This document is the product of the Network File System Version 4 Working
Group.

The IESG contact persons are Martin Stiemerling and Wesley Eddy.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-nfsv4-federated-fs-protocol/




Technical Summary
 
    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. 

Working Group Summary

    The FedFS protocol as to be used with NFSv4 file servers is an
    important component to providing enterprise usable federated
    NFSv4 file systems.  Combined with the Administration Protocol
    for Federated Filesystems, and NFSv4 protocols a complete
    solution is possible and provides substantial utility. 
   
Document Quality

    Not only is the NSDB Protocol for Federated Filesystems document
    complete, readable and useful as a guide to implementation and
    interoperability, this has been proven by prototype
    implementations that have been built by those authoring the
    document.  This is an important culture of the NFSv4 working
    group and has become the norm of behavior for the work product
    generated by the working group. 

Personnel

   Spencer Shepler (sshepler@microsoft.com) is the document shepherd. 
   Martin Stiemerling (martin.stiemerling@neclab.eu) is the responsible Area Director. 

RFC Editor Note

 1. Please remove Daniel Ellard from the list of author
 2. Add this text to Appendix A.  Acknowledgments:
    'Daniel Ellard contributed significant parts to this draft.'