[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

WG Review: Network File System Version 4 (nfsv4)



A modified charter has been submitted for Network File System Version 4 
(nfsv4) in the Transport Area of the IETF.


Network File System Version 4 (nfsv4)
-------------------------------------

 Current Status: Active Working Group

 Chair(s):
     Brian Pawlowski  <beepy@netapp.com>
     Robert Thurlow  <robert.thurlow@sun.com>

 Transport Area Director(s):
     Scott Bradner  <sob@harvard.edu>
     Allison Mankin  <mankin@psg.com>

 Transport Area Advisor:
     Scott Bradner  <sob@harvard.edu>

 Mailing Lists: 
     General Discussion:nfsv4-wg@sunroof.eng.sun.com
     To Subscribe:      majordomo@sunroof.eng.sun.com
     Archive:           http://playground.sun.com/pub/nfsv4/nfsv4-wg-archive

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.

=================================================
NEW CHARTER WORDING ADDITION:

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 

   OCT 02       ADs to submit API advancement internet draft as 
informational RFC (needed to advance GSSAPI to Draft 
Standard to allow advancement of NFS Version 4) 

   OCT 02       Strawman NFS V4 replication/migration protocol proposal 
submitted as an ID 

   NOV 02       Internet draft on NFS V4 migration/replication requirements 

   NOV 02       AD review of NFS V4 migration/replication requirements 
draft 

   DEC 02       Creation of internet draft on ONC RPC MIB 

   DEC 02       Revision of internet draft on NFS MIB 

   DEC 02       Depending on results of AD review of NFS Version 4 
migration/replication requirements document, review scope 
of task 

   FEB 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 

   MAR 03       Continued interoperability testing of NFS Version 4 

   MAY 03       Document full Interoperability tests for all NFSv4 features 

   MAY 03       Interoperability tests of NFS V4 migration/replication 

   MAY 03       Submit an NFS V4 migration/replication protocol to IESG for 
consideration as a Proposed Standard 

   MAY 03       Submit ONC RPC and NFS MIBs to IESG for consideration as 
Proposed Standards 

   JUN 03       Submit report on results of interoperability testing 

   AUG 03       Submit revised NFS Version 4 Proposed Standard for 
consideration as Draft Standard to IESG 


=================================================
NEW MILESTONES

FEB 03 ADs to submit API advancement internet draft as
                                nformational RFC (needed to advance GSSAPI to Draft
                                Standard to allow advancement of NFS Version 4)

DONE Strawman NFS V4 replication/migration protocol
                                proposal submitted as an ID

FEB 03 Internet draft on NFS V4 migration/replication requirements

FEB 03 AD review of NFS V4 migration/replication requirements draft

FEB 03 Creation of internet draft on ONC RPC MIB

JAN 03 Revision of internet draft on NFS MIB

JUN 03 Depending on results of AD review of NFS Version 4
                                migration/replication requirements document, review
                                scope of task

FEB 03 Draft problem statement I-D for NFS/RPC/RDDP submitted

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

MAR 03 Continued interoperability testing of NFS Version 4

MAR 03 Draft requirements document I-D for NFS/RPC/RDDP submitted

APR 03 AD review of NFS/RPC/RDDP progress and charter

MAY 03 Document full Interoperability tests for all NFSv4 features

JUL 03 Interoperability tests of NFS V4 migration/replication

JUN 03 Submit an NFS V4 migration/replication protocol to
                                IESG for consideration as a Proposed Standard

JUN 03 Submit ONC RPC and NFS MIBs to IESG for consideration as
                                Proposed Standards

JUN 03 Submit report on results of *NFS VERSION 4 RFC*
                                interoperability testing

AUG 03 Submit revised NFS Version 4 Proposed Standard for
                                consideration as Draft Standard to IESG