RFC 8000: Requirements for NFSv4 Multi-Domain Namespace Deployment
In plain English — editorial summary, not part of the RFC
This document presents requirements for the deployment of the NFSv4 protocols for the construction of an NFSv4 file namespace in environments with multiple NFSv4 Domains. To participate in an NFSv4 multi-domain file namespace, the server must offer a multi-domain-capable file system and support RPCSEC_GSS for user authentication. In most instances, the server must also support identity-mapping services.
Document record
- Document ID
- RFC8000
- Published
- November 2016
- Authors
- A. Adamson; N. Williams
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5716Requirements for Federated File SystemsCurrent
January 2010
- RFC 8282Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic EngineeringCurrent
December 2017
- RFC 8685Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) ArchitectureUpdated
December 2019
- RFC 8006Content Delivery Network Interconnection (CDNI) MetadataCurrent
December 2016
- RFC 8007Content Delivery Network Interconnection (CDNI) Control Interface / TriggersCurrent
December 2016
- RFC 8008Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities SemanticsUpdated
December 2016
- RFC 7983Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram Transport Layer Security (DTLS)Updated
September 2016
- RFC 7975Request Routing Redirection Interface for Content Delivery Network (CDN) InterconnectionCurrent
October 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?