draft-ietf-mmusic-sdp-mux-attributes-04.txt   draft-ietf-mmusic-sdp-mux-attributes-05.txt 
Network Working Group S. Nandakumar Network Working Group S. Nandakumar
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track October 24, 2014 Intended status: Standards Track November 26, 2014
Expires: April 27, 2015 Expires: May 30, 2015
A Framework for SDP Attributes when Multiplexing A Framework for SDP Attributes when Multiplexing
draft-ietf-mmusic-sdp-mux-attributes-04 draft-ietf-mmusic-sdp-mux-attributes-05
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. In the RTCWeb WG, there is a need to use a multimedia session. In the RTCWEB WG, there is a need to use a
single 5-tuple for sending and receiving media associated with single 5-tuple for sending and receiving media associated with
multiple media descriptions ("m=" lines). Such a requirement has multiple media descriptions ("m=" lines). Such a requirement has
raised concerns over the semantic implications of the SDP attributes raised concerns over the semantic implications of the SDP attributes
associated with the RTP Media Streams multiplexed over a single associated with the RTP Media Streams multiplexed over a single
underlying transport layer flow. underlying transport layer flow.
The scope of this specification is to provide a framework for The scope of this specification is to provide a framework for
analyzing the multiplexing characteristics of SDP attributes. This analyzing the multiplexing characteristics of SDP attributes. This
specification also categorizes the existing SDP attributes based on specification also categorizes the existing SDP attributes based on
the framework described herein. the framework described herein.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 April 27, 2015. This Internet-Draft will expire on May 30, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 42 skipping to change at page 2, line 42
4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 6 4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 6
4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7 4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7
4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 7 4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 7
4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8 4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8
4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 8 4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 8
4.5. Category: TRANSPORT . . . . . . . . . . . . . . . . . . . 9 4.5. Category: TRANSPORT . . . . . . . . . . . . . . . . . . . 9
4.6. Category: INHERIT . . . . . . . . . . . . . . . . . . . . 10 4.6. Category: INHERIT . . . . . . . . . . . . . . . . . . . . 10
4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 10 4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 10
4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 11 4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 11
4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 11 4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 11
5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 11 5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12
5.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 12 5.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 12
5.2. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 13 5.2. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 14
5.3. RFC5761 - Multiplexing RTP and RTCP . . . . . . . . . . . 14 5.3. RFC5761 - Multiplexing RTP and RTCP . . . . . . . . . . . 14
5.4. RFC3312 - Integration of Resource Management and (SIP) . 14 5.4. RFC3312 - Integration of Resource Management and (SIP) . 14
5.5. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 15 5.5. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 15
5.6. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 15 5.6. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 15
5.7. RFC4568 - SDP Security Descriptions . . . . . . . . . . . 16 5.7. RFC4568 - SDP Security Descriptions . . . . . . . . . . . 16
5.8. RFC5762 - RTP over DCCP . . . . . . . . . . . . . . . . . 16 5.8. RFC5762 - RTP over DCCP . . . . . . . . . . . . . . . . . 16
5.9. RFC6773 - DCCP-UDP Encapsulation . . . . . . . . . . . . 17 5.9. RFC6773 - DCCP-UDP Encapsulation . . . . . . . . . . . . 17
5.10. RFC5506 - Reduced-Size RTCP in RTP Profile . . . . . . . 18 5.10. RFC5506 - Reduced-Size RTCP in RTP Profile . . . . . . . 18
5.11. RFC6787 - Media Resource Control Protocol Version 2 . . . 18 5.11. RFC6787 - Media Resource Control Protocol Version 2 . . . 18
5.12. RFC5245 - Interactive Connectivity Establishment (ICE) . 19 5.12. RFC5245 - Interactive Connectivity Establishment (ICE) . 19
5.13. RFC5285 - RTP Header Extensions . . . . . . . . . . . . . 20 5.13. RFC5285 - RTP Header Extensions . . . . . . . . . . . . . 21
5.14. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 21 5.14. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 21
5.15. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 21 5.15. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 21
5.16. RFC7273 - RTP Clock Source Signalling . . . . . . . . . . 22 5.16. RFC7273 - RTP Clock Source Signalling . . . . . . . . . . 22
5.17. RFC6236 - Image Attributes in SDP . . . . . . . . . . . . 23 5.17. RFC6236 - Image Attributes in SDP . . . . . . . . . . . . 23
5.18. RFC7197 - Duplication Delay Attribute in SDP . . . . . . 23 5.18. RFC7197 - Duplication Delay Attribute in SDP . . . . . . 23
5.19. RFC7226 - RTCP XR Blocks for MOS Metric Reporting . . . 23 5.19. RFC7266 - RTCP XR Blocks for MOS Metric Reporting . . . 23
5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions . . 24 5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions . . 24
5.21. RFC6230 - Media Control Channel Framework . . . . . . . . 24 5.21. RFC6230 - Media Control Channel Framework . . . . . . . . 24
5.22. RFC6364 - SDP Elements for FEC Framework . . . . . . . . 25 5.22. RFC6364 - SDP Elements for FEC Framework . . . . . . . . 25
5.23. RFC4796 - Content Attribute . . . . . . . . . . . . . . . 25 5.23. RFC4796 - Content Attribute . . . . . . . . . . . . . . . 25
5.24. RFC3407 - SDP Simple Capability Declaration . . . . . . . 26 5.24. RFC3407 - SDP Simple Capability Declaration . . . . . . . 26
5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP 5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP
Sessions . . . . . . . . . . . . . . . . . . . . . . . . 26 Sessions . . . . . . . . . . . . . . . . . . . . . . . . 26
5.26. RFC6714 - MSRP-CEMA . . . . . . . . . . . . . . . . . . . 27 5.26. RFC6714 - MSRP-CEMA . . . . . . . . . . . . . . . . . . . 27
5.27. RFC4583 - SDP Format for BFCP Streams . . . . . . . . . . 27 5.27. RFC4583 - SDP Format for BFCP Streams . . . . . . . . . . 27
5.28. RFC5547 - SDP Offer/Answer for File Transfer . . . . . . 28 5.28. RFC5547 - SDP Offer/Answer for File Transfer . . . . . . 28
skipping to change at page 3, line 37 skipping to change at page 3, line 37
5.33. RFC6871- SDP Media Capabilities Negotiation . . . . . . . 30 5.33. RFC6871- SDP Media Capabilities Negotiation . . . . . . . 30
5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP . . 31 5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP . . 31
5.35. RFC4567 - Key Management Extensions for SDP and RTSP . . 32 5.35. RFC4567 - Key Management Extensions for SDP and RTSP . . 32
5.36. RFC4572 - Comedia over TLS in SDP . . . . . . . . . . . . 33 5.36. RFC4572 - Comedia over TLS in SDP . . . . . . . . . . . . 33
5.37. RFC4570 - SDP Source Filters . . . . . . . . . . . . . . 33 5.37. RFC4570 - SDP Source Filters . . . . . . . . . . . . . . 33
5.38. RFC6128 - RTCP Port for Multicast Sessions . . . . . . . 34 5.38. RFC6128 - RTCP Port for Multicast Sessions . . . . . . . 34
5.39. RFC6189 - ZRTP . . . . . . . . . . . . . . . . . . . . . 34 5.39. RFC6189 - ZRTP . . . . . . . . . . . . . . . . . . . . . 34
5.40. RFC4145 - Connection-Oriented Media . . . . . . . . . . . 35 5.40. RFC4145 - Connection-Oriented Media . . . . . . . . . . . 35
5.41. RFC6947 - The SDP ALTC Attribute . . . . . . . . . . . . 35 5.41. RFC6947 - The SDP ALTC Attribute . . . . . . . . . . . . 35
5.42. RFC7195 - SDP Extension for Circuit Switched Bearers 5.42. RFC7195 - SDP Extension for Circuit Switched Bearers
in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 36 in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP) . . 36 5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP) . . 36
5.44. RFC5159 - OMA BCAST SDP Attributes . . . . . . . . . . . 37 5.44. RFC5159 - OMA BCAST SDP Attributes . . . . . . . . . . . 36
5.45. RFC6193 - Media Description for IKE in SDP . . . . . . . 37 5.45. RFC6193 - Media Description for IKE in SDP . . . . . . . 37
5.46. RFC2326 - Real Time Streaming Protocol . . . . . . . . . 38 5.46. RFC2326 - Real Time Streaming Protocol . . . . . . . . . 38
5.47. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 39 5.47. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 38
5.48. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 42 5.48. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 41
5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 43 5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 42
5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 44 5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 43
5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 44 5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 43
5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 44 5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 44
5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 45 5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 44
5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 46 5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 45
5.55. ITU-T-REC.Q1970 . . . . . . . . . . . . . . . . . . . . . 46 5.55. ITU-T-REC.Q1970 . . . . . . . . . . . . . . . . . . . . . 46
5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 47 5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 47
5.57. RFC4975 - The Message Session Relay Protocol . . . . . . 47 5.57. RFC4975 - The Message Session Relay Protocol . . . . . . 47
5.58. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 48 5.58. Historical Attributes . . . . . . . . . . . . . . . . . . 48
5.59. Historical Attributes . . . . . . . . . . . . . . . . . . 48 6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 48
6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 49 6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 48
6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 49
6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 49 6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 49
6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 50 6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 49
7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 51 7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 50
7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 51 7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 50
7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 52 7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 51
7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 53 7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 52
7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 53 7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 52
7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 54 7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 53
7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 55 7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 54
8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 55 8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 54
8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 55 8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 54
8.2. RFC3524 - Mapping Media Streams to Resource 8.2. RFC3524 - Mapping Media Streams to Resource
Reservation Flows . . . . . . . . . . . . . . . . . . . . 56 Reservation Flows . . . . . . . . . . . . . . . . . . . . 55
8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 56 8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 55
8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 56 8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 55
8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 57 8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 56
8.6. RFC7104 - Duplication Grouping Semantics in the SDP . . 57 8.6. RFC7104 - Duplication Grouping Semantics in the SDP . . 56
9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 58 9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 57
9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 58 9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 57
9.2. RFC7104 - Duplication Grouping Semantics in the SDP . . . 58 9.2. RFC7104 - Duplication Grouping Semantics in the SDP . . . 57
10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 58 10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 57
10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 58 10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 57
11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 59 11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 58
11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 59 11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 58
12. content Attribute Analysis . . . . . . . . . . . . . . . . . 59 12. content Attribute Analysis . . . . . . . . . . . . . . . . . 58
12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 59 12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 58
13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 60 13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 59
13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 60 13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 59
14. Multiplexing Considerations for Encapsulating Attributes . . 60 14. Multiplexing Considerations for Encapsulating Attributes . . 59
14.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 61 14.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 60
14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 61 14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 60
14.2.1. Recommendation - Procedures for Potential 14.2.1. Recommendation - Procedures for Potential
Configuration Pairing . . . . . . . . . . . . . . . 62 Configuration Pairing . . . . . . . . . . . . . . . 61
14.2.1.1. Example: Transport Capability Multiplexing . . . 63 14.2.1.1. Example: Transport Capability Multiplexing . . . 62
14.2.1.2. Example: Attribute Capability Multiplexing . . . 64 14.2.1.2. Example: Attribute Capability Multiplexing . . . 63
14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 65 14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 64
14.3.1. Recommendation: Dealing with Payload Type Numbers . 65 14.3.1. Recommendation: Dealing with Payload Type Numbers . 64
14.3.1.1. Example: Attribute Capability Under Shared 14.3.1.1. Example: Attribute Capability Under Shared
Payload Type . . . . . . . . . . . . . . . . . . 65 Payload Type . . . . . . . . . . . . . . . . . . 64
14.3.2. Recommendation: Dealing with Latent Configurations . 66 14.3.2. Recommendation: Dealing with Latent Configurations . 65
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66
15.1. New 'Multiplexing Categories' subregistry . . . . . . . 67 15.1. New 'Multiplexing Categories' subregistry . . . . . . . 66
15.2. 'Mux Category' column for subregistries . . . . . . . . 68 15.2. 'Mux Category' column for subregistries . . . . . . . . 67
15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 68 15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 67
15.2.2. Table: att-field (session level) . . . . . . . . . . 68 15.2.2. Table: att-field (session level) . . . . . . . . . . 67
15.2.3. Table: att-field (both session and media level) . . 69 15.2.3. Table: att-field (both session and media level) . . 68
15.2.4. Table: att-field (media level only) . . . . . . . . 71 15.2.4. Table: att-field (media level only) . . . . . . . . 70
15.2.5. Table: att-field (source level) . . . . . . . . . . 74 15.2.5. Table: att-field (source level) . . . . . . . . . . 73
15.2.6. Table: content SDP Parameters . . . . . . . . . . . 74 15.2.6. Table: content SDP Parameters . . . . . . . . . . . 73
15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 75 15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 74
15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 75 15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 74
15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 76 15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 75
15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 76 15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 75
15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 76 15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 75
15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 77 15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 76
15.2.13. Table: SDP/RTSP key management protocol identifiers 77 15.2.13. Table: SDP/RTSP key management protocol identifiers 76
15.2.14. Table: Codec Control Messages . . . . . . . . . . . 77 15.2.14. Table: Codec Control Messages . . . . . . . . . . . 76
15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 78 15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 77
15.2.16. Table: SDP Capability Negotiation Option Tags . . . 78 15.2.16. Table: SDP Capability Negotiation Option Tags . . . 77
15.2.17. Table: Timestamp Reference Clock Source Parameters . 78 15.2.17. Table: Timestamp Reference Clock Source Parameters . 77
15.2.18. Table: Media Clock Source Parameters . . . . . . . . 79 15.2.18. Table: Media Clock Source Parameters . . . . . . . . 78
16. Security Considerations . . . . . . . . . . . . . . . . . . . 79 16. Security Considerations . . . . . . . . . . . . . . . . . . . 78
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 79 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 78
18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 80 18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 79
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 82 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 81
19.1. Normative References . . . . . . . . . . . . . . . . . . 82 19.1. Normative References . . . . . . . . . . . . . . . . . . 81
19.2. Informative References . . . . . . . . . . . . . . . . . 82 19.2. Informative References . . . . . . . . . . . . . . . . . 81
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 88 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 88
1. Introduction 1. Introduction
Real-Time Communication Web (RTCWeb) framework requires Real-time Real-Time Communication in WEB-browsers (Rtcweb) framework requires
Transport Protocol (RTP) as the media transport protocol and Session Real-time Transport Protocol (RTP) as the media transport protocol
Description Protocol (SDP) [RFC4566] for describing and negotiating and Session Description Protocol (SDP) [RFC4566] for describing and
multi-media communication sessions. negotiating multi-media communication sessions.
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 in the IETF RTCWEB WG, a need to use transport layer flows. However in the IETF RTCWEB WG, a need to use
a single 5-tuple for sending and receiving media associated with a single 5-tuple for sending and receiving media associated with
multiple SDP media descriptions ("m=" lines) has been identified. multiple SDP media descriptions ("m=" lines) has been identified.
This would for e.g. allow the usage of a single set of Interactive This would for e.g. allow the usage of a single set of Interactive
skipping to change at page 6, line 34 skipping to change at page 6, line 31
The time and complications of setting up ICE [RFC5245] and DTLS-SRTP The time and complications of setting up ICE [RFC5245] and DTLS-SRTP
[RFC5763] transports for use by RTP, and conservation of ports, forms [RFC5763] transports for use by RTP, and conservation of ports, forms
an requirement to try and reduce the number of transport level flows an requirement to try and reduce the number of transport level flows
needed. This has resulted in the definition of ways, such as, needed. This has resulted in the definition of ways, such as,
[I-D.ietf-mmusic-sdp-bundle-negotiation] to multiplex RTP over a [I-D.ietf-mmusic-sdp-bundle-negotiation] to multiplex RTP over a
single transport flow in order to preserve network resources such as single transport flow in order to preserve network resources such as
port numbers. This imposes further restrictions on applicability of port numbers. This imposes further restrictions on applicability of
these SDP attributes as they are defined today. these 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.
As of today there are close to 250 SDP attributes registered with the As of today there are close to 250 SDP attributes registered with the
[IANA] and more will be added in the future. There is no clearly [IANA] and more will be added in the future. There is no clearly
defined procedure to establish the validity/applicability of these defined procedure to establish the validity/applicability of these
attribute when used with transport multiplexing. attribute when used with transport multiplexing.
skipping to change at page 8, line 27 skipping to change at page 8, line 25
</allOneLine> </allOneLine>
m=video 34567 RTP/AVP 31 //without zrtp m=video 34567 RTP/AVP 31 //without zrtp
a=rtpmap:31 H261/90000 a=rtpmap:31 H261/90000
4.3. Category: IDENTICAL 4.3. Category: IDENTICAL
Attributes that MUST be identical across all the media descriptions Attributes that MUST be identical across all the media descriptions
being multiplexed. being multiplexed.
Attributes such as rtcp-mux fall into this category. Since RTCP Attributes such as rtcp-mux fall into this category. Since RTCP
reporting is done per RTP Session, RTCP Multiplexing MUST to enabled reporting is done per RTP Session, RTCP Multiplexing MUST be enabled
for both the audio and video m=lines in the example below if they are for both the audio and video m=lines if they are transported over a
transported over a single 5-tuple. single 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=audio 34567 RTP/AVP 97 m=audio 34567 RTP/AVP 97
a=rtcp-mux a=rtcp-mux
m=video 34567 RTP/AVP 31 m=video 34567 RTP/AVP 31
a=rtpmap:31 H261/90000 a=rtpmap:31 H261/90000
skipping to change at page 10, line 48 skipping to change at page 10, line 48
a=cdsc: 2 video RTP/AVP 101 a=cdsc: 2 video RTP/AVP 101
a=cpar: a=rtcp-mux a=cpar: a=rtcp-mux
In the above example , the category IDENTICAL is inherited for the In the above example , the category IDENTICAL is inherited for the
cpar encapsulated rtcp-mux attribute. cpar encapsulated rtcp-mux attribute.
4.7. Category: IDENTICAL-PER-PT 4.7. Category: IDENTICAL-PER-PT
Attributes that define the RTP payload configuration on per Payload Attributes that define the RTP payload configuration on per Payload
Type basis and MUST have identical values across all the media Type basis and MUST have identical values across all the media
descriptions for a given RTP Payload Type when repeated. descriptions for a given RTP Payload Type when repeated. These
Payload Types identify the same codec configuration as defined in the
Section 10.1.2 of [I-D.ietf-mmusic-sdp-bundle-negotiation] under this
context.
In the SDP example below, Payload Types 96 and 97 are repeated across In the SDP example below, Payload Types 96 and 97 are repeated across
all the video m= lines and all the payload specific parameters (ex: all the video m= lines and all the payload specific parameters (ex:
rtpmap, fmtp) are identical. rtpmap, fmtp) are identical.
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=
c=IN IP4 host.atlanta.example.com c=IN IP4 host.atlanta.example.com
t=0 0 t=0 0
skipping to change at page 11, line 46 skipping to change at page 12, line 7
4.9. Category: TBD 4.9. Category: TBD
Attributes that have not been analyzed under the proposed Attributes that have not been analyzed under the proposed
multiplexing framework yet. For the purposes of implementations it multiplexing framework yet. For the purposes of implementations it
is advised to consider "NOT RECOMMENDED" as the category when is advised to consider "NOT RECOMMENDED" as the category when
multiplexing these attributes. multiplexing these attributes.
5. Analysis of Existing Attributes 5. Analysis of Existing Attributes
This section analyzes attributes listed in [IANA] grouped under the This section analyzes attributes listed in [IANA], grouped under the
IETF document that defines them. The "Level" column indicates IETF document that defines them.
whether the attribute is currently specified as:
The "Level" column indicates whether the attribute is currently
specified as:
o S -- Session level o S -- Session level
o M -- Media level o M -- Media level
o B -- Both o B -- Both
o SR -- Source-level (for a single SSRC) o SR -- Source-level (for a single SSRC)
The "Mux Category" column identifies multiplexing category assigned
per attribute and the "Notes" column captures additional informative
details regarding the assigned category, wherever necessary.
5.1. RFC4566 - SDP: Session Description Protocol 5.1. RFC4566 - SDP: Session Description Protocol
[RFC4566] defines the Session Description Protocol (SDP) that is [RFC4566] defines the Session Description Protocol (SDP) that is
intended for describing multimedia sessions for the purposes of intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of session announcement, session invitation, and other forms of
multimedia session initiation. multimedia session initiation.
+-----------------+---------------------+-------+-------------------+ +-----------------+---------------------+-------+-------------------+
| Attr Name | Notes | Level | Category | | Attr Name | Notes | Level | Mux Category |
+-----------------+---------------------+-------+-------------------+ +-----------------+---------------------+-------+-------------------+
| sendrecv | Not impacted | B | NORMAL | | sendrecv | Not impacted | B | NORMAL |
| | | | | | | | | |
| sendonly | Not impacted | B | NORMAL | | sendonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| recvonly | Not impacted | B | NORMAL | | recvonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| inactive | Not impacted | B | NORMAL | | inactive | Not impacted | B | NORMAL |
| | | | | | | | | |
| cat | Not impacted | S | NORMAL | | cat | Not impacted | S | NORMAL |
skipping to change at page 14, line 6 skipping to change at page 14, line 13
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.
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| Attr | Notes | Level | Category | | Attr | Notes | Level | Mux Category |
| Name | | | | | Name | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| 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. | | |
| | | | | | | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
skipping to change at page 14, line 29 skipping to change at page 14, line 36
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 Session Description Protocol (SDP) can be used to
signal multiplexed sessions. signal multiplexed sessions.
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | 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 | Category | | Name | Notes | Level | Mux Category |
+-------+-----------------------+-------+------------------+ +-------+-----------------------+-------+------------------+
| des | Refer to notes below | M | NOT RECOMMENDED | | des | Refer to notes below | M | NOT RECOMMENDED |
| | | | | | | | | |
| conf | Refer to notes below | M | NOT RECOMMENDED | | conf | Refer to notes below | M | NOT RECOMMENDED |
| | | | | | | | | |
| curr | Refer to notes below | M | NOT RECOMMENDED | | curr | Refer to notes below | M | NOT RECOMMENDED |
| | | | | | | | | |
+-------+-----------------------+-------+------------------+ +-------+-----------------------+-------+------------------+
RFC3312 Attribute Analysis RFC3312 Attribute Analysis
A mismatched set of Preconditions across media descriptions results A mismatched set of preconditions across media descriptions results
in Session establishment failures due to inability to meet the right in Session establishment failures due to inability in meeting the
resource reservations requested. 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 Session Description Protocol (SDP) media-
level attribute: "label". The "label" attribute carries a pointer to level attribute: "label". The "label" attribute carries a pointer to
a media stream in the context of an arbitrary network application a media stream in the context of an arbitrary network application
that uses SDP. The sender of the SDP document can attach the "label" that uses SDP. The sender of the SDP document can attach the "label"
attribute to a particular media stream or streams. The application attribute to a particular media stream or streams. The application
can then use the provided pointer to refer to each particular media can then use the provided pointer to refer to each particular media
stream in its context. stream in its context.
+--------+---------------+-------+----------+ +--------+---------------+-------+--------------+
| Name | Notes | Level | 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. Session Description Protocol (SDP) offer/answer model.
+----------------+------------------------+-------+----------+ +----------------+------------------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+----------------+------------------------+-------+----------+ +----------------+------------------------+-------+--------------+
| qos-mech-send | Refer to notes below | B | NORMAL | | qos-mech-send | Refer to notes below | B | NORMAL |
| | | | | | | | | |
| qos-mech-recv | Refer to notes below. | B | NORMAL | | qos-mech-recv | Refer to notes below. | B | NORMAL |
| | | | | | | | | |
+----------------+------------------------+-------+----------+ +----------------+------------------------+-------+--------------+
RFC5432 Attribute Analysis RFC5432 Attribute Analysis
A single DSCP code point per flow being multiplexed doesn't impact A single DSCP code point per flow being multiplexed doesn't impact
multiplexing since QOS mechanisms are signaled/scoped per flow.For multiplexing since QOS mechanisms are signaled/scoped per flow. For
scenarios that involves having different DSCP for packets being scenarios that involves having different DSCP code points for packets
transmitted over the same 5-tuple, has issues as discussed in being transmitted over the same 5-tuple, issues as discussed in
[I.D-draft-ietf-dart-dscp-rtp] [I.D-draft-ietf-dart-dscp-rtp] needs to be taken into consideration.
5.7. RFC4568 - SDP Security Descriptions 5.7. RFC4568 - SDP Security Descriptions
[RFC4568] defines a Session Description Protocol (SDP) cryptographic [RFC4568] defines a Session Description Protocol (SDP) cryptographic
attribute for unicast media streams. The attribute describes a attribute for unicast media streams. The attribute describes a
cryptographic key and other parameters that serve to configure cryptographic key and other parameters that serve to configure
security for a unicast media stream in either a single message or a security for a unicast media stream in either a single message or a
roundtrip exchange. roundtrip exchange.
+---------+------------------------------------+-------+------------+ +---------+------------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | 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 The Real-time Transport Protocol (RTP) is a widely used transport for
real-time multimedia on IP networks. The Datagram Congestion Control real-time multimedia on IP networks. The Datagram Congestion Control
Protocol (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 | 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 | | |
| | RFC5762, the port | | | | | RFC5762, the port | | |
| | in the "m=" line is | | | | | in the "m=" line is | | |
| | a DCCP port. DCCP | | | | | a DCCP port. DCCP | | |
| | being a connection | | | | | being a connection | | |
| | oriented protocol, | | | | | oriented protocol, | | |
| | does not allow | | | | | does not allow | | |
skipping to change at page 17, line 42 skipping to change at page 17, line 42
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 the
Datagram Congestion Control Protocol (DCCP), referred to as DCCP-UDP. Datagram Congestion Control Protocol (DCCP), referred to as DCCP-UDP.
This encapsulation allows DCCP to be carried through the current This encapsulation allows DCCP to be carried through the current
generation of Network Address Translation (NAT) middle boxes without generation of Network Address Translation (NAT) middle boxes without
modification of those middle boxes. modification of those middle boxes.
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| Name | Notes | Level | 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
skipping to change at page 18, line 23 skipping to change at page 18, line 23
nature of DCCP encapsulations and ports choses thus rendering it to nature of DCCP encapsulations and ports choses 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
Real-time Transport Protocol (RTCP) packets to be transmitted with Real-time Transport Protocol (RTCP) packets to be transmitted with
reduced size. reduced size.
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | 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
skipping to change at page 19, line 5 skipping to change at page 19, line 5
coordinate MRCPv2 clients and servers and manage sessions between coordinate MRCPv2 clients and servers and manage sessions between
them, and the Session Description Protocol (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 | Category | | Name | Notes | Level | Mux Category |
+-----------+---------------+-------+----------+ +-----------+---------------+-------+--------------+
| 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 - Interactive Connectivity Establishment (ICE)
[RFC5245] describes a protocol for Network Address Translator(NAT) [RFC5245] describes a protocol for Network Address Translator(NAT)
traversal for UDP-based multimedia sessions established with the traversal for UDP-based multimedia sessions established with the
offer/answer model. This protocol is called Interactive Connectivity offer/answer model. This protocol is called Interactive Connectivity
Establishment (ICE). ICE makes use of the Session Traversal Establishment (ICE). ICE makes use of the Session Traversal
Utilities for NAT (STUN) protocol and its extension,Traversal Using Utilities for NAT (STUN) protocol and its extension,Traversal Using
Relay NAT (TURN). ICE can be used by any protocol utilizing the Relay NAT (TURN). ICE can be used by any protocol utilizing the
offer/answer model, such as the Session Initiation Protocol (SIP). offer/answer model, such as the Session Initiation Protocol (SIP).
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
| ice-lite | Not Impacted | S | NORMAL | | ice-lite | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-options | Not Impacted | S | NORMAL | | ice-options | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-mismatch | Not Impacted | S | NORMAL | | ice-mismatch | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-pwd | ice-pwd MUST be the one | B | TRANSPORT | | ice-pwd | ice-pwd MUST be the one | B | TRANSPORT |
| | that corresponds to the | | | | | that corresponds to the | | |
| | m=line chosen for | | | | | m=line chosen for | | |
skipping to change at page 21, line 8 skipping to change at page 21, line 14
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 (the Real-Time Transport Protocol). It provides the
option to use a small number of small extensions in each RTP packet, option to use a small number of small extensions in each RTP packet,
where the universe of possible extensions is large and registration where the universe of possible extensions is large and registration
is de-centralized. The actual extensions in use in a session are is de-centralized. The actual extensions in use in a session are
signaled in the setup information for that session. signaled in the setup information for that session.
+---------+--------------------------------------+-------+----------+ +---------+-------------------------------------+-------+-----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
+---------+--------------------------------------+-------+----------+ | | | | Category |
| extmap | Specific RTP extension document MUST | B | SPECIAL | +---------+-------------------------------------+-------+-----------+
| | be referred | | | | extmap | Specific RTP extension document | B | SPECIAL |
| | | | | | | 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 | Category | | Name | Notes | Level | Mux |
| | | | Category |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| rtcp | Identical attribute value MUST be | M | IDENTICAL | | rtcp | Identical attribute value MUST be | M | IDENTICAL |
| | used since the RTCP port affects the | | | | | used since the RTCP port affects the | | |
| | entire RTP session. | | | | | entire RTP session. | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
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 | Category | | Name | Notes | Level | Mux Category |
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
| ssrc | Refer to Notes below | M | NORMAL | | ssrc | Refer to Notes below | M | NORMAL |
| | | | | | | | | |
| ssrc-group | Refer to section | M | NORMAL | | ssrc-group | Refer to section | M | NORMAL |
| | Section 9 for | | | | | Section 9 for | | |
| | specific analysis of | | | | | specific analysis of | | |
| | the grouping | | | | | the grouping | | |
| | semantics | | | | | semantics | | |
| | | | | | | | | |
| cname | Not Impacted | SR | NORMAL | | cname | Not Impacted | SR | NORMAL |
skipping to change at page 22, line 38 skipping to change at page 22, line 38
If SSRCs are repeated across m=lines being multiplexed, they MUST all If SSRCs are repeated across m=lines being multiplexed, they MUST all
represent the same underlying RTP Source. 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 Session Description Protocol (SDP) signalling
that identifies timestamp reference clock sources and SDP signalling that identifies timestamp reference clock sources and SDP signalling
that identifies the media clock sources in a multimedia session. that identifies the media clock sources in a multimedia session.
+------------+---------------+-------+----------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | 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 |
| | | | | | | | | |
+------------+---------------+-------+----------+ +------------+---------------+-------+--------------+
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,something that may consume large amounts of memory and image,something that may consume large amounts of memory and
processing power. The document also helps to maintain an optimal processing power. The document also helps to maintain an optimal
bitrate for video as only the image size that is desired by the bitrate for video as only the image size that is desired by the
receiver is transmitted. receiver is transmitted.
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
| Name | Notes | Level | 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 the Session
Description Protocol. Description Protocol.
+--------------------+---------------+-------+----------+ +--------------------+---------------+-------+--------------+
| Name | Notes | Level | 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. RFC7226 - RTCP XR Blocks for MOS Metric Reporting 5.19. RFC7266 - RTCP XR Blocks for MOS Metric Reporting
[RFC7226] defines an RTP Control Protocol (RTCP) Extended Report (XR) [RFC7266] defines an RTP Control Protocol (RTCP) Extended Report (XR)
Block including two new segment types and associated Session Block including two new segment types and associated Session
Description Protocol (SDP) parameters that allow the reporting of Description Protocol (SDP) parameters that allow the reporting of
mean opinion score (MOS) Metrics for use in a range of RTP mean opinion score (MOS) Metrics for use in a range of RTP
applications. applications.
+-------------+---------------+-------+----------+ +-------------+---------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+-------------+---------------+-------+----------+ +-------------+---------------+-------+--------------+
| calgextmap | Not Impacted | B | NORMAL | | calgextmap | Not Impacted | B | NORMAL |
| | | | | | | | | |
+-------------+---------------+-------+----------+ +-------------+---------------+-------+--------------+
RFC7226 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 RTP Control
Protocol (RTCP) machinery that reduces the acquisition delay. In Protocol (RTCP) machinery that reduces the acquisition delay. In
this method, an auxiliary unicast RTP session carrying the Reference this method, an auxiliary unicast RTP session carrying the Reference
Information to the receiver precedes or accompanies the multicast Information to the receiver precedes or accompanies the multicast
stream. This unicast RTP flow can be transmitted at a faster than stream. This unicast RTP flow can be transmitted at a faster than
natural bitrate to further accelerate the acquisition. The natural bitrate to further accelerate the acquisition. The
motivating use case for this capability is multicast applications motivating use case for this capability is multicast applications
that carry real-time compressed audio and video. that carry real-time compressed audio and video.
+---------------+-------------------+-------+------------------+ +---------------+-------------------+-------+------------------+
| Name | Notes | Level | 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 the Session Initiation Protocol (SIP) to establish an
application-level control mechanism between application servers and application-level control mechanism between application servers and
associated external servers such as media servers. associated external servers such as media servers.
+---------+-----------------+-------+----------+ +---------+-----------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+---------+-----------------+-------+----------+ +---------+-----------------+-------+--------------+
| cfw-id | Not Applicable | M | NORMAL | | cfw-id | Not Applicable | 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 the Session Description Protocol (SDP)
to describe the parameters required to signal the Forward Error to describe the parameters required to signal the Forward Error
Correction (FEC) Framework Configuration Information between the Correction (FEC) Framework Configuration Information between the
sender(s) and receiver(s). This document also provides examples that sender(s) and receiver(s). This document also provides examples that
show the semantics for grouping multiple source and repair flows show the semantics for grouping multiple source and repair flows
together for the applications that simultaneously use multiple together for the applications that simultaneously use multiple
instances of the FEC Framework. instances of the FEC Framework.
+------------------+-----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | 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 |
| | document needs to be | | | | | document needs to be | | |
| | referred | | | | | referred | | |
| | | | | | | | | |
| repair-window | Specific FEC scheme | M | SPECIAL | | repair-window | Specific FEC scheme | M | SPECIAL |
skipping to change at page 25, line 44 skipping to change at page 25, line 45
5.23. RFC4796 - Content Attribute 5.23. RFC4796 - Content Attribute
[RFC4796] defines a new Session Description Protocol (SDP) media- [RFC4796] defines a new Session Description Protocol (SDP) media-
level attribute, 'content'. The 'content' attribute defines the level attribute, 'content'. The 'content' attribute defines the
content of the media stream to a more detailed level than the media content of the media stream to a more detailed level than the media
description line. The sender of an SDP session description can description line. The sender of an SDP session description can
attach the 'content' attribute to one or more media streams. The attach the 'content' attribute to one or more media streams. The
receiving application can then treat each media stream differently receiving application can then treat each media stream differently
(e.g., show it on a big or small screen) based on its content. (e.g., show it on a big or small screen) based on its content.
+----------+---------------+-------+----------+ +----------+---------------+-------+--------------+
| Name | Notes | Level | 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 Session Description Protocol (SDP)
attributes that enables SDP to provide a minimal and backwards attributes that enables SDP to provide a minimal and backwards
compatible capability declaration mechanism. compatible capability declaration mechanism.
+----------+------------------------+-------+----------+ +----------+------------------------+-------+--------------+
| Name | Notes | Level | 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 |
| | | | | | | | | |
| cparmin | Refer to notes below | B | SPECIAL | | cparmin | Refer to notes below | B | SPECIAL |
| | | | | | | | | |
| cparmax | Refer to notes below | B | SPECIAL | | cparmax | Refer to notes below | B | SPECIAL |
| | | | | | | | | |
+----------+------------------------+-------+----------+ +----------+------------------------+-------+--------------+
RFC3407 Attribute Analysis RFC3407 Attribute Analysis
Since the attributes (a=cparmin and a=cparmax) define minimum and Since the attributes (a=cparmin and a=cparmax) define minimum and
maximum numerical values associated with the attributes described in maximum numerical values associated with the attributes described in
a=cpar, it is recommended to consult the document defining the 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 | 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
skipping to change at page 27, line 17 skipping to change at page 27, line 17
[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 Session Description Protocol (SDP) attribute,
'msrp-cema', that MSRP endpoints use to indicate support of the CEMA 'msrp-cema', that MSRP endpoints use to indicate support of the CEMA
extension. extension.
+------------+---------------+-------+----------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+------------+---------------+-------+----------+ +------------+---------------+-------+--------------+
| msrp-cema | Not Impacted | M | NORMAL | | msrp-cema | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+----------+ +------------+---------------+-------+--------------+
RFC6714 Attribute Analysis RFC6714 Attribute Analysis
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 Session Description Protocol (SDP)
descriptions. User agents using the offer/answer model to establish descriptions. User agents using the offer/answer model to establish
BFCP streams use this format in their offers and answers. BFCP streams use this format in their offers and answers.
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| floorctrl | Must be repeated across all the | M | IDENTICAL | | floorctrl | Must be repeated across all the | M | IDENTICAL |
| | multiplexed m=lines | | | | | multiplexed m=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 | | |
skipping to change at page 28, line 11 skipping to change at page 28, line 11
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
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 Session Description
Protocol (SDP) offer/answer model specified in [RFC3264]. Protocol (SDP) offer/answer model specified in [RFC3264].
+----------------------+---------------+-------+----------+ +----------------------+---------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+----------------------+---------------+-------+----------+ +----------------------+---------------+-------+--------------+
| file-selector | Not Impacted | M | NORMAL | | file-selector | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-transfer-id | Not Impacted | M | NORMAL | | file-transfer-id | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-disposition | Not Impacted | M | NORMAL | | file-disposition | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-date | Not Impacted | M | NORMAL | | file-date | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-iconfile-range | Not Impacted | M | NORMAL | | file-iconfile-range | Not Impacted | M | NORMAL |
| | | | | | | | | |
+----------------------+---------------+-------+----------+ +----------------------+---------------+-------+--------------+
RFC5547 Attribute Analysis RFC5547 Attribute Analysis
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 VoIP, Real-time Text and Video over IP performance metrics.
+------------------------------+----------------+-------+----------+ +---------------------------+----------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+------------------------------+----------------+-------+----------+ +---------------------------+----------------+-------+--------------+
| loopback rtp-pkt-loopback | Not Impacted | M | NORMAL | | loopback rtp-pkt-loopback | Not Impacted | M | NORMAL |
| | | | | | | | | |
| loopback rtp-media-loopback | Not Impacted | M | NORMAL | | loopback rtp-media- | Not Impacted | M | NORMAL |
| | | | | | loopback | | | |
| 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 the Real-time Transport Control
Protocol (RTCP) to use unicast feedback to a multicast sender. The Protocol (RTCP) to use unicast feedback to a multicast sender. The
proposed extension is useful for single-source multicast sessions proposed extension is useful for single-source multicast sessions
such as Source-Specific Multicast (SSM) communication where the such as Source-Specific Multicast (SSM) communication where the
traditional model of many-to-many group communication is either not traditional model of many-to-many group communication is either not
available or not desired. available or not desired.
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| rtcp-unicast | The attribute MUST be | M | IDENTICAL | | rtcp-unicast | The attribute MUST be | M | IDENTICAL |
| | reported across all m=lines | | | | | reported across all m=lines | | |
| | multiplexed | | | | | 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 the RTP
Control Protocol (RTCP), and defines how the use of XR packets can be Control Protocol (RTCP), and defines how the use of XR packets can be
signaled by an application if it employs the Session Description signaled by an application if it employs the Session Description
Protocol (SDP). Protocol (SDP).
+----------+---------------+-------+----------+ +----------+---------------+-------+--------------+
| Name | Notes | Level | 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 | Category | | Name | Notes | Level | Mux Category |
+---------+-------------------------------+-------+----------+ +---------+-------------------------------+-------+--------------+
| pcfg | Refer to Section Section 14 | M | SPECIAL | | pcfg | Refer to Section Section 14 | M | SPECIAL |
| | | | | | | | | |
| acfg | Refer to Section Section 14 | M | SPECIAL | | acfg | Refer to Section Section 14 | M | SPECIAL |
| | | | | | | | | |
| csup | Not Impacted | B | NORMAL | | csup | Not Impacted | B | NORMAL |
| | | | | | | | | |
| creq | Not Impacted | B | NORMAL | | creq | Not Impacted | B | NORMAL |
| | | | | | | | | |
| acap | Refer to section Section 14 | B | INHERIT | | acap | Refer to section Section 14 | B | INHERIT |
| | | | | | | | | |
| tcap | Refer to section Section 14 | B | INHERIT | | tcap | Refer to section 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 Session Description Protocol (SDP) capability negotiation provides a
general framework for indicating and negotiating capabilities in SDP. general framework for indicating and negotiating capabilities in SDP.
The base framework defines only capabilities for negotiating The base framework defines only capabilities for negotiating
transport protocols and attributes. [RFC6871] extends the framework transport protocols and attributes. [RFC6871] extends the framework
by defining media capabilities that can be used to negotiate media by defining media capabilities that can be used to negotiate media
types and their associated parameters. types and their associated parameters.
+---------+-----------------------------+-------+-------------------+ +---------+-----------------------------+-------+-------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+---------+-----------------------------+-------+-------------------+ +---------+-----------------------------+-------+-------------------+
| rmcap | Refer to Section Section 14 | B | IDENTICAL-PER-PT | | rmcap | Refer to Section Section 14 | B | IDENTICAL-PER-PT |
| | | | | | | | | |
| omcap | Not Impacted | B | NORMAL | | omcap | Not Impacted | B | NORMAL |
| | | | | | | | | |
| mfcap | Refer to Section Section 14 | B | IDENTICAL-PER-PT | | mfcap | Refer to Section Section 14 | B | IDENTICAL-PER-PT |
| | | | | | | | | |
| mscap | Refer to Section Section 14 | B | INHERIT | | mscap | Refer to Section Section 14 | B | INHERIT |
| | | | | | | | | |
| lcfg | Refer to Section Section 14 | B | SPECIAL | | lcfg | Refer to Section Section 14 | B | SPECIAL |
| | | | | | | | | |
| sescap | Refer to Section Section 14 | S | NOT RECOMMENDED | | sescap | Refer to notes below | S | NOT RECOMMENDED |
| | | | | | | | | |
| med-v0 | Not Impacted | S | NORMAL | | med-v0 | Not Impacted | S | NORMAL |
| | | | | | | | | |
+---------+-----------------------------+-------+-------------------+ +---------+-----------------------------+-------+-------------------+
RFC6871 - Attribute Analysis RFC6871 - Attribute Analysis
The "sescap" attribute is NOT RECOMMENDED for use with multiplexing. The "sescap" attribute is NOT RECOMMENDED for use with multiplexing.
The reason is that it requires the use of unique configuration The reason is that it requires the use of unique configuration
numbers across the entire SDP (per [RFC6871] as opposed to within a numbers across the entire SDP (per [RFC6871]) as opposed to within a
media description only (per [RFC5939]). As described in Section 14, media description only (per [RFC5939]). As described in Section 14,
the use of identical configuration numbers between multiplxed the use of identical configuration numbers between multiplexed
(bundled) media descriptions is the default way of indicating (bundled) media descriptions is the default way of indicating
compatible configurations in a bundle. 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 | Category | | Name | Notes | Level | Mux |
| | | | Category |
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
| bcap | Inherit the category SUM as | B | INHERIT | | bcap | Inherit the category SUM as | B | INHERIT |
| | applicable to b= attribute | | | | | applicable to b= attribute | | |
| | | | | | | | | |
| bcap-v0 | Not Impacted | B | NORMAL | | bcap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
| ccap | The connection address type MUST | B | IDENTICAL | | ccap | The connection address type MUST | B | IDENTICAL |
| | be identical across all the | | | | | be identical across all the | | |
| | multiplexed m= lines. | | | | | multiplexed m= lines. | | |
| | | | | | | | | |
skipping to change at page 32, line 37 skipping to change at page 32, line 38
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 Session Description Protocol
(SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as (SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as
specified by a key management protocol, in order to secure the media. specified by a key management protocol, in order to secure the media.
These extensions are presented as a framework, to be used by one or These extensions are presented as a framework, to be used by one or
more key management protocols. As such, their use is meaningful only more key management protocols. As such, their use is meaningful only
when complemented by an appropriate key management protocol. when complemented by an appropriate key management protocol.
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| key-mgmt | Key management protocol MUST be | B | IDENTICAL | | key-mgmt | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the m=lines | | | | | identical across all the m=lines | | |
| | | | | | | | | |
| mikey | Key management protocol MUST be | B | IDENTICAL | | mikey | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the m=lines | | | | | identical across all the m=lines | | |
| | | | | | | | | |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
RFC4567 Attribute Analysis RFC4567 Attribute Analysis
skipping to change at page 33, line 18 skipping to change at page 33, line 18
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 the Session Description Protocol (SDP). It defines a new SDP
protocol identifier, 'TCP/TLS'. It also defines the syntax and protocol identifier, 'TCP/TLS'. It also defines the syntax and
semantics for an SDP 'fingerprint' attribute that identifies the semantics for an SDP 'fingerprint' attribute that identifies the
certificate that will be presented for the TLS session. This certificate that will be presented for the TLS session. This
mechanism allows media transport over TLS connections to be mechanism allows media transport over TLS connections to be
established securely, so long as the integrity of session established securely, so long as the integrity of session
descriptions is assured. descriptions is assured.
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | 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 the Session Description Protocol
(SDP) to express one or more source addresses as a source filter for (SDP) to express one or more source addresses as a source filter for
one or more destination "connection" addresses. It defines the one or more destination "connection" addresses. It defines the
syntax and semantics for an SDP "source-filter" attribute that may syntax and semantics for an SDP "source-filter" attribute that may
reference either IPv4 or IPv6 address(es) as either an inclusive or reference either IPv4 or IPv6 address(es) as either an inclusive or
exclusive source list for either multicast or unicast destinations. exclusive source list for either multicast or unicast destinations.
In particular, an inclusive source-filter can be used to specify a In particular, an inclusive source-filter can be used to specify a
Source-Specific Multicast (SSM) session. Source-Specific Multicast (SSM) session.
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| source-filter | The attribute MUST be | B | IDENTICAL | | source-filter | The attribute MUST be | B | IDENTICAL |
| | repeated across all m=lines | | | | | repeated across all m=lines | | |
| | multiplexed | | | | | multiplexed | | |
| | | | | | | | | |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
RFC4570 Attribute Analysis RFC4570 Attribute Analysis
5.38. RFC6128 - RTCP Port for Multicast Sessions 5.38. RFC6128 - RTCP Port for Multicast Sessions
skipping to change at page 34, line 20 skipping to change at page 34, line 20
multicast (SSM) sessions, the same attribute is used to designate the multicast (SSM) sessions, the same attribute is used to designate the
address and the RTCP port of the Feedback Target in the SDP address and the RTCP port of the Feedback Target in the SDP
description. However, the RTCP port associated with the SSM session description. However, the RTCP port associated with the SSM session
itself cannot be specified by the same attribute to avoid ambiguity, itself cannot be specified by the same attribute to avoid ambiguity,
and thus, is required to be derived from the "m=" line of the media and thus, is required to be derived from the "m=" line of the media
description. Deriving the RTCP port from the "m=" line imposes an description. Deriving the RTCP port from the "m=" line imposes an
unnecessary restriction. [RFC6128] removes this restriction by unnecessary restriction. [RFC6128] removes this restriction by
introducing a new SDP attribute. introducing a new SDP attribute.
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | 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 Secure Real-time Transport Protocol (SRTP) sessions for Voice
over IP (VoIP) applications. over IP (VoIP) applications.
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| zrtp-hash | Complicates if all the | M | NOT | | zrtp-hash | Complicates if all the | M | NOT |
| | m=lines are not authenticated | | RECOMMENDED | | | m=lines are not authenticated | | RECOMMENDED |
| | as given in the example below | | | | | as given in the example below | | |
| | | | | | | | | |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
RFC6189 Attribute Analysis RFC6189 Attribute Analysis
Example: Multiplexing media descriptions having attribute zrtp-hash
defined with the media descriptions lacking it, would either
complicate the handling of multiplexed stream or fail multiplexing.
v=0
o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com
s=
c=IN IP4 client.biloxi.example.com
t=0 0
m=audio 3456 RTP/AVP 97
a=rtpmap:97 iLBC/8000
<allOneLine>
a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2
df881ae642c371ba46df
</allOneLine>
m=video 34567 RTP/AVP 31
a=rtpmap:31 H261/90000
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 the
Session Description Protocol (SDP). It defines the SDP 'TCP' Session Description Protocol (SDP). It defines the SDP 'TCP'
protocol identifier, the SDP 'setup' attribute, which describes the protocol identifier, the SDP 'setup' attribute, which describes the
connection setup procedure, and the SDP 'connection' attribute, which connection setup procedure, and the SDP 'connection' attribute, which
handles connection reestablishment. handles connection reestablishment.
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| setup | MUST be identical across all | B | IDENTICAL | | setup | MUST be identical across all | B | IDENTICAL |
| | m=lines | | | | | m=lines | | |
| | | | | | | | | |
| connection | MUST be identical across all | B | IDENTICAL | | connection | MUST be identical across all | B | IDENTICAL |
| | m=lines | | | | | m=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 | Category | | Name | Notes | Level | Mux |
| | | | 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=line | | | | | one that corresponds to the m=line | | |
| | chosen for setting up the underlying | | | | | chosen for setting up the underlying | | |
| | transport flow. | | | | | 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 the Session Description Protocol (SDP) offer/answer model
for establishing audio and video media streams over circuit-switched for establishing audio and video media streams over circuit-switched
bearers in the Public Switched Telephone Network (PSTN). bearers in the Public Switched Telephone Network (PSTN).
+--------------------------+----------------+-------+----------+ +--------------------------+----------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+--------------------------+----------------+-------+----------+ +--------------------------+----------------+-------+--------------+
| cs-correlation:callerid | Not Impacted. | M | NORMAL | | cs-correlation:callerid | Not Impacted. | M | NORMAL |
| | | | | | | | | |
| cs-correlation:uuie | Not Impacted. | M | NORMAL | | cs-correlation:uuie | Not Impacted. | M | NORMAL |
| | | | | | | | | |
| cs-correlation:dtmf | Not Impacted. | M | NORMAL | | cs-correlation:dtmf | Not Impacted. | M | NORMAL |
| | | | | | | | | |
| cs-correlation:external | Not Impacted. | M | NORMAL | | cs-correlation:external | Not Impacted. | M | NORMAL |
| | | | | | | | | |
+--------------------------+----------------+-------+----------+ +--------------------------+----------------+-------+--------------+
RFC7195 Attribute Analysis RFC7195 Attribute Analysis
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 RTP Control Protocol (RTCP) Packet Type and
an RTCP Extended Report (XR) Block Type to be used for achieving an RTCP Extended Report (XR) Block Type to be used for achieving
Inter-Destination Media Synchronization (IDMS). Inter-Destination Media Synchronization (IDMS).
+------------+----------------+-------+----------+ +------------+----------------+-------+--------------+
| Name | Notes | Level | 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 - OMA BCAST SDP Attributes
[RFC5159] provides descriptions of Session Description Protocol (SDP) [RFC5159] provides descriptions of Session Description Protocol (SDP)
attributes used by the Open Mobile Alliance's Broadcast Service and attributes used by the Open Mobile Alliance's Broadcast Service and
Content Protection specification. Content Protection specification.
+---------------------+---------------+-------+----------+ +---------------------+---------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+---------------------+---------------+-------+----------+ +---------------------+---------------+-------+--------------+
| bcastversion | Not Impacted | S | NORMAL | | bcastversion | Not Impacted | S | NORMAL |
| | | | | | | | | |
| stkmstream | Not Impacted | B | NORMAL | | stkmstream | Not Impacted | B | NORMAL |
| | | | | | | | | |
| SRTPAuthentication | Not Impacted | M | NORMAL | | SRTPAuthentication | Not Impacted | M | NORMAL |
| | | | | | | | | |
| SRTPROCTxRate | Not Impacted | M | NORMAL | | SRTPROCTxRate | Not Impacted | M | NORMAL |
| | | | | | | | | |
+---------------------+---------------+-------+----------+ +---------------------+---------------+-------+--------------+
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 the Session Description Protocol
(SDP) so that it can negotiate use of the Internet Key Exchange (SDP) so that it can negotiate use of the Internet Key Exchange
Protocol (IKE) for media sessions in the SDP offer/answer model. Protocol (IKE) for media sessions in the SDP offer/answer model.
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | 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 |
| | identical across all the | | | | | identical across all the | | |
| | m=lines | | | | | m=lines | | |
| | | | | | | | | |
| ike-esp | Attribute MUST be | B | IDENTICAL | | ike-esp | Attribute MUST be | B | IDENTICAL |
skipping to change at page 39, line 6 skipping to change at page 38, line 17
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 | Category | | Name | Notes | Level | Mux Category |
+----------+---------------------------------+-------+--------------+ +----------+---------------------------------+-------+--------------+
| etag | RTSP is not supported for RTP | B | NOT | | etag | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED | | | Stream multiplexing | | RECOMMENDED |
| | | | | | | | | |
| range | RTSP is not supported for RTP | B | NOT | | range | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED | | | Stream multiplexing | | RECOMMENDED |
| | | | | | | | | |
| control | RTSP is not supported for RTP | B | NOT | | control | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED | | | Stream multiplexing | | RECOMMENDED |
| | | | | | | | | |
skipping to change at page 39, line 33 skipping to change at page 38, line 44
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 the Session
Description Protocol (SDP) and Real Time Streaming Protocol (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 | Category | | Name | Notes | Level | Mux Category |
+-------------------------------+------------+-------+--------------+ +-------------------------------+------------+-------+--------------+
| X-predecbufsize | Refer to | M | NOT | | X-predecbufsize | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| X-initpredecbufperiod | Refer to | M | NOT | | X-initpredecbufperiod | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| X-initpostdecbufperiod | Refer to | M | NOT | | X-initpostdecbufperiod | Refer to | M | NOT |
skipping to change at page 40, line 38 skipping to change at page 39, line 49
| | below | | | | | below | | |
| | | | | | | | | |
| alt-group | Refer to | M | NOT | | alt-group | Refer to | M | 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-Informatio | Refer to | B | NOT | | 3GPP-Asset-Information | Refer to | B | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| mbms-mode | Refer to | B | NOT | | mbms-mode | Refer to | B | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| mbms-flowid | Refer to | M | NOT | | mbms-flowid | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| mbms-repair | Refer to | B | NOT | | mbms-repair | Refer to | B | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics | Refer to | M | NOT |
| | notes | | RECOMMENDED |
| | below | | |
| | | | |
| 3GPP-QoE-Metrics:Corruption | Refer to | M | NOT | | 3GPP-QoE-Metrics:Corruption | Refer to | M | NOT |
| duration | notes | | RECOMMENDED | | duration | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Rebuffering | Refer to | M | NOT | | 3GPP-QoE-Metrics:Rebuffering | Refer to | M | NOT |
| duration | notes | | RECOMMENDED | | duration | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Initial | Refer to | M | NOT | | 3GPP-QoE-Metrics:Initial | Refer to | M | NOT |
| buffering duration | notes | | RECOMMENDED | | buffering duration | notes | | RECOMMENDED |
skipping to change at page 41, line 35 skipping to change at page 40, line 50
| | | | | | | | | |
| 3GPP-QoE-Metrics:Jitter | Refer to | M | NOT | | 3GPP-QoE-Metrics:Jitter | Refer to | M | NOT |
| duration | notes | | RECOMMENDED | | duration | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Content | Refer to | B | NOT | | 3GPP-QoE-Metrics:Content | Refer to | B | NOT |
| Switch Time | notes | | RECOMMENDED | | Switch Time | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Average | Refer to | M | NOT | | 3GPP-QoE-Metrics:Average | Refer to | M | NOT |
| Codec Bitrat | notes | | RECOMMENDED | | Codec Bitrate | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Codec | Refer to | M | NOT | | 3GPP-QoE-Metrics:Codec | Refer to | M | NOT |
| Information | notes | | RECOMMENDED | | Information | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Buffer | Refer to | M | NOT | | 3GPP-QoE-Metrics:Buffer | Refer to | M | NOT |
| Status | notes | | RECOMMENDED | | Status | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
skipping to change at page 42, line 13 skipping to change at page 41, line 28
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 [RFC3108] describes conventions for using the Session RFC3108 [RFC3108] describes conventions for using the Session
Description Protocol (SDP) described for controlling ATM Bearer Description Protocol (SDP) described for controlling ATM Bearer
Connections, and any associated ATM Adaptation Layer (AAL). Connections, and any associated ATM Adaptation Layer (AAL).
+------------------------+--------------+-------+----------+ +------------------------+--------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+------------------------+--------------+-------+----------+ +------------------------+--------------+-------+--------------+
| aalType | Not Impacted | B | NORMAL | | aalType | Not Impacted | B | NORMAL |
| eecid | Not Impacted | B | NORMAL | | eecid | Not Impacted | B | NORMAL |
| aalType | Not Impacted | B | NORMAL | | aalType | Not Impacted | B | NORMAL |
| capability | Not Impacted | B | NORMAL | | capability | Not Impacted | B | NORMAL |
| qosClass | Not Impacted | B | NORMAL | | qosClass | Not Impacted | B | NORMAL |
| bcob | Not Impacted | B | NORMAL | | bcob | Not Impacted | B | NORMAL |
| stc | Not Impacted | B | NORMAL | | stc | Not Impacted | B | NORMAL |
| upcc | Not Impacted | B | NORMAL | | upcc | Not Impacted | B | NORMAL |
| atmQOSparms | Not Impacted | B | NORMAL | | atmQOSparms | Not Impacted | B | NORMAL |
| atmTrfcDesc | Not Impacted | B | NORMAL | | atmTrfcDesc | Not Impacted | B | NORMAL |
| abrParms | Not Impacted | B | NORMAL | | abrParms | Not Impacted | B | NORMAL |
| abrSetup | Not Impacted | B | NORMAL | | abrSetup | Not Impacted | B | NORMAL |
| bearerType | Not Impacted | B | NORMAL | | bearerType | Not Impacted | B | NORMAL |
| lij | Not Impacted | B | NORMAL | | lij | Not Impacted | B | NORMAL |
| anycast | Not Impacted | B | NORMAL | | anycast | Not Impacted | B | NORMAL |
| cache | Not Impacted | B | NORMAL | | cache | Not Impacted | B | NORMAL |
| bearerSigIE | Not Impacted | B | NORMAL | | bearerSigIE | Not Impacted | B | NORMAL |
| aalApp | Not Impacted | B | NORMAL | | aalApp | Not Impacted | B | NORMAL |
| cbrRate | Not Impacted | B | NORMAL | | cbrRate | Not Impacted | B | NORMAL |
| sbc | Not Impacted | B | NORMAL | | sbc | Not Impacted | B | NORMAL |
| clkrec | Not Impacted | B | NORMAL | | clkrec | Not Impacted | B | NORMAL |
| fec | Not Impacted | B | NORMAL | | fec | Not Impacted | B | NORMAL |
| prtfl | Not Impacted | B | NORMAL | | prtfl | Not Impacted | B | NORMAL |
| structure | Not Impacted | B | NORMAL | | structure | Not Impacted | B | NORMAL |
| cpsSDUsize | Not Impacted | B | NORMAL | | cpsSDUsize | Not Impacted | B | NORMAL |
| aal2CPS | Not Impacted | B | NORMAL | | aal2CPS | Not Impacted | B | NORMAL |
| aal2CPSSDUrate | Not Impacted | B | NORMAL | | aal2CPSSDUrate | Not Impacted | B | NORMAL |
| aal2sscs3661unassured | Not Impacted | B | NORMAL | | aal2sscs3661unassured | Not Impacted | B | NORMAL |
| aal2sscs3661assured | Not Impacted | B | NORMAL | | aal2sscs3661assured | Not Impacted | B | NORMAL |
| aal2sscs3662 | Not Impacted | B | NORMAL | | aal2sscs3662 | Not Impacted | B | NORMAL |
| aal5sscop | Not Impacted | B | NORMAL | | aal5sscop | Not Impacted | B | NORMAL |
| atmmap | Not Impacted | B | NORMAL | | atmmap | Not Impacted | B | NORMAL |
| silenceSupp | Not Impacted | B | NORMAL | | silenceSupp | Not Impacted | B | NORMAL |
| ecan | Not Impacted | B | NORMAL | | ecan | Not Impacted | B | NORMAL |
| gc | Not Impacted | B | NORMAL | | gc | Not Impacted | B | NORMAL |
| profileDesc | Not Impacted | B | NORMAL | | profileDesc | Not Impacted | B | NORMAL |
| vsel | Not Impacted | B | NORMAL | | vsel | Not Impacted | B | NORMAL |
| dsel | Not Impacted | B | NORMAL | | dsel | Not Impacted | B | NORMAL |
| fsel | Not Impacted | B | NORMAL | | fsel | Not Impacted | B | NORMAL |
| onewaySel | Not Impacted | B | NORMAL | | onewaySel | Not Impacted | B | NORMAL |
| codecconfig | Not Impacted | B | NORMAL | | codecconfig | Not Impacted | B | NORMAL |
| isup_usi | Not Impacted | B | NORMAL | | isup_usi | Not Impacted | B | NORMAL |
| isup_usi | Not Impacted | B | NORMAL | | uiLayer1_Prot | Not Impacted | B | NORMAL |
| chain | Not Impacted | B | NORMAL | | chain | Not Impacted | B | NORMAL |
| | | | | | | | | |
+------------------------+--------------+-------+----------+ +------------------------+--------------+-------+--------------+
RFC3108 Attribute Analysis RFC3108 Attribute Analysis
RFC3108 describes conventions for using the Session Description RFC3108 describes conventions for using the Session Description
Protocol (SDP) for characterizing ATM bearer connections using an Protocol (SDP) for characterizing ATM bearer connections using an
AAL1, AAL2 or AAL5 adaptation layers. For AAL1, AAL2 and AAL5, AAL1, AAL2 or AAL5 adaptation layers. For AAL1, AAL2 and AAL5,
bearer connections can be used to transport single media streams. In bearer connections can be used to transport single media streams. In
addition, for AAL1 and AAL2, multiple media streams may be addition, for AAL1 and AAL2, multiple media streams may be
multiplexed into a bearer connection. For all adaptation types multiplexed into a bearer connection. For all adaptation types
(AAL1, AAL2 and AAL5), bearer connections may be bundled into a (AAL1, AAL2 and AAL5), bearer connections may be bundled into a
skipping to change at page 43, line 36 skipping to change at page 43, line 4
or a multiplex of media streams is mapped directly into an ATM or a multiplex of media streams is mapped directly into an ATM
connection. RFC3108 does not address cases where ATM serves as a connection. RFC3108 does not address cases where ATM serves as a
low-level transport pipe for IP packets which in turn may carry one low-level transport pipe for IP packets which in turn may carry one
or more real-time (e.g. VoIP) media sessions with a life-cycle or more real-time (e.g. VoIP) media sessions with a life-cycle
different from that of the underlying ATM transport. different from that of the underlying ATM 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 | Category | | Name | Notes | Level | Mux |
| | | | 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 | | |
| | | | | | | | | |
+----------------------+-------------------------+-------+----------+ +----------------------+-------------------------+-------+----------+
3GPP TS 26.114 Attribute Analysis 3GPP TS 26.114 Attribute Analysis
5.50. 3GPP TS 183.063 5.50. 3GPP TS 183.063
[R3GPPTS183.063] Telecommunications and Internet converged Services [R3GPPTS183.063] Telecommunications and Internet converged Services
and Protocols for Advanced Networking (TISPAN); and Protocols for Advanced Networking (TISPAN);
+---------------------+---------------+----------------+----------+ +---------------------+--------------+----------------+-------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
+---------------------+---------------+----------------+----------+ | | | | Category |
| PSCid | Not Impacted | Not-ApplIcable | NORMAL | +---------------------+--------------+----------------+-------------+
| | | | | | PSCid | Not Impacted | Not-Applicable | NORMAL |
| bc_service | Not Impacted | Not-AppIlcable | NORMAL | | | | | |
| | | | | | bc_service | Not Impacted | Not-Applicable | NORMAL |
| bc_program | Not Impacted | Not-AppIlcable | NORMAL | | | | | |
| | | | | | bc_program | Not Impacted | Not-Applicable | NORMAL |
| bc_service_package | Not Impacted | Not-Appilcable | NORMAL | | | | | |
| | | | | | bc_service_package | Not Impacted | Not-Applicable | NORMAL |
+---------------------+---------------+----------------+----------+ | | | | |
+---------------------+--------------+----------------+-------------+
3GPP TS 183.063 Attribute Analysis 3GPP TS 183.063 Attribute Analysis
5.51. 3GPP TS 24.182 5.51. 3GPP TS 24.182
[R3GPPTS24.182] specifies IP multimedia subsystem Custom Alerting [R3GPPTS24.182] specifies IP multimedia subsystem Custom Alerting
tones tones
+-------------+---------------------------------+-------+-----------+
+-------------+----------------------------------+-------+----------+ | Name | Notes | Level | Mux |
| Name | Notes | Level | Category | | | | | Category |
+-------------+----------------------------------+-------+----------+ +-------------+---------------------------------+-------+-----------+
| g.3gpp.cat | Usage defined for the IP | M | NORMAL | | g.3gpp.cat | Usage defined for the IP | M | NORMAL |
| | Multimedia Subsystem | | | | | Multimedia Subsystem | | |
| | | | | | | | | |
+-------------+----------------------------------+-------+----------+ +-------------+---------------------------------+-------+-----------+
3GPP TS 24.182 Attribute Analysis 3GPP TS 24.182 Attribute Analysis
5.52. 3GPP TS 24.183 5.52. 3GPP TS 24.183
[R3GPPTS24.183] specifies IP multimedia subsystem Custom Ringing [R3GPPTS24.183] specifies IP multimedia subsystem Custom Ringing
Signal Signal
+-------------+----------------------------------+-------+----------+
| Name | Notes | Level | Category | +-------------+---------------------------------+-------+-----------+
+-------------+----------------------------------+-------+----------+ | Name | Notes | Level | Mux |
| g.3gpp.crs | Usage defined for the IP | M | NORMAL | | | | | Category |
| | Multimedia Subsystem | | | +-------------+---------------------------------+-------+-----------+
| | | | | | g.3gpp.crs | Usage defined for the IP | M | NORMAL |
+-------------+----------------------------------+-------+----------+ | | Multimedia Subsystem | | |
| | | | |
+-------------+---------------------------------+-------+-----------+
3GPP TS 24.183 Attribute Analysis 3GPP TS 24.183 Attribute Analysis
5.53. 3GPP TS 24.229 5.53. 3GPP TS 24.229
[R3GPPTS24.229] specifies IP multimedia call control protocol based [R3GPPTS24.229] specifies IP multimedia call control protocol based
on Session Initial protocol and Session Description Protocol. on Session Initial protocol and Session Description Protocol.
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| secondary-realm | Per media-level attribute | M | TRANSPORT | | secondary-realm | secondary-realm must be | M | TRANSPORT |
| | MUST be used per | | | | | the one that corresponds | | |
| | underlying transport | | | | | to the m=line chosen for | | |
| | setting up the underlying | | |
| | transport flow. | | |
| | | | | | | | | |
| visited-realm | Per media-level attribute | M | TRANSPORT | | visited-realm | visited-realm must be | M | TRANSPORT |
| | MUST be used per | | | | | the one that corresponds | | |
| | underlying transport | | | | | to the m=line chosen for | | |
| | setting up the underlying | | |
| | transport flow. | | |
| | | | | | | | | |
| omr-m-cksum | Not Impacted | M | NORMAL | | omr-m-cksum | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-s-cksum | Not Impacted | M | NORMAL | | omr-s-cksum | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-m-att | Not Impacted | M | NORMAL | | omr-m-att | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-s-bw | Not Impacted | M | NORMAL | | omr-s-att | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-s-bw | Not Impacted | M | NORMAL | | omr-m-bw | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-m-att | Not Impacted | M | NORMAL | | omr-s-bw | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-codecs | Not Impacted | M | NORMAL | | omr-codecs | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
3GPP TS 24.229 Attribute Analysis 3GPP TS 24.229 Attribute Analysis
5.54. ITU T.38 5.54. ITU T.38
[T.38] defines procedures for real-time Group 3 facsimile [T.38] defines procedures for real-time Group 3 facsimile
communications over IP networks. communications over IP networks.
+------------------------+---------------+-------+----------+ +------------------------+---------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+------------------------+---------------+-------+----------+ +------------------------+---------------+-------+--------------+
| T38FaxVersion | Not Impacted | S | NORMAL | | T38FaxVersion | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38MaxBitRate | Not Impacted | S | NORMAL | | T38MaxBitRate | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxFillBitRemoval | Not Impacted | S | NORMAL | | T38FaxFillBitRemoval | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxTranscodingMMR | Not Impacted | S | NORMAL | | T38FaxTranscodingMMR | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxTranscodingJBIG | Not Impacted | S | NORMAL | | T38FaxTranscodingJBIG | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxRateManagement | Not Impacted | S | NORMAL | | T38FaxRateManagement | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxMaxBuffer | Not Impacted | S | NORMAL | | T38FaxMaxBuffer | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxMaxDatagram | Not Impacted | S | NORMAL | | T38FaxMaxDatagram | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxUdpEC | Not Impacted | S | NORMAL | | T38FaxUdpEC | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxMaxIFP | Not Impacted | S | NORMAL | | T38FaxMaxIFP | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxUdpECDepth | Not Impacted | S | NORMAL | | T38FaxUdpECDepth | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxUdpFECMaxSpan | Not Impacted | S | NORMAL | | T38FaxUdpFECMaxSpan | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38ModemType | Not Impacted | S | NORMAL | | T38ModemType | Not Impacted | S | NORMAL |
| | | | | | | | | |
+------------------------+---------------+-------+----------+ | T38VendorInfo | Not Impacted | S | NORMAL |
| | | | |
+------------------------+---------------+-------+--------------+
ITU T.38 Attribute Analysis ITU T.38 Attribute Analysis
The ITU T.38 attributes are clearly unaffected by multiplexing and The ITU T.38 attributes are clearly unaffected by multiplexing and
are specific to the working of the fax protocol itself. are specific to the working of the fax protocol itself.
5.55. ITU-T-REC.Q1970 5.55. ITU-T-REC.Q1970
[ITU-T-REC.Q1970] defines BICC IP bearer control protocol. [ITU-T-REC.Q1970] defines BICC IP bearer control protocol.
+--------+---------------+-------+----------+ +--------+---------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+--------+---------------+-------+----------+ +--------+---------------+-------+--------------+
| ipbcp | Not Impacted | S | NORMAL | | ipbcp | Not Impacted | S | NORMAL |
| | | | | | | | | |
+--------+---------------+-------+----------+ +--------+---------------+-------+--------------+
ITU-T-REC.Q1970 Attribute Analysis ITU-T-REC.Q1970 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 | Category | | Name | Notes | Level | Mux |
| | | | Category |
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| h248item | It is also 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 may | | |
| | 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. | | |
skipping to change at page 48, line 5 skipping to change at page 48, line 7
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 | Category | | Name | Notes | Level | Mux Category |
+-----------------------+---------------+-------+----------+ +-----------------------+---------------+-------+--------------+
| accept-types | Not Impacted | M | NORMAL | | accept-types | Not Impacted | M | NORMAL |
| | | | | | | | | |
| accept-wrapped-types | Not Impacted | M | NORMAL | | accept-wrapped-types | Not Impacted | M | NORMAL |
| | | | | | | | | |
| max-size | Not Impacted | M | NORMAL | | max-size | Not Impacted | M | NORMAL |
| | | | | | | | | |
| path | Not Impacted | M | NORMAL | | path | Not Impacted | M | NORMAL |
| | | | | | | | | |
+-----------------------+---------------+-------+----------+ +-----------------------+---------------+-------+--------------+
RFC4975 Attribute Analysis RFC4975 Attribute Analysis
5.58. RFC4574 - SDP Label Attribute 5.58. Historical Attributes
[RFC4574] defines a new Session Description Protocol (SDP) media-
level attribute: "label". The "label" attribute carries a pointer to
a media stream in the context of an arbitrary network application
that uses SDP. The sender of the SDP document can attach the "label"
attribute to a particular media stream or streams. The application
can then use the provided pointer to refer to each particular media
stream in its context.
+--------+---------------+-------+----------+
| Name | Notes | Level | Category |
+--------+---------------+-------+----------+
| label | Not Impacted | M | NORMAL |
| | | | |
+--------+---------------+-------+----------+
RFC4574 Attribute Analysis
5.59. Historical Attributes
This section specifies analysis for the attributes that are included This section specifies analysis for the attributes that are included
for historic usage alone by the [IANA]. for historic usage alone by the [IANA].
+----------+---------------------+----------------+-----------------+ +----------+---------------------+----------------+-----------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+----------+---------------------+----------------+-----------------+ +----------+---------------------+----------------+-----------------+
| rtpred1 | Historic | Not-Applicable | NOT RECOMMENDED | | rtpred1 | Historic | Not-Applicable | NOT RECOMMENDED |
| | attributes. | | | | | attributes. | | |
| | | | | | | | | |
| rtpred2 | Historic | Not-Applicable | NOT RECOMMENDED | | rtpred2 | Historic | Not-Applicable | NOT RECOMMENDED |
| | attributes. | | | | | attributes. | | |
| | | | | | | | | |
+----------+---------------------+----------------+-----------------+ +----------+---------------------+----------------+-----------------+
Historical Attribute Analysis Historical Attribute Analysis
skipping to change at page 49, line 24 skipping to change at page 49, line 4
+----------+---------------------+----------------+-----------------+ +----------+---------------------+----------------+-----------------+
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: Session Description Protocol
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| bwtype:CT | Not Impacted | S | NORMAL | | bwtype:CT | Not Impacted | S | NORMAL |
| | | | | | | | | |
| bwtype:AS | As a session attribute, it | B | NORMAL |
| | specifies the session aggregate | | |
| | unless media-level b=RR and/or | | |
| | b=RS attributes are used. Under | | |
| | this interpretation the | | |
| | multiplexing scheme has no impact | | |
| | and thus NORMAL category applies. | | |
| | | | |
| 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 the Session Description Protocol
(SDP) to specify two additional modifiers for the bandwidth (SDP) to specify two additional modifiers for the bandwidth
attribute. These modifiers may be used to specify the bandwidth attribute. These modifiers may be used to specify the bandwidth
allowed for RTP Control Protocol (RTCP) packets in a Real-time allowed for RTP Control Protocol (RTCP) packets in a Real-time
Transport Protocol (RTP) session. Transport Protocol (RTP) session.
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| bwtype:RS | Session level usage represents | B | NORMAL | | bwtype:RS | Session level usage represents | B | SUM |
| | session aggregate and media level | | | | | session aggregate and media level | | |
| | usage indicates SUM of the | | | | | usage indicates SUM of the | | |
| | individual values while | | | | | individual values while | | |
| | multiplexing | | | | | multiplexing | | |
| | | | | | | | | |
| bwtype:RR | Session level usage represents | B | NORMAL | | 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 a Session Description Protocol (SDP) Transport
Independent Application Specific Maximum (TIAS) bandwidth modifier Independent Application Specific Maximum (TIAS) bandwidth modifier
that does not include transport overhead; instead an additional that does not include transport overhead; instead an additional
packet rate attribute is defined. The transport independent bit-rate packet rate attribute is defined. The transport independent bit-rate
value together with the maximum packet rate can then be used to value together with the maximum packet rate can then be used to
calculate the real bit-rate over the transport actually used. calculate the real bit-rate over the transport actually used.
+------------------+-----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | Category |
+------------------+-----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| bwtype:TIAS | The usage of TIAS is not | B | SPECIAL | | bwtype:TIAS | The usage of TIAS is not | B | SPECIAL |
| | clearly defined | | | | | clearly defined | | |
| | Offer/Answer usage. | | | | | Offer/Answer usage. | | |
| | | | | | | | | |
| bwtype:maxprate | The usage of TIAS and | B | SPECIAL | | bwtype:maxprate | The usage of TIAS and | B | SPECIAL |
| | maxprate is not well | | | | | maxprate is not well | | |
| | defined under multiplexing | | | | | defined under multiplexing | | |
| | | | | | | | | |
+------------------+-----------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
RFC3890 bwtype Analysis RFC3890 bwtype Analysis
The intention of TIAS is that the media level bit-rate is multiplied The intention of TIAS is that the media level bit-rate is multiplied
with the known per-packet overhead for the selected transport and the with the known per-packet overhead for the selected transport and the
maxprate value to determine the worst case bit-rate from the maxprate value to determine the worst case bit-rate from the
transport to more accurately capture the required usage. Summing transport to more accurately capture the required usage. Summing
TIAS values independently across m=lines and multiplying the computed TIAS values independently across m=lines and multiplying the computed
sum with maxprate and the per-packet overhead would inflate the value sum with maxprate and the per-packet overhead would inflate the value
significantly. Instead performing multiplication and adding the significantly. Instead performing multiplication and adding the
individual values is a more appropriate usage. This still ignores individual values is a more appropriate usage.
the fact that this is a send side declaration, and not intended for
receiver negotiation.
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.
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| Attr | Notes | Level | Category | | Attr | Notes | Level | Mux Category |
| Name | | | | | Name | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| ack rpsi | The attribute value must | M | IDENTICAL-PER-PT | | ack rpsi | The attribute value must | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ack app | Feedback parameters MUST | M | SPECIAL | | ack app | Feedback parameters MUST | M | SPECIAL |
| | be handled in the app | | | | | be handled in the app | | |
| | specific way when | | | | | specific way when | | |
| | multiplexed | | | | | multiplexed | | |
skipping to change at page 53, line 8 skipping to change at page 52, line 8
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.
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| Attr | Notes | Level | Category | | Attr | Notes | Level | Mux Category |
| Name | | | | | Name | | | |
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| 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 RAMS
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| Name | Notes | Level | 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
skipping to change at page 54, line 6 skipping to change at page 53, line 6
[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 Real-time Transport Protocol (RTP) running over UDP,
using the RTP Control Protocol (RTCP) as a feedback mechanism. It using the RTP Control Protocol (RTCP) as a feedback mechanism. It
defines a new RTCP Extended Report (XR) block for periodic ECN defines a new RTCP Extended Report (XR) block for periodic ECN
feedback, a new RTCP transport feedback message for timely reporting feedback, a new RTCP transport feedback message for timely reporting
of congestion events, and a Session Traversal Utilities for NAT of congestion events, and a Session Traversal Utilities for NAT
(STUN) extension used in the optional initialization method using (STUN) extension used in the optional initialization method using
Interactive Connectivity Establishment (ICE). Interactive Connectivity Establishment (ICE).
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
| | | | 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 | | |
| | | | | | | | | |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
skipping to change at page 54, line 36 skipping to change at page 53, line 37
allowing them to avoid sending duplicate feedback reports. However, allowing them to avoid sending duplicate feedback reports. However,
there are cases where it is not recommended to forward feedback there are cases where it is not recommended to forward feedback
reports, and this may allow feedback implosion. [RFC6642] memo reports, and this may allow feedback implosion. [RFC6642] memo
discusses these cases and defines a new RTCP Third-Party Loss Report discusses these cases and defines a new RTCP Third-Party Loss Report
that can be used to inform receivers that the feedback target is that can be used to inform receivers that the feedback target is
aware of some loss event, allowing them to suppress feedback. aware of some loss event, allowing them to suppress feedback.
Associated Session Description Protocol (SDP) signaling is also Associated Session Description Protocol (SDP) signaling is also
defined. defined.
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Name | Notes | Level | 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
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Attr | Notes | Level | Category | | Attr | Notes | Level | Mux Category |
| Name | | | | | Name | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value must be | M | IDENTICAL-PER-PT |
| fir | same for a given codec | | | | fir | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value must be | M | IDENTICAL-PER-PT |
| tmmbr | same for a given codec | | | | tmmbr | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
skipping to change at page 55, line 40 skipping to change at page 54, line 40
8. group Attribute Analysis 8. group Attribute Analysis
This section analyzes SDP "group" semantics. This section analyzes SDP "group" semantics.
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 the Session
Description Protocol (SDP) for different purposes. Description Protocol (SDP) for different purposes.
+------------+---------------+-------+----------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | 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 Session Description Protocol
(SDP) grouping framework. It allows requesting a group of media (SDP) grouping framework. It allows requesting a group of media
streams to be mapped into a single resource reservation flow. The streams to be mapped into a single resource reservation flow. The
SDP syntax needed is defined, as well as a new "semantics" attribute SDP syntax needed is defined, as well as a new "semantics" attribute
called Single Reservation Flow (SRF). called Single Reservation Flow (SRF).
+------------+---------------+-------+----------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | 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 the Alternative Network Address Types (ANAT)
semantics for the Session Description Protocol (SDP) grouping semantics for the Session Description Protocol (SDP) grouping
framework. The ANAT semantics allow alternative types of network framework. The ANAT semantics allow alternative types of network
addresses to establish a particular media stream. addresses to establish a particular media stream.
+-------------+---------------------------+-------+-----------------+ +-------------+---------------------------+-------+-----------------+
| Name | Notes | Level | 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
skipping to change at page 57, line 5 skipping to change at page 56, line 5
and FEC-based (Forward Error Correction) repair flows in the Session and FEC-based (Forward Error Correction) repair flows in the Session
Description Protocol (SDP). The semantics defined in the document Description Protocol (SDP). The semantics defined in the document
are to be used with the SDP Grouping Framework (RFC 5888). These are to be used with the SDP Grouping Framework (RFC 5888). These
semantics allow the description of grouping relationships between the semantics allow the description of grouping relationships between the
source and repair flows when one or more source and/or repair flows source and repair flows when one or more source and/or repair flows
are associated in the same group, and they provide support for are associated in the same group, and they provide support for
additive repair flows. SSRC-level (Synchronization Source) grouping additive repair flows. SSRC-level (Synchronization Source) grouping
semantics are also defined in this document for Real-time Transport semantics are also defined in this document for Real-time Transport
Protocol (RTP) streams using SSRC multiplexing. Protocol (RTP) streams using SSRC multiplexing.
+---------------+---------------+-------+----------+ +---------------+---------------+-------+--------------+
| Name | Notes | Level | 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 the Session Description Protocol (SDP). This is required, for
example, if media data is separated and transported in different example, if media data is separated and transported in different
network streams as a result of the use of a layered or multiple network streams as a result of the use of a layered or multiple
descriptive media coding process. descriptive media coding process.
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| depend | The attribute value must be | M | IDENTICAL-PER-PT | | depend | The attribute value must be | M | IDENTICAL-PER-PT |
| lay | same for a given codec | | | | lay | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| depend | The attribute value must be | M | IDENTICAL-PER-PT | | depend | The attribute value must be | M | IDENTICAL-PER-PT |
| mdc | same for a given codec | | | | mdc | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
skipping to change at page 58, line 5 skipping to change at page 57, line 5
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 the
Session Description Protocol (SDP). The semantics defined in this Session Description Protocol (SDP). The semantics defined in this
document are to be used with the SDP Grouping Framework. Grouping document are to be used with the SDP Grouping Framework. Grouping
semantics at the Synchronization Source (SSRC) level are also defined semantics at the Synchronization Source (SSRC) level are also defined
in this document for RTP streams using SSRC multiplexing. in this document for RTP streams using SSRC multiplexing.
+------------+---------------+-------+----------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | 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
+-------------------+---------------+-------+----------+ +-------------------+---------------+-------+--------------+
| Name | Notes | Level | 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-groupFEC-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
+-----------------+---------------+-------+----------+ +-----------------+---------------+-------+--------------+
| Name | Notes | Level | 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
+-------+----------------------------------------+-------+----------+ +-------+---------------------------------------+-------+-----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux |
+-------+----------------------------------------+-------+----------+ | | | | Category |
| rsvp | Not Impacted, since QOS mechanisms are | B | NORMAL | +-------+---------------------------------------+-------+-----------+
| | applied per flow. | | | | rsvp | Not Impacted, since QOS mechanisms | B | NORMAL |
| | | | | | | are applied per flow. | | |
| nsis | Not Impacted, since QOS mechanisms are | B | NORMAL | | | | | |
| | applied per flow. | | | | nsis | Not Impacted, since QOS mechanisms | B | NORMAL |
| | | | | | | are applied per flow. | | |
+-------+----------------------------------------+-------+----------+ | | | | |
+-------+---------------------------------------+-------+-----------+
RFC5432 Attribute Analysis RFC5432 Attribute Analysis
11. k= Attribute Analysis 11. k= Attribute Analysis
11.1. RFC4566 SDP: Session Description Protocol 11.1. RFC4566 SDP: Session Description Protocol
+------+------------------------------------+-------+---------------+ +------+------------------------------------+-------+---------------+
| Name | Notes | Level | 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
+------------------+---------------+-------+----------+ +------------------+---------------+-------+--------------+
| Name | Notes | Level | 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.
+---------------------+----------------------+-------+--------------+ +---------------------+----------------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Mux Category |
+---------------------+----------------------+-------+--------------+ +---------------------+----------------------+-------+--------------+
| audio/ulpfec | Not recommended for | M | NOT | | audio/ulpfec | Not recommended for | M | NOT |
| | multiplexing due to | | RECOMMENDED | | | multiplexing due to | | RECOMMENDED |
| | reuse of SSRCs | | | | | reuse of SSRCs | | |
| | | | | | | | | |
| video/ulpfec | Not recommended for | M | NOT | | video/ulpfec | Not recommended for | M | NOT |
| | multiplexing due to | | RECOMMENDED | | | multiplexing due to | | RECOMMENDED |
| | reuse of SSRCs | | | | | reuse of SSRCs | | |
| | | | | | | | | |
| text/ulpfec | Not recommended for | M | NOT | | text/ulpfec | Not recommended for | M | NOT |
skipping to change at page 63, line 7 skipping to change at page 62, line 7
Although it is possible to analyze the various potential Although it is possible to analyze the various potential
configurations in bundled media descriptions to find combinations configurations in bundled media descriptions to find combinations
that satisfy such constraints, it can quickly become complicated to that satisfy such constraints, it can quickly become complicated to
do so. do so.
The procedures defined in [RFC5939] state that each potential The procedures defined in [RFC5939] state that each potential
configuration in the SDP has a unique configuration number, however configuration in the SDP has a unique configuration number, however
the scope of uniqueness is limited to each media description. To the scope of uniqueness is limited to each media description. To
make it simple for the answerer to chose valid combinations of make it simple for the answerer to chose valid combinations of
potential configurations across media descriptions in a given bundle potential configurations across media descriptions in a given bundle
group, we provide a simple rule for constructiong potential group, we provide a simple rule for constructing potential
configurations:- configurations:-
o Let m-bundle be the set of media descriptions that form a given o Let m-bundle be the set of media descriptions that form a given
bundle . bundle .
o Let m-bundle-pcfg be the set of media descriptions in m-bundle o Let m-bundle-pcfg be the set of media descriptions in m-bundle
that include one or more potential configurations. that include one or more potential configurations.
o Each media description in m-bundle-pcfg MUST have at least one o Each media description in m-bundle-pcfg MUST have at least one
potential configuration with the same configuration number (e.g. potential configuration with the same configuration number (e.g.
skipping to change at page 67, line 15 skipping to change at page 66, line 15
configurations with bundled media. It is still allowed to use the configurations with bundled media. It is still allowed to use the
latent configuration attribute, however the limitations above will latent configuration attribute, however the limitations above will
apply. To determine valid combinations, actual negotiation will have apply. To determine valid combinations, actual negotiation will have
to be attempted subsequently instead. to be attempted subsequently instead.
15. IANA Considerations 15. IANA Considerations
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
document.] document.]
The IANA is requested to add a new column named "Mux Category" to all The IANA is requested to add a new column named "Mux Category" to
several of the subregistries in the "Session Description Protocol several of the subregistries in the "Session Description Protocol
(SDP) Parameters" registry. Section 15.1 defines a new subregistry (SDP) Parameters" registry. Section 15.1 defines a new subregistry
for identifying the initial registrations for various multiplexing for identifying the initial registrations for various multiplexing
categories applicable as proposed in this document. categories applicable, as proposed in this document.
The tables in Section 15.2 identify name of an entry in the existing The tables in Section 15.2 identify name of an entry in the existing
subregistry and specify the value to put in the new "Mux Category" subregistry and specify the value to put in the new "Mux Category"
column of the associated IANA registry. Any entries in the existing column of the associated IANA registry. Any entries in the existing
tables that do not have a value for the "Mux Category" specified in tables that do not have a value for the "Mux Category" specified in
this RFC will get a value of "TBD". Future specifications can change this RFC will get a value of "TBD". Future specifications can change
the "TBD" entries to the correct value. the "TBD" entries to the correct value.
15.1. New 'Multiplexing Categories' subregistry 15.1. New 'Multiplexing Categories' subregistry
A new sub-registry needs to be defined called the "Multiplexing A new sub-registry needs to be defined called the "Multiplexing
Categories", with the following registrations created initially: Categories", with the following registrations created initially:
"NORMAL", "NOT RECOMMENDED", "IDENTICAL", "TRANSPORT", "IDENTICAL- "NORMAL", "NOT RECOMMENDED", "IDENTICAL", "TRANSPORT", "SUM",
PER-PT", "SPECIAL" and "TBD" as defined in this document. "INHERIT", "IDENTICAL-PER-PT", "SPECIAL" and "TBD" as defined in this
document.
Initial value registration for "Mux Category". Initial value registration for "Multiplexing Categories".
+-------------------------+-----------+ +-------------------------+-----------+
| Multiplexing Categories | Reference | | Multiplexing Categories | Reference |
+-------------------------+-----------+ +-------------------------+-----------+
| NORMAL | RFCXXXX | | NORMAL | RFCXXXX |
| NOT RECOMMENDED | RFCXXXX | | NOT RECOMMENDED | RFCXXXX |
| IDENTICAL | RFCXXXX | | IDENTICAL | RFCXXXX |
| TRANSPORT | RFCXXXX | | TRANSPORT | RFCXXXX |
| SUM | 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 may 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 68, line 33 skipping to change at page 67, line 35
The following values are to be added to the 'SDP bwtype' subregistry The following values are to be added to the 'SDP bwtype' subregistry
in the "Session Description Protocol (SDP) Parameters" registry. The in the "Session Description Protocol (SDP) Parameters" registry. The
references should be updated to point at this RFC as well as the references should be updated to point at this RFC as well as the
previous references. previous references.
+----------+--------------+ +----------+--------------+
| SDP Name | Mux Category | | SDP Name | Mux Category |
+----------+--------------+ +----------+--------------+
| CT | NORMAL | | CT | NORMAL |
| AS | SUM | | AS | SUM |
| RS | NORMAL | | RS | SUM |
| RR | NORMAL | | RR | SUM |
| TIAS | SPECIAL | | TIAS | SPECIAL |
+----------+--------------+ +----------+--------------+
15.2.2. Table: att-field (session level) 15.2.2. Table: att-field (session level)
The following values are to be added to the "att-field (session The following values are to be added to the "att-field (session
level)" subregistry in the "Session Description Protocol (SDP) level)" subregistry in the "Session Description Protocol (SDP)
Parameters registry. The references should be updated to point at Parameters" registry. The references should be updated to point at
this RFC as well as the previous references. this RFC as well as the previous references.
+---------------------+------------------+ +---------------------+------------------+
| SDP Name | Mux Category | | SDP Name | Mux Category |
+---------------------+------------------+ +---------------------+------------------+
| cat | NORMAL | | cat | NORMAL |
| keywds | NORMAL | | keywds | NORMAL |
| type | NORMAL | | type | NORMAL |
| type:broadcast | NORMAL | | type:broadcast | NORMAL |
| type:H332 | NORMAL | | type:H332 | NORMAL |
skipping to change at page 69, line 39 skipping to change at page 68, line 39
| 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 | NOT RECOMMENDED |
+---------------------+------------------+ +---------------------+------------------+
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 point (SDP) Parameters" registry. The references should be updated to
at this RFC as well as the previous references. point at this RFC as well as the previous references.
+-------------------------+-------------------+ +-------------------------+-------------------+
| SDP Name | Mux Category | | SDP Name | Mux Category |
+-------------------------+-------------------+ +-------------------------+-------------------+
| recvonly | NORMAL | | recvonly | NORMAL |
| sendrecv | NORMAL | | sendrecv | NORMAL |
| sendonly | NORMAL | | sendonly | NORMAL |
| sdplang | NORMAL | | sdplang | NORMAL |
| lang | NORMAL | | lang | NORMAL |
| h248item | SPECIAL | | h248item | SPECIAL |
skipping to change at page 70, line 23 skipping to change at page 69, line 23
| inactive | NORMAL | | inactive | NORMAL |
| 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 |
| qos-mech-send | NORMAL | | qos-mech-send | NORMAL |
| qos-mech-recv | NORMAL | | qos-mech-recv | NORMAL |
| 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 |
| multicast-rtcp | IDENTICAL | | multicast-rtcp | IDENTICAL |
| rmcap | IDENTICAL-PER-PT | | rmcap | IDENTICAL-PER-PT |
| omcap | NORMAL | | omcap | NORMAL |
| mfcap | IDENTICAL-PER-PT | | mfcap | IDENTICAL-PER-PT |
| mscap | INHERIT | | mscap | INHERIT |
| 3gpp.iut.replication | TBD |
| bcap | INHERIT | | bcap | INHERIT |
| ccap | IDENTICAL | | ccap | IDENTICAL |
| icap | NORMAL | | icap | NORMAL |
| 3gpp_sync_info | NORMAL | | 3gpp_sync_info | NORMAL |
| 3gpp_MaxRecvSDUSize | NORMAL | | 3gpp_MaxRecvSDUSize | NORMAL |
| etag | NOT RECOMMENDED | | etag | NOT RECOMMENDED |
| duplication-delay | NORMAL | | duplication-delay | NORMAL |
| range | NOT RECOMMENDED | | range | NOT RECOMMENDED |
| control | NOT RECOMMENDED | | control | NOT RECOMMENDED |
| mtag | NOT RECOMMENDED | | mtag | NOT RECOMMENDED |
| ts-refclk | NORMAL | | ts-refclk | NORMAL |
| mediaclk | NORMAL | | mediaclk | NORMAL |
| calgextmap | NORMAL | | calgextmap | NORMAL |
+-------------------------+-------------------+ +-------------------------+-------------------+
15.2.4. Table: att-field (media level only) 15.2.4. Table: att-field (media level only)
The following values are to be added to the "att-field (media level The following values are to be added to the "att-field (media level
only" registry in the "Session Description Protocol (SDP) Parameters only)" registry in the "Session Description Protocol (SDP)
registry. The references should be updated to point at this RFC as Parameters" registry. The references should be updated to point at
well as the previous references. this RFC as well as the previous references.
+---------------------------+-------------------+ +---------------------------+-------------------+
| SDP Name | Mux Category | | SDP Name | Mux Category |
+---------------------------+-------------------+ +---------------------------+-------------------+
| ptime | IDENTICAL-PER-PT | | ptime | IDENTICAL-PER-PT |
| orient | NORMAL | | orient | NORMAL |
| orient:portrait | NORMAL | | orient:portrait | NORMAL |
| orient:landscape | NORMAL | | orient:landscape | NORMAL |
| orient:seascape | NORMAL | | orient:seascape | NORMAL |
| framerate | IDENTICAL-PER-PT | | framerate | IDENTICAL-PER-PT |
| quality | NORMAL | | quality | NORMAL |
| rtpmap | IDENTICAL-PER-PT | | rtpmap | IDENTICAL-PER-PT |
| fmtp | IDENTICAL-PER-PT | | fmtp | IDENTICAL-PER-PT |
| rtpred1 | NOT RECOMMENDED | | rtpred1 | NOT RECOMMENDED |
| rtpred2 | NOT RECOMMENDED | | rtpred2 | NOT RECOMMENDED |
| T38FaxVersion | NORMAL | | T38FaxVersion | NORMAL |
| T38MaxBitRate | NORMAL | | T38MaxBitRate | NORMAL |
| T38MaxBitRate | NORMAL | | T38FaxFillBitRemoval | NORMAL |
| T38FaxTranscodingMMR | NORMAL | | T38FaxTranscodingMMR | NORMAL |
| T38FaxTranscodingJBIG | NORMAL | | T38FaxTranscodingJBIG | NORMAL |
| T38FaxRateManagement | NORMAL | | T38FaxRateManagement | NORMAL |
| T38FaxMaxBuffer | NORMAL | | T38FaxMaxBuffer | NORMAL |
| T38FaxMaxDatagram | NORMAL | | T38FaxMaxDatagram | NORMAL |
| T38FaxUdpEC | NORMAL | | T38FaxUdpEC | NORMAL |
| maxptime | IDENTICAL-PER-PT | | maxptime | IDENTICAL-PER-PT |
| des | NOT RECOMMENDED | | des | NOT RECOMMENDED |
| curr | NOT RECOMMENDED | | curr | NOT RECOMMENDED |
| conf | NOT RECOMMENDED | | conf | NOT RECOMMENDED |
skipping to change at page 72, line 7 skipping to change at page 71, line 9
| T38VendorInfo | NORMAL | | T38VendorInfo | NORMAL |
| crypto | TRANSPORT | | crypto | TRANSPORT |
| eecid | NORMAL | | eecid | NORMAL |
| aalType | NORMAL | | aalType | NORMAL |
| capability | NORMAL | | capability | NORMAL |
| qosClass | NORMAL | | qosClass | NORMAL |
| bcob | NORMAL | | bcob | NORMAL |
| stc | NORMAL | | stc | NORMAL |
| upcc | NORMAL | | upcc | NORMAL |
| atmQOSparms | NORMAL | | atmQOSparms | NORMAL |
| atmQOSparms | NORMAL | | atmTrfcDesc | NORMAL |
| abrParms | NORMAL | | abrParms | NORMAL |
| abrSetup | NORMAL | | abrSetup | NORMAL |
| bearerType | NORMAL | | bearerType | NORMAL |
| lij | NORMAL | | lij | NORMAL |
| anycast | NORMAL | | anycast | NORMAL |
| cache | NORMAL | | cache | NORMAL |
| bearerSigIE | NORMAL | | bearerSigIE | NORMAL |
| aalApp | NORMAL | | aalApp | NORMAL |
| cbrRate | NORMAL | | cbrRate | NORMAL |
| sbc | NORMAL | | sbc | NORMAL |
skipping to change at page 72, line 47 skipping to change at page 71, line 49
| onewaySel | NORMAL | | onewaySel | NORMAL |
| codecConfig | NORMAL | | codecConfig | NORMAL |
| isup_usi | NORMAL | | isup_usi | NORMAL |
| uiLayer1_Prot | NORMAL | | uiLayer1_Prot | NORMAL |
| chain | NORMAL | | chain | NORMAL |
| floorctrl | IDENTICAL | | floorctrl | IDENTICAL |
| confid | NORMAL | | confid | NORMAL |
| userid | NORMAL | | userid | NORMAL |
| floorid | NORMAL | | floorid | NORMAL |
| FEC | NORMAL | | FEC | NORMAL |
| profileDesc | NORMAL |
| accept-types | NORMAL | | accept-types | NORMAL |
| accept-wrapped-types | NORMAL | | accept-wrapped-types | NORMAL |
| max-size | NORMAL | | max-size | NORMAL |
| path | NORMAL | | path | NORMAL |
| dccp-service-code | NOT RECOMMENDED | | dccp-service-code | NOT RECOMMENDED |
| rtcp-mux | IDENTICAL | | rtcp-mux | IDENTICAL |
| candidate | TRANSPORT | | candidate | TRANSPORT |
| ice-mismatch | NORMAL | | ice-mismatch | NORMAL |
| remote-candidates | TRANSPORT | | remote-candidates | TRANSPORT |
| SRTPAuthentication | NORMAL | | SRTPAuthentication | NORMAL |
skipping to change at page 73, line 51 skipping to change at page 73, line 4
| cfw-id | NORMAL | | cfw-id | NORMAL |
| portmapping-req | NOT RECOMMENDED | | portmapping-req | NOT RECOMMENDED |
| g.3gpp.cat | NORMAL | | g.3gpp.cat | NORMAL |
| g.3gpp.crs | NORMAL | | g.3gpp.crs | NORMAL |
| ecn-capable-rtp | IDENTICAL | | ecn-capable-rtp | IDENTICAL |
| visited-realm | TRANSPORT | | visited-realm | TRANSPORT |
| secondary-realm | TRANSPORT | | secondary-realm | TRANSPORT |
| omr-s-cksum | NORMAL | | omr-s-cksum | NORMAL |
| omr-m-cksum | NORMAL | | omr-m-cksum | NORMAL |
| omr-codecs | NORMAL | | omr-codecs | NORMAL |
| omr-codecs | NORMAL |
| omr-m-att | NORMAL | | omr-m-att | NORMAL |
| omr-s-att | NORMAL |
| omr-m-bw | NORMAL | | omr-m-bw | NORMAL |
| omr-s-bw | NORMAL | | omr-s-bw | NORMAL |
| msrcp-cema | NORMAL | | msrp-cema | NORMAL |
| dccp-port | NOT RECOMMENDED | | dccp-port | NOT RECOMMENDED |
| resource | NORMAL | | resource | NORMAL |
| channel | NORMAL | | channel | NORMAL |
| cmid | NORMAL | | cmid | NORMAL |
| content | NORMAL | | content | NORMAL |
| lcfg | SPECIAL | | lcfg | SPECIAL |
| loopback | NORMAL | | loopback | NORMAL |
| loopback-source | NORMAL | | loopback-source | NORMAL |
| loopback-mirror | NORMAL | | loopback-mirror | NORMAL |
| chatroom | TBD | | chatroom | TBD |
| altc | TRANSPORT | | altc | TRANSPORT |
| T38FaxMaxIFP | NORMAL | | T38FaxMaxIFP | NORMAL |
| T38FaxUdpECDepth | NORMAL | | T38FaxUdpECDepth | NORMAL |
| T38FaxUdpFECMaxSpan | NORMAL | | T38FaxUdpFECMaxSpan | NORMAL |
| T38ModemType | NORMAL | | T38ModemType | NORMAL |
| cs-correlation | NORMAL | | cs-correlation | NORMAL |
| rtcpidms | NORMAL | | rtcp-idms | NORMAL |
+---------------------------+-------------------+ +---------------------------+-------------------+
15.2.5. Table: att-field (source level) 15.2.5. Table: att-field (source level)
The following values are to be added to the "att-field (source The following values are to be added to the "att-field (source
level)" registry in the "Session Description Protocol (SDP) level)" registry in the "Session Description Protocol (SDP)
Parameters registry. The references should be updated to point at Parameters" registry. The references should be updated to point at
this RFC as well as the previous references. this RFC as well as the previous references.
+----------------+-------------------+ +----------------+-------------------+
| SDP Name | Mux Category | | SDP Name | Mux Category |
+----------------+-------------------+ +----------------+-------------------+
| cname | NORMAL | | cname | NORMAL |
| previous-ssrc | NORMAL | | previous-ssrc | NORMAL |
| fmtp | IDENTICAL-PER-PT | | fmtp | IDENTICAL-PER-PT |
| ts-refclk | NORMAL | | ts-refclk | NORMAL |
| mediaclk | NORMAL | | mediaclk | NORMAL |
+----------------+-------------------+ +----------------+-------------------+
15.2.6. Table: content SDP Parameters 15.2.6. Table: content SDP Parameters
The following values are to be added to the "content SDP Parameters" The following values are to be added to the "content SDP Parameters"
subregistry in the "Session Description Protocol (SDP) Parameters subregistry in the "Session Description Protocol (SDP) Parameters"
registry. The references should be updated to point at this RFC as registry. The references should be updated to point at this RFC as
well as the previous references. well as the previous references.
+----------+--------------+ +----------+--------------+
| SDP Name | Mux Category | | SDP Name | Mux Category |
+----------+--------------+ +----------+--------------+
| slides | NORMAL | | slides | NORMAL |
| speaker | NORMAL | | speaker | NORMAL |
| sl | NORMAL | | sl | NORMAL |
| main | NORMAL | | main | NORMAL |
| alt | NORMAL | | alt | NORMAL |
+----------+--------------+ +----------+--------------+
15.2.7. Table: Semantics for the 'group' SDP Attribute 15.2.7. Table: Semantics for the 'group' SDP Attribute
The following values are to be added to the "Semantics for the The following values are to be added to the "Semantics for the
"group" SDP Attribute" subregistry in the "Session Description "group" SDP Attribute" subregistry in the "Session Description
Protocol (SDP) Parameters registry. The references should be updated Protocol (SDP) Parameters" registry. The references should be
to point at this RFC as well as the previous references. updated to point at this RFC as well as the previous references.
+---------+------------------+ +---------+------------------+
| Token | Mux Category | | Token | Mux Category |
+---------+------------------+ +---------+------------------+
| LS | NORMAL | | LS | NORMAL |
| FID | NORMAL | | FID | NORMAL |
| SRF | NORMAL | | SRF | NORMAL |
| ANAT | NOT RECOMMENDED | | ANAT | NOT RECOMMENDED |
| FEC | NORMAL | | FEC | NORMAL |
| FEC-FR | NORMAL | | FEC-FR | NORMAL |
| CS | NORMAL | | CS | NORMAL |
| DDP | NORMAL | | DDP | NORMAL |
| DUP | NORMAL | | DUP | NORMAL |
+---------+------------------+ +---------+------------------+
15.2.8. Table: 'rtcp-fb' Attribute Values 15.2.8. Table: 'rtcp-fb' Attribute Values
The following values are to be added to the " 'rtcp-fb' Attribute The following values are to be added to the " 'rtcp-fb' Attribute
Values" subregistry in the "Session Description Protocol (SDP) Values" subregistry in the "Session Description Protocol (SDP)
Parameters registry. The references should be updated to point at Parameters" registry. The references should be updated to point at
this RFC as well as the previous references. this RFC as well as the previous references.
+------------+-------------------+ +------------+-------------------+
| Value Name | Mux Category | | Value Name | Mux Category |
+------------+-------------------+ +------------+-------------------+
| ack | IDENTICAL-PER-PT | | ack | IDENTICAL-PER-PT |
| app | SPECIAL | | app | SPECIAL |
| ccm | IDENTICAL-PER-PT | | ccm | IDENTICAL-PER-PT |
| nack | IDENTICAL-PER-PT | | nack | IDENTICAL-PER-PT |
| trr-int | IDENTICAL-PER-PT | | trr-int | IDENTICAL-PER-PT |
skipping to change at page 76, line 18 skipping to change at page 75, line 18
Attribute Values" subregistry in the "Session Description Protocol Attribute Values" 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.
+------------+-------------------+ +------------+-------------------+
| Value Name | Mux Category | | Value Name | Mux Category |
+------------+-------------------+ +------------+-------------------+
| sli | IDENTICAL-PER-PT | | sli | IDENTICAL-PER-PT |
| pli | IDENTICAL-PER-PT | | pli | IDENTICAL-PER-PT |
| rpsi | IDENTICAL-PER-PT | | rpsi | IDENTICAL-PER-PT |
| app | IDENTICAL-PER-PT | | app | SPECIAL |
| rai | IDENTICAL-PER-PT | | rai | IDENTICAL-PER-PT |
| tllei | IDENTICAL-PER-PT | | tllei | IDENTICAL-PER-PT |
| pslei | IDENTICAL-PER-PT | | pslei | IDENTICAL-PER-PT |
| ecn | IDENTICAL | | ecn | IDENTICAL |
+------------+-------------------+ +------------+-------------------+
15.2.10. Table: 'depend' SDP Attribute Values 15.2.10. Table: 'depend' SDP Attribute Values
The following values are to be added to the " 'depend' SDP Attribute The following values are to be added to the " 'depend' SDP Attribute
Values" subregistry in the "Session Description Protocol (SDP) Values" subregistry in the "Session Description Protocol (SDP)
Parameters registry. The references should be updated to point at Parameters" registry. The references should be updated to point at
this RFC as well as the previous references. this RFC as well as the previous references.
+-------+-------------------+ +-------+-------------------+
| Token | Mux Category | | Token | Mux Category |
+-------+-------------------+ +-------+-------------------+
| lay | IDENTICAL-PER-PT | | lay | IDENTICAL-PER-PT |
| mdc | IDENTICAL-PER-PT | | mdc | IDENTICAL-PER-PT |
+-------+-------------------+ +-------+-------------------+
15.2.11. Table: 'cs-correlation' Attribute Values 15.2.11. Table: 'cs-correlation' Attribute Values
The following values are to be added to the " "cs-correlation" The following values are to be added to the " "cs-correlation"
Attribute Values" subregistry in the "Session Description Protocol Attribute Values" subregistry in the "Session Description Protocol
(SDP) Parameters registry. The references should be updated to point (SDP) Parameters" registry. The references should be updated to
at this RFC as well as the previous references. point at this RFC as well as the previous references.
+-----------+--------------+ +-----------+--------------+
| Value | Mux Category | | Value | Mux Category |
+-----------+--------------+ +-----------+--------------+
| callerid | NORMAL | | callerid | NORMAL |
| uuie | NORMAL | | uuie | NORMAL |
| dtmf | NORMAL | | dtmf | NORMAL |
| external | NORMAL | | external | NORMAL |
+-----------+--------------+ +-----------+--------------+
15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute
The following values are to be added to the Semantics for the The following values are to be added to the Semantics for the
"Semantics for the "ssrc-group" SDP Attribute" subregistry in the "Semantics for the "ssrc-group" SDP Attribute" subregistry in the
"Session Description Protocol (SDP) Parameters registry. The "Session Description Protocol (SDP) Parameters" registry. The
references should be updated to point at this RFC as well as the references should be updated to point at this RFC as well as the
previous references. previous references.
+---------+--------------+ +---------+--------------+
| Token | Mux Category | | Token | Mux Category |
+---------+--------------+ +---------+--------------+
| FID | NORMAL | | FID | NORMAL |
| FEC | NORMAL | | FEC | NORMAL |
| FEC-FR | NORMAL | | FEC-FR | NORMAL |
| DUP | NORMAL | | DUP | NORMAL |
+---------+--------------+ +---------+--------------+
15.2.13. Table: SDP/RTSP key management protocol identifiers 15.2.13. Table: SDP/RTSP key management protocol identifiers
The following values are to be added to the "SDP/RTSP key management The following values are to be added to the "SDP/RTSP key management
protocol identifiers" subregistry in the "Session Description protocol identifiers" subregistry in the "Session Description
Protocol (SDP) Parameters registry. The references should be updated Protocol (SDP) Parameters" registry. The references should be
to point at this RFC as well as the previous references. updated to point at this RFC as well as the previous references.
+------------+--------------+ +------------+--------------+
| Value Name | Mux Category | | Value Name | Mux Category |
+------------+--------------+ +------------+--------------+
| mikey | IDENTICAL | | mikey | IDENTICAL |
+------------+--------------+ +------------+--------------+
15.2.14. Table: Codec Control Messages 15.2.14. Table: Codec Control Messages
The following values are to be added to the "Codec Control Messages" The following values are to be added to the "Codec Control Messages"
subregistry in the "Session Description Protocol (SDP) Parameters subregistry in the "Session Description Protocol (SDP) Parameters"
registry. The references should be updated to point at this RFC as registry. The references should be updated to point at this RFC as
well as the previous references. well as the previous references.
+------------+-------------------+ +------------+-------------------+
| Value Name | Mux Category | | Value Name | Mux Category |
+------------+-------------------+ +------------+-------------------+
| fir | IDENTICAL-PER-PT | | fir | IDENTICAL-PER-PT |
| tmmbr | IDENTICAL-PER-PT | | tmmbr | IDENTICAL-PER-PT |
| tstr | IDENTICAL-PER-PT | | tstr | IDENTICAL-PER-PT |
| vbcm | IDENTICAL-PER-PT | | vbcm | IDENTICAL-PER-PT |
+------------+-------------------+ +------------+-------------------+
15.2.15. Table: QoS Mechanism Tokens 15.2.15. Table: QoS Mechanism Tokens
The following values are to be added to the "QoS Mechanism Tokens" The following values are to be added to the "QoS Mechanism Tokens"
subregistry in the "Session Description Protocol (SDP) Parameters subregistry in the "Session Description Protocol (SDP) Parameters"
registry. The references should be updated to point at this RFC as registry. The references should be updated to point at this RFC as
well as the previous references. well as the previous references.
+---------------+--------------+ +---------------+--------------+
| QoS Mechanism | Mux Category | | QoS Mechanism | Mux Category |
+---------------+--------------+ +---------------+--------------+
| rsvp | NORMAL | | rsvp | NORMAL |
| nsis | NORMAL | | nsis | NORMAL |
+---------------+--------------+ +---------------+--------------+
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 updated Protocol (SDP) Parameters" registry. The references should be
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 | | QoS Mechanism | 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 updated Protocol (SDP) Parameters" registry. The references should be
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 |
+----------+--------------+ +----------+--------------+
| ntp | NORMAL | | ntp | NORMAL |
| ptp | NORMAL | | ptp | NORMAL |
| gps | NORMAL | | gps | NORMAL |
| gal | NORMAL | | gal | NORMAL |
| glonass | NORMAL | | glonass | NORMAL |
| local | NORMAL | | local | NORMAL |
| private | NORMAL | | private | NORMAL |
+----------+--------------+ +----------+--------------+
15.2.18. Table: Media Clock Source Parameters 15.2.18. Table: Media Clock Source Parameters
The following values are to be added to the "Media Clock Source The following values are to be added to the "Media Clock Source
Parameters" subegistry in the "Session Description Protocol (SDP) Parameters" subegistry in the "Session Description Protocol (SDP)
Parameters registry. The references should be updated to point at Parameters" registry. The references should be updated to point at
this RFC as well as the previous references. this RFC as well as the previous references.
+-----------+--------------+ +-----------+--------------+
| Name | Mux Category | | Name | Mux Category |
+-----------+--------------+ +-----------+--------------+
| sender | NORMAL | | sender | NORMAL |
| direct | NORMAL | | direct | NORMAL |
| IEEE1722 | NORMAL | | IEEE1722 | NORMAL |
+-----------+--------------+ +-----------+--------------+
skipping to change at page 79, line 44 skipping to change at page 78, line 44
This document does not add any new security considerations beyond the This document does not add any new security considerations beyond the
existing considerations in the RFC for protocols that are being existing considerations in the RFC for protocols that are being
multiplexed together. multiplexed together.
The ways that SRTP streams are keyed is not believed to create any The ways that SRTP streams are keyed is not believed to create any
two-time pad vulnerability for the currently defined SRTP keying two-time pad vulnerability for the currently defined SRTP keying
mechanism. mechanism.
17. Acknowledgments 17. Acknowledgments
I would like to thank Cullen Jennings and Flemming Andreasen for I would like to thank Cullen Jennings, Flemming Andreasen for
suggesting the categories, contributing text and reviewing the draft. suggesting the categories, contributing text and reviewing the draft.
I would also link to thank Magnus Westerlund, Christer Holmberg, I would also link to thank Magnus Westerlund, Christer Holmberg,
Jonathan Lennox, Bo Burman, and Dan on suggesting structural changes Jonathan Lennox, Bo Burman, and Dan Wing on suggesting structural
helping improve the document readability. changes helping improve the document readability.
I would like also to thank following experts on their inputs and I would like also to thank following experts on their inputs and
reviews as listed - Flemming Andreasen(5.20,5.28,5.29,14), Rohan reviews as listed - Flemming Andreasen(5.24,5.32,5.33,14), Rohan
Mahy(5.45), Eric Burger(5.22),Christian Huitema(5.13), Christer Mahy(5.57), Eric Burger(5.26),Christian Huitema(5.14), Christer
Holmberg(5.17,5.22,5.40,5.41), Richard Ejzak (5.36,5.42,5.43,5.44), Holmberg(5.21,5.26,5.51,5.52), Richard Ejzak (5.44,5.53,5.54), Colin
Colin Perkins(5.7,5.8), Magnus westerlund(5.2,5.3,5.9,5.26, Perkins(5.7,5.8,5.9,5.58), Magnus
5.27,6.1,6.2,6.3,8.3,7), Roni Evens(5.12,5.27,8.4), Subha westerlund(5.2,5.3,5.9,5.27,5.47,6.1,6.2,6.3,8.3,7), Roni
Dhesikan(5.5,12.1,14), Dan Wing(5.6,5.11,5.30,5.34,5.37), Ali C Evens(5.12,5.27,8.4), Subha Dhesikan(5.6,10), Dan
Begen(5.1,5.16,5.18,5.21,5.33,8.2,8.4,13.1), Bo Burman (7.2,7.6), Wing(5.7,5.12,5.35,5.39,5.45), Cullen Jennings (5.40), Ali C
Charles Eckel(5.14,5.23,5.24,9.1,8.5), Paul Kyzivat(5.24), Ian Begen(5.1,5.20,5.22,5.25,5.38,7.3,8.2,8.4,8.6,9.2,13.1), Bo Burman
Johansson(5.15), Saravanan Shanmugham(5.10), Paul E Jones(5.25), (7.2,7.6), Charles Eckel(5.15,5.27,5.28,9.1,8.5), Paul Kyzivat(5.24),
Rajesh Kumar(5.39), Jonathan Lennox(5.31,5,14,11.1), Mo Ian Johansson(5.15), Saravanan Shanmugham(5.11), Paul E Jones(5.30),
Zanaty(5.4,5.19,8.1,8.3,8.5,12.1), Christian Huitema (5.13), Qin Wu Rajesh Kumar(5.48), Jonathan Lennox(5.36,5,15,9.1,11.1), Mo
(5.38 PM-Dir review). 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).
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-04
o Fixed minor nits overall.
o Updated Acknowledgement Sections
o Last Call Version.
Changes from draft-ietf-mmusic-sdp-mux-attributes-03 Changes from draft-ietf-mmusic-sdp-mux-attributes-03
o More re-work on the IANA section. o More re-work on the IANA section.
o Clean ups preparing for the last call. o Clean ups preparing for the last call.
Changes from draft-ietf-mmusic-sdp-mux-attributes-02 Changes from draft-ietf-mmusic-sdp-mux-attributes-02
o Incorporated suggestions from Flemming on Capability Negotiation. o Incorporated suggestions from Flemming on Capability Negotiation.
skipping to change at page 88, line 19 skipping to change at page 87, line 32
[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, May
2014. 2014.
[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. April 2014.
[RFC7226] Villamizar, C., McDysan, D., Ning, S., Malis, A., and L. [RFC7266] Clark, A., Wu, Q., Schott, R., and G. Zorn, "RTP Control
Yong, "Requirements for Advanced Multipath in MPLS Protocol (RTCP) Extended Report (XR) Blocks for Mean
Networks", RFC 7226, May 2014. Opinion Score (MOS) Metric Reporting", RFC 7266, June
2014.
[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, June 2014.
[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, June
2014. 2014.
 End of changes. 168 change blocks. 
634 lines changed or deleted 646 lines changed or added

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