draft-ietf-mmusic-mux-exclusive-04.txt   draft-ietf-mmusic-mux-exclusive-05.txt 
Network Working Group C. Holmberg Network Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 5761 (if approved) April 15, 2016 Updates: 5761 (if approved) June 3, 2016
Intended status: Standards Track Intended status: Standards Track
Expires: October 17, 2016 Expires: December 5, 2016
Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP
draft-ietf-mmusic-mux-exclusive-04 draft-ietf-mmusic-mux-exclusive-05
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 October 17, 2016. This Internet-Draft will expire on December 5, 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 3, line 9 skipping to change at page 3, line 9
separation of RTP and RTCP. For those applications, this document separation of RTP and RTCP. For those applications, this document
defines an SDP attribute to signal intent to require multiplexing. defines an SDP attribute to signal intent to require multiplexing.
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.
The document also describes the Interactive Connectivity The document also describes the Interactive Connectivity
Establishment (ICE) [I-D.ietf-ice-rfc5245bis] considerations when Establishment (ICE) [RFC5245] considerations when indicating
indicating exclusive support of RTP/RTCP multiplexing. exclusive support of RTP/RTCP multiplexing.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"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-only Attribute 3. SDP rtcp-mux-only Attribute
This section defines a new SDP media-level attribute, 'rtcp-mux- This section defines a new SDP media-level attribute, 'rtcp-mux-
skipping to change at page 8, line 24 skipping to change at page 8, line 24
NEW TEXT: NEW TEXT:
If it is desired to use both ICE and multiplexed RTP and RTCP, the If it is desired to use both ICE and multiplexed RTP and RTCP, the
initial offer MUST contain an "a=rtcp-mux" attribute to indicate that initial offer MUST contain an "a=rtcp-mux" attribute to indicate that
RTP and RTCP multiplexing is desired and MUST contain "a=candidate:" RTP and RTCP multiplexing is desired and MUST contain "a=candidate:"
lines for both RTP and RTCP along with an "a=rtcp:" line indicating a lines for both RTP and RTCP along with an "a=rtcp:" line indicating a
fallback port for RTCP in the case that the answerer does not support fallback port for RTCP in the case that the answerer does not support
RTP and RTCP multiplexing. This MUST be done for each media where RTP and RTCP multiplexing. This MUST be done for each media where
RTP and RTCP multiplexing is desired. However, if the offerer RTP and RTCP multiplexing is desired. However, if the offerer
indicates in the offer that it is not able to send and receive RTCP indicates in the offer that it is not able to send and receive RTCP
on a separate port, the offerer MUST NOT include "a=candidiate:" lines on a separate port, the offerer MUST NOT include "a=candidiate:"
for RTCP, and the offerer MUST NOT provide a fallback port for RTCP using lines for RTCP, and the offerer MUST NOT provide a fallback port for
the "a=rtcp:" line. RTCP using the "a=rtcp:" line.
6. ICE Considerations 6. ICE Considerations
As defined in [I-D.ietf-ice-rfc5245bis], if an entity is aware that As defined in [RFC5245], if an entity is aware that the remote peer
the remote peer supports, and is willing to use, RTP/RTCP supports, and is willing to use, RTP/RTCP multiplexing, the entity
multiplexing, the entity will only provide RTP candidates (component will only provide RTP candidates (component ID 1). However, only
ID 1). However, only providing RTP candidates does not as such imply providing RTP candidates does not as such imply exclusive support of
exclusive support of RTP/RTCP multiplexing. RTCP candidates would RTP/RTCP multiplexing. RTCP candidates would not be provided also in
not be provided also in cases where RTCP is not supported at all. cases where RTCP is not supported at all. Therefore, additional
Therefore, additional information is needed in order to indicate information is needed in order to indicate support of exclusive RTP/
support of exclusive RTP/RTCP multiplexing. This document defines RTCP multiplexing. This document defines such mechanism using the
such mechanism using the SDP 'rtcp-mux-only' attributes. SDP 'rtcp-mux-only' attributes.
7. Security Considerations 7. Security Considerations
This document does not introduce new security considerations in This document does not introduce new security considerations in
additions to those specified in [RFC3605] and [RFC5761]. additions to those specified in [RFC3605] and [RFC5761].
8. IANA Considerations 8. IANA Considerations
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-only' attribute to the table for SDP media it adds the SDP 'rtcp-mux-only' attribute to the table for SDP media
level attributes. level attributes.
Attribute name: rtcp-mux-only Attribute name: rtcp-mux-only
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: Appropriate Values:
Contact name: Christer Holmberg Contact name: Christer Holmberg
Category: NORMAL Mux Category: IDENTICAL
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. document.
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-04
o Changes based on comments from Flemming Andreasen.
o - Attribute mux category changed to IDENTICAL.
o - Reference to draft-5245bis changed to RFC 5245.
Changes from draft-ietf-mmusic-rtcp-mux-exclusive-03 Changes from draft-ietf-mmusic-rtcp-mux-exclusive-03
o Editorial changes based on comments from Martin Thomson. o Editorial changes based on comments from Martin Thomson.
o Change of attribute name. o Change of attribute name.
o RFC 5761 updates added. o RFC 5761 updates added.
Changes from draft-ietf-mmusic-rtcp-mux-exclusive-02 Changes from draft-ietf-mmusic-rtcp-mux-exclusive-02
skipping to change at page 10, line 42 skipping to change at page 11, line 5
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
DOI 10.17487/RFC3264, June 2002, DOI 10.17487/RFC3264, June 2002,
<http://www.rfc-editor.org/info/rfc3264>. <http://www.rfc-editor.org/info/rfc3264>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, DOI 10.17487/RFC4566, Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <http://www.rfc-editor.org/info/rfc4566>. July 2006, <http://www.rfc-editor.org/info/rfc4566>.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245,
DOI 10.17487/RFC5245, April 2010,
<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-ice-rfc5245bis]
Keranen, A. and J. Rosenberg, "Interactive Connectivity
Establishment (ICE): A Protocol for Network Address
Translator (NAT) Traversal", draft-ietf-ice-rfc5245bis-00
(work in progress), October 2015.
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
(SDP)", RFC 5576, DOI 10.17487/RFC5576, June 2009, (SDP)", RFC 5576, DOI 10.17487/RFC5576, June 2009,
 End of changes. 11 change blocks. 
25 lines changed or deleted 33 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/