draft-ietf-nfsv4-federated-fs-admin-14.txt   draft-ietf-nfsv4-federated-fs-admin-15.txt 
NFSv4 Working Group J. Lentini NFSv4 Working Group J. Lentini
Internet-Draft NetApp Internet-Draft NetApp
Intended status: Standards Track D. Ellard Intended status: Standards Track D. Ellard
Expires: May 14, 2013 Raytheon BBN Technologies Expires: June 15, 2013 Raytheon BBN Technologies
R. Tewari R. Tewari
IBM Almaden IBM Almaden
C. Lever, Ed. C. Lever, Ed.
Oracle Corporation Oracle Corporation
November 10, 2012 December 12, 2012
Administration Protocol for Federated Filesystems Administration Protocol for Federated Filesystems
draft-ietf-nfsv4-federated-fs-admin-14 draft-ietf-nfsv4-federated-fs-admin-15
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 May 14, 2013. This Internet-Draft will expire on June 15, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 29 skipping to change at page 3, line 29
5.2.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 19 5.2.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 19
5.2.2. Description . . . . . . . . . . . . . . . . . . . . . 19 5.2.2. Description . . . . . . . . . . . . . . . . . . . . . 19
5.2.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 21 5.2.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3. FEDFS_DELETE_JUNCTION . . . . . . . . . . . . . . . . . . 21 5.3. FEDFS_DELETE_JUNCTION . . . . . . . . . . . . . . . . . . 21
5.3.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 21 5.3.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 21
5.3.2. Description . . . . . . . . . . . . . . . . . . . . . 21 5.3.2. Description . . . . . . . . . . . . . . . . . . . . . 21
5.3.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 22 5.3.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4. FEDFS_LOOKUP_JUNCTION . . . . . . . . . . . . . . . . . . 23 5.4. FEDFS_LOOKUP_JUNCTION . . . . . . . . . . . . . . . . . . 23
5.4.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 23 5.4.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 23
5.4.2. Description . . . . . . . . . . . . . . . . . . . . . 23 5.4.2. Description . . . . . . . . . . . . . . . . . . . . . 23
5.4.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 25 5.4.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 26
5.5. FEDFS_CREATE_REPLICATION . . . . . . . . . . . . . . . . . 26 5.5. FEDFS_CREATE_REPLICATION . . . . . . . . . . . . . . . . . 26
5.5.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 26 5.5.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 26
5.5.2. Description . . . . . . . . . . . . . . . . . . . . . 26 5.5.2. Description . . . . . . . . . . . . . . . . . . . . . 26
5.5.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 27 5.5.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 27
5.6. FEDFS_DELETE_REPLICATION . . . . . . . . . . . . . . . . . 28 5.6. FEDFS_DELETE_REPLICATION . . . . . . . . . . . . . . . . . 28
5.6.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 28 5.6.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 28
5.6.2. Description . . . . . . . . . . . . . . . . . . . . . 28 5.6.2. Description . . . . . . . . . . . . . . . . . . . . . 28
5.6.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 29 5.6.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 29
5.7. FEDFS_LOOKUP_REPLICATION . . . . . . . . . . . . . . . . . 29 5.7. FEDFS_LOOKUP_REPLICATION . . . . . . . . . . . . . . . . . 29
5.7.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 29 5.7.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 29
5.7.2. Description . . . . . . . . . . . . . . . . . . . . . 29 5.7.2. Description . . . . . . . . . . . . . . . . . . . . . 29
5.7.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 30 5.7.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 30
5.8. FEDFS_SET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 30 5.8. FEDFS_SET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 31
5.8.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 30 5.8.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 31
5.8.2. Description . . . . . . . . . . . . . . . . . . . . . 31 5.8.2. Description . . . . . . . . . . . . . . . . . . . . . 31
5.8.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 31 5.8.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 31
5.9. FEDFS_GET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 32 5.9. FEDFS_GET_NSDB_PARAMS . . . . . . . . . . . . . . . . . . 32
5.9.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 32 5.9.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 32
5.9.2. Description . . . . . . . . . . . . . . . . . . . . . 32 5.9.2. Description . . . . . . . . . . . . . . . . . . . . . 32
5.9.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 32 5.9.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 32
5.10. FEDFS_GET_LIMITED_NSDB_PARAMS . . . . . . . . . . . . . . 32 5.10. FEDFS_GET_LIMITED_NSDB_PARAMS . . . . . . . . . . . . . . 33
5.10.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 33 5.10.1. Synopsis . . . . . . . . . . . . . . . . . . . . . . . 33
5.10.2. Description . . . . . . . . . . . . . . . . . . . . . 33 5.10.2. Description . . . . . . . . . . . . . . . . . . . . . 33
5.10.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 33 5.10.3. Errors . . . . . . . . . . . . . . . . . . . . . . . . 34
6. Security Considerations . . . . . . . . . . . . . . . . . . . 34 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1. Normative References . . . . . . . . . . . . . . . . . . . 35 8.1. Normative References . . . . . . . . . . . . . . . . . . . 35
8.2. Informative References . . . . . . . . . . . . . . . . . . 35 8.2. Informative References . . . . . . . . . . . . . . . . . . 36
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 36 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 36
Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 37 Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37
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.
skipping to change at page 5, line 43 skipping to change at page 5, line 43
configure the fileservers and construct the namespace. configure the fileservers and construct the namespace.
1.1. Definitions 1.1. Definitions
Administrator: A user with the necessary authority to initiate Administrator: A 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 fileserver data using a supported File-access Client: Standard off-the-shelf network attached storage
file-access protocol. (NAS) client software that communicates with fileservers using a
standard file-access protocol.
Federation: A set of server collections and singleton servers that Federation: A set of fileserver collections and singleton
use a common set of interfaces and protocols in order to provide fileservers that use a common set of interfaces and protocols in
to their clients a federated namespace accessible through a order to provide to file-access clients a federated namespace
filesystem access protocol. accessible through a filesystem access protocol.
Fileserver: A server exporting one or more filesystems via a file- Fileserver: A server that stores physical fileset data, or refers
access protocol. file-access clients to other fileservers. A fileserver provides
access to its shared filesystem data via a file-access protocol.
Fileset: The abstraction of a set of files and the directory tree Fileset: The abstraction of a set of files and the directory tree
that contains them. A fileset is the fundamental unit of data that contains them. A fileset is the fundamental unit of data
management in the federation. management in the federation.
Note that all files within a fileset are descendants of one Note that all files within a fileset are descendants of one
directory, and that filesets do not span filesystems. directory, and that filesets do not span filesystems.
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. file-access protocol and the fileserver permit this.
File-access Protocol: A network filesystem access protocol such as File-access Protocol: A network filesystem access protocol such as
NFSv3 [RFC1813], NFSv4 [3530bis], or CIFS (Common Internet File NFSv3 [RFC1813], NFSv4 [3530bis], or CIFS (Common Internet File
System) [MS-SMB] [MS-SMB2] [MS-CIFS]. 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 resource that a file-access client can access directly, such as an
fs_locations attribute (for NFSv4), or a share name (for CIFS). fs_locations attribute (for NFSv4), or a share name (for CIFS).
FSN (Fileset Name): A platform-independent and globally unique name FSN (Fileset Name): A platform-independent and globally unique name
for a fileset. Two FSLs that implement replicas of the same for a fileset. Two FSLs that implement replicas of the same
fileset MUST have the same FSN, and if a fileset is migrated from fileset MUST have the same FSN, and if a fileset is migrated from
one location to another, the FSN of that fileset MUST remain the one location to another, the FSN of that fileset MUST remain the
same. same.
Junction: A filesystem object used to link a directory name in the Junction: A filesystem object used to link a directory name in the
current fileset with an object within another fileset. The current fileset with an object within another fileset. The
server-side "link" from a leaf node in one fileset to the root of server-side "link" from a leaf node in one fileset to the root of
another fileset. another fileset.
Namespace: A filename/directory tree that a sufficiently authorized Namespace: A filename/directory tree that a sufficiently authorized
client can observe. file-access client can observe.
NSDB (Namespace Database) Service: A service that maps FSNs to FSLs. NSDB (Namespace Database) Service: A service that maps FSNs to FSLs.
The NSDB may also be used to store other information, such as The NSDB may also be used to store other information, such as
annotations for these mappings and their components. annotations for these mappings and their components.
NSDB Node: The name or location of a server that implements part of NSDB Node: The name or location of a server that implements part of
the NSDB service and is responsible for keeping track of the FSLs the NSDB service and is responsible for keeping track of the FSLs
(and related info) that implement a given partition of the FSNs. (and related info) that implement a given partition of the FSNs.
Referral: A server response to a client access that directs the Referral: A server response to a file-access client access that
client to evaluate the current object as a reference to an object directs the client to evaluate the current object as a reference
at a different location (specified by an FSL) in another fileset, to an object at a different location (specified by an FSL) in
and possibly hosted on another fileserver. The client re-attempts another fileset, and possibly hosted on another fileserver. The
the access to the object at the new location. client re-attempts the access to the object at the new location.
Replica: A replica is a redundant implementation of a fileset. Each Replica: A replica is a redundant implementation of a fileset. Each
replica shares the same FSN, but has a different FSL. replica shares the same FSN, but has a different FSL.
Replicas may be used to increase availability or performance. Replicas may be used to increase availability or performance.
Updates to replicas of the same fileset MUST appear to occur in Updates to replicas of the same fileset MUST appear to occur in
the same order, and therefore each replica is self-consistent at the same order, and therefore each replica is self-consistent at
any moment. any moment.
We do not assume that updates to each replica occur We do not assume that updates to each replica occur
skipping to change at page 15, line 16 skipping to change at page 15, line 16
connection with the NSDB. connection with the NSDB.
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 an ADMIN protocol client.
FEDFS_ERR_NSDB_NONCE: The fileserver was unable to locate the NCE in FEDFS_ERR_NSDB_NONCE: The fileserver was unable to locate the NCE in
the appropriate NSDB. 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.
skipping to change at page 15, line 42 skipping to change at page 15, line 42
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.
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL: Indicates the same error as FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL: Indicates the same error as
FEDFS_ERR_NSDB_LDAP_REFERRAL, and allows the LDAP protocol error FEDFS_ERR_NSDB_LDAP_REFERRAL, and allows the LDAP protocol error
value to be returned back to the client. value to be returned back to an ADMIN protocol client.
FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED: The fileserver received an FEDFS_ERR_NSDB_LDAP_REFERRAL_NOTFOLLOWED: The fileserver received an
LDAP referral that it chose not to follow, either because the LDAP referral that it chose not to follow, either because the
fileserver does not support following LDAP referrals or LDAP fileserver does not support following LDAP referrals or LDAP
referral following is disabled. referral following is disabled.
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL: The fileserver received an LDAP FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL: The fileserver received an LDAP
referral that it chose not to follow because the fileserver had no referral that it chose not to follow because the fileserver had no
NSDB parameters for the NSDB targeted by the LDAP referral. 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 FEDFS_ERR_NOTSUPP: The fileserver does not support the specified
procedure. procedure.
FEDFS_ERR_DELAY: The fileserver initiated the request, but was not FEDFS_ERR_DELAY: The fileserver initiated the request, but was not
able to complete it in a timely fashion. The client should wait able to complete it in a timely fashion. The ADMIN protocol
and then try the request with a new RPC transaction ID. 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 FEDFS_ERR_NO_CACHE: The fileserver does not implement an FSN-to-FSL
cache. cache.
FEDFS_ERR_UNKNOWN_CACHE: The software receiving the ONC RPC request FEDFS_ERR_UNKNOWN_CACHE: The software receiving the ONC RPC request
is unaware if the fileserver implements an FSN-to-FSL cache or is unaware if the fileserver implements an FSN-to-FSL cache or
unable to communicate with the FSN-to-FSL cache if it exists. unable to communicate with the FSN-to-FSL cache if it exists.
FEDFS_ERR_NO_CACHE_UPDATE: The fileserver was unable to update its FEDFS_ERR_NO_CACHE_UPDATE: The fileserver was unable to update its
FSN-to-FSL cache. FSN-to-FSL cache.
4. Data Types 4. Data Types
The basic data types defined above MUST be formatted as follows: The basic data types defined above are 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 4 UUID. The UUID should be formatted in [RFC4122] as a version 4 UUID. The UUID MUST 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. It SHOULD be NSDB's network location in DNS name notation. It SHOULD be
prepared using the server4 rules defined in Chapter 12 prepared using the server4 rules defined in Chapter 12
"Internationalization" of [3530bis]. The DNS name MUST be "Internationalization" of [3530bis]. The DNS name MUST be
represented using a fully qualified domain name. A system (i.e., represented using a fully qualified domain name.
fileserver or administrative host) SHOULD resolve the fully
qualified domain name to a network address using the system's
standard resolution mechanisms.
The port value in the FedFsNsdbName indicates the LDAP port on the The port value in the FedFsNsdbName indicates the LDAP port on the
NSDB (see [RFC4511]). The value MUST be in the range 0 to 65535. NSDB (see [RFC4511]). The value MUST be in the range 0 to 65535.
A value of 0 indicates that the standard LDAP port number, 389, A value of 0 indicates that the standard LDAP port number, 389,
SHOULD be assumed. MUST 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 MUST 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. It SHOULD be prepared using the filesystem path component. It MUST be prepared using the
component4 rules defined in Chapter 12 "Internationalization" of component4 rules defined in Chapter 12 "Internationalization" of
[3530bis]. [3530bis].
FedFsPathName: A variable length array of FedFsPathComponent values FedFsPathName: A variable length array of FedFsPathComponent values
representing a filesystem path. The path's first component is representing a filesystem path. The path's first component is
stored at the first position of the array, the second component is stored at the first position of the array, the second component is
stored at the second position of the array, and so on. stored at the second position of the array, and so on.
The path "/" MUST be encoded as an array with zero components. The path "/" MUST be encoded as an array with zero components.
skipping to change at page 17, line 41 skipping to change at page 17, line 39
FedFsNsdbParams: A set of parameters for connecting to an NSDB. FedFsNsdbParams: A set of parameters for connecting to an NSDB.
Conceptually the fileserver contains a data structure that maps an Conceptually the fileserver contains a data structure that maps an
NSDB name (DNS name and port value) to these LDAP connection NSDB name (DNS name and port value) to these LDAP connection
parameters. parameters.
The secType field indicates the security mechanism that MUST be The secType field indicates the security mechanism that MUST be
used to protect all connections to the NSDB with the connection used to protect all connections to the NSDB with the connection
parameters. parameters.
A value of FEDFS_SEC_NONE indicates that no security mechanism is A value of FEDFS_SEC_NONE indicates that a transport security
necessary. In this case, the secData array will have 0 length. mechanism MUST NOT be used when connecting to the NSDB. In this
case, the secData array will have a length of zero.
A value of FEDFS_SEC_TLS indicates that the StartTLS security A value of FEDFS_SEC_TLS indicates that the StartTLS security
mechanism [RFC4513] MUST be used to protect all connections to the mechanism [RFC4513] MUST be used to protect all connections to the
NSDB. In this case, the secData array will contain an X.509v3 NSDB. In this case, the secData array will contain an X.509v3
root certificate in binary DER format [RFC5280] fulfilling the TLS root certificate in binary DER format [RFC5280] fulfilling the TLS
requirement that root keys be distributed independently from the requirement that root keys be distributed independently from the
TLS protocol. The certificate MUST be used by the fileserver as a TLS protocol. The certificate MUST be used by the fileserver as a
Trust Anchor to validate the NSDB's TLS server certificate list Trust Anchor to validate the NSDB's TLS server certificate list
chain (see section 7.4.2 of [RFC5246]) and thus authenticate the chain (see section 7.4.2 of [RFC5246]) and thus authenticate the
identitiy of the NSDB. The certificate could be that of a identitiy of the NSDB. The certificate could be that of a
certificate authority or a self-signed certificate. certificate authority or a self-signed certificate. To ensure
that this security configuration information does not cause
vulnerabilities for other services, trust anchors provided through
secData MUST only be used for the NSDB service (as opposed to
being installed as system-wide trust anchors for other services).
Most popular TLS libraries provide ways in which this can be done
such as denoting a private file system location for the
certificates.
4.1. FedFsNsdbName Equality 4.1. FedFsNsdbName Equality
Two FedFsNsdbNames are considered equal if both their DNS name and Two FedFsNsdbNames are considered equal if their respective hostname
port values are the same. As described above, the standard LDAP port and port fields contain the same values. The only exception to this
number, 389, SHOULD be assumed if a port number of 0 is specified. rule is that a value of 0 in the port field always matches the
standard LDAP port number, 389.
Therefore, the FedFsNsdbName "(nsdb.example.com, 0)" is considered Therefore, the FedFsNsdbName "(nsdb.example.com, 0)" is considered
equal to "(nsdb.example.com, 389)" but not equal to 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 numbers are different, or
"(nsdb.foo.example.com, 389)" since the DNS name is different. "(nsdb.foo.example.com, 389)" since the hostnames are 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 the following procedures: namespace MUST implement the following procedures:
FEDFS_NULL FEDFS_NULL
skipping to change at page 19, line 40 skipping to change at page 19, line 48
pathname) to an FSN. pathname) to an FSN.
5.2.2. Description 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 file-access client). This path does not appear in the
namespace, except by coincidence; there is no requirement that the federated namespace, except by coincidence; there is no requirement
global namespace parallel the server namespace, nor is it required that the global namespace parallel the server namespace, nor is it
that this path be relative to the server pseudo-root. It does not required that this path be relative to the server pseudo-root. It
need to be a path that is accessible via NFS (although the junction does not need to be a path that is accessible via NFS (although the
will be of limited utility if the directory specified by the path is junction will be of limited utility if the directory specified by the
not also accessible via NFS). path is not also accessible via NFS).
If the fileset is read-only, then this operation MUST indicate this If the fileset is read-only, then this operation MUST indicate this
with a status of FEDFS_ERR_ROFS. with a status of FEDFS_ERR_ROFS.
If the path contains a character that is not supported by the server, If the path contains a character that is not supported by the server,
then status FEDFS_ERR_BADCHAR MUST be returned. then status 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_EXIST (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 might contain a symbolic link (if supported by the local path might contain a symbolic link (if supported by the local
server), but the traversal of the path MUST remain within the server- server), but the traversal of the path MUST remain within the server-
local namespace. local 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 MUST
with status FEDFS_ERR_INVAL. fail 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
the final component. If a server wishes to report that a path cannot the final component. If a server wishes to report that a path cannot
be traversed because of insufficient permissions, or the final be traversed because of insufficient permissions, or the final
component is an unexecutable or unwritable directory, then the component is an unexecutable or unwritable directory, then the
operation MUST fail with status FEDFS_ERR_ACCESS. operation MUST fail with status 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, or the server may allow the operation to proceed
using some set of default NSDB connection parameters.
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 returns successfully. If the operation return codes the operation returns successfully. If the operation return codes
indicates success, then the junction was successfully created and is indicates success, then the junction was successfully created and is
immediately accessible. immediately accessible.
If successful, subsequent references via NFSv4 [3530bis] or NFSv4.1 If successful, subsequent references via NFSv4.0 [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].
The effective permissions of the directory that is converted, by this The effective permissions of the directory that is converted, by this
operation, into a junction are the permissions of the root directory operation, into a junction are the permissions of the root directory
of the target fileset. The original permissions of the directory of the target fileset. The original permissions of the directory
(and any other attributes it might have) are subsumed by the (and any other attributes it might have) are subsumed by the
junction. junction.
skipping to change at page 21, line 40 skipping to change at page 21, line 46
as a pathname). as a pathname).
5.3.2. Description 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 file-access client). This
not appear in the federated namespace, except by coincidence; there path does not appear in the federated namespace, except by
is no requirement that the global namespace reflect the server coincidence; there is no requirement that the global namespace
namespace, nor is it required that this path be relative to the reflect the server namespace, nor is it required that this path be
server pseudo-root. It does not need to be a path that is accessible relative to the server pseudo-root. It does not need to be a path
via NFS. that is accessible via NFS.
If the fileset is read-only, then this operation SHOULD indicate this If the fileset is read-only, then this operation MUST indicate this
with a status of FEDFS_ERR_ROFS. with a status of FEDFS_ERR_ROFS.
If the path contains a character that is not supported by the server, If the path contains a character that is not supported by the server,
then status FEDFS_ERR_BADCHAR MUST be returned. then status FEDFS_ERR_BADCHAR MUST be returned.
The path used to delete a junction might not be the same path that The path used to delete a junction might not be the same path that
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 might now appear at a different path than changed, then the junction might 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 can be used. junction, any of them can be used.
skipping to change at page 23, line 33 skipping to change at page 23, line 39
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
array of one or more UTF-8 path component strings. It is not array of one or more UTF-8 path component strings. It is not
required that this path be accessible in any other manner (e.g., to a required that this path be accessible in any other manner (e.g., to a
client). This path does not appear in the federated namespace, file-access client). This path does not appear in the federated
except by coincidence; there is no requirement that the global namespace, except by coincidence; there is no requirement that the
namespace reflect the server namespace, nor is it required that this global namespace reflect the server namespace, nor is it required
path be relative to the server pseudo-root. It does not need to be a that this path be relative to the server pseudo-root. It does not
path that is accessible via NFS. need to be a path that is accessible via NFS.
If the path contains a character that is not supported by the server, If the path contains a character that is not supported by the server,
then status FEDFS_ERR_BADCHAR MUST be returned. then status FEDFS_ERR_BADCHAR MUST be returned.
The path used to lookup a junction might not be the same path that The path used to lookup a junction might not be the same path that
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 a junction might now appear at a different path than changed, then a junction might 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 might be used. junction, any of them might be used.
skipping to change at page 24, line 50 skipping to change at page 25, line 8
cached information. The resolution MAY fail with cached information. The resolution MAY fail with
FEDFS_ERR_NSDB_ROUTE, FEDFS_ERR_NSDB_DOWN, FEDFS_ERR_NSDB_CONN, FEDFS_ERR_NSDB_ROUTE, FEDFS_ERR_NSDB_DOWN, FEDFS_ERR_NSDB_CONN,
FEDFS_ERR_NSDB_AUTH, FEDFS_ERR_NSDB_LDAP, FEDFS_ERR_NSDB_LDAP_VAL, FEDFS_ERR_NSDB_AUTH, FEDFS_ERR_NSDB_LDAP, FEDFS_ERR_NSDB_LDAP_VAL,
FEDFS_ERR_NSDB_NOFSN, FEDFS_ERR_NSDB_NOFSL, FEDFS_ERR_NSDB_NONCE, FEDFS_ERR_NSDB_NOFSN, FEDFS_ERR_NSDB_NOFSL, FEDFS_ERR_NSDB_NONCE,
FEDFS_ERR_NSDB_RESPONSE, FEDFS_ERR_NSDB_FAULT, FEDFS_ERR_NSDB_RESPONSE, FEDFS_ERR_NSDB_FAULT,
FEDFS_ERR_NSDB_LDAP_REFERRAL, 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 MUST 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
(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 If the NSDB responds with an LDAP referral, either the Referral type
defined in Section 4.1.10 of [RFC4511] or the SearchResultReference defined in Section 4.1.10 of [RFC4511] or the SearchResultReference
type defined in Section 4.5.3 of [RFC4511], the fileserver SHOULD type defined in Section 4.5.3 of [RFC4511], the fileserver SHOULD
process the LDAP referral using the same policies as the fileserver's process the LDAP referral using the same policies as the fileserver's
file-access protocol server. The fileserver can indicate a failure file-access protocol server. The fileserver MUST indicate a failure
while processing the LDAP referral using while processing the LDAP referral using
FEDFS_ERR_NSDB_LDAP_REFERRAL, 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. The FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL. The
FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL is analogous to the FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL is analogous to the
FEDFS_ERR_NSDB_LDAP_VAL error and allows the LDAP protocol error FEDFS_ERR_NSDB_LDAP_VAL error and allows the LDAP protocol error
value to be returned in the FedFsLookupResReferralVal's value to be returned in the FedFsLookupResReferralVal's
ldapResultCode field. The FEDFS_ERR_NSDB_LDAP_REFERRAL and ldapResultCode field. The FEDFS_ERR_NSDB_LDAP_REFERRAL and
FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL errors errors allow the NSDB FEDFS_ERR_NSDB_PARAMS_LDAP_REFERRAL errors errors allow the NSDB
targeted by the LDAP referral to be returned in the FedFsLookupRes's targeted by the LDAP referral to be returned in the FedFsLookupRes's
targetNsdb field. Similarly, the FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL targetNsdb field. Similarly, the FEDFS_ERR_NSDB_LDAP_REFERRAL_VAL
error includes this information in the FedFsLookupResReferralVal's error includes this information in the FedFsLookupResReferralVal's
targetNsdb. 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. A failure to update the cache can be indicated with the updated. A failure to update the cache MAY be indicated with the
FEDFS_ERR_NO_CACHE_UPDATE status value. When updating the cache, new FEDFS_ERR_NO_CACHE_UPDATE status value, or the operation may complete
FSLs for the given FSN SHOULD be added to the cache and deleted FSLs successfully.
SHOULD be removed from the cache. This behavior is desirable because
it allows an administrator to proactively request that the fileserver When updating the cache, new FSLs for the given FSN SHOULD be added
refresh its FSL cache. For example, the administrator might like to to the cache and deleted FSLs SHOULD be removed from the cache. This
refresh the fileserver's cache when changes are made to an FSN's behavior is desirable because it allows an administrator to
FSLs. proactively request that the fileserver 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 include a list of If the junction is resolved, the fileserver will include a list of
UUIDs for the FSN's FSLs in the FedFsLookupResOk structure's fsl UUIDs for the FSN's FSLs in the FedFsLookupResOk structure's fsl
array. array.
5.4.3. Errors 5.4.3. Errors
FEDFS_ERR_ACCESS FEDFS_ERR_ACCESS
FEDFS_ERR_BADCHAR FEDFS_ERR_BADCHAR
FEDFS_ERR_BADNAME FEDFS_ERR_BADNAME
skipping to change at page 26, line 45 skipping to change at page 26, line 52
5.5. FEDFS_CREATE_REPLICATION 5.5. FEDFS_CREATE_REPLICATION
5.5.1. Synopsis 5.5.1. Synopsis
Set an FSN representing the replication information for the fileset Set an FSN representing the replication information for the fileset
containing the pathname. containing the pathname.
5.5.2. Description 5.5.2. Description
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 might request for a particular fileset. An NFSv4 client might request fs_locations
fs_locations or fs_locations_info at any time to detect other copies or fs_locations_info at any time to detect other copies of this
of this fileset, and this operation supports this by supplying the fileset, and this operation supports this by supplying the FSN the
FSN the fileserver should use to respond. This FSN should be fileserver should use to respond. This FSN should be associated with
associated with the entire fileset in which the path resides, and the entire fileset in which the path resides, and should be used to
should be used to satisfy fs_locations or fs_locations_info attribute satisfy fs_locations or fs_locations_info attribute requests whenever
requests whenever no junction is being accessed; if a junction is no junction is being accessed; if a junction is being accessed, the
being accessed, the FSN specified by FEDFS_CREATE_JUNCTION will take FSN specified by FEDFS_CREATE_JUNCTION will take precedence. Setting
precedence. Setting the replication FSN on a fileset that already the replication FSN on a fileset that already has a replication FSN
has a replication FSN set is allowed. 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 MUST return FEDFS_ERR_ROFS if this is not possible. but MUST return FEDFS_ERR_ROFS if this is not possible.
If the path contains a character that is not supported by the server, If the path contains a character that is not supported by the server,
then status FEDFS_ERR_BADCHAR MUST be returned. then status FEDFS_ERR_BADCHAR MUST be returned.
skipping to change at page 27, line 32 skipping to change at page 27, line 38
remain within the server-local namespace. remain within the server-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 a server wishes to report that a path cannot the final component. If a server wishes to report that a path cannot
be traversed because of insufficient permissions, or the final be traversed because of insufficient permissions, or the final
component is an unexecutable or unwritable directory, then the component is an unexecutable or unwritable directory, then the
operation MUST fail with status FEDFS_ERR_ACCESS. operation MUST fail with status 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, or the server may allow the operation to proceed
using some set of default NSDB connection parameters.
The same FSN value SHOULD be associated with all replicas of a The same FSN value SHOULD be associated with all replicas of a
filesystem. Depending on the underlying representation, the FSN filesystem. Depending on the underlying representation, the FSN
associated with a filesystem might or might not be replicated associated with a filesystem might or might not be replicated
automatically with the filesystem replication mechanism. Therefore automatically with the filesystem replication mechanism. Therefore
if FEDFS_CREATE_REPLICATION is used on one replica of a filesystem, if FEDFS_CREATE_REPLICATION is used on one replica of a filesystem,
it SHOULD be used on all replicas. 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
FEDFS_ERR_IO FEDFS_ERR_IO
FEDFS_ERR_NOSPC FEDFS_ERR_NOSPC
skipping to change at page 28, line 25 skipping to change at page 28, line 32
5.6. FEDFS_DELETE_REPLICATION 5.6. FEDFS_DELETE_REPLICATION
5.6.1. Synopsis 5.6.1. Synopsis
Remove the replication information for the fileset containing the Remove the replication information for the fileset containing the
pathname. pathname.
5.6.2. Description 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 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,
but MUST return FEDFS_ERR_ROFS if this is not possible. but MUST return FEDFS_ERR_ROFS if this is not possible.
If the path contains a character that is not supported by the server, If the path contains a character that is not supported by the server,
skipping to change at page 34, line 16 skipping to change at page 34, line 20
FEDFS_ERR_BADXDR FEDFS_ERR_BADXDR
FEDFS_ERR_INVAL FEDFS_ERR_INVAL
FEDFS_ERR_IO FEDFS_ERR_IO
FEDFS_ERR_SVRFAULT FEDFS_ERR_SVRFAULT
FEDFS_ERR_NSDB_PARAMS FEDFS_ERR_NSDB_PARAMS
FEDFS_ERR_NOTSUPP FEDFS_ERR_NOTSUPP
FEDFS_ERR_DELAY FEDFS_ERR_DELAY
6. Security Considerations 6. Security Considerations
The ONC RPC protocol supports authentication, integrity and privacy The Security Considerations of [RFC5531] apply to the protocol
via the RPCSEC_GSS framework [RFC2203]. Fileservers which support described in this document. The ONC RPC protocol supports
the FedFS administration protocol described above MUST support authentication, integrity and privacy via the RPCSEC_GSS framework
RPCSEC_GSS. When RPCSEC_GSS is employed, RPCSEC_GSS data integrity [RFC2203]. Fileservers which support the FedFS administration
SHOULD be used. protocol described above MUST support RPCSEC_GSS.
As with NFSv4.1 (see Section 2.2.1.1.1.1 of [RFC5661]), FedFS
administration protocol clients and servers MUST support RPCSEC_GSS's
integrity and authentication services. FedFS administration protocol
servers MUST support RPCSEC_GSS's privacy service. FedFS
administration protocol clients SHOULD support RPCSEC_GSS's privacy
service. When RPCSEC_GSS is employed on behalf of the FedFS
administration protocol, RPCSEC_GSS data integrity SHOULD be used.
It is strongly RECOMMENDED that an Access Control Service be employed It is strongly RECOMMENDED that an Access Control Service be employed
to restrict access to a fileserver's FedFS administration to restrict access to a fileserver's FedFS administration
configuration data via the FedFS administrative protocol to prevent configuration data via the FedFS administrative protocol to prevent
FedFS namespace corruption, and protect NSDB communication FedFS namespace corruption, and protect NSDB communication
parameters. parameters.
For example, when the FedFsNsdbParams secType field value For example, when the FedFsNsdbParams secType field value
FEDFS_SEC_TLS is chosen, the payload is used to provision the trust FEDFS_SEC_TLS is chosen, the payload is used to provision the trust
anchor root certificate for TLS secure communication between the anchor root certificate for TLS secure communication between the
skipping to change at page 36, line 32 skipping to change at page 36, line 44
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.
Naik, "Requirements for Federated File Systems", RFC 5716, Naik, "Requirements for Federated File Systems", RFC 5716,
January 2010. January 2010.
Appendix A. Acknowledgments Appendix A. Acknowledgments
We would like to thank Robert Thurlow for helping to author this The authors and editor would like to thank Craig Everhart and Manoj
document, including drafting the replication procedure text. Naik, who were co-authors of an earlier version of this document. In
addition, we would like to thank Paul Lemahieu, Mario Wurzl, and
We would like to thank Craig Everhart and Manoj Naik, who were co- Robert Thurlow for helping to author this document.
authors of an earlier version of this document.
We would also like to thank Paul Lemahieu and Mario Wurzl for helping We would like to thank Trond Myklebust for suggesting improvements to
to author this document. the FSL pathname format, David Noveck for his suggestions on
internationalization and path encoding rules, and Nicolas Williams
for his suggestions.
We would also like to thank Trond Myklebust for suggesting The editor gratefully acknowledges the IESG reviewers, whose
improvements to the FSL pathname format, Chuck Lever for suggesting constructive comments helped make this a much stronger document.
improvements to the XDR type definitions and error codes, David
Noveck for his suggestions on internationalization and path encoding
rules, and Nicolas Williams for his suggestions.
Finally, we would also like to thank Andy Adamson, Rob Thurlow, Tom Finally, we would like to thank Andy Adamson, Rob Thurlow, and Tom
Haynes, and Chuck Lever for the editing effort to get this document Haynes for helping to get this document out the door.
out the door.
The extract.sh shell script and formatting conventions were first The extract.sh shell script and formatting conventions were first
described by the authors of the NFSv4.1 XDR specification [RFC5662]. described by the authors of the NFSv4.1 XDR specification [RFC5662].
Appendix B. RFC Editor Notes Appendix B. RFC Editor Notes
[RFC Editor: please remove this section prior to publishing this [RFC Editor: please remove this section prior to publishing this
document as an RFC] document as an RFC]
[RFC Editor: prior to publishing this document as an RFC, please [RFC Editor: prior to publishing this document as an RFC, please
 End of changes. 49 change blocks. 
114 lines changed or deleted 132 lines changed or added

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