Browse Prior Art Database

Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols (RFC5776)

IP.com Disclosure Number: IPCOM000194674D
Original Publication Date: 2010-Apr-01
Included in the Prior Art Database: 2010-Apr-07

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

V. Roca: AUTHOR [+3]

Abstract

Many applications using multicast and broadcast communications require that each receiver be able to authenticate the source of any packet it receives as well as the integrity of these packets. This is the case with ALC [RFC5775] and NORM [RFC5740], two Content Delivery Protocols (CDPs) designed to transfer objects (e.g., files) reliably between a session's sender and several receivers. The NORM protocol is based on bidirectional transmissions. Each receiver acknowledges data received or, in case of packet erasures, asks for retransmissions. On the opposite, the ALC protocol is based on purely unidirectional transmissions. Reliability is achieved by means of the cyclic transmission of the content within a carousel and/or by the use of proactive Forward Error Correction (FEC) codes. Both protocols have in common the fact that they operate at the application level, on top of an erasure channel (e.g., the Internet) where packets can be lost (erased) during the transmission.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Internet Engineering Task Force (IETF)                           V. Roca Request for Comments: 5776                                 A. Francillon Category: Experimental                                        S. Faurite ISSN: 2070-1721                                                    INRIA                                                               April 2010

 Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in                the Asynchronous Layered Coding (ALC) and            NACK-Oriented Reliable Multicast (NORM) Protocols

Abstract

   This document details the Timed Efficient Stream Loss-Tolerant    Authentication (TESLA) packet source authentication and packet    integrity verification protocol and its integration within the    Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable    Multicast (NORM) content delivery protocols.  This document only    considers the authentication/integrity verification of the packets    generated by the session's sender.  The authentication and integrity    verification of the packets sent by receivers, if any, is out of the    scope of this document.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for examination, experimental implementation, and    evaluation.

   This document defines an Experimental Protocol for the Internet    community.  This document is a product of the Internet Engineering    Task Force (IETF).  It represents the consensus of the IETF    community.  It has received public review and has been approved for    publication by the Internet Engineering Steering Group (IESG).  Not    all documents approved by the IESG are a candidate for any level of    Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc5776.

 Roca, et al.                  Experimental                      [Page 1]
 RFC 5776                  TESLA in ALC and NORM               April 2010

 Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must ...