idnits 2.17.1 draft-ietf-nfsv4-federated-fs-protocol-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 13, 2010) is 4997 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '0' on line 1460 -- Looks like a reference, but probably isn't: '255' on line 1460 ** Obsolete normative reference: RFC 3530 (Obsoleted by RFC 7530) ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Obsolete normative reference: RFC 5661 (Obsoleted by RFC 8881) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NFSv4 Working Group J. Lentini 3 Internet-Draft C. Everhart 4 Intended status: Standards Track NetApp 5 Expires: February 14, 2011 D. Ellard 6 Raytheon BBN Technologies 7 R. Tewari 8 M. Naik 9 IBM Almaden 10 August 13, 2010 12 NSDB Protocol for Federated Filesystems 13 draft-ietf-nfsv4-federated-fs-protocol-07 15 Abstract 17 This document describes a filesystem federation protocol that enables 18 file access and namespace traversal across collections of 19 independently administered fileservers. The protocol specifies a set 20 of interfaces by which fileservers with different administrators can 21 form a fileserver federation that provides a namespace composed of 22 the filesystems physically hosted on and exported by the constituent 23 fileservers. 25 Requirements Language 27 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 28 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 29 document are to be interpreted as described in [RFC2119]. 31 Status of this Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on February 14, 2011. 48 Copyright Notice 49 Copyright (c) 2010 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 This document may contain material from IETF Documents or IETF 63 Contributions published or made publicly available before November 64 10, 2008. The person(s) controlling the copyright in some of this 65 material may not have granted the IETF Trust the right to allow 66 modifications of such material outside the IETF Standards Process. 67 Without obtaining an adequate license from the person(s) controlling 68 the copyright in such materials, this document may not be modified 69 outside the IETF Standards Process, and derivative works of it may 70 not be created outside the IETF Standards Process, except to format 71 it for publication as an RFC or to translate it into languages other 72 than English. 74 Table of Contents 76 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 77 2. Overview of Features and Concepts . . . . . . . . . . . . . . 5 78 2.1. Namespace . . . . . . . . . . . . . . . . . . . . . . . . 5 79 2.2. Fileset . . . . . . . . . . . . . . . . . . . . . . . . . 5 80 2.3. Fileset Name (FSN) . . . . . . . . . . . . . . . . . . . . 5 81 2.4. Fileset Location (FSL) . . . . . . . . . . . . . . . . . . 6 82 2.4.1. Mutual Consistency across Fileset Locations . . . . . 6 83 2.4.2. Caching of Fileset Locations . . . . . . . . . . . . . 7 84 2.4.3. Generating A Referral from Fileset Locations . . . . . 8 85 2.5. Namespace Database (NSDB) . . . . . . . . . . . . . . . . 9 86 2.6. Mount Points, Junctions and Referrals . . . . . . . . . . 9 87 2.7. Unified Namespace and the Root Fileset . . . . . . . . . . 10 88 2.8. Fileservers . . . . . . . . . . . . . . . . . . . . . . . 10 89 2.9. File-access Clients . . . . . . . . . . . . . . . . . . . 10 90 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 91 3.1. Creating a Fileset and its FSL(s) . . . . . . . . . . . . 11 92 3.1.1. Creating a Fileset and an FSN . . . . . . . . . . . . 11 93 3.1.2. Adding a Replica of a Fileset . . . . . . . . . . . . 12 94 3.2. Junction Resolution . . . . . . . . . . . . . . . . . . . 12 95 3.3. Example Use Cases for Fileset Annotations . . . . . . . . 13 96 4. NSDB Configuration and Schema . . . . . . . . . . . . . . . . 13 97 4.1. LDAP Configuration . . . . . . . . . . . . . . . . . . . . 14 98 4.2. LDAP Schema . . . . . . . . . . . . . . . . . . . . . . . 15 99 4.2.1. LDAP Attributes . . . . . . . . . . . . . . . . . . . 16 100 4.2.2. LDAP Objects . . . . . . . . . . . . . . . . . . . . . 34 101 5. NSDB Operations . . . . . . . . . . . . . . . . . . . . . . . 37 102 5.1. NSDB Operations for Administrators . . . . . . . . . . . . 38 103 5.1.1. Create an FSN . . . . . . . . . . . . . . . . . . . . 39 104 5.1.2. Delete an FSN . . . . . . . . . . . . . . . . . . . . 40 105 5.1.3. Create an FSL . . . . . . . . . . . . . . . . . . . . 40 106 5.1.4. Delete an FSL . . . . . . . . . . . . . . . . . . . . 43 107 5.1.5. Update an FSL . . . . . . . . . . . . . . . . . . . . 43 108 5.2. NSDB Operations for Fileservers . . . . . . . . . . . . . 44 109 5.2.1. NSDB Container Entry (NCE) Enumeration . . . . . . . . 44 110 5.2.2. Lookup FSLs for an FSN . . . . . . . . . . . . . . . . 44 111 6. Security Considerations . . . . . . . . . . . . . . . . . . . 46 112 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 113 7.1. LDAP Descriptor Registration . . . . . . . . . . . . . . . 47 114 8. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 115 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 52 116 9.1. Normative References . . . . . . . . . . . . . . . . . . . 52 117 9.2. Informative References . . . . . . . . . . . . . . . . . . 54 118 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 55 119 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 55 121 1. Introduction 123 A federated filesystem enables file access and namespace traversal in 124 a uniform, secure and consistent manner across multiple independent 125 fileservers within an enterprise or across multiple enterprises. 127 This document specifies a set of protocols that allow fileservers, 128 possibly from different vendors and with different administrators, to 129 cooperatively form a federation containing one or more federated 130 filesystems. Each federated filesystem's namespace is composed of 131 the filesystems physically hosted on and exported by the federation's 132 fileservers. A federation MAY contain a common namespace across all 133 its fileservers. A federation MAY project multiple namespaces and 134 enable clients to traverse each one. A federation MAY contain an 135 arbitrary number of namespace repositories, each belonging to a 136 different administrative entity, and each rendering a part of the 137 namespace. A federation MAY also have an arbitrary number of 138 administrative entities responsible for administering disjoint 139 subsets of the fileservers. 141 Traditionally, building a namespace that spans multiple fileservers 142 has been difficult for two reasons. First, the fileservers that 143 export pieces of the namespace are often not in the same 144 administrative domain. Second, there is no standard mechanism for 145 the fileservers to cooperatively present the namespace. Fileservers 146 may provide proprietary management tools and in some cases an 147 administrator may be able to use the proprietary tools to build a 148 shared namespace out of the exported filesystems. However, relying 149 on vendor-specific proprietary tools does not work in larger 150 enterprises or when collaborating across enterprises because the 151 fileservers are likely to be from multiple vendors or use different 152 software versions, each with their own namespace protocols, with no 153 common mechanism to manage the namespace or exchange namespace 154 information. 156 The federated filesystem protocols in this document define how to 157 construct a namespace accessible by an NFSv4 [RFC3530] or NFSv4.1 158 [RFC5661] client and have been designed to accommodate other file 159 access protocols in the future. 161 The requirements for federated filesystems are described in 162 [RFC5716]. A protocol for administering a fileserver's namespace is 163 described in [FEDFS-ADMIN]. The mechanism for discovering the root 164 of an NFSv4 namespace is described in [FEDFS-DNS-SRV]. In the rest 165 of the document, the term fileserver denotes a fileserver that is 166 part of a federation. 168 2. Overview of Features and Concepts 170 2.1. Namespace 172 The goal of a unified namespace is to make all managed data available 173 to all clients via the same path in a common filesystem-like 174 namespace. This should be achieved with minimal or zero client 175 configuration. In particular, updates to the common namespace should 176 not require configuration changes at the client. Filesets, which are 177 the unit of data management, are a set of files and directories. 178 From the perspective of the clients, the common namespace is 179 constructed by mounting filesets that are physically located on 180 different fileservers. The namespace, which is defined in terms of 181 fileset definitions, fileset identifiers, the location of each 182 fileset in the namespace, and the physical location of the 183 implementation(s) of each fileset, is stored in a set of namespace 184 repositories, each managed by an administrative entity. The 185 namespace schema defines the model used for populating, modifying, 186 and querying the namespace repositories. It is not required by the 187 federation that the namespace be common across all fileservers. It 188 should be possible to have several independently rooted namespaces. 190 2.2. Fileset 192 A fileset is defined to be a container of data and is the basic unit 193 of data management. Depending on the configuration, they may be 194 anything between an individual directory of an exported filesystem to 195 an entire exported filesystem at a fileserver. 197 2.3. Fileset Name (FSN) 199 A fileset is uniquely represented by its fileset name (FSN). An FSN 200 is considered unique across the federation. After an FSN is created, 201 it is associated with one or more fileset locations (FSLs) on a 202 fileserver. 204 The attributes of an FSN are: 206 NsdbName: the network location of the NSDB node that contains 207 authoritative information for this FSN. 209 FsnUuid: a 128-bit UUID (universally unique identifier), 210 conforming to [RFC4122], that is used to uniquely identify an 211 FSN. 213 2.4. Fileset Location (FSL) 215 An FSL describes the location where the fileset data resides. An FSL 216 contains generic and type specific information which together 217 describe how to access the fileset. An FSL's type indicates which 218 protocol(s) may be used to access its data. An FSL's attributes can 219 be used by a fileserver to decide which locations it will return to a 220 client. 222 All FSLs have the following attributes: 224 FslUuid: a 128-bit UUID, conforming to [RFC4122], that is used to 225 uniquely identify an FSL. 227 FsnUuid: the 128-bit UUID of the FSL's FSN. 229 NsdbName: the network location of the NSDB node that contains 230 authoritative information for this FSL. 232 FslHost: the network location of the host fileserver storing the 233 physical data 235 FslTTL: the time in seconds during which the FSL may be cached 237 Annotations: optional name/value pairs that can be interpreted by 238 a fileserver. The semantics of this field are not defined by 239 this document. These tuples are intended to be used by higher- 240 level protocols. 242 Descriptions: optional text descriptions. The semantics of this 243 field are not defined by this document. 245 This document defines an FSL subtype for NFS. An NFS FSL contains 246 information suitable for use in an NFSv4 fs_locations [RFC3530] or 247 NFSv4.1 fs_locations_info attribute [RFC5661]. 249 A fileset MAY be accessible by protocols other than NFS. For each 250 such protocol, a corresponding FSL subtype SHOULD be defined. The 251 contents and format of such FSL subtypes are not defined in this 252 document. 254 2.4.1. Mutual Consistency across Fileset Locations 256 All of the FSLs that have the same FSN (and thereby reference the 257 same fileset) are equivalent from the point of view of client access; 258 the different locations of a fileset represent the same data, though 259 potentially at different points in time. Fileset locations are 260 equivalent but not identical. Locations may either be read-only or 261 read-write. Typically, multiple read-write locations are backed by a 262 clustered filesystem while read-only locations are replicas created 263 by a federation-initiated or external replication operation. Read- 264 only locations may represent consistent point-in-time copies of a 265 read-write location. The federation protocols, however, cannot 266 prevent subsequent changes to a read-only location nor guarantee 267 point-in-time consistency of a read-only location if the read-write 268 location is changing. 270 Regardless of the type, all locations exist at the same mount point 271 in the namespace and, thus, one client may be referred to one 272 location while another is directed to a different location. Since 273 updates to each fileset location are not controlled by the federation 274 protocol, it is the responsibility of administrators to guarantee the 275 functional equivalence of the data. 277 The federation protocol does not guarantee that the different 278 locations are mutually consistent in terms of the currency of the 279 data. It relies on the client file-access protocol (e.g., NFSv4) to 280 contain sufficient information to help the clients determine the 281 currency of the data at each location in order to ensure that the 282 clients do not revert back in time when switching locations. 284 2.4.2. Caching of Fileset Locations 286 To resolve an FSN to a set of FSL records, the fileserver queries the 287 appropriate NSDB for the FSL records. A fileserver MAY cache these 288 FSL records for a limited period of time. The period of time, if 289 any, during which FSL records MAY be cached is indicated by the FSL's 290 TTL field. 292 The combination of FSL caching and FSL migration presents a 293 challenge. For example, suppose there are three fileservers named A, 294 B, and C and fileserver A contains a junction to fileset X stored on 295 fileserver B. Now suppose that fileset X is migrated from fileserver 296 B to fileserver C and the corresponding FSL information for fileset X 297 in the appropriate NSDB is updated. If fileserver A has a cached FSL 298 for fileset X, a user traversing the junction on fileserver A will be 299 referred to fileserver B even though fileset X has migrated to 300 fileserver C. If fileserver A had not cached the FSL record, it would 301 have queried the NSDB and obtained the correct location of fileset X. 303 Administrators are advised to be aware of FSL caching when performing 304 a migration. When migrating a fileset, administrators SHOULD create 305 a junction at the fileset's old location referring back to the NSDB 306 entry for the fileset. This junction will redirect any users who 307 follow stale FSL information to the correct location. Thus, in the 308 above example, fileserver A would direct clients to fileserver B, but 309 fileserver B would in turn direct clients to fileserver C. 311 Such supplemental junctions (on fileserver B in the example) would 312 not be required to be in place forever. They need to stay in place 313 only until cached FSL entries for the target fileset are invalidated. 314 Each FSL contains a TTL field, a count in seconds of the time 315 interval the FSL MAY be cached. This is an upper bound for the 316 lifetime of the cached information and a lower bound for the lifetime 317 of the supplemental junctions. For example, suppose this field 318 contains the value 3600 seconds (one hour). In such a case, 319 administrators MUST keep the supplemental junctions in place for at 320 least one hour after the fileset move has taken place, and FSL data 321 MUST NOT be cached by a referring fileserver for more than one hour 322 without a refresh. 324 2.4.3. Generating A Referral from Fileset Locations 326 After resolving an FSN to a set of FSL records, the fileserver can 327 generate a referral to redirect the client to one or more of the 328 FSLs. The fileserver will convert the FSL records to a referral 329 format understood by the client, such as an NFSv4 fs_locations 330 attribute or NFSv4.1 fs_locations_info attribute. 332 In order to give the client as many options as possible, the 333 fileserver SHOULD include the maximum possible number of FSL records 334 in a referral. However, the fileserver MAY omit some of the FSL 335 records from the referral. For example, the fileserver might omit an 336 FSL record with a different file access protocol from the one in use 337 between the fileserver and client, or the fileserver might omit an 338 FSL record because of limitations in the file access protocol's 339 referral format, or the fileserver might omit an FSL record based on 340 some other criteria. 342 For a given FSL record, the fileserver MAY convert or reduce the FSL 343 record's contents in a manner appropriate to the referral format. 344 For example, an NFS FSL record contains all the data necessary to 345 construct an NFSv4.1 fs_locations_info attribute, but an NFSv4.1 346 fs_locations_info attribute contains several pieces of information 347 that are not found in an NFSv4 fs_locations attribute. A fileserver 348 will construct entries in an NFSv4 fs_locations attribute using the 349 relevant contents of an NFS FSL record. Whenever the fileserver 350 converts or reduces FSL data, the fileserver SHOULD attempt to 351 maintain the original meaning where possible. For example, an NFS 352 FSL record contains the rank and order information that is included 353 in an NFSv4.1 fs_locations_info attribute (see NFSv4.1's 354 FSLI4BX_READRANK, FSLI4BX_READORDER, FSLI4BX_WRITERANK, and 355 FSLI4BX_WRITEORDER). While this rank and order information is not 356 explicitly expressible in an NFSv4 fs_locations attribute, the 357 fileserver can arrange the NFSv4 fs_locations attribute's locations 358 list base on the rank and order values. 360 2.5. Namespace Database (NSDB) 362 The NSDB service is a federation-wide service that provides 363 interfaces to define, update, and query FSN information, FSL 364 information, and FSN to FSL mapping information. An individual 365 repository of namespace information is called an NSDB node. Each 366 NSDB node is managed by a single administrative entity. A single 367 admin entity can manage multiple NSDB nodes. 369 The difference between the NSDB service and an NSDB node is analogous 370 to that between the DNS service and a particular DNS server. 372 Each NSDB node stores the definition of the FSNs for which it is 373 authoritative. It also stores the definitions of the FSLs associated 374 with those FSNs. An NSDB node is authoritative for the filesets that 375 it defines. An NSDB node can cache information from a peer NSDB 376 node. The fileserver can always contact a local NSDB node (if it has 377 been defined) or directly contact any NSDB node to resolve a 378 junction. Each NSDB node supports an LDAP [RFC4510] interface and 379 can be accessed by an LDAP client. 381 An NSDB MAY be replicated throughout the federation. If an NSDB is 382 replicated, the NSDB MUST exhibit loose, converging consistency as 383 defined in [RFC3254]. The mechanism by which this is achieved is 384 outside the scope of this document. Many LDAP implementations 385 support replication. These features MAY be used to replicate the 386 NSDB. 388 2.6. Mount Points, Junctions and Referrals 390 A mount point is a directory in a parent fileset where a target 391 fileset may be attached. If a client traverses the path leading from 392 the root of the namespace to the mount point of a target fileset it 393 should be able to access the data in that target fileset (assuming 394 appropriate permissions). 396 The directory where a fileset is mounted is represented by a junction 397 in the underlying filesystem. In other words, a junction can be 398 viewed as a reference from a directory in one fileset to the root of 399 the target fileset. A junction can be implemented as a special 400 marker on a directory that is interpreted by the fileserver as a 401 mount point, or by some other mechanism in the underlying filesystem. 403 What data is used by the underlying filesystem to represent the 404 junction is not defined by this protocol. The essential property is 405 that the server must be able to find, given the junction, the FSN for 406 the target fileset. The mechanism by which the server maps a 407 junction to an FSN is outside the scope of this document. The FSN 408 (as described earlier) contains the authoritative NSDB node, the 409 optional NSDB search base if one is defined, and the FsnUuid (a UUID 410 for the fileset). 412 When a client traversal reaches a junction, the client is referred to 413 a list of FSLs associated with the FSN targeted by the junction. The 414 client can then redirect its connection to one of the FSLs. This act 415 is called a referral. For NFSv4 and NFSv4.1 clients, the FSL 416 information is returned in the fs_locations and fs_locations_info 417 attributes respectively. 419 The federation protocols do not limit where and how many times a 420 fileset is mounted in the namespace. Filesets can be nested; a 421 fileset can be mounted under another fileset. 423 2.7. Unified Namespace and the Root Fileset 425 The root fileset, when defined, is the top-level fileset of the 426 federation-wide namespace. The root of the unified namespace is the 427 top level directory of this fileset. A set of designated fileservers 428 in the federation can export the root fileset to render the 429 federation-wide unified namespace. When a client mounts the root 430 fileset from any of these designated fileservers it can view a common 431 federation-wide namespace. The root fileset could be implemented 432 either as an exported NFS file system or as data in the NSDB itself. 433 The properties and schema definition of an NSDB-based root fileset 434 and the protocol details that describe how to configure and replicate 435 the root fileset are not defined in this document. 437 2.8. Fileservers 439 Fileservers are servers that store the physical fileset data or refer 440 the client to other fileservers. A fileserver can be implemented in 441 a number of different ways, including a single system, a cluster of 442 systems, or some other configuration. A fileserver provides access 443 to a federated filesystem via NFSv4, NFSv4.1, or some other protocol. 445 2.9. File-access Clients 447 File access clients are standard off-the-shelf network attached 448 storage (NAS) clients that access file data using the NFSv4 protocol, 449 the NFSv4.1 protocol, or some other protocol. 451 3. Examples 453 In this section we provide examples and discussion of the basic 454 operations facilitated by the federated filesystem protocol: creating 455 a fileset, adding a replica of a fileset, resolving a junction, and 456 creating a junction. 458 3.1. Creating a Fileset and its FSL(s) 460 A fileset is the abstraction of a set of files and the directory tree 461 that contains them. The fileset abstraction is the fundamental unit 462 of data management in the federation. This abstraction is 463 implemented by an actual directory tree whose root location is 464 specified by a fileset location (FSL). 466 In this section, we describe the basic requirements for starting with 467 a directory tree and creating a fileset that can be used in the 468 federation protocols. Note that we do not assume that the process of 469 creating a fileset requires any transformation of the files or the 470 directory hierarchy. The only thing that is required by this process 471 is assigning the fileset a fileset name (FSN) and expressing the 472 location of the implementation of the fileset as an FSL. 474 There are many possible variations to this procedure, depending on 475 how the FSN that binds the FSL is created, and whether other replicas 476 of the fileset exist, are known to the federation, and need to be 477 bound to the same FSN. 479 It is easiest to describe this in terms of how to create the initial 480 implementation of the fileset, and then describe how to add replicas. 482 3.1.1. Creating a Fileset and an FSN 484 1. Choose the NSDB node that will keep track of the FSL(s) and 485 related information for the fileset. 487 2. Create an FSN in the NSDB node. 489 The FSN UUID is chosen by the administrator or generated 490 automatically by administration software. The former case is 491 used if the fileset is being restored, perhaps as part of 492 disaster recovery, and the administrator wishes to specify the 493 FSN UUID in order to permit existing junctions that reference 494 that FSN to work again. 496 At this point, the FSN exists, but its fileset locations are 497 unspecified. 499 3. For the FSN created above, create an FSL with the appropriate 500 information in the NSDB node. 502 3.1.2. Adding a Replica of a Fileset 504 Adding a replica is straightforward: the NSDB node and the FSN are 505 already known. The only remaining step is to add another FSL. 507 Note that the federation protocols only provide the mechanisms to 508 register and unregister replicas of a fileset. Fileserver-to- 509 fileserver replication protocols are not defined. 511 3.2. Junction Resolution 513 A fileset may contain references to other filesets. These references 514 are represented by junctions. If a client requests access to a 515 fileset object that is a junction, the fileserver resolves the 516 junction to discover one or more FSLs that implement the referenced 517 fileset. 519 There are many possible variations to this procedure, depending on 520 how the junctions are represented by the fileserver and how the 521 fileserver performs junction resolution. 523 Step 4 is the only step that interacts directly with the federation 524 protocols. The rest of the steps may use platform-specific 525 interfaces. 527 1. The fileserver determines that the object being accessed is a 528 junction. 530 2. The fileserver does a local lookup to find the FSN of the target 531 fileset. 533 3. Using the FSN, the fileserver finds the NSDB node responsible for 534 the target FSN. 536 4. The fileserver contacts that NSDB node and asks for the set of 537 FSLs that implement the target FSN. The NSDB node responds with 538 a (possibly empty) set of FSLs. 540 5. The fileserver converts one or more of the FSLs to the location 541 type used by the client (e.g., a Network File System (NFSv4) 542 fs_location, as described in [RFC3530]). 544 6. The fileserver redirects (in whatever manner is appropriate for 545 the client) the client to the location(s). 547 3.3. Example Use Cases for Fileset Annotations 549 Fileset annotations MAY be used to convey additional attributes of a 550 fileset 552 For example, fileset annotations can be used to define relationships 553 between filesets that can be used by an auxiliary replication 554 protocol. Consider the scenario where a fileset is created and 555 mounted at some point in the namespace. A snapshot of the read-write 556 FSL of that fileset is taken periodically at different frequencies 557 say a daily snapshot or a weekly snapshot. The different snapshots 558 are mounted at different locations in the namespace. The daily 559 snapshots are considered as a different fileset from the weekly ones 560 but both are related to the source fileset. For this we can define 561 an annotation labeling the filesets as source and replica. The 562 replication protocol can use this information to copy data from one 563 or more FSLs of the source fileset to all the FSLs of the replica 564 fileset. The replica filesets are read-only while the source fileset 565 is read-write. 567 This follows the traditional Andrew File System (AFS) model of 568 mounting the read-only volume at a path in the namespace different 569 from that of the read-write volume [AFS]. 571 The federation protocol does not control or manage the relationship 572 among filesets. It merely enables annotating the filesets with user- 573 defined relationships. 575 Another potential use for annotations is recording references to an 576 FSN. A single annotation containing the number of references could 577 be defined or multiple annotations, one per reference, could be used 578 to store detailed information on the location of each reference. As 579 with the replication annotation described above, the maintenance of 580 reference information would not be controlled by the federation 581 protocol. The information would mostly likely be non-authoritative 582 because the the ability to create a junction does not require the 583 authority to update the FSN record. In any event, such annotations 584 could be useful to administrators for determining if an FSN is 585 referenced by a junction. 587 4. NSDB Configuration and Schema 589 This section describes how an NSDB is constructed using an LDAP 590 Version 3 [RFC4510] Directory. Section 4.1 describes the basic 591 properties of the LDAP configuration that MUST be used in order to 592 ensure compatibility between different implementations. Section 4.2 593 defines the new LDAP attribute types, the new object types, and 594 specifies how the distinguished name (DN) of each object instance 595 MUST be constructed. 597 4.1. LDAP Configuration 599 An NSDB is constructed using an LDAP Directory. This LDAP Directory 600 MAY have multiple naming contexts. For each naming context, the LDAP 601 Directory's root DSE will have a namingContext attribute. Each 602 namingContext attribute contains the DN of the naming context's root 603 entry. For each naming context that contains federation entries 604 (e.g. FSNs and FSLs): 606 1. There MUST be an LDAP entry that is superior to all of the naming 607 context's federation entries in the Directory Information Tree 608 (DIT) This entry is termed the NSDB Container Entry (NCE). The 609 NCE's children are FSNs. An FSNs children are FSLs. 611 2. The naming context's root entry MUST include the 612 fedfsNsdbContainerInfo (defined below) as one of its object 613 classes. The fedfsNsdbContainerInfo's fedfsNcePrefix attribute 614 is used to locate the naming context's NCE. 616 If a naming context does not contain federation entries, it will not 617 contain an NCE and its root entry will not include a 618 fedfsNsdbContainerInfo as one of its object classes. 620 A fedfsNsdbContainerInfo's fedfsNcePrefix attribute contains a 621 string. Prepending this string to the namingContext value produces 622 the Distinguished Name (DN) of the NSDB Container Entry. An empty 623 fedfsNcePrefix string value indicates that the NSDB Container Entry 624 is the namingContext's root entry. 626 For example, an LDAP directory might have the following entries: 628 -+ [root DSE] 629 | namingContext: o=fedfs 630 | namingContext: dc=example,dc=com 631 | namingContext: ou=system 632 | 633 | 634 +---- [o=fedfs] 635 | fedfsNcePrefix: 636 | 637 | 638 +---- [dc=example,dc=com] 639 | fedfsNcePrefix: ou=fedfs,ou=corp-it 640 | 641 | 642 +---- [ou=system] 644 In this case, the o=fedfs namingContext has an NSBD Container Entry 645 at o=fedfs, the dc=example,dc=com namingContext has an NSDB Container 646 Entry at ou=fedfs,ou=corp-it,dc=example,dc=com, and the ou=system 647 namingContext has no NSDB Container Entry. 649 The NSDB SHOULD be configured with one or more privileged LDAP users. 650 These users are able to modify the contents of the LDAP database. An 651 administrator that performs the operations described in Section 5.1 652 SHOULD authenticate using the DN of a privileged LDAP user. 654 It MUST be possible for an unprivileged (unauthenticated) user to 655 perform LDAP queries that access the NSDB data. A fileserver 656 performs the operations described in Section 5.2 as an unprivileged 657 user. 659 All implementations SHOULD use the same schema, or, at minimum, a 660 schema that includes all of the objects, with each of the attributes, 661 named in the following sections. 663 Given the above configuration guidelines, an NSDB SHOULD be 664 constructed using a dedicated LDAP directory. Separate LDAP 665 directories are RECOMMENDED for other purposes, such as storing user 666 account information. By using an LDAP directory dedicated to storing 667 NSDB records, there is no need to disturb the configuration of any 668 other LDAP directories that store information unrelated to an NSDB. 670 4.2. LDAP Schema 672 The schema definitions provided in this document use the LDAP schema 673 syntax defined in [RFC4512]. The definitions are formatted to allow 674 the reader to easily extract them from the document. The reader can 675 use the following shell script to extract the definitions: 677 679 #!/bin/sh 680 grep '^ *///' | sed 's?^ */// ??' | sed 's?^ *///$??' 682 684 If the above script is stored in a file called "extract.sh", and this 685 document is in a file called "spec.txt", then the reader can do: 687 689 sh extract.sh < spec.txt > fedfs.schema 691 693 The effect of the script is to remove leading white space from each 694 line, plus a sentinel sequence of "///". 696 4.2.1. LDAP Attributes 698 This section describes the required attributes of the NSDB LDAP 699 schema. The following definitions are used below: 701 o The "name" attribute described in [RFC4519]. 703 o The Integer syntax (1.3.6.1.4.1.1466.115.121.1.27) described in 704 [RFC4517]. 706 o The "integerMatch" rule described in [RFC4517]. 708 o The Octet String syntax (1.3.6.1.4.1.1466.115.121.1.40) described 709 in [RFC4517]. 711 o The "octetStringMatch" rule described in [RFC4517]. 713 o The Boolean syntax (1.3.6.1.4.1.1466.115.121.1.7) described in 714 [RFC4517]. 716 o The "booleanMatch" rule described in [RFC4517]. 718 o The "distinguishedNameMatch" rule described in [RFC4517]. 720 o The DN syntax (1.3.6.1.4.1.1466.115.121.1.12) described in 721 [RFC4517]. 723 4.2.1.1. fedfsUuid 725 A fedfsUuid is the base type for all of the universally unique 726 identifiers (UUIDs) used by the federated filesystem protocols. 728 To minimize the probability of two UUIDs colliding, a consistent 729 procedure for generating UUIDs SHOULD be used throughout a 730 federation. Within a federation, UUIDs SHOULD be generated using the 731 procedure described for version 1 of the UUID variant specified in 732 [RFC4122]. 734 The UUID's text representation (as defined in [RFC4122]) SHOULD be 735 encoded as a UTF-8 string. 737 It MAY also be useful, for purposes of debugging or annotation, to 738 permit a fedfsUuid to include members of a more general class of 739 strings. 741 A fedfsUuid is a single-valued LDAP attribute. 743 745 /// 746 /// attributetype ( 747 /// 1.3.6.1.4.1.31103.1.1 NAME 'fedfsUuid' 748 /// DESC 'A UUID used by NSDB' 749 /// SUP name 750 /// SINGLE-VALUE 751 /// ) 752 /// 754 756 4.2.1.2. fedfsNetAddr 758 A fedfsNetAddr is the locative name of a network service. It MUST be 759 a UTF-8 string and represent a network location in either IPv4, IPv6, 760 or DNS name notation. 762 An IPv4 address MUST be represented using the standard dotted decimal 763 format defined by the IPv4address rule in Section 3.2.2 of RFC 3986 764 [RFC3986]. An IPv6 address MUST be represented using the format 765 defined in Section 2.2 of RFC 4291 [RFC4291]. 767 A DNS name MUST be represented using a fully qualified domain name. 768 A system (i.e. fileserver or administrative host) SHOULD resolve the 769 fully qualified domain name to a network address using the system's 770 standard resolution mechanisms. 772 This attribute is single-valued. 774 775 /// 776 /// attributetype ( 777 /// 1.3.6.1.4.1.31103.1.2 NAME 'fedfsNetAddr' 778 /// DESC 'The network name of a host or service' 779 /// SUP name 780 /// SINGLE-VALUE 781 /// ) 782 /// 784 786 4.2.1.3. fedfsNetPort 788 A fedfsNetPort is the decimal representation of a transport service's 789 port number. A fedfsNetPort MUST be encoded as an Integer syntax 790 value [RFC4517]. 792 This attribute is single-valued. 794 796 /// 797 /// attributetype ( 798 /// 1.3.6.1.4.1.31103.1.3 NAME 'fedfsNetPort' 799 /// DESC 'A transport port number of a service' 800 /// EQUALITY integerMatch 801 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 802 /// SINGLE-VALUE 803 /// ) 804 /// 806 808 4.2.1.4. fedfsFsnUuid 810 A fedfsFsnUuid represents the UUID component of an FSN. An NSDB 811 SHOULD ensure that no two FSNs it stores have the same fedfsFsnUuid. 813 The fedfsFsnUuid is a subclass of fedfsUuid, with the same encoding 814 rules. 816 This attribute is single-valued. 818 819 /// 820 /// attributetype ( 821 /// 1.3.6.1.4.1.31103.1.4 NAME 'fedfsFsnUuid' 822 /// DESC 'The FSN UUID component of an FSN' 823 /// SUP fedfsUuid 824 /// SINGLE-VALUE 825 /// ) 826 /// 828 830 4.2.1.5. fedfsNsdbName 832 A fedfsNsdbName is the NSDB component of an FSN. 834 It MUST be a UTF-8 string containing a DNS name. The DNS name MUST 835 be represented using a fully qualified domain name. A system (i.e. 836 fileserver or administrative host) SHOULD resolve the fully qualified 837 domain name to a network address using the system's standard 838 resolution mechanisms. 840 FSNs are immutable and invariant. The attributes of an FSN, 841 including the fedfsNsdbName, are expected to remain constant. 842 Therefore, a fedfsNsdbName SHOULD NOT contain a network address, such 843 as an IPv4 or IPv6 address, as this would indefinitely assign the 844 network address. 846 This attribute is single-valued. 848 850 /// 851 /// attributetype ( 852 /// 1.3.6.1.4.1.31103.1.5 NAME 'fedfsNsdbName' 853 /// DESC 'The NSDB node component of an FSN' 854 /// SUP name 855 /// SINGLE-VALUE 856 /// ) 857 /// 859 861 4.2.1.6. fedfsNsdbPort 863 A fedfsNsdbPort is the decimal representation of an NSDB's port 864 number. The fedfsNsdbPort attribute is a subclass of fedfsNetPort, 865 with the same encoding rules. 867 This attribute is single-valued. 869 871 /// 872 /// attributetype ( 873 /// 1.3.6.1.4.1.31103.1.6 NAME 'fedfsNsdbPort' 874 /// DESC 'The transport port number of an NSDB' 875 /// SUP fedfsNetPort 876 /// SINGLE-VALUE 877 /// ) 878 /// 880 882 4.2.1.7. fedfsNcePrefix 884 A fedfsNcePrefix stores a distinguished name (DN) prefix. 886 This attribute is single-valued. 888 890 /// 891 /// attributetype ( 892 /// 1.3.6.1.4.1.31103.1.7 NAME 'fedfsNcePrefix' 893 /// DESC 'NCE prefix' 894 /// EQUALITY distinguishedNameMatch 895 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 896 /// SINGLE-VALUE 897 /// ) 898 /// 900 902 OID 1.3.6.1.4.1.1466.115.121.1.12 is the DN syntax [RFC4517]. 904 4.2.1.8. fedfsFslUuid 906 A fedfsFslUuid represents the UUID of an FSL. An NSDB SHOULD ensure 907 that no two FSLs it stores have the same fedfsFslUuid. 909 The fedfsFslUuid attribute is a subclass of fedfsUuid, with the same 910 encoding rules. 912 This attribute is single-valued. 914 915 /// 916 /// attributetype ( 917 /// 1.3.6.1.4.1.31103.1.8 NAME 'fedfsFslUuid' 918 /// DESC 'UUID of an FSL' 919 /// SUP fedfsUuid 920 /// SINGLE-VALUE 921 /// ) 922 /// 924 926 4.2.1.9. fedfsFslHost 928 A fedfsFslHost is the host component of an FSL. The fedfsFslHost 929 attribute is a subclass of fedfsNetAddr, with the same encoding 930 rules. 932 This attribute is single-valued. 934 936 /// 937 /// attributetype ( 938 /// 1.3.6.1.4.1.31103.1.9 NAME 'fedfsFslHost' 939 /// DESC 'Service location for a fileserver' 940 /// SUP fedfsNetAddr 941 /// SINGLE-VALUE 942 /// ) 943 /// 945 947 4.2.1.10. fedfsFslPort 949 A fedfsFslPort is the decimal representation of a file service's port 950 number. The fedfsFslPort attribute is a subclass of fedfsNetPort, 951 with the same encoding rules. 953 This attribute is single-valued. 955 956 /// 957 /// attributetype ( 958 /// 1.3.6.1.4.1.31103.1.10 NAME 'fedfsFslPort' 959 /// DESC 'The file service transport port number' 960 /// SUP fedfsNetPort 961 /// SINGLE-VALUE 962 /// ) 963 /// 965 967 4.2.1.11. fedfsFslTTL 969 A fedfsFslTTL is the amount of time in seconds an FSL SHOULD be 970 cached by a fileserver. A fedfsFslTTL MUST be encoded as an Integer 971 syntax value [RFC4517]. 973 This attribute is single-valued. 975 977 /// 978 /// attributetype ( 979 /// 1.3.6.1.4.1.31103.1.11 NAME 'fedfsFslTTL' 980 /// DESC 'Time to live of an FSL' 981 /// EQUALITY integerMatch 982 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 983 /// SINGLE-VALUE 984 /// ) 985 /// 987 989 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 991 4.2.1.12. fedfsAnnotation 993 A fedfsAnnotation contains an object annotation. 995 This attribute is multi-valued; an object type that permits 996 annotations may have any number of annotations per instance. 998 A fedfsAnnotation attribute MUST be an UTF-8 string formatted as 999 follows: 1001 "KEY" = "VAL" 1003 White space, defined as space, form-feed ('\f'), newline ('\n'), 1004 carriage return ('\r'), horizontal tab ('\t'), and vertical tab 1005 ('\v') characters, is ignored. 1007 KEY and VAL MAY may contain any UTF-8 characters. The following 1008 escape sequences are allowed: 1010 +-----------------+-------------+ 1011 | escape sequence | replacement | 1012 +-----------------+-------------+ 1013 | \\ | \ | 1014 | \" | " | 1015 +-----------------+-------------+ 1017 A fedfsAnnotation attribute that does not adhere to this format 1018 SHOULD be ignored. 1020 The following are examples of valid fedfsAnnotation attributes: 1022 "key1" = "foo" 1023 "another key" = "x=3" 1024 "key-2" = "A string with \" and \\ characters." 1026 which correspond to the following key/value pairs: 1028 +-------------+-----------------------------------+ 1029 | key | value | 1030 +-------------+-----------------------------------+ 1031 | key1 | foo | 1032 | another key | x=3 | 1033 | key-2 | A string with " and \ characters. | 1034 +-------------+-----------------------------------+ 1036 1038 /// 1039 /// attributetype ( 1040 /// 1.3.6.1.4.1.31103.1.12 NAME 'fedfsAnnotation' 1041 /// DESC 'Annotation of an object' 1042 /// SUP name 1043 /// ) 1044 /// 1046 1048 4.2.1.13. fedfsDescr 1050 A fedfsDescr stores an object description. The description MUST be 1051 encoded as a UTF-8 string. 1053 This attribute is multi-valued which permits any number of 1054 descriptions per entry. 1056 1058 /// 1059 /// attributetype ( 1060 /// 1.3.6.1.4.1.31103.1.13 NAME 'fedfsDescr' 1061 /// DESC 'Description of an object' 1062 /// SUP name 1063 /// ) 1064 /// 1066 1068 4.2.1.14. fedfsNfsPath 1070 A fedfsNfsPath is the path component of an FSL. The path MUST be the 1071 XDR encoded NFS pathname as defined by the fs_location's rootpath 1072 [RFC3530] and the fs_locations_item's fli_rootpath [RFC5661]. A 1073 pathname is an XDR encoded variable length array of variable length 1074 opaque data. 1076 This attribute is single-valued. 1078 1080 /// 1081 /// attributetype ( 1082 /// 1.3.6.1.4.1.31103.1.100 NAME 'fedfsNfsPath' 1083 /// DESC 'Server-local path to a fileset' 1084 /// EQUALITY octetStringMatch 1085 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 1086 /// SINGLE-VALUE 1087 /// ) 1088 /// 1090 1092 OID 1.3.6.1.4.1.1466.115.121.1.40 is the Octet String syntax 1093 [RFC4517]. 1095 4.2.1.15. fedfsNfsMajorVer 1097 A fedfsNfsMajorVer contains the NFS major version of the associated 1098 NFS FSL. A fedfsNfsMajorVer MUST be encoded as an Integer syntax 1099 value [RFC4517]. 1101 For example if the FSL was exported via NFS 4.1, the contents of this 1102 attribute would be the value 4. 1104 This attribute is single-valued. 1106 1108 /// 1109 /// attributetype ( 1110 /// 1.3.6.1.4.1.31103.1.101 NAME 'fedfsNfsMajorVer' 1111 /// DESC 'NFS major version' 1112 /// EQUALITY integerMatch 1113 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1114 /// SINGLE-VALUE 1115 /// ) 1116 /// 1118 1120 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1122 4.2.1.16. fedfsNfsMinorVer 1124 A fedfsNfsMinorVer contain the NFS minor version of the associated 1125 NFS FSL. A fedfsNfsMinorVer MUST be encoded as an Integer syntax 1126 value [RFC4517]. 1128 For example if the FSL was exported via NFS 4.1, the contents of this 1129 attribute would be the value 1. 1131 This attribute is single-valued. 1133 1135 /// 1136 /// attributetype ( 1137 /// 1.3.6.1.4.1.31103.1.102 NAME 'fedfsNfsMinorVer' 1138 /// DESC 'NFS minor version' 1139 /// EQUALITY integerMatch 1140 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1141 /// SINGLE-VALUE 1142 /// ) 1143 /// 1145 1147 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1149 4.2.1.17. fedfsNfsCurrency 1151 A fedfsNfsCurrency stores the NFSv4.1 fs_locations_server's 1152 fls_currency value [RFC5661]. A fedfsNfsCurrency MUST be encoded as 1153 an Integer syntax value [RFC4517] in the range [-2147483648, 1154 2147483647]. 1156 This attribute is single-valued. 1158 1160 /// 1161 /// attributetype ( 1162 /// 1.3.6.1.4.1.31103.1.103 NAME 'fedfsNfsCurrency' 1163 /// DESC 'up-to-date measure of the data' 1164 /// EQUALITY integerMatch 1165 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1166 /// SINGLE-VALUE 1167 /// ) 1168 /// 1170 1172 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1174 4.2.1.18. fedfsNfsGenFlagWritable 1176 A fedfsNfsGenFlagWritable stores the value of an FSL's NFSv4.1 1177 FSLI4GF_WRITABLE bit [RFC5661]. A value of "TRUE" indicates the bit 1178 is true. A value of "FALSE" indicates the bit is false. 1180 1182 /// 1183 /// attributetype ( 1184 /// 1.3.6.1.4.1.31103.1.104 NAME 'fedfsNfsGenFlagWritable' 1185 /// DESC 'Indicates if the filesystem is writable' 1186 /// EQUALITY booleanMatch 1187 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 1188 /// SINGLE-VALUE 1189 /// ) 1190 /// 1192 1194 OID 1.3.6.1.4.1.1466.115.121.1.7 is the Boolean syntax [RFC4517]. 1196 4.2.1.19. fedfsNfsGenFlagGoing 1198 A fedfsNfsGenFlagGoing stores the value of an FSL's NFSv4.1 1199 FSLI4GF_GOING bit [RFC5661]. A value of "TRUE" indicates the bit is 1200 true. A value of "FALSE" indicates the bit is false. 1202 1204 /// 1205 /// attributetype ( 1206 /// 1.3.6.1.4.1.31103.1.105 NAME 'fedfsNfsGenFlagGoing' 1207 /// DESC 'Indicates if the filesystem is going' 1208 /// EQUALITY booleanMatch 1209 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 1210 /// SINGLE-VALUE 1211 /// ) 1212 /// 1214 1216 OID 1.3.6.1.4.1.1466.115.121.1.7 is the Boolean syntax [RFC4517]. 1218 4.2.1.20. fedfsNfsGenFlagSplit 1220 A fedfsNfsGenFlagSplit stores the value of an FSL's NFSv4.1 1221 FSLI4GF_SPLIT bit [RFC5661]. A value of "TRUE" indicates the bit is 1222 true. A value of "FALSE" indicates the bit is false. 1224 1226 /// 1227 /// attributetype ( 1228 /// 1.3.6.1.4.1.31103.1.106 NAME 'fedfsNfsGenFlagSplit' 1229 /// DESC 'Indicates if there are multiple filesystems' 1230 /// EQUALITY booleanMatch 1231 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 1232 /// SINGLE-VALUE 1233 /// ) 1234 /// 1236 1238 OID 1.3.6.1.4.1.1466.115.121.1.7 is the Boolean syntax [RFC4517]. 1240 4.2.1.21. fedfsNfsTransFlagRdma 1242 A fedfsNfsTransFlagRdma stores the value of an FSL's NFSv4.1 1243 FSLI4TF_RDMA bit [RFC5661]. A value of "TRUE" indicates the bit is 1244 true. A value of "FALSE" indicates the bit is false. 1246 1248 /// 1249 /// attributetype ( 1250 /// 1.3.6.1.4.1.31103.1.107 NAME 'fedfsNfsTransFlagRdma' 1251 /// DESC 'Indicates if the transport supports RDMA' 1252 /// EQUALITY booleanMatch 1253 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 1254 /// SINGLE-VALUE 1255 /// ) 1256 /// 1258 1260 OID 1.3.6.1.4.1.1466.115.121.1.7 is the Boolean syntax [RFC4517]. 1262 4.2.1.22. fedfsNfsClassSimul 1264 A fedfsNfsClassSimul contains the FSL's NFSv4.1 FSLI4BX_CLSIMUL 1265 [RFC5661] value. A fedfsNfsClassSimul MUST be encoded as an Integer 1266 syntax value [RFC4517] in the range [0, 255]. 1268 1270 /// 1271 /// attributetype ( 1272 /// 1.3.6.1.4.1.31103.1.108 NAME 'fedfsNfsClassSimul' 1273 /// DESC 'The simultaneous-use class of the filesystem' 1274 /// EQUALITY integerMatch 1275 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1276 /// SINGLE-VALUE 1277 /// ) 1278 /// 1280 1282 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1284 4.2.1.23. fedfsNfsClassHandle 1286 A fedfsNfsClassHandle contains the FSL's NFSv4.1 FSLI4BX_CLHANDLE 1287 [RFC5661] value. A fedfsNfsClassHandle MUST be encoded as an Integer 1288 syntax value [RFC4517] in the range [0, 255]. 1290 1291 /// 1292 /// attributetype ( 1293 /// 1.3.6.1.4.1.31103.1.109 NAME 'fedfsNfsClassHandle' 1294 /// DESC 'The handle class of the filesystem' 1295 /// EQUALITY integerMatch 1296 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1297 /// SINGLE-VALUE 1298 /// ) 1299 /// 1301 1303 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1305 4.2.1.24. fedfsNfsClassFileid 1307 A fedfsNfsClassFileid contains the FSL's NFSv4.1 FSLI4BX_CLFILEID 1308 [RFC5661] value. A fedfsNfsClassFileid MUST be encoded as an Integer 1309 syntax value [RFC4517] in the range [0, 255]. 1311 1313 /// 1314 /// attributetype ( 1315 /// 1.3.6.1.4.1.31103.1.110 NAME 'fedfsNfsClassFileid' 1316 /// DESC 'The fileid class of the filesystem' 1317 /// EQUALITY integerMatch 1318 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1319 /// SINGLE-VALUE 1320 /// ) 1321 /// 1323 1325 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1327 4.2.1.25. fedfsNfsClassWritever 1329 A fedfsNfsClassWritever contains the FSL's NFSv4.1 FSLI4BX_CLWRITEVER 1330 [RFC5661] value. A fedfsNfsClassWritever MUST be encoded as an 1331 Integer syntax value [RFC4517] in the range [0, 255]. 1333 1334 /// 1335 /// attributetype ( 1336 /// 1.3.6.1.4.1.31103.1.111 NAME 'fedfsNfsClassWritever' 1337 /// DESC 'The write-verifier class of the filesystem' 1338 /// EQUALITY integerMatch 1339 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1340 /// SINGLE-VALUE 1341 /// ) 1342 /// 1344 1346 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1348 4.2.1.26. fedfsNfsClassChange 1350 A fedfsNfsClassChange contains the FSL's NFSv4.1 FSLI4BX_CLCHANGE 1351 [RFC5661] value. A fedfsNfsClassChange MUST be encoded as an Integer 1352 syntax value [RFC4517] in the range [0, 255]. 1354 1356 /// 1357 /// attributetype ( 1358 /// 1.3.6.1.4.1.31103.1.112 NAME 'fedfsNfsClassChange' 1359 /// DESC 'The change class of the filesystem' 1360 /// EQUALITY integerMatch 1361 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1362 /// SINGLE-VALUE 1363 /// ) 1364 /// 1366 1368 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1370 4.2.1.27. fedfsNfsClassReaddir 1372 A fedfsNfsClassReaddir contains the FSL's NFSv4.1 FSLI4BX_CLREADDIR 1373 [RFC5661] value. A fedfsNfsClassReaddir MUST be encoded as an 1374 Integer syntax value [RFC4517] in the range [0, 255]. 1376 1377 /// 1378 /// attributetype ( 1379 /// 1.3.6.1.4.1.31103.1.113 NAME 'fedfsNfsClassReaddir' 1380 /// DESC 'The readdir class of the filesystem' 1381 /// EQUALITY integerMatch 1382 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1383 /// SINGLE-VALUE 1384 /// ) 1385 /// 1387 1389 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1391 4.2.1.28. fedfsNfsReadRank 1393 A fedfsNfsReadRank contains the FSL's NFSv4.1 FSLI4BX_READRANK 1394 [RFC5661] value. A fedfsNfsReadRank MUST be encoded as an Integer 1395 syntax value [RFC4517] in the range [0, 255]. 1397 1399 /// 1400 /// attributetype ( 1401 /// 1.3.6.1.4.1.31103.1.114 NAME 'fedfsNfsReadRank' 1402 /// DESC 'The read rank of the filesystem' 1403 /// EQUALITY integerMatch 1404 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1405 /// SINGLE-VALUE 1406 /// ) 1407 /// 1409 1411 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1413 4.2.1.29. fedfsNfsReadOrder 1415 A fedfsNfsReadOrder contains the FSL's NFSv4.1 FSLI4BX_READORDER 1416 [RFC5661] value. A fedfsNfsReadOrder MUST be encoded as an Integer 1417 syntax value [RFC4517] in the range [0, 255]. 1419 1420 /// 1421 /// attributetype ( 1422 /// 1.3.6.1.4.1.31103.1.115 NAME 'fedfsNfsReadOrder' 1423 /// DESC 'The read order of the filesystem' 1424 /// EQUALITY integerMatch 1425 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1426 /// SINGLE-VALUE 1427 /// ) 1428 /// 1430 1432 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1434 4.2.1.30. fedfsNfsWriteRank 1436 A fedfsNfsWriteRank contains the FSL's FSLI4BX_WRITERANK [RFC5661] 1437 value. A fedfsNfsWriteRank MUST be encoded as an Integer syntax 1438 value [RFC4517] in the range [0, 255]. 1440 1442 /// 1443 /// attributetype ( 1444 /// 1.3.6.1.4.1.31103.1.116 NAME 'fedfsNfsWriteRank' 1445 /// DESC 'The write rank of the filesystem' 1446 /// EQUALITY integerMatch 1447 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1448 /// SINGLE-VALUE 1449 /// ) 1450 /// 1452 1454 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1456 4.2.1.31. fedfsNfsWriteOrder 1458 A fedfsNfsWriteOrder contains the FSL's FSLI4BX_WRITEORDER [RFC5661] 1459 value. A fedfsNfsWriteOrder MUST be encoded as an Integer syntax 1460 value [RFC4517] in the range [0, 255]. 1462 1463 /// 1464 /// attributetype ( 1465 /// 1.3.6.1.4.1.31103.1.117 NAME 'fedfsNfsWriteOrder' 1466 /// DESC 'The write order of the filesystem' 1467 /// EQUALITY integerMatch 1468 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1469 /// SINGLE-VALUE 1470 /// ) 1471 /// 1473 1475 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1477 4.2.1.32. fedfsNfsVarSub 1479 A fedfsNfsVarSub stores the value of an FSL's NFSv4.1 FSLI4F_VAR_SUB 1480 bit [RFC5661]. A value of "TRUE" indicates the bit is true. A value 1481 of "FALSE" indicates the bit is false. 1483 1485 /// 1486 /// attributetype ( 1487 /// 1.3.6.1.4.1.31103.1.118 NAME 'fedfsNfsVarSub' 1488 /// DESC 'Indicates if variable substitution is present' 1489 /// EQUALITY booleanMatch 1490 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 1491 /// SINGLE-VALUE 1492 /// ) 1493 /// 1495 1497 OID 1.3.6.1.4.1.1466.115.121.1.7 is the Boolean syntax [RFC4517]. 1499 4.2.1.33. fedfsNfsValidFor 1501 A fedfsNfsValidFor stores an FSL's NFSv4.1 fs_locations_info 1502 fli_valid_for value [RFC5661]. A fedfsNfsValidFor MUST be encoded as 1503 an Integer syntax value [RFC4517] in the range [-2147483648, 1504 2147483647]. 1506 An FSL's fedfsFslTTL value and fedfsNfsValidFor value MAY be 1507 different. 1509 This attribute is single-valued. 1511 1513 /// 1514 /// attributetype ( 1515 /// 1.3.6.1.4.1.31103.1.19 NAME 'fedfsNfsValidFor' 1516 /// DESC 'Valid for time' 1517 /// EQUALITY integerMatch 1518 /// SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 1519 /// SINGLE-VALUE 1520 /// ) 1521 /// 1523 OID 1.3.6.1.4.1.1466.115.121.1.27 is the Integer syntax [RFC4517]. 1525 1527 4.2.2. LDAP Objects 1529 4.2.2.1. fedfsNsdbContainerInfo 1531 A fedfsNsdbContainerInfo describes the location of the NCE. 1533 A fedfsFsn's fedfsNcePrefix attribute is REQUIRED. 1535 A fedfsFsn's fedfsAnnotation and fedfsDescr attributes are OPTIONAL. 1537 1539 /// 1540 /// objectclass ( 1541 /// 1.3.6.1.4.1.31103.1.1001 NAME 'fedfsNsdbContainerInfo' 1542 /// DESC 'Describes NCE location' 1543 /// SUP top AUXILIARY 1544 /// MUST ( 1545 /// fedfsNcePrefix 1546 /// ) 1547 /// MAY ( 1548 /// fedfsAnnotation 1549 /// $ fedfsDescr 1550 /// )) 1551 /// 1553 1555 4.2.2.2. fedfsFsn 1557 A fedfsFsn represents an FSN. 1559 A fedfsFsn's fedfsNsdbName and fedfsFsnUuid attributes are REQUIRED. 1561 A fedfsFsn's fedfsNsdbPort, fedfsAnnotation, and fedfsDescr 1562 attributes are OPTIONAL. 1564 If the fedfsNsdbPort is omitted, the standard LDAP port number, 389, 1565 SHOULD be assumed. 1567 The DN of an FSN is REQUIRED to take the following form: 1568 "fedfsFsnUuid=$FSNUUID,$NCE", where $FSNUUID is the UUID of the FSN 1569 and $NCE is the DN of the NCE ("o=fedfs" by default). Since LDAP 1570 requires a DN to be unique, this ensures that each FSN entry has a 1571 unique UUID value within the LDAP directory. 1573 A fedfsFsn MAY also have additional attributes, but these attributes 1574 MUST NOT be referenced by any part of this document. 1576 1578 /// 1579 /// objectclass ( 1580 /// 1.3.6.1.4.1.31103.1.1002 NAME 'fedfsFsn' 1581 /// DESC 'Represents a fileset' 1582 /// SUP top STRUCTURAL 1583 /// MUST ( 1584 /// fedfsFsnUuid 1585 /// $ fedfsNsdbName 1586 /// ) 1587 /// MAY ( 1588 /// fedfsNsdbPort 1589 /// $ fedfsAnnotation 1590 /// $ fedfsDescr 1591 /// )) 1592 /// 1594 1596 4.2.2.3. fedfsFsl 1598 The fedfsFsl object class represents an FSL. 1600 The fedfsFsl is an abstract object class. Protocol specific subtypes 1601 of this object class are used to store FSL information. The 1602 fedfsNfsFsl object class defined below is used to record an NFS FSL's 1603 location. Other subtypes MAY be defined for other protocols (e.g. 1604 CIFS). 1606 A fedfsFsl's fedfsFslUuid, fedfsFsnUuid, fedfsNsdbName, fedfsFslHost, 1607 and fedfsFslTTL attributes are REQUIRED. 1609 A fedfsFsl's fedfsNsdbPort, fedfsFslPort, fedfsAnnotation, and 1610 fedfsDescr attributes are OPTIONAL. 1612 If the fedfsNsdbPort is omitted, the standard LDAP port number, 389, 1613 SHOULD be assumed. 1615 If the fedfsFslPort is omitted, a standard port number based on the 1616 type of FSL should be assumed. For an NFS FSL, the standard NFS port 1617 number, 2049, SHOULD be assumed. 1619 The DN of an FSL is REQUIRED to take the following form: 1620 "fedfsFslUuid=$FSLUUID,fedfsFsnUuid=$FSNUUID,$NCE" where $FSLUUID is 1621 the FSL's UUID, $FSNUUID is the FSN's UUID, and $NCE is the DN of the 1622 NCE ("o=fedfs" by default). Since LDAP requires a DN to be unique, 1623 this ensures that each FSL entry has a unique UUID value within the 1624 LDAP directory. 1626 1628 /// 1629 /// objectclass ( 1630 /// 1.3.6.1.4.1.31103.1.1003 NAME 'fedfsFsl' 1631 /// DESC 'A physical location of a fileset' 1632 /// SUP top ABSTRACT 1633 /// MUST ( 1634 /// fedfsFslUuid 1635 /// $ fedfsFsnUuid 1636 /// $ fedfsNsdbName 1637 /// $ fedfsFslHost 1638 /// $ fedfsFslTTL 1639 /// ) 1640 /// MAY ( 1641 /// fedfsNsdbPort 1642 /// $ fedfsFslPort 1643 /// $ fedfsAnnotation 1644 /// $ fedfsDescr 1645 /// )) 1646 /// 1648 1650 4.2.2.4. fedfsNfsFsl 1652 A fedfsNfsFsl is used to represent an NFS FSL. The fedfsNfsFsl 1653 inherits all of the attributes of the fedfsFsl and extends the 1654 fedfsFsl with information specific to the NFS protocol. 1656 The DN of an NFS FSL is REQUIRED to take the following form: 1657 "fedfsFslUuid=$FSLUUID,fedfsFsnUuid=$FSNUUID,$NCE" where $FSLUUID is 1658 the FSL's UUID, $FSNUUID is the FSN's UUID, and $NCE is the DN of the 1659 NCE ("o=fedfs" by default). Since LDAP requires a DN to be unique, 1660 this ensures that each NFS FSL entry has a unique UUID value within 1661 the LDAP directory. 1663 1665 /// 1666 /// objectclass ( 1667 /// 1.3.6.1.4.1.31103.1.1004 NAME 'fedfsNfsFsl' 1668 /// DESC 'An NFS location of a fileset' 1669 /// SUP fedfsFsl STRUCTURAL 1670 /// MUST ( 1671 /// fedfsNfsPath 1672 /// $ fedfsNfsMajorVer 1673 /// $ fedfsNfsMinorVer 1674 /// $ fedfsNfsCurrency 1675 /// $ fedfsNfsGenFlagWritable 1676 /// $ fedfsNfsGenFlagGoing 1677 /// $ fedfsNfsGenFlagSplit 1678 /// $ fedfsNfsTransFlagRdma 1679 /// $ fedfsNfsClassSimul 1680 /// $ fedfsNfsClassHandle 1681 /// $ fedfsNfsClassFileid 1682 /// $ fedfsNfsClassWritever 1683 /// $ fedfsNfsClassChange 1684 /// $ fedfsNfsClassReaddir 1685 /// $ fedfsNfsReadRank 1686 /// $ fedfsNfsReadOrder 1687 /// $ fedfsNfsWriteRank 1688 /// $ fedfsNfsWriteOrder 1689 /// $ fedfsNfsVarSub 1690 /// $ fedfsNfsValidFor 1691 /// )) 1692 /// 1694 1696 5. NSDB Operations 1698 The operations defined by the protocol can be described as several 1699 sub-protocols that are used by entities within the federation to 1700 perform different roles. 1702 The first of these sub-protocols defines how the state of an NSDB 1703 node can be initialized and updated. The primary use of this sub- 1704 protocol is by an administrator to add, edit, or delete filesets, 1705 their properties, and their fileset locations. 1707 The second of these sub-protocols defines the queries that are sent 1708 to an NSDB node in order to perform resolution (or to find other 1709 information about the data stored within that NSDB node) and the 1710 responses returned by the NSDB node. The primary use of this sub- 1711 protocol is by a fileserver in order to perform resolution, but it 1712 may also be used by an administrator to query the state of the 1713 system. 1715 The first and second sub-protocols are defined as LDAP operations, 1716 using the schema defined in the previous section. If each NSDB node 1717 is a standard LDAP server, then, in theory, it is unnecessary to 1718 describe the LDAP operations in detail, because the operations are 1719 ordinary LDAP operations to query and update records. However, we do 1720 not require that an NSDB node implement a complete LDAP service, and 1721 therefore we define in these sections the minimum level of LDAP 1722 functionality required to implement an NSDB node. 1724 The NSDB sub-protocols are defined in the next two sub-sections. The 1725 descriptions of LDAP messages in these sections use the LDAP Data 1726 Interchange Format (LDIF) [RFC2849]. In order to differentiate 1727 constant and variable strings in the LDIF specifications, variables 1728 are prefixed by a $ character and use all upper case characters. For 1729 example, a variable named FOO would be specified as $FOO. 1731 The third sub-protocol defines the queries and other requests that 1732 are sent to a fileserver in order to get information from it or to 1733 modify the state of the fileserver in a manner related to the 1734 federation protocols. The primary purpose of this protocol is for an 1735 administrator to create or delete a junction or discover related 1736 information about a particular fileserver. 1738 The third sub-protocol is defined as an ONC RPC protocols. The 1739 reason for using ONC RPC instead of LDAP is that all fileservers 1740 support ONC RPC but some do not support an LDAP Directory server. 1742 The ONC RPC administration protocol is defined in [FEDFS-ADMIN]. 1744 5.1. NSDB Operations for Administrators 1746 The admin entity initiates and controls the commands to manage 1747 fileset and namespace information. The admin entity, however, is 1748 stateless. All state is maintained at the NSDB nodes or at the 1749 fileserver. 1751 We require that each NSDB node be able to act as an LDAP server and 1752 that the protocol used for communicating between the admin entity and 1753 each NSDB node is LDAP. 1755 The names we assign to these operations are entirely for the purpose 1756 of exposition in this document, and are not part of the LDAP dialogs. 1758 5.1.1. Create an FSN 1760 This operation creates a new FSN in the NSDB by adding a new fedfsFsn 1761 entry in the NSDB's LDAP directory. 1763 A fedfsFsn entry contains a fedfsFsnUuid and fedfsNsdbName. The 1764 administrator chooses the fedfsFsnUuid and fedfsNsdbName. The 1765 process for choosing the fedfsFsnUuid is described in 1766 Section 4.2.1.1). The fedfsNsdbName is the name of the NSDB node 1767 that will serve as the source of definitive information about the FSN 1768 for the life of the FSN. 1770 The NSDB node that receives the request SHOULD check that 1771 fedfsNsdbName value matches its own value and return an error if it 1772 does not. This is to ensure that an FSN is always created by the 1773 NSDB node encoded within the FSN as its owner. 1775 The NSDB node that receives the request SHOULD check all of the 1776 attributes for validity and consistency, but this is not generally 1777 possible for LDAP servers because the consistency requirements cannot 1778 be expressed in the LDAP schema (although many LDAP servers can be 1779 extended, via plug-ins or other mechanisms, to add functionality 1780 beyond the strict definition of LDAP). 1782 5.1.1.1. LDAP Request 1784 This operation is implemented using the LDAP ADD request described by 1785 the LDIF below. 1787 dn: fedfsFsnUuid=$FSNUUID,$NCE 1788 changeType: add 1789 objectClass: fedfsFsn 1790 fedfsFsnUuid: $FSNUUID 1791 fedfsNsdbName: $NSDBNAME 1793 For example, if the $FSNUUID is "f81d4fae-7dec-11d0-a765- 1794 00a0c91e6bf6", the $NSDBNAME is "nsdb.example.com", and the $NCE is 1795 "o=fedfs" the operation would be: 1797 dn: fedfsFsnUuid=f81d4fae-7dec-11d0-a765-00a0c91e6bf6,o=fedfs 1798 changeType: add 1799 objectClass: fedfsFsn 1800 fedfsFsnUuid: f81d4fae-7dec-11d0-a765-00a0c91e6bf6 1801 fedfsNsdbName: nsdb.example.com 1803 5.1.2. Delete an FSN 1805 This operation deletes an FSN by removing a fedfsFsn entry in the 1806 NSDB's LDAP directory. 1808 If the FSN entry being deleted has child FSL entries, this function 1809 MUST return an error. This ensures that the NSDB will not contain 1810 any orphaned FSL entries. A compliant LDAP implementation will meet 1811 this requirement since Section 4.8 of [RFC4511] defines the LDAP 1812 delete operation to only be capable of removing leaf entries. 1814 Note that the FSN delete function only removes the fileset from the 1815 namespace (by removing the records for that FSN from the NSDB node 1816 that receives this request). The fileset and its data are not 1817 deleted. Any junction that has this FSN as its target may continue 1818 to point to this non-existent FSN. A dangling reference may be 1819 detected when a client tries to resolve the target of a junction that 1820 refers to the deleted FSN and the NSDB returns an error. 1822 5.1.2.1. LDAP Request 1824 This operation is implemented using the LDAP DELETE request described 1825 by the LDIF below. 1827 dn: fedfsFsnUuid=$FSNUUID,$NCE 1828 changeType: delete 1830 For example, if the $FSNUUID is "f81d4fae-7dec-11d0-a765- 1831 00a0c91e6bf6" and $NCE is "o=fedfs", the operation would be: 1833 dn: fedfsFsnUuid=f81d4fae-7dec-11d0-a765-00a0c91e6bf6,o=fedfs 1834 changeType: delete 1836 5.1.3. Create an FSL 1838 This operation creates a new FSL for the given FSN by adding a new 1839 fedfsFsl entry in the NSDB's LDAP directory. 1841 A fedfsFsl entry contains a fedfsFslUuid, fedfsFsnUuid, 1842 fedfsNsdbName, fedfsFslHost, and fedfsFslTTL. The administrator 1843 chooses the fedfsFslUuid. The process for choosing the fedfsFslUuid 1844 is described in Section 4.2.1.1. The fedfsFsnUuid is the UUID of the 1845 FSL's FSN. The fedfsNsdbName is the name of the NSDB node that 1846 stores definitive information about the FSL's FSN. The fedfsFslHost 1847 value is the network location of the fileserver that stores the FSL. 1848 The fedfsFslTTL is chosen by the administrator as described in 1849 Section 2.4.2. 1851 The administrator will also set additional attributes depending on 1852 the FSL type. 1854 5.1.3.1. LDAP Request 1856 This operation is implemented using the LDAP ADD request described by 1857 the LDIF below (NOTE: the LDIF shows the creation of an NFS FSL) 1859 dn:fedfsFslUuid=$FSLUUID,fedfsFsnUuid=$FSNUUID,$NCE 1860 changeType: add 1861 objectClass: fedfsNfsFsl 1862 fedfsFslUuid: $FSLUUID 1863 fedfsFsnUuid: $FSNUUID 1864 fedfsNsdbName: $NSDBNAME 1865 fedfsFslHost: $HOST 1866 fedfsFslPort: $PORT 1867 fedfsFslTTL: $TTL 1868 fedfsNfsPath: $PATH 1869 fedfsNfsMajorVer: $MAJOR 1870 fedfsNfsMinorVer: $MINOR 1871 fedfsNfsCurrency: $CURRENCY 1872 fedfsNfsGenFlagWritable: $WRITABLE 1873 fedfsNfsGenFlagGoing: $GOING 1874 fedfsNfsGenFlagSplit: $SPLIT 1875 fedfsNfsTransFlagRdma: $RDMA 1876 fedfsNfsClassSimul: $CLASS_SIMUL 1877 fedfsNfsClassHandle:$CLASS_HANDLE 1878 fedfsNfsClassFileid:$CLASS_FILEID 1879 fedfsNfsClassWritever:$CLASS_WRITEVER 1880 fedfsNfsClassChange: $CLASS_CHANGE 1881 fedfsNfsClassReaddir: $CLASS_READDIR 1882 fedfsNfsReadRank: $READ_RANK 1883 fedfsNfsReadOrder: $READ_ORDER 1884 fedfsNfsWriteRank: $WRITE_RANK 1885 fedfsNfsWriteOrder: $WRITE_ORDER 1886 fedfsNfsVarSub: $VAR_SUB 1887 fedfsNfsValidFor: $TIME 1888 fedfsAnnotation: $ANNOTATION 1889 fedfsDescr: $DESCR 1891 For example, if the $FSNUUID is "f81d4fae-7dec-11d0-a765- 1892 00a0c91e6bf6", the $FSLUUID is "84f775a7-8e31-14ae-b39d- 1893 10eeee060d2c", the $NSDBNAME is "nsdb.example.com", the $HOST is 1894 "server.example.com", $PORT is "2049", the $TTL is "300" seconds, the 1895 $PATH is stored in the file "/tmp/fsl_path", fileset is exported via 1896 NFSv4.1 ($MAJOR is "4" and $MINOR is "1"), $CURRENCY is "0" (an up to 1897 date copy), the FSL is writable, but not going, split, or accessible 1898 via RDMA, the simultaneous-use class is "1", the handle class is "0", 1899 the fileid class is "1", the write-verifier class is "1", the change 1900 class is "1", the readdir class is "9", the read rank is "7", the 1901 read order is "8", the write rank is "5", the write order is "6", 1902 variable substitution is false, $TIME is "300" seconds, $ANNOTATION 1903 is ""foo" = "bar"", $DESC is "This is a description.", and the $NCE 1904 is "o=fedfs", the operation would be (for readability the DN is split 1905 into two lines): 1907 dn:fedfsFslUuid=84f775a7-8e31-14ae-b39d-10eeee060d2c, 1908 fedfsFsnUuid=f81d4fae-7dec-11d0-a765-00a0c91e6bf6,o=fedfs 1909 changeType: add 1910 objectClass: fedfsNfsFsl 1911 fedfsFslUuid: 84f775a7-8e31-14ae-b39d-10eeee060d2c 1912 fedfsFsnUuid: f81d4fae-7dec-11d0-a765-00a0c91e6bf6 1913 fedfsNsdbName: nsdb.example.com 1914 fedfsFslHost: server.example.com 1915 fedfsFslPort: 2049 1916 fedfsFslTTL: 300 1917 fedfsNfsPath:< file:///tmp/fsl_path 1918 fedfsNfsMajorVer: 4 1919 fedfsNfsMinorVer: 1 1920 fedfsNfsCurrency: 0 1921 fedfsNfsGenFlagWritable: TRUE 1922 fedfsNfsGenFlagGoing: FALSE 1923 fedfsNfsGenFlagSplit: FALSE 1924 fedfsNfsTransFlagRdma: FALSE 1925 fedfsNfsClassSimul: 1 1926 fedfsNfsClassHandle: 0 1927 fedfsNfsClassFileid: 1 1928 fedfsNfsClassWritever: 1 1929 fedfsNfsClassChange: 1 1930 fedfsNfsClassReaddir: 9 1931 fedfsNfsReadRank: 7 1932 fedfsNfsReadOrder: 8 1933 fedfsNfsWriteRank: 5 1934 fedfsNfsWriteOrder: 6 1935 fedfsNfsVarSub: FALSE 1936 fedfsNfsValidFor: 300 1937 fedfsAnnotation: "foo" = "bar" 1938 fedfsDescr: This is a description. 1940 5.1.4. Delete an FSL 1942 This operation deletes the given Fileset location. The admin 1943 requests the NSDB node storing the fedfsFsl to delete it from its 1944 database. This operation does not result in the fileset location's 1945 data being deleted at the fileserver. 1947 5.1.4.1. LDAP Request 1949 The admin sends an LDAP DELETE request to the NSDB node to remove the 1950 FSL. 1952 dn: fedfsFslUuid=$FSLUUID,fedfsFsnUuid=$FSNUUID,$NCE 1953 changeType: delete 1955 For example, if the $FSNUUID is "f81d4fae-7dec-11d0-a765- 1956 00a0c91e6bf6", the $FSLUUID is "84f775a7-8e31-14ae-b39d- 1957 10eeee060d2c", and the $NCE is "o=fedfs", the operation would be (for 1958 readability the DN is split into two lines): 1960 dn: fedfsFslUuid=84f775a7-8e31-14ae-b39d-10eeee060d2c, 1961 fedfsFsnUuid=f81d4fae-7dec-11d0-a765-00a0c91e6bf6,o=fedfs 1962 changeType: delete 1964 5.1.5. Update an FSL 1966 This operation updates the attributes of a given FSL. This command 1967 results in a change in the attributes of the fedfsFsl at the NSDB 1968 node maintaining this FSL. The attributes that must not change are 1969 the fedfsFslUuid and the fedfsFsnUuid of the fileset this FSL 1970 implements. 1972 5.1.5.1. LDAP Request 1974 The admin sends an LDAP MODIFY request to the NSDB node to update the 1975 FSL. 1977 dn: fedfsFslUuid=$FSLUUID,fedfsFsnUuid=$FSNUUID,$NCE 1978 changeType: modify 1979 replace: $ATTRIBUTE-TYPE 1981 For example, if the $FSNUUID is "f81d4fae-7dec-11d0-a765- 1982 00a0c91e6bf6", the $FSLUUID is "84f775a7-8e31-14ae-b39d- 1983 10eeee060d2c", the $NCE is "o=fedfs", and the administrator wished to 1984 change the TTL to 10 minutes, the operation would be (for readability 1985 the DN is split into two lines): 1987 dn: fedfsFslUuid=84f775a7-8e31-14ae-b39d-10eeee060d2c, 1988 fedfsFsnUuid=f81d4fae-7dec-11d0-a765-00a0c91e6bf6,o=fedfs 1989 changeType: modify 1990 replace: fedfsFslTTL 1991 fedfsFslTTL: 600 1993 5.2. NSDB Operations for Fileservers 1995 5.2.1. NSDB Container Entry (NCE) Enumeration 1997 To find the NCEs for the NSDB foo.example.com, a fileserver would do 1998 the following: 2000 nce_list = empty 2001 connect to the LDAP directory at foo.example.com 2002 for each namingContext value $BAR in the root DSE 2003 /* $BAR is a DN */ 2004 query for a fedfsNcePrefix value at $BAR 2005 /* 2006 * The LDAP URL for this search would be 2007 * 2008 * ldap://foo.example.com:389/$BAR?fedfsNcePrefix?? 2009 * (objectClass=fedfsNsdbContainerInfo) 2010 * 2011 */ 2012 if a fedfsNcePrefix value is found 2013 prepend value to $BAR and add to nce_list 2015 5.2.2. Lookup FSLs for an FSN 2017 Using an LDAP search, the fileserver can obtain all of the FSLs for a 2018 given FSN. The FSN's fedfsFsnUuid is used as the search key. The 2019 following examples use the LDAP URI format defined in [RFC4516]. 2021 To obtain a list of all FSLs for $FSNUUID on the NSDB named 2022 $NSDBNAME, the following search can be used (for readability the URI 2023 is split into two lines): 2025 for each $NCE in nce_list 2026 ldap://$NSDBNAME/fsnUuid=$FSNUUID,$NCE??one? 2027 (objectClass=fedfsFsl) 2029 This search is for the children of the object with DN 2030 "fedfsFsnUuid=$FSNUUID,$NCE" with a filter for 2031 "objectClass=fedfsFsl". The scope value of "one" restricts the 2032 search to the entry's children (rather than the entire subtree below 2033 the entry) and the filter ensures that only FSL entries are returned. 2035 For example if $NSDBNAME is "nsdb.example.com", $FSNUUID is 2036 "f81d4fae-7dec-11d0-a765-00a0c91e6bf6", and $NCE is "o=fedfs", the 2037 search would be (for readability the URI is split into three lines): 2039 ldap://nsdb.example.com/ 2040 fsnUuid=f81d4fae-7dec-11d0-a765-00a0c91e6bf6,o=fedfs 2041 ??one?(objectClass=fedfsFsl) 2043 The following search can be used to obtain only the NFS FSLs for 2044 $FSNUUID on the NSDB named $NSDBNAME (for readability the URI is 2045 split into two lines): 2047 for each $NCE in nce_list 2048 ldap://$NSDBNAME/fsnUuid=$FSNUUID,$NCE??one? 2049 (objectClass=fedfsNfsFsl) 2051 This also searches for the children of the object with DN 2052 "fedfsFsnUuid=$FSNUUID,$NCE", but the filter for "objectClass = 2053 fedfsNfsFsl" restricts the results to only NFS FSLs. 2055 For example if $NSDBNAME is nsdb.example.com, $FSNUUID is f81d4fae- 2056 7dec-11d0-a765-00a0c91e6bf6, and $NCE is "o=fedfs",the search would 2057 be (for readability the URI is split into three lines): 2059 ldap://nsdb.example.com/ 2060 fsnUuid=f81d4fae-7dec-11d0-a765-00a0c91e6bf6,o=fedfs 2061 ??one?(objectClass=fedfsNfsFsl) 2063 The fileserver will generate a referral based on the set of FSLs 2064 returned by these queries using the process described in 2065 Section 2.4.3. 2067 6. Security Considerations 2069 Both NFSv4/NFSv4.1 and LDAP provide security mechanisms. When used 2070 in conjunction with the federated filesystem protocols described in 2071 this document, the use of these mechanisms is RECOMMENDED. 2072 Specifically, the use of RPCSEC_GSS [RFC2203], which is built on the 2073 GSS-API [RFC2743], is RECOMMENDED on all NFS connections between a 2074 client and fileserver. The "Security Considerations" sections of the 2075 the NFSv4 [RFC3530] and NFSv4.1 [RFC5661] specifications contain 2076 special considerations for the handling of GETATTR operations for the 2077 fs_locations and fs_locations_info attributes. For all LDAP 2078 connections established by the federated filesystem protocols, the 2079 use of TLS [RFC5246], as described in [RFC4513], is RECOMMENDED. 2081 Within a federation, there are two types of components an attacker 2082 may compromise: a fileserver and an NSDB. 2084 If an attacker compromises a fileserver, the attacker can interfere 2085 with the client's filesystem I/O operations (e.g. by returning 2086 fictitious data in the response to a read request) or fabricating a 2087 referral. The attacker's abilities are the same regardless of 2088 whether or not the federation protocols are in use. While the 2089 federation protocols do not give the attacker additional 2090 capabilities, they are additional targets for attack. The LDAP 2091 protocol described in Section 5.2 SHOULD be secured using the methods 2092 described above to defeat attacks on a fileserver via this channel. 2094 If an attacker compromises an NSDB, the attacker will be able to 2095 forge FSL information and thus poison the fileserver's referral 2096 information. Therefore an NSDB should be as secure as the 2097 fileservers which query it. The LDAP operations described in 2098 Section 5 SHOULD be secured using the methods described above to 2099 defeat attacks on an NSDB via this channel. 2101 It should be noted that the federation protocols do not directly 2102 provide access to filesystem data. The federation protocols only 2103 provide a mechanism for building a namespace. All data transfers 2104 occur between a client and server just as they would if the 2105 federation protocols were not in use. As a result, the federation 2106 protocols do not require new user authentication and authorization 2107 mechanisms or require a fileserver to act as a proxy for a client. 2109 7. IANA Considerations 2111 The LDAP attributes and object classes defined in this document are 2112 assigned object identifier (OID) values from the 1.3.6.1.4.1.31103.x 2113 range. This is an Internet Private Enterprise Numbers range and was 2114 assigned to the authors using the process described in [RFC2578]. 2116 In accordance with Section 3.4 and Section 4 of [RFC4520], the object 2117 identifier descriptors defined in this document (listed below) will 2118 be registered via the Expert Review process. 2120 7.1. LDAP Descriptor Registration 2122 Subject: Request for LDAP Descriptor Registration 2123 Person & email address to contact for further information: See 2124 "Author/Change Controller" 2125 Specification: draft-ietf-nfsv4-federated-fs-protocol 2126 Author/Change Controller: [document authors] 2128 Object Identifier: 1.3.6.1.4.1.31103.1.1 2129 Descriptor (short name): fedfsUuid 2130 Usage: attribute type 2132 Object Identifier: 1.3.6.1.4.1.31103.1.2 2133 Descriptor (short name): fedfsNetAddr 2134 Usage: attribute type 2136 Object Identifier: 1.3.6.1.4.1.31103.1.3 2137 Descriptor (short name): fedfsNetPort 2138 Usage: attribute type 2140 Object Identifier: 1.3.6.1.4.1.31103.1.4 2141 Descriptor (short name): fedfsFsnUuid 2142 Usage: attribute type 2144 Object Identifier: 1.3.6.1.4.1.31103.1.5 2145 Descriptor (short name): fedfsNsdbName 2146 Usage: attribute type 2148 Object Identifier: 1.3.6.1.4.1.31103.1.6 2149 Descriptor (short name): fedfsNsdbPort 2150 Usage: attribute type 2152 Object Identifier: 1.3.6.1.4.1.31103.1.7 2153 Descriptor (short name): fedfsNcePrefix 2154 Usage: attribute type 2156 Object Identifier: 1.3.6.1.4.1.31103.1.8 2157 Descriptor (short name): fedfsFslUuid 2158 Usage: attribute type 2160 Object Identifier: 1.3.6.1.4.1.31103.1.9 2161 Descriptor (short name): fedfsFslHost 2162 Usage: attribute type 2164 Object Identifier: 1.3.6.1.4.1.31103.1.10 2165 Descriptor (short name): fedfsFslPort 2166 Usage: attribute type 2168 Object Identifier: 1.3.6.1.4.1.31103.1.11 2169 Descriptor (short name): fedfsFslTTL 2170 Usage: attribute type 2172 Object Identifier: 1.3.6.1.4.1.31103.1.12 2173 Descriptor (short name): fedfsAnnotation 2174 Usage: attribute type 2176 Object Identifier: 1.3.6.1.4.1.31103.1.13 2177 Descriptor (short name): fedfsDescr 2178 Usage: attribute type 2180 Object Identifier: 1.3.6.1.4.1.31103.1.100 2181 Descriptor (short name): fedfsNfsPath 2182 Usage: attribute type 2184 Object Identifier: 1.3.6.1.4.1.31103.1.101 2185 Descriptor (short name): fedfsNfsMajorVer 2186 Usage: attribute type 2188 Object Identifier: 1.3.6.1.4.1.31103.1.102 2189 Descriptor (short name): fedfsNfsMinorVer 2190 Usage: attribute type 2192 Object Identifier: 1.3.6.1.4.1.31103.1.103 2193 Descriptor (short name): fedfsNfsCurrency 2194 Usage: attribute type 2196 Object Identifier: 1.3.6.1.4.1.31103.1.104 2197 Descriptor (short name): fedfsNfsGenFlagWritable 2198 Usage: attribute type 2200 Object Identifier: 1.3.6.1.4.1.31103.1.105 2201 Descriptor (short name): fedfsNfsGenFlagGoing 2202 Usage: attribute type 2204 Object Identifier: 1.3.6.1.4.1.31103.1.106 2205 Descriptor (short name): fedfsNfsGenFlagSplit 2206 Usage: attribute type 2208 Object Identifier: 1.3.6.1.4.1.31103.1.107 2209 Descriptor (short name): fedfsNfsTransFlagRdma 2210 Usage: attribute type 2212 Object Identifier: 1.3.6.1.4.1.31103.1.108 2213 Descriptor (short name): fedfsNfsClassSimul 2214 Usage: attribute type 2216 Object Identifier: 1.3.6.1.4.1.31103.1.109 2217 Descriptor (short name): fedfsNfsClassHandle 2218 Usage: attribute type 2220 Object Identifier: 1.3.6.1.4.1.31103.1.110 2221 Descriptor (short name): fedfsNfsClassFileid 2222 Usage: attribute type 2224 Object Identifier: 1.3.6.1.4.1.31103.1.111 2225 Descriptor (short name): fedfsNfsClassWritever 2226 Usage: attribute type 2228 Object Identifier: 1.3.6.1.4.1.31103.1.112 2229 Descriptor (short name): fedfsNfsClassChange 2230 Usage: attribute type 2232 Object Identifier: 1.3.6.1.4.1.31103.1.113 2233 Descriptor (short name): fedfsNfsClassReaddir 2234 Usage: attribute type 2236 Object Identifier: 1.3.6.1.4.1.31103.1.114 2237 Descriptor (short name): fedfsNfsReadRank 2238 Usage: attribute type 2240 Object Identifier: 1.3.6.1.4.1.31103.1.115 2241 Descriptor (short name): fedfsNfsReadOrder 2242 Usage: attribute type 2244 Object Identifier: 1.3.6.1.4.1.31103.1.116 2245 Descriptor (short name): fedfsNfsWriteRank 2246 Usage: attribute type 2248 Object Identifier: 1.3.6.1.4.1.31103.1.117 2249 Descriptor (short name): fedfsNfsWriteOrder 2250 Usage: attribute type 2252 Object Identifier: 1.3.6.1.4.1.31103.1.118 2253 Descriptor (short name): fedfsNfsVarSub 2254 Usage: attribute type 2256 Object Identifier: 1.3.6.1.4.1.31103.1.119 2257 Descriptor (short name): fedfsNfsValidFor 2258 Usage: attribute type 2260 Object Identifier: 1.3.6.1.4.1.31103.1.1001 2261 Descriptor (short name): fedfsNsdbContainerInfo 2262 Usage: object class 2264 Object Identifier: 1.3.6.1.4.1.31103.1.1002 2265 Descriptor (short name): fedfsFsn 2266 Usage: object class 2268 Object Identifier: 1.3.6.1.4.1.31103.1.1003 2269 Descriptor (short name): fedfsFsl 2270 Usage: object class 2272 Object Identifier: 1.3.6.1.4.1.31103.1.1004 2273 Descriptor (short name): fedfsNfsFsl 2274 Usage: object class 2276 8. Glossary 2278 Administrator: user with the necessary authority to initiate 2279 administrative tasks on one or more servers. 2281 Admin Entity: A server or agent that administers a collection of 2282 fileservers and persistently stores the namespace information. 2284 Client: Any client that accesses the fileserver data using a 2285 supported filesystem access protocol. 2287 Federation: A set of server collections and singleton servers that 2288 use a common set of interfaces and protocols in order to provide 2289 to their clients a federated namespace accessible through a 2290 filesystem access protocol. 2292 Fileserver: A server exporting a filesystem via a network filesystem 2293 access protocol. 2295 Fileset: The abstraction of a set of files and the directory tree 2296 that contains them. A fileset is the fundamental unit of data 2297 management in the federation. 2299 Note that all files within a fileset are descendants of one 2300 directory, and that filesets do not span filesystems. 2302 Filesystem: A self-contained unit of export for a fileserver, and 2303 the mechanism used to implement filesets. The fileset does not 2304 need to be rooted at the root of the filesystem, nor at the export 2305 point for the filesystem. 2307 A single filesystem MAY implement more than one fileset, if the 2308 client protocol and the fileserver permit this. 2310 Filesystem Access Protocol: A network filesystem access protocol 2311 such as NFSv2 [RFC1094], NFSv3 [RFC1813], NFSv4 [RFC3530], or CIFS 2312 (Common Internet File System) [MS-SMB] [MS-SMB2] [MS-CIFS]. 2314 FSL (Fileset Location): The location of the implementation of a 2315 fileset at a particular moment in time. An FSL MUST be something 2316 that can be translated into a protocol-specific description of a 2317 resource that a client can access directly, such as an fs_location 2318 (for NFSv4), or share name (for CIFS). Note that not all FSLs 2319 need to be explicitly exported as long as they are contained 2320 within an exported path on the fileserver. 2322 FSN (Fileset Name): A platform-independent and globally unique name 2323 for a fileset. Two FSLs that implement replicas of the same 2324 fileset MUST have the same FSN, and if a fileset is migrated from 2325 one location to another, the FSN of that fileset MUST remain the 2326 same. 2328 Junction: A filesystem object used to link a directory name in the 2329 current fileset with an object within another fileset. The 2330 server-side "link" from a leaf node in one fileset to the root of 2331 another fileset. 2333 Namespace: A filename/directory tree that a sufficiently authorized 2334 client can observe. 2336 NSDB (Namespace Database) Service: A service that maps FSNs to FSLs. 2337 The NSDB may also be used to store other information, such as 2338 annotations for these mappings and their components. 2340 NSDB Node: The name or location of a server that implements part of 2341 the NSDB service and is responsible for keeping track of the FSLs 2342 (and related info) that implement a given partition of the FSNs. 2344 Referral: A server response to a client access that directs the 2345 client to evaluate the current object as a reference to an object 2346 at a different location (specified by an FSL) in another fileset, 2347 and possibly hosted on another fileserver. The client re-attempts 2348 the access to the object at the new location. 2350 Replica: A replica is a redundant implementation of a fileset. Each 2351 replica shares the same FSN, but has a different FSL. 2353 Replicas may be used to increase availability or performance. 2354 Updates to replicas of the same fileset MUST appear to occur in 2355 the same order, and therefore each replica is self-consistent at 2356 any moment. 2358 We do not assume that updates to each replica occur 2359 simultaneously. If a replica is offline or unreachable, the other 2360 replicas may be updated. 2362 Server Collection: A set of fileservers administered as a unit. A 2363 server collection may be administered with vendor-specific 2364 software. 2366 The namespace provided by a server collection could be part of the 2367 federated namespace. 2369 Singleton Server: A server collection containing only one server; a 2370 stand-alone fileserver. 2372 9. References 2374 9.1. Normative References 2376 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2377 Requirement Levels", BCP 14, RFC 2119, March 1997. 2379 [RFC2203] Eisler, M., Chiu, A., and L. Ling, "RPCSEC_GSS Protocol 2380 Specification", RFC 2203, September 1997. 2382 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2383 Schoenwaelder, Ed., "Structure of Management Information 2384 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2386 [RFC2743] Linn, J., "Generic Security Service Application Program 2387 Interface Version 2, Update 1", RFC 2743, January 2000. 2389 [RFC2849] Good, G., "The LDAP Data Interchange Format (LDIF) - 2390 Technical Specification", RFC 2849, June 2000. 2392 [RFC3530] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., 2393 Beame, C., Eisler, M., and D. Noveck, "Network File System 2394 (NFS) version 4 Protocol", RFC 3530, April 2003. 2396 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 2397 Resource Identifier (URI): Generic Syntax", STD 66, 2398 RFC 3986, January 2005. 2400 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 2401 Unique IDentifier (UUID) URN Namespace", RFC 4122, 2402 July 2005. 2404 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2405 Architecture", RFC 4291, February 2006. 2407 [RFC4510] Zeilenga, K., "Lightweight Directory Access Protocol 2408 (LDAP): Technical Specification Road Map", RFC 4510, 2409 June 2006. 2411 [RFC4511] Sermersheim, J., "Lightweight Directory Access Protocol 2412 (LDAP): The Protocol", RFC 4511, June 2006. 2414 [RFC4512] Zeilenga, K., "Lightweight Directory Access Protocol 2415 (LDAP): Directory Information Models", RFC 4512, 2416 June 2006. 2418 [RFC4513] Harrison, R., "Lightweight Directory Access Protocol 2419 (LDAP): Authentication Methods and Security Mechanisms", 2420 RFC 4513, June 2006. 2422 [RFC4516] Smith, M. and T. Howes, "Lightweight Directory Access 2423 Protocol (LDAP): Uniform Resource Locator", RFC 4516, 2424 June 2006. 2426 [RFC4517] Legg, S., "Lightweight Directory Access Protocol (LDAP): 2427 Syntaxes and Matching Rules", RFC 4517, June 2006. 2429 [RFC4519] Sciberras, A., "Lightweight Directory Access Protocol 2430 (LDAP): Schema for User Applications", RFC 4519, 2431 June 2006. 2433 [RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority (IANA) 2434 Considerations for the Lightweight Directory Access 2435 Protocol (LDAP)", BCP 64, RFC 4520, June 2006. 2437 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 2438 (TLS) Protocol Version 1.2", RFC 5246, August 2008. 2440 [RFC5661] Shepler, S., Eisler, M., and D. Noveck, "Network File 2441 System (NFS) Version 4 Minor Version 1 Protocol", 2442 RFC 5661, January 2010. 2444 9.2. Informative References 2446 [AFS] Howard, J., "An Overview of the Andrew File System", 2447 Proceeding of the USENIX Winter Technical Conference , 2448 1988. 2450 [FEDFS-ADMIN] 2451 Lentini, J., Everhart, C., Ellard, D., Tewari, R., and M. 2452 Naik, "Administration Protocol for Federated Filesystems", 2453 draft-ietf-nfsv4-federated-fs-admin (Work In Progress), 2454 2010. 2456 [FEDFS-DNS-SRV] 2457 Everhart, C., Adamson, W., and J. Zhang, "Using DNS SRV to 2458 Specify a Global File Name Space with NFS version 4", 2459 draft-ietf-nfsv4-federated-fs-dns-srv-namespace (Work In 2460 Progress), 2010. 2462 [MS-CIFS] Microsoft Corporation, "Common Internet File System (CIFS) 2463 Protocol Specification", MS-CIFS 2.0, November 2009. 2465 [MS-SMB] Microsoft Corporation, "Server Message Block (SMB) 2466 Protocol Specification", MS-SMB 17.0, November 2009. 2468 [MS-SMB2] Microsoft Corporation, "Server Message Block (SMB) Version 2469 2 Protocol Specification", MS-SMB2 19.0, November 2009. 2471 [RFC1094] Nowicki, B., "NFS: Network File System Protocol 2472 specification", RFC 1094, March 1989. 2474 [RFC1813] Callaghan, B., Pawlowski, B., and P. Staubach, "NFS 2475 Version 3 Protocol Specification", RFC 1813, June 1995. 2477 [RFC3254] Alvestrand, H., "Definitions for talking about 2478 directories", RFC 3254, April 2002. 2480 [RFC5662] Shepler, S., Eisler, M., and D. Noveck, "Network File 2481 System (NFS) Version 4 Minor Version 1 External Data 2482 Representation Standard (XDR) Description", RFC 5662, 2483 January 2010. 2485 [RFC5716] Lentini, J., Everhart, C., Ellard, D., Tewari, R., and M. 2486 Naik, "Requirements for Federated File Systems", RFC 5716, 2487 January 2010. 2489 Appendix A. Acknowledgments 2491 We would like to thank Andy Adamson of NetApp, Paul Lemahieu of EMC, 2492 Robert Thurlow of Sun Microsystems, and Mario Wurzl of EMC for 2493 helping to author this document. 2495 We would also like to thank George Amvrosiadis, Trond Myklebust, and 2496 Nicolas Williams for their comments. 2498 The extract.sh shell script and formatting conventions were first 2499 described by the authors of the NFSv4.1 XDR specification [RFC5662]. 2501 Authors' Addresses 2503 James Lentini 2504 NetApp 2505 1601 Trapelo Rd, Suite 16 2506 Waltham, MA 02451 2507 US 2509 Phone: +1 781-768-5359 2510 Email: jlentini@netapp.com 2512 Craig Everhart 2513 NetApp 2514 7301 Kit Creek Rd 2515 Research Triangle Park, NC 27709 2516 US 2518 Phone: +1 919-476-5320 2519 Email: everhart@netapp.com 2520 Daniel Ellard 2521 Raytheon BBN Technologies 2522 10 Moulton Street 2523 Cambridge, MA 02138 2524 US 2526 Phone: +1 617-873-8000 2527 Email: dellard@bbn.com 2529 Renu Tewari 2530 IBM Almaden 2531 650 Harry Rd 2532 San Jose, CA 95120 2533 US 2535 Email: tewarir@us.ibm.com 2537 Manoj Naik 2538 IBM Almaden 2539 650 Harry Rd 2540 San Jose, CA 95120 2541 US 2543 Email: manoj@almaden.ibm.com