Signalling the Ability To Understand Packing of Multiple Telephony Events Into One RTP Packet
draft-taylor-mmusic-multev-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Tom Taylor | ||
Last updated | 2007-01-05 | ||
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
Section 2.5.1.5 of RFC 4733 specifies how an implementation of the telephony-event payload type can pack multiple short-duration event reports into one RTP packet. Because this capability was added to RFC 4733 in a fashion which is not backward compatible with RFC 2833, it is desirable that a sender have the means to determine whether the receiver understands such packets. This memo specifies a new SDP attribute, a=multev, to indicate that capability.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)