RFC 6580: IANA Registries for the Remote Direct Data Placement (RDDP) Protocols
In plain English — editorial summary, not part of the RFC
The original RFCs that specified the Remote Direct Data Placement (RDDP) protocol suite did not create IANA registries for RDDP error codes, operation codes, and function codes. Extensions to the RDDP protocols now require these registries to be created. This memo creates the RDDP registries, populates them with values defined in the original RDDP RFCs, and provides guidance to IANA for future assignment of code points within these registries. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6580
- Published
- April 2012
- Authors
- M. Ko; D. Black
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6581Enhanced Remote Direct Memory Access (RDMA) Connection EstablishmentCurrent
April 2012
- RFC 6584Simple Authentication Schemes for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) ProtocolsCurrent
April 2012
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 6627Overview of Pre-Congestion Notification EncodingCurrent
July 2012
- RFC 6646DECoupled Application Data Enroute (DECADE) Problem StatementCurrent
July 2012
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 6661Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of OperationCurrent
July 2012
- RFC 6662Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of OperationCurrent
July 2012
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?