draft-ietf-nfsv4-federated-fs-admin-05.txt   draft-ietf-nfsv4-federated-fs-admin-06.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: January 11, 2011 D. Ellard Expires: April 2, 2011 D. Ellard
Raytheon BBN Technologies Raytheon BBN Technologies
R. Tewari R. Tewari
M. Naik M. Naik
IBM Almaden IBM Almaden
July 10, 2010 September 29, 2010
Administration Protocol for Federated Filesystems Administration Protocol for Federated Filesystems
draft-ietf-nfsv4-federated-fs-admin-05 draft-ietf-nfsv4-federated-fs-admin-06
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 January 11, 2011. This Internet-Draft will expire on April 2, 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 7 skipping to change at page 3, line 7
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Error Values . . . . . . . . . . . . . . . . . . . . . . . . . 9 3. Error Values . . . . . . . . . . . . . . . . . . . . . . . . . 10
4. Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4. Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. FedFsNsdbName Equality . . . . . . . . . . . . . . . . . . 12 4.1. FedFsNsdbName Equality . . . . . . . . . . . . . . . . . . 14
5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1. FEDFS_CREATE_JUNCTION . . . . . . . . . . . . . . . . . . 14 5.1. FEDFS_NULL . . . . . . . . . . . . . . . . . . . . . . . . 15
5.2. FEDFS_DELETE_JUNCTION . . . . . . . . . . . . . . . . . . 15 5.1.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 15
5.3. FEDFS_LOOKUP_JUNCTION . . . . . . . . . . . . . . . . . . 16 5.1.2. Description . . . . . . . . . . . . . . . . . . . . . 15
5.4. FEDFS_CREATE_REPLICATION . . . . . . . . . . . . . . . . . 18 5.1.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 16
5.5. FEDFS_DELETE_REPLICATION . . . . . . . . . . . . . . . . . 19 5.2. FEDFS_CREATE_JUNCTION . . . . . . . . . . . . . . . . . . 16
5.6. FEDFS_LOOKUP_REPLICATION . . . . . . . . . . . . . . . . . 20 5.2.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 16
5.7. FEDFS_SET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 20 5.2.2. Description . . . . . . . . . . . . . . . . . . . . . 16
5.8. FEDFS_GET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 21 5.2.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 17
5.9. FEDFS_GET_LIMITED_NSDB_PARAMS . . . . . . . . . . . . . . 21 5.3. FEDFS_DELETE_JUNCTION . . . . . . . . . . . . . . . . . . 18
6. Internationalization . . . . . . . . . . . . . . . . . . . . . 22 5.3.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 5.3.2. Description . . . . . . . . . . . . . . . . . . . . . 18
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 5.3.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 19
9. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.4. FEDFS_LOOKUP_JUNCTION . . . . . . . . . . . . . . . . . . 19
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.4.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 19
10.1. Normative References . . . . . . . . . . . . . . . . . . . 25 5.4.2. Description . . . . . . . . . . . . . . . . . . . . . 20
10.2. Informative References . . . . . . . . . . . . . . . . . . 26 5.4.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 22
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 26 5.5. FEDFS_CREATE_REPLICATION . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 5.5.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 23
5.5.2. Description . . . . . . . . . . . . . . . . . . . . . 23
5.5.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 24
5.6. FEDFS_DELETE_REPLICATION . . . . . . . . . . . . . . . . . 24
5.6.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 24
5.6.2. Description . . . . . . . . . . . . . . . . . . . . . 24
5.6.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 25
5.7. FEDFS_LOOKUP_REPLICATION . . . . . . . . . . . . . . . . . 25
5.7.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 25
5.7.2. Description . . . . . . . . . . . . . . . . . . . . . 25
5.7.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 26
5.8. FEDFS_SET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 27
5.8.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 27
5.8.2. Description . . . . . . . . . . . . . . . . . . . . . 27
5.8.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 28
5.9. FEDFS_GET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 28
5.9.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 28
5.9.2. Description . . . . . . . . . . . . . . . . . . . . . 28
5.9.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 28
5.10. FEDFS_GET_LIMITED_NSDB_PARAMS . . . . . . . . . . . . . . 29
5.10.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 29
5.10.2. Description . . . . . . . . . . . . . . . . . . . . . 29
5.10.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 30
6. Security Considerations . . . . . . . . . . . . . . . . . . . 30
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
8. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.1. Normative References . . . . . . . . . . . . . . . . . . . 33
9.2. Informative References . . . . . . . . . . . . . . . . . . 33
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34
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 5, line 25 skipping to change at page 6, line 25
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>
/// 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,
/// FEDFS_ERR_IO = 9, /// FEDFS_ERR_IO = 9,
/// FEDFS_ERR_NOSPC = 10, /// FEDFS_ERR_NOSPC = 10,
/// FEDFS_ERR_NOTDIR = 11, /// FEDFS_ERR_NOTJUNCT = 11,
/// FEDFS_ERR_NOTEMPTY = 12, /// FEDFS_ERR_NOTLOCAL = 12,
/// FEDFS_ERR_NOTJUNCT = 13, /// FEDFS_ERR_PERM = 13,
/// FEDFS_ERR_NOTLOCAL = 14, /// FEDFS_ERR_ROFS = 14,
/// FEDFS_ERR_PERM = 15, /// FEDFS_ERR_SVRFAULT = 15,
/// FEDFS_ERR_ROFS = 16, /// FEDFS_ERR_NOTSUPP = 16,
/// FEDFS_ERR_SVRFAULT = 17, /// FEDFS_ERR_NSDB_ROUTE = 17,
/// FEDFS_ERR_NSDB_ROUTE = 18, /// FEDFS_ERR_NSDB_DOWN = 18,
/// FEDFS_ERR_NSDB_DOWN = 19, /// FEDFS_ERR_NSDB_CONN = 19,
/// FEDFS_ERR_NSDB_CONN = 20, /// FEDFS_ERR_NSDB_AUTH = 20,
/// FEDFS_ERR_NSDB_AUTH = 21, /// FEDFS_ERR_NSDB_LDAP = 21,
/// FEDFS_ERR_NSDB_LDAP = 22, /// FEDFS_ERR_NSDB_LDAP_VAL = 22,
/// FEDFS_ERR_NSDB_LDAP_VAL = 23, /// FEDFS_ERR_NSDB_NOFSN = 23,
/// FEDFS_ERR_NSDB_NOFSN = 24, /// FEDFS_ERR_NSDB_NOFSL = 24,
/// FEDFS_ERR_NSDB_NOFSL = 25, /// FEDFS_ERR_NSDB_RESPONSE = 25,
/// FEDFS_ERR_NSDB_RESPONSE = 26, /// FEDFS_ERR_NSDB_FAULT = 26,
/// FEDFS_ERR_NSDB_FAULT = 27, /// FEDFS_ERR_NSDB_PARAMS = 27,
/// FEDFS_ERR_NSDB_PARAMS = 28, /// FEDFS_ERR_NSDB_LDAP_REFERRAL = 28,
/// FEDFS_ERR_PATH_TYPE_UNSUPP = 29 /// FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL = 29,
/// FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED = 30,
/// FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL = 31,
/// FEDFS_ERR_PATH_TYPE_UNSUPP = 32,
/// FEDFS_ERR_DELAY = 33,
/// FEDFS_ERR_NO_CACHE = 34,
/// FEDFS_ERR_UNKOWN_CACHE = 35,
/// FEDFS_ERR_NO_CACHE_UPDATE = 36
/// }; /// };
/// ///
/// 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 {
/// unsigned int port; /// unsigned int port;
skipping to change at page 7, line 8 skipping to change at page 8, line 16
/// }; /// };
/// ///
/// enum FedFsPathType { /// enum FedFsPathType {
/// FEDFS_PATH_SYS = 0, /// FEDFS_PATH_SYS = 0,
/// FEDFS_PATH_NFS = 1 /// FEDFS_PATH_NFS = 1
/// /* other types TBD */ /// /* other types TBD */
/// }; /// };
/// ///
/// union FedFsPath switch(FedFsPathType type) { /// union FedFsPath switch(FedFsPathType type) {
/// case FEDFS_PATH_SYS: /* administrative path */ /// case FEDFS_PATH_SYS: /* administrative path */
/// FedFsPathName admin_path; /// FedFsPathName adminPath;
/// case FEDFS_PATH_NFS: /* NFS namespace path */ /// case FEDFS_PATH_NFS: /* NFS namespace path */
/// FedFsPathName nfs_path; /// FedFsPathName nfsPath;
/// }; /// };
/// ///
/// struct FedFsCreateJunctionArgs { /// struct FedFsCreateArgs {
/// FedFsPath path; /// FedFsPath path;
/// FedFsFsn fsn; /// FedFsFsn fsn;
/// }; /// };
/// ///
/// enum FedFsResolveType { /// enum FedFsResolveType {
/// FEDFS_RESOLVE_NONE = 0, /// FEDFS_RESOLVE_NONE = 0,
/// FEDFS_RESOLVE_CACHE = 1, /// FEDFS_RESOLVE_CACHE = 1,
/// FEDFS_RESOLVE_NSDB = 2 /// FEDFS_RESOLVE_NSDB = 2
/// }; /// };
/// ///
/// struct FedFsLookupFsnArgs { /// struct FedFsLookupArgs {
/// FedFsPath path; /// FedFsPath path;
/// FedFsResolveType resolve; /// FedFsResolveType resolve;
/// }; /// };
/// ///
/// struct FedFsLookupFsnResOk { /// struct FedFsLookupResOk {
/// FedFsFsn fsn; /// FedFsFsn fsn;
/// FedFsFsl fsl<>; /// FedFsFsl fsl<>;
/// }; /// };
/// ///
/// union FedFsLookupFsnRes switch (FedFsStatus status) { /// struct FedFsLookupResReferralVal {
/// FedFsNsdbName targetNsdb;
/// unsigned int ldapResultCode;
/// };
///
/// union FedFsLookupRes switch (FedFsStatus status) {
/// case FEDFS_OK: /// case FEDFS_OK:
/// FedFsLookupFsnResOk resok; /// case FEDFS_ERR_NO_CACHE_UPDATE:
/// FedFsLookupResOk resok;
/// case FEDFS_ERR_NSDB_LDAP_VAL: /// case FEDFS_ERR_NSDB_LDAP_VAL:
/// unsigned int ldapResultCode; /// unsigned int ldapResultCode;
/// case FEDFS_ERR_NSDB_LDAP_REFERRAL:
/// case FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL:
/// FedFsNsdbName targetNsdb;
/// case FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL:
/// FedFsLookupResReferralVal resReferralVal;
/// default: /// default:
/// void; /// void;
/// }; /// };
/// ///
/// enum FedFsConnectionSec { /// enum FedFsConnectionSec {
/// FEDFS_SEC_NONE = 0, /// FEDFS_SEC_NONE = 0,
/// FEDFS_SEC_TLS = 1 /* StartTLS mechanism; RFC4513, Section 3 */ /// FEDFS_SEC_TLS = 1 /* StartTLS mechanism; RFC4513, Section 3 */
/// /* other mechanisms TBD */ /// /* other mechanisms TBD */
/// }; /// };
/// ///
skipping to change at page 8, line 31 skipping to change at page 9, line 49
/// case FEDFS_OK: /// case FEDFS_OK:
/// FedFsConnectionSec secType; /// FedFsConnectionSec secType;
/// default: /// default:
/// void; /// void;
/// }; /// };
/// ///
/// program FEDFS_PROG { /// program FEDFS_PROG {
/// version FEDFS_V1 { /// version FEDFS_V1 {
/// void FEDFS_NULL(void) = 0; /// void FEDFS_NULL(void) = 0;
/// FedFsStatus FEDFS_CREATE_JUNCTION( /// FedFsStatus FEDFS_CREATE_JUNCTION(
/// FedFsCreateJunctionArgs) = 1; /// FedFsCreateArgs) = 1;
/// FedFsStatus FEDFS_DELETE_JUNCTION( /// FedFsStatus FEDFS_DELETE_JUNCTION(
/// FedFsPathName) = 2; /// FedFsPath) = 2;
/// FedFsLookupFsnRes FEDFS_LOOKUP_JUNCTION( /// FedFsLookupRes FEDFS_LOOKUP_JUNCTION(
/// FedFsLookupFsnArgs) = 3; /// FedFsLookupArgs) = 3;
/// FedFsStatus FEDFS_CREATE_REPLICATION( /// FedFsStatus FEDFS_CREATE_REPLICATION(
/// FedFsCreateJunctionArgs) = 7; /// FedFsCreateArgs) = 7;
/// FedFsStatus FEDFS_DELETE_REPLICATION( /// FedFsStatus FEDFS_DELETE_REPLICATION(
/// FedFsPathName) = 8; /// FedFsPath) = 8;
/// FedFsLookupFsnRes FEDFS_LOOKUP_REPLICATION( /// FedFsLookupRes FEDFS_LOOKUP_REPLICATION(
/// FedFsLookupFsnArgs) = 9; /// FedFsLookupArgs) = 9;
/// FedFsStatus FEDFS_SET_NSDB_PARAMS( /// FedFsStatus FEDFS_SET_NSDB_PARAMS(
/// FedFsSetNsdbParamsArgs) = 4; /// FedFsSetNsdbParamsArgs) = 4;
/// FedFsGetNsdbParamsRes FEDFS_GET_NSDB_PARAMS( /// FedFsGetNsdbParamsRes FEDFS_GET_NSDB_PARAMS(
/// FedFsNsdbName) = 5; /// FedFsNsdbName) = 5;
/// FedFsGetLimitedNsdbParamsRes FEDFS_GET_LIMITED_NSDB_PARAMS( /// FedFsGetLimitedNsdbParamsRes FEDFS_GET_LIMITED_NSDB_PARAMS(
/// FedFsNsdbName) = 6; /// FedFsNsdbName) = 6;
/// } = 1; /// } = 1;
/// } = 100418; /// } = 100418;
<CODE ENDS> <CODE ENDS>
3. Error Values 3. Error Values
The results of successful operations will consist of a status of The results of successful operations will consist of a status of
FEDFS_OK. The results of unsuccessful operations will begin with a FEDFS_OK. The results of unsuccessful operations will begin with a
status, other than FEDFS_OK, that indicates the reason why the status, other than FEDFS_OK, that indicates the reason why the
operation failed. operation failed.
Many of the error status names and meanings (and the prose for their Many of the error status names and meanings (and the prose for their
descriptions) are taken from the specification for NFSv4 [RFC3530]. descriptions) are taken from the specification for NFSv4 [3530bis].
Note, however, that the literal values for the status codes are Note, however, that the literal values for the status codes are
different. different.
Note that the status of an unsuccessful operation will generally only Note that the status of an unsuccessful operation will generally only
indicate the first error encountered during the attempt to execute indicate the first error encountered during the attempt to execute
the operation. the operation.
FEDFS_OK: No errors were encountered. The operation was a success. FEDFS_OK: No errors were encountered. The operation was a success.
FEDFS_ERR_ACCESS: Permission denied. The caller does not have the FEDFS_ERR_ACCESS: Permission denied. The caller does not have the
skipping to change at page 10, line 5 skipping to change at page 11, line 25
FEDFS_ERR_INVAL: Invalid argument for an operation. FEDFS_ERR_INVAL: Invalid argument for an operation.
FEDFS_ERR_IO: A hard error occurred while processing the requested FEDFS_ERR_IO: A hard error occurred while processing the requested
operation. operation.
FEDFS_ERR_NOSPC: The requested operation would have caused the FEDFS_ERR_NOSPC: The requested operation would have caused the
server's filesystem to exceed some limit (for example, if there is server's filesystem to exceed some limit (for example, if there is
a fixed number of junctions per fileset or per server). a fixed number of junctions per fileset or per server).
FEDFS_ERR_NOTDIR: The caller specified a non-directory in an
operation that requires a directory.
FEDFS_ERR_NOTEMPTY: The caller specified a directory that is not
empty as the operand of an operation that requires an empty
directory.
FEDFS_ERR_NOTJUNCT: The caller specified a path that does not end in FEDFS_ERR_NOTJUNCT: The caller specified a path that does not end in
a junction as the operand for an operation that requires the last a junction as the operand for an operation that requires the last
component of the path to be a junction. component of the path to be a junction.
FEDFS_ERR_NOTLOCAL: The caller specified a path that contains a FEDFS_ERR_NOTLOCAL: The caller specified a path that contains a
junction in any position other than the last component. junction in any position other than the last component.
FEDFS_ERR_PERM: The operation was not allowed because the caller is FEDFS_ERR_PERM: The operation was not allowed because the caller is
either not a privileged user or not the owner of an object that either not a privileged user or not the owner of an object that
would be modified by the operation. would be modified by the operation.
skipping to change at page 11, line 17 skipping to change at page 12, line 30
FEDFS_ERR_NSDB_RESPONSE: The fileserver received a malformed FEDFS_ERR_NSDB_RESPONSE: The fileserver received a malformed
response from the NSDB. response from the NSDB.
FEDFS_ERR_NSDB_FAULT: An unanticipated error related to the NSDB FEDFS_ERR_NSDB_FAULT: An unanticipated error related to the NSDB
occurred. occurred.
FEDFS_ERR_NSDB_PARAMS: The fileserver does not have any connection FEDFS_ERR_NSDB_PARAMS: The fileserver does not have any connection
parameters on record for the specified NSDB. parameters on record for the specified NSDB.
FEDFS_ERR_NSDB_LDAP_REFERRAL: The fileserver received an LDAP
referral that it was unable to follow.
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL: Indicates the same error as
FEDFS_ERR_NSDB_LDAP_REFERRAL, and allows the LDAP protocol error
value to be returned back to the client.
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED: The fileserver received an
LDAP referral that it chose not to follow, either because the
fileserver does not support following LDAP referrals or LDAP
referral following is disabled.
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL: The fileserver received an LDAP
referral that it chose not to follow because the fileserver had no
NSDB parameters for the NSDB targeted by the LDAP referral.
FEDFS_ERR_PATH_TYPE_UNSUPP: The fileserver does not support the FEDFS_ERR_PATH_TYPE_UNSUPP: The fileserver does not support the
specified FedFsPathType value. specified FedFsPathType value.
FEDFS_ERR_NOTSUPP: The fileserver does not support the specified
procedure.
FEDFS_ERR_DELAY: The fileserver initiated the request, but was not
able to complete it in a timely fashion. The client should wait
and then try the request with a new RPC transaction ID.
FEDFS_ERR_NO_CACHE: The fileserver does not implement an FSN-to-FSL
cache.
FEDFS_ERR_UNKOWN_CACHE: The software receiving the ONC RPC request
is unaware if the fileserver implements an FSN-to-FSL cache or
unable to communicate with the FSN-to-FSL cache if it exists.
FEDFS_ERR_NO_CACHE_UPDATE: The fileserver was unable to update its
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:
FedFsUuid: A universally unique identifier (UUID) as described in FedFsUuid: A universally unique identifier (UUID) as described in
[RFC4122] as a version 1 UUID. The UUID should be formatted in [RFC4122] as a version 1 UUID. The UUID should be formatted in
network byte order. network byte order.
FedFsNsdbName: A (hostname, port) pair. FedFsNsdbName: A (hostname, port) pair.
The hostname is a variable length UTF-8 string that represents an The hostname is a variable length UTF-8 string that represents an
NSDB's network location in DNS name notation. The DNS name MUST NSDB's network location in DNS name notation. It SHOULD be
be represented using a fully qualified domain name. A system prepared using the server4 rules defined in Chapter 12
(i.e. fileserver or administrative host) SHOULD resolve the fully "Internationalization" of [3530bis]. The DNS name MUST be
represented using a fully qualified domain name. A system (i.e.
fileserver or administrative host) SHOULD resolve the fully
qualified domain name to a network address using the system's qualified domain name to a network address using the system's
standard resolution mechanisms. standard resolution mechanisms.
The port is the NSDB transport port. The port value MUST be in The port is the NSDB transport port. The port value MUST be in
the range 0 (zero) to 65535. A value of 0 (zero) indicates that the range 0 (zero) to 65535. A value of 0 (zero) indicates that
the standard LDAP port number, 389, SHOULD be assumed. the standard LDAP port number, 389, SHOULD be assumed.
FSNs are immutable and invariant. The attributes of an FSN, FSNs are immutable and invariant. The attributes of an FSN,
including the fedfsNsdbName, are expected to remain constant. including the fedfsNsdbName, are expected to remain constant.
Therefore, a FedFsNsdbName SHOULD NOT contain a network address, Therefore, a FedFsNsdbName SHOULD NOT contain a network address,
such as an IPv4 or IPv6 address, as this would indefinitely assign such as an IPv4 or IPv6 address, as this would indefinitely assign
the network address. the network address.
FedFsPathComponent: A case sensitive UTF-8 string containing a FedFsPathComponent: A case sensitive UTF-8 string containing a
filesystem path component. filesystem path component. It SHOULD be prepared using the
component4 rules defined in Chapter 12 "Internationalization" of
[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.
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.
skipping to change at page 13, line 7 skipping to change at page 15, line 7
Two FedFsNsdbNames are considered equal if both their DNS name and Two FedFsNsdbNames are considered equal if both their DNS name and
port values are the same. As described above, the standard LDAP port port values are the same. As described above, the standard LDAP port
number, 389, SHOULD be assumed if a port number of 0 (zero) is number, 389, SHOULD be assumed if a port number of 0 (zero) is
specified. Therefore, the FedFsNsdbName "(nsdb.example.com, 0)" is specified. Therefore, the FedFsNsdbName "(nsdb.example.com, 0)" is
considered equal to "(nsdb.example.com, 389)" but not equal to considered equal to "(nsdb.example.com, 389)" but not equal to
"(nsdb.example.com, 1066)" since the port number is different or "(nsdb.example.com, 1066)" since the port number is different or
"(nsdb.foo.example.com, 389)" since the DNS name is different. "(nsdb.foo.example.com, 389)" since the DNS name is different.
5. Procedures 5. Procedures
Fileservers that participate as "internal" nodes in the federated The procedures defined in Section 2 are described in detail in the
namespace MUST provide these procedures: following sections.
FEDFS_NULL The null RPC, which is included, by convention, in every
ONC RPC protocol.
FEDFS_CREATE_JUNCTION Create a new junction from some location on
the server (defined as a pathname) to an FSN.
FEDFS_DELETE_JUNCTION Delete an existing junction from some location
on the server (defined as a pathname).
FEDFS_LOOKUP_JUNCTION Query the server to discover the current value
of the junction (if any) at a given path in the server namespace.
FEDFS_CREATE_REPLICATION Set an FSN representing the replication
information for the fileset containing the pathname.
FEDFS_DELETE_REPLICATION Remove the replication information for the
fileset containing the pathname.
FEDFS_LOOKUP_REPLICATION Query the server to discover the current
replication information (if any) at the given path.
FEDFS_SET_NSDB_PARAMS Set the connection parameters for the
specified NSDB.
FEDFS_GET_NSDB_PARAMS Get the connection parameters for the
specified NSDB.
FEDFS_GET_LIMITED_NSDB_PARAMS Get a limited subset of the connection Fileservers that participate as "internal" nodes in the federated
parameters for the specified NSDB. namespace MUST implement all procedures, specifically:
The procedures above are described in more detail in the following FEDFS_NULL
sections. FEDFS_CREATE_JUNCTION
FEDFS_DELETE_JUNCTION
FEDFS_LOOKUP_JUNCTION
FEDFS_CREATE_REPLICATION
FEDFS_DELETE_REPLICATION
FEDFS_LOOKUP_REPLICATION
FEDFS_SET_NSDB_PARAMS
FEDFS_GET_NSDB_PARAMS
FEDFS_GET_LIMITED_NSDB_PARAMS
Fileservers that participate as "leaf" nodes in the namespace (i.e., Fileservers that participate as "leaf" nodes in the namespace (i.e.,
fileservers that host filesets that are the target of junctions, but fileservers that host filesets that are the target of junctions, but
that do not contain any junctions) are not required to implement any that do not contain any junctions) are not required to implement any
of these operations. of these operations.
Note that operations that modify the state of a replicated fileset Note that operations that modify the state of a replicated fileset
MUST result in the update of all of the replicas in a consistent MUST result in the update of all of the replicas in a consistent
manner. Ideally all of the replicas SHOULD be updated before any manner. Ideally all of the replicas SHOULD be updated before any
operation returns. If one or more of the replicas are unavailable, operation returns. If one or more of the replicas are unavailable,
the operation MAY succeed, but the changes MUST be applied before the the operation MAY succeed, but the changes MUST be applied before the
unavailable replicas are brought back online. We assume that unavailable replicas are brought back online. We assume that
replicas are updated via some protocol that permits state changes to replicas are updated via some protocol that permits state changes to
be reflected consistently across the set of replicas in such a manner be reflected consistently across the set of replicas in such a manner
that the replicas will converge to a consistent state within a that the replicas will converge to a consistent state within a
bounded number of successful message exchanges between the servers bounded number of successful message exchanges between the servers
hosting the replicas. hosting the replicas.
5.1. FEDFS_CREATE_JUNCTION 5.1. FEDFS_NULL
5.1.1. Synopsis
The standard NULL procedure.
5.1.2. Description
The null RPC, which is included, by convention, in every ONC RPC
protocol. This procedure does not take any arguments and does not
produce a result.
5.1.3. Errors
None.
5.2. FEDFS_CREATE_JUNCTION
5.2.1. Synopsis
Create a new junction from some location on the server (defined as a
pathname) to an FSN.
5.2.2. Description
This operation creates a junction from a server-relative path to a This operation creates a junction from a server-relative path to a
(potentially) remote fileset named by the given FSN. (potentially) remote fileset named by the given FSN.
The junction directory on the server is identified by a pathname in The junction directory on the server is identified by a pathname in
the form of an array of one or more UTF-8 path component strings. It the form of an array of one or more UTF-8 path component strings. It
is not required that this path be accessible in any other manner is not required that this path be accessible in any other manner
(e.g., to a client). This path does not appear in the federated (e.g., to a client). This path does not appear in the federated
namespace, except by coincidence; there is no requirement that the namespace, except by coincidence; there is no requirement that the
global namespace parallel the server namespace, nor is it required global namespace parallel the server namespace, nor is it required
skipping to change at page 14, line 37 skipping to change at page 16, line 42
If the fileset is read-only, then this operation SHOULD indicate this If the fileset is read-only, then this operation SHOULD indicate this
with a status of FEDFS_ERR_ROFS. with a status of FEDFS_ERR_ROFS.
If the path contains an invalid UTF-8 character, then status If the path contains an invalid UTF-8 character, then status
FEDFS_ERR_BADCHAR must be returned. FEDFS_ERR_BADCHAR must be returned.
The path is REQUIRED to exist and be completely local to the server. The path is REQUIRED to exist and be completely local to the server.
It MUST NOT contain a junction. If the last component of the path is It MUST NOT contain a junction. If the last component of the path is
a junction (i.e., this operation is attempting to create a junction a junction (i.e., this operation is attempting to create a junction
where one already exists), then this operation MUST return the error where one already exists), then this operation MUST return the error
FEDFS_ERR_EXISTS (even if the requested junction is identical to the FEDFS_ERR_EXIST (even if the requested junction is identical to the
current junction). If any other component of the path is a junction, current junction). If any other component of the path is a junction,
then this operation MUST fail with status FEDFS_ERR_NOTLOCAL. The then this operation MUST fail with status FEDFS_ERR_NOTLOCAL. The
path may contain a symbolic link (if supported by the local server), path may contain a symbolic link (if supported by the local server),
but the traversal of the path must remain within the server-local but the traversal of the path must remain within the server-local
namespace. namespace.
If any component of the path does not exist, then the operation fails If any component of the path does not exist, then the operation fails
with status FEDFS_ERR_INVAL. with status FEDFS_ERR_INVAL.
The server MAY enforce the local permissions on the path, including The server MAY enforce the local permissions on the path, including
skipping to change at page 15, line 14 skipping to change at page 17, line 18
The operation SHOULD fail with status FEDFS_ERR_NSDB_PARAMS if the The operation SHOULD fail with status FEDFS_ERR_NSDB_PARAMS if the
fileserver does not have any connection parameters on record for the fileserver does not have any connection parameters on record for the
specified NSDB. specified NSDB.
The association between the path and the FSN MUST be durable before The association between the path and the FSN MUST be durable before
the operation may return successfully. If the operation return codes the operation may return successfully. If the operation return codes
indicates success, then the caller may assume that the junction was indicates success, then the caller may assume that the junction was
successfully created and is immediately accessible. successfully created and is immediately accessible.
If successful, subsequent references via NFSv4 [RFC3530] or NFSv4.1 If successful, subsequent references via NFSv4 [3530bis] or NFSv4.1
[RFC5661] clients to the directory that has been replaced by the [RFC5661] clients to the directory that has been replaced by the
junction will result in a referral to a current location of the junction will result in a referral to a current location of the
target fileset [FEDFS-NSDB]. target fileset [FEDFS-NSDB].
Note that the effective permissions of the directory that is Note that the effective permissions of the directory that is
converted, by this operation, into a junction are the permissions of converted, by this operation, into a junction are the permissions of
the root directory of the target fileset. The original permissions the root directory of the target fileset. The original permissions
of the directory (and any other attributes it might have) are of the directory (and any other attributes it might have) are
subsumed by the junction. subsumed by the junction.
Note that this operation does not create a fileset at the location Note that this operation does not create a fileset at the location
targeted by the junction. If the target fileset does not exist, the targeted by the junction. If the target fileset does not exist, the
junction will still be created. An NFS client will discover the junction will still be created. An NFS client will discover the
missing fileset when it traverses the junction. missing fileset when it traverses the junction.
5.2. FEDFS_DELETE_JUNCTION 5.2.3. Errors
FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_NAMETOOLONG
FEDFS_ERR_LOOP
FEDFS_ERR_BADXDR
FEDFS_ERR_EXIST
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_NOSPC
FEDFS_ERR_NOTLOCAL
FEDFS_ERR_PERM
FEDFS_ERR_ROFS
FEDFS_ERR_SVRFAULT
FEDFS_ERR_PATH_TYPE_UNSUPP
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
5.3. FEDFS_DELETE_JUNCTION
5.3.1. Synopsis
Delete an existing junction from some location on the server (defined
as a pathname).
5.3.2. Description
This operation removes a junction specified by a server-relative This operation removes a junction specified by a server-relative
path. path.
As with FEDFS_CREATE_JUNCTION, the junction on the server is As with FEDFS_CREATE_JUNCTION, the junction on the server is
identified by a pathname in the form of an array of one or more UTF-8 identified by a pathname in the form of an array of one or more UTF-8
path component strings. It is not required that this path be path component strings. It is not required that this path be
accessible in any other manner (e.g., to a client). This path does accessible in any other manner (e.g., to a client). This path does
not appear in the federated namespace, except by coincidence; there not appear in the federated namespace, except by coincidence; there
is no requirement that the global namespace reflect the server is no requirement that the global namespace reflect the server
skipping to change at page 16, line 13 skipping to change at page 18, line 47
was used to create the junction. If the namespace on the server has was used to create the junction. If the namespace on the server has
changed, then the junction may now appear at a different path than changed, then the junction may now appear at a different path than
where it was created. If there is more than one valid path to the where it was created. If there is more than one valid path to the
junction, any of them may be used. junction, any of them may be used.
The path is REQUIRED to exist and be completely local to the server. The path is REQUIRED to exist and be completely local to the server.
It MUST NOT contain a junction, except as the final component, which It MUST NOT contain a junction, except as the final component, which
MUST be a junction. If any other component of the path is a MUST be a junction. If any other component of the path is a
junction, then this operation MUST fail with status junction, then this operation MUST fail with status
FEDFS_ERR_NOTLOCAL. If the last component of the path is not a FEDFS_ERR_NOTLOCAL. If the last component of the path is not a
junction then this operation MUST return status FEDFS_ERR_INVAL. The junction then this operation MUST return status FEDFS_ERR_NOTJUNCT.
path may contain a symbolic link (if supported by the local server), The path may contain a symbolic link (if supported by the local
but the traversal of the path must remain within the server-local server), but the traversal of the path must remain within the server-
namespace. local namespace.
The server MAY enforce the local permissions on the path, including The server MAY enforce the local permissions on the path, including
the final component. If the path cannot be traversed because of the final component. If the path cannot be traversed because of
insufficient permissions, or the parent directory of the junction is insufficient permissions, or the parent directory of the junction is
an unexecutable or unwritable directory, then the operation MAY fail an unexecutable or unwritable directory, then the operation MAY fail
with status FEDFS_ERR_ACCESS. with status FEDFS_ERR_ACCESS.
The removal of the association between the path and the FSN MUST be The removal of the association between the path and the FSN MUST be
durable before the operation may return successfully. If the durable before the operation may return successfully. If the
operation return codes indicates success, then the caller may assume operation return codes indicates success, then the caller may assume
skipping to change at page 16, line 38 skipping to change at page 19, line 25
The effective permissions and other attributes of the directory that The effective permissions and other attributes of the directory that
is restored by this operation SHOULD be identical to their value is restored by this operation SHOULD be identical to their value
prior to the creation of the junction. prior to the creation of the junction.
After removal of the junction, the fileserver MAY check if any of its After removal of the junction, the fileserver MAY check if any of its
existing junctions reference the NSDB specified in the removed existing junctions reference the NSDB specified in the removed
junction's FSN. If the NSDB is not referenced, the fileserver MAY junction's FSN. If the NSDB is not referenced, the fileserver MAY
delete the connection parameters of the unreferenced NSDB. delete the connection parameters of the unreferenced NSDB.
5.3. FEDFS_LOOKUP_JUNCTION 5.3.3. Errors
FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_NAMETOOLONG
FEDFS_ERR_LOOP
FEDFS_ERR_BADXDR
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_NOTJUNCT
FEDFS_ERR_NOTLOCAL
FEDFS_ERR_PERM
FEDFS_ERR_ROFS
FEDFS_ERR_SVRFAULT
FEDFS_ERR_PATH_TYPE_UNSUPP
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
5.4. FEDFS_LOOKUP_JUNCTION
5.4.1. Synopsis
Query the server to discover the current value of the junction (if
any) at a given path in the server namespace.
5.4.2. Description
This operation queries a server to determine whether a given path This operation queries a server to determine whether a given path
ends in a junction, and if so, the FSN to which the junction refers ends in a junction, and if so, the FSN to which the junction refers
and the filerserver's ability to resolve the junction. and the filerserver's ability to resolve the junction.
Ordinary NFSv4 operations do not provide any general mechanism to Ordinary NFSv4 operations do not provide any general mechanism to
determine whether an object is a junction -- there is no encoding determine whether an object is a junction -- there is no encoding
specified by the NFSv4 protocol that can represent this information. specified by the NFSv4 protocol that can represent this information.
As with FEDFS_CREATE_JUNCTION, the pathname must be in the form of an As with FEDFS_CREATE_JUNCTION, the pathname must be in the form of an
skipping to change at page 17, line 42 skipping to change at page 21, line 8
If the junction exists, the resolve parameter allows for testing the If the junction exists, the resolve parameter allows for testing the
fileserver's ability to resolve the junction. If the junction does fileserver's ability to resolve the junction. If the junction does
not exist, the fileserver will ignore the resolve parameter. not exist, the fileserver will ignore the resolve parameter.
If the junction exists and the resolve parameter is set to If the junction exists and the resolve parameter is set to
FEDFS_RESOLVE_NONE, the fileserver MUST NOT attempt to resolve the FEDFS_RESOLVE_NONE, the fileserver MUST NOT attempt to resolve the
FSN. This will allow the administrator to obtain the junction's FSN FSN. This will allow the administrator to obtain the junction's FSN
even if the resolution would fail. Therefore on success, the result even if the resolution would fail. Therefore on success, the result
of a FEDFS_RESOLVE_NONE call will return a 0 (zero) length fsl list of a FEDFS_RESOLVE_NONE call will return a 0 (zero) length fsl list
in the FedFsLookupFsnResOk 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 does the FSN by contacting the appropriate NSDB. If the fileserver's
not have a cache or its cache does not have a mapping for the FSN in cache does not have a mapping for the FSN in question, the result of
question, the result of the operation MUST be FEDFS_OK with the the operation MUST be FEDFS_OK with 0 (zero) elements in the
FedFsResolveRes's resolve value set to FEDFS_RESOLVE_NONE. FedFsLookupResOk structure's fsl array. The operation MAY fail with
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
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_RESPONSE, FEDFS_ERR_NSDB_NOFSN, FEDFS_ERR_NSDB_NOFSL, FEDFS_ERR_NSDB_RESPONSE,
or FEDFS_ERR_NSDB_FAULT depending on the nature of the failure. FEDFS_ERR_NSDB_FAULT, FEDFS_ERR_NSDB_LDAP_REFERRAL,
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL,
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED, or
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL, depending on the nature of the
failure.
In the case of a LDAP failure, the fileserver MAY return either In the case of a LDAP failure, the fileserver MAY return either
FEDFS_ERR_NSDB_LDAP or FEDFS_ERR_NSDB_LDAP_VAL. FEDFS_ERR_NSDB_LDAP FEDFS_ERR_NSDB_LDAP or FEDFS_ERR_NSDB_LDAP_VAL. FEDFS_ERR_NSDB_LDAP
indicates that an LDAP protocol error occurred during the resolution. indicates that an LDAP protocol error occurred during the resolution.
FEDFS_ERR_NSDB_LDAP_VAL also indicates that an LDAP protocol error FEDFS_ERR_NSDB_LDAP_VAL also indicates that an LDAP protocol error
occurred during the resolution and allows the LDAP protocol error occurred during the resolution and allows the LDAP protocol error
value to be returned in the FedFsLookupFsnRes's ldapResultCode field value to be returned in the FedFsLookupRes's ldapResultCode field
(see the resultCode values in Section 4.1.9 of [RFC4511]). (see the resultCode values in Section 4.1.9 of [RFC4511]).
If the NSDB responds with an LDAP referral, either the Referral type
defined in Section 4.1.10 of [RFC4511] or the SearchResultReference
type defined in Section 4.5.3 of [RFC4511], the fileserver SHOULD
process the LDAP referral using the same policies as the fileserver's
file-access protocol server. The fileserver can indicate a failure
while processing the LDAP referral using
FEDFS_ERR_NSDB_LDAP_REFERRAL, FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL,
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED, or
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL. The
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL is analogous to the
FEDFS_ERR_NSDB_LDAP_VAL error and allows the LDAP protocol error
value to be returned in the FedFsLookupResReferralVal's
ldapResultCode field. The FEDFS_ERR_NSDB_LDAP_REFERRAL and
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL errors errors allow the NSDB
targeted by the LDAP referral to be returned in the FedFsLookupRes's
targetNsdb field. Similarly, the FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL
error includes this information in the FedFsLookupResReferralVal's
targetNsdb.
If the fileserver has a cache of FSL records, the process of If the fileserver has a cache of FSL records, the process of
resolving an FSN using an NSDB SHOULD result in the cache being resolving an FSN using an NSDB SHOULD result in the cache being
updated. New FSLs for the given FSN SHOULD be added to the cache and updated. A failure to update the cache can be indicated with the
deleted FSLs SHOULD be removed from the cache. This behavior is FEDFS_ERR_NO_CACHE_UPDATE status value. When updating the cache, new
desirable because it allows an administrator to proactively request FSLs for the given FSN SHOULD be added to the cache and deleted FSLs
that the fileserver refresh its FSL cache. For example, the SHOULD be removed from the cache. This behavior is desirable because
administrator might like to refresh the fileserver's cache when it allows an administrator to proactively request that the fileserver
changes are made to an FSN's FSLs. refresh its FSL cache. For example, the administrator might like to
refresh the fileserver's cache when changes are made to an FSN's
FSLs.
If the junction is resolved, the fileserver will indicate the type of If the junction is resolved, the fileserver will include a list of
resolution that was performed using the FedFsResolveRes's resolve UUIDs for the FSN's FSLs in the FedFsLookupResOk structure's fsl
value and include a list of UUIDs for the FSN's FSLs in the array.
FedFsResolveRes's fslUuid array.
5.4. FEDFS_CREATE_REPLICATION 5.4.3. Errors
FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_NAMETOOLONG
FEDFS_ERR_LOOP
FEDFS_ERR_BADXDR
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_NOTJUNCT
FEDFS_ERR_NOTLOCAL
FEDFS_ERR_PERM
FEDFS_ERR_SVRFAULT
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_NOFSN
FEDFS_ERR_NSDB_NOFSL
FEDFS_ERR_NSDB_RESPONSE
FEDFS_ERR_NSDB_FAULT
FEDFS_ERR_NSDB_PARAMS
FEDFS_ERR_NSDB_LDAP_REFERRAL
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL
FEDFS_ERR_PATH_TYPE_UNSUPP
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
FEDFS_ERR_NO_CACHE
FEDFS_ERR_UNKOWN_CACHE
FEDFS_ERR_NO_CACHE_UPDATE
5.5. FEDFS_CREATE_REPLICATION
5.5.1. Synopsis
Set an FSN representing the replication information for the fileset
containing the pathname.
5.5.2. Description
This operation indicates the replication information to be returned This operation indicates the replication information to be returned
for a particular fileset. An NFSv4.x client may request fs_locations for a particular fileset. An NFSv4.x client may request fs_locations
or fs_locations_info at any time to detect other copies of this or fs_locations_info at any time to detect other copies of this
fileset, and this operation supports this by supplying the FSN the fileset, and this operation supports this by supplying the FSN the
fileserver should use to respond. This FSN should be associated with fileserver should use to respond. This FSN should be associated with
the entire fileset in which the path resides, and should be used to the entire fileset in which the path resides, and should be used to
satisfy fs_locations or fs_locations_info attribute requests whenever satisfy fs_locations or fs_locations_info attribute requests whenever
no junction is being accessed; if a junction is being accessed, the no junction is being accessed; if a junction is being accessed, the
FSN specified by FEDFS_CREATE_JUNCTION will take precedence. FSN specified by FEDFS_CREATE_JUNCTION will take precedence.
skipping to change at page 19, line 25 skipping to change at page 24, line 15
The server MAY enforce the local permissions on the path, including The server MAY enforce the local permissions on the path, including
the final component. If the path cannot be traversed because of the final component. If the path cannot be traversed because of
insufficient permissions, or the final component is an unexecutable insufficient permissions, or the final component is an unexecutable
or unwritable directory, then the operation MAY fail with status or unwritable directory, then the operation MAY fail with status
FEDFS_ERR_ACCESS. FEDFS_ERR_ACCESS.
The operation SHOULD fail with status FEDFS_ERR_NSDB_PARAMS if the The operation SHOULD fail with status FEDFS_ERR_NSDB_PARAMS if the
fileserver does not have any connection parameters on record for the fileserver does not have any connection parameters on record for the
specified NSDB. specified NSDB.
5.5. FEDFS_DELETE_REPLICATION 5.5.3. Errors
FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_NAMETOOLONG
FEDFS_ERR_LOOP
FEDFS_ERR_BADXDR
FEDFS_ERR_EXIST
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_NOSPC
FEDFS_ERR_NOTLOCAL
FEDFS_ERR_PERM
FEDFS_ERR_ROFS
FEDFS_ERR_SVRFAULT
FEDFS_ERR_PATH_TYPE_UNSUPP
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
5.6. FEDFS_DELETE_REPLICATION
5.6.1. Synopsis
Remove the replication information for the fileset containing the
pathname.
5.6.2. Description
This operation removes any replication information from the fileset This operation removes any replication information from the fileset
in which the path resides, such that NFSv4.x client requests for in which the path resides, such that NFSv4.x client requests for
fs_locations or fs_locations_info in the absence of a junction will fs_locations or fs_locations_info in the absence of a junction will
not be satisfied. not be satisfied.
This operation differs from FEDFS_DELETE_JUNCTION in that it controls This operation differs from FEDFS_DELETE_JUNCTION in that it controls
a fileset-wide attribute not associated with a junction. a fileset-wide attribute not associated with a junction.
The server SHOULD permit this operation even on read-only filesets, The server SHOULD permit this operation even on read-only filesets,
skipping to change at page 20, line 5 skipping to change at page 25, line 20
It MUST NOT contain a junction. If any component of the path is a It MUST NOT contain a junction. If any component of the path is a
junction, then this operation MUST fail with status junction, then this operation MUST fail with status
FEDFS_ERR_NOTLOCAL. FEDFS_ERR_NOTLOCAL.
The server MAY enforce the local permissions on the path, including The server MAY enforce the local permissions on the path, including
the final component. If the path cannot be traversed because of the final component. If the path cannot be traversed because of
insufficient permissions, or the parent directory of the junction insufficient permissions, or the parent directory of the junction
unexecutable or unwritable directory, then the operation MAY fail unexecutable or unwritable directory, then the operation MAY fail
with status FEDFS_ERR_ACCESS. with status FEDFS_ERR_ACCESS.
5.6. FEDFS_LOOKUP_REPLICATION 5.6.3. Errors
FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_NAMETOOLONG
FEDFS_ERR_LOOP
FEDFS_ERR_BADXDR
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_NOTJUNCT
FEDFS_ERR_NOTLOCAL
FEDFS_ERR_PERM
FEDFS_ERR_ROFS
FEDFS_ERR_SVRFAULT
FEDFS_ERR_PATH_TYPE_UNSUPP
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
5.7. FEDFS_LOOKUP_REPLICATION
5.7.1. Synopsis
Query the server to discover the current replication information (if
any) at the given path.
5.7.2. Description
This operation queries a server to determine whether a fileset This operation queries a server to determine whether a fileset
containing the given path has replication information associated with containing the given path has replication information associated with
it, and if so, the FSN for that replication information. it, and if so, the FSN for that replication information.
This operation differs from FEDFS_LOOKUP_JUNCTION in that it inquires This operation differs from FEDFS_LOOKUP_JUNCTION in that it inquires
about a fileset-wide attribute not associated with a junction. about a fileset-wide attribute not associated with a junction.
If the path contains an invalid UTF-8 character, then status If the path contains an invalid UTF-8 character, then status
FEDFS_ERR_BADCHAR must be returned. FEDFS_ERR_BADCHAR must be returned.
skipping to change at page 20, line 28 skipping to change at page 26, line 22
It MUST NOT contain a junction. If any component of the path is a It MUST NOT contain a junction. If any component of the path is a
junction, then this operation MUST fail with status junction, then this operation MUST fail with status
FEDFS_ERR_NOTLOCAL. FEDFS_ERR_NOTLOCAL.
The server MAY enforce the local permissions on the path, including The server MAY enforce the local permissions on the path, including
the final component. If the path cannot be traversed because of the final component. If the path cannot be traversed because of
insufficient permissions, or the parent directory of the junction is insufficient permissions, or the parent directory of the junction is
an unexecutable or unwritable directory, then the operation MAY fail an unexecutable or unwritable directory, then the operation MAY fail
with status FEDFS_ERR_ACCESS. with status FEDFS_ERR_ACCESS.
Interpretation of the 'resolve' parameter shall be the same as Interpretation of the 'resolve' parameter and the procedure's results
specified in Section 5.3 for the FEDFS_LOOKUP_JUNCTION operation. shall be the same as specified in Section 5.4 for the
FEDFS_LOOKUP_JUNCTION operation.
5.7. FEDFS_SET_NSDB_PARAMS 5.7.3. Errors
FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_NAMETOOLONG
FEDFS_ERR_LOOP
FEDFS_ERR_BADXDR
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_NOTJUNCT
FEDFS_ERR_NOTLOCAL
FEDFS_ERR_PERM
FEDFS_ERR_SVRFAULT
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_NOFSN
FEDFS_ERR_NSDB_NOFSL
FEDFS_ERR_NSDB_RESPONSE
FEDFS_ERR_NSDB_FAULT
FEDFS_ERR_NSDB_PARAMS
FEDFS_ERR_NSDB_LDAP_REFERRAL
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL
FEDFS_ERR_PATH_TYPE_UNSUPP
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
FEDFS_ERR_NO_CACHE
FEDFS_ERR_UNKOWN_CACHE
5.8. FEDFS_SET_NSDB_PARAMS
5.8.1. Synopsis
Set the connection parameters for the specified NSDB.
5.8.2. Description
This operations allows the administrator to set the connection This operations allows the administrator to set the connection
parameters for a given NSDB. parameters for a given NSDB.
If a record for the given NSDB does not exist, a new record is If a record for the given NSDB does not exist, a new record is
created with the specified connection parameters. created with the specified connection parameters.
If a record for the given NSDB does exist, the existing connection If a record for the given NSDB does exist, the existing connection
parameters are replaced with the specified connection parameters. parameters are replaced with the specified connection parameters.
skipping to change at page 21, line 14 skipping to change at page 28, line 5
subsequent LDAP connections to the given NSDB. Existing connections subsequent LDAP connections to the given NSDB. Existing connections
MAY be terminated and re-established using the new connection MAY be terminated and re-established using the new connection
parameters. The connection parameters SHOULD be durable across parameters. The connection parameters SHOULD be durable across
fileserver reboots. fileserver reboots.
On failure, an error value indicating the type of error is returned. On failure, an error value indicating the type of error is returned.
The operation MAY return FEDFS_ERR_ACCESS if the operation's The operation MAY return FEDFS_ERR_ACCESS if the operation's
associated user does not have sufficient permissions to create/modify associated user does not have sufficient permissions to create/modify
NSDB connection parameters. NSDB connection parameters.
5.8. FEDFS_GET_NSDB_PARAMS 5.8.3. Errors
FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_BADXDR
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_NOSPC
FEDFS_ERR_SVRFAULT
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
5.9. FEDFS_GET_NSDB_PARAMS
5.9.1. Synopsis
Get the connection parameters for the specified NSDB.
5.9.2. Description
This operations allows the administrator to retrieve connection This operations allows the administrator to retrieve connection
parameters, if they exist, for the given NSDB. parameters, if they exist, for the given NSDB.
An NSDB is specified using a FedFsNsdbName. The rules in Section 4.1 An NSDB is specified using a FedFsNsdbName. The rules in Section 4.1
define when two FedFsNsdbNames are considered equal define when two FedFsNsdbNames are considered equal
A set of connection parameters is considered a match if their A set of connection parameters is considered a match if their
associated NSDB is equal (as defined above) to the operation's NSDB associated NSDB is equal (as defined above) to the operation's NSDB
argument. Therefore, there is at most one set of connection argument. Therefore, there is at most one set of connection
skipping to change at page 21, line 39 skipping to change at page 28, line 49
On success, this operation returns FEDFS_OK and the connection On success, this operation returns FEDFS_OK and the connection
parameters on record for the given NSDB. parameters on record for the given NSDB.
On failure, an error value indicating the type of error is returned. On failure, an error value indicating the type of error is returned.
This operation MAY return FEDFS_ERR_NSDB_PARAMS to indicate that This operation MAY return FEDFS_ERR_NSDB_PARAMS to indicate that
there are no connection parameters on record for the given NSDB. The there are no connection parameters on record for the given NSDB. The
operation MAY return FEDFS_ERR_ACCESS if the operation's associated operation MAY return FEDFS_ERR_ACCESS if the operation's associated
user does not have sufficient permissions to view NSDB connection user does not have sufficient permissions to view NSDB connection
parameters. parameters.
5.9. FEDFS_GET_LIMITED_NSDB_PARAMS 5.9.3. Errors
FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_BADXDR
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_SVRFAULT
FEDFS_ERR_NSDB_PARAMS
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
5.10. FEDFS_GET_LIMITED_NSDB_PARAMS
5.10.1. Synopsis
Get a limited subset of the connection parameters for the specified
NSDB.
5.10.2. Description
This operations allows the administrator to retrieve a limited subset This operations allows the administrator to retrieve a limited subset
of information on the connection parameters, if they exist, for the of information on the connection parameters, if they exist, for the
given NSDB. given NSDB.
An NSDB is specified using a FedFsNsdbName. The rules in Section 4.1 An NSDB is specified using a FedFsNsdbName. The rules in Section 4.1
define when two FedFsNsdbNames are considered equal define when two FedFsNsdbNames are considered equal
A set of connection parameters is considered a match if their A set of connection parameters is considered a match if their
associated NSDB is equal (as defined above) to the operation's NSDB associated NSDB is equal (as defined above) to the operation's NSDB
skipping to change at page 22, line 29 skipping to change at page 30, line 12
On success, this operation returns FEDFS_OK and the On success, this operation returns FEDFS_OK and the
FedFsConnectionSec value on record for the given NSDB. FedFsConnectionSec value on record for the given NSDB.
On failure, an error value indicating the type of error is returned. On failure, an error value indicating the type of error is returned.
This operation MAY return FEDFS_ERR_NSDB_PARAMS to indicate that This operation MAY return FEDFS_ERR_NSDB_PARAMS to indicate that
there are no connection parameters on record for the given NSDB. The there are no connection parameters on record for the given NSDB. The
operation MAY return FEDFS_ERR_ACCESS if the operation's associated operation MAY return FEDFS_ERR_ACCESS if the operation's associated
user does not have sufficient permissions to view the subset of NSDB user does not have sufficient permissions to view the subset of NSDB
connection parameters returned by this procedure. connection parameters returned by this procedure.
6. Internationalization 5.10.3. Errors
TBD. All UTF-8 strings and DNS names will conform to the rules FEDFS_ERR_ACCESS
defined by rfc3530bis. FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME
FEDFS_ERR_BADXDR
FEDFS_ERR_INVAL
FEDFS_ERR_IO
FEDFS_ERR_SVRFAULT
FEDFS_ERR_NSDB_PARAMS
FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY
7. Security Considerations 6. Security Considerations
The ONC RPC protocol supports authentication, integrity and privacy The ONC RPC protocol supports authentication, integrity and privacy
via the RPCSEC_GSS framework [RFC2203]. Fileservers which support via the RPCSEC_GSS framework [RFC2203]. Fileservers which support
the FedFS administration protocol described above MUST support the FedFS administration protocol described above MUST support
RPCSEC_GSS. RPCSEC_GSS.
8. IANA Considerations 7. IANA Considerations
A range of ONC RPC program numbers were assigned for use by FedFS A range of ONC RPC program numbers were assigned for use by FedFS
using the procedure described in Section 7.3 "Program Number using the procedure described in Section 7.3 "Program Number
Assignment" of [RFC5531]. The FedFS range is: Assignment" of [RFC5531]. The FedFS range is:
IETF NFSv4 Working Group - FedFS 100418 - 100421 IETF NFSv4 Working Group - FedFS 100418 - 100421
This document describes version 1 of the ONC RPC program 100418. This document describes version 1 of the ONC RPC program 100418.
9. Glossary 8. Glossary
Administrator: user with the necessary authority to initiate Administrator: user with the necessary authority to initiate
administrative tasks on one or more servers. administrative tasks on one or more servers.
Admin Entity: A server or agent that administers a collection of Admin Entity: A server or agent that administers a collection of
fileservers and persistently stores the namespace information. fileservers and persistently stores the namespace information.
Client: Any client that accesses the fileserver data using a Client: Any client that accesses the fileserver data using a
supported filesystem access protocol. supported filesystem access protocol.
skipping to change at page 23, line 44 skipping to change at page 31, line 35
Filesystem: A self-contained unit of export for a fileserver, and Filesystem: A self-contained unit of export for a fileserver, and
the mechanism used to implement filesets. The fileset does not the mechanism used to implement filesets. The fileset does not
need to be rooted at the root of the filesystem, nor at the export need to be rooted at the root of the filesystem, nor at the export
point for the filesystem. point for the filesystem.
A single filesystem MAY implement more than one fileset, if the A single filesystem MAY implement more than one fileset, if the
client protocol and the fileserver permit this. client protocol and the fileserver permit this.
Filesystem Access Protocol: A network filesystem access protocol Filesystem Access Protocol: A network filesystem access protocol
such as NFSv2 [RFC1094], NFSv3 [RFC1813], NFSv4 [RFC3530], or CIFS such as NFSv2 [RFC1094], NFSv3 [RFC1813], NFSv4 [3530bis], or CIFS
(Common Internet File System) [MS-SMB] [MS-SMB2] [MS-CIFS]. (Common Internet File System) [MS-SMB] [MS-SMB2] [MS-CIFS].
FSL (Fileset Location): The location of the implementation of a FSL (Fileset Location): The location of the implementation of a
fileset at a particular moment in time. An FSL MUST be something fileset at a particular moment in time. An FSL MUST be something
that can be translated into a protocol-specific description of a that can be translated into a protocol-specific description of a
resource that a client can access directly, such as an fs_location resource that a client can access directly, such as an fs_location
(for NFSv4), or share name (for CIFS). Note that not all FSLs (for NFSv4), or share name (for CIFS). Note that not all FSLs
need to be explicitly exported as long as they are contained need to be explicitly exported as long as they are contained
within an exported path on the fileserver. within an exported path on the fileserver.
skipping to change at page 25, line 9 skipping to change at page 32, line 49
Server Collection: A set of fileservers administered as a unit. A Server Collection: A set of fileservers administered as a unit. A
server collection may be administered with vendor-specific server collection may be administered with vendor-specific
software. software.
The namespace provided by a server collection could be part of the The namespace provided by a server collection could be part of the
federated namespace. federated namespace.
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.
10. References 9. References
9.1. Normative References
10.1. Normative References [3530bis] Haynes, T. and D. Noveck, "NFS Version 4 Protocol",
draft-ietf-nfsv4-rfc3530bis (Work In Progress), 2010.
[RFC1094] Nowicki, B., "NFS: Network File System Protocol [RFC1094] Nowicki, B., "NFS: Network File System Protocol
specification", RFC 1094, March 1989. specification", RFC 1094, March 1989.
[RFC1813] Callaghan, B., Pawlowski, B., and P. Staubach, "NFS [RFC1813] Callaghan, B., Pawlowski, B., and P. Staubach, "NFS
Version 3 Protocol Specification", RFC 1813, June 1995. 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.
skipping to change at page 26, line 5 skipping to change at page 33, line 46
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, May 2008. (CRL) Profile", RFC 5280, May 2008.
[RFC5531] Thurlow, R., "RPC: Remote Procedure Call Protocol [RFC5531] Thurlow, R., "RPC: Remote Procedure Call Protocol
Specification Version 2", RFC 5531, May 2009. Specification Version 2", RFC 5531, May 2009.
10.2. Informative References 9.2. Informative References
[FEDFS-NSDB] [FEDFS-NSDB]
Lentini, J., Everhart, C., Ellard, D., Tewari, R., and M. Lentini, J., Everhart, C., Ellard, D., Tewari, R., and M.
Naik, "NSDB Protocol for Federated Filesystems", Naik, "NSDB Protocol for Federated Filesystems",
draft-ietf-nfsv4-federated-fs-protocol (Work In Progress), draft-ietf-nfsv4-federated-fs-protocol (Work In Progress),
2010. 2010.
[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.
[RFC3530] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R.,
Beame, C., Eisler, M., and D. Noveck, "Network File System
(NFS) version 4 Protocol", RFC 3530, April 2003.
[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 27, line 21 skipping to change at page 35, line 18
NetApp NetApp
1601 Trapelo Rd, Suite 16 1601 Trapelo Rd, Suite 16
Waltham, MA 02451 Waltham, MA 02451
US US
Phone: +1 781-768-5359 Phone: +1 781-768-5359
Email: jlentini@netapp.com Email: jlentini@netapp.com
Craig Everhart Craig Everhart
NetApp NetApp
7301 Kit Creek Rd 800 Cranberry Woods Drive
Research Triangle Park, NC 27709 Cranberry Township, PA 16066
US US
Phone: +1 919-476-5320 Phone: +1 724-741-5101
Email: everhart@netapp.com Email: Craig.Everhart@netapp.com
Daniel Ellard Daniel Ellard
Raytheon BBN Technologies Raytheon BBN Technologies
10 Moulton Street 10 Moulton Street
Cambridge, MA 02138 Cambridge, MA 02138
US US
Phone: +1 617-873-8000 Phone: +1 617-873-8004
Email: dellard@bbn.com Email: dellard@bbn.com
Renu Tewari Renu Tewari
IBM Almaden IBM Almaden
650 Harry Rd 650 Harry Rd
San Jose, CA 95120 San Jose, CA 95120
US US
Email: tewarir@us.ibm.com Email: tewarir@us.ibm.com
Manoj Naik Manoj Naik
 End of changes. 60 change blocks. 
172 lines changed or deleted 517 lines changed or added

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