draft-ietf-mmusic-mux-exclusive-10.txt   draft-ietf-mmusic-mux-exclusive-11.txt 
Network Working Group C. Holmberg Network Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 5761 (if approved) August 8, 2016 Updates: 5761 (if approved) February 17, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: February 9, 2017 Expires: August 21, 2017
Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP
draft-ietf-mmusic-mux-exclusive-10.txt draft-ietf-mmusic-mux-exclusive-11.txt
Abstract Abstract
This document defines a new SDP media-level attribute, 'rtcp-mux- This document defines a new SDP media-level attribute, 'rtcp-mux-
only', that can be used by an endpoint to indicate exclusive support only', that can be used by an endpoint to indicate exclusive support
of RTP/RTCP multiplexing. The document also updates RFC 5761, by of RTP/RTCP multiplexing. The document also updates RFC 5761, by
clarifying that an offerer can use a mechanism to indicate that it is clarifying that an offerer can use a mechanism to indicate that it is
not able to send and receive RTCP on separate ports. not able to send and receive RTCP on separate ports.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 February 9, 2017. This Internet-Draft will expire on August 21, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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-only Attribute . . . . . . . . . . . . . . . . . 3 3. SDP rtcp-mux-only Attribute . . . . . . . . . . . . . . . . . 3
4. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 4 4. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 5
4.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. Generating the Initial SDP Offer . . . . . . . . . . . . 5 4.2. Generating the Initial SDP Offer . . . . . . . . . . . . 5
4.3. Generating the Answer . . . . . . . . . . . . . . . . . . 5 4.3. Generating the Answer . . . . . . . . . . . . . . . . . . 5
4.4. Offerer Processing of the SDP Answer . . . . . . . . . . 6 4.4. Offerer Processing of the SDP Answer . . . . . . . . . . 6
4.5. Modifying the Session . . . . . . . . . . . . . . . . . . 6 4.5. Modifying the Session . . . . . . . . . . . . . . . . . . 6
5. Update to RFC 5761 . . . . . . . . . . . . . . . . . . . . . 7 5. Update to RFC 5761 . . . . . . . . . . . . . . . . . . . . . 7
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2. Update to 4th paragraph of section 5.1.1 . . . . . . . . 7 5.2. Update to 4th paragraph of section 5.1.1 . . . . . . . . 7
5.3. Update to 2nd paragraph of section 5.1.3 . . . . . . . . 8 5.3. Update to 2nd paragraph of section 5.1.3 . . . . . . . . 8
6. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 8
skipping to change at page 4, line 25 skipping to change at page 4, line 25
rtcp-mux-only rtcp-mux-only
Example: Example:
a=rtcp-mux-only a=rtcp-mux-only
In an SDP offer, the offerer uses the SDP 'rtcp-mux-only' attribute In an SDP offer, the offerer uses the SDP 'rtcp-mux-only' attribute
to indicate exclusive support of RTP/RTCP multiplexing for the RTP- to indicate exclusive support of RTP/RTCP multiplexing for the RTP-
based media associated with the SDP media description ("m=" line). based media associated with the SDP media description ("m=" line).
In an SDP answer, the 'rtcp-mux-only' attribute indicates that the In an SDP answer, the 'rtcp-mux' attribute [RFC5761] indicates that
answerer supports, and accepts usage of, RTP/RTCP multiplexing for the answerer supports, and accepts usage of, RTP/RTCP multiplexing
the RTP-based media associated with the SDP media description ("m=" for the RTP-based media associated with the SDP media description
line). ("m=" line).
The usage of the 'rtcp-mux-only' attribue in an SDP answer is
forbidden.
The usage of the SDP 'rtcp-mux-only' attribute is only defined for The usage of the SDP 'rtcp-mux-only' attribute is only defined for
RTP-based media. RTP-based media.
The mux category [I-D.ietf-mmusic-sdp-mux-attributes] for the 'rtcp- The mux category [I-D.ietf-mmusic-sdp-mux-attributes] for the 'rtcp-
mux-only' attribute is 'IDENTICAL', which means that the attribute, mux-only' attribute is 'IDENTICAL', which means that the attribute,
if used within a BUNDLE group if used within a BUNDLE group
[I-D.ietf-mmusic-sdp-bundle-negotiation], must be associated with all [I-D.ietf-mmusic-sdp-bundle-negotiation], must be associated with all
multiplexed RTP-based media descriptions within the BUNDLE group. multiplexed RTP-based media descriptions within the BUNDLE group.
skipping to change at page 5, line 21 skipping to change at page 5, line 24
media descriptions ("m=" lines). media descriptions ("m=" lines).
4.2. Generating the Initial SDP Offer 4.2. Generating the Initial SDP Offer
When an offerer sends the initial offer, if the offerer wants to When an offerer sends the initial offer, if the offerer wants to
indicate exclusive RTP/RTCP multiplexing for RTP-based media, the indicate exclusive RTP/RTCP multiplexing for RTP-based media, the
offerer MUST associate an SDP 'rtcp-mux-only' attribute with the offerer MUST associate an SDP 'rtcp-mux-only' attribute with the
associated SDP media description ("m=" line). associated SDP media description ("m=" line).
In addition, if the offerer associates an SDP 'rtcp-mux-only' In addition, if the offerer associates an SDP 'rtcp-mux-only'
attribute with an SDP media description ("m=" line), the offerer MAY attribute with an SDP media description ("m=" line, the offerer MUST
also associate an SDP 'rtcp-mux' attribute with the same SDP media also associate an SDP 'rtcp-mux' attribute with the same SDP media
description ("m=" line), following the procedures in [RFC5761]. description ("m=" line), following the procedures in [RFC5761].
If the offerer associates an SDP 'rtcp' attribute [RFC3605] with an If the offerer associates an SDP 'rtcp' attribute [RFC3605] with an
SDP media description ("m=" line), and if the offerer also associates SDP media description ("m=" line), and if the offerer also associates
an SDP 'rtcp-mux-only' attribute with the same SDP media description an SDP 'rtcp-mux-only' attribute with the same SDP media description
("m=" line), the address and port values of the SDP 'rtcp' attribute ("m=" line), the address and port values of the SDP 'rtcp' attribute
MUST match the corresponding values for RTP. MUST match the corresponding values for RTP.
NOTE: This specification does not mandate the usage of the SDP 'rtcp' NOTE: This specification does not mandate the usage of the SDP 'rtcp'
attribute for RTP/RTCP multiplexing. attribute for RTP/RTCP multiplexing.
4.3. Generating the Answer 4.3. Generating the Answer
When an answerer receives an offer that contains an SDP 'rtcp-mux- When an answerer receives an offer that contains an SDP 'rtcp-mux-
only' attribute, associated with an RTP-based SDP media description only' attribute, associated with an RTP-based SDP media description
("m=" line), if the answerer accepts the usage of RTP/RTCP ("m=" line), if the answerer accepts the usage of RTP/RTCP
multiplexing, the answerer MUST associate an SDP 'rtcp-mux-only' multiplexing, the answerer MUST associate an SDP 'rtcp-mux' attribute
attribute with the corresponding SDP media description ("m=") in the with the corresponding SDP media description ("m=") in the associated
associated answer. If the answerer does not accept the usage of RTP/ answer, following the procedures in [RFC5761]. If the answerer does
RTCP multiplexing, the answerer MUST either reject the SDP media not accept the usage of RTP/RTCP multiplexing, the answerer MUST
description ("m=") by setting the port value to zero in the either reject the SDP media description ("m=") by setting the port
associated answer, or reject the whole offer, following the value to zero in the associated answer, or reject the whole offer,
procedures in [RFC3264]. following the procedures in [RFC3264].
In addition, if the answerer associates an SDP 'rtcp-mux-only' The answerer MUST NOT associate an SDP 'rtcp-mux-only' attribute with
attribute with an SDP media description ("m=" line) in the answer, an SDP media description ("m=" line) in the answer.
and if the corresponding "m=" line in the associated offer contained
an SDP 'rtcp-mux' attribute, the answerer MUST in addition associate
an SDP 'rtcp-mux' attribute with the same "m=" line, following the
procedures in [RFC5761].
4.4. Offerer Processing of the SDP Answer 4.4. Offerer Processing of the SDP Answer
If an offerer associated an SDP 'rtcp-mux-only' attribute with an If an offerer associated an SDP 'rtcp-mux-only' attribute with an
RTP-based SDP media description ("m=" line) in an offer, and if the RTP-based SDP media description ("m=" line) in an offer, and if the
corresponding SDP media description ("m=" line) in the associated corresponding SDP media description ("m=" line) in the associated
answer contains an SDP 'rtcp-mux-only' attribute, and/or an SDP answer contains an SDP 'rtcp-mux' attribute, the offerer MUST apply
'rtcp-mux' attribute, the offerer MUST apply the RTP/RTCP the RTP/RTCP multiplexing procedures [RFC5761] to the associated RTP-
multiplexing procedures [RFC5761] to the associated RTP-based media. based media. If the corresponding SDP media description ("m=" line)
If the corresponding SDP media description ("m=" line) in the in the associated answer does not contain an SDP 'rtcp-mux'
associated answer does not contain an SDP 'rtcp-mux-only' attribute, attribute, the offerer MUST either take appropriate actions in order
nor an SDP 'rtcp-mux' attribute, the offerer MUST either take to disable the associated RTP-based media, e.g., send a new offer
appropriate actions in order to disable the associated RTP-based with a zero port value associated with the SDP media description
media, or send a new offer without associating an SDP 'rtcp-mux-only' ("m=" line), or send a new offer without associating an SDP 'rtcp-
attribute with the SDP media description ("m=" line). mux-only' attribute with the SDP media description ("m=" line).
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 exclusive RTP/RTCP multiplexing have previously negotiated usage of exclusive RTP/RTCP multiplexing
for the media associated with an RTP-based SDP media description for the media associated with an RTP-based SDP media description
("m=" line), the offerer SHOULD associate an SDP 'rtcp-mux-only' with ("m=" line), the offerer SHOULD associate an SDP 'rtcp-mux-only' with
the corresponding SDP media description ("m=" line). the corresponding SDP media description ("m=" line).
In addition, if the offerer associates an SDP 'rtcp-mux-only' In addition, if the offerer associates an SDP 'rtcp-mux-only'
attribute with an SDP media description ("m=" line), the offerer MAY attribute with an SDP media description ("m=" line), the offerer MUST
also associate an SDP 'rtcp-mux' attribute with the same SDP media also associate an SDP 'rtcp-mux' attribute with the same SDP media
description ("m=" line), following the procedures in [RFC5761]. description ("m=" line), following the procedures in [RFC5761].
If the offerer does not associate the attributes with the If the offerer does not associate the attributes with the
corresponding SDP media description ("m=" line) it is an indication corresponding SDP media description ("m=" line) it is an indication
that the offerer no longer wants to use RTP/RTCP multiplexing, and that the offerer no longer wants to use RTP/RTCP multiplexing, and
instead MUST fallback to usage of separate ports for RTP and RTCP instead MUST fallback to usage of separate ports 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
skipping to change at page 9, line 30 skipping to change at page 9, line 30
9. Acknowledgments 9. Acknowledgments
Thanks to Roman Shpount, Paul Kyzivat, Ari Keranen, Bo Burman, Tomas Thanks to Roman Shpount, Paul Kyzivat, Ari Keranen, Bo Burman, Tomas
Frankkila and Martin Thomson for their comments and input on the Frankkila and Martin Thomson for their comments and input on the
document. Thanks to Francis Dupont for the genart review. document. Thanks to Francis Dupont for the genart review.
10. Change Log 10. 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-10
o Changes based on comments from Ekr:
o - 'rtcp-mux-only' attribute only defined for SDP offers
Changes from draft-ietf-mmusic-rtcp-mux-exclusive-09 Changes from draft-ietf-mmusic-rtcp-mux-exclusive-09
o Changes based on IESG review comments from Alexey Melnikov and o Changes based on IESG review comments from Alexey Melnikov and
Mirja Kuhlewind: Mirja Kuhlewind:
o - References to draft-mux-attributes and draft-sdp-bundle made o - References to draft-mux-attributes and draft-sdp-bundle made
normative. normative.
o - Text added regarding cases where entities might want to use non- o - Text added regarding cases where entities might want to use non-
multiplexed RTP and RTCP. multiplexed RTP and RTCP.
skipping to change at page 12, line 7 skipping to change at page 12, line 12
DOI 10.17487/RFC5245, April 2010, DOI 10.17487/RFC5245, April 2010,
<http://www.rfc-editor.org/info/rfc5245>. <http://www.rfc-editor.org/info/rfc5245>.
[RFC5761] Perkins, C. and M. Westerlund, "Multiplexing RTP Data and [RFC5761] Perkins, C. and M. Westerlund, "Multiplexing RTP Data and
Control Packets on a Single Port", RFC 5761, Control Packets on a Single Port", RFC 5761,
DOI 10.17487/RFC5761, April 2010, DOI 10.17487/RFC5761, April 2010,
<http://www.rfc-editor.org/info/rfc5761>. <http://www.rfc-editor.org/info/rfc5761>.
[I-D.ietf-mmusic-sdp-mux-attributes] [I-D.ietf-mmusic-sdp-mux-attributes]
Nandakumar, S., "A Framework for SDP Attributes when Nandakumar, S., "A Framework for SDP Attributes when
Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-13 Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-16
(work in progress), June 2016. (work in progress), December 2016.
[I-D.ietf-mmusic-sdp-bundle-negotiation] [I-D.ietf-mmusic-sdp-bundle-negotiation]
Holmberg, C., Alvestrand, H., and C. Jennings, Holmberg, C., Alvestrand, H., and C. Jennings,
"Negotiating Media Multiplexing Using the Session "Negotiating Media Multiplexing Using the Session
Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle- Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-
negotiation-31 (work in progress), June 2016. negotiation-36 (work in progress), October 2016.
11.2. Informative References 11.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 [RFC5576] Lennox, J., Ott, J., and T. Schierl, "Source-Specific
Media Attributes in the Session Description Protocol Media Attributes in the Session Description Protocol
 End of changes. 15 change blocks. 
37 lines changed or deleted 42 lines changed or added

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