RFC 6688: Parallel NFS (pNFS) Block Disk Protection
In plain English — editorial summary, not part of the RFC
Parallel NFS (pNFS) extends the Network File System version 4 (NFSv4) to enable direct client access to file data on storage devices and bypass the NFSv4 server. This can increase both performance and parallelism, but it requires additional client functionality, some of which depends upon the type of storage used. The pNFS specification for block storage (RFC 5663) describes how clients can identify the volumes used for pNFS, but this mechanism requires communication with the NFSv4 server. This document updates RFC 5663 to add a mechanism that enables identification of block storage devices used by pNFS file systems without communicating with the server. This enables clients to control access to pNFS block devices when the client initially boots, as opposed to waiting until the client can communicate with the NFSv4 server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6688
- Published
- July 2012
- Authors
- D. Black; J. Glasgow; S. Faibish
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 5663
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5661Network File System (NFS) Version 4 Minor Version 1 ProtocolObsoleted
January 2010
- RFC 7204Requirements for Labeled NFSCurrent
April 2014
- RFC 7569Registry Specification for Mandatory Access Control (MAC) Security Label FormatsCurrent
July 2015
- RFC 5667Network File System (NFS) Direct Data PlacementObsoleted
January 2010
- RFC 5666Remote Direct Memory Access Transport for Remote Procedure CallObsoleted
January 2010
- RFC 5662Network File System (NFS) Version 4 Minor Version 1 External Data Representation Standard (XDR) DescriptionCurrent
January 2010
- RFC 5532Network File System (NFS) Remote Direct Memory Access (RDMA) Problem StatementCurrent
May 2009
- RFC 7861Remote Procedure Call (RPC) Security Version 3Current
November 2016
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?