draft-ietf-mmusic-sdp-bundle-negotiation-42.txt   draft-ietf-mmusic-sdp-bundle-negotiation-43.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: June 2, 2018 C. Jennings Expires: June 11, 2018 C. Jennings
Cisco Cisco
November 29, 2017 December 8, 2017
Negotiating Media Multiplexing Using the Session Description Protocol Negotiating Media Multiplexing Using the Session Description Protocol
(SDP) (SDP)
draft-ietf-mmusic-sdp-bundle-negotiation-42.txt draft-ietf-mmusic-sdp-bundle-negotiation-43.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 transport (5-tuple) for sending and receiving media described single transport (5-tuple) for sending and receiving media described
by multiple SDP media descriptions ("m=" sections). Such transport by multiple SDP media descriptions ("m=" sections). Such transport
is referred to as a BUNDLE transport, and the media is referred to as is referred to as a BUNDLE transport, and the media is referred to as
bundled media. The "m=" sections that use the BUNDLE transport form bundled media. The "m=" sections that use the BUNDLE transport form
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 June 2, 2018. This Internet-Draft will expire on June 11, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
skipping to change at page 3, line 12 skipping to change at page 3, line 12
8.1. Mux Category Considerations . . . . . . . . . . . . . . . 10 8.1. Mux Category Considerations . . . . . . . . . . . . . . . 10
8.2. Generating the Initial SDP Offer . . . . . . . . . . . . 11 8.2. Generating the Initial SDP Offer . . . . . . . . . . . . 11
8.2.1. Suggesting the offerer BUNDLE address . . . . . . . . 11 8.2.1. Suggesting the offerer BUNDLE address . . . . . . . . 11
8.2.2. Example: Initial SDP Offer . . . . . . . . . . . . . 12 8.2.2. Example: Initial SDP Offer . . . . . . . . . . . . . 12
8.3. Generating the SDP Answer . . . . . . . . . . . . . . . . 12 8.3. Generating the SDP Answer . . . . . . . . . . . . . . . . 12
8.3.1. Answerer Selection of Offerer Bundle Address . . . . 13 8.3.1. Answerer Selection of Offerer Bundle Address . . . . 13
8.3.2. Answerer Selection of Answerer BUNDLE Address . . . . 14 8.3.2. Answerer Selection of Answerer BUNDLE Address . . . . 14
8.3.3. Moving A Media Description Out Of A BUNDLE Group . . 14 8.3.3. Moving A Media Description Out Of A BUNDLE Group . . 14
8.3.4. Rejecting A Media Description In A BUNDLE Group . . . 15 8.3.4. Rejecting A Media Description In A BUNDLE Group . . . 15
8.3.5. Example: SDP Answer . . . . . . . . . . . . . . . . . 16 8.3.5. Example: SDP Answer . . . . . . . . . . . . . . . . . 16
8.4. Offerer Processing of the SDP Answer . . . . . . . . . . 16 8.4. Offerer Processing of the SDP Answer . . . . . . . . . . 17
8.5. Modifying the Session . . . . . . . . . . . . . . . . . . 17 8.5. Modifying the Session . . . . . . . . . . . . . . . . . . 17
8.5.1. Suggesting a new offerer BUNDLE address . . . . . . . 17 8.5.1. Suggesting a new offerer BUNDLE address . . . . . . . 17
8.5.2. Adding a media description to a BUNDLE group . . . . 18 8.5.2. Adding a media description to a BUNDLE group . . . . 18
8.5.3. Moving A Media Description Out Of A BUNDLE Group . . 18 8.5.3. Moving A Media Description Out Of A BUNDLE Group . . 18
8.5.4. Disabling A Media Description In A BUNDLE Group . . . 19 8.5.4. Disabling A Media Description In A BUNDLE Group . . . 19
9. Protocol Identification . . . . . . . . . . . . . . . . . . . 19 9. Protocol Identification . . . . . . . . . . . . . . . . . . . 19
9.1. STUN, DTLS, SRTP . . . . . . . . . . . . . . . . . . . . 20 9.1. STUN, DTLS, SRTP . . . . . . . . . . . . . . . . . . . . 20
10. RTP Considerations . . . . . . . . . . . . . . . . . . . . . 20 10. RTP Considerations . . . . . . . . . . . . . . . . . . . . . 20
10.1. Single RTP Session . . . . . . . . . . . . . . . . . . . 20 10.1. Single RTP Session . . . . . . . . . . . . . . . . . . . 20
10.1.1. Payload Type (PT) Value Reuse . . . . . . . . . . . 21 10.1.1. Payload Type (PT) Value Reuse . . . . . . . . . . . 21
skipping to change at page 4, line 21 skipping to change at page 4, line 21
18.5. Example: Offerer Disables A Media Description Within A 18.5. Example: Offerer Disables A Media Description Within A
BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 46 BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 46
19. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47 19. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47
20. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 48 20. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 48
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 58 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 58
21.1. Normative References . . . . . . . . . . . . . . . . . . 58 21.1. Normative References . . . . . . . . . . . . . . . . . . 58
21.2. Informative References . . . . . . . . . . . . . . . . . 60 21.2. Informative References . . . . . . . . . . . . . . . . . 60
Appendix A. Design Considerations . . . . . . . . . . . . . . . 61 Appendix A. Design Considerations . . . . . . . . . . . . . . . 61
A.1. UA Interoperability . . . . . . . . . . . . . . . . . . . 62 A.1. UA Interoperability . . . . . . . . . . . . . . . . . . . 62
A.2. Usage of port number value zero . . . . . . . . . . . . . 63 A.2. Usage of port number value zero . . . . . . . . . . . . . 63
A.3. B2BUA And Proxy Interoperability . . . . . . . . . . . . 63 A.3. B2BUA And Proxy Interoperability . . . . . . . . . . . . 64
A.3.1. Traffic Policing . . . . . . . . . . . . . . . . . . 64 A.3.1. Traffic Policing . . . . . . . . . . . . . . . . . . 64
A.3.2. Bandwidth Allocation . . . . . . . . . . . . . . . . 64 A.3.2. Bandwidth Allocation . . . . . . . . . . . . . . . . 64
A.4. Candidate Gathering . . . . . . . . . . . . . . . . . . . 64 A.4. Candidate Gathering . . . . . . . . . . . . . . . . . . . 65
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65
1. Introduction 1. Introduction
When multimedia communications are established, each transport When multimedia communications are established, each transport
(5-tuple) reserved for an individual media stream consume additional (5-tuple) reserved for an individual media stream consume additional
resources (especially when Interactive Connectivity Establishment resources (especially when Interactive Connectivity Establishment
(ICE) [I-D.ietf-ice-rfc5245bis] is used). For this reason, it is (ICE) [I-D.ietf-ice-rfc5245bis] is used). For this reason, it is
attractive to use a single transport for multiple media streams. attractive to use a single transport for multiple media streams.
skipping to change at page 6, line 29 skipping to change at page 6, line 29
Offerer BUNDLE-tag: The first identification-tag in a given SDP Offerer BUNDLE-tag: The first identification-tag in a given SDP
'group:BUNDLE' attribute identification-tag list in an offer. 'group:BUNDLE' attribute identification-tag list in an offer.
Answerer BUNDLE-tag: The first identification-tag in a given SDP Answerer BUNDLE-tag: The first identification-tag in a given SDP
'group:BUNDLE' attribute identification-tag list in an answer. 'group:BUNDLE' attribute identification-tag list in an answer.
BUNDLE address: An address:port combination that an endpoint uses for BUNDLE address: An address:port combination that an endpoint uses for
sending and receiving bundled media. sending and receiving bundled media.
Offerer BUNDLE address: In an offer, the BUNDLE address of the Offerer BUNDLE address: the address:port combination used by the
offerer. offerer for sending and receiving media.
Answerer BUNDLE address: In an answer, the BUNDLE address of the Suggested Offerer BUNDLE address: before an offerer BUNDLE address
answerer. has been selected by the answerer, or when the offerer wants to
change a previously selected offerer BUNDLE address, the address:port
combination that the offerer wants to use for sending and receiving
media. While suggested by the offerer, the selection of the offerer
BUNDLE address is done by the answerer.
Answerer BUNDLE address: the address:port combination used by the
answerer for sending and receiving media.
BUNDLE transport: The transport (5-tuple) used by all media described BUNDLE transport: The transport (5-tuple) used by all media described
by the "m=" sections within a BUNDLE group. by the "m=" sections within a BUNDLE group.
BUNDLE group: A set of "m=" sections, created using an SDP Offer/ BUNDLE group: A set of "m=" sections, created using an SDP Offer/
Answer exchange, which uses a single BUNDLE transport for sending and Answer exchange, which uses a single BUNDLE transport for sending and
receiving all media (bundled media) described by the set of "m=" receiving all media (bundled media) described by the set of "m="
sections. The same BUNDLE transport is used for sending and sections. The same BUNDLE transport is used for sending and
receiving bundled media. receiving bundled media.
skipping to change at page 48, line 30 skipping to change at page 48, line 30
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.
20. Change Log 20. 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-42
o Changes based on final WG review.
Changes from draft-ietf-mmusic-sdp-bundle-negotiation-41 Changes from draft-ietf-mmusic-sdp-bundle-negotiation-41
o Update to section 6 o RFC 3264: o Update to section 6 o RFC 3264:
o https://github.com/cdh4u/draft-sdp-bundle/pull/47 o https://github.com/cdh4u/draft-sdp-bundle/pull/47
o Editorial clarification on BUNDLE address selection: o Editorial clarification on BUNDLE address selection:
o https://github.com/cdh4u/draft-sdp-bundle/pull/46 o https://github.com/cdh4u/draft-sdp-bundle/pull/46
 End of changes. 10 change blocks. 
11 lines changed or deleted 22 lines changed or added

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