Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP
draft-ietf-mmusic-mux-exclusive-01

The information below is for an old version of the document
Document Type Active Internet-Draft (mmusic WG)
Last updated 2016-02-06
Replaces draft-holmberg-mmusic-mux-exclusive
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        C. Holmberg
Internet-Draft                                                  Ericsson
Intended status: Standards Track                        February 6, 2016
Expires: August 9, 2016

    Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP
                   draft-ietf-mmusic-mux-exclusive-01

Abstract

   This document defines a new SDP media-level attribute, 'rtcp-mux-
   exclusive', that can be used by an endpoint to indicate exclusive
   support of RTP/RTCP multiplexing.

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 August 9, 2016.

Copyright Notice

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

Holmberg                 Expires August 9, 2016                 [Page 1]
Internet-Draft           Exclusive RTP/RTCP Mux            February 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  SDP rtcp-mux-exclusive Attribute  . . . . . . . . . . . . . .   3
   4.  SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . .   3
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Generating the Initial SDP Offer  . . . . . . . . . . . .   4
     4.3.  Generating the Answer . . . . . . . . . . . . . . . . . .   4
     4.4.  Offerer Processing of the SDP Answer  . . . . . . . . . .   4
     4.5.  Modifying the Session . . . . . . . . . . . . . . . . . .   5
   5.  ICE Considerations  . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   [RFC5761] defines how to multiplex RTP and RTCP on a single address
   and port, referred to as RTP/RTCP multiplexing.  [RFC5761] also
   defines an Session Description Protocol (SDP) [RFC4566] attribute,
   'rtcp-mux' that can be used by entities to indicate support, and
   negotiate usage of, RTP/RTCP multiplexing.

   As defined in [RFC5761], if the peer endpoint does not support RTP/
   RTCP multiplexing, there must be a fallback to usage of separate
   ports for RTP and RTCP.

   The RTCWEB WG has defined that support of the fallback mentioned
   above is optional.  Therefore, there is a need for a mechanism that
   allows an endpoint to indicate exclusive support of RTP/RTCP
   multiplexing, meaning that endpoint only supports RTP/RTCP
   multiplexing and is not able to fallback to usage of separate ports
   for RTP and RTCP.

   This document defines a new SDP media-level attribute, 'rtcp-mux-
   exclusive', that can be used to indicate exclusive support of RTP/
   RTCP multiplexing.

   The document also describes the Interactive Connectivity
   Establishment (ICE) [I-D.ietf-ice-rfc5245bis] considerations when
   indicating exclusive support of RTP/RTCP multiplexing.

Holmberg                 Expires August 9, 2016                 [Page 2]
Internet-Draft           Exclusive RTP/RTCP Mux            February 2016

2.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text