draft-ietf-nfsv4-federated-fs-protocol-10.txt   draft-ietf-nfsv4-federated-fs-protocol-11.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: May 23, 2011 D. Ellard Expires: September 12, 2011 D. Ellard
Raytheon BBN Technologies Raytheon BBN Technologies
R. Tewari R. Tewari
M. Naik M. Naik
IBM Almaden IBM Almaden
November 19, 2010 March 11, 2011
NSDB Protocol for Federated Filesystems NSDB Protocol for Federated Filesystems
draft-ietf-nfsv4-federated-fs-protocol-10 draft-ietf-nfsv4-federated-fs-protocol-11
Abstract Abstract
This document describes a filesystem federation protocol that enables This document describes a filesystem federation protocol that enables
file access and namespace traversal across collections of file access and namespace traversal across collections of
independently administered fileservers. The protocol specifies a set independently administered fileservers. The protocol specifies a set
of interfaces by which fileservers with different administrators can of interfaces by which fileservers with different administrators can
form a fileserver federation that provides a namespace composed of form a fileserver federation that provides a namespace composed of
the filesystems physically hosted on and exported by the constituent the filesystems physically hosted on and exported by the constituent
fileservers. 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 23, 2011. This Internet-Draft will expire on September 12, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 47 skipping to change at page 3, line 47
5.1.2. Delete an FSN . . . . . . . . . . . . . . . . . . . . 43 5.1.2. Delete an FSN . . . . . . . . . . . . . . . . . . . . 43
5.1.3. Create an FSL . . . . . . . . . . . . . . . . . . . . 43 5.1.3. Create an FSL . . . . . . . . . . . . . . . . . . . . 43
5.1.4. Delete an FSL . . . . . . . . . . . . . . . . . . . . 47 5.1.4. Delete an FSL . . . . . . . . . . . . . . . . . . . . 47
5.1.5. Update an FSL . . . . . . . . . . . . . . . . . . . . 47 5.1.5. Update an FSL . . . . . . . . . . . . . . . . . . . . 47
5.2. NSDB Operations for Fileservers . . . . . . . . . . . . . 48 5.2. NSDB Operations for Fileservers . . . . . . . . . . . . . 48
5.2.1. NSDB Container Entry (NCE) Enumeration . . . . . . . . 48 5.2.1. NSDB Container Entry (NCE) Enumeration . . . . . . . . 48
5.2.2. Lookup FSLs for an FSN . . . . . . . . . . . . . . . . 48 5.2.2. Lookup FSLs for an FSN . . . . . . . . . . . . . . . . 48
5.3. NSDB Operations and LDAP Referrals . . . . . . . . . . . . 50 5.3. NSDB Operations and LDAP Referrals . . . . . . . . . . . . 50
6. Security Considerations . . . . . . . . . . . . . . . . . . . 50 6. Security Considerations . . . . . . . . . . . . . . . . . . . 50
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51
7.1. LDAP Descriptor Registration . . . . . . . . . . . . . . . 51 7.1. Registry for the fedfsAnnotation Key Namespace . . . . . . 51
8. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 7.2. Registry for FedFS Object Identifiers . . . . . . . . . . 51
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57 7.3. LDAP Descriptor Registration . . . . . . . . . . . . . . . 54
9.1. Normative References . . . . . . . . . . . . . . . . . . . 57 8. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
9.2. Informative References . . . . . . . . . . . . . . . . . . 59 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 60 9.1. Normative References . . . . . . . . . . . . . . . . . . . 59
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 60 9.2. Informative References . . . . . . . . . . . . . . . . . . 61
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 62
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 62
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 or across multiple enterprises. fileservers within an enterprise or across multiple enterprises.
This document specifies a set of protocols that allow fileservers, This document specifies a set of protocols that allow fileservers,
possibly from different vendors and with different administrators, to possibly from different vendors and with different administrators, to
cooperatively form a federation containing one or more federated cooperatively form a federation containing one or more federated
skipping to change at page 26, line 5 skipping to change at page 26, line 5
+-----------------+-------------+ +-----------------+-------------+
| escape sequence | replacement | | escape sequence | replacement |
+-----------------+-------------+ +-----------------+-------------+
| \\ | \ | | \\ | \ |
| \" | " | | \" | " |
+-----------------+-------------+ +-----------------+-------------+
A fedfsAnnotation value SHOULD be processed as follows: A fedfsAnnotation value SHOULD be processed as follows:
1. Scan through the attribute value and replace the above escape 1. Parse the attribute value according to the ANNOTATION rule,
sequences. ignoring the escape sequences above.
2. Parse the results of the previous step according to the 2. Scan through results of the previous step and replace the escape
ANNOTATION rule. sequences above.
A fedfsAnnotation attribute that does not adhere to this format A fedfsAnnotation attribute that does not adhere to this format
SHOULD be ignored. SHOULD be ignored.
The following are examples of valid fedfsAnnotation attributes: The following are examples of valid fedfsAnnotation attributes:
"key1" = "foo" "key1" = "foo"
"another key" = "x=3" "another key" = "x=3"
"key-2" = "A string with \" and \\ characters." "key-2" = "A string with \" and \\ characters."
skipping to change at page 51, line 33 skipping to change at page 51, line 33
It should be noted that the federation protocols do not directly It should be noted that the federation protocols do not directly
provide access to filesystem data. The federation protocols only provide access to filesystem data. The federation protocols only
provide a mechanism for building a namespace. All data transfers provide a mechanism for building a namespace. All data transfers
occur between a client and server just as they would if the occur between a client and server just as they would if the
federation protocols were not in use. As a result, the federation federation protocols were not in use. As a result, the federation
protocols do not require new user authentication and authorization protocols do not require new user authentication and authorization
mechanisms or require a fileserver to act as a proxy for a client. mechanisms or require a fileserver to act as a proxy for a client.
7. IANA Considerations 7. IANA Considerations
7.1. Registry for the fedfsAnnotation Key Namespace
This document defines the fedfsAnnotation key in Section 4.2.1.12.
The fedfsAnnotation key namespace is to be managed by IANA. IANA is
to create and maintain a new registry entitled "FedFS Annotation
Keys". Future registrations are to be administered by IANA using the
"First Come First Served" policy defined in [RFC5226]. Registration
requests MUST include the key (a valid UTF-8 string of any length), a
brief description of the key's purpose, and an email contact for the
registration. For viewing, the registry should be sorted
lexicographically by key. There are no initial assignments for this
registry.
7.2. Registry for FedFS Object Identifiers
Using the process described in [RFC2578], one of the authors was Using the process described in [RFC2578], one of the authors was
assigned the Internet Private Enterprise Numbers range assigned the Internet Private Enterprise Numbers range
1.3.6.1.4.1.31103.x. Within this range, the subrange 1.3.6.1.4.1.31103.x. Within this range, the subrange
1.3.6.1.4.1.31103.1.x is permanently dedicated for use by the 1.3.6.1.4.1.31103.1.x is permanently dedicated for use by the
federated file system protocols. All of the LDAP attributes and federated file system protocols.
object classes defined in this document are assigned object
identifier (OID) values within the range 1.3.6.1.4.1.31103.1.x. IANA is to create and maintain a new registry entitled "FedFS Object
Identifiers" for the purpose of administering the FedFS Object
Identifier (OID) range. Future allocations from the
1.3.6.1.4.1.31103.1.x range are to be assigned by IANA using the "RFC
Required" policy defined in [RFC5226]. Registration requests MUST
include an OID value from the 1.3.6.1.4.1.31103.1.x range, a short
description of the OID, and a reference to the specification that
defines the OID's usage. For viewing, the registry should be sorted
numerically by OID value. The initial contents of the FedFS Object
Identifiers registry are given in Table 1.
+--------------------------+-------------------------+-----------+
| OID | Description | Reference |
+--------------------------+-------------------------+-----------+
| 1.3.6.1.4.1.31103.1.1 | fedfsUuid | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.2 | fedfsNetAddr | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.3 | fedfsNetPort | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.4 | fedfsFsnUuid | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.5 | fedfsNsdbName | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.6 | fedfsNsdbPort | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.7 | fedfsNcePrefix | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.8 | fedfsFslUuid | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.9 | fedfsFslHost | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.10 | fedfsFslPort | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.11 | fedfsFslTTL | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.12 | fedfsAnnotation | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.13 | fedfsDescr | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.100 | fedfsNfsPath | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.101 | fedfsNfsMajorVer | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.102 | fedfsNfsMinorVer | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.103 | fedfsNfsCurrency | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.104 | fedfsNfsGenFlagWritable | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.105 | fedfsNfsGenFlagGoing | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.106 | fedfsNfsGenFlagSplit | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.107 | fedfsNfsTransFlagRdma | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.108 | fedfsNfsClassSimul | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.109 | fedfsNfsClassHandle | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.110 | fedfsNfsClassFileid | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.111 | fedfsNfsClassWritever | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.112 | fedfsNfsClassChange | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.113 | fedfsNfsClassReaddir | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.114 | fedfsNfsReadRank | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.115 | fedfsNfsReadOrder | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.116 | fedfsNfsWriteRank | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.117 | fedfsNfsWriteOrder | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.118 | fedfsNfsVarSub | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.119 | fedfsNfsValidFor | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.1001 | fedfsNsdbContainerInfo | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.1002 | fedfsFsn | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.1003 | fedfsFsl | RFC-TBD1 |
| 1.3.6.1.4.1.31103.1.1004 | fedfsNfsFsl | RFC-TBD1 |
+--------------------------+-------------------------+-----------+
Table 1
7.3. LDAP Descriptor Registration
In accordance with Section 3.4 and Section 4 of [RFC4520], the object In accordance with Section 3.4 and Section 4 of [RFC4520], the object
identifier descriptors defined in this document (listed below) will identifier descriptors defined in this document (listed below) will
be registered via the Expert Review process. be registered via the Expert Review process.
7.1. LDAP Descriptor Registration
Subject: Request for LDAP Descriptor Registration Subject: Request for LDAP Descriptor Registration
Person & email address to contact for further information: See Person & email address to contact for further information: See
"Author/Change Controller" "Author/Change Controller"
Specification: draft-ietf-nfsv4-federated-fs-protocol Specification: draft-ietf-nfsv4-federated-fs-protocol
Author/Change Controller: [document authors] Author/Change Controller: [document authors]
Object Identifier: 1.3.6.1.4.1.31103.1.1 Object Identifier: 1.3.6.1.4.1.31103.1.1
Descriptor (short name): fedfsUuid Descriptor (short name): fedfsUuid
Usage: attribute type Usage: attribute type
skipping to change at page 58, line 43 skipping to change at page 61, line 5
Syntaxes and Matching Rules", RFC 4517, June 2006. Syntaxes and Matching Rules", RFC 4517, June 2006.
[RFC4519] Sciberras, A., "Lightweight Directory Access Protocol [RFC4519] Sciberras, A., "Lightweight Directory Access Protocol
(LDAP): Schema for User Applications", RFC 4519, (LDAP): Schema for User Applications", RFC 4519,
June 2006. June 2006.
[RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority (IANA) [RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority (IANA)
Considerations for the Lightweight Directory Access Considerations for the Lightweight Directory Access
Protocol (LDAP)", BCP 64, RFC 4520, June 2006. Protocol (LDAP)", BCP 64, RFC 4520, June 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[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.
 End of changes. 12 change blocks. 
20 lines changed or deleted 95 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/