2.8.9 Network File System Version 4 (nfsv4)

Last Modified: 2003-08-01

Brian Pawlowski <beepy@netapp.com>
Spencer Shepler <spencer.shepler@sun.com>
Transport Area Director(s):
Allison Mankin <mankin@psg.com>
Jon Peterson <jon.peterson@neustar.biz>
Transport Area Advisor:
Jon Peterson <jon.peterson@neustar.biz>
Mailing Lists:
General Discussion: nfsv4@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/nfsv4
Archive: https://www1.ietf.org/mail-archive/working-groups/nfsv4/current/maillist.html
Description of Working Group:
The objective of this working group is to advance the state of NFS
technology 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.
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 03  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 03  Continued interoperability testing of NFS Version 4
Apr 03  Internet draft on NFS V4 migration/replication requirements
Apr 03  AD review of NFS V4 migration/replication requirements draft
Apr 03  Creation of internet draft on ONC RPC MIB
Apr 03  Revision of internet draft on NFS MIB
Apr 03  Draft problem statement I-D for NFS/RPC/RDDP submitted
May 03  Document full Interoperability tests for all NFSv4 features
Jun 03  Depending on results of AD review of NFS Version 4 migration/replication requirements document, review scope of task
Jun 03  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 03  Draft requirements document I-D for NFS/RPC/RDDP submitted
Jun 03  Submit ONC RPC and NFS MIBs to IESG for consideration as Proposed Standards
Jun 03  Submit an NFS V4 migration/replication protocol to IESG for consideration as a Proposed Standard
Jun 03  Submit report on results of NFS version 4 RFC interoperability testing
Jul 03  AD review of NFS/RPC/RDDP progress and charter
Jul 03  Interoperability tests of NFS V4 migration/replication
Aug 03  Submit revised NFS Version 4 Proposed Standard for consideration as Draft Standard to IESG
  • - draft-ietf-nfsv4-repl-mig-proto-01.txt
  • - draft-ietf-nfsv4-repl-mig-design-00.txt
  • - draft-ietf-nfsv4-rfc1832bis-01.txt
  • - draft-ietf-nfsv4-ccm-01.txt
  • - draft-ietf-nfsv4-secinfo-00.txt
  • - draft-ietf-nfsv4-rpc-iana-00.txt
  • - draft-ietf-nfsv4-rfc1831bis-00.txt
  • - draft-ietf-nfsv4-acl-mapping-00.txt
  • 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) obsoleted by RFC 3530
    Network File System (NFS) version 4 Protocol (RFC 3530) (600986 bytes)

    Current Meeting Report

    Network File System Version 4 (nfsv4)
        Spencer Shepler <Spencer.Shepler@sun.com>
        Brian Pawlowski <beepy@netapp.com>
    AGENDA:  Tuesday July 15th: 13:00pm - 14:00 (1 hour)
        Welcome and Introduction            (beepy)            1 min
        Agenda bash
        Bakeathon results                   (Shepler by proxy) 5 min
        Summary of NFS V4 Interim Meeting   (beepy)           10 min
        Summary of Linux NFS V4 Issues      (Myklebust)       10 min
        Review and discussion of NFS/RDMA
        Problem Statement                   (Talpey)          30 min
        Open discussion                     (beepy)            3 min
        Wrapup                              (Pawlowski)        1 m
    beepy presented the agenda - no additions. Noted well and blue sheets.
    Spencer to summarize Bakeathon results on alias. beepy gave a brief 
    summary of the interim meeting.  Materials for interim meeting can be 
    found at 
    beepy summarized the meeting - see the slides.
    Trond presented the Linux implementation.  Need Best 
    Practices/Implementation document.  Trond flagged scalability concerns with 
    state mgmt. Recovery is complicated. But, that said, the V4 spec is 
    holding up to implementation - no gotchas.
    Workaround for WCC stuff - when delegation disabled, V2 plus CTO. Talpey and 
    Trond ping-ponged the alternative to WCC. 
    But spec is fine.
    Tom Talpey presented the NFS/RDMA (RDDP) Problem Statement. See his 
    slides. Following edits will accept into working group as a working group 
    I believe our WG web page is still broken and misses approved charter 
    expansion language to cover the RDMA problem statement and 


    NFS RDMA Problem Statement
    Linux NFS V4 Issues