RFC 7530: Network File System (NFS) Version 4 Protocol
In plain English — editorial summary, not part of the RFC
The Network File System (NFS) version 4 protocol is a distributed file system protocol that builds on the heritage of NFS protocol version 2 (RFC 1094) and version 3 (RFC 1813). Unlike earlier versions, the NFS version 4 protocol supports traditional file access while integrating support for file locking and the MOUNT protocol. In addition, support for strong security (and its negotiation), COMPOUND operations, client caching, and internationalization has been added. Of course, attention has been applied to making NFS version 4 operate well in an Internet environment. This document, together with the companion External Data Representation (XDR) description document, RFC 7531, obsoletes RFC 3530 as the definition of the NFS version 4 protocol.
Document record
- Document ID
- RFC7530
- Published
- March 2015
- Authors
- T. Haynes; D. Noveck
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 323
- Also known as
- —
- Obsoletes:
- RFC 3530
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3010 (2000)
- RFC 3530 (2003)
- RFC 7530 (2015)
Read the full history of Network File System (NFS) Version 4 Protocol →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7531Network File System (NFS) Version 4 External Data Representation Standard (XDR) DescriptionCurrent
March 2015
- RFC 7532Namespace Database (NSDB) Protocol for Federated File SystemsCurrent
March 2015
- RFC 7533Administration Protocol for Federated File SystemsCurrent
March 2015
- RFC 7538The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)Obsoleted
April 2015
- RFC 7540Hypertext Transfer Protocol Version 2 (HTTP/2)Obsoleted
May 2015
- RFC 7541HPACK: Header Compression for HTTP/2Current
May 2015
- RFC 7560Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) FeedbackCurrent
August 2015
- RFC 7496Additional Policies for the Partially Reliable Stream Control Transmission Protocol ExtensionCurrent
April 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?