RFC 7532 on Namespace Database (NSDB) Protocol for Federated File Systems
rfc-editor@rfc-editor.org Thu, 26 March 2015 18:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 061D61B2ABA; Thu, 26 Mar 2015 11:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3VFTN6cUJPBS; Thu, 26 Mar 2015 11:36:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 0DCCF1B2A59; Thu, 26 Mar 2015 11:36:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5A186180470; Thu, 26 Mar 2015 11:34:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7532 on Namespace Database (NSDB) Protocol for Federated File Systems
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150326183443.5A186180470@rfc-editor.org>
Date: Thu, 26 Mar 2015 11:34:43 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/c_Fhz2BkXSeDAKwnUuUCsILDYv0>
Cc: drafts-update-ref@iana.org, nfsv4@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: Thu, 26 Mar 2015 18:36:23 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7532
Title: Namespace Database (NSDB) Protocol for
Federated File Systems
Author: J. Lentini, R. Tewari, C. Lever, Ed.
Status: Standards Track
Stream: IETF
Date: March 2015
Mailbox: jlentini@netapp.com,
tewarir@us.ibm.com,
chuck.lever@oracle.com
Pages: 65
Characters: 127373
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-nfsv4-federated-fs-protocol-15.txt
URL: https://www.rfc-editor.org/info/rfc7532
This document describes a file system 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 file systems physically hosted on and exported by the constituent
fileservers.
This document is a product of the Network File System Version 4 Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC