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

The information below is for an old version of the document
Document Type Active Internet-Draft (mmusic WG)
Last updated 2016-01-12
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
Updates: 5761 (if approved)                             January 12, 2016
Intended status: Standards Track
Expires: July 15, 2016

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

Abstract

   This document defines how an endpoint can indicate exclusive support
   of RTP/RTCP multiplexing using the Session Description Protocol
   (SDP).

   The document updates RFC 5761, by defining how the SDP 'rtcp'
   attribute is used, together with the SDP 'rtcp-mux' attribute, 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 July 15, 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

Holmberg                  Expires July 15, 2016                 [Page 1]
Internet-Draft           Exclusive RTP/RTCP Mux             January 2016

   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.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Update to RFC 5761  . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  RFC 5761 Section 5.1.1 Update . . . . . . . . . . . . . .   3
     4.3.  RFC 5761 Section 5.1.3 Update . . . . . . . . . . . . . .   4
     4.4.  Issues And TBDs . . . . . . . . . . . . . . . . . . . . .   5
   5.  ICE Considerations  . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   [RFC5761] defines how to multiplex RTP and RTCP on a single 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 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.  However, the RTCWEB WG have defined that
   support of the fallback is optional.  Therefore, there needs to be a
   mechanism for an endpoint to be able to indicate exclusive support of
   RTP/RTCP multiplexing, i.e. to be able to indicate that the endpoint
   only supports RTP/RTCP multiplexing and is not able to fallback to
   usage of separate ports for receiving RTP and RTCP.

   This document describes a mechanism, how the SDP 'rtcp-mux' attribute
   [RFC5761] and the SDP 'rtcp' attribute [RFC3605] can be used to
   indicate exclusive support of RTP/RTCP multiplexing.  The document
   updates sections 5.1.1 and 5.1.3 of [RFC5761] in order to enable
   usage of the mechanism.

   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 July 15, 2016                 [Page 2]
Internet-Draft           Exclusive RTP/RTCP Mux             January 2016
Show full document text