RTP Payload Format for Keying-Information Stream (KS)
draft-harrison-avt-rtpkeys-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Chuck Harrison | ||
| Last updated | 2001-04-30 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
[Note: This draft is preliminary and is believed to contain errors and omissions.] This memo describes an RTP payload format (KS) which transports cryptographic key information for encrypted media streams. The media streams themselves are transported independently, and may or may not be carried by RTP. The KS payload format makes particular provision for media carried by SRTP [4]. The payload carried over KS contains the information necessary for seamlessly applying new decryption keys during an active session, by means of byte-granularity pointers referencing into the protected stream. The KS payload is based on CMS [2] and is scalable to a wide variety of streaming media
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)