draft-ietf-mmusic-sdp-bundle-negotiation-29.txt   draft-ietf-mmusic-sdp-bundle-negotiation-30.txt 
MMUSIC Working Group C. Holmberg MMUSIC Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 3264 (if approved) H. Alvestrand Updates: 3264 (if approved) H. Alvestrand
Intended status: Standards Track Google Intended status: Standards Track Google
Expires: October 17, 2016 C. Jennings Expires: December 9, 2016 C. Jennings
Cisco Cisco
April 15, 2016 June 7, 2016
Negotiating Media Multiplexing Using the Session Description Protocol Negotiating Media Multiplexing Using the Session Description Protocol
(SDP) (SDP)
draft-ietf-mmusic-sdp-bundle-negotiation-29.txt draft-ietf-mmusic-sdp-bundle-negotiation-30.txt
Abstract Abstract
This specification defines a new Session Description Protocol (SDP) This specification defines a new Session Description Protocol (SDP)
Grouping Framework extension, 'BUNDLE'. The extension can be used Grouping Framework extension, 'BUNDLE'. The extension can be used
with the SDP Offer/Answer mechanism to negotiate the usage of a with the SDP Offer/Answer mechanism to negotiate the usage of a
single address:port combination (BUNDLE address) for receiving media, single address:port combination (BUNDLE address) for receiving media,
referred to as bundled media, specified by multiple SDP media referred to as bundled media, specified by multiple SDP media
descriptions ("m=" lines). descriptions ("m=" lines).
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 9, 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 46 skipping to change at page 3, line 46
3264 . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3264 . . . . . . . . . . . . . . . . . . . . . . . . . . 26
14. RTP/RTCP extensions for identification-tag transport . . . . 27 14. RTP/RTCP extensions for identification-tag transport . . . . 27
14.1. General . . . . . . . . . . . . . . . . . . . . . . . . 27 14.1. General . . . . . . . . . . . . . . . . . . . . . . . . 27
14.2. RTCP MID SDES Item . . . . . . . . . . . . . . . . . . . 28 14.2. RTCP MID SDES Item . . . . . . . . . . . . . . . . . . . 28
14.3. RTP MID Header Extension . . . . . . . . . . . . . . . . 28 14.3. RTP MID Header Extension . . . . . . . . . . . . . . . . 28
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
15.1. New SDES item . . . . . . . . . . . . . . . . . . . . . 29 15.1. New SDES item . . . . . . . . . . . . . . . . . . . . . 29
15.2. New RTP Header Extension URI . . . . . . . . . . . . . . 29 15.2. New RTP Header Extension URI . . . . . . . . . . . . . . 29
15.3. New SDP Attribute . . . . . . . . . . . . . . . . . . . 30 15.3. New SDP Attribute . . . . . . . . . . . . . . . . . . . 30
15.4. New SDP Group Semantics . . . . . . . . . . . . . . . . 30 15.4. New SDP Group Semantics . . . . . . . . . . . . . . . . 30
16. Security Considerations . . . . . . . . . . . . . . . . . . . 30 16. Security Considerations . . . . . . . . . . . . . . . . . . . 31
17. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 31 17. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 31
17.1. Example: Bundle Address Selection . . . . . . . . . . . 31 17.1. Example: Bundle Address Selection . . . . . . . . . . . 31
17.2. Example: BUNDLE Extension Rejected . . . . . . . . . . . 33 17.2. Example: BUNDLE Extension Rejected . . . . . . . . . . . 33
17.3. Example: Offerer Adds A Media Description To A BUNDLE 17.3. Example: Offerer Adds A Media Description To A BUNDLE
Group . . . . . . . . . . . . . . . . . . . . . . . . . 34 Group . . . . . . . . . . . . . . . . . . . . . . . . . 34
17.4. Example: Offerer Moves A Media Description Out Of A 17.4. Example: Offerer Moves A Media Description Out Of A
BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 36 BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 36
17.5. Example: Offerer Disables A Media Description Within A 17.5. Example: Offerer Disables A Media Description Within A
BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 37 BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 37
18. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39 18. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39
19. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 39 19. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 39
20. References . . . . . . . . . . . . . . . . . . . . . . . . . 46 20. References . . . . . . . . . . . . . . . . . . . . . . . . . 46
20.1. Normative References . . . . . . . . . . . . . . . . . . 46 20.1. Normative References . . . . . . . . . . . . . . . . . . 46
20.2. Informative References . . . . . . . . . . . . . . . . . 48 20.2. Informative References . . . . . . . . . . . . . . . . . 48
Appendix A. Design Considerations . . . . . . . . . . . . . . . 48 Appendix A. Design Considerations . . . . . . . . . . . . . . . 48
A.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 48 A.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 48
A.2. UA Interoperability . . . . . . . . . . . . . . . . . . . 49 A.2. UA Interoperability . . . . . . . . . . . . . . . . . . . 49
A.3. Usage of port number value zero . . . . . . . . . . . . . 50 A.3. Usage of port number value zero . . . . . . . . . . . . . 51
A.4. B2BUA And Proxy Interoperability . . . . . . . . . . . . 51 A.4. B2BUA And Proxy Interoperability . . . . . . . . . . . . 51
A.4.1. Traffic Policing . . . . . . . . . . . . . . . . . . 51 A.4.1. Traffic Policing . . . . . . . . . . . . . . . . . . 52
A.4.2. Bandwidth Allocation . . . . . . . . . . . . . . . . 51 A.4.2. Bandwidth Allocation . . . . . . . . . . . . . . . . 52
A.5. Candidate Gathering . . . . . . . . . . . . . . . . . . . 52 A.5. Candidate Gathering . . . . . . . . . . . . . . . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53
1. Introduction 1. Introduction
This specification defines a way to use a single address:port This specification defines a way to use a single address:port
combination (BUNDLE address) for receiving media specified by combination (BUNDLE address) for receiving media specified by
multiple SDP media descriptions ("m=" lines). multiple SDP media descriptions ("m=" lines).
This specification defines a new SDP Grouping Framework [RFC5888] This specification defines a new SDP Grouping Framework [RFC5888]
extension called 'BUNDLE'. The extension can be used with the extension called 'BUNDLE'. The extension can be used with the
Session Description Protocol (SDP) Offer/Answer mechanism [RFC3264] Session Description Protocol (SDP) Offer/Answer mechanism [RFC3264]
skipping to change at page 18, line 51 skipping to change at page 18, line 51
in every offer and answer. in every offer and answer.
o A given SSRC MUST NOT transmit RTP packets using payload types o A given SSRC MUST NOT transmit RTP packets using payload types
that originate from different bundled "m=" lines. that originate from different bundled "m=" lines.
NOTE: The last bullet above is to avoid sending multiple media types NOTE: The last bullet above is to avoid sending multiple media types
from the same SSRC. If transmission of multiple media types are done from the same SSRC. If transmission of multiple media types are done
with time overlap, RTP and RTCP fail to function. Even if done in with time overlap, RTP and RTCP fail to function. Even if done in
proper sequence this causes RTP Timestamp rate switching issues proper sequence this causes RTP Timestamp rate switching issues
[RFC7160]. However, once an SSRC has left the RTP session (by [RFC7160]. However, once an SSRC has left the RTP session (by
sending an RTCP BYE packet), that SSRC value can later be reused by sending an RTCP BYE packet), that SSRC can be reused by another
another source(possibly associated with a different bundled "m=" source (possibly associated with a different bundled "m=" line) after
line. a delay of 5 RTCP reporting intervals (the delay is to ensure the
SSRC has timed out, in case the RTCP BYE packet was lost [RFC3550]).
10.1.2. Payload Type (PT) Value Reuse 10.1.2. Payload Type (PT) Value Reuse
Multiple bundled "m=" lines might represent RTP based media. As all Multiple bundled "m=" lines might represent RTP based media. As all
RTP based media specified by a BUNDLE group belong to the same RTP RTP based media specified by a BUNDLE group belong to the same RTP
session, in order for a given payload type value to be used inside session, in order for a given payload type value to be used inside
more than one bundled "m=" line, all codecs associated with the more than one bundled "m=" line, all codecs associated with the
payload type number MUST share an identical codec configuration. payload type number MUST share an identical codec configuration.
This means that the codecs MUST share the same media type, encoding This means that the codecs MUST share the same media type, encoding
name, clock rate and any parameter that can affect the codec name, clock rate and any parameter that can affect the codec
skipping to change at page 29, line 23 skipping to change at page 29, line 23
15. IANA Considerations 15. IANA Considerations
15.1. New SDES item 15.1. New SDES item
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
document.] document.]
[RFC EDITOR NOTE: Please replace TBD with the assigned SDES [RFC EDITOR NOTE: Please replace TBD with the assigned SDES
identifier value.] identifier value.]
This document adds the MID SDES item to the IANA "RTCP SDES item This document adds the MID SDES item to the IANA "RTP SDES item
types" registry as follows: types" registry as follows:
Value: TBD Value: TBD
Abbrev.: MID Abbrev.: MID
Name: Media Identification Name: Media Identification
Reference: RFCXXXX Reference: RFCXXXX
15.2. New RTP Header Extension URI 15.2. New RTP Header Extension URI
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
document.] document.]
This document defines a new extension URI in the RTP Compact Header This document defines a new extension URI in the RTP SDES Compact
Extensions subregistry of the Real-Time Transport Protocol (RTP) Header Extensions sub-registry of the RTP Compact Header Extensions
Parameters registry, according to the following data: registry sub-registry, according to the following data:
Extension URI: urn:ietf:params:rtp-hdrext:sdes:mid Extension URI: urn:ietf:params:rtp-hdrext:sdes:mid
Description: Media identification Description: Media identification
Contact: christer.holmberg@ericsson.com Contact: christer.holmberg@ericsson.com
Reference: RFCXXXX Reference: RFCXXXX
The SDES item does not reveal privacy information about the users.
It is simply used to associate RTP-based media with the correct SDP
media description (m- line) in the SDP used to negotiate the media.
The purpose of the extension is for the offerer to be able to
associate received multiplexed RTP-based media before the offerer
receives the associated SDP answer.
15.3. New SDP Attribute 15.3. New SDP Attribute
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
document.] document.]
This document defines a new SDP media-level attribute, 'bundle-only', This document defines a new SDP media-level attribute, 'bundle-only',
according to the following data: according to the following data:
Attribute name: bundle-only Attribute name: bundle-only
skipping to change at page 39, line 37 skipping to change at page 39, line 37
Thanks to Magnus Westerlund, Colin Perkins and Jonathan Lennox for Thanks to Magnus Westerlund, Colin Perkins and Jonathan Lennox for
providing help and text on the RTP/RTCP procedures. providing help and text on the RTP/RTCP procedures.
Thanks to Spotify for providing music for the countless hours of Thanks to Spotify for providing music for the countless hours of
document editing. document editing.
19. Change Log 19. 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-sdp-bundle-negotiation-29
o Change based on WGLC comment from Colin Perkins.
o - Clarify that SSRC can be reused by another source after a delay
of 5 RTCP reporting intervals.
o Change based on WGLC comment from Alissa Cooper.
o - IANA registry name fix.
o - Additional IANA registration information added.
Changes from draft-ietf-mmusic-sdp-bundle-negotiation-28 Changes from draft-ietf-mmusic-sdp-bundle-negotiation-28
o - Alignment with exclusive mux procedures. o - Alignment with exclusive mux procedures.
Changes from draft-ietf-mmusic-sdp-bundle-negotiation-27 Changes from draft-ietf-mmusic-sdp-bundle-negotiation-27
o - Yet another terminology change. o - Yet another terminology change.
o - Mux category considerations added. o - Mux category considerations added.
skipping to change at page 46, line 46 skipping to change at page 47, line 9
<http://www.rfc-editor.org/info/rfc3605>. <http://www.rfc-editor.org/info/rfc3605>.
[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>.
[RFC4961] Wing, D., "Symmetric RTP / RTP Control Protocol (RTCP)", [RFC4961] Wing, D., "Symmetric RTP / RTP Control Protocol (RTCP)",
BCP 131, RFC 4961, DOI 10.17487/RFC4961, July 2007, BCP 131, RFC 4961, DOI 10.17487/RFC4961, July 2007,
<http://www.rfc-editor.org/info/rfc4961>. <http://www.rfc-editor.org/info/rfc4961>.
[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>.
[RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP [RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP
Header Extensions", RFC 5285, DOI 10.17487/RFC5285, July Header Extensions", RFC 5285, DOI 10.17487/RFC5285, July
2008, <http://www.rfc-editor.org/info/rfc5285>. 2008, <http://www.rfc-editor.org/info/rfc5285>.
[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>.
[RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer [RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer
skipping to change at page 47, line 43 skipping to change at page 47, line 47
(work in progress), December 2015. (work in progress), December 2015.
[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-12 Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-12
(work in progress), January 2016. (work in progress), January 2016.
[I-D.ietf-mmusic-mux-exclusive] [I-D.ietf-mmusic-mux-exclusive]
Holmberg, C., "Indicating Exclusive Support of RTP/RTCP Holmberg, C., "Indicating Exclusive Support of RTP/RTCP
Multiplexing using SDP", draft-ietf-mmusic-mux- Multiplexing using SDP", draft-ietf-mmusic-mux-
exclusive-03 (work in progress), February 2016. exclusive-05 (work in progress), June 2016.
[I-D.ietf-mmusic-ice-sip-sdp] [I-D.ietf-mmusic-ice-sip-sdp]
Petit-Huguenin, M., Keranen, A., and S. Nandakumar, "Using Petit-Huguenin, M., Keranen, A., and S. Nandakumar, "Using
Interactive Connectivity Establishment (ICE) with Session Interactive Connectivity Establishment (ICE) with Session
Description Protocol (SDP) offer/answer and Session Description Protocol (SDP) offer/answer and Session
Initiation Protocol (SIP)", draft-ietf-mmusic-ice-sip- Initiation Protocol (SIP)", draft-ietf-mmusic-ice-sip-
sdp-07 (work in progress), October 2015. sdp-08 (work in progress), March 2016.
20.2. Informative References 20.2. Informative References
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>. <http://www.rfc-editor.org/info/rfc3261>.
[RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session
 End of changes. 16 change blocks. 
28 lines changed or deleted 44 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/