RFC 5665: IANA Considerations for Remote Procedure Call (RPC) Network Identifiers and Universal Address Formats
In plain English — editorial summary, not part of the RFC
This document lists IANA Considerations for Remote Procedure Call (RPC) Network Identifiers (netids) and RPC Universal Network Addresses (uaddrs). This document updates, but does not replace, RFC 1833. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5665
- Published
- January 2010
- Authors
- M. Eisler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 14
- Also known as
- —
- Updates:
- RFC 1833
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5664Object-Based Parallel NFS (pNFS) OperationsCurrent
January 2010
- RFC 5666Remote Direct Memory Access Transport for Remote Procedure CallObsoleted
January 2010
- RFC 5667Network File System (NFS) Direct Data PlacementObsoleted
January 2010
- RFC 5663Parallel NFS (pNFS) Block/Volume LayoutUpdated
January 2010
- RFC 5662Network File System (NFS) Version 4 Minor Version 1 External Data Representation Standard (XDR) DescriptionCurrent
January 2010
- RFC 5661Network File System (NFS) Version 4 Minor Version 1 ProtocolObsoleted
January 2010
- RFC 5681TCP Congestion ControlUpdated
September 2009
- RFC 5682Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCPCurrent
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?