RFC 5716: Requirements for Federated File Systems
In plain English — editorial summary, not part of the RFC
This document describes and lists the functional requirements of a federated file system and defines related terms. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5716
- Published
- January 2010
- Authors
- J. Lentini; C. Everhart; D. Ellard; R. Tewari; M. Naik
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7336Framework for Content Distribution Network Interconnection (CDNI)Current
August 2014
- RFC 7532Namespace Database (NSDB) Protocol for Federated File SystemsCurrent
March 2015
- RFC 7533Administration Protocol for Federated File SystemsCurrent
March 2015
- RFC 8000Requirements for NFSv4 Multi-Domain Namespace DeploymentCurrent
November 2016
- RFC 7711PKIX over Secure HTTP (POSH)Current
November 2015
- RFC 7712Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP)Current
November 2015
- RFC 5682Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCPCurrent
September 2009
- RFC 5681TCP Congestion ControlUpdated
September 2009
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?