[nfsv4] WG Action: Rechartered Network File System Version 4 (nfsv4)
The IESG <firstname.lastname@example.org> Tue, 10 October 2017 18:21 UTC
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 25B84134687; Tue, 10 Oct 2017 11:21:36 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
From: The IESG <email@example.com>
To: "IETF-Announce" <firstname.lastname@example.org>
Cc: The IESG <email@example.com>, firstname.lastname@example.org, email@example.com
Content-Type: text/plain; charset="utf-8"
Date: Tue, 10 Oct 2017 11:21:36 -0700
Subject: [nfsv4] WG Action: Rechartered Network File System Version 4 (nfsv4)
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:email@example.com?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2017 18:21:36 -0000
The Network File System Version 4 (nfsv4) WG in the Transport Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the WG Chairs. Network File System Version 4 (nfsv4) ----------------------------------------------------------------------- Current status: Active WG Chairs: Spencer Shepler <firstname.lastname@example.org> Brian Pawlowski <email@example.com> Secretaries: Thomas Haynes <firstname.lastname@example.org> Assigned Area Director: Spencer Dawkins <email@example.com> Transport Area Directors: Spencer Dawkins <firstname.lastname@example.org> Mirja Kühlewind <email@example.com> Technical advisors: Leif Johansson <firstname.lastname@example.org> Mailing list: Address: email@example.com To subscribe: https://www.ietf.org/mailman/listinfo/nfsv4 Archive: https://mailarchive.ietf.org/arch/browse/nfsv4/ Group page: https://datatracker.ietf.org/group/nfsv4/ Charter: https://datatracker.ietf.org/doc/charter-ietf-nfsv4/ Network File System version 4 (NFSv4) is the IETF standard for file sharing. To maintain NFS Version 4's utility and currency, the NFSv4 working group is chartered to maintain the existing NFSv4.0, NFSv4.1, and NFSv4.2 protocols and specifications of related ONC components, such as those defining RPC, XDR, and RPCSECGSS. In addition, extensions will be developed, as necessary, to correct problems with the protocols as currently specified, to accommodate needed file system semantics, and to respond to technological developments in the areas of networking and persistent storage/memory. Maintenance The working group's experience has been that, as NFSv4 implementations mature and deployments continue, clarifications and corrections to existing RFCs are needed. These specification updates help vendors in delivering high-quality and interoperable implementations. The NFSv4 working group is chartered with vetting reported issues and determining correctness of submitted errata. In addition, some areas may need more concentrated work to correct the specifications already published, to deal with unanticipated interactions between features, or to respond to evolving expectations with regard to areas such as security. Since necessary changes in such cases are generally not appropriate for the errata system, the working group will assist in publication of new RFCs that provide implementation guidance, editorial modification or technical updates to existing RFCs. Since the new NFSv4 versioning framework has been approved, these technical updates to NFSv4 minor versions could include limited XDR changes. Extensions The NFSv4 protocol is designed to allow extension by the definition of new operations, new attributes, and new Parallel NFS layout types, as well as the creation of minor versions. Similarly, associated ONC protocol components that have a versioning/ extension framework can be incrementally extended, when necessary. The working group will discuss proposals for such extensions and assure that they have adequate technical review, including discussion of their interaction with existing features, before adopting them as working group items and helping to draft specification documents. Some likely motivations for such extensions would be to: Maximize NFS performance on advanced network fabrics. Accommodate new storage technologies. Provide facilities useful in management of NFS-accessed storage in large-scale virtualization environments. Provide more effective NFS response to security challenges. New milestones that fall within the scope specified in this charter can be added to the list below after working group consensus and upon approval by the responsible Area Director. Milestones: Jun 2018 - WGLC for draft-ietf-nfsv4-migration-issues (Informational) Jun 2018 - Submit final document describing use of NVMe in accessing a pNFS SCSI Layout (as Proposed Standard) Nov 2018 - Submit final document describing NFSv4.0 trunking discovery (as Proposed Standard) Mar 2019 - Submit final document describing NFSv4.1 trunking discovery (as Proposed Standard) Mar 2019 - Submit final document describing Transparent State Migration in NFSv4.1 (as Proposed Standard) Jun 2019 - Submit final document describing CM private data convention for RPC-over-RDMA version 1 (Informational) Sep 2019 - Submit final document describing pNFS RDMA Layout (as Proposed Standard) Dec 2019 - Submit final document defining RPC-over-RDMA Version 2 (as Proposed Standard)