Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

A. Perrig
D. Song
R. Canetti
J. D. Tygar
B. Briscoe

Stream:

IETF

Source:

msec (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4082

Discuss this RFC: Send questions or comments to the mailing listmsec@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4082

Abstract

This document introduces Timed Efficient StreamLoss-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 alonecannot 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.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.