RFC 6584: Simple Authentication Schemes for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols
In plain English — editorial summary, not part of the RFC
This document introduces four schemes that provide per-packet authentication, integrity, and anti-replay services in the context of the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) protocols. The first scheme is based on RSA Digital Signatures. The second scheme relies on the Elliptic Curve Digital Signature Algorithm (ECDSA). The third scheme relies on a Group- keyed Message Authentication Code (MAC). Finally, the fourth scheme merges the Digital Signature and group schemes. These schemes have different target use cases, and they do not all provide the same service. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6584
- Published
- April 2012
- Authors
- V. Roca
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5776Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) ProtocolsCurrent
April 2010
- RFC 3926FLUTE - File Delivery over Unidirectional TransportObsoleted
October 2004
- RFC 6581Enhanced Remote Direct Memory Access (RDMA) Connection EstablishmentCurrent
April 2012
- RFC 6580IANA Registries for the Remote Direct Data Placement (RDDP) ProtocolsCurrent
April 2012
- RFC 6627Overview of Pre-Congestion Notification EncodingCurrent
July 2012
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 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
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?