Real-Time Transport Protocol (RTP) Considerations for Endpoints Sending Multiple Media Streams
draft-lennox-avtcore-rtp-multi-stream-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-10-22
Replaced by rfc8108, draft-ietf-avtcore-rtp-multi-stream
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
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: April 25, 2013                                 October 22, 2012

Real-Time Transport Protocol (RTP) Considerations for Endpoints Sending
                         Multiple Media Streams
                draft-lennox-avtcore-rtp-multi-stream-01

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.

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 25, 2013.

Copyright Notice

   Copyright (c) 2012 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
   (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

Lennox & Westerlund      Expires April 25, 2013                 [Page 1]
Internet-Draft       RTP Multi-Stream Considerations        October 2012

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Use Cases For Multi-Stream Endpoints . . . . . . . . . . . . .  3
     3.1.  Multiple-Capturer Endpoints  . . . . . . . . . . . . . . .  3
     3.2.  Multi-Media Sessions . . . . . . . . . . . . . . . . . . .  4
     3.3.  Multi-Stream Mixers  . . . . . . . . . . . . . . . . . . .  4
   4.  Issue Cases  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  Cascaded Multi-party Conference with Source Projecting
           Mixers . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Multi-Stream Endpoint RTP Media Recommendations  . . . . . . .  5
   6.  Multi-Stream Endpoint RTCP Recommendations . . . . . . . . . .  5
     6.1.  RTCP Reporting Requirement . . . . . . . . . . . . . . . .  6
     6.2.  Initial Reporting Interval . . . . . . . . . . . . . . . .  6
     6.3.  Compound RTCP Packets  . . . . . . . . . . . . . . . . . .  6
   7.  RTCP Bandwidth Considerations When Sources have
       Greatly-Differing Bandwidths . . . . . . . . . . . . . . . . .  7
   8.  Grouping of RTCP Reception Statistics and Other Feedback . . .  7
     8.1.  Semantics and Behavior of Reporting Groups . . . . . . . .  8
     8.2.  RTCP Source Description (SDES) item for Reporting
           Groups . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     8.3.  SDP signaling for Reporting Groups . . . . . . . . . . . .  9
     8.4.  Bandwidth Benefits of RTCP Reporting Groups  . . . . . . .  9
     8.5.  Consequences of RTCP Reporting Groups  . . . . . . . . . . 10
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   10. Open Issues  . . . . . . . . . . . . . . . . . . . . . . . . . 11
   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 11
     12.2. Informative References . . . . . . . . . . . . . . . . . . 12
   Appendix A.  Changes From Earlier Versions . . . . . . . . . . . . 13
     A.1.  Changes From Draft -00 . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

Lennox & Westerlund      Expires April 25, 2013                 [Page 2]
Internet-Draft       RTP Multi-Stream Considerations        October 2012

1.  Introduction

   At the time The Real-Time Tranport Protocol (RTP) [RFC3550] was
   originally written, and for quite some time after, endpoints in RTP
Show full document text