Network File System version 4 Protocol
RFC 3530, “Network File System version 4 Protocol”, is a Proposed Standard document published in April 2003 by S. Shepler, B. Callaghan, D. Robinson, R. Thurlow, C. Beame, M. Eisler, D. Noveck. It obsoletes RFC 3010. It has been obsoleted by RFC 7530 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
The Network File System (NFS) version 4 is a distributed filesystem protocol which owes heritage to 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 have been added. Of course, attention has been applied to making NFS version 4 operate well in an Internet environment. This document replaces RFC 3010 as the definition of the NFS version 4 protocol. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3530 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3529 Using Extensible Markup Language-Remote Procedure Calling in Blocks Extensible Exchange Protocol
- RFC 3531 A Flexible Method for Managing the Assignment of Bits of an IPv6 Address Block
- RFC 3528 Mesh-enhanced Service Location Protocol
- RFC 3532 Requirements for the Dynamic Partitioning of Switching Elements
- RFC 3527 Link Selection sub-option for the Relay Agent Information Option for DHCPv4
- RFC 3533 The Ogg Encapsulation Format Version 0
- RFC 3526 More Modular Exponential Diffie-Hellman groups for Internet Key Exchange
- RFC 3534 The application/ogg Media Type