Using Simulcast in SDP and RTP Sessions
draft-ietf-mmusic-sdp-simulcast-01

The information below is for an old version of the document
Document Type Active Internet-Draft (mmusic WG)
Last updated 2015-07-21
Replaces draft-burman-mmusic-sdp-simulcast
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Oct 2017 - Submit Using Simulca... )
Document shepherd Flemming Andreasen
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Flemming Andreasen" <fandreas@cisco.com>
Network Working Group                                          B. Burman
Internet-Draft                                             M. Westerlund
Intended status: Standards Track                                Ericsson
Expires: January 22, 2016                                  S. Nandakumar
                                                               M. Zanaty
                                                                   Cisco
                                                           July 21, 2015

                Using Simulcast in SDP and RTP Sessions
                   draft-ietf-mmusic-sdp-simulcast-01

Abstract

   In some application scenarios it may be desirable to send multiple
   differently encoded versions of the same media source in independent
   RTP streams.  This is called simulcast.  This document discusses the
   best way of accomplishing simulcast in RTP and how to signal it in
   SDP.  A solution is defined by making an extension to SDP, and using
   RTP/RTCP identification methods to relate RTP streams belonging to
   the same media source.  The SDP extension consists a new media level
   SDP attribute that express capability to send and/or receive
   simulcast RTP streams.  One part of the RTP/RTCP identification
   method is included as a reference to a separate document, since it is
   useful also for other purposes.

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 January 22, 2016.

Copyright Notice

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

Burman, et al.          Expires January 22, 2016                [Page 1]
Internet-Draft                  Simulcast                      July 2015

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Reaching a Diverse Set of Receivers . . . . . . . . . . .   5
     3.2.  Application Specific Media Source Handling  . . . . . . .   6
     3.3.  Receiver Adaptation in Multicast/Broadcast  . . . . . . .   6
     3.4.  Receiver Media Source Preferences . . . . . . . . . . . .   7
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Proposed Solution Overview  . . . . . . . . . . . . . . . . .   9
   6.  Proposed Solution . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Simulcast Capability  . . . . . . . . . . . . . . . . . .   9
       6.1.1.  Declarative Use . . . . . . . . . . . . . . . . . . .  11
       6.1.2.  Offer/Answer Use  . . . . . . . . . . . . . . . . . .  11
     6.2.  Relating Simulcast Versions . . . . . . . . . . . . . . .  13
     6.3.  Signaling Examples  . . . . . . . . . . . . . . . . . . .  13
       6.3.1.  Unified Plan Client . . . . . . . . . . . . . . . . .  13
       6.3.2.  Multi-Source Client . . . . . . . . . . . . . . . . .  15
   7.  Network Aspects . . . . . . . . . . . . . . . . . . . . . . .  16
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  18
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  18
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     12.2.  Informative References . . . . . . . . . . . . . . . . .  19
   Appendix A.  Changes From Earlier Versions  . . . . . . . . . . .  21
Show full document text