RTP Payload Format Constraints

Document Type Replaced Internet-Draft (individual)
Authors Peter Thatcher  , Mo Zanaty  , Suhas Nandakumar  , Bo Burman  , Adam Roach  , Byron Campen 
Last updated 2015-10-19
Replaced by RFC 8851
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mmusic-rid
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


In this specification, we define a framework for identifying Source RTP Streams with the constraints on its payload format in the Session Description Protocol. This framework uses "rid" SDP attribute to: a) effectively identify the Source RTP Streams within a RTP Session, b) constrain their payload format parameters in a codec-agnostic way beyond what is provided with the regular Payload Types and c) enable unambiguous mapping between the Source RTP Streams to their media format specification in the SDP. Note-1: The name 'rid' is not yet finalized. Please refer to Section 12 for more details on the naming.


Peter Thatcher (pthatcher@google.com)
Mo Zanaty (mzanaty@cisco.com)
Suhas Nandakumar (snandaku@cisco.com)
Bo Burman (bo.burman@ericsson.com)
Adam Roach (adam@nostrum.com)
Byron Campen (bcampen@mozilla.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)