Sending Multiple Media Streams in a Single RTP Session
draft-ietf-avtcore-rtp-multi-stream-02

The information below is for an old version of the document
Document Type Active Internet-Draft (avtcore WG)
Last updated 2014-01-13
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 (if approved)                                M. Westerlund
Intended status: Standards Track                                Ericsson
Expires: July 17, 2014                                             Q. Wu
                                                                  Huawei
                                                              C. Perkins
                                                   University of Glasgow
                                                        January 13, 2014

         Sending Multiple Media Streams in a Single RTP Session
                 draft-ietf-avtcore-rtp-multi-stream-02

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 RTP Control Protocol (RTCP) messages are described.

   This document updates RFC 3550 in regards to handling of multiple
   SSRCs per endpoint in RTP sessions.

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 July 17, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Lennox, et al.           Expires July 17, 2014                  [Page 1]
Internet-Draft  Multiple Media Streams in an RTP Session    January 2014

   (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.  Multiple-Capturer Endpoints . . . . . . . . . . . . . . .   3
     3.2.  Multi-Media Sessions  . . . . . . . . . . . . . . . . . .   3
     3.3.  Multi-Stream Mixers . . . . . . . . . . . . . . . . . . .   4
   4.  Multi-Stream Endpoint RTP Media Recommendations . . . . . . .   4
   5.  Multi-Stream Endpoint RTCP Recommendations  . . . . . . . . .   4
     5.1.  RTCP Reporting Requirement  . . . . . . . . . . . . . . .   5
     5.2.  Initial Reporting Interval  . . . . . . . . . . . . . . .   5
     5.3.  Compound RTCP Packets . . . . . . . . . . . . . . . . . .   5
   6.  RTCP Considerations for Streams with Disparate Rates  . . . .   6
     6.1.  Timing out SSRCs  . . . . . . . . . . . . . . . . . . . .   8
     6.2.  Tuning RTCP transmissions . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Appendix A.  Changes From Earlier Versions  . . . . . . . . . . .  13
     A.1.  Changes From WG Draft -00 . . . . . . . . . . . . . . . .  13
     A.2.  Changes From Individual Draft -02 . . . . . . . . . . . .  13
     A.3.  Changes From Individual Draft -01 . . . . . . . . . . . .  14
     A.4.  Changes From Individual Draft -00 . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   At the time The Real-Time Transport Protocol (RTP) [RFC3550] was
   originally written, and for quite some time after, endpoints in RTP
   sessions typically only transmitted a single media stream per RTP
   session, where separate RTP sessions were typically used for each
   distinct media type.

   Recently, however, a number of scenarios have emerged (discussed
Show full document text