draft-ietf-mmusic-sdp-mux-attributes-10.txt   draft-ietf-mmusic-sdp-mux-attributes-11.txt 
Network Working Group S. Nandakumar Network Working Group S. Nandakumar
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track July 5, 2015 Intended status: Standards Track January 4, 2016
Expires: January 6, 2016 Expires: July 7, 2016
A Framework for SDP Attributes when Multiplexing A Framework for SDP Attributes when Multiplexing
draft-ietf-mmusic-sdp-mux-attributes-10 draft-ietf-mmusic-sdp-mux-attributes-11
Abstract Abstract
The Session Description Protocol (SDP) provides mechanisms to The Session Description Protocol (SDP) provides mechanisms to
describe attributes of multimedia sessions and of individual media describe attributes of multimedia sessions and of individual media
streams (e.g., Real-time Transport Protocol (RTP) sessions) within a streams (e.g., Real-time Transport Protocol (RTP) sessions) within a
multimedia session. Typically media associated with individual media multimedia session. Typically media associated with individual media
descriptions ("m=" lines) represent RTP sessions and are thus carried descriptions ("m=" lines) represent RTP sessions and are thus carried
over individual underlying transport layer flows. For scenarios over individual underlying transport layer flows. For scenarios
where SDP is used to negotiate the usage of single 5-tuple for where SDP is used to negotiate the usage of single 5-tuple for
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 January 6, 2016. This Internet-Draft will expire on July 7, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 48 skipping to change at page 2, line 48
4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7 4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7
4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 8 4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 8
4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8 4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8
4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 9 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 . . . . . . . . . . . . . . . 11 4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 11
4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 12 4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 12
4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 12 4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 12
5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12 5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12
5.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 13 5.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 13
5.2. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 14 5.2. RFC4585: RTP/AVPF . . . . . . . . . . . . . . . . . . . . 14
5.3. RFC5761 - Multiplexing RTP and RTCP . . . . . . . . . . . 15 5.3. RFC5761: Multiplexing RTP and RTCP . . . . . . . . . . . 15
5.4. RFC3312 - Integration of Resource Management and (SIP) . 15 5.4. RFC3312: Integration of Resource Management and SIP . . . 15
5.5. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 16 5.5. RFC4574: SDP Label Attribute . . . . . . . . . . . . . . 16
5.6. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 16 5.6. RFC5432: QOS Mechanism Selection in SDP . . . . . . . . . 16
5.7. RFC4568 - SDP Security Descriptions . . . . . . . . . . . 17 5.7. RFC4568: SDP Security Descriptions . . . . . . . . . . . 17
5.8. RFC5762 - RTP over DCCP . . . . . . . . . . . . . . . . . 17 5.8. RFC5762: RTP over DCCP . . . . . . . . . . . . . . . . . 17
5.9. RFC6773 - DCCP-UDP Encapsulation . . . . . . . . . . . . 18 5.9. RFC6773: DCCP-UDP Encapsulation . . . . . . . . . . . . . 18
5.10. RFC5506 - Reduced-Size RTCP in RTP Profile . . . . . . . 19 5.10. RFC5506: Reduced-Size RTCP in RTP Profile . . . . . . . . 19
5.11. RFC6787 - Media Resource Control Protocol Version 2 . . . 19 5.11. RFC6787: Media Resource Control Protocol Version 2 . . . 19
5.12. RFC5245 - Interactive Connectivity Establishment (ICE) . 20 5.12. RFC5245: ICE . . . . . . . . . . . . . . . . . . . . . . 20
5.13. RFC5285 - RTP Header Extensions . . . . . . . . . . . . . 21 5.13. RFC5285: RTP Header Extensions . . . . . . . . . . . . . 21
5.14. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 22 5.14. RFC3605: RTCP attribute in SDP . . . . . . . . . . . . . 22
5.15. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 22 5.15. RFC5576: Source-Specific SDP Attributes . . . . . . . . . 22
5.16. RFC7273 - RTP Clock Source Signalling . . . . . . . . . . 23 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 . . 25 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 . . . . . . . . . . . . . . . . . . . 27 5.26. RFC6714: MSRP-CEMA . . . . . . . . . . . . . . . . . . . 28
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 . . . . . . . . . . . . . . . . . . . . 31 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 . . . . . . . 32 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 - OMA BCAST SDP Attributes . . . . . . . . . . . 38 5.44. RFC5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP
5.45. RFC6193 - Media Description for IKE in SDP . . . . . . . 38 Attributes . . . . . . . . . . . . . . . . . . . . . . . 39
5.46. RFC2326 - Real Time Streaming Protocol . . . . . . . . . 39 5.45. RFC6193: Media Description for IKE in SDP . . . . . . . . 39
5.47. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 40 5.46. RFC2326: Real Time Streaming Protocol . . . . . . . . . . 40
5.48. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 43 5.47. RFC6064: SDP and RTSP Extensions for 3GPP . . . . . . . . 41
5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 45 5.48. RFC3108: ATM SDP . . . . . . . . . . . . . . . . . . . . 44
5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 46 5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 46
5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 46 5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 47
5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 47
5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 47 5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 47
5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 47 5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 48
5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 48 5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 49
5.55. ITU-T Q.1970 . . . . . . . . . . . . . . . . . . . . . . 50 5.55. ITU-T Q.1970 . . . . . . . . . . . . . . . . . . . . . . 51
5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 50 5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 51
5.57. RFC4975 - The Message Session Relay Protocol . . . . . . 51 5.57. RFC4975: The Message Session Relay Protocol . . . . . . . 52
5.58. Historical Attributes . . . . . . . . . . . . . . . . . . 52 5.58. Historical Attributes . . . . . . . . . . . . . . . . . . 53
6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 52 6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 53
6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 53 6.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 54
6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 53 6.2. RFC3556: SDP Bandwidth Modifiers for RTCP Bandwidth . . . 54
6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 54 6.3. RFC3890: Bandwidth Modifier for SDP . . . . . . . . . . . 55
7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 54 7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 55
7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 54 7.1. RFC4585: RTP/AVPF . . . . . . . . . . . . . . . . . . . . 55
7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 55 7.2. RFC5104: Codec Control Messages in AVPF . . . . . . . . . 56
7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 56 7.3. RFC6285: Unicast-Based Rapid Acquisition of Multicast RTP
7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 56 Sessions (RAMS) . . . . . . . . . . . . . . . . . . . . . 57
7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 57 7.4. RFC6679: ECN for RTP over UDP/IP . . . . . . . . . . . . 57
7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 58 7.5. RFC6642: Third-Party Loss Report . . . . . . . . . . . . 58
8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 58 7.6. RFC5104: Codec Control Messages in AVPF . . . . . . . . . 59
8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 58 8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 59
8.2. RFC3524 - Mapping Media Streams to Resource 8.1. RFC5888: SDP Grouping Framework . . . . . . . . . . . . . 59
Reservation Flows . . . . . . . . . . . . . . . . . . . . 59 8.2. RFC3524: Mapping Media Streams to Resource
8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 59 Reservation Flows . . . . . . . . . . . . . . . . . . . . 60
8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 60 8.3. RFC4091: ANAT Semantics . . . . . . . . . . . . . . . . . 60
8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 60 8.4. RFC5956: FEC Grouping Semantics in SDP . . . . . . . . . 60
8.6. RFC7104 - Duplication Grouping Semantics in the SDP . . 61 8.5. RFC5583: Signaling Media Decoding Dependency in SDP . . . 61
9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 61 8.6. RFC7104: Duplication Grouping Semantics in the SDP . . . 61
9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 61 9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 62
9.2. RFC7104 - Duplication Grouping Semantics in the SDP . . . 61 9.1. RFC5576: Source-Specific SDP Attributes . . . . . . . . . 62
10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 62 9.2. RFC7104: Duplication Grouping Semantics in the SDP . . . 62
10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 62 10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 63
10.1. RFC5432: QoS Mechanism Selection in SDP . . . . . . . . 63
11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 63 11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 63
11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 63 11.1. RFC4566: SDP . . . . . . . . . . . . . . . . . . . . . . 64
12. content Attribute Analysis . . . . . . . . . . . . . . . . . 63 12. content Attribute Analysis . . . . . . . . . . . . . . . . . 64
12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 63 12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 64
13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 64 13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 65
13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 64 13.1. RFC5109: RTP Payload Format for Generic FEC . . . . . . 65
14. Multiplexing Considerations for Encapsulating Attributes . . 64 14. Multiplexing Considerations for Encapsulating Attributes . . 65
14.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 65 14.1. RFC3407: cpar Attribute Analysis . . . . . . . . . . . . 66
14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 65 14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 66
14.2.1. Recommendation - Procedures for Potential 14.2.1. Recommendation: Procedures for Potential
Configuration Pairing . . . . . . . . . . . . . . . 66 Configuration Pairing . . . . . . . . . . . . . . . 67
14.2.1.1. Example: Transport Capability Multiplexing . . . 67 14.2.1.1. Example: Transport Capability Multiplexing . . . 68
14.2.1.2. Example: Attribute Capability Multiplexing . . . 68 14.2.1.2. Example: Attribute Capability Multiplexing . . . 69
14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 69 14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 70
14.3.1. Recommendation: Dealing with Payload Type Numbers . 69 14.3.1. Recommendation: Dealing with Payload Type Numbers . 70
14.3.1.1. Example: Attribute Capability Under Shared 14.3.1.1. Example: Attribute Capability Under Shared
Payload Type . . . . . . . . . . . . . . . . . . 69 Payload Type . . . . . . . . . . . . . . . . . . 70
14.3.2. Recommendation: Dealing with Latent Configurations . 71
14.3.2. Recommendation: Dealing with Latent Configurations . 70 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 72
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 71 15.1. New 'Multiplexing Categories' subregistry . . . . . . . 72
15.1. New 'Multiplexing Categories' subregistry . . . . . . . 71 15.2. 'Mux Category' column for subregistries . . . . . . . . 73
15.2. 'Mux Category' column for subregistries . . . . . . . . 72 15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 73
15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 72 15.2.2. Table: att-field (session level) . . . . . . . . . . 73
15.2.2. Table: att-field (session level) . . . . . . . . . . 72 15.2.3. Table: att-field (both session and media level) . . 74
15.2.3. Table: att-field (both session and media level) . . 73 15.2.4. Table: att-field (media level only) . . . . . . . . 76
15.2.4. Table: att-field (media level only) . . . . . . . . 75 15.2.5. Table: att-field (source level) . . . . . . . . . . 79
15.2.5. Table: att-field (source level) . . . . . . . . . . 78 15.2.6. Table: content SDP Parameters . . . . . . . . . . . 80
15.2.6. Table: content SDP Parameters . . . . . . . . . . . 79 15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 80
15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 79 15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 80
15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 79 15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 81
15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 80 15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 81
15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 80 15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 82
15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 81 15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 82
15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 81 15.2.13. Table: SDP/RTSP key management protocol identifiers 82
15.2.13. Table: SDP/RTSP key management protocol identifiers 81 15.2.14. Table: Codec Control Messages . . . . . . . . . . . 83
15.2.14. Table: Codec Control Messages . . . . . . . . . . . 82 15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 83
15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 82 15.2.16. Table: SDP Capability Negotiation Option Tags . . . 83
15.2.16. Table: SDP Capability Negotiation Option Tags . . . 82 15.2.17. Table: Timestamp Reference Clock Source Parameters . 84
15.2.17. Table: Timestamp Reference Clock Source Parameters . 83 15.2.18. Table: Media Clock Source Parameters . . . . . . . . 84
15.2.18. Table: Media Clock Source Parameters . . . . . . . . 83 16. Security Considerations . . . . . . . . . . . . . . . . . . . 84
16. Security Considerations . . . . . . . . . . . . . . . . . . . 83 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 85
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 84 18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 85
18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 84 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 88
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 87 19.1. Normative References . . . . . . . . . . . . . . . . . . 88
19.1. Normative References . . . . . . . . . . . . . . . . . . 87 19.2. Informative References . . . . . . . . . . . . . . . . . 88
19.2. Informative References . . . . . . . . . . . . . . . . . 87 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 96
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 93
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
single address:port combination (BUNDLE address) for receiving media single address:port combination (BUNDLE address) for receiving media
associated with multiple SDP media descriptions. This would for e.g. associated with multiple SDP media descriptions. This would for e.g.
allow the usage of a single set of ICE [RFC5245] candidates for allow the usage of a single set of Interactive Connectivity
multiple media descriptions. This in turn has made necessary to Establishment (ICE) [RFC5245] candidates for multiple media
understand the interpretation and usage of the SDP attributes defined descriptions. This in turn has made necessary to understand the
for the multiplexed media descriptions. interpretation and usage of the SDP attributes defined for the
multiplexed media descriptions.
Given the number of SDP attributes registered with the [IANA] and Given the number of SDP attributes registered with the [IANA] and
possibility of new attributes being defined in the future, there is possibility of new attributes being defined in the future, there is
need for generic future-proof framework to analyze these attributes need for generic future-proof framework to analyze these attributes
for their applicability in the transport multiplexing use-cases. for their applicability in the transport multiplexing use-cases.
The document starts with providing the motivation for requiring such The document starts with providing the motivation for requiring such
a framework. This is followed by introduction to the SDP attribute a framework. This is followed by introduction to the SDP attribute
analysis framework/procedures, following which several sections apply analysis framework/procedures, following which several sections apply
the framework to the SDP attributes registered with the [IANA]. the framework to the SDP attributes registered with the [IANA].
2. Terminology 2. Terminology
5-tuple: A collection of the following values: source address, source 5-tuple: A collection of the following values: source address, source
port, destination address, destination port, and transport-layer port, destination address, destination port, and transport-layer
protocol. protocol.
The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", 3GPP: Third Generation Partnership Project; see http://www.3gpp.org
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be for more information about this organization.
interpreted as described in [RFC2119].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. Motivation 3. Motivation
The time and complications of setting up ICE [RFC5245] and DTLS-SRTP The time and complications of setting up ICE [RFC5245] and Datagram
[RFC5763] transports for use by RTP, and conservation of ports (to Transport Layer Security (DTLS) based Secure Real-time Transport
avoid maintaining large number of NAT bindings open, reduce time/ Protocol (SRTP) [RFC5763] transports for use by RTP, and conservation
ports needed for ICE to detect connectivity), forms a requirement to of ports (to avoid maintaining large number of Network Address
try and reduce the number of transport level flows needed. This has Translator (NAT) bindings open, reduce time/ports needed for ICE to
resulted in the definition of ways, such as, detect connectivity), forms a requirement to try and reduce the
[I-D.ietf-mmusic-sdp-bundle-negotiation] to multiplex RTP over a number of transport level flows needed. This has resulted in the
single transport flow in order to preserve network resources such as definition of ways, such as, [I-D.ietf-mmusic-sdp-bundle-negotiation]
port numbers. This imposes further restrictions on applicability of to multiplex RTP over a single transport flow in order to preserve
the SDP attributes as they are defined today. network resources such as port numbers. This imposes further
restrictions on applicability of the SDP attributes as they are
defined today.
The specific problem is that there are attribute combinations which The specific problem is that there are attribute combinations which
make sense when specified on independent "m=" lines -- as with make sense when specified on independent "m=" lines -- as with
classical SDP -- that do not make sense when those "m=" lines are classical SDP -- that do not make sense when those "m=" lines are
then multiplexed over the same transport. To give an obvious then multiplexed over the same transport. To give an obvious
example, ICE permits each "m=" line to have an independently example, ICE permits each "m=" line to have an independently
specified ice-ufrag attribute. However, if the media from multiple specified ice-ufrag attribute. However, if the media from multiple
"m=" lines is multiplexed over the same ICE component, then the "m=" lines is multiplexed over the same ICE component, then the
meaning of media-level ice-ufrag attributes becomes muddled. meaning of media-level ice-ufrag attributes becomes muddled.
skipping to change at page 7, line 14 skipping to change at page 7, line 20
4. SDP Attribute Analysis Framework 4. SDP Attribute Analysis Framework
Attributes in an SDP session description can be defined at the Attributes in an SDP session description can be defined at the
session-level and media-level. Informally, these attributes could be session-level and media-level. Informally, these attributes could be
semantically grouped as noted below. semantically grouped as noted below.
o Attributes related to media content such as media type, encoding o Attributes related to media content such as media type, encoding
schemes, payload types. schemes, payload types.
o Attributes specifying media transport characteristics like RTP/ o Attributes specifying media transport characteristics like RTP/RTP
RTCP port numbers, network addresses, QOS. Control Protocol (RTCP) port numbers, network addresses, QOS.
o Metadata description attributes capturing session timing and o Metadata description attributes capturing session timing and
origin information. origin information.
o Attributes establishing relationships between media descriptions o Attributes establishing relationships between media descriptions
such as grouping framework [RFC5888] such as grouping framework [RFC5888]
With the above semantic grouping as a reference, the proposed With the above semantic grouping as a reference, the proposed
framework classifies each attribute into one of the following framework classifies each attribute into one of the following
categories: categories:
skipping to change at page 8, line 10 skipping to change at page 8, line 24
m=video 49172 RTP/AVP 31 m=video 49172 RTP/AVP 31
a=recvonly a=recvonly
a=label:2 a=label:2
a=rtpmap:31 H261/90000 a=rtpmap:31 H261/90000
4.2. Category: NOT RECOMMENDED 4.2. Category: NOT RECOMMENDED
Attributes that are not recommended for multiplexing since their Attributes that are not recommended for multiplexing since their
usage under multiplexing might lead to incorrect behavior. usage under multiplexing might lead to incorrect behavior.
Example: Multiplexing media descriptions over a single DCCP transport Example: Multiplexing media descriptions over a single Datagram
[RFC5762] is NOT RECOMMENDED since DCCP being a connection oriented Congestion Control Protocol (DCCP) transport [RFC5762] is NOT
protocol doesn't allow multiple connections on the same 5-tuple. RECOMMENDED since DCCP being a connection oriented protocol doesn't
allow multiple connections on the same 5-tuple.
v=0 v=0
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=video 5004 DCCP/RTP/AVP 99 m=video 5004 DCCP/RTP/AVP 99
a=rtpmap:99 h261/9000 a=rtpmap:99 h261/9000
a=dccp-service-code:SC=x52545056 a=dccp-service-code:SC=x52545056
a=setup:passive a=setup:passive
skipping to change at page 9, line 20 skipping to change at page 9, line 33
independently. This is typically used for bandwidth or other rate independently. This is typically used for bandwidth or other rate
limiting attributes to the underlying transport. 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
descriptions to determine the AS value for the multiplexed session. descriptions to determine the AS value for the multiplexed session.
Thus the calculated AS value would be 256+64 kilobits per second for Thus the calculated AS value would be 256+64 kilobits per second for
the given example. the given example.
v=0 v=0
o=test 2890844526 2890842807 IN IP4 126.16.64.4 o=test 2890844526 2890842807 IN IP4 client.biloxi.example.com
c=IN IP4 client.biloxi.example.com c=IN IP4 client.biloxi.example.com
t=0 0 t=0 0
m=audio 49170 RTP/AVP 0 m=audio 49170 RTP/AVP 0
b=AS:64 b=AS:64
m=video 51372 RTP/AVP 31 m=video 51372 RTP/AVP 31
b=AS:256 b=AS:256
4.5. Category: TRANSPORT 4.5. Category: TRANSPORT
Attributes that can be set normally for multiple items in a Attributes that can be set normally for multiple items in a
skipping to change at page 10, line 28 skipping to change at page 10, line 33
a=crypto:1 AES_CM_128_HMAC_SHA1_80 a=crypto:1 AES_CM_128_HMAC_SHA1_80
inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32 inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32
a=rtpmap:96 H261/90000 a=rtpmap:96 H261/90000
4.6. Category: INHERIT 4.6. Category: INHERIT
Attributes that encapsulate other SDP attributes or parameters. Attributes that encapsulate other SDP attributes or parameters.
These attributes inherit their multiplexing characteristics from the These attributes inherit their multiplexing characteristics from the
attributes or parameters they encapsulate. Such attributes are attributes or parameters they encapsulate. Such attributes are
defined in [RFC3407], [RFC5939] and [RFC6871] as part of a generic defined in [RFC3407], [RFC5939] and [RFC6871] as part of a generic
framework for indicating and negotiating transport, media and media framework for indicating and negotiating transport, media, and media
format related capabilities in the SDP. format related capabilities in the SDP.
The inheritance manifests itself when the encapsulated attribute or The inheritance manifests itself when the encapsulated attribute or
parameter is being leveraged. In the case of SDP Capability parameter is being leveraged. In the case of SDP Capability
Negotiation [RFC5939] for example, this occurs when a capability Negotiation [RFC5939] for example, this occurs when a capability
(encapsulating attribute) is used as part of a configuration; the (encapsulating attribute) is used as part of a configuration; the
configuration inherits the multiplexing category of each of its configuration inherits the multiplexing category of each of its
constituent (encapsulated) attributes and parameters. This in turn constituent (encapsulated) attributes and parameters. This in turn
MAY place constraints on what constitutes a valid configuration from MAY place constraints on what constitutes a valid configuration from
a multiplexing point of view, e.g. because some attributes MUST be a multiplexing point of view, e.g. because some attributes MUST be
skipping to change at page 13, line 14 skipping to change at page 13, line 14
o M -- Media level o M -- Media level
o B -- Both o B -- Both
o SR -- Source-level (for a single SSRC) [RFC5576] o SR -- Source-level (for a single SSRC) [RFC5576]
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: Session Description Protocol 5.1. RFC4566: SDP
[RFC4566] defines the Session Description Protocol (SDP) that is [RFC4566] defines SDP that is intended for describing multimedia
intended for describing multimedia sessions for the purposes of sessions for the purposes of session announcement, session
session announcement, session invitation, and other forms of invitation, and other forms of multimedia session initiation.
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 |
| | | | | | | | | |
skipping to change at page 14, line 41 skipping to change at page 14, line 40
| 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 |
| | | | | | | | | |
+-----------------+---------------------+-------+-------------------+ +-----------------+---------------------+-------+-------------------+
RFC4566 Attribute Analysis 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-fb | Since RTCP feedback | M | IDENTICAL-PER-PT |
| | attributes are Payload | | | | | attributes are Payload | | |
| | Type (PT) scoped, their | | | | | Type (PT) scoped, their | | |
| | values MUST be identical | | | | | values MUST be identical | | |
| | for a given PT across the | | | | | for a given PT across the | | |
| | multiplexed "m=" lines. | | | | | multiplexed "m=" lines. | | |
| | | | | | | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
RFC4585 Attribute Analysis 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 Session Description Protocol (SDP) can be used to explains how the SDP can be used to signal multiplexed sessions.
signal multiplexed sessions.
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| rtcp-mux | RTP and RTCP Multiplexing | M | IDENTICAL | | rtcp-mux | RTP and RTCP Multiplexing | M | IDENTICAL |
| | affects the entire RTP session | | | | | affects the entire RTP session | | |
| | | | | | | | | |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
RFC5761 Attribute Analysis 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
reserve network resources before continuing with the session. reserve network resources before continuing with the session.
+-------+-----------------------+-------+------------------+ +-------+-----------------------+-------+------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
skipping to change at page 16, line 22 skipping to change at page 16, line 22
| curr | Refer to notes below | M | NOT RECOMMENDED | | curr | Refer to notes below | M | NOT RECOMMENDED |
| | | | | | | | | |
+-------+-----------------------+-------+------------------+ +-------+-----------------------+-------+------------------+
RFC3312 Attribute Analysis RFC3312 Attribute Analysis
NOTE: A mismatched set of preconditions across media descriptions NOTE: A mismatched set of preconditions across media descriptions
results in Session establishment failures due to inability in meeting results in Session establishment failures due to inability in meeting
the right resource reservations requested. the right resource reservations requested.
5.5. RFC4574 - SDP Label Attribute 5.5. RFC4574: SDP Label Attribute
[RFC4574] defines a new Session Description Protocol (SDP) media- [RFC4574] defines a new SDP media-level attribute: "label". The
level attribute: "label". The "label" attribute carries a pointer to "label" attribute carries a pointer to a media stream in the context
a media stream in the context of an arbitrary network application of an arbitrary network application that uses SDP. The sender of the
that uses SDP. The sender of the SDP document can attach the "label" SDP document can attach the "label" attribute to a particular media
attribute to a particular media stream or streams. The application stream or streams. The application can then use the provided pointer
can then use the provided pointer to refer to each particular media to refer to each particular media stream in its context.
stream in its context.
+--------+---------------+-------+--------------+ +--------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+--------+---------------+-------+--------------+ +--------+---------------+-------+--------------+
| label | Not Impacted | M | NORMAL | | label | Not Impacted | M | NORMAL |
| | | | | | | | | |
+--------+---------------+-------+--------------+ +--------+---------------+-------+--------------+
RFC4574 Attribute Analysis RFC4574 Attribute Analysis
5.6. RFC5432 - QoS Mechanism Selection in SDP 5.6. RFC5432: QOS Mechanism Selection in SDP
[RFC5432] defines procedures to negotiate QOS mechanisms using the [RFC5432] defines procedures to negotiate QOS mechanisms using the
Session Description Protocol (SDP) offer/answer model. SDP offer/answer model.
+----------------+----------------------------+-------+-------------+ +----------------+----------------------------+-------+-------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------------+----------------------------+-------+-------------+ +----------------+----------------------------+-------+-------------+
| qos-mech-send | Refer to section Section | B | TRANSPORT | | qos-mech-send | Refer to section Section | B | TRANSPORT |
| | 10 | | | | | 10 | | |
| | | | | | | | | |
| qos-mech-recv | Refer to section Section | B | TRANSPORT | | qos-mech-recv | Refer to section Section | B | TRANSPORT |
| | 10 | | | | | 10 | | |
| | | | | | | | | |
+----------------+----------------------------+-------+-------------+ +----------------+----------------------------+-------+-------------+
RFC5432 Attribute Analysis RFC5432 Attribute Analysis
5.7. RFC4568 - SDP Security Descriptions 5.7. RFC4568: SDP Security Descriptions
[RFC4568] defines a Session Description Protocol (SDP) cryptographic [RFC4568] defines a SDP cryptographic attribute for unicast media
attribute for unicast media streams. The attribute describes a streams. The attribute describes a cryptographic key and other
cryptographic key and other parameters that serve to configure parameters that serve to configure security for a unicast media
security for a unicast media stream in either a single message or a stream in either a single message or a roundtrip exchange.
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 transport flow | | | | | underlying transport flow | | |
| | | | | | | | | |
+---------+------------------------------------+-------+------------+ +---------+------------------------------------+-------+------------+
RFC4568 Attribute Analysis RFC4568 Attribute Analysis
5.8. RFC5762 - RTP over DCCP 5.8. RFC5762: RTP over DCCP
The Real-time Transport Protocol (RTP) is a widely used transport for RTP is a widely used transport for real-time multimedia on IP
real-time multimedia on IP networks. The Datagram Congestion Control networks. DCCP is a transport protocol that provides desirable
Protocol (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 Category | | Name | Notes | Current | Mux Category |
+--------------------+---------------------+---------+--------------+ +--------------------+---------------------+---------+--------------+
| dccp-service-code | If RFC6773 is not | M | NOT | | dccp-service-code | If RFC6773 is not | M | NOT |
| | being used in | | RECOMMENDED | | | being used in | | RECOMMENDED |
| | addition to | | | | | addition to | | |
skipping to change at page 18, line 26 skipping to change at page 18, line 26
| | it does not allow | | | | | it does not allow | | |
| | multiple | | | | | multiple | | |
| | connections on the | | | | | connections on the | | |
| | same 5-tuple | | | | | same 5-tuple | | |
| | | | | | | | | |
+--------------------+---------------------+---------+--------------+ +--------------------+---------------------+---------+--------------+
RFC5762 Attribute Analysis RFC5762 Attribute Analysis
If RFC6773 is being used in addition to RFC5762 and provided that If RFC6773 is being used in addition to RFC5762 and provided that
DCCP-in-UDP layer has additional demultiplexing, then it may be 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 standardized yet and it wouldn't work as explained. Hence
multiplexing MUST not be performed even in this alternate scenario. multiplexing MUST NOT be performed even in this alternate scenario.
5.9. RFC6773 - DCCP-UDP Encapsulation 5.9. RFC6773: DCCP-UDP Encapsulation
[RFC6773] document specifies an alternative encapsulation of the [RFC6773] document specifies an alternative encapsulation of DCCP,
Datagram Congestion Control Protocol (DCCP), referred to as DCCP-UDP. referred to as DCCP-UDP. This encapsulation allows DCCP to be
This encapsulation allows DCCP to be carried through the current carried through the current generation of Network Address Translation
generation of Network Address Translation (NAT) middle boxes without (NAT) middle boxes without modification of those middle boxes.
modification of those middle boxes.
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| dccp-port | Multiplexing MUST not be | M | NOT | | dccp-port | Multiplexing MUST NOT be | M | NOT |
| | performed due to potential | | RECOMMENDED | | | performed due to potential | | RECOMMENDED |
| | conflict between the port | | | | | conflict between the port | | |
| | used for DCCP | | | | | used for DCCP | | |
| | en/decapsulation and the RTP | | | | | en/decapsulation and the RTP | | |
| | | | | | | | | |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
RFC6773 Attribute Analysis 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 MAY 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 may or may not 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 [RFC5506] discusses benefits and issues that arise when allowing RTCP
Real-time Transport Protocol (RTCP) packets to be transmitted with packets to be transmitted with reduced size.
reduced size.
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| rtcp-rsize | Reduced size RTCP affects the | M | IDENTICAL | | rtcp-rsize | Reduced size RTCP affects the | M | IDENTICAL |
| | entire RTP session | | | | | entire RTP session | | |
| | | | | | | | | |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
RFC5506 Attribute Analysis 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 Session Initiation Protocol (SIP), to other protocols, such as the SIP, to coordinate MRCPv2 clients and
coordinate MRCPv2 clients and servers and manage sessions between servers, and manage session between them, and SDP to describe,
them, and the Session Description Protocol (SDP) to describe,
discover, and exchange capabilities. It also depends on SIP and SDP discover, and exchange capabilities. It also depends on SIP and SDP
to establish the media sessions and associated parameters between the to establish the media sessions and associated parameters between the
media source or sink and the media server. Once this is done, the media source or sink and the media server. Once this is done, the
MRCPv2 exchange operates over the control session established above, MRCPv2 exchange operates over the control session established above,
allowing the client to control the media processing resources on the allowing the client to control the media processing resources on the
speech resource server. [RFC6787] defines attributes for this speech resource server. [RFC6787] defines attributes for this
purpose. purpose.
+-----------+---------------+-------+--------------+ +-----------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
skipping to change at page 20, line 18 skipping to change at page 20, line 18
| resource | Not Impacted | M | NORMAL | | resource | Not Impacted | M | NORMAL |
| | | | | | | | | |
| channel | Not Impacted | M | NORMAL | | channel | Not Impacted | M | NORMAL |
| | | | | | | | | |
| cmid | Not Impacted | M | NORMAL | | cmid | Not Impacted | M | NORMAL |
| | | | | | | | | |
+-----------+---------------+-------+--------------+ +-----------+---------------+-------+--------------+
RFC6787 Attribute Analysis RFC6787 Attribute Analysis
5.12. RFC5245 - Interactive Connectivity Establishment (ICE) 5.12. RFC5245: ICE
[RFC5245] describes a protocol for Network Address Translator(NAT) [RFC5245] describes a protocol for NAT traversal for UDP-based
traversal for UDP-based multimedia sessions established with the multimedia sessions established with the offer/answer model. ICE
offer/answer model. This protocol is called Interactive Connectivity makes use of the Session Traversal Utilities for NAT (STUN) protocol
Establishment (ICE). ICE makes use of the Session Traversal and its extension, Traversal Using Relay NAT (TURN). ICE can be used
Utilities for NAT (STUN) protocol and its extension,Traversal Using by any protocol utilizing the offer/answer model, such as the SIP.
Relay NAT (TURN). ICE can be used by any protocol utilizing the
offer/answer model, such as the Session Initiation Protocol (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 |
skipping to change at page 21, line 47 skipping to change at page 21, line 47
| | MUST be the one that | | | | | MUST be the one that | | |
| | corresponds to the "m=" | | | | | corresponds to the "m=" | | |
| | line chosen for setting | | | | | line chosen for setting | | |
| | up the underlying | | | | | up the underlying | | |
| | transport flow | | | | | transport flow | | |
| | | | | | | | | |
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
RFC5245 Attribute Analysis 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 (the Real-Time Transport Protocol). It provides the feature of RTP. It provides the option to use a small number of
option to use a small number of small extensions in each RTP packet, small extensions in each RTP packet, where the universe of possible
where the universe of possible extensions is large and registration extensions is large and registration is de-centralized. The actual
is de-centralized. The actual extensions in use in a session are extensions in use in a session are signaled in the setup information
signaled in the setup information for that session. for that session.
+---------+-------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------+-------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
| extmap | Specific RTP extension document | B | SPECIAL | | extmap | Specific RTP extension document | B | SPECIAL |
| | MUST be referred | | | | | MUST be referred | | |
| | | | | | | | | |
+---------+-------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
RFC5285 Attribute Analysis 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. | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
RFC3605 Attribute Analysis 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 |
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
skipping to change at page 23, line 31 skipping to change at page 23, line 31
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
RFC5576 Attribute Analysis 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 Session Description Protocol (SDP) signalling [RFC7273] specifies SDP signalling that identifies timestamp
that identifies timestamp reference clock sources and SDP signalling reference clock sources and SDP signalling that identifies the media
that identifies the media clock sources in a multimedia session. clock sources in a multimedia session.
+------------+---------------+-------+--------------+ +--------------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+---------------+-------+--------------+ +--------------------+---------------+-------+--------------+
| ts-refclk | Not Impacted | B | NORMAL | | ts-refclk | Not Impacted | B | NORMAL |
| | | | | | | | | |
| mediaclk | Not Impacted | B | NORMAL | | mediaclk | Not Impacted | B | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+--------------+ | ts-refclk:ntp | Not Impacted | B | NORMAL |
| | | | |
| ts-refclk:ptp | Not Impacted | B | NORMAL |
| | | | |
| ts-refclk:gps | Not Impacted | B | NORMAL |
| | | | |
| ts-refclk:gal | Not Impacted | B | NORMAL |
| | | | |
| ts-refclk:glonass | Not Impacted | B | NORMAL |
| | | | |
| ts-refclk:local | Not Impacted | B | NORMAL |
| | | | |
| ts-refclk:private | Not Impacted | B | NORMAL |
| | | | |
| mediaclk:sender | Not Impacted | B | NORMAL |
| | | | |
| mediaclk:direct | Not Impacted | B | NORMAL |
| | | | |
| mediaclk:IEEE1722 | Not Impacted | B | NORMAL |
| | | | |
+--------------------+---------------+-------+--------------+
RFC7273 Attribute Analysis RFC7273 Attribute Analysis
5.17. RFC6236 - Image Attributes in SDP 5.17. RFC6236: Image Attributes in SDP
[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 terminal to display video without the need to rescale the image,
image,something that may consume large amounts of memory and something that may consume large amounts of memory and processing
processing power. The document also helps to maintain an optimal power. The document also helps to maintain an optimal bitrate for
bitrate for video as only the image size that is desired by the video as only the image size that is desired by the receiver is
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-PT |
| | be same for a given | | | | | be same for a given | | |
| | codec configuration | | | | | codec configuration | | |
| | | | | | | | | |
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
RFC6236 Attribute Analysis 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 the Session redundant media streams and the duplication delay in SDP.
Description Protocol.
+--------------------+---------------+-------+--------------+ +--------------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+--------------------+---------------+-------+--------------+ +--------------------+---------------+-------+--------------+
| duplication-delay | Not Impacted | B | NORMAL | | duplication-delay | Not Impacted | B | NORMAL |
| | | | | | | | | |
+--------------------+---------------+-------+--------------+ +--------------------+---------------+-------+--------------+
RFC7197 Attribute Analysis RFC7197 Attribute Analysis
5.19. RFC7266 - RTCP XR Blocks for MOS Metric Reporting 5.19. RFC7266: RTCP XR Blocks for MOS Metric Reporting
[RFC7266] defines an RTP Control Protocol (RTCP) Extended Report (XR) [RFC7266] defines an RTCP Extended Report (XR) Block including two
Block including two new segment types and associated Session new segment types and associated SDP parameters that allow the
Description Protocol (SDP) parameters that allow the reporting of reporting of mean opinion score (MOS) Metrics for use in a range of
mean opinion score (MOS) Metrics for use in a range of RTP RTP applications.
applications.
+-------------+---------------+-------+--------------+ +-------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-------------+---------------+-------+--------------+ +-------------+---------------+-------+--------------+
| calgextmap | Not Impacted | B | NORMAL | | calgextmap | Not Impacted | B | NORMAL |
| | | | | | | | | |
+-------------+---------------+-------+--------------+ +-------------+---------------+-------+--------------+
RFC7266 Attribute Analysis RFC7266 Attribute Analysis
5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions 5.20. RFC6285: Rapid Acquisition of Multicast RTP Sessions
[RFC6285] describes a method using the existing RTP and RTP Control [RFC6285] describes a method using the existing RTP and RTCP
Protocol (RTCP) machinery that reduces the acquisition delay. In machinery that reduces the acquisition delay. In this method, an
this method, an auxiliary unicast RTP session carrying the Reference auxiliary unicast RTP session carrying the Reference Information to
Information to the receiver precedes or accompanies the multicast the receiver precedes or accompanies the multicast stream. This
stream. This unicast RTP flow can be transmitted at a faster than unicast RTP flow can be transmitted at a faster than natural bitrate
natural bitrate to further accelerate the acquisition. The to further accelerate the acquisition. The motivating use case for
motivating use case for this capability is multicast applications this capability is multicast applications that carry real-time
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 | NOT RECOMMENDED | | rams-updates | Not recommended | M | NOT RECOMMENDED |
| | | | | | | | | |
+---------------+-------------------+-------+------------------+ +---------------+-------------------+-------+------------------+
RFC6285 Attribute Analysis 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
framework uses the Session Initiation Protocol (SIP) to establish an framework uses SIP to establish an application-level control
application-level control mechanism between application servers and mechanism between application servers and associated external servers
associated external servers such as media servers. such as media servers.
+---------+---------------+-------+--------------+ +---------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+---------+---------------+-------+--------------+ +---------+---------------+-------+--------------+
| cfw-id | Not Impacted | M | NORMAL | | cfw-id | Not Impacted | M | NORMAL |
| | | | | | | | | |
+---------+---------------+-------+--------------+ +---------+---------------+-------+--------------+
RFC6230 Attribute Analysis RFC6230 Attribute Analysis
5.22. RFC6364 - SDP Elements for FEC Framework 5.22. RFC6364: SDP Elements for FEC Framework
[RFC6364] specifies the use of the Session Description Protocol (SDP) [RFC6364] specifies the use of SDP to describe the parameters
to describe the parameters required to signal the Forward Error required to signal the Forward Error Correction (FEC) Framework
Correction (FEC) Framework Configuration Information between the Configuration Information between the sender(s) and receiver(s).
sender(s) and receiver(s). This document also provides examples that This document also provides examples that show the semantics for
show the semantics for grouping multiple source and repair flows grouping multiple source and repair flows together for the
together for the applications that simultaneously use multiple applications that simultaneously use multiple instances of the FEC
instances of the FEC Framework. Framework.
+------------------+-----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------------+-----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| fec-source-flow | Specific FEC scheme | M | SPECIAL | | fec-source-flow | Specific FEC scheme | M | SPECIAL |
| | document needs to be | | | | | document needs to be | | |
| | referred | | | | | referred | | |
| | | | | | | | | |
| fec-repair-flow | Specific FEC scheme | M | SPECIAL | | fec-repair-flow | Specific FEC scheme | M | SPECIAL |
skipping to change at page 26, line 27 skipping to change at page 27, line 25
| | referred | | | | | referred | | |
| | | | | | | | | |
| repair-window | Specific FEC scheme | M | SPECIAL | | repair-window | Specific FEC scheme | M | SPECIAL |
| | document needs to be | | | | | document needs to be | | |
| | referred | | | | | referred | | |
| | | | | | | | | |
+------------------+-----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
RFC6364 Attribute Analysis RFC6364 Attribute Analysis
5.23. RFC4796 - Content Attribute 5.23. RFC4796: Content Attribute
[RFC4796] defines a new Session Description Protocol (SDP) media- [RFC4796] defines a new SDP media-level attribute, 'content'. The
level attribute, 'content'. The 'content' attribute defines the 'content' attribute defines the content of the media stream to a more
content of the media stream to a more detailed level than the media detailed level than the media description line. The sender of an SDP
description line. The sender of an SDP session description can session description can attach the 'content' attribute to one or more
attach the 'content' attribute to one or more media streams. The media streams. The receiving application can then treat each media
receiving application can then treat each media stream differently stream differently (e.g., show it on a big or small screen) based on
(e.g., show it on a big or small screen) based on its content. its content.
+----------+---------------+-------+--------------+ +----------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+----------+---------------+-------+--------------+ +----------+---------------+-------+--------------+
| content | Not Impacted | M | NORMAL | | content | Not Impacted | M | NORMAL |
| | | | | | | | | |
+----------+---------------+-------+--------------+ +----------+---------------+-------+--------------+
RFC4796 Attribute Analysis RFC4796 Attribute Analysis
5.24. RFC3407 - SDP Simple Capability Declaration 5.24. RFC3407: SDP Simple Capability Declaration
[RFC3407] defines a set of Session Description Protocol (SDP) [RFC3407] defines a set of SDP attributes that enables SDP to provide
attributes that enables SDP to provide a minimal and backwards a minimal and backwards compatible capability declaration mechanism.
compatible capability declaration mechanism.
+----------+------------------------+-------+--------------+ +----------+------------------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+----------+------------------------+-------+--------------+ +----------+------------------------+-------+--------------+
| sqn | Not Impacted | B | NORMAL | | sqn | Not Impacted | B | NORMAL |
| | | | | | | | | |
| cdsc | Not Impacted. | B | NORMAL | | cdsc | Not Impacted. | B | NORMAL |
| | | | | | | | | |
| cpar | Refer to Section 14 | B | INHERIT | | cpar | Refer to Section 14 | B | INHERIT |
| | | | | | | | | |
skipping to change at page 27, line 27 skipping to change at page 28, line 27
| | | | | | | | | |
+----------+------------------------+-------+--------------+ +----------+------------------------+-------+--------------+
RFC3407 Attribute Analysis RFC3407 Attribute Analysis
NOTE: Since the attributes (a=cparmin and a=cparmax) define minimum NOTE: Since the attributes (a=cparmin and a=cparmax) define minimum
and maximum numerical values associated with the attributes described and maximum numerical values associated with the attributes described
in a=cpar, it is recommended to consult the document defining the in a=cpar, it is recommended to consult the document defining the
attribute. attribute.
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 Category | | Name | Notes | Level | Mux Category |
+------------------+-------------------------+-------+--------------+ +------------------+-------------------------+-------+--------------+
| portmapping-req | Not recommended, if | M | NOT | | portmapping-req | Not recommended, if | M | NOT |
| | port mapping is | | RECOMMENDED | | | port mapping is | | RECOMMENDED |
| | required by the | | | | | required by the | | |
| | application | | | | | application | | |
| | | | | | | | | |
+------------------+-------------------------+-------+--------------+ +------------------+-------------------------+-------+--------------+
RFC6284 Attribute Analysis 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
communication in networks where such middle boxes are deployed. This communication in networks where such middle boxes are deployed. This
document also defines a Session Description Protocol (SDP) attribute, document also defines a SDP attribute, 'msrp-cema', that MSRP
'msrp-cema', that MSRP endpoints use to indicate support of the CEMA endpoints use to indicate support of the CEMA extension.
extension.
+------------+-----------------------+-------+--------------+ +------------+-----------------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+-----------------------+-------+--------------+ +------------+-----------------------+-------+--------------+
| msrp-cema | Refer to notes below | M | TBD | | msrp-cema | Refer to notes below | M | TBD |
| | | | | | | | | |
+------------+-----------------------+-------+--------------+ +------------+-----------------------+-------+--------------+
RFC6714 Attribute Analysis RFC6714 Attribute Analysis
NOTE: As per section 9.1 of [I-D.ietf-mmusic-sdp-bundle-negotiation], NOTE: As per section 9.1 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 MUST be categories assignments for the attributes in this section MUST be
revisited. revisited.
5.27. RFC4583 - SDP Format for BFCP Streams 5.27. RFC4583: SDP Format for BFCP Streams
[RFC4583] document specifies how to describe Binary Floor Control [RFC4583] document specifies how to describe Binary Floor Control
Protocol (BFCP) streams in Session Description Protocol (SDP) Protocol (BFCP) streams in SDP descriptions. User agents using the
descriptions. User agents using the offer/answer model to establish offer/answer model to establish BFCP streams use this format in their
BFCP streams use this format in their offers and answers. offers and answers.
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| floorctrl | The attribute MUST be repeated | M | IDENTICAL | | floorctrl | The attribute MUST be repeated | M | IDENTICAL |
| | across all the multiplexed "m=" | | | | | across all the multiplexed "m=" | | |
| | lines | | | | | lines | | |
| | | | | | | | | |
| confid | Not Impacted | M | NORMAL | | confid | Not Impacted | M | NORMAL |
| | | | | | | | | |
| userid | Not Impacted | M | NORMAL | | userid | Not Impacted | M | NORMAL |
| | | | | | | | | |
| floorid | The floorid MUST be globally | M | NORMAL | | floorid | The floorid MUST be globally | M | NORMAL |
| | unique | | | | | unique | | |
| | | | | | | | | |
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
RFC4583 Attribute Analysis RFC4583 Attribute Analysis
5.28. RFC5547 - SDP Offer/Answer for File Transfer 5.28. RFC5547: SDP Offer/Answer for File Transfer
[RFC5547] provides a mechanism to negotiate the transfer of one or [RFC5547] provides a mechanism to negotiate the transfer of one or
more files between two endpoints by using the Session Description more files between two endpoints by using the SDP offer/answer model
Protocol (SDP) offer/answer model specified in [RFC3264]. specified in [RFC3264].
+-------------------+-----------------------+-------+--------------+ +-------------------+-----------------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-------------------+-----------------------+-------+--------------+ +-------------------+-----------------------+-------+--------------+
| file-selector | Refer to notes below | M | TBD | | file-selector | Refer to notes below | M | TBD |
| | | | | | | | | |
| file-transfer-id | Refer to notes below | M | TBD | | file-transfer-id | Refer to notes below | M | TBD |
| | | | | | | | | |
| file-disposition | Refer to notes below | M | TBD | | file-disposition | Refer to notes below | M | TBD |
| | | | | | | | | |
skipping to change at page 29, line 37 skipping to change at page 30, line 37
RFC5547 Attribute Analysis RFC5547 Attribute Analysis
NOTE: As per section 9.1 of [I-D.ietf-mmusic-sdp-bundle-negotiation], NOTE: As per section 9.1 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 attributes in this section MUST be categories assignments for attributes in this section MUST be
revisited. revisited.
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 VoIP, Real-time Text, and Video over IP performance metrics. advanced Voice over IP (VoIP), Real-time Text, and Video over IP
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-PT |
| loopback | value MUST be | | | | loopback | value MUST be | | |
| | same for a | | | | | same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
skipping to change at page 30, line 28 skipping to change at page 31, line 28
| | 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 |
| | | | | | | | | |
+---------------------+-----------------+-------+-------------------+ +---------------------+-----------------+-------+-------------------+
RFC6849 Analysis RFC6849 Analysis
5.30. RFC5760 - RTCP with Unicast Feedback 5.30. RFC5760: RTCP with Unicast Feedback
[RFC5760] specifies an extension to the Real-time Transport Control [RFC5760] specifies an extension to RTCP to use unicast feedback to a
Protocol (RTCP) to use unicast feedback to a multicast sender. The multicast sender. The proposed extension is useful for single-source
proposed extension is useful for single-source multicast sessions multicast sessions such as Source-Specific Multicast (SSM)
such as Source-Specific Multicast (SSM) communication where the communication where the traditional model of many-to-many group
traditional model of many-to-many group communication is either not communication is either not available or not desired.
available or not desired.
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| rtcp-unicast | The attribute MUST be | M | IDENTICAL | | rtcp-unicast | The attribute MUST be | M | IDENTICAL |
| | reported across all "m=" | | | | | reported across all "m=" | | |
| | lines multiplexed | | | | | lines multiplexed | | |
| | | | | | | | | |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
RFC5760 Attribute Analysis RFC5760 Attribute Analysis
5.31. RFC3611 - RTCP XR 5.31. RFC3611: RTCP XR
[RFC3611] defines the Extended Report (XR) packet type for the RTP [RFC3611] defines the Extended Report (XR) packet type for RTCP, and
Control Protocol (RTCP), and defines how the use of XR packets can be defines how the use of XR packets can be signaled by an application
signaled by an application if it employs the Session Description if it employs the Session Description Protocol (SDP).
Protocol (SDP).
+----------+---------------+-------+--------------+ +----------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+----------+---------------+-------+--------------+ +----------+---------------+-------+--------------+
| rtcp-xr | Not Impacted | B | NORMAL | | rtcp-xr | Not Impacted | B | NORMAL |
| | | | | | | | | |
+----------+---------------+-------+--------------+ +----------+---------------+-------+--------------+
RFC3611 Attribute Analysis RFC3611 Attribute Analysis
5.32. RFC5939 - SDP Capability Negotiation 5.32. RFC5939: SDP Capability Negotiation
[RFC5939] defines a general SDP Capability Negotiation framework. It [RFC5939] defines a general SDP Capability Negotiation framework. It
also specifies how to provide attributes and transport protocols as also specifies how to provide attributes and transport protocols as
capabilities and negotiate them using the framework. Extensions for capabilities and negotiate them using the framework. Extensions for
other types of capabilities (e.g., media types and media formats) may other types of capabilities (e.g., media types and media formats) may
be provided in other documents. be provided in other documents.
+---------+-----------------------+-------+--------------+ +---------+-----------------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+---------+-----------------------+-------+--------------+ +---------+-----------------------+-------+--------------+
skipping to change at page 32, line 5 skipping to change at page 32, line 43
| acap | Refer to Section 14 | B | INHERIT | | acap | Refer to Section 14 | B | INHERIT |
| | | | | | | | | |
| tcap | Refer to Section 14 | B | INHERIT | | tcap | Refer to Section 14 | B | INHERIT |
| | | | | | | | | |
| cap-v0 | Not Impacted | B | NORMAL | | cap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
+---------+-----------------------+-------+--------------+ +---------+-----------------------+-------+--------------+
RFC5939 Attribute Analysis RFC5939 Attribute Analysis
5.33. RFC6871- SDP Media Capabilities Negotiation 5.33. RFC6871: SDP Media Capabilities Negotiation
Session Description Protocol (SDP) capability negotiation provides a SDP capability negotiation provides a general framework for
general framework for indicating and negotiating capabilities in SDP. indicating and negotiating capabilities in SDP. The base framework
The base framework defines only capabilities for negotiating defines only capabilities for negotiating transport protocols and
transport protocols and attributes. [RFC6871] extends the framework attributes. [RFC6871] extends the framework by defining media
by defining media capabilities that can be used to negotiate media capabilities that can be used to negotiate media types and their
types and their associated parameters. associated parameters.
+---------+-----------------------+-------+-------------------+ +---------+-----------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+---------+-----------------------+-------+-------------------+ +---------+-----------------------+-------+-------------------+
| rmcap | Refer to Section 14 | B | IDENTICAL-PER-PT | | rmcap | Refer to Section 14 | B | IDENTICAL-PER-PT |
| | | | | | | | | |
| omcap | Not Impacted | B | NORMAL | | omcap | Not Impacted | B | NORMAL |
| | | | | | | | | |
| mfcap | Refer to Section 14 | B | IDENTICAL-PER-PT | | mfcap | Refer to Section 14 | B | IDENTICAL-PER-PT |
| | | | | | | | | |
skipping to change at page 32, line 43 skipping to change at page 33, line 34
RFC6871 - Attribute Analysis RFC6871 - Attribute Analysis
NOTE: The "sescap" attribute is NOT RECOMMENDED for use with NOTE: The "sescap" attribute is NOT RECOMMENDED for use with
multiplexing. The reason is that it requires the use of unique multiplexing. The reason is that it requires the use of unique
configuration numbers across the entire SDP (per [RFC6871]) as configuration numbers across the entire SDP (per [RFC6871]) as
opposed to within a media description only (per [RFC5939]). As opposed to within a media description only (per [RFC5939]). As
described in Section 14, the use of identical configuration numbers described in Section 14, the use of identical configuration numbers
between multiplexed (bundled) media descriptions is the default way between multiplexed (bundled) media descriptions is the default way
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 |
skipping to change at page 33, line 28 skipping to change at page 34, line 28
| 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 |
| | | | | | | | | |
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
RFC7006 - Attribute Analysis 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 Session Description Protocol [RFC4567] defines general extensions for SDP and Real Time Streaming
(SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as Protocol (RTSP) to carry messages, as specified by a key management
specified by a key management protocol, in order to secure the media. protocol, in order to secure the media. These extensions are
These extensions are presented as a framework, to be used by one or presented as a framework, to be used by one or more key management
more key management protocols. As such, their use is meaningful only protocols. As such, their use is meaningful only when complemented
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-mgmt | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the "m=" | | | | | 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 | | |
| | | | | | | | | |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
RFC4567 Attribute Analysis 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 the Session Description Protocol (SDP). It defines a new SDP using SDP. It defines a new SDP protocol identifier, 'TCP/TLS'. It
protocol identifier, 'TCP/TLS'. It also defines the syntax and also defines the syntax and semantics for an SDP 'fingerprint'
semantics for an SDP 'fingerprint' attribute that identifies the attribute that identifies the certificate that will be presented for
certificate that will be presented for the TLS session. This the TLS session. This mechanism allows media transport over TLS
mechanism allows media transport over TLS connections to be connections to be established securely, so long as the integrity of
established securely, so long as the integrity of session session descriptions is assured.
descriptions is assured.
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
| fingerprint | fingerprint value from the | B | TRANSPORT | | fingerprint | fingerprint value from the | B | TRANSPORT |
| | "m=" line defining the | | | | | "m=" line defining the | | |
| | underlying transport is | | | | | underlying transport is | | |
| | chosen | | | | | chosen | | |
| | | | | | | | | |
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
RFC4572 Attribute Analysis RFC4572 Attribute Analysis
5.37. RFC4570 - SDP Source Filters 5.37. RFC4570: SDP Source Filters
[RFC4570] describes how to adapt the Session Description Protocol [RFC4570] describes how to adapt SDP to express one or more source
(SDP) to express one or more source addresses as a source filter for addresses as a source filter for one or more destination "connection"
one or more destination "connection" addresses. It defines the addresses. It defines the syntax and semantics for an SDP "source-
syntax and semantics for an SDP "source-filter" attribute that may filter" attribute that may reference either IPv4 or IPv6 address(es)
reference either IPv4 or IPv6 address(es) as either an inclusive or as either an inclusive or exclusive source list for either multicast
exclusive source list for either multicast or unicast destinations. or unicast destinations. In particular, an inclusive source-filter
In particular, an inclusive source-filter can be used to specify a can be used to specify a Source-Specific Multicast (SSM) session.
Source-Specific Multicast (SSM) session.
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| source-filter | The attribute MUST be | B | IDENTICAL | | source-filter | The attribute MUST be | B | IDENTICAL |
| | repeated across all "m=" | | | | | repeated across all "m=" | | |
| | lines multiplexed | | | | | lines multiplexed | | |
| | | | | | | | | |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
RFC4570 Attribute Analysis RFC4570 Attribute Analysis
5.38. RFC6128 - RTCP Port for Multicast Sessions 5.38. RFC6128: RTCP Port for Multicast Sessions
The Session Description Protocol (SDP) has an attribute that allows SDP has an attribute that allows RTP applications to specify an
RTP applications to specify an address and a port associated with the address and a port associated with the RTCP traffic. In RTP-based
RTP Control Protocol (RTCP) traffic. In RTP-based source-specific source-specific multicast (SSM) sessions, the same attribute is used
multicast (SSM) sessions, the same attribute is used to designate the to designate the address and the RTCP port of the Feedback Target in
address and the RTCP port of the Feedback Target in the SDP the SDP description. However, the RTCP port associated with the SSM
description. However, the RTCP port associated with the SSM session session itself cannot be specified by the same attribute to avoid
itself cannot be specified by the same attribute to avoid ambiguity, ambiguity, and thus, is required to be derived from the "m=" line of
and thus, is required to be derived from the "m=" line of the media the media description. Deriving the RTCP port from the "m=" line
description. Deriving the RTCP port from the "m=" line imposes an imposes an unnecessary restriction. [RFC6128] removes this
unnecessary restriction. [RFC6128] removes this restriction by restriction by introducing a new SDP attribute.
introducing a new SDP attribute.
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
| multicast-rtcp | Multicast RTCP port MUST | B | IDENTICAL | | multicast-rtcp | Multicast RTCP port MUST | B | IDENTICAL |
| | be identical across all | | | | | be identical across all | | |
| | the "m=" lines | | | | | the "m=" lines | | |
| | | | | | | | | |
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
RFC6128 Attribute Analysis 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 Secure Real-time Transport Protocol (SRTP) sessions for Voice unicast SRTP sessions for (VoIP applications.
over IP (VoIP) applications.
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| zrtp-hash | zrtp-hash attribute MUST be the | M | TRANSPORT | | zrtp-hash | zrtp-hash attribute MUST be the | M | TRANSPORT |
| | one that corresponds to the | | | | | one that corresponds to the | | |
| | "m=" line chosen for setting up | | | | | "m=" line chosen for setting up | | |
| | the underlying transport flow | | | | | the underlying transport flow | | |
| | | | | | | | | |
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
RFC6189 Attribute Analysis 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 the [RFC4145] describes how to express media transport over TCP using
Session Description Protocol (SDP). It defines the SDP 'TCP' SDP. It defines the SDP 'TCP' protocol identifier, the SDP 'setup'
protocol identifier, the SDP 'setup' attribute, which describes the attribute, which describes the connection setup procedure, and the
connection setup procedure, and the SDP 'connection' attribute, which SDP 'connection' attribute, which handles connection reestablishment.
handles connection reestablishment.
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| setup | The attribute MUST be | B | IDENTICAL | | setup | The attribute MUST be | B | IDENTICAL |
| | identical across all "m=" | | | | | identical across all "m=" | | |
| | lines | | | | | lines | | |
| | | | | | | | | |
| connection | Thee attribute MUST be | B | IDENTICAL | | connection | Thee attribute MUST be | B | IDENTICAL |
| | identical across all "m=" | | | | | identical across all "m=" | | |
| | lines | | | | | lines | | |
| | | | | | | | | |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
RFC4145 Attribute Analysis 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 chosen for setting up the | | | | | line chosen for setting up the | | |
| | underlying transport flow | | | | | underlying transport flow | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
RFC6947 Attribute Analysis 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 the Session Description Protocol (SDP) offer/answer model for using SDP offer/answer model for establishing audio and video
for establishing audio and video media streams over circuit-switched media streams over circuit-switched bearers in the Public 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-correlation:callerid | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| cs-correlation:uuie | Refer to notes | M | TBD | | cs-correlation:uuie | Refer to notes | M | TBD |
| | below | | | | | below | | |
skipping to change at page 37, line 36 skipping to change at page 38, line 36
| | below | | | | | below | | |
| | | | | | | | | |
+--------------------------+-------------------+-------+------------+ +--------------------------+-------------------+-------+------------+
RFC7195 Attribute Analysis 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
MUST be revisited. MUST be revisited.
5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP) 5.43. RFC7272: IDMS Using the RTP Control Protocol (RTCP)
[RFC7272] defines a new RTP Control Protocol (RTCP) Packet Type and [RFC7272] defines a new RTCP Packet Type and an RTCP Extended Report
an RTCP Extended Report (XR) Block Type to be used for achieving (XR) Block Type to be used for achieving Inter-Destination Media
Inter-Destination Media Synchronization (IDMS). Synchronization (IDMS).
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| rtcp-idms | Not Impacted | M | NORMAL | | rtcp-idms | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
RFC7272 Attribute Analysis RFC7272 Attribute Analysis
5.44. RFC5159 - OMA BCAST SDP Attributes 5.44. RFC5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP
Attributes
[RFC5159] provides descriptions of Session Description Protocol (SDP) [RFC5159] provides descriptions of SDP attributes used by the Open
attributes used by the Open Mobile Alliance's Broadcast Service and Mobile Alliance's Broadcast Service and Content Protection
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 | | |
| | | | | | | | | |
+---------------------+-----------------------+-------+-------------+ +---------------------+-----------------------+-------+-------------+
RFC5159 Attribute Analysis 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 the Session Description Protocol extends the protocol identifier of SDP so that it can negotiate use
(SDP) so that it can negotiate use of the Internet Key Exchange of the Internet Key Exchange Protocol (IKE) for media sessions in the
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 | Attribute MUST be | B | IDENTICAL | | ike-setup | Attribute MUST be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
| | "m=" lines | | | | | "m=" lines | | |
| | | | | | | | | |
| psk-fingerprint | Attribute MUST be | B | IDENTICAL | | psk-fingerprint | Attribute MUST be | B | IDENTICAL |
skipping to change at page 39, line 33 skipping to change at page 40, line 33
| | "m=" lines | | | | | "m=" lines | | |
| | | | | | | | | |
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
RFC6193 Attribute Analysis RFC6193 Attribute Analysis
NOTE: With the above SDP constraints, a session multiplexed with NOTE: With the above SDP constraints, a session multiplexed with
multiple "m=" lines will use only one IPSec association for all of multiple "m=" lines will use only one IPSec association for all of
the "m=" lines. the "m=" lines.
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 Category | | Name | Notes | Level | Mux Category |
+----------+---------------------------------+-------+--------------+ +----------+---------------------------------+-------+--------------+
skipping to change at page 40, line 29 skipping to change at page 41, line 29
| | | | | | | | | |
+----------+---------------------------------+-------+--------------+ +----------+---------------------------------+-------+--------------+
RFC2326 Attribute Analysis 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
The Packet-switched Streaming Service (PSS) and the Multimedia The Packet-switched Streaming Service (PSS) and the Multimedia
Broadcast/Multicast Service (MBMS) defined by 3GPP use the Session Broadcast/Multicast Service (MBMS) defined by 3GPP use SDP and RTSP
Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)
with some extensions. [RFC6064] provides information about these with some extensions. [RFC6064] provides information about these
extensions and registers the RTSP and SDP extensions with IANA. extensions and registers the RTSP and SDP extensions with IANA.
+-------------------------------+------------+-------+--------------+ +-------------------------------+------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-------------------------------+------------+-------+--------------+ +-------------------------------+------------+-------+--------------+
| X-predecbufsize | Refer to | M | NOT | | X-predecbufsize | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
skipping to change at page 41, line 35 skipping to change at page 42, line 34
| | below | | | | | below | | |
| | | | | | | | | |
| alt | Refer to | M | NOT | | alt | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| alt-default-id | Refer to | M | NOT | | alt-default-id | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| alt-group | Refer to | M | NOT | | alt-group | Refer to | S | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-Adaptation-Support | Refer to | M | NOT | | 3GPP-Adaptation-Support | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-Asset-Information | Refer to | B | NOT | | 3GPP-Asset-Information | Refer to | B | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
skipping to change at page 43, line 16 skipping to change at page 44, line 15
| | | | | | | | | |
+-------------------------------+------------+-------+--------------+ +-------------------------------+------------+-------+--------------+
RFC6064 Attribute Analysis 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 the Session Description [RFC3108] describes conventions for using SDP described for
Protocol (SDP) described for controlling ATM Bearer Connections, and controlling ATM Bearer Connections, and any associated ATM Adaptation
any associated ATM Adaptation Layer (AAL). Layer (AAL).
+------------------------+------------------+-------+---------------+ +------------------------+------------------+-------+---------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------------------+------------------+-------+---------------+ +------------------------+------------------+-------+---------------+
| aalType | Refer to notes | B | NOT | | aalType | Refer to notes | B | NOT |
| | below | | RECOMMENDED | | | below | | RECOMMENDED |
| eecid | Refer to notes | B | NOT | | eecid | Refer to notes | B | NOT |
| | below | | RECOMMENDED | | | below | | RECOMMENDED |
| capability | Refer to notes | B | NOT | | capability | Refer to notes | B | NOT |
| | below | | RECOMMENDED | | | below | | RECOMMENDED |
skipping to change at page 45, line 20 skipping to change at page 46, line 19
| | below | | RECOMMENDED | | | below | | RECOMMENDED |
| uiLayer1_Prot | Refer to notes | B | NOT | | uiLayer1_Prot | Refer to notes | B | NOT |
| | below | | RECOMMENDED | | | below | | RECOMMENDED |
| chain | Refer to notes | B | NOT | | chain | Refer to notes | B | NOT |
| | below | | RECOMMENDED | | | below | | RECOMMENDED |
| | | | | | | | | |
+------------------------+------------------+-------+---------------+ +------------------------+------------------+-------+---------------+
RFC3108 Attribute Analysis RFC3108 Attribute Analysis
NOTE: RFC3108 describes conventions for using the Session Description NOTE: RFC3108 describes conventions for using SDP for characterizing
Protocol (SDP) for characterizing ATM bearer connections using an ATM bearer connections using an AAL1, AAL2 or AAL5 adaptation layers.
AAL1, AAL2 or AAL5 adaptation layers. For AAL1, AAL2 and AAL5, For AAL1, AAL2 and AAL5, bearer connections can be used to transport
bearer connections can be used to transport single media streams. In single media streams. In addition, for AAL1 and AAL2, multiple media
addition, for AAL1 and AAL2, multiple media streams MAY be streams can be multiplexed into a bearer connection. For all
multiplexed into a bearer connection. For all adaptation types adaptation types (AAL1, AAL2 and AAL5), bearer connections can be
(AAL1, AAL2 and AAL5), bearer connections MAY be bundled into a bundled into a single media group. In all cases addressed by
single media group. In all cases addressed by RFC3108, a real-time RFC3108, a real-time media stream (voice, video, voiceband data,
media stream (voice, video, voiceband data, pseudo-wire and others) pseudo-wire, and others) or a multiplex of media streams is mapped
or a multiplex of media streams is mapped directly into an ATM directly into an ATM connection. RFC3108 does not address cases
connection. RFC3108 does not address cases where ATM serves as a where ATM serves as a low-level transport pipe for IP packets which
low-level transport pipe for IP packets which in turn MAY carry one in turn can carry one or more real-time (e.g. VoIP) media sessions
or more real-time (e.g. VoIP) media sessions with a life-cycle with a life-cycle different from that of the underlying ATM
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 | M | NORMAL |
| | IP Multimedia Subsystem | | | | | IP Multimedia Subsystem | | |
| | | | | | | | | |
| 3gpp_MaxRecvSDUSize | Usage defined for the | M | NORMAL | | 3gpp_MaxRecvSDUSize | Usage defined for the | M | NORMAL |
| | IP Multimedia Subsystem | | | | | IP Multimedia Subsystem | | |
| | | | | | | | | |
skipping to change at page 48, line 48 skipping to change at page 49, line 48
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 | S | TBD | | T38FaxVersion | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38MaxBitRate | Refer to notes | S | TBD | | T38MaxBitRate | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxFillBitRemoval | Refer to notes | S | TBD | | T38FaxFillBitRemoval | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxTranscodingMMR | Refer to notes | S | TBD | | T38FaxTranscodingMMR | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxTranscodingJBIG | Refer to notes | S | TBD | | T38FaxTranscodingJBIG | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxRateManagement | Refer to notes | S | TBD | | T38FaxRateManagement | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxMaxBuffer | Refer to notes | S | TBD | | T38FaxMaxBuffer | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxMaxDatagram | Refer to notes | S | TBD | | T38FaxMaxDatagram | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxUdpEC | Refer to notes | S | TBD | | T38FaxUdpEC | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxMaxIFP | Refer to notes | S | TBD | | T38FaxMaxIFP | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxUdpECDepth | Refer to notes | S | TBD | | T38FaxUdpECDepth | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38FaxUdpFECMaxSpan | Refer to notes | S | TBD | | T38FaxUdpFECMaxSpan | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38ModemType | Refer to notes | S | TBD | | T38ModemType | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
| T38VendorInfo | Refer to notes | S | TBD | | T38VendorInfo | Refer to notes | M | TBD |
| | below | | | | | below | | |
| | | | | | | | | |
+------------------------+--------------------+-------+-------------+ +------------------------+--------------------+-------+-------------+
ITU T.38 Attribute Analysis ITU T.38 Attribute Analysis
NOTE: As per section 9.1 of [I-D.ietf-mmusic-sdp-bundle-negotiation], NOTE: As per section 9.1 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
MUST be revisited. MUST be revisited.
5.55. ITU-T Q.1970 5.55. ITU-T Q.1970
[Q.1970] defines BICC IP bearer control protocol. [Q.1970] defines Bearer Independent Call Control (BICC) IP bearer
control protocol.
+--------+---------------------------------------+-------+----------+ +--------+---------------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------+---------------------------------------+-------+----------+ +--------+---------------------------------------+-------+----------+
| ipbcp | ipbcp version identifies type of | S | SPECIAL | | ipbcp | ipbcp version identifies type of IP | S | SPECIAL |
| | IPBCP message used in BICC (ITU-T | | | | | bearer control protocol (IPBCP) | | |
| | Q.1901) environment which are limited | | | | | message used in BICC (ITU-T Q.1901) | | |
| | to single media payload. Pertinent | | | | | environment which are limited to | | |
| | ITU.T specifications needs to be | | | | | single media payload. Pertinent ITU-T | | |
| | referred while multiplexing | | | | | specifications needs to be referred | | |
| | while multiplexing | | |
| | | | | | | | | |
+--------+---------------------------------------+-------+----------+ +--------+---------------------------------------+-------+----------+
ITU-T Q.1970 Attribute Analysis 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 | B | SPECIAL |
| | signaling the inclusion of H.248 | | | | | signaling the inclusion of H.248 | | |
| | extension packages to a gateway | | | | | extension packages to a gateway | | |
| | via the local and remote | | | | | via the local and remote | | |
| | descriptors. The attribute itself | | | | | descriptors. The attribute itself | | |
| | is unaffected by multiplexing, but | | | | | is unaffected by multiplexing, but | | |
| | the packaged referenced in a | | | | | the packaged referenced in a | | |
| | specific use of the attribute may | | | | | specific use of the attribute can | | |
| | be impacted. Further analysis of | | | | | be impacted. Further analysis of | | |
| | each package is needed to | | | | | each package is needed 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 | | | | | signal the use of multiplexing to | | |
| | a gateway | | | | | a gateway | | |
| | | | | | | | | |
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
ITU-T H.248.15 Attribute Analysis 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 |
skipping to change at page 53, line 5 skipping to change at page 54, line 5
| | | | | | | | | |
+----------+----------------------+-------+------------------+ +----------+----------------------+-------+------------------+
Historical Attribute Analysis Historical Attribute Analysis
6. bwtype Attribute Analysis 6. bwtype Attribute Analysis
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: Session Description Protocol 6.1. RFC4566: SDP
[RFC4566] defines the Session Description Protocol (SDP) that is [RFC4566] defines SDP that is intended for describing multimedia
intended for describing multimedia sessions for the purposes of sessions for the purposes of session announcement, session
session announcement, session invitation, and other forms of invitation, and other forms of multimedia session initiation.
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 | | |
| | | | | | | | | |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
RFC4566 bwtype Analysis 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 the Session Description Protocol [RFC3556] defines an extension to SDP to specify two additional
(SDP) to specify two additional modifiers for the bandwidth modifiers for the bandwidth attribute. These modifiers may be used
attribute. These modifiers may be used to specify the bandwidth to specify the bandwidth allowed for RTCP packets in a RTP session.
allowed for RTP Control Protocol (RTCP) packets in a Real-time
Transport Protocol (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 | | |
skipping to change at page 54, line 5 skipping to change at page 55, line 5
| 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 | | |
| | | | | | | | | |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
RFC3556 bwtype Analysis RFC3556 bwtype Analysis
6.3. RFC3890 - Bandwidth Modifier for SDP 6.3. RFC3890: Bandwidth Modifier for SDP
[RFC3890] defines a Session Description Protocol (SDP) Transport [RFC3890] defines SDP Transport Independent Application Specific
Independent Application Specific Maximum (TIAS) bandwidth modifier Maximum (TIAS) bandwidth modifier that does not include transport
that does not include transport overhead; instead an additional overhead; instead an additional packet rate attribute is defined.
packet rate attribute is defined. The transport independent bit-rate The transport independent bit-rate value together with the maximum
value together with the maximum packet rate can then be used to packet rate can then be used to calculate the real bit-rate over the
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 | B | SPECIAL |
| | clearly defined Offer/Answer | | | | | clearly defined Offer/Answer | | |
| | usage. | | | | | usage. | | |
| | | | | | | | | |
| maxprate | The usage of TIAS and maxprate | B | SPECIAL | | maxprate | The usage of TIAS and maxprate | B | SPECIAL |
skipping to change at page 54, line 43 skipping to change at page 55, line 43
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
and adding the individual values is a more appropriate usage. and adding the individual values is a more appropriate usage.
7. rtcp-fb Attribute Analysis 7. rtcp-fb Attribute Analysis
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 rpsi | The attribute value MUST | M | IDENTICAL-PER-PT |
skipping to change at page 55, line 46 skipping to change at page 56, line 46
| | multiplexed | | | | | multiplexed | | |
| | | | | | | | | |
| trr-int | The attribute value MUST | M | IDENTICAL-PER-PT | | trr-int | The attribute value MUST | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
RFC4585 Attribute Analysis 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-PT |
| | same for a given codec | | | | | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+------+--------------------------------+-------+-------------------+ +------+--------------------------------+-------+-------------------+
RFC5104 Attribute Analysis RFC5104 Attribute Analysis
7.3. RFC6285 - Unicast-Based RAMS 7.3. RFC6285: Unicast-Based Rapid Acquisition of Multicast RTP Sessions
(RAMS)
[RFC6285] describes a method using the existing RTP and RTP Control [RFC6285] describes a method using the existing RTP and RTCP
Protocol (RTCP) machinery that reduces the acquisition delay. In machinery that reduces the acquisition delay. In this method, an
this method, an auxiliary unicast RTP session carrying the Reference auxiliary unicast RTP session carrying the Reference Information to
Information to the receiver precedes or accompanies the multicast the receiver precedes or accompanies the multicast stream. This
stream. This unicast RTP flow can be transmitted at a faster than unicast RTP flow can be transmitted at a faster than natural bitrate
natural bitrate to further accelerate the acquisition. The to further accelerate the acquisition. The motivating use case for
motivating use case for this capability is multicast applications this capability is multicast applications that carry real-time
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-PT |
| rai | same for a given codec | | | | rai | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
RFC6285 Attribute Analysis 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 Real-time Transport Protocol (RTP) running over UDP, used with the RTP running over UDP, using the RTCP as a feedback
using the RTP Control Protocol (RTCP) as a feedback mechanism. It mechanism. It defines a new RTCP Extended Report (XR) block for
defines a new RTCP Extended Report (XR) block for periodic ECN periodic ECN feedback, a new RTCP transport feedback message for
feedback, a new RTCP transport feedback message for timely reporting timely reporting of congestion events, and a STUN extension used in
of congestion events, and a Session Traversal Utilities for NAT the optional initialization method using ICE.
(STUN) extension used in the optional initialization method using
Interactive Connectivity Establishment (ICE).
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| ecn-capable-rtp | ECN markup are enabled at | M | IDENTICAL | | ecn-capable-rtp | ECN markup are enabled at | M | IDENTICAL |
| | the RTP session level | | | | | the RTP session level | | |
| | | | | | | | | |
| nack ecn | This attribute enables | M | IDENTICAL | | nack ecn | This attribute enables | M | IDENTICAL |
| | ECN at the RTP session | | | | | ECN at the RTP session | | |
| | level | | | | | level | | |
| | | | | | | | | |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
RFC6679 Attribute Analysis RFC6679 Attribute Analysis
7.5. RFC6642 - Third-Party Loss Report 7.5. RFC6642: Third-Party Loss Report
In a large RTP session using the RTP Control Protocol (RTCP) feedback In a large RTP session using the RTCP feedback mechanism defined in
mechanism defined in [RFC4585], a feedback target may experience [RFC4585], a feedback target may experience transient overload if
transient overload if some event causes a large number of receivers some event causes a large number of receivers to send feedback at
to send feedback at once. This overload is usually avoided by once. This overload is usually avoided by ensuring that feedback
ensuring that feedback reports are forwarded to all receivers, reports are forwarded to all receivers, allowing them to avoid
allowing them to avoid sending duplicate feedback reports. However, sending duplicate feedback reports. However, there are cases where
there are cases where it is not recommended to forward feedback it is not recommended to forward feedback reports, and this may allow
reports, and this may allow feedback implosion. [RFC6642] memo feedback implosion. [RFC6642] memo discusses these cases and defines
discusses these cases and defines a new RTCP Third-Party Loss Report a new RTCP Third-Party Loss Report that can be used to inform
that can be used to inform receivers that the feedback target is receivers that the feedback target is aware of some loss event,
aware of some loss event, allowing them to suppress feedback. allowing them to suppress feedback. Associated SDP signaling is also
Associated Session Description Protocol (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-PT |
| tllei | same for a given codec | | | | tllei | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack | The attribute value MUST be | M | IDENTICAL-PER-PT | | nack | The attribute value MUST be | M | IDENTICAL-PER-PT |
| pslei | same for a given codec | | | | pslei | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
RFC6642 Attribute Analysis 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 |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
skipping to change at page 58, line 40 skipping to change at page 59, line 40
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
RFC5104 Attribute Analysis 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 the Session [RFC5888] defines a framework to group "m" lines in SDP for different
Description Protocol (SDP) for different purposes. purposes.
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| group:LS | Not Impacted | S | NORMAL | | group:LS | Not Impacted | S | NORMAL |
| | | | | | | | | |
| group:FID | Not Impacted | S | NORMAL | | group:FID | Not Impacted | S | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
RFC5888 Attribute Analysis RFC5888 Attribute Analysis
8.2. RFC3524 - Mapping Media Streams to Resource Reservation Flows 8.2. RFC3524: Mapping Media Streams to Resource Reservation Flows
[RFC3524] defines an extension to the Session Description Protocol [RFC3524] defines an extension to the SDP grouping framework. It
(SDP) grouping framework. It allows requesting a group of media allows requesting a group of media streams to be mapped into a single
streams to be mapped into a single resource reservation flow. The resource reservation flow. The SDP syntax needed is defined, as well
SDP syntax needed is defined, as well as a new "semantics" attribute as a new "semantics" attribute called Single Reservation Flow (SRF).
called Single Reservation Flow (SRF).
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| group:SRF | Not Impacted | S | NORMAL | | group:SRF | Not Impacted | S | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
RFC3524 Attribute Analysis RFC3524 Attribute Analysis
8.3. RFC4091 - ANAT Semantics 8.3. RFC4091: ANAT Semantics
[RFC4091] defines the Alternative Network Address Types (ANAT) [RFC4091] defines ANAT semantics for the SDP grouping framework. The
semantics for the Session Description Protocol (SDP) grouping ANAT semantics allow alternative types of network addresses to
framework. The ANAT semantics allow alternative types of network establish a particular media stream.
addresses to establish a particular media stream.
+-------------+---------------------------+-------+-----------------+ +-------------+---------------------------+-------+-----------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-------------+---------------------------+-------+-----------------+ +-------------+---------------------------+-------+-----------------+
| group:ANAT | ANAT semantics is | S | NOT RECOMMENDED | | group:ANAT | ANAT semantics is | S | NOT RECOMMENDED |
| | obseleted | | | | | obseleted | | |
| | | | | | | | | |
+-------------+---------------------------+-------+-----------------+ +-------------+---------------------------+-------+-----------------+
RFC4091 Attribute Analysis RFC4091 Attribute Analysis
8.4. RFC5956 - FEC Grouping Semantics in SDP 8.4. RFC5956: FEC Grouping Semantics in SDP
[RFC5956] defines the semantics for grouping the associated source [RFC5956] defines the semantics for grouping the associated source
and FEC-based (Forward Error Correction) repair flows in the Session and FEC-based (Forward Error Correction) repair flows in SDP. The
Description Protocol (SDP). The semantics defined in the document semantics defined in the document are to be used with the SDP
are to be used with the SDP Grouping Framework (RFC 5888). These Grouping Framework [RFC5888]. These semantics allow the description
semantics allow the description of grouping relationships between the of grouping relationships between the source and repair flows when
source and repair flows when one or more source and/or repair flows one or more source and/or repair flows are associated in the same
are associated in the same group, and they provide support for group, and they provide support for additive repair flows. SSRC-
additive repair flows. SSRC-level (Synchronization Source) grouping level (Synchronization Source) grouping semantics are also defined in
semantics are also defined in this document for Real-time Transport this document for RTP streams using SSRC multiplexing.
Protocol (RTP) streams using SSRC multiplexing.
+---------------+---------------+-------+--------------+ +---------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+---------------+---------------+-------+--------------+ +---------------+---------------+-------+--------------+
| group:FEC-FR | Not Impacted | S | NORMAL | | group:FEC-FR | Not Impacted | S | NORMAL |
| | | | | | | | | |
+---------------+---------------+-------+--------------+ +---------------+---------------+-------+--------------+
RFC5956 Attribute Analysis 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 the Session Description Protocol (SDP). This is required, for in SDP. This is required, for example, if media data is separated
example, if media data is separated and transported in different and transported in different network streams as a result of the use
network streams as a result of the use of a layered or multiple of a layered or multiple descriptive media coding process.
descriptive media coding process.
+--------+------------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+--------+------------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
| depend | The attribute value MUST be | M | IDENTICAL-PER-PT | | group:DDP | Not Impacted | S | NORMAL |
| lay | same for a given codec | | | | | | | |
| | configuration | | | | depend lay | The attribute value MUST | M | IDENTICAL-PER-PT |
| | | | | | | be same for a given | | |
| depend | The attribute value MUST be | M | IDENTICAL-PER-PT | | | codec configuration | | |
| mdc | same for a given codec | | | | | | | |
| | configuration | | | | depend mdc | The attribute value MUST | M | IDENTICAL-PER-PT |
| | | | | | | be same for a given | | |
+--------+------------------------------+-------+-------------------+ | | codec configuration | | |
| | | | |
+------------+--------------------------+-------+-------------------+
RFC5583 Attribute Analysis 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 the [RFC7104] defines the semantics for grouping redundant streams in
Session Description Protocol (SDP). The semantics defined in this SDP, The semantics defined in this document are to be used with the
document are to be used with the SDP Grouping Framework. Grouping SDP Grouping Framework. Grouping semantics at the SSRC)level are
semantics at the Synchronization Source (SSRC) level are also defined also defined in this document for RTP streams using SSRC
in this document for RTP streams using SSRC multiplexing. multiplexing.
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| group:DUP | Not Impacted | S | NORMAL | | group:DUP | Not Impacted | S | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
RFC7104 Attribute Analysis RFC7104 Attribute Analysis
9. ssrc-group Attribute Analysis 9. ssrc-group Attribute Analysis
This section analyzes "ssrc-group" semantics. This section analyzes "ssrc-group" semantics.
9.1. RFC5576 - Source-Specific SDP Attributes 9.1. 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-group:FID | Not Impacted | SR | NORMAL | | ssrc-group:FID | Not Impacted | SR | NORMAL |
| | | | | | | | | |
| ssrc-group:FEC | Not Impacted | SR | NORMAL | | ssrc-group:FEC | Not Impacted | SR | NORMAL |
| | | | | | | | | |
| ssrc-groupFEC-FR | Not Impacted | SR | NORMAL | | ssrc-group:FEC-FR | Not Impacted | SR | NORMAL |
| | | | | | | | | |
+-------------------+---------------+-------+--------------+ +--------------------+---------------+-------+--------------+
RFC5576 Attribute Analysis RFC5576 Attribute Analysis
9.2. RFC7104 - Duplication Grouping Semantics in the SDP 9.2. RFC7104: Duplication Grouping Semantics in the SDP
[RFC7104] defines the semantics for grouping redundant streams in the [RFC7104] defines the semantics for grouping redundant streams in
Session Description Protocol (SDP). The semantics defined in this SDP. The semantics defined in this document are to be used with the
document are to be used with the SDP Grouping Framework. Grouping SDP Grouping Framework. Grouping semantics at the Synchronization
semantics at the Synchronization Source (SSRC) level are also defined Source (SSRC) level are also defined in this document for RTP streams
in this document for RTP streams using SSRC multiplexing. using SSRC multiplexing.
+-----------------+---------------+-------+--------------+ +-----------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-----------------+---------------+-------+--------------+ +-----------------+---------------+-------+--------------+
| ssrc-group:DUP | Not Impacted | SR | NORMAL | | ssrc-group:DUP | Not Impacted | SR | NORMAL |
| | | | | | | | | |
+-----------------+---------------+-------+--------------+ +-----------------+---------------+-------+--------------+
RFC7104 Attribute Analysis RFC7104 Attribute Analysis
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
Session Description Protocol (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 | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
RFC5432 Attribute Analysis RFC5432 Attribute Analysis
NOTE: A single DSCP code point per flow being multiplexed doesn't NOTE: A single Differentiated Services Code Point (DSCP) code point
impact multiplexing since QOS mechanisms are signaled/scoped per per flow being multiplexed doesn't impact multiplexing since QOS
flow. For scenarios that involve having different DSCP code points mechanisms are signaled/scoped per flow. For scenarios that involve
for packets being transmitted over the same 5-tuple, issues as having different DSCP code points for packets being transmitted over
discussed in [I.D-draft-ietf-dart-dscp-rtp] need to be taken into the same 5-tuple, issues as discussed in [I-D.ietf-dart-dscp-rtp]
consideration. need to be taken into consideration.
11. k= Attribute Analysis 11. k= Attribute Analysis
11.1. RFC4566: SDP
11.1. RFC4566 SDP: Session Description Protocol [RFC4566] defines SDP that is intended for describing multimedia
sessions for the purposes of session announcement, session
[RFC4566] defines the Session Description Protocol (SDP) that is invitation, and other forms of multimedia session initiation.
intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of
multimedia session initiation.
+------+------------------------------------+-------+---------------+ +------+------------------------------------+-------+---------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------+------------------------------------+-------+---------------+ +------+------------------------------------+-------+---------------+
| k= | It is NOT recommended to use this | S | NOT | | k= | It is NOT recommended to use this | S | NOT |
| | attribute | | RECOMMENDED | | | attribute | | RECOMMENDED |
| | | | | | | | | |
+------+------------------------------------+-------+---------------+ +------+------------------------------------+-------+---------------+
RFC4566 Attribute Analysis RFC4566 Attribute Analysis
12. content Attribute Analysis 12. content Attribute Analysis
12.1. RFC4796 12.1. RFC4796
[RFC4796] defines a new Session Description Protocol (SDP) media- [RFC4796] defines a new SDP media-level attribute, 'content'. The
level attribute, 'content'. The 'content' attribute defines the 'content' attribute defines the content of the media stream to a more
content of the media stream to a more detailed level than the media detailed level than the media description line. The sender of an SDP
description line. The sender of an SDP session description can session description can attach the 'content' attribute to one or more
attach the 'content' attribute to one or more media streams. The media streams. The receiving application can then treat each media
receiving application can then treat each media stream differently stream differently (e.g., show it on a big or small screen) based on
(e.g., show it on a big or small screen) based on its content. its content.
+------------------+---------------+-------+--------------+ +------------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------------+---------------+-------+--------------+ +------------------+---------------+-------+--------------+
| content:slides | Not Impacted | M | NORMAL | | content:slides | Not Impacted | M | NORMAL |
| | | | | | | | | |
| content:speaker | Not Impacted | M | NORMAL | | content:speaker | Not Impacted | M | NORMAL |
| | | | | | | | | |
| content:main | Not Impacted | M | NORMAL | | content:main | Not Impacted | M | NORMAL |
| | | | | | | | | |
| content:sl | Not Impacted | M | NORMAL | | content:sl | Not Impacted | M | NORMAL |
| | | | | | | | | |
| content:alt | Not Impacted | M | NORMAL | | content:alt | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------------+---------------+-------+--------------+ +------------------+---------------+-------+--------------+
RFC4796 Attribute Analysis RFC4796 Attribute Analysis
13. Payload Formats 13. Payload Formats
13.1. RFC5109 - RTP Payload Format for Generic FEC 13.1. RFC5109: RTP Payload Format for Generic FEC
[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.
skipping to change at page 64, line 47 skipping to change at page 65, line 47
+---------------------+----------------------+-------+--------------+ +---------------------+----------------------+-------+--------------+
RFC5109 Payload Format Analysis 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,
and media format related capabilities in the SDP. and media format related capabilities in the SDP.
The behavior of such attributes under multiplexing is in turn defined The behavior of such attributes under multiplexing is in turn defined
by the multiplexing behavior of the attributes they encapsulate which by the multiplexing behavior of the attributes they encapsulate which
are made known once the Offer/Answer negotiation process is are made known once the Offer/Answer negotiation process is
completed. completed.
14.1. RFC3407 - cpar Attribute Analysis 14.1. RFC3407: cpar Attribute Analysis
[RFC3407] capability parameter attribute (a=cpar) encapsulates b= [RFC3407] capability parameter attribute (a=cpar) encapsulates b=
(bandwidth) or an a= attribute. For bandwidth attribute (bandwidth) or an a= attribute. For bandwidth attribute
encapsulation, the category SUM is inherited. For the case of a= encapsulation, the category SUM is inherited. For the case of a=
attribute, the category corresponding to the SDP attribute being attribute, the category corresponding to the SDP attribute being
encapsulated is inherited. encapsulated is inherited.
v=0 v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s= s=
skipping to change at page 66, line 22 skipping to change at page 67, line 22
identifies the potential configuration that was negotiated for identifies the potential configuration that was negotiated for
use. Use of an actual configuration does not require any further use. Use of an actual configuration does not require any further
negotiation. negotiation.
o A negotiation process that takes the current actual and the set of o A negotiation process that takes the current actual and the set of
potential configurations (combinations of capabilities) as input potential configurations (combinations of capabilities) as input
and provides the negotiated actual configurations as output. In and provides the negotiated actual configurations as output. In
[RFC5939] the negotiation process is done independently for each [RFC5939] the negotiation process is done independently for each
media description. media description.
14.2.1. Recommendation - Procedures for Potential Configuration Pairing 14.2.1. Recommendation: Procedures for Potential Configuration Pairing
This section provides recommendations for entities generating and This section provides recommendations for entities generating and
processing SDP under the generic capability negotiation framework as processing SDP under the generic capability negotiation framework as
defined in [RFC5939] under the context of media stream multiplexing. defined in [RFC5939] under the context of media stream multiplexing.
These recommendations are provided for the purposes of enabling the These recommendations are provided for the purposes of enabling the
Offerer to make sure that the generated potential configurations Offerer to make sure that the generated potential configurations
between the multiplexed streams can (easily) be negotiated to be between the multiplexed streams can (easily) be negotiated to be
consistent between those streams. In particular, the procedures aim consistent between those streams. In particular, the procedures aim
to simplify Answerer's procedure to choose potential configurations to simplify Answerer's procedure to choose potential configurations
skipping to change at page 69, line 16 skipping to change at page 70, line 16
[RFC6871] extends capability negotiation framework described in [RFC6871] extends capability negotiation framework described in
[RFC5939] by defining media capabilities that can be used to indicate [RFC5939] by defining media capabilities that can be used to indicate
and negotiate media types and their associated format parameters. It and negotiate media types and their associated format parameters. It
also allows indication of latent configurations and session also allows indication of latent configurations and session
capabilities. capabilities.
14.3.1. Recommendation: Dealing with Payload Type Numbers 14.3.1. Recommendation: Dealing with Payload Type Numbers
[RFC6871] defines a new payload type ("pt") parameter to be used with [RFC6871] defines a new payload type ("pt") parameter to be used with
the potential, actual and latent configuration parameters. The the potential, actual, and latent configuration parameters. The
parameter associates RTP payload type numbers with the referenced parameter associates RTP payload type numbers with the referenced
RTP-based media format capabilities ("a=rmcap") defined in [RFC6871] RTP-based media format capabilities ("a=rmcap") defined in [RFC6871]
and is appropriate only when the transport protocol uses RTP. This and is appropriate only when the transport protocol uses RTP. This
means that the same payload type number can be assigned as part of means that the same payload type number can be assigned as part of
potential or actual configurations in different media descriptions in potential or actual configurations in different media descriptions in
a bundle. There are rules for the usage of identical Payload Type a bundle. There are rules for the usage of identical Payload Type
values across multiplexed "m=" lines as described in values across multiplexed "m=" lines as described in
[I-D.ietf-mmusic-sdp-bundle-negotiation], which MUST be followed here [I-D.ietf-mmusic-sdp-bundle-negotiation], which MUST be followed here
as well. As described in Section 14.2.1, the use of identical as well. As described in Section 14.2.1, the use of identical
configuration numbers for compatible configurations in different configuration numbers for compatible configurations in different
skipping to change at page 70, line 42 skipping to change at page 71, line 42
In the example above, the potential configuration number "1" is In the example above, the potential configuration number "1" is
repeated when referring to media and media format capability used for repeated when referring to media and media format capability used for
the Payload Type 96. This implies that both the media capability 2 the Payload Type 96. This implies that both the media capability 2
and 4 along with their media format capabilities MUST refer to the and 4 along with their media format capabilities MUST refer to the
same codec configuration, as per the definition of IDENTICAL-PER-PT. same codec configuration, as per the definition of IDENTICAL-PER-PT.
14.3.2. Recommendation: Dealing with Latent Configurations 14.3.2. Recommendation: Dealing with Latent Configurations
[RFC6871] adds the notion of a latent configurations, which provides [RFC6871] adds the notion of a latent configurations, which provides
configuration information that may be used to guide a subsequent configuration information that MAY be used to guide a subsequent
offer/exchange, e.g. by adding another media stream or use offer/exchange, e.g. by adding another media stream or use
alternative codec combinations not currently offered. Latent alternative codec combinations not currently offered. Latent
configurations have configuration numbers which cannot overlap with configurations have configuration numbers which cannot overlap with
the potential configuration numbers [RFC6871]. Supported the potential configuration numbers [RFC6871]. Supported
combinations of potential and latent configurations are indicated by combinations of potential and latent configurations are indicated by
use of the "a=sescap" attribute, however use of this attribute is NOT use of the "a=sescap" attribute, however use of this attribute is NOT
RECOMMENDED with multiplexed media, since it requires the use of RECOMMENDED with multiplexed media, since it requires the use of
unique configuration numbers across the SDP. Taken together, this unique configuration numbers across the SDP. Taken together, this
means there is no well-defined way to indicate supported combinations means there is no well-defined way to indicate supported combinations
of latent configurations, or combinations of latent and potential of latent configurations, or combinations of latent and potential
skipping to change at page 72, line 4 skipping to change at page 73, line 4
| NORMAL | RFCXXXX | | NORMAL | RFCXXXX |
| NOT RECOMMENDED | RFCXXXX | | NOT RECOMMENDED | RFCXXXX |
| IDENTICAL | RFCXXXX | | IDENTICAL | RFCXXXX |
| TRANSPORT | RFCXXXX | | TRANSPORT | RFCXXXX |
| SUM | RFCXXXX | | SUM | RFCXXXX |
| INHERIT | RFCXXXX | | INHERIT | RFCXXXX |
| IDENTICAL-PER-PT | RFCXXXX | | IDENTICAL-PER-PT | RFCXXXX |
| SPECIAL | RFCXXXX | | SPECIAL | RFCXXXX |
| TBD | RFCXXXX | | TBD | RFCXXXX |
+-------------------------+-----------+ +-------------------------+-----------+
Further entries may be registered on a first-come first-serve basis. Further entries can be registered on a first-come first-serve basis.
Each registration needs to indicate the multiplexing category value Each registration needs to indicate the multiplexing category value
to be added to the "Multiplexing Categories" subregistry as defined to be added to the "Multiplexing Categories" subregistry as defined
in this section. in this section.
Such a registration MUST also indicate the applicability of the newly Such a registration MUST also indicate the applicability of the newly
defined multiplexing category value to various subregistries defined defined multiplexing category value to various subregistries defined
at "Session Description Protocol (SDP) Parameters". at "Session Description Protocol (SDP) Parameters".
The general registration procedures of [RFC4566] apply. The general registration procedures of [RFC4566] apply.
skipping to change at page 73, line 32 skipping to change at page 74, line 32
| ice-options | NORMAL | | ice-options | NORMAL |
| bcastversion | NORMAL | | bcastversion | NORMAL |
| 3GPP-Integrity-Key | NOT RECOMMENDED | | 3GPP-Integrity-Key | NOT RECOMMENDED |
| 3GPP-SDP-Auth | NOT RECOMMENDED | | 3GPP-SDP-Auth | NOT RECOMMENDED |
| alt-group | NOT RECOMMENDED | | alt-group | NOT RECOMMENDED |
| PSCid | NORMAL | | PSCid | NORMAL |
| bc_service | NORMAL | | bc_service | NORMAL |
| bc_program | NORMAL | | bc_program | NORMAL |
| bc_service_package | NORMAL | | bc_service_package | NORMAL |
| sescap | NOT RECOMMENDED | | sescap | NOT RECOMMENDED |
| rtsp-ice-d-m | NOT RECOMMENDED | | rtsp-ice-d-m | TBD |
+---------------------+------------------+ +---------------------+------------------+
15.2.3. Table: att-field (both session and media level) 15.2.3. Table: att-field (both session and media level)
The following values are to be added to the "att-field (both session The following values are to be added to the "att-field (both session
and media level)" subregistry in the "Session Description Protocol and media level)" subregistry in the "Session Description Protocol
(SDP) Parameters" registry. The references should be updated to (SDP) Parameters" registry. The references should be updated to
point at this RFC as well as the previous references. point at this RFC as well as the previous references.
NOTE: The attributes from draft-ietf-rmt-flute-sdp ('flute-tsi', NOTE: The attributes from draft-ietf-rmt-flute-sdp ('flute-tsi',
skipping to change at page 74, line 30 skipping to change at page 75, line 30
| fingerprint | TRANSPORT | | fingerprint | TRANSPORT |
| flute-tsi | TBD | | flute-tsi | TBD |
| flute-ch | TBD | | flute-ch | TBD |
| FEC-declaration | TBD | | FEC-declaration | TBD |
| FEC-OTI-extension | TBD | | FEC-OTI-extension | TBD |
| content-desc | TBD | | content-desc | TBD |
| ice-pwd | TRANSPORT | | ice-pwd | TRANSPORT |
| ice-ufrag | TRANSPORT | | ice-ufrag | TRANSPORT |
| stkmstream | NORMAL | | stkmstream | NORMAL |
| extmap | SPECIAL | | extmap | SPECIAL |
| qos-mech-send | NORMAL | | qos-mech-send | TRANSOPORT |
| qos-mech-recv | NORMAL | | qos-mech-recv | TRANSPORT |
| csup | NORMAL | | csup | NORMAL |
| creq | NORMAL | | creq | NORMAL |
| acap | INHERIT | | acap | INHERIT |
| tcap | INHERIT | | tcap | INHERIT |
| 3GPP-QoE-Metrics | NOT RECOMMENDED | | 3GPP-QoE-Metrics | NOT RECOMMENDED |
| 3GPP-Asset-Information | NOT RECOMMENDED | | 3GPP-Asset-Information | NOT RECOMMENDED |
| mbms-mode | NOT RECOMMENDED | | mbms-mode | NOT RECOMMENDED |
| mbms-repair | NOT RECOMMENDED | | mbms-repair | NOT RECOMMENDED |
| ike-setup | IDENTICAL | | ike-setup | IDENTICAL |
| psk-fingerprint | IDENTICAL | | psk-fingerprint | IDENTICAL |
skipping to change at page 76, line 46 skipping to change at page 77, line 46
| aal5sscop | NOT RECOMMENDED | | aal5sscop | NOT RECOMMENDED |
| atmmap | NOT RECOMMENDED | | atmmap | NOT RECOMMENDED |
| silenceSupp | NOT RECOMMENDED | | silenceSupp | NOT RECOMMENDED |
| ecan | NOT RECOMMENDED | | ecan | NOT RECOMMENDED |
| gc | NOT RECOMMENDED | | gc | NOT RECOMMENDED |
| profileDesc | NOT RECOMMENDED | | profileDesc | NOT RECOMMENDED |
| vsel | NOT RECOMMENDED | | vsel | NOT RECOMMENDED |
| dsel | NOT RECOMMENDED | | dsel | NOT RECOMMENDED |
| fsel | NOT RECOMMENDED | | fsel | NOT RECOMMENDED |
| onewaySel | NOT RECOMMENDED | | onewaySel | NOT RECOMMENDED |
| codecConfig | NOT RECOMMENDED | | codecconfig | NOT RECOMMENDED |
| isup_usi | NOT RECOMMENDED | | isup_usi | NOT RECOMMENDED |
| uiLayer1_Prot | NOT RECOMMENDED | | uiLayer1_Prot | NOT RECOMMENDED |
| chain | NOT RECOMMENDED | | chain | NOT RECOMMENDED |
| floorctrl | IDENTICAL | | floorctrl | IDENTICAL |
| confid | NORMAL | | confid | NORMAL |
| userid | NORMAL | | userid | NORMAL |
| floorid | NORMAL | | floorid | NORMAL |
| FEC | NORMAL | | FEC | NORMAL |
| accept-types | TBD | | accept-types | TBD |
| accept-wrapped-types | TBD | | accept-wrapped-types | TBD |
skipping to change at page 82, line 42 skipping to change at page 83, line 42
| nsis | TRANSPORT | | nsis | TRANSPORT |
+---------------+--------------+ +---------------+--------------+
15.2.16. Table: SDP Capability Negotiation Option Tags 15.2.16. Table: SDP Capability Negotiation Option Tags
The following values are to be added to the "SDP Capability The following values are to be added to the "SDP Capability
Negotiation Option Tags" subregistry in the "Session Description Negotiation Option Tags" subregistry in the "Session Description
Protocol (SDP) Parameters" registry. The references should be Protocol (SDP) Parameters" registry. The references should be
updated to point at this RFC as well as the previous references. updated to point at this RFC as well as the previous references.
+---------------+--------------+ +------------+--------------+
| QoS Mechanism | Mux Category | | Option Tag | Mux Category |
+---------------+--------------+ +------------+--------------+
| cap-v0 | NORMAL | | cap-v0 | NORMAL |
| med-v0 | NORMAL | | med-v0 | NORMAL |
| bcap-v0 | NORMAL | | bcap-v0 | NORMAL |
| ccap-v0 | NORMAL | | ccap-v0 | NORMAL |
| icap-v0 | NORMAL | | icap-v0 | NORMAL |
+---------------+--------------+ +------------+--------------+
15.2.17. Table: Timestamp Reference Clock Source Parameters 15.2.17. Table: Timestamp Reference Clock Source Parameters
The following values are to be added to the "Timestamp Reference The following values are to be added to the "Timestamp Reference
Clock Source Parameters" subregistry in the "Session Description Clock Source Parameters" subregistry in the "Session Description
Protocol (SDP) Parameters" registry. The references should be Protocol (SDP) Parameters" registry. The references should be
updated to point at this RFC as well as the previous references. updated to point at this RFC as well as the previous references.
+----------+--------------+ +----------+--------------+
| Name | Mux Category | | Name | Mux Category |
skipping to change at page 84, line 33 skipping to change at page 85, line 33
Ian Johansson(5.15), Saravanan Shanmugham(5.11), Paul E Jones(5.30), Ian Johansson(5.15), Saravanan Shanmugham(5.11), Paul E Jones(5.30),
Rajesh Kumar(5.48), Jonathan Lennox(5.36,5,15,9.1,11.1), Mo Rajesh Kumar(5.48), Jonathan Lennox(5.36,5,15,9.1,11.1), Mo
Zanaty(5.4,5.5,5.23,8.1,8.3,8.5,12.1), Christian Huitema (5.14), Qin Zanaty(5.4,5.5,5.23,8.1,8.3,8.5,12.1), Christian Huitema (5.14), Qin
Wu (5.47 PM-Dir review), Hans Stokking(5.43,5.16), Christian Groves Wu (5.47 PM-Dir review), Hans Stokking(5.43,5.16), Christian Groves
(5.48,5.55), Thomas Stach. (5.48,5.55), Thomas Stach.
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 from draft-ietf-mmusic-sdp-mux-attributes-06 - 08 Changes from draft-ietf-mmusic-sdp-mux-attributes-10
o Incorporated Comments from Bo Burman for publication request
Changes from draft-ietf-mmusic-sdp-mux-attributes-08 to draft-ietf-
mmusic-sdp-mux-attributes-10
o Minor nits and version update to advert expiration
Changes from draft-ietf-mmusic-sdp-mux-attributes-06 to draft-ietf-
mmusic-sdp-mux-attributes-08
o Assigned TBD category to all the attributes for whom there exists o Assigned TBD category to all the attributes for whom there exists
no specification on multiplexing behavior over the underlying no specification on multiplexing behavior over the underlying
transport protocol today. transport protocol today.
o Incorporated comments from Flemming and Ari (post last call) o Incorporated comments from Flemming and Ari (post last call)
Changes from draft-ietf-mmusic-sdp-mux-attributes-06 Changes from draft-ietf-mmusic-sdp-mux-attributes-06
o Incorporated last call review comments from Thomas Stach and Ari o Incorporated last call review comments from Thomas Stach and Ari
Keranen. Keranen.
o Fixed more nits to prep for the LastCall. o Fixed more nits to prep for the LastCall.
Changes from draft-ietf-mmusic-sdp-mux-attributes-05 Changes from draft-ietf-mmusic-sdp-mux-attributes-05
o Incorporated review comments from Christian Grooves and Ari o Incorporated review comments from Christian Grooves and Ari
Keranen. Keranen.
skipping to change at page 87, line 21 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-12 (work in progress), October 2014. negotiation-23 (work in progress), July 2015.
[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, July 2006. Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <http://www.rfc-editor.org/info/rfc4566>.
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-draft-ietf-dart-dscp-rtp] [I-D.ietf-dart-dscp-rtp]
Black, D. and P. Jones, "Differentiated Services Black, D. and P. Jones, "Differentiated Services
(DiffServ) and Real-time Communication", draft-ietf-dart- (DiffServ) and Real-time Communication", draft-ietf-dart-
dscp-rtp-10 (work in progress), September 2014. dscp-rtp-10 (work in progress), November 2014.
[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.",
<http://www.in2eps.com/etispan/ <http://www.etsi.org/deliver/
tk-etsi-tispan03-183-063.html>. etsi_ts/183000_183099/183063/02.01.00_60/
ts_183063v020100p.pdf>.
[R3GPPTS24.182] [R3GPPTS24.182]
"IP Multimedia Subsystem (IMS) Customized Alerting Tones "IP Multimedia Subsystem (IMS) Customized Alerting Tones
(CAT); Protocol specification", (CAT); Protocol specification",
<http://www.3gpp.org/ftp/Specs/html-info/24182.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24182.htm>.
[R3GPPTS24.183] [R3GPPTS24.183]
"IP Multimedia Subsystem (IMS) Customized Ringing Signal "IP Multimedia Subsystem (IMS) Customized Ringing Signal
(CRS); Protocol specification", (CRS); Protocol specification",
<http://www.3gpp.org/ftp/Specs/html-info/24183.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24183.htm>.
[R3GPPTS24.229] [R3GPPTS24.229]
"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", interaction", <http://www.3gpp.org/DynaReport/26114.htm>.
<http://www.in2eps.com/3g26/tk-3gpp-26-114.html>.
[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, April 1998. Streaming Protocol (RTSP)", RFC 2326, DOI 10.17487/
RFC2326, April 1998,
<http://www.rfc-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, May 2001. Connections", RFC 3108, DOI 10.17487/RFC3108, May 2001,
<http://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, June with Session Description Protocol (SDP)", RFC 3264, DOI
2002. 10.17487/RFC3264, June 2002,
<http://www.rfc-editor.org/info/rfc3264>.
[RFC3312] Camarillo, G., Marshall, W., 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, October 2002. Protocol (SIP)", RFC 3312, DOI 10.17487/RFC3312, October
2002, <http://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, October 2002. Capability Declaration", RFC 3407, DOI 10.17487/RFC3407,
October 2002, <http://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, April 2003. Resource Reservation Flows", RFC 3524, DOI 10.17487/
RFC3524, April 2003,
<http://www.rfc-editor.org/info/rfc3524>.
[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", RFC
3556, July 2003. 3556, DOI 10.17487/RFC3556, July 2003,
<http://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, October in Session Description Protocol (SDP)", RFC 3605, DOI
2003. 10.17487/RFC3605, October 2003,
<http://www.rfc-editor.org/info/rfc3605>.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,
Protocol Extended Reports (RTCP XR)", RFC 3611, November "RTP Control Protocol Extended Reports (RTCP XR)", RFC
2003. 3611, DOI 10.17487/RFC3611, November 2003,
<http://www.rfc-editor.org/info/rfc3611>.
[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)", RFC
3890, September 2004. 3890, DOI 10.17487/RFC3890, September 2004,
<http://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, June 2005. Protocol (SDP) Grouping Framework", RFC 4091, DOI
10.17487/RFC4091, June 2005,
<http://www.rfc-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, the Session Description Protocol (SDP)", RFC 4145, DOI
September 2005. 10.17487/RFC4145, September 2005,
<http://www.rfc-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, July 2006. Protocol (RTSP)", RFC 4567, DOI 10.17487/RFC4567, July
2006, <http://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, July 2006. Streams", RFC 4568, DOI 10.17487/RFC4568, July 2006,
<http://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, July 2006. (SDP) Source Filters", RFC 4570, DOI 10.17487/RFC4570,
July 2006, <http://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, July 2006. Description Protocol (SDP)", RFC 4572, DOI 10.17487/
RFC4572, July 2006,
<http://www.rfc-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, August 2006. Protocol (SDP) Label Attribute", RFC 4574, DOI 10.17487/
RFC4574, August 2006,
<http://www.rfc-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", RFC
4583, November 2006. 4583, DOI 10.17487/RFC4583, November 2006,
<http://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, July Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, DOI
2006. 10.17487/RFC4585, July 2006,
<http://www.rfc-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, February Protocol (SDP) Content Attribute", RFC 4796, DOI 10.17487/
2007. RFC4796, February 2007,
<http://www.rfc-editor.org/info/rfc4796>.
[RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message [RFC4975] Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed.,
Session Relay Protocol (MSRP)", RFC 4975, September 2007. "The Message Session Relay Protocol (MSRP)", RFC 4975, DOI
10.17487/RFC4975, September 2007,
<http://www.rfc-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, February 2008. with Feedback (AVPF)", RFC 5104, DOI 10.17487/RFC5104,
February 2008, <http://www.rfc-editor.org/info/rfc5104>.
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., Ed., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, December 2007. Correction", RFC 5109, DOI 10.17487/RFC5109, December
2007, <http://www.rfc-editor.org/info/rfc5109>.
[RFC5159] Dondeti, L. and A. Jerichow, "Session Description Protocol [RFC5159] Dondeti, L., Ed. and A. Jerichow, "Session Description
(SDP) Attributes for Open Mobile Alliance (OMA) Broadcast Protocol (SDP) Attributes for Open Mobile Alliance (OMA)
(BCAST) Service and Content Protection", RFC 5159, March Broadcast (BCAST) Service and Content Protection", RFC
2008. 5159, DOI 10.17487/RFC5159, March 2008,
<http://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, April Traversal for Offer/Answer Protocols", RFC 5245, DOI
2010. 10.17487/RFC5245, April 2010,
<http://www.rfc-editor.org/info/rfc5245>.
[RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP [RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP
Header Extensions", RFC 5285, July 2008. Header Extensions", RFC 5285, DOI 10.17487/RFC5285, July
2008, <http://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, March 2009. Description Protocol (SDP)", RFC 5432, DOI 10.17487/
RFC5432, March 2009,
<http://www.rfc-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, April 2009. and Consequences", RFC 5506, DOI 10.17487/RFC5506, April
2009, <http://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,
May 2009. DOI 10.17487/RFC5547, May 2009,
<http://www.rfc-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, June 2009. (SDP)", RFC 5576, DOI 10.17487/RFC5576, June 2009,
<http://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)", RFC
5583, July 2009. 5583, DOI 10.17487/RFC5583, July 2009,
<http://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, February 2010. Sessions with Unicast Feedback", RFC 5760, DOI 10.17487/
RFC5760, February 2010,
<http://www.rfc-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, April 2010. Control Packets on a Single Port", RFC 5761, DOI 10.17487/
RFC5761, April 2010,
<http://www.rfc-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, April 2010. Protocol (DCCP)", RFC 5762, DOI 10.17487/RFC5762, April
2010, <http://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, May 2010. Security (DTLS)", RFC 5763, DOI 10.17487/RFC5763, May
2010, <http://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, June 2010. Protocol (SDP) Grouping Framework", RFC 5888, DOI
10.17487/RFC5888, June 2010,
<http://www.rfc-editor.org/info/rfc5888>.
[RFC5939] Andreasen, F., "Session Description Protocol (SDP) [RFC5939] Andreasen, F., "Session Description Protocol (SDP)
Capability Negotiation", RFC 5939, September 2010. Capability Negotiation", RFC 5939, DOI 10.17487/RFC5939,
September 2010, <http://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, September the Session Description Protocol", RFC 5956, DOI 10.17487/
2010. RFC5956, September 2010,
<http://www.rfc-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, January Multimedia Broadcast/Multicast Service", RFC 6064, DOI
2011. 10.17487/RFC6064, January 2011,
<http://www.rfc-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, February Specific Multicast (SSM) Sessions", RFC 6128, DOI
2011. 10.17487/RFC6128, February 2011,
<http://www.rfc-editor.org/info/rfc6128>.
[RFC6189] Zimmermann, P., Johnston, A., and J. Callas, "ZRTP: Media [RFC6189] Zimmermann, P., Johnston, A., Ed., and J. Callas, "ZRTP:
Path Key Agreement for Unicast Secure RTP", RFC 6189, Media Path Key Agreement for Unicast Secure RTP", RFC
April 2011. 6189, DOI 10.17487/RFC6189, April 2011,
<http://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, April 2011. Description Protocol (SDP)", RFC 6193, DOI 10.17487/
RFC6193, April 2011,
<http://www.rfc-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, May 2011. Control Channel Framework", RFC 6230, DOI 10.17487/
RFC6230, May 2011,
<http://www.rfc-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)", RFC
6236, May 2011. 6236, DOI 10.17487/RFC6236, May 2011,
<http://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, between Unicast and Multicast RTP Sessions", RFC 6284, DOI
June 2011. 10.17487/RFC6284, June 2011,
<http://www.rfc-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, June 2011. Sessions", RFC 6285, DOI 10.17487/RFC6285, June 2011,
<http://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, Forward Error Correction (FEC) Framework", RFC 6364, DOI
October 2011. 10.17487/RFC6364, October 2011,
<http://www.rfc-editor.org/info/rfc6364>.
[RFC6642] Wu, Q., Xia, F., and R. Even, "RTP Control Protocol (RTCP) [RFC6642] Wu, Q., Ed., Xia, F., and R. Even, "RTP Control Protocol
Extension for a Third-Party Loss Report", RFC 6642, June (RTCP) Extension for a Third-Party Loss Report", RFC 6642,
2012. DOI 10.17487/RFC6642, June 2012,
<http://www.rfc-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, August 2012. for RTP over UDP", RFC 6679, DOI 10.17487/RFC6679, August
2012, <http://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, August 2012. Session Relay Protocol (MSRP)", RFC 6714, DOI 10.17487/
RFC6714, August 2012,
<http://www.rfc-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, November 2012. NAT Traversal", RFC 6773, DOI 10.17487/RFC6773, November
2012, <http://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, November 2012. Protocol Version 2 (MRCPv2)", RFC 6787, DOI 10.17487/
RFC6787, November 2012,
<http://www.rfc-editor.org/info/rfc6787>.
[RFC6849] Kaplan, H., 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, February 2013. Media Loopback", RFC 6849, DOI 10.17487/RFC6849, February
2013, <http://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, February 2013. Negotiation", RFC 6871, DOI 10.17487/RFC6871, February
2013, <http://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, May Alternate Connectivity (ALTC) Attribute", RFC 6947, DOI
2013. 10.17487/RFC6947, May 2013,
<http://www.rfc-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, September 2013. Description Protocol (SDP)", RFC 7006, DOI 10.17487/
RFC7006, September 2013,
<http://www.rfc-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,
January 2014. DOI 10.17487/RFC7104, January 2014,
<http://www.rfc-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, May Public Switched Telephone Network (PSTN)", RFC 7195, DOI
2014. 10.17487/RFC7195, May 2014,
<http://www.rfc-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,
April 2014. DOI 10.17487/RFC7197, April 2014,
<http://www.rfc-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, June Opinion Score (MOS) Metric Reporting", RFC 7266, DOI
2014. 10.17487/RFC7266, June 2014,
<http://www.rfc-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, June 2014. Control Protocol (RTCP)", RFC 7272, DOI 10.17487/RFC7272,
June 2014, <http://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, June Stokking, "RTP Clock Source Signalling", RFC 7273, DOI
2014. 10.17487/RFC7273, June 2014,
<http://www.rfc-editor.org/info/rfc7273>.
[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
 End of changes. 251 change blocks. 
682 lines changed or deleted 771 lines changed or added

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