"RPC: Remote Procedure Call Protocol Specification Version 2", Robert Thurlow, 30-Oct-08. ( bytes)

This document describes the ONC (Open Network Computing) Remote Procedure Call (ONC RPC Version 2) protocol as it is currently deployed and accepted. This document obsoletes [RFC1831].

"NFS RDMA Problem Statement", Thomas Talpey, Chet Juszczak, Intellectual Property, 21-Feb-08. ( bytes)

This draft addresses enabling the use of Remote Direct Memory Access (RDMA) by the Network File System (NFS) protocols. NFS implementations historically incur significant overhead due to data copies on end-host systems, as well as other processing overhead. The potential benefits of RDMA to these implementations are explored, and the reasons why RDMA is especially well-suited to NFS and network file protocols in general are evaluated.

"Remote Direct Memory Access Transport for Remote Procedure Call", Thomas Talpey, Brent Callaghan, Intellectual Property, 16-Apr-08. ( bytes)

A protocol is described providing Remote Direct Memory Access (RDMA) as a new transport for Remote Procedure Call (RPC). The RDMA transport binding conveys the benefits of efficient, bulk data transport over high speed networks, while providing for minimal change to RPC applications and with no required revision of the application RPC protocol, or the RPC protocol itself.

"NFS Direct Data Placement", Thomas Talpey, Brent Callaghan, Intellectual Property, 16-Apr-08. ( bytes)

This draft defines the bindings of the various Network File System (NFS) versions to the Remote Direct Memory Access (RDMA) operations supported by the RPC/RDMA transport protocol. It describes the use of direct data placement by means of server-initiated RDMA operations into client-supplied buffers for implementations of NFS versions 2, 3, 4 and 4.1 over such an RDMA transport.

"NFS Version 4 Minor Version 1", Spencer Shepler, Mike Eisler, David Noveck, 5-Sep-08. ( bytes)

This Internet-Draft describes NFS version 4 minor version one, including features retained from the base protocol and protocol extensions made subsequently. Major extensions introduced in NFS version 4 minor version one include: Sessions, Directory Delegations, and parallel NFS (pNFS).

"pNFS Block/Volume Layout", David Black, Stephen Fridella, Jason Glasgow, 11-Jun-08. ( bytes)

Parallel NFS (pNFS) extends NFSv4 to allow clients to directly access file data on the storage used by the NFSv4 server. This ability to bypass the server for data access can increase both performance and parallelism, but requires additional client functionality for data access, some of which is dependent on the class of storage used. The main pNFS operations draft specifies storage-class-independent extensions to NFS; this draft specifies the additional extensions (primarily data structures) for use of pNFS with block and volume based storage.

"Object-based pNFS Operations", Benny Halevy, Brent Welch, Jim Zelenka, 19-Jun-08. ( bytes)

This Internet-Draft provides a description of the object-based pNFS extension for NFSv4. This is a companion to the main pnfs specification in the NFSv4 Minor Version 1 Internet Draft, which is currently draft-ietf-nfsv4-minorversion1-23.

"NFSv4 Minor Version 1 XDR Description", Spencer Shepler, Mike Eisler, David Noveck, 5-Sep-08. ( bytes)

This Internet-Draft provides the XDR description for NFSv4 minor version one.

"RPCSEC_GSS Version 2", Mike Eisler, 9-Oct-08. ( bytes)

This Internet-Draft describes version 2 of the RPCSEC_GSS protocol. Version 2 is the same as Version 1 but adds support for channel bindings.

"IANA Considerations for RPC Net Identifiers and Universal Address Formats", Mike Eisler, 19-Aug-08. ( bytes)

This Internet-Draft lists IANA Considerations for RPC Network Identifiers (netids) and RPC Universal Network Addresses (uaddrs). This Internet-Draft updates, but does not replace, RFC1833.

"Using DNS SRV to Specify a Global File Name Space with NFS version 4", Craig Everhart, Andy Adamson, Jiaying Zhang, 26-Sep-08. ( bytes)

The NFS version 4 protocol provides a natural way for a collection of NFS file servers to collaborate in providing an organization-wide file name space. The DNS SRV RR allows a simple and appropriate way for an organization to publish the root of its name space, even to clients that might not be intimately associated with such an organization. DNS SRV can be used to join these organization-wide file name spaces together to allow construction of a global, uniform NFS version 4 file name space. This document refreshes the draft.

"Administration Protocol for Federated Filesystems", Daniel Ellard, Craig Everhart, James Lentini, Renu Tewari, Manoj Naik, 26-Sep-08. ( bytes)

This document describes the administration protocol for a federated file system that enables file access and namespace traversal across collections of independently administered fileservers. The protocol specifies a set of interfaces by which fileservers and collections of fileservers with different administrators can form a fileserver federation that provides a namespace composed of the filesystems physically hosted on and exported by the constituent fileservers.

"Requirements for Federated File Systems", Daniel Ellard, Craig Everhart, James Lentini, Renu Tewari, Manoj Naik, 26-Sep-08. ( bytes)

This draft describes and lists the functional requirements of a federated file system and defines related terms. Our intent is to use this draft as a starting point and refine it, with input and feedback from the file system community and other interested parties, until we reach general agreement. We will then begin, again with the help of any interested parties, to define standard, open federated file system protocols that satisfy these requirements and are suitable for implementation and deployment.

"NSDB Protocol for Federated Filesystems", Daniel Ellard, Craig Everhart, James Lentini, Renu Tewari, Manoj Naik, 26-Sep-08. ( bytes)

This document describes a file system federation protocol that enables file access and namespace traversal across collections of independently administered fileservers. The protocol specifies a set of interfaces by which fileservers and collections of fileservers with different administrators can form a fileserver federation that provides a namespace composed of the filesystems physically hosted on and exported by the constituent fileservers.

Return to Internet-Draft directory.

Return to IETF home page.