Sending Multiple Media Streams in a Single RTP Session
draft-ietf-avtcore-rtp-multi-stream-06
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (avtcore WG)
|
|
Last updated |
|
2014-10-27
|
|
Replaces |
|
draft-lennox-avtcore-rtp-multi-stream
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
Roni Even
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
AVTCORE J. Lennox
Internet-Draft Vidyo
Updates: 3550, 4585 (if approved) M. Westerlund
Intended status: Standards Track Ericsson
Expires: April 30, 2015 Q. Wu
Huawei
C. Perkins
University of Glasgow
October 27, 2014
Sending Multiple Media Streams in a Single RTP Session
draft-ietf-avtcore-rtp-multi-stream-06
Abstract
This memo expands and clarifies the behaviour of Real-time Transport
Protocol (RTP) endpoints that use multiple synchronization sources
(SSRCs). This occurs, for example, when an endpoint sends multiple
media streams in a single RTP session. This memo updates RFC 3550
with regards to handling multiple SSRCs per endpoint in RTP sessions,
with a particular focus on RTCP behaviour. It also updates RFC 4585
to update and clarify the calculation of the timeout of SSRCs and the
inclusion of feedback messages.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 30, 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
Lennox, et al. Expires April 30, 2015 [Page 1]
Internet-Draft Multiple Media Streams in an RTP Session October 2014
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
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Use Cases For Multi-Stream Endpoints . . . . . . . . . . . . 3
3.1. Endpoints with Multiple Capture Devices . . . . . . . . . 3
3.2. Multiple Media Types in a Single RTP Session . . . . . . 3
3.3. Multiple Stream Mixers . . . . . . . . . . . . . . . . . 4
3.4. Multiple SSRCs for a Single Media Source . . . . . . . . 4
4. Use of RTP by endpoints that send multiple media streams . . 5
5. Use of RTCP by Endpoints that send multiple media streams . . 5
5.1. RTCP Reporting Requirement . . . . . . . . . . . . . . . 5
5.2. Initial Reporting Interval . . . . . . . . . . . . . . . 5
5.3. Aggregation of Reports into Compound RTCP Packets . . . . 6
5.3.1. Maintaining AVG_RTCP_SIZE . . . . . . . . . . . . . . 7
5.3.2. Scheduling RTCP with Multiple Reporting SSRCs . . . . 8
5.4. Use of RTP/AVPF Feedback . . . . . . . . . . . . . . . . 10
5.4.1. Choice of SSRC for Feedback Packets . . . . . . . . . 10
5.4.2. Scheduling an RTCP Feedback Packet . . . . . . . . . 11
6. RTCP Considerations for Streams with Disparate Rates . . . . 12
6.1. Timing out SSRCs . . . . . . . . . . . . . . . . . . . . 13
6.1.1. Problems with RTP/AVPF the T_rr_interval Parameter . 13
6.1.2. Avoiding Premature Timeout . . . . . . . . . . . . . 14
6.1.3. Interoperability Between RTP/AVP and RTP/AVPF . . . . 15
6.1.4. Updated SSRC Timeout Rules . . . . . . . . . . . . . 15
6.2. Tuning RTCP transmissions . . . . . . . . . . . . . . . . 16
6.2.1. RTP/AVP and RTP/SAVP . . . . . . . . . . . . . . . . 16
6.2.2. RTP/AVPF and RTP/SAVPF . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
9. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 19
Show full document text