Network File System Version 4 (nfsv4)
|WG||Name||Network File System Version 4|
|Area||Transport Area (tsv)|
|Charter||charter-ietf-nfsv4-06-01 External Review (Message to Community, Selected by Secretariat)|
|Dependencies||Document dependency graph (SVG)|
|Jabber chat||Room address||xmpp:firstname.lastname@example.org?join|
Charter for Working Group
Network File System version 4 (NFSv4) is the IETF standard for file
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.
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
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
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.
Submit final document defining RPC-over-RDMA Version 2 (as Proposed Standard)
|Aug 2020||Submit final document describing use of NVMe in accessing a pNFS SCSI Layout (as Proposed Standard)|
Submit final document defining TLS use for RPC / NFS
|Done||Submit final document describing CM private data convention for RPC-over-RDMA version 1 (as Proposed Standard)|
Submit final document describing Transparent State Migration in NFSv4.1 (as Proposed Standard)
Submit final document describing NFSv4.1 trunking discovery (as Proposed Standard)
|Done||Submit final document describing NFSv4.0 trunking discovery (as Proposed Standard)|
|Done||WGLC for draft-ietf-nfsv4-migration-issues (Informational)|