draft-ietf-nfsv4-federated-fs-admin-07.txt   draft-ietf-nfsv4-federated-fs-admin-08.txt 
NFSv4 Working Group J. Lentini NFSv4 Working Group J. Lentini
Internet-Draft C. Everhart Internet-Draft C. Everhart
Intended status: Standards Track NetApp Intended status: Standards Track NetApp
Expires: April 13, 2011 D. Ellard Expires: May 23, 2011 D. Ellard
Raytheon BBN Technologies Raytheon BBN Technologies
R. Tewari R. Tewari
M. Naik M. Naik
IBM Almaden IBM Almaden
October 10, 2010 November 19, 2010
Administration Protocol for Federated Filesystems Administration Protocol for Federated Filesystems
draft-ietf-nfsv4-federated-fs-admin-07 draft-ietf-nfsv4-federated-fs-admin-08
Abstract Abstract
This document describes the administration protocol for a federated This document describes the administration protocol for a federated
file system that enables file access and namespace traversal across file system that enables file access and namespace traversal across
collections of independently administered fileservers. The protocol collections of independently administered fileservers. The protocol
specifies a set of interfaces by which fileservers with different specifies a set of interfaces by which fileservers with different
administrators can form a fileserver federation that provides a administrators can form a fileserver federation that provides a
namespace composed of the filesystems physically hosted on and namespace composed of the filesystems physically hosted on and
exported by the constituent fileservers. exported by the constituent fileservers.
skipping to change at page 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 13, 2011. This Internet-Draft will expire on May 23, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 3, line 9 skipping to change at page 3, line 9
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Error Values . . . . . . . . . . . . . . . . . . . . . . . . . 10 3. Error Values . . . . . . . . . . . . . . . . . . . . . . . . . 11
4. Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4. Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1. FedFsNsdbName Equality . . . . . . . . . . . . . . . . . . 15 4.1. FedFsNsdbName Equality . . . . . . . . . . . . . . . . . . 16
5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1. FEDFS_NULL . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1. FEDFS_NULL . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 16 5.1.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.2. Description . . . . . . . . . . . . . . . . . . . . . 16 5.1.2. Description . . . . . . . . . . . . . . . . . . . . . 17
5.1.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2. FEDFS_CREATE_JUNCTION . . . . . . . . . . . . . . . . . . 16 5.2. FEDFS_CREATE_JUNCTION . . . . . . . . . . . . . . . . . . 17
5.2.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 16 5.2.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 17
5.2.2. Description . . . . . . . . . . . . . . . . . . . . . 16 5.2.2. Description . . . . . . . . . . . . . . . . . . . . . 17
5.2.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 17 5.2.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3. FEDFS_DELETE_JUNCTION . . . . . . . . . . . . . . . . . . 18 5.3. FEDFS_DELETE_JUNCTION . . . . . . . . . . . . . . . . . . 19
5.3.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 18 5.3.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.2. Description . . . . . . . . . . . . . . . . . . . . . 18 5.3.2. Description . . . . . . . . . . . . . . . . . . . . . 19
5.3.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 19 5.3.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 20
5.4. FEDFS_LOOKUP_JUNCTION . . . . . . . . . . . . . . . . . . 20 5.4. FEDFS_LOOKUP_JUNCTION . . . . . . . . . . . . . . . . . . 21
5.4.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 20 5.4.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.2. Description . . . . . . . . . . . . . . . . . . . . . 20 5.4.2. Description . . . . . . . . . . . . . . . . . . . . . 21
5.4.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 22 5.4.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 23
5.5. FEDFS_CREATE_REPLICATION . . . . . . . . . . . . . . . . . 23 5.5. FEDFS_CREATE_REPLICATION . . . . . . . . . . . . . . . . . 24
5.5.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 23 5.5.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 24
5.5.2. Description . . . . . . . . . . . . . . . . . . . . . 23 5.5.2. Description . . . . . . . . . . . . . . . . . . . . . 24
5.5.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 24 5.5.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 25
5.6. FEDFS_DELETE_REPLICATION . . . . . . . . . . . . . . . . . 25 5.6. FEDFS_DELETE_REPLICATION . . . . . . . . . . . . . . . . . 26
5.6.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 25 5.6.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 26
5.6.2. Description . . . . . . . . . . . . . . . . . . . . . 25 5.6.2. Description . . . . . . . . . . . . . . . . . . . . . 26
5.6.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 25 5.6.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 26
5.7. FEDFS_LOOKUP_REPLICATION . . . . . . . . . . . . . . . . . 26 5.7. FEDFS_LOOKUP_REPLICATION . . . . . . . . . . . . . . . . . 27
5.7.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 26 5.7.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 27
5.7.2. Description . . . . . . . . . . . . . . . . . . . . . 26 5.7.2. Description . . . . . . . . . . . . . . . . . . . . . 27
5.7.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 27 5.7.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 28
5.8. FEDFS_SET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 27 5.8. FEDFS_SET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 28
5.8.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 27 5.8.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 28
5.8.2. Description . . . . . . . . . . . . . . . . . . . . . 27 5.8.2. Description . . . . . . . . . . . . . . . . . . . . . 28
5.8.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 28 5.8.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 29
5.9. FEDFS_GET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 28 5.9. FEDFS_GET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 29
5.9.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 28 5.9.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 29
5.9.2. Description . . . . . . . . . . . . . . . . . . . . . 29 5.9.2. Description . . . . . . . . . . . . . . . . . . . . . 30
5.9.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 29 5.9.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 30
5.10. FEDFS_GET_LIMITED_NSDB_PARAMS . . . . . . . . . . . . . . 29 5.10. FEDFS_GET_LIMITED_NSDB_PARAMS . . . . . . . . . . . . . . 30
5.10.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 29 5.10.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 30
5.10.2. Description . . . . . . . . . . . . . . . . . . . . . 30 5.10.2. Description . . . . . . . . . . . . . . . . . . . . . 31
5.10.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 30 5.10.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 31
6. Security Considerations . . . . . . . . . . . . . . . . . . . 31 6. Security Considerations . . . . . . . . . . . . . . . . . . . 32
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
8. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 8. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.1. Normative References . . . . . . . . . . . . . . . . . . . 33 9.1. Normative References . . . . . . . . . . . . . . . . . . . 34
9.2. Informative References . . . . . . . . . . . . . . . . . . 34 9.2. Informative References . . . . . . . . . . . . . . . . . . 35
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 35 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 35 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
A federated filesystem enables file access and namespace traversal in A federated filesystem enables file access and namespace traversal in
a uniform, secure and consistent manner across multiple independent a uniform, secure and consistent manner across multiple independent
fileservers within an enterprise (and possibly across multiple fileservers within an enterprise (and possibly across multiple
enterprises) with reasonably good performance. enterprises) with reasonably good performance.
Traditionally, building a namespace that spans multiple fileservers Traditionally, building a namespace that spans multiple fileservers
has been difficult for two reasons. First, the fileservers that has been difficult for two reasons. First, the fileservers that
skipping to change at page 6, line 24 skipping to change at page 6, line 24
The effect of the script is to remove leading white space from each The effect of the script is to remove leading white space from each
line, plus a sentinel sequence of "///". line, plus a sentinel sequence of "///".
The protocol definition in XDR notation is shown below. We begin by The protocol definition in XDR notation is shown below. We begin by
defining basic constants and structures used by the protocol. We defining basic constants and structures used by the protocol. We
then present the procedures defined by the protocol. then present the procedures defined by the protocol.
<CODE BEGINS> <CODE BEGINS>
/// /*
/// * Copyright (c) 2010 IETF Trust and the persons identified
/// * as authors of the code. All rights reserved.
/// *
/// * The authors of the code are the authors of
/// * [draft-ietf-nfsv4-federated-fs-admin-xx.txt]: J. Lentini,
/// * C. Everhart, D. Ellard, R. Tewari, and M. Naik.
/// *
/// * Redistribution and use in source and binary forms, with
/// * or without modification, are permitted provided that the
/// * following conditions are met:
/// *
/// * - Redistributions of source code must retain the above
/// * copyright notice, this list of conditions and the
/// * following disclaimer.
/// *
/// * - Redistributions in binary form must reproduce the above
/// * copyright notice, this list of conditions and the
/// * following disclaimer in the documentation and/or other
/// * materials provided with the distribution.
/// *
/// * - Neither the name of Internet Society, IETF or IETF
/// * Trust, nor the names of specific contributors, may be
/// * used to endorse or promote products derived from this
/// * software without specific prior written permission.
/// *
/// * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
/// * AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
/// * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
/// * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
/// * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
/// * EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
/// * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
/// * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
/// * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
/// * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
/// * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
/// * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
/// * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
/// * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
/// * ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
/// */
///
/// enum FedFsStatus { /// enum FedFsStatus {
/// FEDFS_OK = 0, /// FEDFS_OK = 0,
/// FEDFS_ERR_ACCESS = 1, /// FEDFS_ERR_ACCESS = 1,
/// FEDFS_ERR_BADCHAR = 2, /// FEDFS_ERR_BADCHAR = 2,
/// FEDFS_ERR_BADNAME = 3, /// FEDFS_ERR_BADNAME = 3,
/// FEDFS_ERR_NAMETOOLONG = 4, /// FEDFS_ERR_NAMETOOLONG = 4,
/// FEDFS_ERR_LOOP = 5, /// FEDFS_ERR_LOOP = 5,
/// FEDFS_ERR_BADXDR = 6, /// FEDFS_ERR_BADXDR = 6,
/// FEDFS_ERR_EXIST = 7, /// FEDFS_ERR_EXIST = 7,
/// FEDFS_ERR_INVAL = 8, /// FEDFS_ERR_INVAL = 8,
skipping to change at page 7, line 16 skipping to change at page 8, line 12
/// FEDFS_ERR_NSDB_RESPONSE = 26, /// FEDFS_ERR_NSDB_RESPONSE = 26,
/// FEDFS_ERR_NSDB_FAULT = 27, /// FEDFS_ERR_NSDB_FAULT = 27,
/// FEDFS_ERR_NSDB_PARAMS = 28, /// FEDFS_ERR_NSDB_PARAMS = 28,
/// FEDFS_ERR_NSDB_LDAP_REFERRAL = 29, /// FEDFS_ERR_NSDB_LDAP_REFERRAL = 29,
/// FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL = 30, /// FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL = 30,
/// FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED = 31, /// FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED = 31,
/// FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL = 32, /// FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL = 32,
/// FEDFS_ERR_PATH_TYPE_UNSUPP = 33, /// FEDFS_ERR_PATH_TYPE_UNSUPP = 33,
/// FEDFS_ERR_DELAY = 34, /// FEDFS_ERR_DELAY = 34,
/// FEDFS_ERR_NO_CACHE = 35, /// FEDFS_ERR_NO_CACHE = 35,
/// FEDFS_ERR_UNKOWN_CACHE = 36, /// FEDFS_ERR_UNKNOWN_CACHE = 36,
/// FEDFS_ERR_NO_CACHE_UPDATE = 37 /// FEDFS_ERR_NO_CACHE_UPDATE = 37
/// }; /// };
/// ///
/// typedef opaque utf8string<>; /// typedef opaque utf8string<>;
/// typedef utf8string utf8str_cs; /// typedef utf8string utf8str_cs;
/// typedef utf8string utf8str_cis; /// typedef utf8string utf8str_cis;
/// ///
/// typedef opaque FedFsUuid[16]; /// typedef opaque FedFsUuid[16];
/// ///
/// struct FedFsNsdbName { /// struct FedFsNsdbName {
skipping to change at page 13, line 18 skipping to change at page 14, line 18
FEDFS_ERR_NOTSUPP: The fileserver does not support the specified FEDFS_ERR_NOTSUPP: The fileserver does not support the specified
procedure. procedure.
FEDFS_ERR_DELAY: The fileserver initiated the request, but was not FEDFS_ERR_DELAY: The fileserver initiated the request, but was not
able to complete it in a timely fashion. The client should wait able to complete it in a timely fashion. The client should wait
and then try the request with a new RPC transaction ID. and then try the request with a new RPC transaction ID.
FEDFS_ERR_NO_CACHE: The fileserver does not implement an FSN-to-FSL FEDFS_ERR_NO_CACHE: The fileserver does not implement an FSN-to-FSL
cache. cache.
FEDFS_ERR_UNKOWN_CACHE: The software receiving the ONC RPC request FEDFS_ERR_UNKNOWN_CACHE: The software receiving the ONC RPC request
is unaware if the fileserver implements an FSN-to-FSL cache or is unaware if the fileserver implements an FSN-to-FSL cache or
unable to communicate with the FSN-to-FSL cache if it exists. unable to communicate with the FSN-to-FSL cache if it exists.
FEDFS_ERR_NO_CACHE_UPDATE: The fileserver was unable to update its FEDFS_ERR_NO_CACHE_UPDATE: The fileserver was unable to update its
FSN-to-FSL cache. FSN-to-FSL cache.
4. Data Types 4. Data Types
The basic data types defined above MUST be formatted as follows: The basic data types defined above MUST be formatted as follows:
skipping to change at page 14, line 16 skipping to change at page 15, line 16
FedFsPathComponent: A case sensitive UTF-8 string containing a FedFsPathComponent: A case sensitive UTF-8 string containing a
filesystem path component. It SHOULD be prepared using the filesystem path component. It SHOULD be prepared using the
component4 rules defined in Chapter 12 "Internationalization" of component4 rules defined in Chapter 12 "Internationalization" of
[3530bis]. [3530bis].
FedFsPathName: A variable length array of FedFsPathComponent values FedFsPathName: A variable length array of FedFsPathComponent values
representing a filesystem path. The path's first component is representing a filesystem path. The path's first component is
stored at the first position of the array, the second component is stored at the first position of the array, the second component is
stored at the second position of the array, and so on. stored at the second position of the array, and so on.
The path "/" MUST be encoded as an array with zero components.
A FedFsPathName MUST NOT contain any zero-length components.
FedFsPath: A pathname container. The format and semantics of the FedFsPath: A pathname container. The format and semantics of the
pathname are defined by the FedFsPathType value. type specific pathname are defined by the FedFsPathType value. type specific
description of a pathname. description of a pathname.
A FEDFS_PATH_SYS is an implementation dependent administrative A FEDFS_PATH_SYS is an implementation dependent administrative
pathname. For example, it could be a local file system path. pathname. For example, it could be a local file system path.
A FEDFS_PATH_NFS is a pathname in the NFSv4 server's single-server A FEDFS_PATH_NFS is a pathname in the NFSv4 server's single-server
namespace. namespace.
skipping to change at page 21, line 32 skipping to change at page 22, line 32
in the FedFsLookupResOk structure. in the FedFsLookupResOk structure.
If the junction exists and the resolve parameter is set to If the junction exists and the resolve parameter is set to
FEDFS_RESOLVE_CACHE, the fileserver MUST attempt to resolve the FSN FEDFS_RESOLVE_CACHE, the fileserver MUST attempt to resolve the FSN
using its FSL cache, if one exists. The fileserver MUST NOT resolve using its FSL cache, if one exists. The fileserver MUST NOT resolve
the FSN by contacting the appropriate NSDB. If the fileserver's the FSN by contacting the appropriate NSDB. If the fileserver's
cache does not have a mapping for the FSN in question, the result of cache does not have a mapping for the FSN in question, the result of
the operation MUST be FEDFS_OK with 0 (zero) elements in the the operation MUST be FEDFS_OK with 0 (zero) elements in the
FedFsLookupResOk structure's fsl array. The operation MAY fail with FedFsLookupResOk structure's fsl array. The operation MAY fail with
status FEDFS_ERR_NO_CACHE if the fileserver does not contain an FSN- status FEDFS_ERR_NO_CACHE if the fileserver does not contain an FSN-
to-FSL cache or with status FEDFS_ERR_UNKOWN_CACHE if the state of to-FSL cache or with status FEDFS_ERR_UNKNOWN_CACHE if the state of
the cache is unknown. the cache is unknown.
If the junction exists and the resolve parameter is set to If the junction exists and the resolve parameter is set to
FEDFS_RESOLVE_NSDB, the fileserver MUST attempt to resolve the FSN by FEDFS_RESOLVE_NSDB, the fileserver MUST attempt to resolve the FSN by
contacting the appropriate NSDB. The FSN MUST NOT be resolved using contacting the appropriate NSDB. The FSN MUST NOT be resolved using
cached information. The resolution MAY fail with cached information. The resolution MAY fail with
FEDFS_ERR_NSDB_ROUTE, FEDFS_ERR_NSDB_DOWN, FEDFS_ERR_NSDB_CONN, FEDFS_ERR_NSDB_ROUTE, FEDFS_ERR_NSDB_DOWN, FEDFS_ERR_NSDB_CONN,
FEDFS_ERR_NSDB_AUTH, FEDFS_ERR_NSDB_LDAP, FEDFS_ERR_NSDB_LDAP_VAL, FEDFS_ERR_NSDB_AUTH, FEDFS_ERR_NSDB_LDAP, FEDFS_ERR_NSDB_LDAP_VAL,
FEDFS_ERR_NSDB_NOFSN, FEDFS_ERR_NSDB_NOFSL, FEDFS_ERR_NSDB_NONCE, FEDFS_ERR_NSDB_NOFSN, FEDFS_ERR_NSDB_NOFSL, FEDFS_ERR_NSDB_NONCE,
FEDFS_ERR_NSDB_RESPONSE, FEDFS_ERR_NSDB_FAULT, FEDFS_ERR_NSDB_RESPONSE, FEDFS_ERR_NSDB_FAULT,
skipping to change at page 23, line 30 skipping to change at page 24, line 30
FEDFS_ERR_NSDB_FAULT FEDFS_ERR_NSDB_FAULT
FEDFS_ERR_NSDB_PARAMS FEDFS_ERR_NSDB_PARAMS
FEDFS_ERR_NSDB_LDAP_REFERRAL FEDFS_ERR_NSDB_LDAP_REFERRAL
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL
FEDFS_ERR_PATH_TYPE_UNSUPP FEDFS_ERR_PATH_TYPE_UNSUPP
FEDFS_ERR_NOTSUPP FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY FEDFS_ERR_DELAY
FEDFS_ERR_NO_CACHE FEDFS_ERR_NO_CACHE
FEDFS_ERR_UNKOWN_CACHE FEDFS_ERR_UNKNOWN_CACHE
FEDFS_ERR_NO_CACHE_UPDATE FEDFS_ERR_NO_CACHE_UPDATE
5.5. FEDFS_CREATE_REPLICATION 5.5. FEDFS_CREATE_REPLICATION
5.5.1. Synopsis 5.5.1. Synopsis
Set an FSN representing the replication information for the fileset Set an FSN representing the replication information for the fileset
containing the pathname. containing the pathname.
5.5.2. Description 5.5.2. Description
skipping to change at page 27, line 40 skipping to change at page 28, line 40
FEDFS_ERR_NSDB_FAULT FEDFS_ERR_NSDB_FAULT
FEDFS_ERR_NSDB_PARAMS FEDFS_ERR_NSDB_PARAMS
FEDFS_ERR_NSDB_LDAP_REFERRAL FEDFS_ERR_NSDB_LDAP_REFERRAL
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL
FEDFS_ERR_PATH_TYPE_UNSUPP FEDFS_ERR_PATH_TYPE_UNSUPP
FEDFS_ERR_NOTSUPP FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY FEDFS_ERR_DELAY
FEDFS_ERR_NO_CACHE FEDFS_ERR_NO_CACHE
FEDFS_ERR_UNKOWN_CACHE FEDFS_ERR_UNKNOWN_CACHE
5.8. FEDFS_SET_NSDB_PARAMS 5.8. FEDFS_SET_NSDB_PARAMS
5.8.1. Synopsis 5.8.1. Synopsis
Set the connection parameters for the specified NSDB. Set the connection parameters for the specified NSDB.
5.8.2. Description 5.8.2. Description
This operations allows the administrator to set the connection This operations allows the administrator to set the connection
skipping to change at page 33, line 44 skipping to change at page 34, line 44
Singleton Server: A server collection containing only one server; a Singleton Server: A server collection containing only one server; a
stand-alone fileserver. stand-alone fileserver.
9. References 9. References
9.1. Normative References 9.1. Normative References
[3530bis] Haynes, T. and D. Noveck, "NFS Version 4 Protocol", [3530bis] Haynes, T. and D. Noveck, "NFS Version 4 Protocol",
draft-ietf-nfsv4-rfc3530bis (Work In Progress), 2010. draft-ietf-nfsv4-rfc3530bis (Work In Progress), 2010.
[RFC1094] Nowicki, B., "NFS: Network File System Protocol
specification", RFC 1094, March 1989.
[RFC1813] Callaghan, B., Pawlowski, B., and P. Staubach, "NFS
Version 3 Protocol Specification", RFC 1813, June 1995.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2203] Eisler, M., Chiu, A., and L. Ling, "RPCSEC_GSS Protocol [RFC2203] Eisler, M., Chiu, A., and L. Ling, "RPCSEC_GSS Protocol
Specification", RFC 2203, September 1997. Specification", RFC 2203, September 1997.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122,
July 2005. July 2005.
skipping to change at page 34, line 50 skipping to change at page 35, line 44
[MS-CIFS] Microsoft Corporation, "Common Internet File System (CIFS) [MS-CIFS] Microsoft Corporation, "Common Internet File System (CIFS)
Protocol Specification", MS-CIFS 2.0, November 2009. Protocol Specification", MS-CIFS 2.0, November 2009.
[MS-SMB] Microsoft Corporation, "Server Message Block (SMB) [MS-SMB] Microsoft Corporation, "Server Message Block (SMB)
Protocol Specification", MS-SMB 17.0, November 2009. Protocol Specification", MS-SMB 17.0, November 2009.
[MS-SMB2] Microsoft Corporation, "Server Message Block (SMB) Version [MS-SMB2] Microsoft Corporation, "Server Message Block (SMB) Version
2 Protocol Specification", MS-SMB2 19.0, November 2009. 2 Protocol Specification", MS-SMB2 19.0, November 2009.
[RFC1094] Nowicki, B., "NFS: Network File System Protocol
specification", RFC 1094, March 1989.
[RFC1813] Callaghan, B., Pawlowski, B., and P. Staubach, "NFS
Version 3 Protocol Specification", RFC 1813, June 1995.
[RFC5661] Shepler, S., Eisler, M., and D. Noveck, "Network File [RFC5661] Shepler, S., Eisler, M., and D. Noveck, "Network File
System (NFS) Version 4 Minor Version 1 Protocol", System (NFS) Version 4 Minor Version 1 Protocol",
RFC 5661, January 2010. RFC 5661, January 2010.
[RFC5662] Shepler, S., Eisler, M., and D. Noveck, "Network File [RFC5662] Shepler, S., Eisler, M., and D. Noveck, "Network File
System (NFS) Version 4 Minor Version 1 External Data System (NFS) Version 4 Minor Version 1 External Data
Representation Standard (XDR) Description", RFC 5662, Representation Standard (XDR) Description", RFC 5662,
January 2010. January 2010.
[RFC5716] Lentini, J., Everhart, C., Ellard, D., Tewari, R., and M. [RFC5716] Lentini, J., Everhart, C., Ellard, D., Tewari, R., and M.
skipping to change at page 35, line 25 skipping to change at page 36, line 26
We would like to thank Robert Thurlow of Sun Microsystems for helping We would like to thank Robert Thurlow of Sun Microsystems for helping
to author this document, including drafting the replication procedure to author this document, including drafting the replication procedure
text. text.
We would also like to thank Paul Lemahieu of EMC and Mario Wurzl of We would also like to thank Paul Lemahieu of EMC and Mario Wurzl of
EMC for helping to author this document. EMC for helping to author this document.
We would also like to thank Trond Myklebust for suggesting We would also like to thank Trond Myklebust for suggesting
improvements to the FSL pathname format, Chuck Lever for suggesting improvements to the FSL pathname format, Chuck Lever for suggesting
improvements to the XDR type definitions and error codes, and Nicolas improvements to the XDR type definitions and error codes, David
Williams for his suggestions. Noveck for his suggestions on internationalization and path encoding
rules, and Nicolas Williams for his suggestions.
The extract.sh shell script and formatting conventions were first The extract.sh shell script and formatting conventions were first
described by the authors of the NFSv4.1 XDR specification [RFC5662]. described by the authors of the NFSv4.1 XDR specification [RFC5662].
Authors' Addresses Authors' Addresses
James Lentini James Lentini
NetApp NetApp
1601 Trapelo Rd, Suite 16 1601 Trapelo Rd, Suite 16
Waltham, MA 02451 Waltham, MA 02451
 End of changes. 16 change blocks. 
69 lines changed or deleted 117 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/