2.8.9 Network File System Version 4 (nfsv4)

NOTE: This charter is a snapshot of the 64th IETF Meeting in Vancouver, British Columbia Canada. It may now be out-of-date.

Last Modified: 2005-09-28


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: 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 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.

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

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


  • draft-ietf-nfsv4-rfc1832bis-06.txt
  • draft-ietf-nfsv4-nfs-rdma-problem-statement-03.txt
  • draft-ietf-nfsv4-rpcrdma-02.txt
  • draft-ietf-nfsv4-nfsdirect-02.txt
  • draft-ietf-nfsv4-directory-delegation-01.txt
  • draft-ietf-nfsv4-sess-02.txt
  • draft-ietf-nfsv4-referrals-00.txt
  • draft-even-xcon-pnc-00.txt
  • draft-ietf-nfsv4-pnfs-00.txt
  • draft-ietf-nfsv4-minorversion1-00.txt
  • draft-ietf-nfsv4-dns-rr-00.txt

    Request For Comments:

    RFC2623 PS NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5
    RFC2624 I NFS Version 4 Design Considerations
    RFC3010 PS NFS version 4
    RFC3530 PS Network File System (NFS) version 4 Protocol

    Current Meeting Report

    And maybe attach edited Welch notes?
    Network File System Version 4 (nfsv4)
        Spencer Shepler 
        Brian Pawlowski 
    AGENDA:  Tuesday, November 8, 2005: 13:00pm - 15:00 (2 hour)
    Subject to change
        Welcome and Introduction            (beepy)            2 min
        Agenda bash
            - Blue Sheets
            - NOTE WELL
    bepey went over agenda, no additions. Asked that planning of pNFS as
    poart of NFS Version 4 minor version plan be covered during Spencer's
        Identifying Implementations in NFSv4 (Eisler)         5 min
    Implementation IDs.  
    Dealing with interoperability problems is a constant pain, the servers
    and clients might want to know what each side is running as an environment.
    Idea is to solicit information from the other side to find OS version
    While number of clients is reducing their are still more than one of various
    flavors. Raw data on what server is seeing could be used to guide
    testing matrices.
    uname -a info essentially?  Use heuristics to determine other side
    is not necessarily simple.
    Trond raised that Linux kernel does not have a central respository
    cataloguing patch levels in a release to capture.
    Eisler mentioned security implications?
    We will attempt to come to consensus for inclusion in the
    first minor version.
        Low Infrastructure Mutual Authentication Using SPKM-3 5 min
    Summarized goals for SPKM3/LIPKEY attack in late '90's to gain
    similar public key security as in web applications.
    Admason and Olga wrote a new draft to clarify some issues.
    Called out specifically X.509 and mappings.  Adamson wants
    to leverage Globus security using open source for Grid computing.
    Shepler asks what should the WG do?  Eisler tried to pass off
    to Kitten WG, but they do not want to do mechanisms.  So Eisler
    will pursue individually.  There are flaws in current SPKM 3
    specification in NFS Version 4 spec.  So, we will address in 
    minor version?
    Eisler and Adamson to go off and produce spec for consideration.
        pNFS       (Goodson)                                  20 min
    Many updates folded in since Paris meeting.  Needs a few tweaks,
    wants more feedback.
    Some fixes to crash recovery specification.
    NetApp working on server prototype, Eshel working on one at IBM,
    UMich working on a Linux client and server, Sun will dust off their
    implementation.  Goodson suggests Connectathon testing.
    "No more morons" says beepy...
        pNFS block (Black)                                    10 min
    Sometime in next week will be -nfsv4- draft.
        pNFS objects (Welch)                                  5 min
    Brent updated draft.  There is an OSD2 in the spec.  Two versions
    of the OSD spec.
        Byte Range Delegation Proposal (Myklebust)            20 min
    Trond presented motivation for byte range delegations.
    A large streaming media/caching application - where chunks of static
    data are cacheable while appends proceed.
    Discussion about "partial file caching", synchronous vs.
    asynchronous notifications.
    Comparison of locking vs. byte range delegations.
    What are interactions with pNFS layouts?
    There was a back and forth on efficiency/implementability of fine-grained
    cache control.
        NFS Referrals / Migration Replication (Noveck)        10 min
    beepy to curl up with Noveck et. al. to curl up and define the *minimum*
    set of requirements of the transient state needed in addition to persistent
    state for migration and replication to work.
        NFS Version 4 ACLs (Falkner / Week)                   15 min
    Sam Falkner and Lisa Weeks.
    Interaction of Mode and ACLs, end user complaints and security
    issues.  Modes being ignored with inheritable ACEs.
    Behaviour of ACLs in event of ID mapping.
    Should Windows semantics be included?
    POSIX ACLs vs. NFS V4 native ACLs. In Solaris.
    Goal is to get as working group item to be informational RFC?
    Is that the correct goal?
    Free standing standards doc...
    Follow up off line on how to best pursue the semantic/correctness
    with beepy and Shepler and David Black on how best to handle...
        Prep for WG last call on RPC/RDMA I-Ds (Talpey)       2 min
    Problem statement essentially unchanged.
    Clean-ups done?  NetID stuff? 
        Minor Version Plan (Shepler)                          20 min
    Minor version and pNFS - plan presented.
    SNIA meeting last week of January in San Jose - one trip...
    Try to propose a meeting time... beepy....
    David Black, and Brent Welch and Spencer and beepy to converge on 
    strategy for files/blocks/objects specs.
        Wrapup                              (beepy)            1 m


    NFSv4 ImpID
    pNFS update
    Byte Range Delegation Proposal
    NFS Referrals / Migration Replication
    NFS Version 4 ACLs
    Minor Version Plan