RFC 4082: Timed Efficient Stream Loss-Tolerant Authentication (TESLA): Multicast Source Authentication Transform Introduction
In plain English — editorial summary, not part of the RFC
This document introduces Timed Efficient Stream Loss-tolerant Authentication (TESLA). TESLA allows all receivers to check the integrity and authenticate the source of each packet in multicast or broadcast data streams. TESLA requires no trust between receivers, uses low-cost operations per packet at both sender and receiver, can tolerate any level of loss without retransmissions, and requires no per-receiver state at the sender. TESLA can protect receivers against denial of service attacks in certain circumstances. Each receiver must be loosely time-synchronized with the source in order to verify messages, but otherwise receivers do not have to send any messages. TESLA alone cannot support non-repudiation of the data source to third parties. This informational document is intended to assist in writing standardizable and secure specifications for protocols based on TESLA in different contexts. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4082
- Published
- June 2005
- Authors
- A. Perrig; D. Song; R. Canetti; J. D. Tygar; B. Briscoe
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4059Internet X.509 Public Key Infrastructure Warranty Certificate ExtensionCurrent
May 2005
- RFC 4106The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)Current
June 2005
- RFC 4056Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS)Current
June 2005
- RFC 4055Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileUpdated
June 2005
- RFC 4046Multicast Security (MSEC) Group Key Management ArchitectureCurrent
May 2005
- RFC 4120The Kerberos Network Authentication Service (V5)Updated
July 2005
- RFC 4043Internet X.509 Public Key Infrastructure Permanent IdentifierCurrent
May 2005
- RFC 4121The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2Updated
July 2005
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?