RTP Considerations for Endpoints Sending Multiple Media Streams
draft-lennox-avtcore-rtp-multi-stream-02

 
Document
Type Replaced Internet-Draft (individual)
Last updated 2013-05-13 (latest revision 2013-02-25)
Replaced by draft-ietf-avtcore-rtp-multi-stream
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-avtcore-rtp-multi-stream
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-lennox-avtcore-rtp-multi-stream-02.txt

Abstract

This document expands and clarifies the behavior of the Real-Time Transport Protocol (RTP) endpoints when they are sending multiple media streams in a single RTP session. In particular, issues involving Real-Time Transport Control Protocol (RTCP) messages are described. This document updates RFC 3550 in regards to handling of multiple SSRCs per endpoint in RTP sessions.

Authors

Jonathan Lennox (jonathan@vidyo.com)
Magnus Westerlund (magnus.westerlund@ericsson.com)
Wenson Wu (sunseawq@huawei.com)
Colin Perkins (csp@csperkins.org)

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