Bandwidth and RTCP timing issues for multi-source endpoint
draft-wu-avtcore-multiplex-multisource-endpoint-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-10-11
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
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)
Audio/Video Transport Working Group                                Q. Wu
Internet-Draft                                                    Huawei
Intended status: Standards Track                        October 12, 2012
Expires: April 15, 2013

       Bandwidth and RTCP timing issues for multi-source endpoint
         draft-wu-avtcore-multiplex-multisource-endpoint-00.txt

Abstract

   This document discusses bandwidth issues and RTCP timing rule issues
   that arise when the multi-source endpoint multiplexing all the media
   type in one RTP session and follows RFC3550 timing rules.  It
   provides recommendations for multi-source host sending multiple media
   types in the same session.

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 15, 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Wu                       Expires April 15, 2013                 [Page 1]
Internet-Draft          Bandwidth and RTCP Timing           October 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  Standards Language . . . . . . . . . . . . . . . . . . . .  4
   3.  Use Cases for multi-source host communications . . . . . . . .  5
     3.1.  One to one Communication between multi-source endpoints  .  5
     3.2.  Multi-party Communication between multi-source
           endpoints  . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.3.  Communication between multi-source endpoint
           multiplexing each medium in separate RTP session and
           multiple-source endpoint multiplexing all mediums in
           one RTP session  . . . . . . . . . . . . . . . . . . . . .  7
   4.  Discuss  . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   5.  Recommendations  . . . . . . . . . . . . . . . . . . . . . . . 10
     5.1.  Choosing RTCP Bandwidth  . . . . . . . . . . . . . . . . . 10
     5.2.  Maintaining the number of session members and senders  . . 11
     5.3.  RTCP Reporting Interval calculation  . . . . . . . . . . . 12
     5.4.  RTCP reception report  . . . . . . . . . . . . . . . . . . 12
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 15
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 15
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16

Wu                       Expires April 15, 2013                 [Page 2]
Internet-Draft          Bandwidth and RTCP Timing           October 2012

1.  Introduction

   Multiplexing is a method by which multiple streams are combined into
   one stream over a shared medium.  In RTP, multiplexing is provided by
   the destination transport address (network address and port number)
   which is different for each RTP session.  Given each media type
   having different requirement for bandwidth, multiple media types
   (e.g., Separate audio and video streams) are usually not carried in a
   single RTP session.

   However for some applications that use unicast transport, e.g., in
   RTCWeb application, multiple-source hosts may use a different SSRC
   for each medium but sending them in the same RTP session, which
   reduces communication failure due to NAT and firewall when using
   multiple RTP sessions or multiple transport flow.  If these multi-
   source hosts still follow RFC3550 timing rules, audio and video are
   multiplexed onto a single RTP session and share a common session
Show full document text