draft-ietf-mmusic-sdp-bundle-negotiation-30.txt   draft-ietf-mmusic-sdp-bundle-negotiation-31.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: December 9, 2016 C. Jennings Expires: December 21, 2016 C. Jennings
Cisco Cisco
June 7, 2016 June 19, 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-30.txt draft-ietf-mmusic-sdp-bundle-negotiation-31.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).
To assist endpoints in negotiating the use of bundle this To assist endpoints in negotiating the use of bundle this
specification defines a new SDP attribute, 'bundle-only', which can specification defines a new SDP attribute, 'bundle-only', which can
be used to request that specific media is only used if bundled. be used to request that specific media is only used if bundled. The
specification also updates RFC 3264, to allow usage of zero port
values without meaning that media is rejcted.
There are multiple ways to correlate the bundled RTP packets with the There are multiple ways to correlate the bundled RTP packets with the
appropriate media descriptions. This specification defines a new appropriate media descriptions. This specification defines a new
Real-time Transport Protocol (RTP) source description (SDES) item and Real-time Transport Protocol (RTP) source description (SDES) item and
a new RTP header extension that provides an additional way to do this a new RTP header extension that provides an additional way to do this
correlation by using them to carry a value that associates the RTP/ correlation by using them to carry a value that associates the RTP/
RTCP packets with a specific media description. RTCP packets with a specific media description.
Status of This Memo Status of This Memo
skipping to change at page 2, line 4 skipping to change at page 2, line 6
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 December 9, 2016.
This Internet-Draft will expire on December 21, 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
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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Applicability Statement . . . . . . . . . . . . . . . . . . . 7 4. Applicability Statement . . . . . . . . . . . . . . . . . . . 7
5. SDP Grouping Framework BUNDLE Extension . . . . . . . . . . . 7 5. SDP Grouping Framework BUNDLE Extension . . . . . . . . . . . 7
6. SDP 'bundle-only' Attribute . . . . . . . . . . . . . . . . . 7 6. SDP 'bundle-only' Attribute . . . . . . . . . . . . . . . . . 8
7. SDP Information Considerations . . . . . . . . . . . . . . . 8 7. SDP Information Considerations . . . . . . . . . . . . . . . 9
7.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.2. Connection Data (c=) . . . . . . . . . . . . . . . . . . 9 7.2. Connection Data (c=) . . . . . . . . . . . . . . . . . . 9
7.3. Bandwidth (b=) . . . . . . . . . . . . . . . . . . . . . 9 7.3. Bandwidth (b=) . . . . . . . . . . . . . . . . . . . . . 9
7.4. Attributes (a=) . . . . . . . . . . . . . . . . . . . . . 9 7.4. Attributes (a=) . . . . . . . . . . . . . . . . . . . . . 9
8. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 9 8. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 9
8.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9 8.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.2. Mux Category Considerations . . . . . . . . . . . . . . . 10 8.2. Mux Category Considerations . . . . . . . . . . . . . . . 10
8.3. Generating the Initial SDP Offer . . . . . . . . . . . . 10 8.3. Generating the Initial SDP Offer . . . . . . . . . . . . 10
8.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 10 8.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 11
8.3.2. Suggesting the offerer BUNDLE address . . . . . . . . 11 8.3.2. Suggesting the offerer BUNDLE address . . . . . . . . 11
8.4. Generating the SDP Answer . . . . . . . . . . . . . . . . 11 8.4. Generating the SDP Answer . . . . . . . . . . . . . . . . 11
8.4.1. General . . . . . . . . . . . . . . . . . . . . . . . 11 8.4.1. General . . . . . . . . . . . . . . . . . . . . . . . 12
8.4.2. Answerer Selection of Offerer Bundle Address . . . . 12 8.4.2. Answerer Selection of Offerer Bundle Address . . . . 13
8.4.3. Answerer Selection of Answerer BUNDLE Address . . . . 13 8.4.3. Answerer Selection of Answerer BUNDLE Address . . . . 13
8.4.4. Moving A Media Description Out Of A BUNDLE Group . . 13 8.4.4. Moving A Media Description Out Of A BUNDLE Group . . 14
8.4.5. Rejecting A Media Description In A BUNDLE Group . . . 14 8.4.5. Rejecting A Media Description In A BUNDLE Group . . . 14
8.5. Offerer Processing of the SDP Answer . . . . . . . . . . 14 8.5. Offerer Processing of the SDP Answer . . . . . . . . . . 14
8.6. Modifying the Session . . . . . . . . . . . . . . . . . . 14 8.6. Modifying the Session . . . . . . . . . . . . . . . . . . 15
8.6.1. General . . . . . . . . . . . . . . . . . . . . . . . 14 8.6.1. General . . . . . . . . . . . . . . . . . . . . . . . 15
8.6.2. Suggesting a new offerer BUNDLE address . . . . . . . 15 8.6.2. Suggesting a new offerer BUNDLE address . . . . . . . 15
8.6.3. Adding a media description to a BUNDLE group . . . . 15 8.6.3. Adding a media description to a BUNDLE group . . . . 16
8.6.4. Moving A Media Description Out Of A BUNDLE Group . . 16 8.6.4. Moving A Media Description Out Of A BUNDLE Group . . 16
8.6.5. Disabling A Media Description In A BUNDLE Group . . . 16 8.6.5. Disabling A Media Description In A BUNDLE Group . . . 17
9. Protocol Identification . . . . . . . . . . . . . . . . . . . 17 9. Protocol Identification . . . . . . . . . . . . . . . . . . . 17
9.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 17 9.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.2. STUN, DTLS, SRTP . . . . . . . . . . . . . . . . . . . . 17 9.2. STUN, DTLS, SRTP . . . . . . . . . . . . . . . . . . . . 18
10. RTP Considerations . . . . . . . . . . . . . . . . . . . . . 18 10. RTP Considerations . . . . . . . . . . . . . . . . . . . . . 18
10.1. Single RTP Session . . . . . . . . . . . . . . . . . . . 18 10.1. Single RTP Session . . . . . . . . . . . . . . . . . . . 18
10.1.1. General . . . . . . . . . . . . . . . . . . . . . . 18 10.1.1. General . . . . . . . . . . . . . . . . . . . . . . 18
10.1.2. Payload Type (PT) Value Reuse . . . . . . . . . . . 19 10.1.2. Payload Type (PT) Value Reuse . . . . . . . . . . . 19
10.2. Associating RTP/RTCP Packets With Correct SDP Media 10.2. Associating RTP/RTCP Packets With Correct SDP Media
Description . . . . . . . . . . . . . . . . . . . . . . 19 Description . . . . . . . . . . . . . . . . . . . . . . 19
10.3. RTP/RTCP Multiplexing . . . . . . . . . . . . . . . . . 20 10.3. RTP/RTCP Multiplexing . . . . . . . . . . . . . . . . . 20
10.3.1. General . . . . . . . . . . . . . . . . . . . . . . 20 10.3.1. General . . . . . . . . . . . . . . . . . . . . . . 20
10.3.2. SDP Offer/Answer Procedures . . . . . . . . . . . . 20 10.3.2. SDP Offer/Answer Procedures . . . . . . . . . . . . 20
11. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 22 11. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 22
11.1. General . . . . . . . . . . . . . . . . . . . . . . . . 22 11.1. General . . . . . . . . . . . . . . . . . . . . . . . . 23
11.2. SDP Offer/Answer Procedures . . . . . . . . . . . . . . 23 11.2. SDP Offer/Answer Procedures . . . . . . . . . . . . . . 23
11.2.1. General . . . . . . . . . . . . . . . . . . . . . . 23 11.2.1. General . . . . . . . . . . . . . . . . . . . . . . 23
11.2.2. Generating the Initial SDP Offer . . . . . . . . . . 24 11.2.2. Generating the Initial SDP Offer . . . . . . . . . . 24
11.2.3. Generating the SDP Answer . . . . . . . . . . . . . 24 11.2.3. Generating the SDP Answer . . . . . . . . . . . . . 24
11.2.4. Offerer Processing of the SDP Answer . . . . . . . . 24 11.2.4. Offerer Processing of the SDP Answer . . . . . . . . 24
11.2.5. Modifying the Session . . . . . . . . . . . . . . . 24 11.2.5. Modifying the Session . . . . . . . . . . . . . . . 24
12. DTLS Considerations . . . . . . . . . . . . . . . . . . . . . 24 12. DTLS Considerations . . . . . . . . . . . . . . . . . . . . . 25
13. Update to RFC 3264 . . . . . . . . . . . . . . . . . . . . . 25 13. Update to RFC 3264 . . . . . . . . . . . . . . . . . . . . . 25
13.1. General . . . . . . . . . . . . . . . . . . . . . . . . 25 13.1. General . . . . . . . . . . . . . . . . . . . . . . . . 25
13.2. Original text of section 5.1 (2nd paragraph) of RFC 3264 25 13.2. Original text of section 5.1 (2nd paragraph) of RFC 3264 26
13.3. New text replacing section 5.1 (2nd paragraph) of RFC 13.3. New text replacing section 5.1 (2nd paragraph) of RFC
3264 . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3264 . . . . . . . . . . . . . . . . . . . . . . . . . . 26
13.4. Original text of section 8.2 (2nd paragraph) of RFC 3264 26 13.4. Original text of section 8.2 (2nd paragraph) of RFC 3264 26
13.5. New text replacing section 8.2 (2nd paragraph) of RFC 13.5. New text replacing section 8.2 (2nd paragraph) of RFC
3264 . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3264 . . . . . . . . . . . . . . . . . . . . . . . . . . 26
13.6. Original text of section 8.4 (6th paragraph) of RFC 3264 26 13.6. Original text of section 8.4 (6th paragraph) of RFC 3264 27
13.7. New text replacing section 8.4 (6th paragraph) of RFC 13.7. New text replacing section 8.4 (6th paragraph) of RFC
3264 . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3264 . . . . . . . . . . . . . . . . . . . . . . . . . . 27
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 . . . . . . . . . . . . . . . . 29
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 . . . . . . . . . . . . . . 30
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 . . . . . . . . . . . . . . . . 31
16. Security Considerations . . . . . . . . . . . . . . . . . . . 31 16. Security Considerations . . . . . . . . . . . . . . . . . . . 31
17. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 31 17. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 32
17.1. Example: Bundle Address Selection . . . . . . . . . . . 31 17.1. Example: Bundle Address Selection . . . . . . . . . . . 32
17.2. Example: BUNDLE Extension Rejected . . . . . . . . . . . 33 17.2. Example: BUNDLE Extension Rejected . . . . . . . . . . . 34
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 . . . . . . . . . . . . . . . . . . . . . . . . . 35
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
17.5. Example: Offerer Disables A Media Description Within A
BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 37 BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 37
18. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39 17.5. Example: Offerer Disables A Media Description Within A
19. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 39 BUNDLE Group . . . . . . . . . . . . . . . . . . . . . . 38
20. References . . . . . . . . . . . . . . . . . . . . . . . . . 46 18. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 40
20.1. Normative References . . . . . . . . . . . . . . . . . . 46 19. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 40
20.2. Informative References . . . . . . . . . . . . . . . . . 48 20. References . . . . . . . . . . . . . . . . . . . . . . . . . 47
Appendix A. Design Considerations . . . . . . . . . . . . . . . 48 20.1. Normative References . . . . . . . . . . . . . . . . . . 47
A.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 48 20.2. Informative References . . . . . . . . . . . . . . . . . 49
A.2. UA Interoperability . . . . . . . . . . . . . . . . . . . 49 Appendix A. Design Considerations . . . . . . . . . . . . . . . 50
A.3. Usage of port number value zero . . . . . . . . . . . . . 51 A.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 50
A.4. B2BUA And Proxy Interoperability . . . . . . . . . . . . 51 A.2. UA Interoperability . . . . . . . . . . . . . . . . . . . 50
A.4.1. Traffic Policing . . . . . . . . . . . . . . . . . . 52 A.3. Usage of port number value zero . . . . . . . . . . . . . 52
A.4.2. Bandwidth Allocation . . . . . . . . . . . . . . . . 52 A.4. B2BUA And Proxy Interoperability . . . . . . . . . . . . 52
A.5. Candidate Gathering . . . . . . . . . . . . . . . . . . . 52 A.4.1. Traffic Policing . . . . . . . . . . . . . . . . . . 53
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53 A.4.2. Bandwidth Allocation . . . . . . . . . . . . . . . . 53
A.5. Candidate Gathering . . . . . . . . . . . . . . . . . . . 53
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54
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 4, line 48 skipping to change at page 5, line 16
negotiate the BUNDLE addresses, one for the offerer (offerer BUNDLE negotiate the BUNDLE addresses, one for the offerer (offerer BUNDLE
address) and one for the answerer (answerer BUNDLE address), to be address) and one for the answerer (answerer BUNDLE address), to be
used for receiving the bundled media specified by a BUNDLE group. used for receiving the bundled media specified by a BUNDLE group.
Once the offerer and the answerer have negotiated a BUNDLE group, Once the offerer and the answerer have negotiated a BUNDLE group,
they associate their respective BUNDLE address with each "m=" line in they associate their respective BUNDLE address with each "m=" line in
the BUNDLE group. The BUNDLE addresses are used to receive all media the BUNDLE group. The BUNDLE addresses are used to receive all media
specified by the BUNDLE group. specified by the BUNDLE group.
The use of a BUNDLE group and a BUNDLE address also allows the usage The use of a BUNDLE group and a BUNDLE address also allows the usage
of a single set of Interactive Connectivity Establishment (ICE) of a single set of Interactive Connectivity Establishment (ICE)
[I-D.ietf-ice-rfc5245bis] candidates for multiple "m=" lines. [RFC5245] candidates for multiple "m=" lines.
This specification also defines a new SDP attribute, 'bundle-only', This specification also defines a new SDP attribute, 'bundle-only',
which can be used to request that specific media is only used if kept which can be used to request that specific media is only used if kept
within a BUNDLE group. within a BUNDLE group. The specification also updates RFC 3264, to
allow usage of zero port values without meaning that media is
rejcted.
As defined in RFC 4566 [RFC4566], the semantics of assigning the same As defined in RFC 4566 [RFC4566], the semantics of assigning the same
port value to multiple "m=" lines are undefined, and there is no port value to multiple "m=" lines are undefined, and there is no
grouping defined by such means. Instead, an explicit grouping grouping defined by such means. Instead, an explicit grouping
mechanism needs to be used to express the intended semantics. This mechanism needs to be used to express the intended semantics. This
specification provides such an extension. specification provides such an extension.
This specification also updates sections 5.1, 8.1 and 8.2 of RFC 3264 This specification also updates sections 5.1, 8.1 and 8.2 of RFC 3264
[RFC3264]. The update allows an answerer to assign a non-zero port [RFC3264]. The update allows an answerer to assign a non-zero port
value to an "m=" line in an SDP answer, even if the "m=" line in the value to an "m=" line in an SDP answer, even if the "m=" line in the
skipping to change at page 39, line 37 skipping to change at page 40, 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-30
o Indicating in the Abstract and Introduction that the document
updates RFC 3264.
Changes from draft-ietf-mmusic-sdp-bundle-negotiation-29 Changes from draft-ietf-mmusic-sdp-bundle-negotiation-29
o Change based on WGLC comment from Colin Perkins. o Change based on WGLC comment from Colin Perkins.
o - Clarify that SSRC can be reused by another source after a delay o - Clarify that SSRC can be reused by another source after a delay
of 5 RTCP reporting intervals. of 5 RTCP reporting intervals.
o Change based on WGLC comment from Alissa Cooper. o Change based on WGLC comment from Alissa Cooper.
o - IANA registry name fix. o - IANA registry name fix.
skipping to change at page 47, line 9 skipping to change at page 48, line 18
<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 34 skipping to change at page 48, line 49
[RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description [RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description
Protocol (SDP) Grouping Framework", RFC 5888, Protocol (SDP) Grouping Framework", RFC 5888,
DOI 10.17487/RFC5888, June 2010, DOI 10.17487/RFC5888, June 2010,
<http://www.rfc-editor.org/info/rfc5888>. <http://www.rfc-editor.org/info/rfc5888>.
[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer [RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347, Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347,
January 2012, <http://www.rfc-editor.org/info/rfc6347>. January 2012, <http://www.rfc-editor.org/info/rfc6347>.
[I-D.ietf-ice-rfc5245bis] [I-D.ietf-ice-rfc5245bis]
Keranen, A. and J. Rosenberg, "Interactive Connectivity Keraenen, A., Holmberg, C., and J. Rosenberg, "Interactive
Establishment (ICE): A Protocol for Network Address Connectivity Establishment (ICE): A Protocol for Network
Translator (NAT) Traversal", draft-ietf-ice-rfc5245bis-01 Address Translator (NAT) Traversal", draft-ietf-ice-
(work in progress), December 2015. rfc5245bis-02 (work in progress), June 2016.
[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-05 (work in progress), June 2016. exclusive-07 (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., Keraenen, A., and S. Nandakumar,
Interactive Connectivity Establishment (ICE) with Session "Using Interactive Connectivity Establishment (ICE) with
Description Protocol (SDP) offer/answer and Session Session Description Protocol (SDP) offer/answer and
Initiation Protocol (SIP)", draft-ietf-mmusic-ice-sip- Session Initiation Protocol (SIP)", draft-ietf-mmusic-ice-
sdp-08 (work in progress), March 2016. sip-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. 35 change blocks. 
61 lines changed or deleted 89 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/