Network File System Version 4 (nfsv4) Internet Drafts
| RPC: Remote Procedure Call Protocol Specification Version 2 | |||||||||||||||||
|
This document describes the ONC (Open Network Computing) Remote Procedure Call (ONC RPC Version 2) protocol as it is currently deployed and accepted. It is meant to supersede [RFC1831]. | ||||||||||||||||
| NFS RDMA Problem Statement | |||||||||||||||||
|
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 | |||||||||||||||||
|
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 | |||||||||||||||||
|
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 | |||||||||||||||||
|
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 | |||||||||||||||||
|
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 | |||||||||||||||||
|
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 | |||||||||||||||||
|
This Internet-Draft provides the XDR description for NFSv4 minor version one. | ||||||||||||||||
| RPCSEC_GSS Version 2 | |||||||||||||||||
|
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. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Network File System Version 4 (nfsv4)
Last Modified: 2008-04-23
Additional information is available at tools.ietf.org/wg/nfsv4
Chair(s):
Transport Area Director(s):
Transport Area Advisor:
Mailing Lists:
General Discussion: nfsv4@ietf.orgTo Subscribe: https://www1.ietf.org/mailman/listinfo/nfsv4
Archive: http://www.ietf.org/mail-archive/web/nfsv4/index.html
Description of Working Group:
The objective of this working group is to advance the state of NFStechnology by producing specifications to extend the original NFS
Version 4 work (RFC 3010) to provide additional capabilities, as
described below.
o NFS version 4
Advance the protocol along the standards track, coordinating the
development of test suites to provide a high level of implementation
quality. The ONC RPC standards that NFSv4 references must also be
advanced. This includes work to make NFSv4 and the underlying ONC RPC
protocol compatible with IPv6. Specifically, we will advance RFC
3010, RFC 1831, RFC 1833 and RFC 2203 to Draft Standard. The working
group will help advance related security RFCs, specifically through
the definition of a method to advance APIs.
o Replication and Migration
The original working group defined a mechanism for NFS clients and
servers to support replication and migration of data transparently
to an application. Left undefined in the initial work was the
server back end migration and replication mechanism. The working
group will produce a draft submission of a replication/migration
protocol that supports NFS Version 4 clients - needed to create and
maintain replicated filesystems as well as migrating filesystems
from one location to another - and servers for consideration as
Proposed Standard.
o Management
The working group will produce a draft submission for consideration
as Proposed Standard of a management MIBs to provide better
management and administration capabilities for NFS and ONC RPC.
o Minor Versions
NFS Version 4 contains within it the capability for minor versioning.
Some discussions within the working group suggest addressing
additional requirements over the original charter. The WG will work
to identify additional requirements for NFSv4 and determine if they
are appropriate and worthwhile for a minor version. This work may
lead to proposals for additional work items. If it does a specific
proposal to add these work items to the charter will be forwarded to
the IESG and IAB.
o RDMA/RDDP enabling
The performance benefit of RDMA/RDDP transports in NFS-related
applications, by reducing the overhead of data and metadata
exchange, has been demonstrated sufficiently such that the
working group will pursue in parallel enabling NFS and RPC over
the transport defined by the RDDP working group. The WG will
restrict its initial activities to defining the problem
statement and specifying the requirements for possible
extensions to RPC and NFS (in the context of a minor
revision).
Goals and Milestones:
| Done | Issue strawman Internet-Draft for v4 | |
| Done | Submit Initial Internet-Draft of requirements document | |
| Done | Submit Final Internet-Draft of requirements document | |
| Done | AD reassesses WG charter | |
| Done | Submit v4 Internet-Draft sufficient to begin prototype implementations | |
| Done | Begin Interoperability testing of prototype implementations | |
| Done | Submit NFS version 4 to IESG for consideration as a Proposed Standard. | |
| Done | Conduct final Interoperability tests | |
| Done | Conduct full Interoperability tests for all NFSv4 features | |
| Done | Update API advancement draft | |
| Done | Form core design team to work on NFS V4 migration/replication requirements and protocol | |
| Done | Submit revised NFS Version 4 specification (revision to RFC 3010) to IESG for consideration as a Proposed Standard | |
| Done | Strawman NFS V4 replication/migration protocol proposal submitted as an ID | |
| Mar 2003 | ADs to submit API advancement internet draft as informational RFC (needed to advance GSSAPI to Draft Standard to allow advancement of NFS Version 4) | |
| Mar 2003 | Continued interoperability testing of NFS Version 4 | |
| Apr 2003 | Internet draft on NFS V4 migration/replication requirements | |
| Apr 2003 | AD review of NFS V4 migration/replication requirements draft | |
| Apr 2003 | Creation of internet draft on ONC RPC MIB | |
| Apr 2003 | Revision of internet draft on NFS MIB | |
| Apr 2003 | Draft problem statement I-D for NFS/RPC/RDDP submitted | |
| May 2003 | Document full Interoperability tests for all NFSv4 features | |
| Jun 2003 | Depending on results of AD review of NFS Version 4 migration/replication requirements document, review scope of task | |
| Jun 2003 | Submit related Proposed Standards required by NFS Version 4 for consideration as Draft Standards to IESG - RFCs 1831, 1833, 2203, 2078, 2744, RFC 1964, & 2847 | |
| Jun 2003 | Draft requirements document I-D for NFS/RPC/RDDP submitted | |
| Jun 2003 | Submit ONC RPC and NFS MIBs to IESG for consideration as Proposed Standards | |
| Jun 2003 | Submit an NFS V4 migration/replication protocol to IESG for consideration as a Proposed Standard | |
| Jun 2003 | Submit report on results of NFS version 4 RFC interoperability testing | |
| Jul 2003 | AD review of NFS/RPC/RDDP progress and charter | |
| Jul 2003 | Interoperability tests of NFS V4 migration/replication | |
| Aug 2003 | Submit revised NFS Version 4 Proposed Standard for consideration as Draft Standard to IESG |
Internet-Drafts:
RPC: Remote Procedure Call Protocol Specification Version 2 (58706 bytes)NFS RDMA Problem Statement (40713 bytes)
Remote Direct Memory Access Transport for Remote Procedure Call (89387 bytes)
NFS Direct Data Placement (26264 bytes)
NFS Version 4 Minor Version 1 (1450231 bytes)
pNFS Block/Volume Layout (67391 bytes)
Object-based pNFS Operations (76980 bytes)
NFSv4 Minor Version 1 XDR Description (125103 bytes)
RPCSEC_GSS Version 2 (22457 bytes)
Request For Comments:
NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5 (RFC 2623) (42521 bytes)NFS Version 4 Design Considerations (RFC 2624) (52891 bytes)
NFS version 4 (RFC 3010) (450434 bytes) obsoletes RFC 1813,RFC 1094/ obsoleted by RFC 3530
Network File System (NFS) version 4 Protocol (RFC 3530) (600986 bytes) obsoletes RFC 3010
XDR: External Data Representation Standard (RFC 4506) (55477 bytes)
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
