draft-ietf-mmusic-mux-exclusive-01.txt   draft-ietf-mmusic-mux-exclusive-02.txt 
Network Working Group C. Holmberg Network Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track February 6, 2016 Intended status: Standards Track February 15, 2016
Expires: August 9, 2016 Expires: August 18, 2016
Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP
draft-ietf-mmusic-mux-exclusive-01 draft-ietf-mmusic-mux-exclusive-02
Abstract Abstract
This document defines a new SDP media-level attribute, 'rtcp-mux- This document defines a new SDP media-level attribute, 'rtcp-mux-
exclusive', that can be used by an endpoint to indicate exclusive exclusive', that can be used by an endpoint to indicate exclusive
support of RTP/RTCP multiplexing. support of RTP/RTCP multiplexing.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 9, 2016. This Internet-Draft will expire on August 18, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 10 skipping to change at page 2, line 10
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. SDP rtcp-mux-exclusive Attribute . . . . . . . . . . . . . . 3 3. SDP rtcp-mux-exclusive Attribute . . . . . . . . . . . . . . 3
4. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 3 4. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 4
4.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Generating the Initial SDP Offer . . . . . . . . . . . . 4 4.2. Generating the Initial SDP Offer . . . . . . . . . . . . 4
4.3. Generating the Answer . . . . . . . . . . . . . . . . . . 4 4.3. Generating the Answer . . . . . . . . . . . . . . . . . . 4
4.4. Offerer Processing of the SDP Answer . . . . . . . . . . 4 4.4. Offerer Processing of the SDP Answer . . . . . . . . . . 5
4.5. Modifying the Session . . . . . . . . . . . . . . . . . . 5 4.5. Modifying the Session . . . . . . . . . . . . . . . . . . 5
5. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
9. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 6 9. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . 8 10.2. Informative References . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
[RFC5761] defines how to multiplex RTP and RTCP on a single address [RFC5761] defines how to multiplex RTP and RTCP on a single IP
and port, referred to as RTP/RTCP multiplexing. [RFC5761] also address and port, referred to as RTP/RTCP multiplexing. [RFC5761]
defines an Session Description Protocol (SDP) [RFC4566] attribute, also defines an Session Description Protocol (SDP) [RFC4566]
'rtcp-mux' that can be used by entities to indicate support, and attribute, 'rtcp-mux' that can be used by entities to indicate
negotiate usage of, RTP/RTCP multiplexing. support, and negotiate usage of, RTP/RTCP multiplexing.
As defined in [RFC5761], if the peer endpoint does not support RTP/ As defined in [RFC5761], if the peer endpoint does not support RTP/
RTCP multiplexing, there must be a fallback to usage of separate RTCP multiplexing, there must be a fallback to usage of separate
ports for RTP and RTCP. ports for RTP and RTCP.
The RTCWEB WG has defined that support of the fallback mentioned The RTCWEB WG has defined that support of the fallback mentioned
above is optional. Therefore, there is a need for a mechanism that above is optional. Therefore, there is a need for a mechanism that
allows an endpoint to indicate exclusive support of RTP/RTCP allows an endpoint to indicate exclusive support of RTP/RTCP
multiplexing, meaning that endpoint only supports RTP/RTCP multiplexing, meaning that endpoint only supports RTP/RTCP
multiplexing and is not able to fallback to usage of separate ports multiplexing and is not able to fallback to usage of separate ports
skipping to change at page 3, line 18 skipping to change at page 3, line 18
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. SDP rtcp-mux-exclusive Attribute 3. SDP rtcp-mux-exclusive Attribute
This section defines a new SDP media-level attribute, 'rtcp-mux- This section defines a new SDP media-level attribute, 'rtcp-mux-
exclusive'. exclusive'.
Name: rtcp-mux-exclusive Name: rtcp-mux-exclusive
Value: Value: N/A
Usage Level: media Usage Level: media
Charset Dependent: no Charset Dependent: no
Syntax:
rtcp-mux-exclusive
Example: Example:
a=rtcp-mux-exclusive a=rtcp-mux-exclusive
In an SDP offer, the offerer uses the SDP 'rtcp-mux-exclusive' In an SDP offer, the offerer uses the SDP 'rtcp-mux-exclusive'
attribute to indicate exclusive support of RTP/RTCP multiplexing for attribute to indicate exclusive support of RTP/RTCP multiplexing for
the RTP-based media associated with the SDP media description ("m=" the RTP-based media associated with the SDP media description ("m="
line). line).
In an SDP answer, the 'rtcp-mux-exclusive' attribute indicates that In an SDP answer, the 'rtcp-mux-exclusive' attribute indicates that
the answerer supports, and accepts usage of, RTP/RTCP multiplexing the answerer supports, and accepts usage of, RTP/RTCP multiplexing
for the RTP-based media associated with the SDP media description for the RTP-based media associated with the SDP media description
("m=" line). ("m=" line).
The usage of the SDP 'rtcp-mux-exclusive' attribute is only defined The usage of the SDP 'rtcp-mux-exclusive' attribute is only defined
for RTP-based media. for RTP-based media.
The mux category [I-D.ietf-mmusic-sdp-mux-attributes] for the 'rtcp-
mux-exclusive' attribute is 'NORMAL', which means that the attribute
can be associated with an individual media description, even if the
media description is multiplexed with other media descriptions
[I-D.ietf-mmusic-sdp-bundle-negotiation] with which the attribute is
not associated.
The 'rtcp-mux-exclusive' attribute applies to the whole associated
media description. The attribute MUST NOT be defined per source
(using the SDP 'ssrc' attribute [RFC5576]).
The SDP offer/answer [RFC3264] procedures associated with the The SDP offer/answer [RFC3264] procedures associated with the
attribute are defined in Section 4 attribute are defined in Section 4
4. SDP Offer/Answer Procedures 4. SDP Offer/Answer Procedures
4.1. General 4.1. General
This section defines the SDP offer/answer [RFC3264] procedures for This section defines the SDP offer/answer [RFC3264] procedures for
indicating exclusive support of, and negotiating usage of, RTP/RTCP indicating exclusive support of, and negotiating usage of, RTP/RTCP
multiplexing. multiplexing.
skipping to change at page 5, line 23 skipping to change at page 5, line 38
NOTE: This document does not mandate specific actions on how to NOTE: This document does not mandate specific actions on how to
terminate the RTP media. The offerer might e.g. send a new offer, terminate the RTP media. The offerer might e.g. send a new offer,
where the port value of the SDP media description is set to zero, in where the port value of the SDP media description is set to zero, in
order to terminate the RTP media. order to terminate the RTP media.
4.5. Modifying the Session 4.5. Modifying the Session
When an offerer sends a subsequent offer, if the offerer and answerer When an offerer sends a subsequent offer, if the offerer and answerer
have previously negotiated usage of RTP/RTCP multiplexing for the have previously negotiated usage of RTP/RTCP multiplexing for the
media associated with an RTP-based SDP media description ("m=" line) media associated with an RTP-based SDP media description ("m=" line),
using the SDP 'rtcp-mux-exclusive' attribute, the offerer SHOULD the offerer SHOULD associate an SDP 'rtcp-mux-exclusive' attribute
associate an SDP 'rtcp-mux-exclusive' attribute and an SDP 'rtcp-mux' and an SDP 'rtcp-mux' attribute with the corresponding SDP media
attribute with the corresponding SDP media description ("m=" line). description ("m=" line). If the offerer does not associate the
If the offerer does not associate the attributes with the attributes with the corresponding SDP media description ("m=" line)
corresponding SDP media description ("m=" line) it is an indication it is an indication that the offerer no longer wants to use RTP/RTCP
that the offerer no longer wants to use RTP/RTCP multiplexing, and multiplexing, and instead MUST fallback to usage of separate ports
instead MUST fallback to usage of separate ports for RTP and RTCP for RTP and RTCP once the offer has been accepted by the answerer.
once the offer has been accepted by the answerer.
When an offerer sends a subsequent offer, if the offerer and answerer When an offerer sends a subsequent offer, if the offerer and answerer
have not previously negotiated usage of RTP/RTCP multiplexing for the have not previously negotiated usage of RTP/RTCP multiplexing for the
media associated with an RTP-based SDP media description ("m=" line), media associated with an RTP-based SDP media description ("m=" line),
the offerer MAY indicate exclusive support of RTP/RTCP multiplexing, the offerer MAY indicate exclusive support of RTP/RTCP multiplexing,
following the procedures in Section 4.2. The offerer MUST process following the procedures in Section 4.2. The offerer MUST process
the associated answer following the procedures in Section 4.4. the associated answer following the procedures in Section 4.4.
NOTE: It is RECOMMENDED to not switch between usage of RTP/RTCP NOTE: It is RECOMMENDED to not switch between usage of RTP/RTCP
multiplexing and usage of separate ports for RTP and RTCP in a multiplexing and usage of separate ports for RTP and RTCP in a
skipping to change at page 6, line 25 skipping to change at page 6, line 39
This document updates the "Session Description Protocol Parameters" This document updates the "Session Description Protocol Parameters"
registry as specified in Section 8.2.2 of [RFC4566]. Specifically, registry as specified in Section 8.2.2 of [RFC4566]. Specifically,
it adds the SDP 'rtcp-mux-exclusive' attribute to the table for SDP it adds the SDP 'rtcp-mux-exclusive' attribute to the table for SDP
media level attributes. media level attributes.
Attribute name: rtcp-mux-exclusive Attribute name: rtcp-mux-exclusive
Type of attribute: media-level Type of attribute: media-level
Subject to charset: no Subject to charset: no
Purpose: Indicate exclusive support of RTP/RTCP multiplexing Purpose: Indicate exclusive support of RTP/RTCP multiplexing
Appropriate Values: N/A Appropriate Values:
Contact name: Christer Holmberg Contact name: Christer Holmberg
Category: NORMAL
8. Acknowledgments 8. Acknowledgments
Thanks to Roman Shpount, Paul Kyzivat, Ari Keraenen, Bo Burman and Thanks to Roman Shpount, Paul Kyzivat, Ari Keraenen, Bo Burman and
Tomas Frankkila for their comments and input on the draft. Tomas Frankkila for their comments and input on the draft.
9. Change Log 9. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing] [RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-ietf-mmusic-rtcp-mux-exclusive-01
o Mux category and source-specific applicability added.
Changes from draft-ietf-mmusic-rtcp-mux-exclusive-00 Changes from draft-ietf-mmusic-rtcp-mux-exclusive-00
o Defined new SDP attribute for indicating rtcp-mux-exclusive. o Defined new SDP attribute for indicating rtcp-mux-exclusive.
o Additional text added to session modification section.
o Updates to RFC 5761 removed. o Updates to RFC 5761 removed.
o IANA considerations added. o IANA considerations added.
Changes from draft-holmberg-mmusic-rtcp-mux-exclusive-03 Changes from draft-holmberg-mmusic-rtcp-mux-exclusive-03
o Submitted as draft-ietf-mmusic-rtcp-mux-exclusive-00. o Submitted as draft-ietf-mmusic-rtcp-mux-exclusive-00.
Changes from draft-holmberg-mmusic-rtcp-mux-exclusive-02 Changes from draft-holmberg-mmusic-rtcp-mux-exclusive-02
skipping to change at page 8, line 12 skipping to change at page 8, line 27
Translator (NAT) Traversal", draft-ietf-ice-rfc5245bis-00 Translator (NAT) Traversal", draft-ietf-ice-rfc5245bis-00
(work in progress), October 2015. (work in progress), October 2015.
10.2. Informative References 10.2. Informative References
[RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute [RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute
in Session Description Protocol (SDP)", RFC 3605, in Session Description Protocol (SDP)", RFC 3605,
DOI 10.17487/RFC3605, October 2003, DOI 10.17487/RFC3605, October 2003,
<http://www.rfc-editor.org/info/rfc3605>. <http://www.rfc-editor.org/info/rfc3605>.
[RFC5576] Lennox, J., Ott, J., and T. Schierl, "Source-Specific
Media Attributes in the Session Description Protocol
(SDP)", RFC 5576, DOI 10.17487/RFC5576, June 2009,
<http://www.rfc-editor.org/info/rfc5576>.
[I-D.ietf-mmusic-sdp-mux-attributes]
Nandakumar, S., "A Framework for SDP Attributes when
Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-12
(work in progress), January 2016.
[I-D.ietf-mmusic-sdp-bundle-negotiation]
Holmberg, C., Alvestrand, H., and C. Jennings,
"Negotiating Media Multiplexing Using the Session
Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-
negotiation-25 (work in progress), January 2016.
Author's Address Author's Address
Christer Holmberg Christer Holmberg
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
Finland Finland
Email: christer.holmberg@ericsson.com Email: christer.holmberg@ericsson.com
 End of changes. 17 change blocks. 
27 lines changed or deleted 60 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/