draft-ietf-mmusic-sdp-mux-attributes-16.txt   draft-ietf-mmusic-sdp-mux-attributes-17.txt 
Network Working Group S. Nandakumar Network Working Group S. Nandakumar
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track December 19, 2016 Intended status: Standards Track February 28, 2018
Expires: June 22, 2017 Expires: September 1, 2018
A Framework for SDP Attributes when Multiplexing A Framework for SDP Attributes when Multiplexing
draft-ietf-mmusic-sdp-mux-attributes-16 draft-ietf-mmusic-sdp-mux-attributes-17
Abstract Abstract
The purpose of this specification is to provide a framework for The purpose of this specification is to provide a framework for
analyzing the multiplexing characteristics of Session Description analyzing the multiplexing characteristics of Session Description
Protocol (SDP) attributes when SDP is used to negotiate the usage of Protocol (SDP) attributes when SDP is used to negotiate the usage of
single 5-tuple for sending and receiving media associated with single 5-tuple for sending and receiving media associated with
multiple media descriptions. multiple media descriptions.
This specification also categorizes the existing SDP attributes based This specification also categorizes the existing SDP attributes based
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 22, 2017. This Internet-Draft will expire on September 1, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 2, line 17 skipping to change at page 2, line 17
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 6 4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 6
4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7 4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7
4.2. Category: CAUTION . . . . . . . . . . . . . . . . . . . . 7 4.2. Category: CAUTION . . . . . . . . . . . . . . . . . . . . 7
4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8 4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8
4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 8 4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 9
4.5. Category: TRANSPORT . . . . . . . . . . . . . . . . . . . 9 4.5. Category: TRANSPORT . . . . . . . . . . . . . . . . . . . 9
4.6. Category: INHERIT . . . . . . . . . . . . . . . . . . . . 10 4.6. Category: INHERIT . . . . . . . . . . . . . . . . . . . . 10
4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 10 4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 11
4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 11 4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 12
4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 11 4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 12
5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12 5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12
5.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 12 5.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 13
5.2. RFC4585: RTP/AVPF . . . . . . . . . . . . . . . . . . . . 14 5.2. RFC4585: RTP/AVPF . . . . . . . . . . . . . . . . . . . . 14
5.3. RFC5761: Multiplexing RTP and RTCP . . . . . . . . . . . 14 5.3. RFC5761: Multiplexing RTP and RTCP . . . . . . . . . . . 15
5.4. RFC3312: Integration of Resource Management and SIP . . . 14 5.4. RFC3312: Integration of Resource Management and SIP . . . 15
5.5. RFC4574: SDP Label Attribute . . . . . . . . . . . . . . 15 5.5. RFC4574: SDP Label Attribute . . . . . . . . . . . . . . 16
5.6. RFC5432: QOS Mechanism Selection in SDP . . . . . . . . . 15 5.6. RFC5432: QOS Mechanism Selection in SDP . . . . . . . . . 16
5.7. RFC4568: SDP Security Descriptions . . . . . . . . . . . 16 5.7. RFC4568: SDP Security Descriptions . . . . . . . . . . . 17
5.8. RFC5762: RTP over DCCP . . . . . . . . . . . . . . . . . 16 5.8. RFC5762: RTP over DCCP . . . . . . . . . . . . . . . . . 17
5.9. RFC6773: DCCP-UDP Encapsulation . . . . . . . . . . . . . 17 5.9. RFC6773: DCCP-UDP Encapsulation . . . . . . . . . . . . . 18
5.10. RFC5506: Reduced-Size RTCP in RTP Profile . . . . . . . . 18 5.10. RFC5506: Reduced-Size RTCP in RTP Profile . . . . . . . . 19
5.11. RFC6787: Media Resource Control Protocol Version 2 . . . 18 5.11. RFC6787: Media Resource Control Protocol Version 2 . . . 19
5.12. RFC5245: ICE . . . . . . . . . . . . . . . . . . . . . . 19 5.12. RFC5245: ICE . . . . . . . . . . . . . . . . . . . . . . 20
5.13. RFC5285: RTP Header Extensions . . . . . . . . . . . . . 20 5.13. RFC5285: RTP Header Extensions . . . . . . . . . . . . . 21
5.14. RFC3605: RTCP attribute in SDP . . . . . . . . . . . . . 21 5.14. RFC3605: RTCP attribute in SDP . . . . . . . . . . . . . 22
5.15. RFC5576: Source-Specific SDP Attributes . . . . . . . . . 21 5.15. RFC5576: Source-Specific SDP Attributes . . . . . . . . . 22
5.16. RFC7273: RTP Clock Source Signalling . . . . . . . . . . 22 5.16. RFC7273: RTP Clock Source Signalling . . . . . . . . . . 23
5.17. RFC6236: Image Attributes in SDP . . . . . . . . . . . . 23 5.17. RFC6236: Image Attributes in SDP . . . . . . . . . . . . 24
5.18. RFC7197: Duplication Delay Attribute in SDP . . . . . . . 24 5.18. RFC7197: Duplication Delay Attribute in SDP . . . . . . . 25
5.19. RFC7266: RTCP XR Blocks for MOS Metric Reporting . . . . 24 5.19. RFC7266: RTCP XR Blocks for MOS Metric Reporting . . . . 25
5.20. RFC6285: Rapid Acquisition of Multicast RTP Sessions . . 24 5.20. RFC6285: Rapid Acquisition of Multicast RTP Sessions . . 25
5.21. RFC6230: Media Control Channel Framework . . . . . . . . 25 5.21. RFC6230: Media Control Channel Framework . . . . . . . . 26
5.22. RFC6364: SDP Elements for FEC Framework . . . . . . . . . 25 5.22. RFC6364: SDP Elements for FEC Framework . . . . . . . . . 26
5.23. RFC4796: Content Attribute . . . . . . . . . . . . . . . 26 5.23. RFC4796: Content Attribute . . . . . . . . . . . . . . . 27
5.24. RFC3407: SDP Simple Capability Declaration . . . . . . . 26 5.24. RFC3407: SDP Simple Capability Declaration . . . . . . . 27
5.25. RFC6284: Port Mapping between Unicast and Multicast RTP 5.25. RFC6284: Port Mapping between Unicast and Multicast RTP
Sessions . . . . . . . . . . . . . . . . . . . . . . . . 27 Sessions . . . . . . . . . . . . . . . . . . . . . . . . 28
5.26. RFC6714: MSRP-CEMA . . . . . . . . . . . . . . . . . . . 28 5.26. RFC6714: MSRP-CEMA . . . . . . . . . . . . . . . . . . . 29
5.27. RFC4583: SDP Format for BFCP Streams . . . . . . . . . . 28 5.27. RFC4583: SDP Format for BFCP Streams . . . . . . . . . . 29
5.28. RFC5547: SDP Offer/Answer for File Transfer . . . . . . . 29 5.28. RFC5547: SDP Offer/Answer for File Transfer . . . . . . . 30
5.29. RFC6849: SDP and RTP Media Loopback Extension . . . . . . 29 5.29. RFC6849: SDP and RTP Media Loopback Extension . . . . . . 30
5.30. RFC5760: RTCP with Unicast Feedback . . . . . . . . . . . 30 5.30. RFC5760: RTCP with Unicast Feedback . . . . . . . . . . . 31
5.31. RFC3611: RTCP XR . . . . . . . . . . . . . . . . . . . . 30 5.31. RFC3611: RTCP XR . . . . . . . . . . . . . . . . . . . . 31
5.32. RFC5939: SDP Capability Negotiation . . . . . . . . . . . 31 5.32. RFC5939: SDP Capability Negotiation . . . . . . . . . . . 32
5.33. RFC6871: SDP Media Capabilities Negotiation . . . . . . . 31 5.33. RFC6871: SDP Media Capabilities Negotiation . . . . . . . 32
5.34. RFC7006: Miscellaneous Capabilities Negotiation SDP . . . 32 5.34. RFC7006: Miscellaneous Capabilities Negotiation SDP . . . 33
5.35. RFC4567: Key Management Extensions for SDP and RTSP . . . 33 5.35. RFC4567: Key Management Extensions for SDP and RTSP . . . 34
5.36. RFC4572: Comedia over TLS in SDP . . . . . . . . . . . . 34 5.36. RFC4572: Comedia over TLS in SDP . . . . . . . . . . . . 35
5.37. RFC4570: SDP Source Filters . . . . . . . . . . . . . . . 34 5.37. RFC4570: SDP Source Filters . . . . . . . . . . . . . . . 35
5.38. RFC6128: RTCP Port for Multicast Sessions . . . . . . . . 35 5.38. RFC6128: RTCP Port for Multicast Sessions . . . . . . . . 36
5.39. RFC6189: ZRTP . . . . . . . . . . . . . . . . . . . . . . 35 5.39. RFC6189: ZRTP . . . . . . . . . . . . . . . . . . . . . . 36
5.40. RFC4145: Connection-Oriented Media . . . . . . . . . . . 36 5.40. RFC4145: Connection-Oriented Media . . . . . . . . . . . 37
5.41. RFC6947: The SDP altc Attribute . . . . . . . . . . . . . 36 5.41. RFC6947: The SDP altc Attribute . . . . . . . . . . . . . 37
5.42. RFC7195: SDP Extension for Circuit Switched Bearers 5.42. RFC7195: SDP Extension for Circuit Switched Bearers
in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 37 in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.43. RFC7272: IDMS Using the RTP Control Protocol (RTCP) . . . 37 5.43. RFC7272: IDMS Using the RTP Control Protocol (RTCP) . . . 38
5.44. RFC5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP 5.44. RFC5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP
Attributes . . . . . . . . . . . . . . . . . . . . . . . 38 Attributes . . . . . . . . . . . . . . . . . . . . . . . 39
5.45. RFC6193: Media Description for IKE in SDP . . . . . . . . 38 5.45. RFC6193: Media Description for IKE in SDP . . . . . . . . 39
5.46. RFC2326: Real Time Streaming Protocol . . . . . . . . . . 39 5.46. RFC2326: Real Time Streaming Protocol . . . . . . . . . . 40
5.47. RFC6064: SDP and RTSP Extensions for 3GPP . . . . . . . . 40 5.47. RFC6064: SDP and RTSP Extensions for 3GPP . . . . . . . . 41
5.48. RFC3108: ATM SDP . . . . . . . . . . . . . . . . . . . . 42 5.48. RFC3108: ATM SDP . . . . . . . . . . . . . . . . . . . . 43
5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 44 5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 45
5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 45 5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 46
5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 45 5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 46
5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 46 5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 47
5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 46 5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 47
5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 47 5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 48
5.55. ITU-T Q.1970 . . . . . . . . . . . . . . . . . . . . . . 49 5.55. ITU-T Q.1970 . . . . . . . . . . . . . . . . . . . . . . 50
5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 49 5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 50
5.57. RFC4975: The Message Session Relay Protocol . . . . . . . 50 5.57. RFC4975: The Message Session Relay Protocol . . . . . . . 51
5.58. Historical Attributes . . . . . . . . . . . . . . . . . . 51 5.58. Historical Attributes . . . . . . . . . . . . . . . . . . 52
6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 51 6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 52
6.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 52 6.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 53
6.2. RFC3556: SDP Bandwidth Modifiers for RTCP Bandwidth . . . 52 6.2. RFC3556: SDP Bandwidth Modifiers for RTCP Bandwidth . . . 53
6.3. RFC3890: Bandwidth Modifier for SDP . . . . . . . . . . . 53 6.3. RFC3890: Bandwidth Modifier for SDP . . . . . . . . . . . 54
7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 53 7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 54
7.1. RFC4585: RTP/AVPF . . . . . . . . . . . . . . . . . . . . 53 7.1. RFC4585: RTP/AVPF . . . . . . . . . . . . . . . . . . . . 54
7.2. RFC5104: Codec Control Messages in AVPF . . . . . . . . . 54 7.2. RFC5104: Codec Control Messages in AVPF . . . . . . . . . 55
7.3. RFC6285: Unicast-Based Rapid Acquisition of Multicast RTP 7.3. RFC6285: Unicast-Based Rapid Acquisition of Multicast RTP
Sessions (RAMS) . . . . . . . . . . . . . . . . . . . . . 55 Sessions (RAMS) . . . . . . . . . . . . . . . . . . . . . 56
7.4. RFC6679: ECN for RTP over UDP/IP . . . . . . . . . . . . 55 7.4. RFC6679: ECN for RTP over UDP/IP . . . . . . . . . . . . 56
7.5. RFC6642: Third-Party Loss Report . . . . . . . . . . . . 56 7.5. RFC6642: Third-Party Loss Report . . . . . . . . . . . . 57
7.6. RFC5104: Codec Control Messages in AVPF . . . . . . . . . 57 7.6. RFC5104: Codec Control Messages in AVPF . . . . . . . . . 58
8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 57 8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 58
8.1. RFC5888: SDP Grouping Framework . . . . . . . . . . . . . 57 8.1. RFC5888: SDP Grouping Framework . . . . . . . . . . . . . 58
8.2. RFC3524: Mapping Media Streams to Resource 8.2. RFC3524: Mapping Media Streams to Resource
Reservation Flows . . . . . . . . . . . . . . . . . . . . 58 Reservation Flows . . . . . . . . . . . . . . . . . . . . 59
8.3. RFC4091: ANAT Semantics . . . . . . . . . . . . . . . . . 58 8.3. RFC4091: ANAT Semantics . . . . . . . . . . . . . . . . . 59
8.4. RFC5956: FEC Grouping Semantics in SDP . . . . . . . . . 58 8.4. RFC5956: FEC Grouping Semantics in SDP . . . . . . . . . 59
8.5. RFC5583: Signaling Media Decoding Dependency in SDP . . . 59 8.5. RFC5583: Signaling Media Decoding Dependency in SDP . . . 60
8.6. RFC7104: Duplication Grouping Semantics in the SDP . . . 59 8.6. RFC7104: Duplication Grouping Semantics in the SDP . . . 60
9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 60 9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 61
9.1. RFC5576: Source-Specific SDP Attributes . . . . . . . . . 60 9.1. RFC5576: Source-Specific SDP Attributes . . . . . . . . . 61
9.2. RFC7104: Duplication Grouping Semantics in the SDP . . . 60 9.2. RFC7104: Duplication Grouping Semantics in the SDP . . . 61
10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 61 10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 62
10.1. RFC5432: QoS Mechanism Selection in SDP . . . . . . . . 61 10.1. RFC5432: QoS Mechanism Selection in SDP . . . . . . . . 62
11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 61 11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 62
11.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 62 11.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 63
12. content Attribute Analysis . . . . . . . . . . . . . . . . . 62 12. content Attribute Analysis . . . . . . . . . . . . . . . . . 63
12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 62 12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 63
13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 63 13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 64
13.1. RFC5109: RTP Payload Format for Generic FEC . . . . . . 63 13.1. RFC5109: RTP Payload Format for Generic FEC . . . . . . 64
14. Multiplexing Considerations for Encapsulating Attributes . . 63 14. Multiplexing Considerations for Encapsulating Attributes . . 64
14.1. RFC3407: cpar Attribute Analysis . . . . . . . . . . . . 64 14.1. RFC3407: cpar Attribute Analysis . . . . . . . . . . . . 65
14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 64 14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 65
14.2.1. Recommendation: Procedures for Potential 14.2.1. Recommendation: Procedures for Potential
Configuration Pairing . . . . . . . . . . . . . . . 65 Configuration Pairing . . . . . . . . . . . . . . . 66
14.2.1.1. Example: Transport Capability Multiplexing . . . 66 14.2.1.1. Example: Transport Capability Multiplexing . . . 67
14.2.1.2. Example: Attribute Capability Multiplexing . . . 67 14.2.1.2. Example: Attribute Capability Multiplexing . . . 68
14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 68 14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 69
14.3.1. Recommendation: Dealing with Payload Type Numbers . 68 14.3.1. Recommendation: Dealing with Payload Type Numbers . 69
14.3.1.1. Example: Attribute Capability Under Shared 14.3.1.1. Example: Attribute Capability Under Shared
Payload Type . . . . . . . . . . . . . . . . . . 68 Payload Type . . . . . . . . . . . . . . . . . . 69
14.3.2. Recommendation: Dealing with Latent Configurations . 69 14.3.2. Recommendation: Dealing with Latent Configurations . 70
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 70 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 71
15.1. New 'Multiplexing Categories' subregistry . . . . . . . 70 15.1. New 'Multiplexing Categories' subregistry . . . . . . . 71
15.2. 'Mux Category' column for subregistries . . . . . . . . 71 15.2. 'Mux Category' column for subregistries . . . . . . . . 72
15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 71 15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 72
15.2.2. Table: att-field (session level) . . . . . . . . . . 71 15.2.2. Table: att-field (session level) . . . . . . . . . . 72
15.2.3. Table: att-field (both session and media level) . . 72 15.2.3. Table: att-field (both session and media level) . . 73
15.2.4. Table: att-field (media level only) . . . . . . . . 74 15.2.4. Table: att-field (media level only) . . . . . . . . 75
15.2.5. Table: att-field (source level) . . . . . . . . . . 77 15.2.5. Table: att-field (source level) . . . . . . . . . . 78
15.2.6. Table: content SDP Parameters . . . . . . . . . . . 78 15.2.6. Table: content SDP Parameters . . . . . . . . . . . 79
15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 78 15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 79
15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 79 15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 80
15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 79 15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 80
15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 79 15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 80
15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 80 15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 81
15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 80 15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 81
15.2.13. Table: SDP/RTSP key management protocol identifiers 80 15.2.13. Table: SDP/RTSP key management protocol identifiers 81
15.2.14. Table: Codec Control Messages . . . . . . . . . . . 81 15.2.14. Table: Codec Control Messages . . . . . . . . . . . 82
15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 81 15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 82
15.2.16. Table: SDP Capability Negotiation Option Tags . . . 81 15.2.16. Table: SDP Capability Negotiation Option Tags . . . 82
15.2.17. Table: Timestamp Reference Clock Source Parameters . 82 15.2.17. Table: Timestamp Reference Clock Source Parameters . 83
15.2.18. Table: Media Clock Source Parameters . . . . . . . . 82 15.2.18. Table: Media Clock Source Parameters . . . . . . . . 83
16. Security Considerations . . . . . . . . . . . . . . . . . . . 83 16. Security Considerations . . . . . . . . . . . . . . . . . . . 84
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 83 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 84
18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 83 18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 84
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 87 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 88
19.1. Normative References . . . . . . . . . . . . . . . . . . 87 19.1. Normative References . . . . . . . . . . . . . . . . . . 88
19.2. Informative References . . . . . . . . . . . . . . . . . 87 19.2. Informative References . . . . . . . . . . . . . . . . . 88
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 95 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 97
1. Introduction 1. Introduction
SDP defines several attributes for capturing characteristics that SDP defines several attributes for capturing characteristics that
apply to the individual media descriptions (described by "m=" lines") apply to the individual media descriptions (described by "m=" lines")
and the overall multimedia session. Typically different media types and the overall multimedia session. Typically different media types
(audio, video, etc.) described using different media descriptions (audio, video, etc.) described using different media descriptions
represent separate RTP sessions that are carried over individual represent separate RTP sessions that are carried over individual
transport layer flows. However transport layer flows. However
[I-D.ietf-mmusic-sdp-bundle-negotiation] defines a way to use a [I-D.ietf-mmusic-sdp-bundle-negotiation] defines a way to use a
skipping to change at page 8, line 43 skipping to change at page 8, line 43
o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com
s= s=
c=IN IP4 client.biloxi.example.com c=IN IP4 client.biloxi.example.com
t=0 0 t=0 0
m=audio 34567 RTP/AVP 97 m=audio 34567 RTP/AVP 97
a=rtcp-mux a=rtcp-mux
m=video 34567 RTP/AVP 31 m=video 34567 RTP/AVP 31
a=rtpmap:31 H261/90000 a=rtpmap:31 H261/90000
a=rtcp-mux a=rtcp-mux
Note: Eventhough IDENTICAL attributes must be repeated across all
media descriptions under multiplexing, they might not always be
explicitly encoded across all media descriptions.
[I-D.ietf-mmusic-sdp-bundle-negotiation] defines rules for when
attributes and their values are implicitly applied to media
description.
4.4. Category: SUM 4.4. Category: SUM
The attributes in the SUM category can be set as they are normally The attributes in the SUM category can be set as they are normally
used but software using them in the multiplexing scenario MUST apply used but software using them in the multiplexing scenario MUST apply
the sum of all the attributes being multiplexed instead of trying to the sum of all the attributes being multiplexed instead of trying to
use them independently. This is typically used for bandwidth or use them independently. This is typically used for bandwidth or
other rate limiting attributes to the underlying transport. other rate limiting attributes to the underlying transport.
The software parsing the SDP sample below, should use the aggregate The software parsing the SDP sample below, should use the aggregate
Application Specific (AS) bandwidth value from the individual media Application Specific (AS) bandwidth value from the individual media
skipping to change at page 12, line 32 skipping to change at page 13, line 21
The "Mux Category" column identifies multiplexing category assigned The "Mux Category" column identifies multiplexing category assigned
per attribute and the "Notes" column captures additional informative per attribute and the "Notes" column captures additional informative
details regarding the assigned category, wherever necessary. details regarding the assigned category, wherever necessary.
5.1. RFC4566: SDP 5.1. RFC4566: SDP
[RFC4566] defines SDP that is intended for describing multimedia [RFC4566] defines SDP that is intended for describing multimedia
sessions for the purposes of session announcement, session sessions for the purposes of session announcement, session
invitation, and other forms of multimedia session initiation. invitation, and other forms of multimedia session initiation.
+-----------------+---------------------+-------+-------------------+ +----------------+-----------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-----------------+---------------------+-------+-------------------+ +----------------+-----------------------+-------+------------------+
| sendrecv | Not impacted | B | NORMAL | | sendrecv | Not impacted | B | NORMAL |
| | | | | | | | | |
| sendonly | Not impacted | B | NORMAL | | sendonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| recvonly | Not impacted | B | NORMAL | | recvonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| inactive | Not impacted | B | NORMAL | | inactive | Not impacted | B | NORMAL |
| | | | | | | | | |
| cat | Not impacted | S | NORMAL | | cat | Not impacted | S | NORMAL |
| | | | | | | | | |
| ptime | The attribute value | M | IDENTICAL-PER-PT | | ptime | The attribute value | M | IDENTICAL-PER-PT |
| | MUST be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| maxptime | The attribute value | M | IDENTICAL-PER-PT | | maxptime | The attribute value | M | IDENTICAL-PER-PT |
| | MUST be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| orient | Not Impacted | M | NORMAL | | orient | Not Impacted | M | NORMAL |
| | | | | | | | | |
| framerate | The attribute value | M | IDENTICAL-PER-PT | | framerate | The attribute value | M | IDENTICAL-PER- |
| | MUST be same for a | | | | | MUST be same for a | | PT |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| quality | Not Impacted | M | NORMAL | | quality | Not Impacted | M | NORMAL |
| | | | | | | | | |
| rtpmap | The attribute value | M | IDENTICAL-PER-PT | | rtpmap | The attribute value | M | IDENTICAL-PER-PT |
| | MUST be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| fmtp | The attribute value | M | IDENTICAL-PER-PT | | fmtp | The attribute value | M | IDENTICAL-PER-PT |
| | MUST be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| keywds | Not impacted | S | NORMAL | | keywds | Not impacted | S | NORMAL |
| | | | | | | | | |
| type | Not Impacted | S | NORMAL | | type | Not Impacted | S | NORMAL |
| | | | | | | | | |
| type:broadcast | Not Impacted | S | NORMAL | | type:broadcast | Not Impacted | S | NORMAL |
| | | | | | | | | |
| type:H332 | Not Impacted | S | NORMAL | | type:H332 | Not Impacted | S | NORMAL |
| | | | | | | | | |
| type:meeting | Not Impacted | S | NORMAL | | type:meeting | Not Impacted | S | NORMAL |
| | | | | | | | | |
| type:moderated | Not Impacted | S | NORMAL | | type:moderated | Not Impacted | S | NORMAL |
| | | | | | | | | |
| type:test | Not Impacted | S | NORMAL | | type:test | Not Impacted | S | NORMAL |
| | | | | | | | | |
| tool | Not Impacted | S | NORMAL | | tool | Not Impacted | S | NORMAL |
| | | | | | | | | |
| charset | Not Impacted | S | NORMAL | | charset | Not Impacted | S | NORMAL |
| | | | | | | | | |
| sdplang | Not Impacted | B | NORMAL | | sdplang | Not Impacted | B | NORMAL |
| | | | | | | | | |
| lang | Not Impacted | B | NORMAL | | lang | Not Impacted | B | NORMAL |
| | | | | | | | | |
+-----------------+---------------------+-------+-------------------+ +----------------+-----------------------+-------+------------------+
5.1 RFC4566 Attribute Analysis 5.1 RFC4566 Attribute Analysis
5.2. RFC4585: RTP/AVPF 5.2. RFC4585: RTP/AVPF
[RFC4585] defines an extension to the Audio-visual Profile (AVP) that [RFC4585] defines an extension to the Audio-visual Profile (AVP) that
enables receivers to provide, statistically, more immediate feedback enables receivers to provide, statistically, more immediate feedback
to the senders and thus allows for short-term adaptation and to the senders and thus allows for short-term adaptation and
efficient feedback-based repair mechanisms to be implemented. efficient feedback-based repair mechanisms to be implemented.
+----------+----------------------------+-------+-------------------+ +---------+------------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+----------+----------------------------+-------+-------------------+ +---------+------------------------------+-------+------------------+
| rtcp-fb | Since RTCP feedback | M | IDENTICAL-PER-PT | | rtcp- | Since RTCP feedback | M | IDENTICAL-PER- |
| | attributes are Payload | | | | fb | attributes are Payload Type | | PT |
| | Type (PT) scoped, their | | | | | (PT) scoped, their values | | |
| | values MUST be identical | | | | | MUST be identical for a | | |
| | for a given PT across the | | | | | given PT across the | | |
| | multiplexed "m=" lines. | | | | | multiplexed "m=" lines. | | |
| | | | | | | | | |
+----------+----------------------------+-------+-------------------+ +---------+------------------------------+-------+------------------+
5.2 RFC4585 Attribute Analysis 5.2 RFC4585 Attribute Analysis
5.3. RFC5761: Multiplexing RTP and RTCP 5.3. RFC5761: Multiplexing RTP and RTCP
[RFC5761] discusses issues that arise when multiplexing RTP data [RFC5761] discusses issues that arise when multiplexing RTP data
packets and RTP Control Protocol (RTCP) packets on a single UDP port. packets and RTP Control Protocol (RTCP) packets on a single UDP port.
It describes when such multiplexing is and is not appropriate, and it It describes when such multiplexing is and is not appropriate, and it
explains how the SDP can be used to signal multiplexed sessions. explains how the SDP can be used to signal multiplexed sessions.
+-----------+----------------------------------+-------+------------+ +----------+------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------+----------------------------------+-------+------------+ +----------+------------------------------------+-------+-----------+
| rtcp-mux | RTP and RTCP Multiplexing | M | IDENTICAL | | rtcp- | RTP and RTCP Multiplexing affects | M | IDENTICAL |
| | affects the entire RTP session | | | | mux | the entire RTP session | | |
| | | | | | | | | |
+-----------+----------------------------------+-------+------------+ +----------+------------------------------------+-------+-----------+
5.3 RFC5761 Attribute Analysis 5.3 RFC5761 Attribute Analysis
5.4. RFC3312: Integration of Resource Management and SIP 5.4. RFC3312: Integration of Resource Management and SIP
[RFC3312] defines a generic framework for preconditions, which are [RFC3312] defines a generic framework for preconditions, which are
extensible through IANA registration. This document also discusses extensible through IANA registration. This document also discusses
how network quality of service can be made a precondition for how network quality of service can be made a precondition for
establishment of sessions initiated by the Session Initiation establishment of sessions initiated by the Session Initiation
Protocol (SIP). These preconditions require that the participant Protocol (SIP). These preconditions require that the participant
skipping to change at page 16, line 23 skipping to change at page 17, line 23
5.6 RFC5432 Attribute Analysis 5.6 RFC5432 Attribute Analysis
5.7. RFC4568: SDP Security Descriptions 5.7. RFC4568: SDP Security Descriptions
[RFC4568] defines a SDP cryptographic attribute for unicast media [RFC4568] defines a SDP cryptographic attribute for unicast media
streams. The attribute describes a cryptographic key and other streams. The attribute describes a cryptographic key and other
parameters that serve to configure security for a unicast media parameters that serve to configure security for a unicast media
stream in either a single message or a roundtrip exchange. stream in either a single message or a roundtrip exchange.
+---------+------------------------------------+-------+------------+ +--------+--------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------+------------------------------------+-------+------------+ +--------+--------------------------------------+-------+-----------+
| crypto | crypto attribute MUST be the one | M | TRANSPORT | | crypto | crypto attribute MUST be the one | M | TRANSPORT |
| | that corresponds to the "m=" line | | | | | that corresponds to the "m=" line | | |
| | chosen for setting up the | | | | | chosen for setting up the underlying | | |
| | underlying transport flow | | | | | transport flow | | |
| | | | | | | | | |
+---------+------------------------------------+-------+------------+ +--------+--------------------------------------+-------+-----------+
5.7 RFC4568 Attribute Analysis 5.7 RFC4568 Attribute Analysis
5.8. RFC5762: RTP over DCCP 5.8. RFC5762: RTP over DCCP
RTP is a widely used transport for real-time multimedia on IP RTP is a widely used transport for real-time multimedia on IP
networks. DCCP is a transport protocol that provides desirable networks. DCCP is a transport protocol that provides desirable
services for real-time applications. [RFC5762] specifies a mapping services for real-time applications. [RFC5762] specifies a mapping
of RTP onto DCCP, along with associated signaling, such that real- of RTP onto DCCP, along with associated signaling, such that real-
time applications can make use of the services provided by DCCP. time applications can make use of the services provided by DCCP.
+--------------------+-------------------------+---------+----------+ +-------------------+--------------------------+---------+----------+
| Name | Notes | Current | Mux | | Name | Notes | Current | Mux |
| | | | Category | | | | | Category |
+--------------------+-------------------------+---------+----------+ +-------------------+--------------------------+---------+----------+
| dccp-service-code | If RFC6773 is not being | M | CAUTION | | dccp-service- | If RFC6773 is not being | M | CAUTION |
| | used in addition to | | | | code | used in addition to | | |
| | RFC5762, the port in | | | | | RFC5762, the port in the | | |
| | the "m=" line is a DCCP | | | | | "m=" line is a DCCP | | |
| | port. DCCP being a | | | | | port. DCCP being a | | |
| | connection oriented | | | | | connection oriented | | |
| | protocol does not allow | | | | | protocol does not allow | | |
| | multiple connections on | | | | | multiple connections on | | |
| | the same 5-tuple | | | | | the same 5-tuple | | |
| | | | | | | | | |
+--------------------+-------------------------+---------+----------+ +-------------------+--------------------------+---------+----------+
5.8 RFC5762 Attribute Analysis 5.8 RFC5762 Attribute Analysis
NOTE: If RFC6773 is being used in addition to RFC5762 and provided NOTE: If RFC6773 is being used in addition to RFC5762 and provided
that DCCP-in-UDP layer has additional demultiplexing, then it can be that DCCP-in-UDP layer has additional demultiplexing, then it can be
possible to use different DCCP service codes for each DCCP flow, possible to use different DCCP service codes for each DCCP flow,
given each uses a different DCCP port. Although doing so might given each uses a different DCCP port. Although doing so might
conflict with the media type of the "m=" line. None of this is conflict with the media type of the "m=" line. None of this is
standardized yet and it wouldn't work as explained. Hence performing standardized yet and it wouldn't work as explained. Hence performing
multiplexing is not recommended even in this alternate scenario. multiplexing is not recommended even in this alternate scenario.
5.9. RFC6773: DCCP-UDP Encapsulation 5.9. RFC6773: DCCP-UDP Encapsulation
[RFC6773] specifies an alternative encapsulation of DCCP, referred to [RFC6773] specifies an alternative encapsulation of DCCP, referred to
as DCCP-UDP. This encapsulation allows DCCP to be carried through as DCCP-UDP. This encapsulation allows DCCP to be carried through
the current generation of Network Address Translation (NAT) middle the current generation of Network Address Translation (NAT) middle
boxes without modification of those middle boxes. boxes without modification of those middle boxes.
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| dccp-port | Multiplexing is not recommended | M | CAUTION | | dccp- | Multiplexing is not recommended | M | CAUTION |
| | due to potential conflict between | | | | port | due to potential conflict between | | |
| | the port used for DCCP | | | | | the port used for DCCP | | |
| | en/decapsulation and the RTP | | | | | en/decapsulation and the RTP | | |
| | | | | | | | | |
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
5.9 RFC6773 Attribute Analysis 5.9 RFC6773 Attribute Analysis
NOTE: RFC6773 is about tunneling DCCP in UDP, with the UDP port being NOTE: RFC6773 is about tunneling DCCP in UDP, with the UDP port being
the port of the DCCP en-/de-capsulation service. This encapsulation the port of the DCCP en-/de-capsulation service. This encapsulation
allows arbitrary DCCP packets to be encapsulated and the DCCP port allows arbitrary DCCP packets to be encapsulated and the DCCP port
chosen can conflict with the port chosen for the RTP traffic. For chosen can conflict with the port chosen for the RTP traffic. For
multiplexing several DCCP-in-UDP encapsulations on the same UDP port multiplexing several DCCP-in-UDP encapsulations on the same UDP port
with no RTP traffic on the same port implies collapsing several DCCP with no RTP traffic on the same port implies collapsing several DCCP
port spaces together. This can or cannot work depending on the port spaces together. This can or cannot work depending on the
nature of DCCP encapsulation and ports choices thus rendering it to nature of DCCP encapsulation and ports choices thus rendering it to
be very application dependent. be very application dependent.
5.10. RFC5506: Reduced-Size RTCP in RTP Profile 5.10. RFC5506: Reduced-Size RTCP in RTP Profile
[RFC5506] discusses benefits and issues that arise when allowing RTCP [RFC5506] discusses benefits and issues that arise when allowing RTCP
packets to be transmitted with reduced size. packets to be transmitted with reduced size.
+-------------+--------------------------------+-------+------------+ +------------+----------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------+--------------------------------+-------+------------+ +------------+----------------------------------+-------+-----------+
| rtcp-rsize | Reduced size RTCP affects the | M | IDENTICAL | | rtcp- | Reduced size RTCP affects the | M | IDENTICAL |
| | entire RTP session | | | | rsize | entire RTP session | | |
| | | | | | | | | |
+-------------+--------------------------------+-------+------------+ +------------+----------------------------------+-------+-----------+
5.10 RFC5506 Attribute Analysis 5.10 RFC5506 Attribute Analysis
5.11. RFC6787: Media Resource Control Protocol Version 2 5.11. RFC6787: Media Resource Control Protocol Version 2
The Media Resource Control Protocol Version 2 (MRCPv2) allows client The Media Resource Control Protocol Version 2 (MRCPv2) allows client
hosts to control media service resources such as speech synthesizers, hosts to control media service resources such as speech synthesizers,
recognizers, verifiers, and identifiers residing in servers on the recognizers, verifiers, and identifiers residing in servers on the
network. MRCPv2 is not a "stand-alone" protocol -- it relies on network. MRCPv2 is not a "stand-alone" protocol -- it relies on
other protocols, such as the SIP, to coordinate MRCPv2 clients and other protocols, such as the SIP, to coordinate MRCPv2 clients and
skipping to change at page 20, line 5 skipping to change at page 21, line 5
5.11 RFC6787 Attribute Analysis 5.11 RFC6787 Attribute Analysis
5.12. RFC5245: ICE 5.12. RFC5245: ICE
[RFC5245] describes a protocol for NAT traversal for UDP-based [RFC5245] describes a protocol for NAT traversal for UDP-based
multimedia sessions established with the offer/answer model. ICE multimedia sessions established with the offer/answer model. ICE
makes use of the Session Traversal Utilities for NAT (STUN) protocol makes use of the Session Traversal Utilities for NAT (STUN) protocol
and its extension, Traversal Using Relay NAT (TURN). ICE can be used and its extension, Traversal Using Relay NAT (TURN). ICE can be used
by any protocol utilizing the offer/answer model, such as the SIP. by any protocol utilizing the offer/answer model, such as the SIP.
+--------------------+-------------------------+-------+------------+ +-------------------+---------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------------------+-------------------------+-------+------------+ +-------------------+---------------------------+-------+-----------+
| ice-lite | Not Impacted | S | NORMAL | | ice-lite | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-options | Not Impacted | S | NORMAL | | ice-options | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-mismatch | Not Impacted | S | NORMAL | | ice-mismatch | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-pwd | ice-pwd MUST be the one | B | TRANSPORT | | ice-pwd | ice-pwd MUST be the one | B | TRANSPORT |
| | that corresponds to the | | | | | that corresponds to the | | |
| | "m=" line chosen for | | | | | "m=" line chosen for | | |
| | setting up the | | | | | setting up the underlying | | |
| | underlying transport | | | | | transport flow | | |
| | flow | | | | | | | |
| | | | | | ice-ufrag | ice-ufrag MUST be the one | B | TRANSPORT |
| ice-ufrag | ice-ufrag MUST be the | B | TRANSPORT | | | that corresponds to the | | |
| | one that corresponds to | | | | | "m=" line chosen for | | |
| | the "m=" line chosen | | | | | setting up the underlying | | |
| | for setting up the | | | | | transport flow | | |
| | underlying transport | | | | | | | |
| | flow | | | | candidate | ice candidate MUST be the | M | TRANSPORT |
| | | | | | | one that corresponds to | | |
| candidate | ice candidate MUST be | M | TRANSPORT | | | the "m=" line chosen for | | |
| | the one that | | | | | setting up the underlying | | |
| | corresponds to the "m=" | | | | | transport flow | | |
| | line chosen for setting | | | | | | | |
| | up the underlying | | | | remote- | ice remote candidate MUST | M | TRANSPORT |
| | transport flow | | | | candidates | be the one that | | |
| | | | | | | corresponds to the "m=" | | |
| remote-candidates | ice remote candidate | M | TRANSPORT | | | line chosen for setting | | |
| | MUST be the one that | | | | | up the underlying | | |
| | corresponds to the "m=" | | | | | transport flow | | |
| | line chosen for setting | | | | | | | |
| | up the underlying | | | +-------------------+---------------------------+-------+-----------+
| | transport flow | | |
| | | | |
+--------------------+-------------------------+-------+------------+
5.12 RFC5245 Attribute Analysis 5.12 RFC5245 Attribute Analysis
5.13. RFC5285: RTP Header Extensions 5.13. RFC5285: RTP Header Extensions
[RFC5285] provides a general mechanism to use the header extension [RFC5285] provides a general mechanism to use the header extension
feature of RTP. It provides the option to use a small number of feature of RTP. It provides the option to use a small number of
small extensions in each RTP packet, where the universe of possible small extensions in each RTP packet, where the universe of possible
extensions is large and registration is de-centralized. The actual extensions is large and registration is de-centralized. The actual
extensions in use in a session are signaled in the setup information extensions in use in a session are signaled in the setup information
for that session. for that session.
+---------+--------------------------------------+-------+----------+ +--------+---------------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------+--------------------------------------+-------+----------+ +--------+---------------------------------------+-------+----------+
| extmap | Refer to the document defining the | B | SPECIAL | | extmap | Refer to the document defining the | B | SPECIAL |
| | specific RTP Extension | | | | | specific RTP Extension | | |
| | | | | | | | | |
+---------+--------------------------------------+-------+----------+ +--------+---------------------------------------+-------+----------+
5.13 RFC5285 Attribute Analysis 5.13 RFC5285 Attribute Analysis
5.14. RFC3605: RTCP attribute in SDP 5.14. RFC3605: RTCP attribute in SDP
Originally, SDP assumed that RTP and RTCP were carried on consecutive Originally, SDP assumed that RTP and RTCP were carried on consecutive
ports. However, this is not always true when NATs are involved. ports. However, this is not always true when NATs are involved.
[RFC3605] specifies an early mechanism to indicate the RTCP port. [RFC3605] specifies an early mechanism to indicate the RTCP port.
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
| rtcp | RTCP Port MUST be the one that | M | TRANSPORT | | rtcp | RTCP Port MUST be the one that | M | TRANSPORT |
| | corresponds to the "m=" line chosen | | | | | corresponds to the "m=" line chosen | | |
| | for setting up the underlying | | | | | for setting up the underlying | | |
| | transport flow. | | | | | transport flow. | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
5.14 RFC3605 Attribute Analysis 5.14 RFC3605 Attribute Analysis
5.15. RFC5576: Source-Specific SDP Attributes 5.15. RFC5576: Source-Specific SDP Attributes
[RFC5576] defines a mechanism to describe RTP media sources, which [RFC5576] defines a mechanism to describe RTP media sources, which
are identified by their synchronization source (SSRC) identifiers, in are identified by their synchronization source (SSRC) identifiers, in
SDP, to associate attributes with these sources, and to express SDP, to associate attributes with these sources, and to express
relationships among sources. It also defines several source-level relationships among sources. It also defines several source-level
attributes that can be used to describe properties of media sources. attributes that can be used to describe properties of media sources.
+----------------+----------------------+-------+-------------------+ +---------------+------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+----------------+----------------------+-------+-------------------+ +---------------+------------------------+-------+------------------+
| ssrc | Refer to Notes below | M | NORMAL | | ssrc | Refer to Notes below | M | NORMAL |
| | | | | | | | | |
| ssrc-group | Refer to Section 9 | M | NORMAL | | ssrc-group | Refer to Section 9 for | M | NORMAL |
| | for specific | | | | | specific analysis of | | |
| | analysis of the | | | | | the grouping | | |
| | grouping semantics | | | | | semantics | | |
| | | | | | | | | |
| cname | Not Impacted | SR | NORMAL | | cname | Not Impacted | SR | NORMAL |
| | | | | | | | | |
| previous-ssrc | Refer to notes below | SR | NORMAL | | previous- | Refer to notes below | SR | NORMAL |
| | | | | | ssrc | | | |
| fmtp | The attribute value | SR | IDENTICAL-PER-PT | | | | | |
| | MUST be same for a | | | | fmtp | The attribute value | SR | IDENTICAL-PER- |
| | given codec | | | | | MUST be same for a | | PT |
| | configuration | | | | | given codec | | |
| | | | | | | configuration | | |
+----------------+----------------------+-------+-------------------+ | | | | |
+---------------+------------------------+-------+------------------+
5.15 RFC5576 Attribute Analysis 5.15 RFC5576 Attribute Analysis
NOTE: If SSRCs are repeated across "m=" lines being multiplexed, they NOTE: If SSRCs are repeated across "m=" lines being multiplexed, they
MUST all represent the same underlying RTP Source. MUST all represent the same underlying RTP Source.
5.16. RFC7273: RTP Clock Source Signalling 5.16. RFC7273: RTP Clock Source Signalling
[RFC7273] specifies SDP signalling that identifies timestamp [RFC7273] specifies SDP signalling that identifies timestamp
reference clock sources and SDP signalling that identifies the media reference clock sources and SDP signalling that identifies the media
skipping to change at page 24, line 5 skipping to change at page 25, line 5
[RFC6236] proposes a new generic session setup attribute to make it [RFC6236] proposes a new generic session setup attribute to make it
possible to negotiate different image attributes such as image size. possible to negotiate different image attributes such as image size.
A possible use case is to make it possible for a low-end hand-held A possible use case is to make it possible for a low-end hand-held
terminal to display video without the need to rescale the image, terminal to display video without the need to rescale the image,
something that may consume large amounts of memory and processing something that may consume large amounts of memory and processing
power. The document also helps to maintain an optimal bitrate for power. The document also helps to maintain an optimal bitrate for
video as only the image size that is desired by the receiver is video as only the image size that is desired by the receiver is
transmitted. transmitted.
+------------+--------------------------+-------+-------------------+ +-----------+----------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+--------------------------+-------+-------------------+ +-----------+----------------------------+-------+------------------+
| imageattr | The attribute value MUST | M | IDENTICAL-PER-PT | | imageattr | The attribute value MUST | M | IDENTICAL-PER- |
| | be same for a given | | | | | be same for a given codec | | PT |
| | codec configuration | | | | | configuration | | |
| | | | | | | | | |
+------------+--------------------------+-------+-------------------+ +-----------+----------------------------+-------+------------------+
5.17 RFC6236 Attribute Analysis 5.17 RFC6236 Attribute Analysis
5.18. RFC7197: Duplication Delay Attribute in SDP 5.18. RFC7197: Duplication Delay Attribute in SDP
[RFC7197] defines an attribute to indicate the presence of temporally [RFC7197] defines an attribute to indicate the presence of temporally
redundant media streams and the duplication delay in SDP. redundant media streams and the duplication delay in SDP.
+--------------------+---------------+-------+--------------+ +--------------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
skipping to change at page 25, line 8 skipping to change at page 26, line 8
[RFC6285] describes a method using the existing RTP and RTCP [RFC6285] describes a method using the existing RTP and RTCP
machinery that reduces the acquisition delay. In this method, an machinery that reduces the acquisition delay. In this method, an
auxiliary unicast RTP session carrying the Reference Information to auxiliary unicast RTP session carrying the Reference Information to
the receiver precedes or accompanies the multicast stream. This the receiver precedes or accompanies the multicast stream. This
unicast RTP flow can be transmitted at a faster than natural bitrate unicast RTP flow can be transmitted at a faster than natural bitrate
to further accelerate the acquisition. The motivating use case for to further accelerate the acquisition. The motivating use case for
this capability is multicast applications that carry real-time this capability is multicast applications that carry real-time
compressed audio and video. compressed audio and video.
+---------------+-------------------+-------+--------------+ +---------------+------------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+---------------+-------------------+-------+--------------+ +---------------+------------------+-------+--------------+
| rams-updates | Not recommended | M | CAUTION | | rams-updates | Not recommended | M | CAUTION |
| | | | | | | | | |
+---------------+-------------------+-------+--------------+ +---------------+------------------+-------+--------------+
5.20 RFC6285 Attribute Analysis 5.20 RFC6285 Attribute Analysis
5.21. RFC6230: Media Control Channel Framework 5.21. RFC6230: Media Control Channel Framework
[RFC6230] describes a framework and protocol for application [RFC6230] describes a framework and protocol for application
deployment where the application programming logic and media deployment where the application programming logic and media
processing are distributed. This implies that application processing are distributed. This implies that application
programming logic can seamlessly gain access to appropriate resources programming logic can seamlessly gain access to appropriate resources
that are not co-located on the same physical network entity. The that are not co-located on the same physical network entity. The
skipping to change at page 26, line 5 skipping to change at page 27, line 5
5.22. RFC6364: SDP Elements for FEC Framework 5.22. RFC6364: SDP Elements for FEC Framework
[RFC6364] specifies the use of SDP to describe the parameters [RFC6364] specifies the use of SDP to describe the parameters
required to signal the Forward Error Correction (FEC) Framework required to signal the Forward Error Correction (FEC) Framework
Configuration Information between the sender(s) and receiver(s). Configuration Information between the sender(s) and receiver(s).
This document also provides examples that show the semantics for This document also provides examples that show the semantics for
grouping multiple source and repair flows together for the grouping multiple source and repair flows together for the
applications that simultaneously use multiple instances of the FEC applications that simultaneously use multiple instances of the FEC
Framework. Framework.
+------------------+-----------------------------+-------+----------+ +-----------------+------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------------+-----------------------------+-------+----------+ +-----------------+------------------------------+-------+----------+
| fec-source-flow | Refer to the document | M | SPECIAL | | fec-source- | Refer to the document | M | SPECIAL |
| | defining specific FEC | | | | flow | defining specific FEC | | |
| | Scheme | | | | | Scheme | | |
| | | | | | | | | |
| fec-repair-flow | Refer to the document | M | SPECIAL | | fec-repair- | Refer to the document | M | SPECIAL |
| | defining specific FEC | | | | flow | defining specific FEC | | |
| | Scheme | | | | | Scheme | | |
| | | | | | | | | |
| repair-window | Refer to the document | M | SPECIAL | | repair-window | Refer to the document | M | SPECIAL |
| | defining specific FEC | | | | | defining specific FEC | | |
| | Scheme | | | | | Scheme | | |
| | | | | | | | | |
+------------------+-----------------------------+-------+----------+ +-----------------+------------------------------+-------+----------+
5.22 RFC6364 Attribute Analysis 5.22 RFC6364 Attribute Analysis
5.23. RFC4796: Content Attribute 5.23. RFC4796: Content Attribute
[RFC4796] defines a new SDP media-level attribute, 'content'. The [RFC4796] defines a new SDP media-level attribute, 'content'. The
'content' attribute defines the content of the media stream to a more 'content' attribute defines the content of the media stream to a more
detailed level than the media description line. The sender of an SDP detailed level than the media description line. The sender of an SDP
session description can attach the 'content' attribute to one or more session description can attach the 'content' attribute to one or more
media streams. The receiving application can then treat each media media streams. The receiving application can then treat each media
skipping to change at page 27, line 42 skipping to change at page 28, line 42
5.25. RFC6284: Port Mapping between Unicast and Multicast RTP Sessions 5.25. RFC6284: Port Mapping between Unicast and Multicast RTP Sessions
[RFC6284] presents a port mapping solution that allows RTP receivers [RFC6284] presents a port mapping solution that allows RTP receivers
to choose their own ports for an auxiliary unicast session in RTP to choose their own ports for an auxiliary unicast session in RTP
applications using both unicast and multicast services. The solution applications using both unicast and multicast services. The solution
provides protection against denial-of-service or packet amplification provides protection against denial-of-service or packet amplification
attacks that could be used to cause one or more RTP packets to be attacks that could be used to cause one or more RTP packets to be
sent to a victim client. sent to a victim client.
+------------------+-----------------------------+-------+----------+ +-----------------+------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------------+-----------------------------+-------+----------+ +-----------------+------------------------------+-------+----------+
| portmapping-req | Not recommended, if port | M | CAUTION | | portmapping- | Not recommended, if port | M | CAUTION |
| | mapping is required by the | | | | req | mapping is required by the | | |
| | application | | | | | application | | |
| | | | | | | | | |
+------------------+-----------------------------+-------+----------+ +-----------------+------------------------------+-------+----------+
5.25 RFC6284 Attribute Analysis 5.25 RFC6284 Attribute Analysis
5.26. RFC6714: MSRP-CEMA 5.26. RFC6714: MSRP-CEMA
[RFC6714] defines a Message Session Relay Protocol (MSRP) extension, [RFC6714] defines a Message Session Relay Protocol (MSRP) extension,
Connection Establishment for Media Anchoring (CEMA). Support of this Connection Establishment for Media Anchoring (CEMA). Support of this
extension is optional. The extension allows middle boxes to anchor extension is optional. The extension allows middle boxes to anchor
the MSRP connection, without the need for middle boxes to modify the the MSRP connection, without the need for middle boxes to modify the
MSRP messages; thus, it also enables secure end-to-end MSRP MSRP messages; thus, it also enables secure end-to-end MSRP
skipping to change at page 30, line 5 skipping to change at page 31, line 5
5.29. RFC6849: SDP and RTP Media Loopback Extension 5.29. RFC6849: SDP and RTP Media Loopback Extension
[RFC6849] adds new SDP media types and attributes, which enable [RFC6849] adds new SDP media types and attributes, which enable
establishment of media sessions where the media is looped back to the establishment of media sessions where the media is looped back to the
transmitter. Such media sessions will serve as monitoring and transmitter. Such media sessions will serve as monitoring and
troubleshooting tools by providing the means for measurement of more troubleshooting tools by providing the means for measurement of more
advanced Voice over IP (VoIP), Real-time Text, and Video over IP advanced Voice over IP (VoIP), Real-time Text, and Video over IP
performance metrics. performance metrics.
+---------------------+-----------------+-------+-------------------+ +--------------------+-------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+---------------------+-----------------+-------+-------------------+ +--------------------+-------------------+-------+------------------+
| loopback rtp-pkt- | The attribute | M | IDENTICAL-PER-PT | | loopback rtp-pkt- | The attribute | M | IDENTICAL-PER- |
| loopback | value MUST be | | | | loopback | value MUST be | | PT |
| | same for a | | | | | same for a given | | |
| | given codec | | | | | codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| loopback rtp-media- | The attribute | M | IDENTICAL-PER-PT | | loopback rtp- | The attribute | M | IDENTICAL-PER- |
| loopback | value MUST be | | | | media-loopback | value MUST be | | PT |
| | same for a | | | | | same for a given | | |
| | given codec | | | | | codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| loopback-source | Not Impacted | M | NORMAL | | loopback-source | Not Impacted | M | NORMAL |
| | | | | | | | | |
| loopback-mirror | Not Impacted | M | NORMAL | | loopback-mirror | Not Impacted | M | NORMAL |
| | | | | | | | | |
+---------------------+-----------------+-------+-------------------+ +--------------------+-------------------+-------+------------------+
5.29 RFC6849 Analysis 5.29 RFC6849 Analysis
5.30. RFC5760: RTCP with Unicast Feedback 5.30. RFC5760: RTCP with Unicast Feedback
[RFC5760] specifies an extension to RTCP to use unicast feedback to a [RFC5760] specifies an extension to RTCP to use unicast feedback to a
multicast sender. The proposed extension is useful for single-source multicast sender. The proposed extension is useful for single-source
multicast sessions such as Source-Specific Multicast (SSM) multicast sessions such as Source-Specific Multicast (SSM)
communication where the traditional model of many-to-many group communication where the traditional model of many-to-many group
communication is either not available or not desired. communication is either not available or not desired.
+---------------+------------------------------+-------+------------+ +--------------+--------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------------+------------------------------+-------+------------+ +--------------+--------------------------------+-------+-----------+
| rtcp-unicast | The attribute MUST be | M | IDENTICAL | | rtcp- | The attribute MUST be reported | M | IDENTICAL |
| | reported across all "m=" | | | | unicast | across all "m=" lines | | |
| | lines multiplexed | | | | | multiplexed | | |
| | | | | | | | | |
+---------------+------------------------------+-------+------------+ +--------------+--------------------------------+-------+-----------+
5.30 RFC5760 Attribute Analysis 5.30 RFC5760 Attribute Analysis
5.31. RFC3611: RTCP XR 5.31. RFC3611: RTCP XR
[RFC3611] defines the Extended Report (XR) packet type for RTCP, and [RFC3611] defines the Extended Report (XR) packet type for RTCP, and
defines how the use of XR packets can be signaled by an application defines how the use of XR packets can be signaled by an application
if it employs the Session Description Protocol (SDP). if it employs the Session Description Protocol (SDP).
+----------+---------------+-------+--------------+ +----------+---------------+-------+--------------+
skipping to change at page 33, line 5 skipping to change at page 34, line 5
of indicating compatible configurations in a bundle. of indicating compatible configurations in a bundle.
5.34. RFC7006: Miscellaneous Capabilities Negotiation SDP 5.34. RFC7006: Miscellaneous Capabilities Negotiation SDP
[RFC7006] extends the SDP capability negotiation framework to allow [RFC7006] extends the SDP capability negotiation framework to allow
endpoints to negotiate three additional SDP capabilities. In endpoints to negotiate three additional SDP capabilities. In
particular, this memo provides a mechanism to negotiate bandwidth particular, this memo provides a mechanism to negotiate bandwidth
("b=" line), connection data ("c=" line), and session or media titles ("b=" line), connection data ("c=" line), and session or media titles
("i=" line for each session or media). ("i=" line for each session or media).
+----------+-----------------------------------+-------+------------+ +---------+-------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------+-----------------------------------+-------+------------+ +---------+-------------------------------------+-------+-----------+
| bcap | Inherit the category SUM as | B | INHERIT | | bcap | Inherit the category SUM as | B | INHERIT |
| | applicable to b= attribute | | | | | applicable to b= attribute | | |
| | | | | | | | | |
| bcap-v0 | Not Impacted | B | NORMAL | | bcap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
| ccap | The connection address type MUST | B | IDENTICAL | | ccap | The connection address type MUST be | B | IDENTICAL |
| | be identical across all the | | | | | identical across all the | | |
| | multiplexed "m=" lines | | | | | multiplexed "m=" lines | | |
| | | | | | | | | |
| ccap-v0 | Not Impacted | B | NORMAL | | ccap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
| icap | Not Impacted | B | NORMAL | | icap | Not Impacted | B | NORMAL |
| | | | | | | | | |
| icap-v0 | Not Impacted | B | NORMAL | | icap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
+----------+-----------------------------------+-------+------------+ +---------+-------------------------------------+-------+-----------+
5.34 RFC7006 - Attribute Analysis 5.34 RFC7006 - Attribute Analysis
5.35. RFC4567: Key Management Extensions for SDP and RTSP 5.35. RFC4567: Key Management Extensions for SDP and RTSP
[RFC4567] defines general extensions for SDP and Real Time Streaming [RFC4567] defines general extensions for SDP and Real Time Streaming
Protocol (RTSP) to carry messages, as specified by a key management Protocol (RTSP) to carry messages, as specified by a key management
protocol, in order to secure the media. These extensions are protocol, in order to secure the media. These extensions are
presented as a framework, to be used by one or more key management presented as a framework, to be used by one or more key management
protocols. As such, their use is meaningful only when complemented protocols. As such, their use is meaningful only when complemented
by an appropriate key management protocol. by an appropriate key management protocol.
+-----------+----------------------------------+-------+------------+ +----------+------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------+----------------------------------+-------+------------+ +----------+------------------------------------+-------+-----------+
| key-mgmt | Key management protocol MUST be | B | IDENTICAL | | key- | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the "m=" | | | | mgmt | identical across all the "m=" | | |
| | lines | | | | | lines | | |
| | | | | | | | | |
| mikey | Key management protocol MUST be | B | IDENTICAL | | mikey | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the "m=" | | | | | identical across all the "m=" | | |
| | lines | | | | | lines | | |
| | | | | | | | | |
+-----------+----------------------------------+-------+------------+ +----------+------------------------------------+-------+-----------+
5.35 RFC4567 Attribute Analysis 5.35 RFC4567 Attribute Analysis
5.36. RFC4572: Comedia over TLS in SDP 5.36. RFC4572: Comedia over TLS in SDP
[RFC4572] specifies how to establish secure connection-oriented media [RFC4572] specifies how to establish secure connection-oriented media
transport sessions over the Transport Layer Security (TLS) protocol transport sessions over the Transport Layer Security (TLS) protocol
using SDP. It defines a new SDP protocol identifier, 'TCP/TLS'. It using SDP. It defines a new SDP protocol identifier, 'TCP/TLS'. It
also defines the syntax and semantics for an SDP 'fingerprint' also defines the syntax and semantics for an SDP 'fingerprint'
attribute that identifies the certificate that will be presented for attribute that identifies the certificate that will be presented for
the TLS session. This mechanism allows media transport over TLS the TLS session. This mechanism allows media transport over TLS
connections to be established securely, so long as the integrity of connections to be established securely, so long as the integrity of
session descriptions is assured. session descriptions is assured.
+--------------+-------------------------------+-------+------------+ +-------------+---------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------------+-------------------------------+-------+------------+ +-------------+---------------------------------+-------+-----------+
| fingerprint | fingerprint value MUST be the | B | TRANSPORT | | fingerprint | fingerprint value MUST be the | B | TRANSPORT |
| | one that corresponds to the | | | | | one that corresponds to the | | |
| | "m=" line chosen for setting | | | | | "m=" line chosen for setting up | | |
| | up the underlying transport | | | | | the underlying transport flow | | |
| | flow | | | | | | | |
| | | | | +-------------+---------------------------------+-------+-----------+
+--------------+-------------------------------+-------+------------+
5.36 RFC4572 Attribute Analysis 5.36 RFC4572 Attribute Analysis
5.37. RFC4570: SDP Source Filters 5.37. RFC4570: SDP Source Filters
[RFC4570] describes how to adapt SDP to express one or more source [RFC4570] describes how to adapt SDP to express one or more source
addresses as a source filter for one or more destination "connection" addresses as a source filter for one or more destination "connection"
addresses. It defines the syntax and semantics for an SDP "source- addresses. It defines the syntax and semantics for an SDP "source-
filter" attribute that may reference either IPv4 or IPv6 address(es) filter" attribute that may reference either IPv4 or IPv6 address(es)
as either an inclusive or exclusive source list for either multicast as either an inclusive or exclusive source list for either multicast
or unicast destinations. In particular, an inclusive source-filter or unicast destinations. In particular, an inclusive source-filter
can be used to specify a Source-Specific Multicast (SSM) session. can be used to specify a Source-Specific Multicast (SSM) session.
+----------------+-----------------------------+-------+------------+ +---------------+-------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------------+-----------------------------+-------+------------+ +---------------+-------------------------------+-------+-----------+
| source-filter | The attribute MUST be | B | IDENTICAL | | source- | The attribute MUST be | B | IDENTICAL |
| | repeated across all "m=" | | | | filter | repeated across all "m=" | | |
| | lines multiplexed | | | | | lines multiplexed | | |
| | | | | | | | | |
+----------------+-----------------------------+-------+------------+ +---------------+-------------------------------+-------+-----------+
5.37 RFC4570 Attribute Analysis 5.37 RFC4570 Attribute Analysis
5.38. RFC6128: RTCP Port for Multicast Sessions 5.38. RFC6128: RTCP Port for Multicast Sessions
SDP has an attribute that allows RTP applications to specify an SDP has an attribute that allows RTP applications to specify an
address and a port associated with the RTCP traffic. In RTP-based address and a port associated with the RTCP traffic. In RTP-based
source-specific multicast (SSM) sessions, the same attribute is used source-specific multicast (SSM) sessions, the same attribute is used
to designate the address and the RTCP port of the Feedback Target in to designate the address and the RTCP port of the Feedback Target in
the SDP description. However, the RTCP port associated with the SSM the SDP description. However, the RTCP port associated with the SSM
session itself cannot be specified by the same attribute to avoid session itself cannot be specified by the same attribute to avoid
ambiguity, and thus, is required to be derived from the "m=" line of ambiguity, and thus, is required to be derived from the "m=" line of
the media description. Deriving the RTCP port from the "m=" line the media description. Deriving the RTCP port from the "m=" line
imposes an unnecessary restriction. [RFC6128] removes this imposes an unnecessary restriction. [RFC6128] removes this
restriction by introducing a new SDP attribute. restriction by introducing a new SDP attribute.
+-----------------+----------------------------+-------+------------+ +----------------+------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------------+----------------------------+-------+------------+ +----------------+------------------------------+-------+-----------+
| multicast-rtcp | Multicast RTCP port MUST | B | IDENTICAL | | multicast- | Multicast RTCP port MUST be | B | IDENTICAL |
| | be identical across all | | | | rtcp | identical across all the | | |
| | the "m=" lines | | | | | "m=" lines | | |
| | | | | | | | | |
+-----------------+----------------------------+-------+------------+ +----------------+------------------------------+-------+-----------+
5.38 RFC6128 Attribute Analysis 5.38 RFC6128 Attribute Analysis
5.39. RFC6189: ZRTP 5.39. RFC6189: ZRTP
[RFC6189] defines ZRTP, a protocol for media path Diffie-Hellman [RFC6189] defines ZRTP, a protocol for media path Diffie-Hellman
exchange to agree on a session key and parameters for establishing exchange to agree on a session key and parameters for establishing
unicast SRTP sessions for (VoIP applications. unicast SRTP sessions for (VoIP applications.
+------------+---------------------------------+-------+------------+ +-----------+-----------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------+---------------------------------+-------+------------+ +-----------+-----------------------------------+-------+-----------+
| zrtp-hash | zrtp-hash attribute MUST be the | M | TRANSPORT | | zrtp- | zrtp-hash attribute MUST be the | M | TRANSPORT |
| | one that corresponds to the | | | | hash | one that corresponds to the "m=" | | |
| | "m=" line chosen for setting up | | | | | line chosen for setting up the | | |
| | the underlying transport flow | | | | | underlying transport flow | | |
| | | | | | | | | |
+------------+---------------------------------+-------+------------+ +-----------+-----------------------------------+-------+-----------+
5.39 RFC6189 Attribute Analysis 5.39 RFC6189 Attribute Analysis
5.40. RFC4145: Connection-Oriented Media 5.40. RFC4145: Connection-Oriented Media
[RFC4145] describes how to express media transport over TCP using [RFC4145] describes how to express media transport over TCP using
SDP. It defines the SDP 'TCP' protocol identifier, the SDP 'setup' SDP. It defines the SDP 'TCP' protocol identifier, the SDP 'setup'
attribute, which describes the connection setup procedure, and the attribute, which describes the connection setup procedure, and the
SDP 'connection' attribute, which handles connection reestablishment. SDP 'connection' attribute, which handles connection reestablishment.
+-------------+--------------------------------+-------+------------+ +------------+----------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------+--------------------------------+-------+------------+ +------------+----------------------------------+-------+-----------+
| setup | The setup attribute MUST be | B | TRANSPORT | | setup | The setup attribute MUST be the | B | TRANSPORT |
| | the one that corresponds to | | | | | one that corresponds to the "m=" | | |
| | the "m=" line chosen for | | | | | line chosen for setting up the | | |
| | setting up the underlying | | | | | underlying transport flow. | | |
| | transport flow. | | | | | | | |
| | | | | | connection | The connection attribute MUST be | B | TRANSPORT |
| connection | The connection attribute MUST | B | TRANSPORT | | | the one that corresponds to the | | |
| | be the one that corresponds to | | | | | "m=" line chosen for setting up | | |
| | the "m=" line chosen for | | | | | the underlying transport flow. | | |
| | setting up the underlying | | | | | | | |
| | transport flow. | | | +------------+----------------------------------+-------+-----------+
| | | | |
+-------------+--------------------------------+-------+------------+
5.40 RFC4145 Attribute Analysis 5.40 RFC4145 Attribute Analysis
5.41. RFC6947: The SDP altc Attribute 5.41. RFC6947: The SDP altc Attribute
[RFC6947] proposes a mechanism that allows the same SDP offer to [RFC6947] proposes a mechanism that allows the same SDP offer to
carry multiple IP addresses of different address families (e.g., IPv4 carry multiple IP addresses of different address families (e.g., IPv4
and IPv6). The proposed attribute, the "altc" attribute, solves the and IPv6). The proposed attribute, the "altc" attribute, solves the
backward-compatibility problem that plagued Alternative Network backward-compatibility problem that plagued Alternative Network
Address Types (ANAT) due to their syntax. Address Types (ANAT) due to their syntax.
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
| altc | The IP Address and port MUST be the | M | TRANSPORT | | altc | The IP Address and port MUST be the | M | TRANSPORT |
| | one that corresponds to the "m=" | | | | | one that corresponds to the "m=" line | | |
| | line chosen for setting up the | | | | | chosen for setting up the underlying | | |
| | underlying transport flow | | | | | transport flow | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
5.41 RFC6947 Attribute Analysis 5.41 RFC6947 Attribute Analysis
5.42. RFC7195: SDP Extension for Circuit Switched Bearers in PSTN 5.42. RFC7195: SDP Extension for Circuit Switched Bearers in PSTN
[RFC7195] describes use cases, requirements, and protocol extensions [RFC7195] describes use cases, requirements, and protocol extensions
for using SDP offer/answer model for establishing audio and video for using SDP offer/answer model for establishing audio and video
media streams over circuit-switched bearers in the Public Switched media streams over circuit-switched bearers in the Public Switched
Telephone Network (PSTN). Telephone Network (PSTN).
+--------------------------+-------------------+-------+------------+ +-------------------------+-------------------+-------+-------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------------------------+-------------------+-------+------------+ +-------------------------+-------------------+-------+-------------+
| cs-correlation:callerid | Refer to notes | M | TBD | | cs- | Refer to notes | M | TBD |
| | below | | | | correlation:callerid | below | | |
| | | | | | | | | |
| cs-correlation:uuie | Refer to notes | M | TBD | | cs-correlation:uuie | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| cs-correlation:dtmf | Refer to notes | M | TBD | | cs-correlation:dtmf | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| cs-correlation:external | Refer to notes | M | TBD | | cs- | Refer to notes | M | TBD |
| | below | | | | correlation:external | below | | |
| | | | | | | | | |
+--------------------------+-------------------+-------+------------+ +-------------------------+-------------------+-------+-------------+
5.42 RFC7195 Attribute Analysis 5.42 RFC7195 Attribute Analysis
NOTE: [RFC7195] defines SDP attributes for establishing audio and NOTE: [RFC7195] defines SDP attributes for establishing audio and
video media streams over circuit-switched bearers by defining a new video media streams over circuit-switched bearers by defining a new
nettype value "PSTN". However, section 7.2 of nettype value "PSTN". However, section 7.2 of
[I-D.ietf-mmusic-sdp-bundle-negotiation] requires the "c=" line [I-D.ietf-mmusic-sdp-bundle-negotiation] requires the "c=" line
nettype value of "IN". If in future there exists a specification nettype value of "IN". If in future there exists a specification
that defines procedures to multiplex media streams over nettype that defines procedures to multiplex media streams over nettype
"PSTN", the multiplexing categories for attributes in this section "PSTN", the multiplexing categories for attributes in this section
skipping to change at page 38, line 21 skipping to change at page 39, line 21
5.43 RFC7272 Attribute Analysis 5.43 RFC7272 Attribute Analysis
5.44. RFC5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP 5.44. RFC5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP
Attributes Attributes
[RFC5159] provides descriptions of SDP attributes used by the Open [RFC5159] provides descriptions of SDP attributes used by the Open
Mobile Alliance's Broadcast Service and Content Protection Mobile Alliance's Broadcast Service and Content Protection
specification. specification.
+---------------------+-----------------------+-------+-------------+ +--------------------+-----------------------+-------+--------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux Category |
| | | | Category | +--------------------+-----------------------+-------+--------------+
+---------------------+-----------------------+-------+-------------+ | bcastversion | Not Impacted | S | NORMAL |
| bcastversion | Not Impacted | S | NORMAL | | | | | |
| | | | | | stkmstream | Not Impacted | B | NORMAL |
| stkmstream | Not Impacted | B | NORMAL | | | | | |
| | | | | | SRTPAuthentication | Needs further | M | TBD |
| SRTPAuthentication | Needs further | M | TBD | | | analysis | | |
| | analysis | | | | | | | |
| | | | | | SRTPROCTxRate | Needs further | M | TBD |
| SRTPROCTxRate | Needs further | M | TBD | | | analysis | | |
| | analysis | | | | | | | |
| | | | | +--------------------+-----------------------+-------+--------------+
+---------------------+-----------------------+-------+-------------+
5.44 RFC5159 Attribute Analysis 5.44 RFC5159 Attribute Analysis
5.45. RFC6193: Media Description for IKE in SDP 5.45. RFC6193: Media Description for IKE in SDP
[RFC6193] specifies how to establish a media session that represents [RFC6193] specifies how to establish a media session that represents
a virtual private network using the Session Initiation Protocol for a virtual private network using the Session Initiation Protocol for
the purpose of on-demand media/application sharing between peers. It the purpose of on-demand media/application sharing between peers. It
extends the protocol identifier of SDP so that it can negotiate use extends the protocol identifier of SDP so that it can negotiate use
of the Internet Key Exchange Protocol (IKE) for media sessions in the of the Internet Key Exchange Protocol (IKE) for media sessions in the
SDP offer/answer model. SDP offer/answer model.
+-------------------+----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------------+----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| ike-setup | Unlikely to use IKE in the | B | CAUTION | | ike-setup | Unlikely to use IKE in the | B | CAUTION |
| | context of multiplexing | | | | | context of multiplexing | | |
| | | | | | | | | |
| psk-fingerprint | Unlikely to use IKE in the | B | CAUTION | | psk-fingerprint | Unlikely to use IKE in the | B | CAUTION |
| | context of multiplexing | | | | | context of multiplexing | | |
| | | | | | | | | |
| ike-esp | Unlikely to use IKE in the | B | CAUTION | | ike-esp | Unlikely to use IKE in the | B | CAUTION |
| | context of multiplexing | | | | | context of multiplexing | | |
| | | | | | | | | |
| ike-esp-udpencap | Unlikely to use IKE in the | B | CAUTION | | ike-esp- | Unlikely to use IKE in the | B | CAUTION |
| | context of multiplexing | | | | udpencap | context of multiplexing | | |
| | | | | | | | | |
+-------------------+----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
5.45 RFC6193 Attribute Analysis 5.45 RFC6193 Attribute Analysis
5.46. RFC2326: Real Time Streaming Protocol 5.46. RFC2326: Real Time Streaming Protocol
The Real Time Streaming Protocol, or RTSP, is an application-level The Real Time Streaming Protocol, or RTSP, is an application-level
protocol for control over the delivery of data with real-time protocol for control over the delivery of data with real-time
properties. RTSP provides an extensible framework to enable properties. RTSP provides an extensible framework to enable
controlled, on-demand delivery of real-time data, such as audio and controlled, on-demand delivery of real-time data, such as audio and
video. video.
+----------+------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------+------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
| etag | RTSP is not supported for RTP | B | CAUTION | | etag | RTSP is not supported for RTP | B | CAUTION |
| | Stream multiplexing | | | | | Stream multiplexing | | |
| | | | | | | | | |
| range | RTSP is not supported for RTP | B | CAUTION | | range | RTSP is not supported for RTP | B | CAUTION |
| | Stream multiplexing | | | | | Stream multiplexing | | |
| | | | | | | | | |
| control | RTSP is not supported for RTP | B | CAUTION | | control | RTSP is not supported for RTP | B | CAUTION |
| | Stream multiplexing | | | | | Stream multiplexing | | |
| | | | | | | | | |
| mtag | RTSP is not supported for RTP | B | CAUTION | | mtag | RTSP is not supported for RTP | B | CAUTION |
| | Stream multiplexing | | | | | Stream multiplexing | | |
| | | | | | | | | |
+----------+------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
5.46 RFC2326 Attribute Analysis 5.46 RFC2326 Attribute Analysis
NOTE: [RFC2326] defines SDP attributes that are applicable in the NOTE: [RFC2326] defines SDP attributes that are applicable in the
declarative usage of SDP alone. For purposes of this document, only declarative usage of SDP alone. For purposes of this document, only
the Offer/Answer usage of SDP is considered as mandated by the Offer/Answer usage of SDP is considered as mandated by
[I-D.ietf-mmusic-sdp-bundle-negotiation]. [I-D.ietf-mmusic-sdp-bundle-negotiation].
5.47. RFC6064: SDP and RTSP Extensions for 3GPP 5.47. RFC6064: SDP and RTSP Extensions for 3GPP
skipping to change at page 42, line 5 skipping to change at page 43, line 5
| | | | | | | | | |
| 3GPP-QoE-Metrics:Content | Refer to | B | CAUTION | | 3GPP-QoE-Metrics:Content | Refer to | B | CAUTION |
| Switch Time | notes below | | | | Switch Time | notes below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Average Codec | Refer to | M | CAUTION | | 3GPP-QoE-Metrics:Average Codec | Refer to | M | CAUTION |
| Bitrate | notes below | | | | Bitrate | notes below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Codec | Refer to | M | CAUTION | | 3GPP-QoE-Metrics:Codec | Refer to | M | CAUTION |
| Information | notes below | | | | Information | notes below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Buffer Status | Refer to | M | CAUTION | | 3GPP-QoE-Metrics:Buffer | Refer to | M | CAUTION |
| | notes below | | | | Status | notes below | | |
| | | | | | | | | |
+--------------------------------+---------------+-------+----------+ +--------------------------------+---------------+-------+----------+
5.47 RFC6064 Attribute Analysis 5.47 RFC6064 Attribute Analysis
NOTE: [RFC6064] defines SDP attributes that are applicable in the NOTE: [RFC6064] defines SDP attributes that are applicable in the
declarative usage of SDP alone. For purposes of this document, only declarative usage of SDP alone. For purposes of this document, only
the Offer/Answer usage of SDP is considered as mandated by the Offer/Answer usage of SDP is considered as mandated by
[I-D.ietf-mmusic-sdp-bundle-negotiation]. [I-D.ietf-mmusic-sdp-bundle-negotiation].
5.48. RFC3108: ATM SDP 5.48. RFC3108: ATM SDP
[RFC3108] describes conventions for using SDP described for [RFC3108] describes conventions for using SDP described for
controlling ATM Bearer Connections, and any associated ATM Adaptation controlling ATM Bearer Connections, and any associated ATM Adaptation
Layer (AAL). Layer (AAL).
+------------------------+--------------------+-------+-------------+ +-----------------------+--------------------+-------+--------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux Category |
| | | | Category | +-----------------------+--------------------+-------+--------------+
+------------------------+--------------------+-------+-------------+ | aalType | Refer to notes | B | CAUTION |
| aalType | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | eecid | Refer to notes | B | CAUTION |
| eecid | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | capability | Refer to notes | B | CAUTION |
| capability | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | qosClass | Refer to notes | B | CAUTION |
| qosClass | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | bcob | Refer to notes | B | CAUTION |
| bcob | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | stc | Refer to notes | B | CAUTION |
| stc | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | upcc | Refer to notes | B | CAUTION |
| upcc | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | atmQOSparms | Refer to notes | B | CAUTION |
| atmQOSparms | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | atmTrfcDesc | Refer to notes | B | CAUTION |
| atmTrfcDesc | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | abrParms | Refer to notes | B | CAUTION |
| abrParms | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | abrSetup | Refer to notes | B | CAUTION |
| abrSetup | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | bearerType | Refer to notes | B | CAUTION |
| bearerType | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | lij | Refer to notes | B | CAUTION |
| lij | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | anycast | Refer to notes | B | CAUTION |
| anycast | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | cache | Refer to notes | B | CAUTION |
| cache | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | bearerSigIE | Refer to notes | B | CAUTION |
| bearerSigIE | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | aalApp | Refer to notes | B | CAUTION |
| aalApp | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | cbrRate | Refer to notes | B | CAUTION |
| cbrRate | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | sbc | Refer to notes | B | CAUTION |
| sbc | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | clkrec | Refer to notes | B | CAUTION |
| clkrec | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | fec | Refer to notes | B | CAUTION |
| fec | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | prtfl | Refer to notes | B | CAUTION |
| prtfl | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | structure | Refer to notes | B | CAUTION |
| structure | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | cpsSDUsize | Refer to notes | B | CAUTION |
| cpsSDUsize | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | aal2CPS | Refer to notes | B | CAUTION |
| aal2CPS | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | aal2CPSSDUrate | Refer to notes | B | CAUTION |
| aal2CPSSDUrate | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | aal2sscs3661unassured | Refer to notes | B | CAUTION |
| aal2sscs3661unassured | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | aal2sscs3661assured | Refer to notes | B | CAUTION |
| aal2sscs3661assured | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | aal2sscs3662 | Refer to notes | B | CAUTION |
| aal2sscs3662 | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | aal5sscop | Refer to notes | B | CAUTION |
| aal5sscop | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | atmmap | Refer to notes | B | CAUTION |
| atmmap | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | silenceSupp | Refer to notes | B | CAUTION |
| silenceSupp | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | ecan | Refer to notes | B | CAUTION |
| ecan | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | gc | Refer to notes | B | CAUTION |
| gc | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | profileDesc | Refer to notes | B | CAUTION |
| profileDesc | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | vsel | Refer to notes | B | CAUTION |
| vsel | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | dsel | Refer to notes | B | CAUTION |
| dsel | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | fsel | Refer to notes | B | CAUTION |
| fsel | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | onewaySel | Refer to notes | B | CAUTION |
| onewaySel | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | codecconfig | Refer to notes | B | CAUTION |
| codecconfig | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | isup_usi | Refer to notes | B | CAUTION |
| isup_usi | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | uiLayer1_Prot | Refer to notes | B | CAUTION |
| uiLayer1_Prot | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | chain | Refer to notes | B | CAUTION |
| chain | Refer to notes | B | CAUTION | | | below | | |
| | below | | | | | | | |
| | | | | +-----------------------+--------------------+-------+--------------+
+------------------------+--------------------+-------+-------------+
5.48 RFC3108 Attribute Analysis 5.48 RFC3108 Attribute Analysis
NOTE: RFC3108 describes conventions for using SDP for characterizing NOTE: RFC3108 describes conventions for using SDP for characterizing
ATM bearer connections using an AAL1, AAL2 or AAL5 adaptation layers. ATM bearer connections using an AAL1, AAL2 or AAL5 adaptation layers.
For AAL1, AAL2 and AAL5, bearer connections can be used to transport For AAL1, AAL2 and AAL5, bearer connections can be used to transport
single media streams. In addition, for AAL1 and AAL2, multiple media single media streams. In addition, for AAL1 and AAL2, multiple media
streams can be multiplexed into a bearer connection. For all streams can be multiplexed into a bearer connection. For all
adaptation types (AAL1, AAL2 and AAL5), bearer connections can be adaptation types (AAL1, AAL2 and AAL5), bearer connections can be
bundled into a single media group. In all cases addressed by bundled into a single media group. In all cases addressed by
skipping to change at page 45, line 4 skipping to change at page 46, line 4
directly into an ATM connection. RFC3108 does not address cases directly into an ATM connection. RFC3108 does not address cases
where ATM serves as a low-level transport pipe for IP packets which where ATM serves as a low-level transport pipe for IP packets which
in turn can carry one or more real-time (e.g. VoIP) media sessions in turn can carry one or more real-time (e.g. VoIP) media sessions
with a life-cycle different from that of the underlying ATM with a life-cycle different from that of the underlying ATM
transport. transport.
5.49. 3GPP TS 26.114 5.49. 3GPP TS 26.114
[R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and [R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and
interaction interaction
+----------------------+-------------------------+-------+----------+ +---------------------+--------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------------------+-------------------------+-------+----------+ +---------------------+--------------------------+-------+----------+
| 3gpp_sync_info | Usage defined for the | M | NORMAL | | 3gpp_sync_info | Usage defined for the IP | M | NORMAL |
| | IP Multimedia Subsystem | | | | | Multimedia Subsystem | | |
| | | | | | | | | |
| 3gpp_MaxRecvSDUSize | Usage defined for the | M | NORMAL | | 3gpp_MaxRecvSDUSize | Usage defined for the IP | M | NORMAL |
| | IP Multimedia Subsystem | | | | | Multimedia Subsystem | | |
| | | | | | | | | |
+----------------------+-------------------------+-------+----------+ +---------------------+--------------------------+-------+----------+
5.49 3GPP TS 26.114 Attribute Analysis 5.49 3GPP TS 26.114 Attribute Analysis
5.50. 3GPP TS 183.063 5.50. 3GPP TS 183.063
[R3GPPTS183.063] Telecommunications and Internet converged Services [R3GPPTS183.063] Telecommunications and Internet converged Services
and Protocols for Advanced Networking (TISPAN); and Protocols for Advanced Networking (TISPAN);
+---------------------+---------------+-------+--------------+ +---------------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
skipping to change at page 46, line 4 skipping to change at page 47, line 4
| bc_service_package | Not Impacted | S | NORMAL | | bc_service_package | Not Impacted | S | NORMAL |
| | | | | | | | | |
+---------------------+---------------+-------+--------------+ +---------------------+---------------+-------+--------------+
5.50 3GPP TS 183.063 Attribute Analysis 5.50 3GPP TS 183.063 Attribute Analysis
5.51. 3GPP TS 24.182 5.51. 3GPP TS 24.182
[R3GPPTS24.182] specifies IP multimedia subsystem Custom Alerting [R3GPPTS24.182] specifies IP multimedia subsystem Custom Alerting
tones tones
+-------------+---------------------------------+-------+-----------+ +------------+----------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------+---------------------------------+-------+-----------+ +------------+----------------------------------+-------+-----------+
| g.3gpp.cat | Usage defined for the IP | M | NORMAL | | g.3gpp.cat | Usage defined for the IP | M | NORMAL |
| | Multimedia Subsystem | | | | | Multimedia Subsystem | | |
| | | | | | | | | |
+-------------+---------------------------------+-------+-----------+ +------------+----------------------------------+-------+-----------+
5.51 3GPP TS 24.182 Attribute Analysis 5.51 3GPP TS 24.182 Attribute Analysis
5.52. 3GPP TS 24.183 5.52. 3GPP TS 24.183
[R3GPPTS24.183] specifies IP multimedia subsystem Custom Ringing [R3GPPTS24.183] specifies IP multimedia subsystem Custom Ringing
Signal Signal
+-------------+---------------------------------+-------+-----------+ +------------+----------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------+---------------------------------+-------+-----------+ +------------+----------------------------------+-------+-----------+
| g.3gpp.crs | Usage defined for the IP | M | NORMAL | | g.3gpp.crs | Usage defined for the IP | M | NORMAL |
| | Multimedia Subsystem | | | | | Multimedia Subsystem | | |
| | | | | | | | | |
+-------------+---------------------------------+-------+-----------+ +------------+----------------------------------+-------+-----------+
5.52 3GPP TS 24.183 Attribute Analysis 5.52 3GPP TS 24.183 Attribute Analysis
5.53. 3GPP TS 24.229 5.53. 3GPP TS 24.229
[R3GPPTS24.229] specifies IP multimedia call control protocol based [R3GPPTS24.229] specifies IP multimedia call control protocol based
on Session Initial protocol and Session Description Protocol. on Session Initial protocol and Session Description Protocol.
+------------------+---------------------------+-------+------------+ +-----------------+-----------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------------+---------------------------+-------+------------+ +-----------------+-----------------------------+-------+-----------+
| secondary-realm | secondary-realm MUST be | M | TRANSPORT | | secondary- | secondary-realm MUST be | M | TRANSPORT |
| | the one that corresponds | | | | realm | the one that corresponds to | | |
| | to the "m=" line chosen | | | | | the "m=" line chosen for | | |
| | for setting up the | | | | | setting up the underlying | | |
| | underlying transport flow | | | | | transport flow | | |
| | | | | | | | | |
| visited-realm | visited-realm MUST be the | M | TRANSPORT | | visited-realm | visited-realm MUST be the | M | TRANSPORT |
| | one that corresponds to | | | | | one that corresponds to the | | |
| | the "m=" line chosen for | | | | | "m=" line chosen for | | |
| | setting up the underlying | | | | | setting up the underlying | | |
| | transport flow | | | | | transport flow | | |
| | | | | | | | | |
| omr-m-cksum | Not Impacted | M | NORMAL | | omr-m-cksum | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-s-cksum | Not Impacted | M | NORMAL | | omr-s-cksum | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-m-att | Not Impacted | M | NORMAL | | omr-m-att | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-s-att | Not Impacted | M | NORMAL | | omr-s-att | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-m-bw | Not Impacted | M | NORMAL | | omr-m-bw | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-s-bw | Not Impacted | M | NORMAL | | omr-s-bw | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-codecs | Not Impacted | M | NORMAL | | omr-codecs | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------------+---------------------------+-------+------------+ +-----------------+-----------------------------+-------+-----------+
5.53 3GPP TS 24.229 Attribute Analysis 5.53 3GPP TS 24.229 Attribute Analysis
5.54. ITU T.38 5.54. ITU T.38
[T.38] defines procedures for real-time Group 3 facsimile [T.38] defines procedures for real-time Group 3 facsimile
communications over IP networks. communications over IP networks.
+------------------------+--------------------+-------+-------------+ +-----------------------+--------------------+-------+--------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux Category |
| | | | Category | +-----------------------+--------------------+-------+--------------+
+------------------------+--------------------+-------+-------------+ | T38FaxVersion | Refer to notes | M | TBD |
| T38FaxVersion | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38MaxBitRate | Refer to notes | M | TBD |
| T38MaxBitRate | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxFillBitRemoval | Refer to notes | M | TBD |
| T38FaxFillBitRemoval | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxTranscodingMMR | Refer to notes | M | TBD |
| T38FaxTranscodingMMR | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxTranscodingJBIG | Refer to notes | M | TBD |
| T38FaxTranscodingJBIG | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxRateManagement | Refer to notes | M | TBD |
| T38FaxRateManagement | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxMaxBuffer | Refer to notes | M | TBD |
| T38FaxMaxBuffer | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxMaxDatagram | Refer to notes | M | TBD |
| T38FaxMaxDatagram | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxUdpEC | Refer to notes | M | TBD |
| T38FaxUdpEC | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxMaxIFP | Refer to notes | M | TBD |
| T38FaxMaxIFP | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxUdpECDepth | Refer to notes | M | TBD |
| T38FaxUdpECDepth | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38FaxUdpFECMaxSpan | Refer to notes | M | TBD |
| T38FaxUdpFECMaxSpan | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38ModemType | Refer to notes | M | TBD |
| T38ModemType | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | T38VendorInfo | Refer to notes | M | TBD |
| T38VendorInfo | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | +-----------------------+--------------------+-------+--------------+
+------------------------+--------------------+-------+-------------+
5.54 ITU T.38 Attribute Analysis 5.54 ITU T.38 Attribute Analysis
NOTE: As per section 9 of [I-D.ietf-mmusic-sdp-bundle-negotiation], NOTE: As per section 9 of [I-D.ietf-mmusic-sdp-bundle-negotiation],
there exists no publicly available specification that defines there exists no publicly available specification that defines
procedures for multiplexing/demultiplexing fax protocols flows over a procedures for multiplexing/demultiplexing fax protocols flows over a
single 5-tuple. Once such a specification is available, the single 5-tuple. Once such a specification is available, the
multiplexing category assignments for the attributes in this section multiplexing category assignments for the attributes in this section
could be revisited. could be revisited.
5.55. ITU-T Q.1970 5.55. ITU-T Q.1970
[Q.1970] defines Bearer Independent Call Control (BICC) IP bearer [Q.1970] defines Bearer Independent Call Control (BICC) IP bearer
control protocol. control protocol.
+--------+---------------------------------------+-------+----------+ +-------+----------------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------+---------------------------------------+-------+----------+ +-------+----------------------------------------+-------+----------+
| ipbcp | ipbcp version identifies type of IP | S | SPECIAL | | ipbcp | ipbcp version identifies type of IP | S | SPECIAL |
| | bearer control protocol (IPBCP) | | | | | bearer control protocol (IPBCP) | | |
| | message used in BICC (ITU-T Q.1901) | | | | | message used in BICC (ITU-T Q.1901) | | |
| | environment which are limited to | | | | | environment which are limited to | | |
| | single media payload. Refer to the | | | | | single media payload. Refer to the | | |
| | pertinent ITU-T specifications while | | | | | pertinent ITU-T specifications while | | |
| | multiplexing | | | | | multiplexing | | |
| | | | | | | | | |
+--------+---------------------------------------+-------+----------+ +-------+----------------------------------------+-------+----------+
5.55 ITU-T Q.1970 Attribute Analysis 5.55 ITU-T Q.1970 Attribute Analysis
5.56. ITU-T H.248.15 5.56. ITU-T H.248.15
ITU-T H.248.15 [H.248.15] defines Gateway Control Protocol SDP H.248 ITU-T H.248.15 [H.248.15] defines Gateway Control Protocol SDP H.248
package attribute package attribute
+-----------+------------------------------------+-------+----------+ +----------+-------------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------+------------------------------------+-------+----------+ +----------+-------------------------------------+-------+----------+
| h248item | It is only applicable for | B | SPECIAL | | h248item | It is only applicable for signaling | B | SPECIAL |
| | signaling the inclusion of H.248 | | | | | the inclusion of H.248 extension | | |
| | extension packages to a gateway | | | | | packages to a gateway via the local | | |
| | via the local and remote | | | | | and remote descriptors. The | | |
| | descriptors. The attribute itself | | | | | attribute itself is unaffected by | | |
| | is unaffected by multiplexing, but | | | | | multiplexing, but the packaged | | |
| | the packaged referenced in a | | | | | referenced in a specific use of the | | |
| | specific use of the attribute can | | | | | attribute can be impacted. Further | | |
| | be impacted. Further analysis of | | | | | analysis of each package is needed | | |
| | each package is needed to | | | | | to determine if there is an issue. | | |
| | determine if there is an issue. | | | | | This is only a concern in | | |
| | This is only a concern in | | | | | environments using a decomposed | | |
| | environments using a decomposed | | | | | server/gateway with H.248 signaled | | |
| | server/gateway with H.248 signaled | | | | | between them. The ITU-T will need | | |
| | between them. The ITU-T will need | | | | | to do further analysis of various | | |
| | to do further analysis of various | | | | | packages when they specify how to | | |
| | packages when they specify how to | | | | | signal the use of multiplexing to a | | |
| | signal the use of multiplexing to | | | | | gateway | | |
| | a gateway | | | | | | | |
| | | | | +----------+-------------------------------------+-------+----------+
+-----------+------------------------------------+-------+----------+
5.56 ITU-T H.248.15 Attribute Analysis 5.56 ITU-T H.248.15 Attribute Analysis
5.57. RFC4975: The Message Session Relay Protocol 5.57. RFC4975: The Message Session Relay Protocol
[RFC4975] the Message Session Relay Protocol, a protocol for [RFC4975] the Message Session Relay Protocol, a protocol for
transmitting a series of related instant messages in the context of a transmitting a series of related instant messages in the context of a
session. Message sessions are treated like any other media stream session. Message sessions are treated like any other media stream
when set up via a rendezvous or session creation protocol such as the when set up via a rendezvous or session creation protocol such as the
Session Initiation Protocol. Session Initiation Protocol.
+-----------------------+---------------------+-------+-------------+ +----------------------+---------------------+-------+--------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux Category |
| | | | Category | +----------------------+---------------------+-------+--------------+
+-----------------------+---------------------+-------+-------------+ | accept-types | Refer to notes | M | TBD |
| accept-types | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | accept-wrapped- | Refer to notes | M | TBD |
| accept-wrapped-types | Refer to notes | M | TBD | | types | below | | |
| | below | | | | | | | |
| | | | | | max-size | Refer to notes | M | TBD |
| max-size | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | | path | Refer to notes | M | TBD |
| path | Refer to notes | M | TBD | | | below | | |
| | below | | | | | | | |
| | | | | +----------------------+---------------------+-------+--------------+
+-----------------------+---------------------+-------+-------------+
5.57 RFC4975 Attribute Analysis 5.57 RFC4975 Attribute Analysis
NOTE: As per section 9 of [I-D.ietf-mmusic-sdp-bundle-negotiation], NOTE: As per section 9 of [I-D.ietf-mmusic-sdp-bundle-negotiation],
there exists no publicly available specification that defines there exists no publicly available specification that defines
procedures for multiplexing/demultiplexing MRSP flows over a single procedures for multiplexing/demultiplexing MRSP flows over a single
5-tuple. Once such a specification is available, the multiplexing 5-tuple. Once such a specification is available, the multiplexing
categories assignments for the attributes in this section could be categories assignments for the attributes in this section could be
revisited. revisited.
skipping to change at page 52, line 11 skipping to change at page 53, line 11
This section specifies handling of specific bandwidth attributes when This section specifies handling of specific bandwidth attributes when
used in multiplexing scenarios. used in multiplexing scenarios.
6.1. RFC4566: SDP 6.1. RFC4566: SDP
[RFC4566] defines SDP that is intended for describing multimedia [RFC4566] defines SDP that is intended for describing multimedia
sessions for the purposes of session announcement, session sessions for the purposes of session announcement, session
invitation, and other forms of multimedia session initiation. invitation, and other forms of multimedia session initiation.
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| bwtype:CT | Not Impacted | S | NORMAL | | bwtype:CT | Not Impacted | S | NORMAL |
| | | | | | | | | |
| bwtype:AS | For the media level usage, the | B | SUM | | bwtype:AS | For the media level usage, the | B | SUM |
| | aggregate of individual bandwidth | | | | | aggregate of individual bandwidth | | |
| | values is considered | | | | | values is considered | | |
| | | | | | | | | |
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
6.1 RFC4566 bwtype Analysis 6.1 RFC4566 bwtype Analysis
6.2. RFC3556: SDP Bandwidth Modifiers for RTCP Bandwidth 6.2. RFC3556: SDP Bandwidth Modifiers for RTCP Bandwidth
[RFC3556] defines an extension to SDP to specify two additional [RFC3556] defines an extension to SDP to specify two additional
modifiers for the bandwidth attribute. These modifiers may be used modifiers for the bandwidth attribute. These modifiers may be used
to specify the bandwidth allowed for RTCP packets in a RTP session. to specify the bandwidth allowed for RTCP packets in a RTP session.
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| bwtype:RS | Session level usage represents | B | SUM | | bwtype:RS | Session level usage represents | B | SUM |
| | session aggregate and media level | | | | | session aggregate and media level | | |
| | usage indicates SUM of the | | | | | usage indicates SUM of the | | |
| | individual values while | | | | | individual values while | | |
| | multiplexing | | | | | multiplexing | | |
| | | | | | | | | |
| bwtype:RR | Session level usage represents | B | SUM | | bwtype:RR | Session level usage represents | B | SUM |
| | session aggregate and media level | | | | | session aggregate and media level | | |
| | usage indicates SUM of the | | | | | usage indicates SUM of the | | |
| | individual values while | | | | | individual values while | | |
| | multiplexing | | | | | multiplexing | | |
| | | | | | | | | |
+------------+-----------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
6.2 RFC3556 bwtype Analysis 6.2 RFC3556 bwtype Analysis
6.3. RFC3890: Bandwidth Modifier for SDP 6.3. RFC3890: Bandwidth Modifier for SDP
[RFC3890] defines SDP Transport Independent Application Specific [RFC3890] defines SDP Transport Independent Application Specific
Maximum (TIAS) bandwidth modifier that does not include transport Maximum (TIAS) bandwidth modifier that does not include transport
overhead; instead an additional packet rate attribute is defined. overhead; instead an additional packet rate attribute is defined.
The transport independent bit-rate value together with the maximum The transport independent bit-rate value together with the maximum
packet rate can then be used to calculate the real bit-rate over the packet rate can then be used to calculate the real bit-rate over the
transport actually used. transport actually used.
+--------------+---------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------------+---------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
| bwtype:TIAS | The usage of TIAS is not | B | SPECIAL | | bwtype:TIAS | The usage of TIAS is not defined | B | SPECIAL |
| | defined under Offer/Answer | | | | | under Offer/Answer usage. | | |
| | usage. | | | | | | | |
| | | | | | maxprate | The usage of TIAS and maxprate | B | SPECIAL |
| maxprate | The usage of TIAS and maxprate | B | SPECIAL | | | is not well defined under | | |
| | is not well defined under | | | | | multiplexing | | |
| | multiplexing | | | | | | | |
| | | | | +-------------+----------------------------------+-------+----------+
+--------------+---------------------------------+-------+----------+
6.3 RFC3890 bwtype Analysis 6.3 RFC3890 bwtype Analysis
NOTE: The intention of TIAS is that the media level bit-rate is NOTE: The intention of TIAS is that the media level bit-rate is
multiplied with the known per-packet overhead for the selected multiplied with the known per-packet overhead for the selected
transport and the maxprate value to determine the worst case bit-rate transport and the maxprate value to determine the worst case bit-rate
from the transport to more accurately capture the required usage. from the transport to more accurately capture the required usage.
Summing TIAS values independently across "m=" lines and multiplying Summing TIAS values independently across "m=" lines and multiplying
the computed sum with maxprate and the per-packet overhead would the computed sum with maxprate and the per-packet overhead would
inflate the value significantly. Instead performing multiplication inflate the value significantly. Instead performing multiplication
skipping to change at page 54, line 5 skipping to change at page 55, line 5
This section analyzes rtcp-fb SDP attributes. This section analyzes rtcp-fb SDP attributes.
7.1. RFC4585: RTP/AVPF 7.1. RFC4585: RTP/AVPF
[RFC4585] defines an extension to the Audio-visual Profile (AVP) that [RFC4585] defines an extension to the Audio-visual Profile (AVP) that
enables receivers to provide, statistically, more immediate feedback enables receivers to provide, statistically, more immediate feedback
to the senders and thus allows for short-term adaptation and to the senders and thus allows for short-term adaptation and
efficient feedback-based repair mechanisms to be implemented. efficient feedback-based repair mechanisms to be implemented.
+----------+----------------------------+-------+-------------------+ +---------+------------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+----------+----------------------------+-------+-------------------+ +---------+------------------------------+-------+------------------+
| ack rpsi | The attribute value MUST | M | IDENTICAL-PER-PT | | ack | The attribute value MUST be | M | IDENTICAL-PER- |
| | be same for a given codec | | | | rpsi | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ack app | Feedback parameters MUST | M | SPECIAL | | ack | Feedback parameters MUST be | M | SPECIAL |
| | be handled in the app | | | | app | handled in the app specific | | |
| | specific way when | | | | | way when multiplexed | | |
| | multiplexed | | | | | | | |
| | | | | | nack | The attribute value MUST be | M | IDENTICAL-PER- |
| nack | The attribute value MUST | M | IDENTICAL-PER-PT | | | same for a given codec | | PT |
| | be same for a given codec | | | | | configuration | | |
| | configuration | | | | | | | |
| | | | | | nack | The attribute value MUST be | M | IDENTICAL-PER- |
| nack pli | The attribute value MUST | M | IDENTICAL-PER-PT | | pli | same for a given codec | | PT |
| | be same for a given codec | | | | | configuration | | |
| | configuration | | | | | | | |
| | | | | | nack | The attribute value MUST be | M | IDENTICAL-PER- |
| nack sli | The attribute value MUST | M | IDENTICAL-PER-PT | | sli | same for a given codec | | PT |
| | be same for a given codec | | | | | configuration | | |
| | configuration | | | | | | | |
| | | | | | nack | The attribute value MUST be | M | IDENTICAL-PER- |
| nack | The attribute value MUST | M | IDENTICAL-PER-PT | | rpsi | same for a given codec | | PT |
| rpsi | be same for a given codec | | | | | configuration | | |
| | configuration | | | | | | | |
| | | | | | nack | Feedback parameters MUST be | M | SPECIAL |
| nack app | Feedback parameters MUST | M | SPECIAL | | app | handled in the app specific | | |
| | be handled in the app | | | | | way when multiplexed | | |
| | specific way when | | | | | | | |
| | multiplexed | | | | trr- | The attribute value MUST be | M | IDENTICAL-PER- |
| | | | | | int | same for a given codec | | PT |
| trr-int | The attribute value MUST | M | IDENTICAL-PER-PT | | | configuration | | |
| | be same for a given codec | | | | | | | |
| | configuration | | | +---------+------------------------------+-------+------------------+
| | | | |
+----------+----------------------------+-------+-------------------+
7.1 RFC4585 Attribute Analysis 7.1 RFC4585 Attribute Analysis
7.2. RFC5104: Codec Control Messages in AVPF 7.2. RFC5104: Codec Control Messages in AVPF
[RFC5104] specifies a few extensions to the messages defined in the [RFC5104] specifies a few extensions to the messages defined in the
Audio-Visual Profile with Feedback (AVPF). They are helpful Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls. in smaller multicast environments and point-to-point calls.
+------+--------------------------------+-------+-------------------+ +------+---------------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------+--------------------------------+-------+-------------------+ +------+---------------------------------+-------+------------------+
| ccm | The attribute value MUST be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER- |
| | same for a given codec | | | | | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+------+--------------------------------+-------+-------------------+ +------+---------------------------------+-------+------------------+
7.2 RFC5104 Attribute Analysis 7.2 RFC5104 Attribute Analysis
7.3. RFC6285: Unicast-Based Rapid Acquisition of Multicast RTP Sessions 7.3. RFC6285: Unicast-Based Rapid Acquisition of Multicast RTP Sessions
(RAMS) (RAMS)
[RFC6285] describes a method using the existing RTP and RTCP [RFC6285] describes a method using the existing RTP and RTCP
machinery that reduces the acquisition delay. In this method, an machinery that reduces the acquisition delay. In this method, an
auxiliary unicast RTP session carrying the Reference Information to auxiliary unicast RTP session carrying the Reference Information to
the receiver precedes or accompanies the multicast stream. This the receiver precedes or accompanies the multicast stream. This
unicast RTP flow can be transmitted at a faster than natural bitrate unicast RTP flow can be transmitted at a faster than natural bitrate
to further accelerate the acquisition. The motivating use case for to further accelerate the acquisition. The motivating use case for
this capability is multicast applications that carry real-time this capability is multicast applications that carry real-time
compressed audio and video. compressed audio and video.
+-------+-------------------------------+-------+-------------------+ +--------+-------------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-------+-------------------------------+-------+-------------------+ +--------+-------------------------------+-------+------------------+
| nack | The attribute value MUST be | M | IDENTICAL-PER-PT | | nack | The attribute value MUST be | M | IDENTICAL-PER- |
| rai | same for a given codec | | | | rai | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+-------+-------------------------------+-------+-------------------+ +--------+-------------------------------+-------+------------------+
7.3 RFC6285 Attribute Analysis 7.3 RFC6285 Attribute Analysis
7.4. RFC6679: ECN for RTP over UDP/IP 7.4. RFC6679: ECN for RTP over UDP/IP
[RFC6679] specifies how Explicit Congestion Notification (ECN) can be [RFC6679] specifies how Explicit Congestion Notification (ECN) can be
used with the RTP running over UDP, using the RTCP as a feedback used with the RTP running over UDP, using the RTCP as a feedback
mechanism. It defines a new RTCP Extended Report (XR) block for mechanism. It defines a new RTCP Extended Report (XR) block for
periodic ECN feedback, a new RTCP transport feedback message for periodic ECN feedback, a new RTCP transport feedback message for
timely reporting of congestion events, and a STUN extension used in timely reporting of congestion events, and a STUN extension used in
the optional initialization method using ICE. the optional initialization method using ICE.
+------------------+---------------------------+-------+------------+ +-----------------+-----------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------------+---------------------------+-------+------------+ +-----------------+-----------------------------+-------+-----------+
| ecn-capable-rtp | ECN markup are enabled at | M | IDENTICAL | | ecn-capable- | ECN markup are enabled at | M | IDENTICAL |
| | the RTP session level | | | | rtp | the RTP session level | | |
| | | | | | | | | |
| nack ecn | This attribute enables | M | IDENTICAL | | nack ecn | This attribute enables ECN | M | IDENTICAL |
| | ECN at the RTP session | | | | | at the RTP session level | | |
| | level | | | | | | | |
| | | | | +-----------------+-----------------------------+-------+-----------+
+------------------+---------------------------+-------+------------+
7.4 RFC6679 Attribute Analysis 7.4 RFC6679 Attribute Analysis
7.5. RFC6642: Third-Party Loss Report 7.5. RFC6642: Third-Party Loss Report
In a large RTP session using the RTCP feedback mechanism defined in In a large RTP session using the RTCP feedback mechanism defined in
[RFC4585], a feedback target may experience transient overload if [RFC4585], a feedback target may experience transient overload if
some event causes a large number of receivers to send feedback at some event causes a large number of receivers to send feedback at
once. This overload is usually avoided by ensuring that feedback once. This overload is usually avoided by ensuring that feedback
reports are forwarded to all receivers, allowing them to avoid reports are forwarded to all receivers, allowing them to avoid
sending duplicate feedback reports. However, there are cases where sending duplicate feedback reports. However, there are cases where
it is not recommended to forward feedback reports, and this may allow it is not recommended to forward feedback reports, and this may allow
feedback implosion. [RFC6642] memo discusses these cases and defines feedback implosion. [RFC6642] memo discusses these cases and defines
a new RTCP Third-Party Loss Report that can be used to inform a new RTCP Third-Party Loss Report that can be used to inform
receivers that the feedback target is aware of some loss event, receivers that the feedback target is aware of some loss event,
allowing them to suppress feedback. Associated SDP signaling is also allowing them to suppress feedback. Associated SDP signaling is also
defined. defined.
+--------+------------------------------+-------+-------------------+ +---------+------------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+--------+------------------------------+-------+-------------------+ +---------+------------------------------+-------+------------------+
| nack | The attribute value MUST be | M | IDENTICAL-PER-PT | | nack | The attribute value MUST be | M | IDENTICAL-PER- |
| tllei | same for a given codec | | | | tllei | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack | The attribute value MUST be | M | IDENTICAL-PER-PT | | nack | The attribute value MUST be | M | IDENTICAL-PER- |
| pslei | same for a given codec | | | | pslei | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +---------+------------------------------+-------+------------------+
7.5 RFC6642 Attribute Analysis 7.5 RFC6642 Attribute Analysis
7.6. RFC5104: Codec Control Messages in AVPF 7.6. RFC5104: Codec Control Messages in AVPF
[RFC5104] specifies a few extensions to the messages defined in the [RFC5104] specifies a few extensions to the messages defined in the
Audio-Visual Profile with Feedback (AVPF). They are helpful Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls. in smaller multicast environments and point-to-point calls.
+--------+------------------------------+-------+-------------------+ +--------+-------------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+--------+------------------------------+-------+-------------------+ +--------+-------------------------------+-------+------------------+
| ccm | The attribute value MUST be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER- |
| fir | same for a given codec | | | | fir | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ccm | The attribute value MUST be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER- |
| tmmbr | same for a given codec | | | | tmmbr | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ccm | The attribute value MUST be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER- |
| tstr | same for a given codec | | | | tstr | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ccm | The attribute value MUST be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER- |
| vbcm | same for a given codec | | | | vbcm | same for a given codec | | PT |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+-------------------------------+-------+------------------+
7.6 RFC5104 Attribute Analysis 7.6 RFC5104 Attribute Analysis
8. group Attribute Analysis 8. group Attribute Analysis
This section analyzes SDP "group" attribute semantics [RFC5888]. This section analyzes SDP "group" attribute semantics [RFC5888].
8.1. RFC5888: SDP Grouping Framework 8.1. RFC5888: SDP Grouping Framework
[RFC5888] defines a framework to group "m" lines in SDP for different [RFC5888] defines a framework to group "m" lines in SDP for different
skipping to change at page 59, line 27 skipping to change at page 60, line 27
8.4 RFC5956 Attribute Analysis 8.4 RFC5956 Attribute Analysis
8.5. RFC5583: Signaling Media Decoding Dependency in SDP 8.5. RFC5583: Signaling Media Decoding Dependency in SDP
[RFC5583] defines semantics that allow for signaling the decoding [RFC5583] defines semantics that allow for signaling the decoding
dependency of different media descriptions with the same media type dependency of different media descriptions with the same media type
in SDP. This is required, for example, if media data is separated in SDP. This is required, for example, if media data is separated
and transported in different network streams as a result of the use and transported in different network streams as a result of the use
of a layered or multiple descriptive media coding process. of a layered or multiple descriptive media coding process.
+------------+--------------------------+-------+-------------------+ +-----------+----------------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+--------------------------+-------+-------------------+ +-----------+----------------------------+-------+------------------+
| group:DDP | Not Impacted | S | NORMAL | | group:DDP | Not Impacted | S | NORMAL |
| | | | | | | | | |
| depend lay | The attribute value MUST | M | IDENTICAL-PER-PT | | depend | The attribute value MUST | M | IDENTICAL-PER- |
| | be same for a given | | | | lay | be same for a given codec | | PT |
| | codec configuration | | | | | configuration | | |
| | | | | | | | | |
| depend mdc | The attribute value MUST | M | IDENTICAL-PER-PT | | depend | The attribute value MUST | M | IDENTICAL-PER- |
| | be same for a given | | | | mdc | be same for a given codec | | PT |
| | codec configuration | | | | | configuration | | |
| | | | | | | | | |
+------------+--------------------------+-------+-------------------+ +-----------+----------------------------+-------+------------------+
8.5 RFC5583 Attribute Analysis 8.5 RFC5583 Attribute Analysis
8.6. RFC7104: Duplication Grouping Semantics in the SDP 8.6. RFC7104: Duplication Grouping Semantics in the SDP
[RFC7104] defines the semantics for grouping redundant streams in [RFC7104] defines the semantics for grouping redundant streams in
SDP, The semantics defined in this document are to be used with the SDP, The semantics defined in this document are to be used with the
SDP Grouping Framework. Grouping semantics at the SSRC)level are SDP Grouping Framework. Grouping semantics at the SSRC)level are
also defined in this document for RTP streams using SSRC also defined in this document for RTP streams using SSRC
multiplexing. multiplexing.
skipping to change at page 61, line 23 skipping to change at page 62, line 23
10. QoS Mechanism Token Analysis 10. QoS Mechanism Token Analysis
This section analyzes QoS tokes specified with SDP. This section analyzes QoS tokes specified with SDP.
10.1. RFC5432: QoS Mechanism Selection in SDP 10.1. RFC5432: QoS Mechanism Selection in SDP
[RFC5432] defines procedures to negotiate QOS mechanisms using the [RFC5432] defines procedures to negotiate QOS mechanisms using the
SDP offer/answer model. SDP offer/answer model.
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
| rsvp | rsvp attribute MUST be the one that | B | TRANSPORT | | rsvp | rsvp attribute MUST be the one that | B | TRANSPORT |
| | corresponds to the "m=" line chosen | | | | | corresponds to the "m=" line chosen | | |
| | for setting up the underlying | | | | | for setting up the underlying | | |
| | transport flow | | | | | transport flow | | |
| | | | | | | | | |
| nsis | rsvp attribute MUST be the one that | B | TRANSPORT | | nsis | rsvp attribute MUST be the one that | B | TRANSPORT |
| | corresponds to the "m=" line chosen | | | | | corresponds to the "m=" line chosen | | |
| | for setting up the underlying | | | | | for setting up the underlying | | |
| | transport | | | | | transport | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +------+----------------------------------------+-------+-----------+
10.1 RFC5432 Attribute Analysis 10.1 RFC5432 Attribute Analysis
NOTE: A single Differentiated Services Code Point (DSCP) code point NOTE: A single Differentiated Services Code Point (DSCP) code point
per flow being multiplexed doesn't impact multiplexing since QOS per flow being multiplexed doesn't impact multiplexing since QOS
mechanisms are signaled/scoped per flow. For scenarios that involve mechanisms are signaled/scoped per flow. For scenarios that involve
having different DSCP code points for packets being transmitted over having different DSCP code points for packets being transmitted over
the same 5-tuple, issues as discussed in [RFC7657] need to be taken the same 5-tuple, issues as discussed in [RFC7657] need to be taken
into consideration. into consideration.
skipping to change at page 63, line 18 skipping to change at page 64, line 18
[RFC5109] describes a payload format for generic Forward Error [RFC5109] describes a payload format for generic Forward Error
Correction (FEC) for media data encapsulated in RTP. It is based on Correction (FEC) for media data encapsulated in RTP. It is based on
the exclusive-or (parity) operation. The payload format allows end the exclusive-or (parity) operation. The payload format allows end
systems to apply protection using various protection lengths and systems to apply protection using various protection lengths and
levels, in addition to using various protection group sizes to adapt levels, in addition to using various protection group sizes to adapt
to different media and channel characteristics. It enables complete to different media and channel characteristics. It enables complete
recovery of the protected packets or partial recovery of the critical recovery of the protected packets or partial recovery of the critical
parts of the payload depending on the packet loss situation. parts of the payload depending on the packet loss situation.
+---------------------+--------------------------+-------+----------+ +--------------------+---------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------------------+--------------------------+-------+----------+ +--------------------+---------------------------+-------+----------+
| audio/ulpfec | Not recommended for | M | CAUTION | | audio/ulpfec | Not recommended for | M | CAUTION |
| | multiplexing due to | | | | | multiplexing due to reuse | | |
| | reuse of SSRCs | | | | | of SSRCs | | |
| | | | | | | | | |
| video/ulpfec | Not recommended for | M | CAUTION | | video/ulpfec | Not recommended for | M | CAUTION |
| | multiplexing due to | | | | | multiplexing due to reuse | | |
| | reuse of SSRCs | | | | | of SSRCs | | |
| | | | | | | | | |
| text/ulpfec | Not recommended for | M | CAUTION | | text/ulpfec | Not recommended for | M | CAUTION |
| | multiplexing due to | | | | | multiplexing due to reuse | | |
| | reuse of SSRCs | | | | | of SSRCs | | |
| | | | | | | | | |
| application/ulpfec | Not recommended for | M | CAUTION | | application/ulpfec | Not recommended for | M | CAUTION |
| | multiplexing due to | | | | | multiplexing due to reuse | | |
| | reuse of SSRCs | | | | | of SSRCs | | |
| | | | | | | | | |
+---------------------+--------------------------+-------+----------+ +--------------------+---------------------------+-------+----------+
13.1 RFC5109 Payload Format Analysis 13.1 RFC5109 Payload Format Analysis
14. Multiplexing Considerations for Encapsulating Attributes 14. Multiplexing Considerations for Encapsulating Attributes
This sections deals with recommendations for defining the This sections deals with recommendations for defining the
multiplexing characteristics of the SDP attributes that encapsulate multiplexing characteristics of the SDP attributes that encapsulate
other SDP attributes/parameters. Such attributes as of today, for other SDP attributes/parameters. Such attributes as of today, for
example, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of example, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of
a generic framework for indicating and negotiating transport, media, a generic framework for indicating and negotiating transport, media,
skipping to change at page 83, line 50 skipping to change at page 84, line 50
review. review.
Thanks to Ben Campbell for AD review suggestions. Thanks to Spencer Thanks to Ben Campbell for AD review suggestions. Thanks to Spencer
Dawkins, Stephen Farrel, Alissa Cooper, Mirja Kuehlewind and the Dawkins, Stephen Farrel, Alissa Cooper, Mirja Kuehlewind and the
entire IESG experts for their reviews. entire IESG experts for their reviews.
18. Change Log 18. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing] [RFC EDITOR NOTE: Please remove this section when publishing]
Changes draft-ietf-mmusic-sdp-mux-attributes-16
o Added a clarification note on when to encode IDENTICAL attributes
as suggested by Christer.
Changes draft-ietf-mmusic-sdp-mux-attributes-15 Changes draft-ietf-mmusic-sdp-mux-attributes-15
o Updated Mux category for floorctrl to TBD o Updated Mux category for floorctrl to TBD
Changes draft-ietf-mmusic-sdp-mux-attributes-14 Changes draft-ietf-mmusic-sdp-mux-attributes-14
o Incorporated Comments from IESG review : o Incorporated Comments from IESG review :
* Updated security considerations section to fix the * Updated security considerations section to fix the
incositencies (Spencer's review) incositencies (Spencer's review)
* Updated section 5.36 to align the text with 5.39 (Stephen's * Updated section 5.36 to align the text with 5.39 (Stephen's
review) review)
skipping to change at page 87, line 22 skipping to change at page 88, line 28
o Added new section for dealing with FEC payload types. o Added new section for dealing with FEC payload types.
19. References 19. References
19.1. Normative References 19.1. Normative References
[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-24 (work in progress), January 2016. negotiation-48 (work in progress), January 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[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, <https://www.rfc-editor.org/info/rfc4566>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5226>. editor.org/info/rfc5226>.
19.2. Informative References 19.2. Informative References
[H.248.15] [H.248.15]
"Gateway control protocol: SDP H.248 package attribute", "Gateway control protocol: SDP H.248 package attribute",
<http://www.itu.int/rec/T-REC-H.248.15>. <http://www.itu.int/rec/T-REC-H.248.15>.
[I-D.ietf-mmusic-rfc4566bis] [I-D.ietf-mmusic-rfc4566bis]
Handley, M., Jacobson, V., Perkins, C., and A. Begen, Begen, A., Kyzivat, P., Perkins, C., and M. Handley, "SDP:
"SDP: Session Description Protocol", draft-ietf-mmusic- Session Description Protocol", draft-ietf-mmusic-
rfc4566bis-17 (work in progress), June 2016. rfc4566bis-25 (work in progress), February 2018.
[IANA] "Session Description Protocol (SDP) Parameters", [IANA] "Session Description Protocol (SDP) Parameters",
<http://www.iana.org/assignments/sdp-parameters/ <http://www.iana.org/assignments/sdp-parameters/
sdp-parameters.xml>. sdp-parameters.xml>.
[Q.1970] "Q.1970 : BICC IP bearer control protocol", [Q.1970] "Q.1970 : BICC IP bearer control protocol",
<https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>. <https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>.
[R3GPPTS183.063] [R3GPPTS183.063]
"TISPAN - IMS based ITPV Stage 3 specification.", "TISPAN - IMS based ITPV Stage 3 specification.",
skipping to change at page 88, line 35 skipping to change at page 89, line 39
"IP multimedia call control protocol based on Session "IP multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol Initiation Protocol (SIP) and Session Description Protocol
(SDP);", (SDP);",
<http://www.3gpp.org/ftp/Specs/html-info/24229.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24229.htm>.
[R3GPPTS26.114] [R3GPPTS26.114]
"IP multimedia Subsystem : Media Handling and "IP multimedia Subsystem : Media Handling and
interaction", <http://www.3gpp.org/DynaReport/26114.htm>. interaction", <http://www.3gpp.org/DynaReport/26114.htm>.
[RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time [RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time
Streaming Protocol (RTSP)", RFC 2326, DOI 10.17487/ Streaming Protocol (RTSP)", RFC 2326,
RFC2326, April 1998, DOI 10.17487/RFC2326, April 1998, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc2326>. editor.org/info/rfc2326>.
[RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the [RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the
Session Description Protocol (SDP) for ATM Bearer Session Description Protocol (SDP) for ATM Bearer
Connections", RFC 3108, DOI 10.17487/RFC3108, May 2001, Connections", RFC 3108, DOI 10.17487/RFC3108, May 2001,
<http://www.rfc-editor.org/info/rfc3108>. <https://www.rfc-editor.org/info/rfc3108>.
[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, DOI with Session Description Protocol (SDP)", RFC 3264,
10.17487/RFC3264, June 2002, DOI 10.17487/RFC3264, June 2002, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3264>. editor.org/info/rfc3264>.
[RFC3312] Camarillo, G., Ed., Marshall, W., Ed., and J. Rosenberg, [RFC3312] Camarillo, G., Ed., Marshall, W., Ed., and J. Rosenberg,
"Integration of Resource Management and Session Initiation "Integration of Resource Management and Session Initiation
Protocol (SIP)", RFC 3312, DOI 10.17487/RFC3312, October Protocol (SIP)", RFC 3312, DOI 10.17487/RFC3312, October
2002, <http://www.rfc-editor.org/info/rfc3312>. 2002, <https://www.rfc-editor.org/info/rfc3312>.
[RFC3407] Andreasen, F., "Session Description Protocol (SDP) Simple [RFC3407] Andreasen, F., "Session Description Protocol (SDP) Simple
Capability Declaration", RFC 3407, DOI 10.17487/RFC3407, Capability Declaration", RFC 3407, DOI 10.17487/RFC3407,
October 2002, <http://www.rfc-editor.org/info/rfc3407>. October 2002, <https://www.rfc-editor.org/info/rfc3407>.
[RFC3524] Camarillo, G. and A. Monrad, "Mapping of Media Streams to [RFC3524] Camarillo, G. and A. Monrad, "Mapping of Media Streams to
Resource Reservation Flows", RFC 3524, DOI 10.17487/ Resource Reservation Flows", RFC 3524,
RFC3524, April 2003, DOI 10.17487/RFC3524, April 2003, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3524>. editor.org/info/rfc3524>.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
July 2003, <http://www.rfc-editor.org/info/rfc3550>. July 2003, <https://www.rfc-editor.org/info/rfc3550>.
[RFC3556] Casner, S., "Session Description Protocol (SDP) Bandwidth [RFC3556] Casner, S., "Session Description Protocol (SDP) Bandwidth
Modifiers for RTP Control Protocol (RTCP) Bandwidth", RFC Modifiers for RTP Control Protocol (RTCP) Bandwidth",
3556, DOI 10.17487/RFC3556, July 2003, RFC 3556, DOI 10.17487/RFC3556, July 2003,
<http://www.rfc-editor.org/info/rfc3556>. <https://www.rfc-editor.org/info/rfc3556>.
[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, DOI in Session Description Protocol (SDP)", RFC 3605,
10.17487/RFC3605, October 2003, DOI 10.17487/RFC3605, October 2003, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3605>. editor.org/info/rfc3605>.
[RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed., [RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,
"RTP Control Protocol Extended Reports (RTCP XR)", RFC "RTP Control Protocol Extended Reports (RTCP XR)",
3611, DOI 10.17487/RFC3611, November 2003, RFC 3611, DOI 10.17487/RFC3611, November 2003,
<http://www.rfc-editor.org/info/rfc3611>. <https://www.rfc-editor.org/info/rfc3611>.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)", Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, DOI 10.17487/RFC3711, March 2004, RFC 3711, DOI 10.17487/RFC3711, March 2004,
<http://www.rfc-editor.org/info/rfc3711>. <https://www.rfc-editor.org/info/rfc3711>.
[RFC3890] Westerlund, M., "A Transport Independent Bandwidth [RFC3890] Westerlund, M., "A Transport Independent Bandwidth
Modifier for the Session Description Protocol (SDP)", RFC Modifier for the Session Description Protocol (SDP)",
3890, DOI 10.17487/RFC3890, September 2004, RFC 3890, DOI 10.17487/RFC3890, September 2004,
<http://www.rfc-editor.org/info/rfc3890>. <https://www.rfc-editor.org/info/rfc3890>.
[RFC4091] Camarillo, G. and J. Rosenberg, "The Alternative Network [RFC4091] Camarillo, G. and J. Rosenberg, "The Alternative Network
Address Types (ANAT) Semantics for the Session Description Address Types (ANAT) Semantics for the Session Description
Protocol (SDP) Grouping Framework", RFC 4091, DOI Protocol (SDP) Grouping Framework", RFC 4091,
10.17487/RFC4091, June 2005, DOI 10.17487/RFC4091, June 2005, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4091>. editor.org/info/rfc4091>.
[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in [RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
the Session Description Protocol (SDP)", RFC 4145, DOI the Session Description Protocol (SDP)", RFC 4145,
10.17487/RFC4145, September 2005, DOI 10.17487/RFC4145, September 2005, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4145>. editor.org/info/rfc4145>.
[RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E. [RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E.
Carrara, "Key Management Extensions for Session Carrara, "Key Management Extensions for Session
Description Protocol (SDP) and Real Time Streaming Description Protocol (SDP) and Real Time Streaming
Protocol (RTSP)", RFC 4567, DOI 10.17487/RFC4567, July Protocol (RTSP)", RFC 4567, DOI 10.17487/RFC4567, July
2006, <http://www.rfc-editor.org/info/rfc4567>. 2006, <https://www.rfc-editor.org/info/rfc4567>.
[RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session
Description Protocol (SDP) Security Descriptions for Media Description Protocol (SDP) Security Descriptions for Media
Streams", RFC 4568, DOI 10.17487/RFC4568, July 2006, Streams", RFC 4568, DOI 10.17487/RFC4568, July 2006,
<http://www.rfc-editor.org/info/rfc4568>. <https://www.rfc-editor.org/info/rfc4568>.
[RFC4570] Quinn, B. and R. Finlayson, "Session Description Protocol [RFC4570] Quinn, B. and R. Finlayson, "Session Description Protocol
(SDP) Source Filters", RFC 4570, DOI 10.17487/RFC4570, (SDP) Source Filters", RFC 4570, DOI 10.17487/RFC4570,
July 2006, <http://www.rfc-editor.org/info/rfc4570>. July 2006, <https://www.rfc-editor.org/info/rfc4570>.
[RFC4572] Lennox, J., "Connection-Oriented Media Transport over the [RFC4572] Lennox, J., "Connection-Oriented Media Transport over the
Transport Layer Security (TLS) Protocol in the Session Transport Layer Security (TLS) Protocol in the Session
Description Protocol (SDP)", RFC 4572, DOI 10.17487/ Description Protocol (SDP)", RFC 4572,
RFC4572, July 2006, DOI 10.17487/RFC4572, July 2006, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4572>. editor.org/info/rfc4572>.
[RFC4574] Levin, O. and G. Camarillo, "The Session Description [RFC4574] Levin, O. and G. Camarillo, "The Session Description
Protocol (SDP) Label Attribute", RFC 4574, DOI 10.17487/ Protocol (SDP) Label Attribute", RFC 4574,
RFC4574, August 2006, DOI 10.17487/RFC4574, August 2006, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4574>. editor.org/info/rfc4574>.
[RFC4583] Camarillo, G., "Session Description Protocol (SDP) Format [RFC4583] Camarillo, G., "Session Description Protocol (SDP) Format
for Binary Floor Control Protocol (BFCP) Streams", RFC for Binary Floor Control Protocol (BFCP) Streams",
4583, DOI 10.17487/RFC4583, November 2006, RFC 4583, DOI 10.17487/RFC4583, November 2006,
<http://www.rfc-editor.org/info/rfc4583>. <https://www.rfc-editor.org/info/rfc4583>.
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,
"Extended RTP Profile for Real-time Transport Control "Extended RTP Profile for Real-time Transport Control
Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, DOI Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585,
10.17487/RFC4585, July 2006, DOI 10.17487/RFC4585, July 2006, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4585>. editor.org/info/rfc4585>.
[RFC4796] Hautakorpi, J. and G. Camarillo, "The Session Description [RFC4796] Hautakorpi, J. and G. Camarillo, "The Session Description
Protocol (SDP) Content Attribute", RFC 4796, DOI 10.17487/ Protocol (SDP) Content Attribute", RFC 4796,
RFC4796, February 2007, DOI 10.17487/RFC4796, February 2007, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4796>. editor.org/info/rfc4796>.
[RFC4975] Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed., [RFC4975] Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed.,
"The Message Session Relay Protocol (MSRP)", RFC 4975, DOI "The Message Session Relay Protocol (MSRP)", RFC 4975,
10.17487/RFC4975, September 2007, DOI 10.17487/RFC4975, September 2007, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4975>. editor.org/info/rfc4975>.
[RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman, [RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman,
"Codec Control Messages in the RTP Audio-Visual Profile "Codec Control Messages in the RTP Audio-Visual Profile
with Feedback (AVPF)", RFC 5104, DOI 10.17487/RFC5104, with Feedback (AVPF)", RFC 5104, DOI 10.17487/RFC5104,
February 2008, <http://www.rfc-editor.org/info/rfc5104>. February 2008, <https://www.rfc-editor.org/info/rfc5104>.
[RFC5109] Li, A., Ed., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., Ed., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, DOI 10.17487/RFC5109, December Correction", RFC 5109, DOI 10.17487/RFC5109, December
2007, <http://www.rfc-editor.org/info/rfc5109>. 2007, <https://www.rfc-editor.org/info/rfc5109>.
[RFC5159] Dondeti, L., Ed. and A. Jerichow, "Session Description [RFC5159] Dondeti, L., Ed. and A. Jerichow, "Session Description
Protocol (SDP) Attributes for Open Mobile Alliance (OMA) Protocol (SDP) Attributes for Open Mobile Alliance (OMA)
Broadcast (BCAST) Service and Content Protection", RFC Broadcast (BCAST) Service and Content Protection",
5159, DOI 10.17487/RFC5159, March 2008, RFC 5159, DOI 10.17487/RFC5159, March 2008,
<http://www.rfc-editor.org/info/rfc5159>. <https://www.rfc-editor.org/info/rfc5159>.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) (ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245, DOI Traversal for Offer/Answer Protocols", RFC 5245,
10.17487/RFC5245, April 2010, DOI 10.17487/RFC5245, April 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5245>. 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, <https://www.rfc-editor.org/info/rfc5285>.
[RFC5432] Polk, J., Dhesikan, S., and G. Camarillo, "Quality of [RFC5432] Polk, J., Dhesikan, S., and G. Camarillo, "Quality of
Service (QoS) Mechanism Selection in the Session Service (QoS) Mechanism Selection in the Session
Description Protocol (SDP)", RFC 5432, DOI 10.17487/ Description Protocol (SDP)", RFC 5432,
RFC5432, March 2009, DOI 10.17487/RFC5432, March 2009, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5432>. editor.org/info/rfc5432>.
[RFC5506] Johansson, I. and M. Westerlund, "Support for Reduced-Size [RFC5506] Johansson, I. and M. Westerlund, "Support for Reduced-Size
Real-Time Transport Control Protocol (RTCP): Opportunities Real-Time Transport Control Protocol (RTCP): Opportunities
and Consequences", RFC 5506, DOI 10.17487/RFC5506, April and Consequences", RFC 5506, DOI 10.17487/RFC5506, April
2009, <http://www.rfc-editor.org/info/rfc5506>. 2009, <https://www.rfc-editor.org/info/rfc5506>.
[RFC5547] Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S., [RFC5547] Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S.,
and P. Kyzivat, "A Session Description Protocol (SDP) and P. Kyzivat, "A Session Description Protocol (SDP)
Offer/Answer Mechanism to Enable File Transfer", RFC 5547, Offer/Answer Mechanism to Enable File Transfer", RFC 5547,
DOI 10.17487/RFC5547, May 2009, DOI 10.17487/RFC5547, May 2009, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5547>. editor.org/info/rfc5547>.
[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,
<http://www.rfc-editor.org/info/rfc5576>. <https://www.rfc-editor.org/info/rfc5576>.
[RFC5583] Schierl, T. and S. Wenger, "Signaling Media Decoding [RFC5583] Schierl, T. and S. Wenger, "Signaling Media Decoding
Dependency in the Session Description Protocol (SDP)", RFC Dependency in the Session Description Protocol (SDP)",
5583, DOI 10.17487/RFC5583, July 2009, RFC 5583, DOI 10.17487/RFC5583, July 2009,
<http://www.rfc-editor.org/info/rfc5583>. <https://www.rfc-editor.org/info/rfc5583>.
[RFC5760] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control [RFC5760] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control
Protocol (RTCP) Extensions for Single-Source Multicast Protocol (RTCP) Extensions for Single-Source Multicast
Sessions with Unicast Feedback", RFC 5760, DOI 10.17487/ Sessions with Unicast Feedback", RFC 5760,
RFC5760, February 2010, DOI 10.17487/RFC5760, February 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5760>. editor.org/info/rfc5760>.
[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, DOI 10.17487/ Control Packets on a Single Port", RFC 5761,
RFC5761, April 2010, DOI 10.17487/RFC5761, April 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5761>. editor.org/info/rfc5761>.
[RFC5762] Perkins, C., "RTP and the Datagram Congestion Control [RFC5762] Perkins, C., "RTP and the Datagram Congestion Control
Protocol (DCCP)", RFC 5762, DOI 10.17487/RFC5762, April Protocol (DCCP)", RFC 5762, DOI 10.17487/RFC5762, April
2010, <http://www.rfc-editor.org/info/rfc5762>. 2010, <https://www.rfc-editor.org/info/rfc5762>.
[RFC5763] Fischl, J., Tschofenig, H., and E. Rescorla, "Framework [RFC5763] Fischl, J., Tschofenig, H., and E. Rescorla, "Framework
for Establishing a Secure Real-time Transport Protocol for Establishing a Secure Real-time Transport Protocol
(SRTP) Security Context Using Datagram Transport Layer (SRTP) Security Context Using Datagram Transport Layer
Security (DTLS)", RFC 5763, DOI 10.17487/RFC5763, May Security (DTLS)", RFC 5763, DOI 10.17487/RFC5763, May
2010, <http://www.rfc-editor.org/info/rfc5763>. 2010, <https://www.rfc-editor.org/info/rfc5763>.
[RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description [RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description
Protocol (SDP) Grouping Framework", RFC 5888, DOI Protocol (SDP) Grouping Framework", RFC 5888,
10.17487/RFC5888, June 2010, DOI 10.17487/RFC5888, June 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5888>. editor.org/info/rfc5888>.
[RFC5939] Andreasen, F., "Session Description Protocol (SDP) [RFC5939] Andreasen, F., "Session Description Protocol (SDP)
Capability Negotiation", RFC 5939, DOI 10.17487/RFC5939, Capability Negotiation", RFC 5939, DOI 10.17487/RFC5939,
September 2010, <http://www.rfc-editor.org/info/rfc5939>. September 2010, <https://www.rfc-editor.org/info/rfc5939>.
[RFC5956] Begen, A., "Forward Error Correction Grouping Semantics in [RFC5956] Begen, A., "Forward Error Correction Grouping Semantics in
the Session Description Protocol", RFC 5956, DOI 10.17487/ the Session Description Protocol", RFC 5956,
RFC5956, September 2010, DOI 10.17487/RFC5956, September 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5956>. editor.org/info/rfc5956>.
[RFC6064] Westerlund, M. and P. Frojdh, "SDP and RTSP Extensions [RFC6064] Westerlund, M. and P. Frojdh, "SDP and RTSP Extensions
Defined for 3GPP Packet-Switched Streaming Service and Defined for 3GPP Packet-Switched Streaming Service and
Multimedia Broadcast/Multicast Service", RFC 6064, DOI Multimedia Broadcast/Multicast Service", RFC 6064,
10.17487/RFC6064, January 2011, DOI 10.17487/RFC6064, January 2011, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6064>. editor.org/info/rfc6064>.
[RFC6128] Begen, A., "RTP Control Protocol (RTCP) Port for Source- [RFC6128] Begen, A., "RTP Control Protocol (RTCP) Port for Source-
Specific Multicast (SSM) Sessions", RFC 6128, DOI Specific Multicast (SSM) Sessions", RFC 6128,
10.17487/RFC6128, February 2011, DOI 10.17487/RFC6128, February 2011, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6128>. editor.org/info/rfc6128>.
[RFC6189] Zimmermann, P., Johnston, A., Ed., and J. Callas, "ZRTP: [RFC6189] Zimmermann, P., Johnston, A., Ed., and J. Callas, "ZRTP:
Media Path Key Agreement for Unicast Secure RTP", RFC Media Path Key Agreement for Unicast Secure RTP",
6189, DOI 10.17487/RFC6189, April 2011, RFC 6189, DOI 10.17487/RFC6189, April 2011,
<http://www.rfc-editor.org/info/rfc6189>. <https://www.rfc-editor.org/info/rfc6189>.
[RFC6193] Saito, M., Wing, D., and M. Toyama, "Media Description for [RFC6193] Saito, M., Wing, D., and M. Toyama, "Media Description for
the Internet Key Exchange Protocol (IKE) in the Session the Internet Key Exchange Protocol (IKE) in the Session
Description Protocol (SDP)", RFC 6193, DOI 10.17487/ Description Protocol (SDP)", RFC 6193,
RFC6193, April 2011, DOI 10.17487/RFC6193, April 2011, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6193>. editor.org/info/rfc6193>.
[RFC6230] Boulton, C., Melanchuk, T., and S. McGlashan, "Media [RFC6230] Boulton, C., Melanchuk, T., and S. McGlashan, "Media
Control Channel Framework", RFC 6230, DOI 10.17487/ Control Channel Framework", RFC 6230,
RFC6230, May 2011, DOI 10.17487/RFC6230, May 2011, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6230>. editor.org/info/rfc6230>.
[RFC6236] Johansson, I. and K. Jung, "Negotiation of Generic Image [RFC6236] Johansson, I. and K. Jung, "Negotiation of Generic Image
Attributes in the Session Description Protocol (SDP)", RFC Attributes in the Session Description Protocol (SDP)",
6236, DOI 10.17487/RFC6236, May 2011, RFC 6236, DOI 10.17487/RFC6236, May 2011,
<http://www.rfc-editor.org/info/rfc6236>. <https://www.rfc-editor.org/info/rfc6236>.
[RFC6284] Begen, A., Wing, D., and T. Van Caenegem, "Port Mapping [RFC6284] Begen, A., Wing, D., and T. Van Caenegem, "Port Mapping
between Unicast and Multicast RTP Sessions", RFC 6284, DOI between Unicast and Multicast RTP Sessions", RFC 6284,
10.17487/RFC6284, June 2011, DOI 10.17487/RFC6284, June 2011, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6284>. editor.org/info/rfc6284>.
[RFC6285] Ver Steeg, B., Begen, A., Van Caenegem, T., and Z. Vax, [RFC6285] Ver Steeg, B., Begen, A., Van Caenegem, T., and Z. Vax,
"Unicast-Based Rapid Acquisition of Multicast RTP "Unicast-Based Rapid Acquisition of Multicast RTP
Sessions", RFC 6285, DOI 10.17487/RFC6285, June 2011, Sessions", RFC 6285, DOI 10.17487/RFC6285, June 2011,
<http://www.rfc-editor.org/info/rfc6285>. <https://www.rfc-editor.org/info/rfc6285>.
[RFC6364] Begen, A., "Session Description Protocol Elements for the [RFC6364] Begen, A., "Session Description Protocol Elements for the
Forward Error Correction (FEC) Framework", RFC 6364, DOI Forward Error Correction (FEC) Framework", RFC 6364,
10.17487/RFC6364, October 2011, DOI 10.17487/RFC6364, October 2011, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6364>. editor.org/info/rfc6364>.
[RFC6642] Wu, Q., Ed., Xia, F., and R. Even, "RTP Control Protocol [RFC6642] Wu, Q., Ed., Xia, F., and R. Even, "RTP Control Protocol
(RTCP) Extension for a Third-Party Loss Report", RFC 6642, (RTCP) Extension for a Third-Party Loss Report", RFC 6642,
DOI 10.17487/RFC6642, June 2012, DOI 10.17487/RFC6642, June 2012, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6642>. editor.org/info/rfc6642>.
[RFC6679] Westerlund, M., Johansson, I., Perkins, C., O'Hanlon, P., [RFC6679] Westerlund, M., Johansson, I., Perkins, C., O'Hanlon, P.,
and K. Carlberg, "Explicit Congestion Notification (ECN) and K. Carlberg, "Explicit Congestion Notification (ECN)
for RTP over UDP", RFC 6679, DOI 10.17487/RFC6679, August for RTP over UDP", RFC 6679, DOI 10.17487/RFC6679, August
2012, <http://www.rfc-editor.org/info/rfc6679>. 2012, <https://www.rfc-editor.org/info/rfc6679>.
[RFC6714] Holmberg, C., Blau, S., and E. Burger, "Connection [RFC6714] Holmberg, C., Blau, S., and E. Burger, "Connection
Establishment for Media Anchoring (CEMA) for the Message Establishment for Media Anchoring (CEMA) for the Message
Session Relay Protocol (MSRP)", RFC 6714, DOI 10.17487/ Session Relay Protocol (MSRP)", RFC 6714,
RFC6714, August 2012, DOI 10.17487/RFC6714, August 2012, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6714>. editor.org/info/rfc6714>.
[RFC6773] Phelan, T., Fairhurst, G., and C. Perkins, "DCCP-UDP: A [RFC6773] Phelan, T., Fairhurst, G., and C. Perkins, "DCCP-UDP: A
Datagram Congestion Control Protocol UDP Encapsulation for Datagram Congestion Control Protocol UDP Encapsulation for
NAT Traversal", RFC 6773, DOI 10.17487/RFC6773, November NAT Traversal", RFC 6773, DOI 10.17487/RFC6773, November
2012, <http://www.rfc-editor.org/info/rfc6773>. 2012, <https://www.rfc-editor.org/info/rfc6773>.
[RFC6787] Burnett, D. and S. Shanmugham, "Media Resource Control [RFC6787] Burnett, D. and S. Shanmugham, "Media Resource Control
Protocol Version 2 (MRCPv2)", RFC 6787, DOI 10.17487/ Protocol Version 2 (MRCPv2)", RFC 6787,
RFC6787, November 2012, DOI 10.17487/RFC6787, November 2012, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6787>. editor.org/info/rfc6787>.
[RFC6849] Kaplan, H., Ed., Hedayat, K., Venna, N., Jones, P., and N. [RFC6849] Kaplan, H., Ed., Hedayat, K., Venna, N., Jones, P., and N.
Stratton, "An Extension to the Session Description Stratton, "An Extension to the Session Description
Protocol (SDP) and Real-time Transport Protocol (RTP) for Protocol (SDP) and Real-time Transport Protocol (RTP) for
Media Loopback", RFC 6849, DOI 10.17487/RFC6849, February Media Loopback", RFC 6849, DOI 10.17487/RFC6849, February
2013, <http://www.rfc-editor.org/info/rfc6849>. 2013, <https://www.rfc-editor.org/info/rfc6849>.
[RFC6871] Gilman, R., Even, R., and F. Andreasen, "Session [RFC6871] Gilman, R., Even, R., and F. Andreasen, "Session
Description Protocol (SDP) Media Capabilities Description Protocol (SDP) Media Capabilities
Negotiation", RFC 6871, DOI 10.17487/RFC6871, February Negotiation", RFC 6871, DOI 10.17487/RFC6871, February
2013, <http://www.rfc-editor.org/info/rfc6871>. 2013, <https://www.rfc-editor.org/info/rfc6871>.
[RFC6947] Boucadair, M., Kaplan, H., Gilman, R., and S. [RFC6947] Boucadair, M., Kaplan, H., Gilman, R., and S.
Veikkolainen, "The Session Description Protocol (SDP) Veikkolainen, "The Session Description Protocol (SDP)
Alternate Connectivity (ALTC) Attribute", RFC 6947, DOI Alternate Connectivity (ALTC) Attribute", RFC 6947,
10.17487/RFC6947, May 2013, DOI 10.17487/RFC6947, May 2013, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6947>. editor.org/info/rfc6947>.
[RFC7006] Garcia-Martin, M., Veikkolainen, S., and R. Gilman, [RFC7006] Garcia-Martin, M., Veikkolainen, S., and R. Gilman,
"Miscellaneous Capabilities Negotiation in the Session "Miscellaneous Capabilities Negotiation in the Session
Description Protocol (SDP)", RFC 7006, DOI 10.17487/ Description Protocol (SDP)", RFC 7006,
RFC7006, September 2013, DOI 10.17487/RFC7006, September 2013, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7006>. editor.org/info/rfc7006>.
[RFC7104] Begen, A., Cai, Y., and H. Ou, "Duplication Grouping [RFC7104] Begen, A., Cai, Y., and H. Ou, "Duplication Grouping
Semantics in the Session Description Protocol", RFC 7104, Semantics in the Session Description Protocol", RFC 7104,
DOI 10.17487/RFC7104, January 2014, DOI 10.17487/RFC7104, January 2014, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7104>. editor.org/info/rfc7104>.
[RFC7195] Garcia-Martin, M. and S. Veikkolainen, "Session [RFC7195] Garcia-Martin, M. and S. Veikkolainen, "Session
Description Protocol (SDP) Extension for Setting Audio and Description Protocol (SDP) Extension for Setting Audio and
Video Media Streams over Circuit-Switched Bearers in the Video Media Streams over Circuit-Switched Bearers in the
Public Switched Telephone Network (PSTN)", RFC 7195, DOI Public Switched Telephone Network (PSTN)", RFC 7195,
10.17487/RFC7195, May 2014, DOI 10.17487/RFC7195, May 2014, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7195>. editor.org/info/rfc7195>.
[RFC7197] Begen, A., Cai, Y., and H. Ou, "Duplication Delay [RFC7197] Begen, A., Cai, Y., and H. Ou, "Duplication Delay
Attribute in the Session Description Protocol", RFC 7197, Attribute in the Session Description Protocol", RFC 7197,
DOI 10.17487/RFC7197, April 2014, DOI 10.17487/RFC7197, April 2014, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7197>. editor.org/info/rfc7197>.
[RFC7266] Clark, A., Wu, Q., Schott, R., and G. Zorn, "RTP Control [RFC7266] Clark, A., Wu, Q., Schott, R., and G. Zorn, "RTP Control
Protocol (RTCP) Extended Report (XR) Blocks for Mean Protocol (RTCP) Extended Report (XR) Blocks for Mean
Opinion Score (MOS) Metric Reporting", RFC 7266, DOI Opinion Score (MOS) Metric Reporting", RFC 7266,
10.17487/RFC7266, June 2014, DOI 10.17487/RFC7266, June 2014, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7266>. editor.org/info/rfc7266>.
[RFC7272] van Brandenburg, R., Stokking, H., van Deventer, O., [RFC7272] van Brandenburg, R., Stokking, H., van Deventer, O.,
Boronat, F., Montagud, M., and K. Gross, "Inter- Boronat, F., Montagud, M., and K. Gross, "Inter-
Destination Media Synchronization (IDMS) Using the RTP Destination Media Synchronization (IDMS) Using the RTP
Control Protocol (RTCP)", RFC 7272, DOI 10.17487/RFC7272, Control Protocol (RTCP)", RFC 7272, DOI 10.17487/RFC7272,
June 2014, <http://www.rfc-editor.org/info/rfc7272>. June 2014, <https://www.rfc-editor.org/info/rfc7272>.
[RFC7273] Williams, A., Gross, K., van Brandenburg, R., and H. [RFC7273] Williams, A., Gross, K., van Brandenburg, R., and H.
Stokking, "RTP Clock Source Signalling", RFC 7273, DOI Stokking, "RTP Clock Source Signalling", RFC 7273,
10.17487/RFC7273, June 2014, DOI 10.17487/RFC7273, June 2014, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7273>. editor.org/info/rfc7273>.
[RFC7657] Black, D., Ed. and P. Jones, "Differentiated Services [RFC7657] Black, D., Ed. and P. Jones, "Differentiated Services
(Diffserv) and Real-Time Communication", RFC 7657, DOI (Diffserv) and Real-Time Communication", RFC 7657,
10.17487/RFC7657, November 2015, DOI 10.17487/RFC7657, November 2015, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7657>. editor.org/info/rfc7657>.
[T.38] "Procedures for real-time Group 3 facsimile communication [T.38] "Procedures for real-time Group 3 facsimile communication
over IP networks", <http://www.itu.int/rec/T-REC-T.38/e>. over IP networks", <http://www.itu.int/rec/T-REC-T.38/e>.
Author's Address Author's Address
Suhas Nandakumar Suhas Nandakumar
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: snandaku@cisco.com Email: snandaku@cisco.com
 End of changes. 139 change blocks. 
1169 lines changed or deleted 1168 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/