Sending Multiple Types of Media in a Single RTP Session
draft-ietf-avtcore-multi-media-rtp-session-07

The information below is for an old version of the document
Document Type Active Internet-Draft (avtcore WG)
Last updated 2015-03-09
Replaces draft-westerlund-avtcore-multi-media-rtp-session
Stream IETF
Intended RFC status (None)
Formats plain text pdf html 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 WG                                                 M. Westerlund
Internet-Draft                                                  Ericsson
Updates: 3550, 3551 (if approved)                             C. Perkins
Intended status: Standards Track                   University of Glasgow
Expires: September 10, 2015                                    J. Lennox
                                                                   Vidyo
                                                           March 9, 2015

        Sending Multiple Types of Media in a Single RTP Session
             draft-ietf-avtcore-multi-media-rtp-session-07

Abstract

   This document specifies how an RTP session can contain RTP Streams
   with media from multiple media types such as audio, video, and text.
   This has been restricted by the RTP Specification, and thus this
   document updates RFC 3550 and RFC 3551 to enable this behaviour for
   applications that satisfy the applicability for using multiple media
   types in a single RTP 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 September 10, 2015.

Copyright Notice

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

Westerlund, et al.     Expires September 10, 2015               [Page 1]
Internet-Draft   Multiple Media Types in an RTP Session       March 2015

   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.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Overview of Solution  . . . . . . . . . . . . . . . . . . . .   5
   5.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Usage of the RTP session  . . . . . . . . . . . . . . . .   6
     5.2.  Signalled Support . . . . . . . . . . . . . . . . . . . .   6
     5.3.  Homogeneous Multi-party . . . . . . . . . . . . . . . . .   7
     5.4.  Reduced number of Payload Types . . . . . . . . . . . . .   8
     5.5.  Stream Differentiation  . . . . . . . . . . . . . . . . .   8
     5.6.  Non-compatible Extensions . . . . . . . . . . . . . . . .   8
   6.  RTP Session Specification . . . . . . . . . . . . . . . . . .   9
     6.1.  RTP Session . . . . . . . . . . . . . . . . . . . . . . .   9
     6.2.  Sender Source Restrictions  . . . . . . . . . . . . . . .  11
     6.3.  Payload Type Applicability  . . . . . . . . . . . . . . .  12
     6.4.  RTCP Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  Extension Considerations  . . . . . . . . . . . . . . . . . .  12
     7.1.  RTP Retransmission  . . . . . . . . . . . . . . . . . . .  13
     7.2.  Generic FEC . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  Signalling  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     8.1.  SDP-Based Signalling  . . . . . . . . . . . . . . . . . .  16
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  16
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     12.2.  Informative References . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   When the Real-time Transport Protocol (RTP) [RFC3550] was designed,
   close to 20 years ago, IP networks were different to those deployed
   at the time of this writing.  The virtually ubiquitous deployment of
   Network Address Translators (NAT) and Firewalls has since increased
   the cost and likely-hood of communication failure when using many
Show full document text