draft-ietf-nfsv4-federated-fs-admin-06.txt   draft-ietf-nfsv4-federated-fs-admin-07.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 2, 2011 D. Ellard Expires: April 13, 2011 D. Ellard
Raytheon BBN Technologies Raytheon BBN Technologies
R. Tewari R. Tewari
M. Naik M. Naik
IBM Almaden IBM Almaden
September 29, 2010 October 10, 2010
Administration Protocol for Federated Filesystems Administration Protocol for Federated Filesystems
draft-ietf-nfsv4-federated-fs-admin-06 draft-ietf-nfsv4-federated-fs-admin-07
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 2, 2011. This Internet-Draft will expire on April 13, 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 11 skipping to change at page 3, line 11
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 . . . . . . . . . . . . . . . . . . . . . . . . . 10
4. Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4. Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. FedFsNsdbName Equality . . . . . . . . . . . . . . . . . . 14 4.1. FedFsNsdbName Equality . . . . . . . . . . . . . . . . . . 15
5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1. FEDFS_NULL . . . . . . . . . . . . . . . . . . . . . . . . 15 5.1. FEDFS_NULL . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 15 5.1.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.2. Description . . . . . . . . . . . . . . . . . . . . . 15 5.1.2. Description . . . . . . . . . . . . . . . . . . . . . 16
5.1.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2. FEDFS_CREATE_JUNCTION . . . . . . . . . . . . . . . . . . 16 5.2. FEDFS_CREATE_JUNCTION . . . . . . . . . . . . . . . . . . 16
5.2.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 16 5.2.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 16
5.2.2. Description . . . . . . . . . . . . . . . . . . . . . 16 5.2.2. Description . . . . . . . . . . . . . . . . . . . . . 16
5.2.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 17 5.2.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3. FEDFS_DELETE_JUNCTION . . . . . . . . . . . . . . . . . . 18 5.3. FEDFS_DELETE_JUNCTION . . . . . . . . . . . . . . . . . . 18
5.3.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 18 5.3.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.2. Description . . . . . . . . . . . . . . . . . . . . . 18 5.3.2. Description . . . . . . . . . . . . . . . . . . . . . 18
5.3.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 19 5.3.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 19
5.4. FEDFS_LOOKUP_JUNCTION . . . . . . . . . . . . . . . . . . 19 5.4. FEDFS_LOOKUP_JUNCTION . . . . . . . . . . . . . . . . . . 20
5.4.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 19 5.4.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 20
5.4.2. Description . . . . . . . . . . . . . . . . . . . . . 20 5.4.2. Description . . . . . . . . . . . . . . . . . . . . . 20
5.4.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 22 5.4.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 22
5.5. FEDFS_CREATE_REPLICATION . . . . . . . . . . . . . . . . . 23 5.5. FEDFS_CREATE_REPLICATION . . . . . . . . . . . . . . . . . 23
5.5.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 23 5.5.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 23
5.5.2. Description . . . . . . . . . . . . . . . . . . . . . 23 5.5.2. Description . . . . . . . . . . . . . . . . . . . . . 23
5.5.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 24 5.5.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 24
5.6. FEDFS_DELETE_REPLICATION . . . . . . . . . . . . . . . . . 24 5.6. FEDFS_DELETE_REPLICATION . . . . . . . . . . . . . . . . . 25
5.6.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 24 5.6.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 25
5.6.2. Description . . . . . . . . . . . . . . . . . . . . . 24 5.6.2. Description . . . . . . . . . . . . . . . . . . . . . 25
5.6.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 25 5.6.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 25
5.7. FEDFS_LOOKUP_REPLICATION . . . . . . . . . . . . . . . . . 25 5.7. FEDFS_LOOKUP_REPLICATION . . . . . . . . . . . . . . . . . 26
5.7.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 25 5.7.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 26
5.7.2. Description . . . . . . . . . . . . . . . . . . . . . 25 5.7.2. Description . . . . . . . . . . . . . . . . . . . . . 26
5.7.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 26 5.7.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 27
5.8. FEDFS_SET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 27 5.8. FEDFS_SET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 27
5.8.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 27 5.8.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 27
5.8.2. Description . . . . . . . . . . . . . . . . . . . . . 27 5.8.2. Description . . . . . . . . . . . . . . . . . . . . . 27
5.8.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 28 5.8.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 28
5.9. FEDFS_GET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 28 5.9. FEDFS_GET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 28
5.9.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 28 5.9.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 28
5.9.2. Description . . . . . . . . . . . . . . . . . . . . . 28 5.9.2. Description . . . . . . . . . . . . . . . . . . . . . 29
5.9.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 28 5.9.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 29
5.10. FEDFS_GET_LIMITED_NSDB_PARAMS . . . . . . . . . . . . . . 29 5.10. FEDFS_GET_LIMITED_NSDB_PARAMS . . . . . . . . . . . . . . 29
5.10.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 29 5.10.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 29
5.10.2. Description . . . . . . . . . . . . . . . . . . . . . 29 5.10.2. Description . . . . . . . . . . . . . . . . . . . . . 30
5.10.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 30 5.10.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 30
6. Security Considerations . . . . . . . . . . . . . . . . . . . 30 6. Security Considerations . . . . . . . . . . . . . . . . . . . 31
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
8. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 8. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.1. Normative References . . . . . . . . . . . . . . . . . . . 33 9.1. Normative References . . . . . . . . . . . . . . . . . . . 33
9.2. Informative References . . . . . . . . . . . . . . . . . . 33 9.2. Informative References . . . . . . . . . . . . . . . . . . 34
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 34 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 35
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 48 skipping to change at page 6, line 48
/// FEDFS_ERR_PERM = 13, /// FEDFS_ERR_PERM = 13,
/// FEDFS_ERR_ROFS = 14, /// FEDFS_ERR_ROFS = 14,
/// FEDFS_ERR_SVRFAULT = 15, /// FEDFS_ERR_SVRFAULT = 15,
/// FEDFS_ERR_NOTSUPP = 16, /// FEDFS_ERR_NOTSUPP = 16,
/// FEDFS_ERR_NSDB_ROUTE = 17, /// FEDFS_ERR_NSDB_ROUTE = 17,
/// FEDFS_ERR_NSDB_DOWN = 18, /// FEDFS_ERR_NSDB_DOWN = 18,
/// FEDFS_ERR_NSDB_CONN = 19, /// FEDFS_ERR_NSDB_CONN = 19,
/// FEDFS_ERR_NSDB_AUTH = 20, /// FEDFS_ERR_NSDB_AUTH = 20,
/// FEDFS_ERR_NSDB_LDAP = 21, /// FEDFS_ERR_NSDB_LDAP = 21,
/// FEDFS_ERR_NSDB_LDAP_VAL = 22, /// FEDFS_ERR_NSDB_LDAP_VAL = 22,
/// FEDFS_ERR_NSDB_NOFSN = 23, /// FEDFS_ERR_NSDB_NONCE = 23,
/// FEDFS_ERR_NSDB_NOFSL = 24, /// FEDFS_ERR_NSDB_NOFSN = 24,
/// FEDFS_ERR_NSDB_RESPONSE = 25, /// FEDFS_ERR_NSDB_NOFSL = 25,
/// FEDFS_ERR_NSDB_FAULT = 26, /// FEDFS_ERR_NSDB_RESPONSE = 26,
/// FEDFS_ERR_NSDB_PARAMS = 27, /// FEDFS_ERR_NSDB_FAULT = 27,
/// FEDFS_ERR_NSDB_LDAP_REFERRAL = 28, /// FEDFS_ERR_NSDB_PARAMS = 28,
/// FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL = 29, /// FEDFS_ERR_NSDB_LDAP_REFERRAL = 29,
/// FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED = 30, /// FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL = 30,
/// FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL = 31, /// FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED = 31,
/// FEDFS_ERR_PATH_TYPE_UNSUPP = 32, /// FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL = 32,
/// FEDFS_ERR_DELAY = 33, /// FEDFS_ERR_PATH_TYPE_UNSUPP = 33,
/// FEDFS_ERR_NO_CACHE = 34, /// FEDFS_ERR_DELAY = 34,
/// FEDFS_ERR_UNKOWN_CACHE = 35, /// FEDFS_ERR_NO_CACHE = 35,
/// FEDFS_ERR_NO_CACHE_UPDATE = 36 /// FEDFS_ERR_UNKOWN_CACHE = 36,
/// 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 {
/// unsigned int port; /// unsigned int port;
skipping to change at page 12, line 15 skipping to change at page 12, line 18
FEDFS_ERR_NSDB_AUTH: The fileserver was unable to authenticate and FEDFS_ERR_NSDB_AUTH: The fileserver was unable to authenticate and
establish a secure connection with the NSDB. establish a secure connection with the NSDB.
FEDFS_ERR_NSDB_LDAP: An LDAP error occurred on the connection FEDFS_ERR_NSDB_LDAP: An LDAP error occurred on the connection
between the fileserver and NSDB. between the fileserver and NSDB.
FEDFS_ERR_NSDB_LDAP_VAL: Indicates the same error as FEDFS_ERR_NSDB_LDAP_VAL: Indicates the same error as
FEDFS_ERR_NSDB_LDAP, and allows the LDAP protocol error value to FEDFS_ERR_NSDB_LDAP, and allows the LDAP protocol error value to
be returned back to the client. be returned back to the client.
FEDFS_ERR_NSDB_NONCE: The fileserver was unable to locate the NCE in
the appropriate NSDB.
FEDFS_ERR_NSDB_NOFSN: The fileserver was unable to locate the given FEDFS_ERR_NSDB_NOFSN: The fileserver was unable to locate the given
FSN in the appropriate NSDB. FSN in the appropriate NSDB.
FEDFS_ERR_NSDB_NOFSL: The fileserver was unable to locate any FSLs FEDFS_ERR_NSDB_NOFSL: The fileserver was unable to locate any FSLs
for the given FSN in the appropriate NSDB. for the given FSN in the appropriate NSDB.
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. This includes situations when an NSDB
entry (e.g. FSN or FSL) is missing a required attribute.
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 FEDFS_ERR_NSDB_LDAP_REFERRAL: The fileserver received an LDAP
referral that it was unable to follow. referral that it was unable to follow.
skipping to change at page 15, line 11 skipping to change at page 15, line 21
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
The procedures defined in Section 2 are described in detail in the The procedures defined in Section 2 are described in detail in the
following sections. following sections.
Fileservers that participate as "internal" nodes in the federated Fileservers that participate as "internal" nodes in the federated
namespace MUST implement all procedures, specifically: namespace MUST implement the following procedures:
FEDFS_NULL FEDFS_NULL
FEDFS_CREATE_JUNCTION FEDFS_CREATE_JUNCTION
FEDFS_DELETE_JUNCTION FEDFS_DELETE_JUNCTION
FEDFS_LOOKUP_JUNCTION FEDFS_LOOKUP_JUNCTION
FEDFS_CREATE_REPLICATION
FEDFS_DELETE_REPLICATION
FEDFS_LOOKUP_REPLICATION
FEDFS_SET_NSDB_PARAMS FEDFS_SET_NSDB_PARAMS
FEDFS_GET_NSDB_PARAMS FEDFS_GET_NSDB_PARAMS
FEDFS_GET_LIMITED_NSDB_PARAMS FEDFS_GET_LIMITED_NSDB_PARAMS
and SHOULD implement the following procedures:
FEDFS_CREATE_REPLICATION
FEDFS_DELETE_REPLICATION
FEDFS_LOOKUP_REPLICATION
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
skipping to change at page 21, line 27 skipping to change at page 21, line 41
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_UNKOWN_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_RESPONSE, FEDFS_ERR_NSDB_NOFSN, FEDFS_ERR_NSDB_NOFSL, FEDFS_ERR_NSDB_NONCE,
FEDFS_ERR_NSDB_FAULT, FEDFS_ERR_NSDB_LDAP_REFERRAL, FEDFS_ERR_NSDB_RESPONSE, FEDFS_ERR_NSDB_FAULT,
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL, FEDFS_ERR_NSDB_LDAP_REFERRAL, FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL,
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED, or FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED, or
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL, depending on the nature of the FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL, depending on the nature of the
failure. 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 FedFsLookupRes's ldapResultCode field value to be returned in the FedFsLookupRes's ldapResultCode field
skipping to change at page 22, line 48 skipping to change at page 23, line 16
FEDFS_ERR_NOTJUNCT FEDFS_ERR_NOTJUNCT
FEDFS_ERR_NOTLOCAL FEDFS_ERR_NOTLOCAL
FEDFS_ERR_PERM FEDFS_ERR_PERM
FEDFS_ERR_SVRFAULT FEDFS_ERR_SVRFAULT
FEDFS_ERR_NSDB_ROUTE FEDFS_ERR_NSDB_ROUTE
FEDFS_ERR_NSDB_DOWN FEDFS_ERR_NSDB_DOWN
FEDFS_ERR_NSDB_CONN FEDFS_ERR_NSDB_CONN
FEDFS_ERR_NSDB_AUTH FEDFS_ERR_NSDB_AUTH
FEDFS_ERR_NSDB_LDAP FEDFS_ERR_NSDB_LDAP
FEDFS_ERR_NSDB_LDAP_VAL FEDFS_ERR_NSDB_LDAP_VAL
FEDFS_ERR_NSDB_NONCE
FEDFS_ERR_NSDB_NOFSN FEDFS_ERR_NSDB_NOFSN
FEDFS_ERR_NSDB_NOFSL FEDFS_ERR_NSDB_NOFSL
FEDFS_ERR_NSDB_RESPONSE FEDFS_ERR_NSDB_RESPONSE
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
skipping to change at page 23, line 35 skipping to change at page 23, line 50
5.5.2. Description 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. Setting
the replication FSN on a fileset that already has a replication FSN
set is allowed.
This operation differs from FEDFS_CREATE_JUNCTION in that it controls This operation differs from FEDFS_CREATE_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,
but MAY return FEDFS_ERR_ROFS if this is not possible. but MAY return FEDFS_ERR_ROFS if this is not possible.
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 24, line 15 skipping to change at page 24, line 32
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.
The same FSN value SHOULD be associated with all replicas of a
filesystem. Depending on the underlying representation, the FSN
associated with a filesystem may or may not be replicated
automatically with the filesystem replication mechanism. Therefore
if FEDFS_CREATE_REPLICATION is used on one replica of a filesystem,
it SHOULD be used on all replicas.
5.5.3. Errors 5.5.3. Errors
FEDFS_ERR_ACCESS FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME FEDFS_ERR_BADNAME
FEDFS_ERR_NAMETOOLONG FEDFS_ERR_NAMETOOLONG
FEDFS_ERR_LOOP FEDFS_ERR_LOOP
FEDFS_ERR_BADXDR FEDFS_ERR_BADXDR
FEDFS_ERR_EXIST FEDFS_ERR_EXIST
FEDFS_ERR_INVAL FEDFS_ERR_INVAL
skipping to change at page 26, line 46 skipping to change at page 27, line 26
FEDFS_ERR_NOTJUNCT FEDFS_ERR_NOTJUNCT
FEDFS_ERR_NOTLOCAL FEDFS_ERR_NOTLOCAL
FEDFS_ERR_PERM FEDFS_ERR_PERM
FEDFS_ERR_SVRFAULT FEDFS_ERR_SVRFAULT
FEDFS_ERR_NSDB_ROUTE FEDFS_ERR_NSDB_ROUTE
FEDFS_ERR_NSDB_DOWN FEDFS_ERR_NSDB_DOWN
FEDFS_ERR_NSDB_CONN FEDFS_ERR_NSDB_CONN
FEDFS_ERR_NSDB_AUTH FEDFS_ERR_NSDB_AUTH
FEDFS_ERR_NSDB_LDAP FEDFS_ERR_NSDB_LDAP
FEDFS_ERR_NSDB_LDAP_VAL FEDFS_ERR_NSDB_LDAP_VAL
FEDFS_ERR_NSDB_NONCE
FEDFS_ERR_NSDB_NOFSN FEDFS_ERR_NSDB_NOFSN
FEDFS_ERR_NSDB_NOFSL FEDFS_ERR_NSDB_NOFSL
FEDFS_ERR_NSDB_RESPONSE FEDFS_ERR_NSDB_RESPONSE
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
skipping to change at page 30, line 40 skipping to change at page 31, line 24
RPCSEC_GSS. RPCSEC_GSS.
7. 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 with
short name "fedfs_admin".
8. 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
 End of changes. 25 change blocks. 
50 lines changed or deleted 70 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/