draft-ietf-mmusic-sdp-mux-attributes-05.txt   draft-ietf-mmusic-sdp-mux-attributes-06.txt 
Network Working Group S. Nandakumar Network Working Group S. Nandakumar
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track November 26, 2014 Intended status: Standards Track December 11, 2014
Expires: May 30, 2015 Expires: June 14, 2015
A Framework for SDP Attributes when Multiplexing A Framework for SDP Attributes when Multiplexing
draft-ietf-mmusic-sdp-mux-attributes-05 draft-ietf-mmusic-sdp-mux-attributes-06
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. [I-D.ietf-mmusic-sdp-bundle-negotiation]
single 5-tuple for sending and receiving media associated with provides SDP extensions to negotiate the usage of single 5-tuple for
multiple media descriptions ("m=" lines). Such a requirement has sending and receiving media associated with multiple media
raised concerns over the semantic implications of the SDP attributes descriptions ("m=" lines). Such a mechanism has made it necessary to
associated with the RTP Media Streams multiplexed over a single understand the semantic implications of the SDP attributes associated
underlying transport layer flow. with the RTP Media Streams multiplexed over a single underlying
transport layer flow.
The scope of this specification is to provide a framework for The purpose of this specification is to provide a framework for
analyzing the multiplexing characteristics of 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.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 May 30, 2015. This Internet-Draft will expire on June 14, 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 32 skipping to change at page 2, line 37
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 6 4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 7
4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7 4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7
4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 7 4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . 11
4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 11 4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 12
4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 11 4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 12
5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12 5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 12
5.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 12 5.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 13
5.2. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 14 5.2. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 14
5.3. RFC5761 - Multiplexing RTP and RTCP . . . . . . . . . . . 14 5.3. RFC5761 - Multiplexing RTP and RTCP . . . . . . . . . . . 15
5.4. RFC3312 - Integration of Resource Management and (SIP) . 14 5.4. RFC3312 - Integration of Resource Management and (SIP) . 15
5.5. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 15 5.5. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 16
5.6. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 15 5.6. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 16
5.7. RFC4568 - SDP Security Descriptions . . . . . . . . . . . 16 5.7. RFC4568 - SDP Security Descriptions . . . . . . . . . . . 17
5.8. RFC5762 - RTP over DCCP . . . . . . . . . . . . . . . . . 16 5.8. RFC5762 - RTP over DCCP . . . . . . . . . . . . . . . . . 17
5.9. RFC6773 - DCCP-UDP Encapsulation . . . . . . . . . . . . 17 5.9. RFC6773 - DCCP-UDP Encapsulation . . . . . . . . . . . . 18
5.10. RFC5506 - Reduced-Size RTCP in RTP Profile . . . . . . . 18 5.10. RFC5506 - Reduced-Size RTCP in RTP Profile . . . . . . . 19
5.11. RFC6787 - Media Resource Control Protocol Version 2 . . . 18 5.11. RFC6787 - Media Resource Control Protocol Version 2 . . . 19
5.12. RFC5245 - Interactive Connectivity Establishment (ICE) . 19 5.12. RFC5245 - Interactive Connectivity Establishment (ICE) . 20
5.13. RFC5285 - RTP Header Extensions . . . . . . . . . . . . . 21 5.13. RFC5285 - RTP Header Extensions . . . . . . . . . . . . . 21
5.14. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 21 5.14. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 22
5.15. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 21 5.15. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 22
5.16. RFC7273 - RTP Clock Source Signalling . . . . . . . . . . 22 5.16. RFC7273 - RTP Clock Source Signalling . . . . . . . . . . 23
5.17. RFC6236 - Image Attributes in SDP . . . . . . . . . . . . 23 5.17. RFC6236 - Image Attributes in SDP . . . . . . . . . . . . 24
5.18. RFC7197 - Duplication Delay Attribute in SDP . . . . . . 23 5.18. RFC7197 - Duplication Delay Attribute in SDP . . . . . . 24
5.19. RFC7266 - RTCP XR Blocks for MOS Metric Reporting . . . 23 5.19. RFC7266 - RTCP XR Blocks for MOS Metric Reporting . . . 24
5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions . . 24 5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions . . 25
5.21. RFC6230 - Media Control Channel Framework . . . . . . . . 24 5.21. RFC6230 - Media Control Channel Framework . . . . . . . . 25
5.22. RFC6364 - SDP Elements for FEC Framework . . . . . . . . 25 5.22. RFC6364 - SDP Elements for FEC Framework . . . . . . . . 26
5.23. RFC4796 - Content Attribute . . . . . . . . . . . . . . . 25 5.23. RFC4796 - Content Attribute . . . . . . . . . . . . . . . 26
5.24. RFC3407 - SDP Simple Capability Declaration . . . . . . . 26 5.24. RFC3407 - SDP Simple Capability Declaration . . . . . . . 27
5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP 5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP
Sessions . . . . . . . . . . . . . . . . . . . . . . . . 26 Sessions . . . . . . . . . . . . . . . . . . . . . . . . 27
5.26. RFC6714 - MSRP-CEMA . . . . . . . . . . . . . . . . . . . 27 5.26. RFC6714 - MSRP-CEMA . . . . . . . . . . . . . . . . . . . 28
5.27. RFC4583 - SDP Format for BFCP Streams . . . . . . . . . . 27 5.27. RFC4583 - SDP Format for BFCP Streams . . . . . . . . . . 28
5.28. RFC5547 - SDP Offer/Answer for File Transfer . . . . . . 28 5.28. RFC5547 - SDP Offer/Answer for File Transfer . . . . . . 29
5.29. RFC6849 - SDP and RTP Media Loopback Extension . . . . . 28 5.29. RFC6849 - SDP and RTP Media Loopback Extension . . . . . 29
5.30. RFC5760 - RTCP with Unicast Feedback . . . . . . . . . . 29 5.30. RFC5760 - RTCP with Unicast Feedback . . . . . . . . . . 30
5.31. RFC3611 - RTCP XR . . . . . . . . . . . . . . . . . . . . 29 5.31. RFC3611 - RTCP XR . . . . . . . . . . . . . . . . . . . . 30
5.32. RFC5939 - SDP Capability Negotiation . . . . . . . . . . 29 5.32. RFC5939 - SDP Capability Negotiation . . . . . . . . . . 30
5.33. RFC6871- SDP Media Capabilities Negotiation . . . . . . . 30 5.33. RFC6871- SDP Media Capabilities Negotiation . . . . . . . 31
5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP . . 31 5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP . . 32
5.35. RFC4567 - Key Management Extensions for SDP and RTSP . . 32 5.35. RFC4567 - Key Management Extensions for SDP and RTSP . . 33
5.36. RFC4572 - Comedia over TLS in SDP . . . . . . . . . . . . 33 5.36. RFC4572 - Comedia over TLS in SDP . . . . . . . . . . . . 34
5.37. RFC4570 - SDP Source Filters . . . . . . . . . . . . . . 33 5.37. RFC4570 - SDP Source Filters . . . . . . . . . . . . . . 34
5.38. RFC6128 - RTCP Port for Multicast Sessions . . . . . . . 34 5.38. RFC6128 - RTCP Port for Multicast Sessions . . . . . . . 35
5.39. RFC6189 - ZRTP . . . . . . . . . . . . . . . . . . . . . 34 5.39. RFC6189 - ZRTP . . . . . . . . . . . . . . . . . . . . . 35
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 . . . . . . . . . . . . 36
5.42. RFC7195 - SDP Extension for Circuit Switched Bearers 5.42. RFC7195 - SDP Extension for Circuit Switched Bearers
in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 35 in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP) . . 36 5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP) . . 37
5.44. RFC5159 - OMA BCAST SDP Attributes . . . . . . . . . . . 36 5.44. RFC5159 - OMA BCAST SDP Attributes . . . . . . . . . . . 37
5.45. RFC6193 - Media Description for IKE in SDP . . . . . . . 37 5.45. RFC6193 - Media Description for IKE in SDP . . . . . . . 38
5.46. RFC2326 - Real Time Streaming Protocol . . . . . . . . . 38 5.46. RFC2326 - Real Time Streaming Protocol . . . . . . . . . 39
5.47. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 38 5.47. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 39
5.48. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 41 5.48. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 42
5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 42 5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 45
5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 43 5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 45
5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 43 5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 45
5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 44 5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 46
5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 44 5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 46
5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 45 5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 47
5.55. ITU-T-REC.Q1970 . . . . . . . . . . . . . . . . . . . . . 46 5.55. ITU-T Q.1970 . . . . . . . . . . . . . . . . . . . . . . 48
5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 47 5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 49
5.57. RFC4975 - The Message Session Relay Protocol . . . . . . 47 5.57. RFC4975 - The Message Session Relay Protocol . . . . . . 50
5.58. Historical Attributes . . . . . . . . . . . . . . . . . . 48 5.58. Historical Attributes . . . . . . . . . . . . . . . . . . 50
6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 48 6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 50
6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 48 6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 51
6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 49 6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 51
6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 49 6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 52
7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 50 7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 52
7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 50 7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 52
7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 51 7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 53
7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 52 7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 54
7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 52 7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 54
7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 53 7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 55
7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 54 7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 56
8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 54 8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 56
8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 54 8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 56
8.2. RFC3524 - Mapping Media Streams to Resource 8.2. RFC3524 - Mapping Media Streams to Resource
Reservation Flows . . . . . . . . . . . . . . . . . . . . 55 Reservation Flows . . . . . . . . . . . . . . . . . . . . 57
8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 55 8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 57
8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 55 8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 58
8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 56 8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 58
8.6. RFC7104 - Duplication Grouping Semantics in the SDP . . 56 8.6. RFC7104 - Duplication Grouping Semantics in the SDP . . 59
9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 57 9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 59
9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 57 9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 59
9.2. RFC7104 - Duplication Grouping Semantics in the SDP . . . 57 9.2. RFC7104 - Duplication Grouping Semantics in the SDP . . . 59
10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 57 10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 60
10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 57 10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 60
11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 58 11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 60
11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 58 11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 60
12. content Attribute Analysis . . . . . . . . . . . . . . . . . 58 12. content Attribute Analysis . . . . . . . . . . . . . . . . . 61
12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 58 12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 61
13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 59 13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 61
13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 59 13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 61
14. Multiplexing Considerations for Encapsulating Attributes . . 59 14. Multiplexing Considerations for Encapsulating Attributes . . 62
14.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 60 14.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 62
14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 60 14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 63
14.2.1. Recommendation - Procedures for Potential 14.2.1. Recommendation - Procedures for Potential
Configuration Pairing . . . . . . . . . . . . . . . 61 Configuration Pairing . . . . . . . . . . . . . . . 64
14.2.1.1. Example: Transport Capability Multiplexing . . . 62 14.2.1.1. Example: Transport Capability Multiplexing . . . 65
14.2.1.2. Example: Attribute Capability Multiplexing . . . 63 14.2.1.2. Example: Attribute Capability Multiplexing . . . 66
14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 64 14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 66
14.3.1. Recommendation: Dealing with Payload Type Numbers . 64 14.3.1. Recommendation: Dealing with Payload Type Numbers . 66
14.3.1.1. Example: Attribute Capability Under Shared 14.3.1.1. Example: Attribute Capability Under Shared
Payload Type . . . . . . . . . . . . . . . . . . 64 Payload Type . . . . . . . . . . . . . . . . . . 67
14.3.2. Recommendation: Dealing with Latent Configurations . 65
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66
15.1. New 'Multiplexing Categories' subregistry . . . . . . . 66
15.2. 'Mux Category' column for subregistries . . . . . . . . 67
15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 67
15.2.2. Table: att-field (session level) . . . . . . . . . . 67
15.2.3. Table: att-field (both session and media level) . . 68
15.2.4. Table: att-field (media level only) . . . . . . . . 70
15.2.5. Table: att-field (source level) . . . . . . . . . . 73
15.2.6. Table: content SDP Parameters . . . . . . . . . . . 73
15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 74
15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 74
15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 75
15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 75
15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 75
15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 76
15.2.13. Table: SDP/RTSP key management protocol identifiers 76
15.2.14. Table: Codec Control Messages . . . . . . . . . . . 76
15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 77
15.2.16. Table: SDP Capability Negotiation Option Tags . . . 77
15.2.17. Table: Timestamp Reference Clock Source Parameters . 77
15.2.18. Table: Media Clock Source Parameters . . . . . . . . 78
16. Security Considerations . . . . . . . . . . . . . . . . . . . 78
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 78
18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 79
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 81
19.1. Normative References . . . . . . . . . . . . . . . . . . 81
19.2. Informative References . . . . . . . . . . . . . . . . . 81
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 88
1. Introduction 14.3.2. Recommendation: Dealing with Latent Configurations . 68
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68
15.1. New 'Multiplexing Categories' subregistry . . . . . . . 68
15.2. 'Mux Category' column for subregistries . . . . . . . . 69
15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 69
15.2.2. Table: att-field (session level) . . . . . . . . . . 70
15.2.3. Table: att-field (both session and media level) . . 71
15.2.4. Table: att-field (media level only) . . . . . . . . 72
15.2.5. Table: att-field (source level) . . . . . . . . . . 75
15.2.6. Table: content SDP Parameters . . . . . . . . . . . 76
15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 76
15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 77
15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 77
15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 77
15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 78
15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 78
15.2.13. Table: SDP/RTSP key management protocol identifiers 78
15.2.14. Table: Codec Control Messages . . . . . . . . . . . 79
15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 79
15.2.16. Table: SDP Capability Negotiation Option Tags . . . 79
15.2.17. Table: Timestamp Reference Clock Source Parameters . 80
15.2.18. Table: Media Clock Source Parameters . . . . . . . . 80
16. Security Considerations . . . . . . . . . . . . . . . . . . . 81
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 81
18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 81
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 84
19.1. Normative References . . . . . . . . . . . . . . . . . . 84
19.2. Informative References . . . . . . . . . . . . . . . . . 84
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 90
Real-Time Communication in WEB-browsers (Rtcweb) framework requires 1. Introduction
Real-time Transport Protocol (RTP) as the media transport protocol
and Session Description Protocol (SDP) [RFC4566] for describing and
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
a single 5-tuple for sending and receiving media associated with [I-D.ietf-mmusic-sdp-bundle-negotiation] defines a way to use a
multiple SDP media descriptions ("m=" lines) has been identified. single address:port combination (BUNDLE address) for receiving media
This would for e.g. allow the usage of a single set of Interactive associated with multiple SDP media descriptions. This would for e.g.
Connectivity Establishment (ICE) [RFC5245] candidates for multiple allow the usage of a single set of ICE [RFC5245] candidates for
media descriptions. This in turn has made necessary to understand multiple media descriptions. This in turn has made necessary to
the interpretation and usage of the SDP attributes defined for the understand the interpretation and usage of the SDP attributes defined
multiplexed media descriptions. for the multiplexed media descriptions.
Given the number of SDP attributes registered with the [IANA] and Given the number of SDP attributes registered with the [IANA] and
possibility of new attributes being defined in the future, there is possibility of new attributes being defined in the future, there is
need for generic future-proof framework to analyze these attributes need for generic future-proof framework to analyze these attributes
for their applicability in the transport multiplexing use-cases. for their applicability in the transport multiplexing use-cases.
The document starts with providing the motivation for requiring such The document starts with providing the motivation for requiring such
a framework. This is followed by introduction to the SDP attribute a framework. This is followed by introduction to the SDP attribute
analysis framework/procedures, following which several sections analysis framework/procedures, following which several sections
applies the framework to the SDP attributes registered with the applies the framework to the SDP attributes registered with the
[IANA]. [IANA].
2. Terminology 2. Terminology
5-tuple: A collection of the following values: source address, source
port, destination address, destination port, and transport-layer
protocol.
The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in [RFC2119]. interpreted as described in [RFC2119].
3. Motivation 3. Motivation
The time and complications of setting up ICE [RFC5245] and DTLS-SRTP The time and complications of setting up ICE [RFC5245] and 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. the SDP attributes as they are defined today.
The specific problem is that there are attribute combinations which The specific problem is that there are attribute combinations which
make sense when specified on independent "m= " lines -- as with make sense when specified on independent "m= " lines -- as with
classical SDP -- that do not make sense when those "m=" lines are classical SDP -- that do not make sense when those "m=" lines are
then multiplexed over the same transport. To give an obvious then multiplexed over the same transport. To give an obvious
example, ICE permits each "m=" line to have an independently example, ICE permits each "m=" line to have an independently
specified ice-ufrag attribute. However, if the media from multiple specified ice-ufrag attribute. However, if the media from multiple
"m=" lines is multiplexed over the same ICE component, then the "m=" lines is multiplexed over the same ICE component, then the
meaning of media-level ice-ufrag attributes becomes muddled. meaning of media-level ice-ufrag attributes becomes muddled.
skipping to change at page 7, line 24 skipping to change at page 7, line 33
With the above semantic grouping as a reference, the proposed With the above semantic grouping as a reference, the proposed
framework classifies each attribute into one of the following framework classifies each attribute into one of the following
categories: categories:
4.1. Category: NORMAL 4.1. Category: NORMAL
Attributes that can be independently specified when multiplexing and Attributes that can be independently specified when multiplexing and
retain their original semantics. retain their original semantics.
In the example given below, the direction and label attributes are In the example given below, the direction and label attributes are
independently specified for audio and video m=lines. These independently specified for audio and video "m=" lines. These
attributes are not impacted by multiplexing these media streams over attributes are not impacted by multiplexing these media streams over
a single transport layer flow. a single transport layer flow.
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
m=audio 49172 RTP/AVP 99 m=audio 49172 RTP/AVP 99
a=sendonly a=sendonly
skipping to change at page 8, line 12 skipping to change at page 8, line 22
complicate the handling of multiplexed streams or might fail complicate the handling of multiplexed streams or might fail
multiplexing altogether. multiplexing altogether.
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 3456 RTP/AVP 97 // with zrtp m=audio 3456 RTP/AVP 97 // with zrtp
a=rtpmap:97 iLBC/8000 a=rtpmap:97 iLBC/8000
<allOneLine>
a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2 a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2
df881ae642c371ba46df df881ae642c371ba46df
</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 and their associated values (if any) that MUST be
being multiplexed. identical across all the media descriptions 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 be enabled reporting is done per RTP Session, RTCP Multiplexing MUST be enabled
for both the audio and video m=lines if they are transported over a for both the audio and video "m=" lines if they are transported over
single 5-tuple. a 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 9, line 18 skipping to change at page 9, line 26
t=0 0 t=0 0
m=audio 49170 RTP/AVP 0 m=audio 49170 RTP/AVP 0
b=AS:64 b=AS:64
m=video 51372 RTP/AVP 31 m=video 51372 RTP/AVP 31
b=AS:256 b=AS:256
4.5. Category: TRANSPORT 4.5. Category: TRANSPORT
Attributes that can be set normally for multiple items in a Attributes that can be set normally for multiple items in a
multiplexed group but the software MUST pick just one of the multiplexed group but the software MUST pick just one of the
attribute of the given type for use. The one chosen is the attribute attributes of the given type for use. The one chosen is the
associated with the "m=" line that represents the information being attribute associated with the "m=" line that represents the
used for the transport of the RTP. information being used for the transport of the RTP.
In the example below, "a=crypto" attribute is defined for both the In the example below, "a=crypto" attribute is defined for both the
audio and the video m=lines. The video media line's a=crypto audio and the video "m=" lines. The video media line's a=crypto
attribute is chosen since its mid value (bar) appears first in the attribute is chosen since its mid value (bar) appears first in the
a=group:BUNDLE line. This is due to BUNDLE grouping semantic a=group:BUNDLE line. This is due to BUNDLE grouping semantic
[I-D.ietf-mmusic-sdp-bundle-negotiation] which mandates the values [I-D.ietf-mmusic-sdp-bundle-negotiation] which mandates the values
from m=line corresponding to the mid appearing first on the from "m=" line corresponding to the mid appearing first on the
a=group:BUNDLE line to be considered for setting up the RTP a=group:BUNDLE line to be considered for setting up the RTP
Transport. Transport.
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
a=group:BUNDLE bar foo a=group:BUNDLE bar foo
m=audio 49172 RTP/AVP 99 m=audio 49172 RTP/AVP 99
skipping to change at page 10, line 41 skipping to change at page 11, line 22
a=fmtp:100 max-fr=30;max-fs=8040 a=fmtp:100 max-fr=30;max-fs=8040
a=sqn: 0 a=sqn: 0
a=cdsc: 1 video RTP/AVP 100 a=cdsc: 1 video RTP/AVP 100
a=cpar: a=rtcp-mux a=cpar: a=rtcp-mux
m=video 3456 RTP/AVP 101 m=video 3456 RTP/AVP 101
a=rtpmap:101 VP8/90000 a=rtpmap:101 VP8/90000
a=fmtp:100 max-fr=15;max-fs=1200 a=fmtp:100 max-fr=15;max-fs=1200
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. These descriptions for a given RTP Payload Type when repeated. These
Payload Types identify the same codec configuration as defined in the 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 Section 10.1.2 of [I-D.ietf-mmusic-sdp-bundle-negotiation] under this
context. 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
a=group:BUNDLE cam1, cam2 a=group:BUNDLE cam1, cam2
m = video 96 97 m= video 96 97
a=mid:cam1 a=mid:cam1
a=rtpmap:96 H264/90000 a=rtpmap:96 H264/90000
a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000; a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000;
max-mbps=108000; max-br=1000 max-mbps=108000; max-br=1000
a=rtpmap:97 H264/90000 a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000; a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000;
max-mbps=7200; max-br=200 max-mbps=7200; max-br=200
m = video 96 97 m= video 96 97
a=mid:cam2 a=mid:cam2
a=rtpmap:96 H264/90000 a=rtpmap:96 H264/90000
a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000; a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000;
max-mbps=108000; max-br=1000 max-mbps=108000; max-br=1000
a=rtpmap:97 H264/90000 a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000; a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000;
max-mbps=7200; max-br=200 max-mbps=7200; max-br=200
4.8. Category: SPECIAL 4.8. Category: SPECIAL
Attributes where the text in the source draft must be consulted for Attributes where the text in the specification defining the attribute
further handling when multiplexed. must be consulted for further handling when multiplexed.
As an example, for the attribute extmap, the specification defining As an example, for the attribute extmap, the specification defining
the extension MUST be referred to understand the multiplexing the extension must be referred to understand the multiplexing
implications. implications.
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
skipping to change at page 12, line 33 skipping to change at page 13, line 22
details regarding the assigned category, wherever necessary. details regarding the assigned category, wherever necessary.
5.1. RFC4566 - SDP: Session Description Protocol 5.1. RFC4566 - SDP: 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 | Mux Category | | Name | Notes | Level | Mux Category |
+-----------------+---------------------+-------+-------------------+ +-----------------+---------------------+-------+-------------------+
| sendrecv | Not impacted | B | NORMAL | | sendrecv | Not impacted | B | NORMAL |
| | | | | | | | | |
| sendonly | Not impacted | B | NORMAL | | sendonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| recvonly | Not impacted | B | NORMAL | | recvonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| inactive | Not impacted | B | NORMAL | | inactive | Not impacted | B | NORMAL |
| | | | | | | | | |
| cat | Not impacted | S | NORMAL | | cat | Not impacted | S | NORMAL |
skipping to change at page 14, line 13 skipping to change at page 15, line 6
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 | Mux Category | | Name | Notes | Level | Mux Category |
| 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. | | |
| | | | | | | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
RFC4585 Attribute Analysis RFC4585 Attribute Analysis
5.3. RFC5761 - Multiplexing RTP and RTCP 5.3. RFC5761 - Multiplexing RTP and RTCP
[RFC5761] discusses issues that arise when multiplexing RTP data [RFC5761] discusses issues that arise when multiplexing RTP data
packets and RTP Control Protocol (RTCP) packets on a single UDP port. packets and RTP Control Protocol (RTCP) packets on a single UDP port.
It describes when such multiplexing is and is not appropriate, and it It describes when such multiplexing is and is not appropriate, and it
skipping to change at page 17, line 16 skipping to change at page 18, line 16
| Name | Notes | Current | Mux Category | | Name | Notes | Current | Mux Category |
+--------------------+---------------------+---------+--------------+ +--------------------+---------------------+---------+--------------+
| dccp-service-code | If RFC6773 is not | M | NOT | | dccp-service-code | If RFC6773 is not | M | NOT |
| | being used in | | RECOMMENDED | | | being used in | | RECOMMENDED |
| | addition to | | | | | addition to | | |
| | 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 | | | | | it does not allow | | |
| | multiple | | | | | multiple | | |
| | connections on the | | | | | connections on the | | |
| | same 5-tuple. | | | | | same 5-tuple | | |
| | | | | | | | | |
+--------------------+---------------------+---------+--------------+ +--------------------+---------------------+---------+--------------+
RFC5762 Attribute Analysis RFC5762 Attribute Analysis
If RFC6773 is being used in addition to RFC5762 and provided that If RFC6773 is being used in addition to RFC5762 and provided that
DCCP-in-UDP layer has additional demultiplexing, then it may be DCCP-in-UDP layer has additional demultiplexing, then it may be
possible to use different DCCP service codes for each DCCP flow, possible to use different DCCP service codes for each DCCP flow,
given each uses a different DCCP port. Although doing so might given each uses a different DCCP port. Although doing so might
conflict with the media type of the "m=" line. None of this is conflict with the media type of the "m=" line. None of this is
standardized yet and it wouldn't work as explained. Hence standardized yet and it wouldn't work as explained. Hence
multiplexing MUST NOT be performed even in this alternate scenario. multiplexing must not be performed even in this alternate scenario.
5.9. RFC6773 - DCCP-UDP Encapsulation 5.9. RFC6773 - DCCP-UDP Encapsulation
[RFC6773] document specifies an alternative encapsulation of the [RFC6773] document specifies an alternative encapsulation of 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 | Mux Category | | Name | Notes | Level | Mux Category |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| dccp-port | Multiplexing MUST NOT be | M | NOT | | dccp-port | Multiplexing must not be | M | NOT |
| | performed due to potential | | RECOMMENDED | | | performed due to potential | | RECOMMENDED |
| | conflict between the port | | | | | conflict between the port | | |
| | used for DCCP | | | | | used for DCCP | | |
| | en/decapsulation and the RTP. | | | | | en/decapsulation and the RTP | | |
| | | | | | | | | |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
RFC6773 Attribute Analysis RFC6773 Attribute Analysis
Since RFC6773 is about tunneling DCCP in UDP, with the UDP port being RFC6773 is about tunneling DCCP in UDP, with the UDP port being the
the port of the DCCP en-/de-capsulation service. This encapsulation port of the DCCP en-/de-capsulation service. This encapsulation
allows arbitrary DCCP packets to be encapsulated and the DCCP port allows arbitrary DCCP packets to be encapsulated and the DCCP port
chosen MAY conflict with the port chosen for the RTP traffic. chosen may conflict with the port chosen for the RTP traffic.
For multiplexing several DCCP-in-UDP encapsulations on the same UDP For multiplexing several DCCP-in-UDP encapsulations on the same UDP
port, with no RTP traffic on the same port implies collapsing several port, with no RTP traffic on the same port implies collapsing several
DCCP port spaces together. This MAY or MAY NOT work depending on the DCCP port spaces together. This may or may not work depending on the
nature of DCCP encapsulations and ports choses thus rendering it to nature of DCCP encapsulations and ports choices thus rendering it to
be very application dependent. be very application dependent.
5.10. RFC5506 - Reduced-Size RTCP in RTP Profile 5.10. RFC5506 - Reduced-Size RTCP in RTP Profile
[RFC5506] discusses benefits and issues that arise when allowing [RFC5506] discusses benefits and issues that arise when allowing
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 | Mux | | Name | Notes | Level | Mux |
skipping to change at page 20, line 15 skipping to change at page 21, line 15
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
| ice-lite | Not Impacted | S | NORMAL | | ice-lite | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-options | Not Impacted | S | NORMAL | | ice-options | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-mismatch | Not Impacted | S | NORMAL | | ice-mismatch | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-pwd | ice-pwd MUST be the one | B | TRANSPORT | | ice-pwd | ice-pwd must be the one | B | TRANSPORT |
| | that corresponds to the | | | | | that corresponds to the | | |
| | m=line chosen for | | | | | "m=" line chosen for | | |
| | setting up the | | | | | setting up the | | |
| | underlying transport | | | | | underlying transport | | |
| | flow | | | | | flow | | |
| | | | | | | | | |
| ice-ufrag | ice-ufrag MUST be the | B | TRANSPORT | | ice-ufrag | ice-ufrag must be the | B | TRANSPORT |
| | one that corresponds to | | | | | one that corresponds to | | |
| | the m=line chosen for | | | | | the "m=" line chosen | | |
| | setting up the | | | | | for setting up the | | |
| | underlying transport | | | | | underlying transport | | |
| | flow | | | | | flow | | |
| | | | | | | | | |
| candidate | ice candidate MUST be | M | TRANSPORT | | candidate | ice candidate must be | M | TRANSPORT |
| | the one that | | | | | the one that | | |
| | corresponds to the | | | | | corresponds to the "m=" | | |
| | m=line chosen for | | | | | line chosen for setting | | |
| | setting up the | | | | | up the underlying | | |
| | underlying transport | | | | | transport flow | | |
| | flow | | |
| | | | | | | | | |
| remote-candidates | ice remote candidate | M | TRANSPORT | | remote-candidates | ice remote candidate | M | TRANSPORT |
| | MUST be the one that | | | | | must be the one that | | |
| | corresponds to the | | | | | corresponds to the "m=" | | |
| | m=line chosen for | | | | | line chosen for setting | | |
| | setting up the | | | | | up the underlying | | |
| | underlying transport | | | | | transport flow | | |
| | flow | | |
| | | | | | | | | |
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
RFC5245 Attribute Analysis RFC5245 Attribute Analysis
5.13. RFC5285 - RTP Header Extensions 5.13. RFC5285 - RTP Header Extensions
[RFC5285] provides a general mechanism to use the header extension [RFC5285] provides a general mechanism to use the header extension
feature of RTP (the Real-Time Transport Protocol). It provides the feature of RTP (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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------+-------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
| extmap | Specific RTP extension document | B | SPECIAL | | extmap | Specific RTP extension document | B | SPECIAL |
| | MUST be referred | | | | | must be referred | | |
| | | | | | | | | |
+---------+-------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
RFC5285 Attribute Analysis RFC5285 Attribute Analysis
5.14. RFC3605 - RTCP attribute in SDP 5.14. RFC3605 - RTCP attribute in SDP
Originally, SDP assumed that RTP and RTCP were carried on consecutive Originally, SDP assumed that RTP and RTCP were carried on consecutive
ports. However, this is not always true when NATs are involved. ports. However, this is not always true when NATs are involved.
[RFC3605] specifies an early mechanism to indicate the RTCP port. [RFC3605] specifies an early mechanism to indicate the RTCP port.
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| rtcp | 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
skipping to change at page 22, line 29 skipping to change at page 23, line 29
| | | | | | | | | |
| fmtp | The attribute value | SR | IDENTICAL-PER-PT | | fmtp | The attribute value | SR | IDENTICAL-PER-PT |
| | must be same for a | | | | | must be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
RFC5576 Attribute Analysis RFC5576 Attribute Analysis
If SSRCs are repeated across m=lines being multiplexed, they MUST all If SSRCs are repeated across "m=" lines being multiplexed, they must
represent the same underlying RTP Source. all represent the same underlying RTP Source.
5.16. RFC7273 - RTP Clock Source Signalling 5.16. RFC7273 - RTP Clock Source Signalling
[RFC7273] specifies Session Description Protocol (SDP) signalling [RFC7273] specifies 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 | Mux Category | | Name | Notes | Level | Mux Category |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
skipping to change at page 24, line 45 skipping to change at page 25, line 45
[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 | Mux Category | | Name | Notes | Level | Mux Category |
+---------+-----------------+-------+--------------+ +---------+---------------+-------+--------------+
| cfw-id | Not Applicable | M | NORMAL | | cfw-id | Not Impacted | M | NORMAL |
| | | | | | | | | |
+---------+-----------------+-------+--------------+ +---------+---------------+-------+--------------+
RFC6230 Attribute Analysis RFC6230 Attribute Analysis
5.22. RFC6364 - SDP Elements for FEC Framework 5.22. RFC6364 - SDP Elements for FEC Framework
[RFC6364] specifies the use of the Session Description Protocol (SDP) [RFC6364] specifies the use of 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
skipping to change at page 27, line 37 skipping to change at page 28, line 37
[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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | 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 34 skipping to change at page 29, line 34
+----------------------+---------------+-------+--------------+ +----------------------+---------------+-------+--------------+
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 | Mux 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- | Not Impacted | M | NORMAL | | loopback rtp-media- | Not Impacted | M | NORMAL |
| loopback | | | | | loopback | | | |
| | | | | | | | | |
| loopback-source | Not Impacted | M | NORMAL | | loopback-source | Not Impacted | M | NORMAL |
skipping to change at page 29, line 18 skipping to change at page 30, line 18
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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| rtcp-unicast | The attribute MUST be | M | IDENTICAL | | rtcp-unicast | The attribute must be | M | IDENTICAL |
| | reported across all m=lines | | | | | reported across all "m=" | | |
| | multiplexed | | | | | lines multiplexed | | |
| | | | | | | | | |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
RFC5760 Attribute Analysis RFC5760 Attribute Analysis
5.31. RFC3611 - RTCP XR 5.31. RFC3611 - RTCP XR
[RFC3611] defines the Extended Report (XR) packet type for the RTP [RFC3611] defines the Extended Report (XR) packet type for 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
skipping to change at page 32, line 14 skipping to change at page 33, line 14
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
| bcap | Inherit the category SUM as | B | INHERIT | | bcap | Inherit the category SUM as | B | INHERIT |
| | applicable to b= attribute | | | | | applicable to b= attribute | | |
| | | | | | | | | |
| bcap-v0 | Not Impacted | B | NORMAL | | bcap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
| ccap | The connection address type MUST | B | IDENTICAL | | ccap | The connection address type must | B | IDENTICAL |
| | be identical across all the | | | | | be identical across all the | | |
| | multiplexed m= lines. | | | | | multiplexed "m=" lines | | |
| | | | | | | | | |
| ccap-v0 | Not Impacted. | B | NORMAL | | ccap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
| icap | Not Impacted | B | NORMAL | | icap | Not Impacted | B | NORMAL |
| | | | | | | | | |
| icap-v0 | Not Impacted | B | NORMAL | | icap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
RFC7006 - Attribute Analysis RFC7006 - Attribute Analysis
5.35. RFC4567 - Key Management Extensions for SDP and RTSP 5.35. RFC4567 - Key Management Extensions for SDP and RTSP
skipping to change at page 32, line 41 skipping to change at page 33, line 41
(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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| key-mgmt | Key management protocol MUST be | B | IDENTICAL | | key-mgmt | Key management protocol must be | B | IDENTICAL |
| | identical across all the m=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
5.36. RFC4572 - Comedia over TLS in SDP 5.36. RFC4572 - Comedia over TLS in SDP
[RFC4572] specifies how to establish secure connection-oriented media [RFC4572] specifies how to establish secure connection-oriented media
transport sessions over the Transport Layer Security (TLS) protocol transport sessions over the Transport Layer Security (TLS) protocol
using the Session Description Protocol (SDP). It defines a new SDP using the Session Description Protocol (SDP). It defines a new SDP
skipping to change at page 33, line 22 skipping to change at page 34, line 22
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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
| fingerprint | fingerprint value from the | B | TRANSPORT | | fingerprint | fingerprint value from the | B | TRANSPORT |
| | m=line defining the | | | | | "m=" line defining the | | |
| | underlying transport is | | | | | underlying transport is | | |
| | chosen | | | | | chosen | | |
| | | | | | | | | |
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
RFC4572 Attribute Analysis RFC4572 Attribute Analysis
5.37. RFC4570 - SDP Source Filters 5.37. RFC4570 - SDP Source Filters
[RFC4570] describes how to adapt the Session Description Protocol [RFC4570] describes how to adapt the Session Description Protocol
skipping to change at page 33, line 45 skipping to change at page 34, line 45
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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| source-filter | The attribute MUST be | B | IDENTICAL | | source-filter | The attribute must be | B | IDENTICAL |
| | repeated across all m=lines | | | | | repeated across all "m=" | | |
| | multiplexed | | | | | lines multiplexed | | |
| | | | | | | | | |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
RFC4570 Attribute Analysis RFC4570 Attribute Analysis
5.38. RFC6128 - RTCP Port for Multicast Sessions 5.38. RFC6128 - RTCP Port for Multicast Sessions
The Session Description Protocol (SDP) has an attribute that allows The Session Description Protocol (SDP) has an attribute that allows
RTP applications to specify an address and a port associated with the RTP applications to specify an address and a port associated with the
RTP Control Protocol (RTCP) traffic. In RTP-based source-specific RTP Control Protocol (RTCP) traffic. In RTP-based source-specific
skipping to change at page 34, line 23 skipping to change at page 35, line 23
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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
| multicast-rtcp | Multicast RTCP port MUST | B | IDENTICAL | | multicast-rtcp | Multicast RTCP port must | B | IDENTICAL |
| | be identical across all | | | | | be identical across all | | |
| | the m=lines | | | | | the "m=" lines | | |
| | | | | | | | | |
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
RFC6128 Attribute Analysis RFC6128 Attribute Analysis
5.39. RFC6189 - ZRTP 5.39. RFC6189 - ZRTP
[RFC6189] defines ZRTP, a protocol for media path Diffie-Hellman [RFC6189] defines ZRTP, a protocol for media path Diffie-Hellman
exchange to agree on a session key and parameters for establishing exchange to agree on a session key and parameters for establishing
unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice
over IP (VoIP) applications. over IP (VoIP) applications.
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| zrtp-hash | Complicates if all the | M | NOT | | zrtp-hash | Complicates if all the "m=" | M | NOT |
| | m=lines are not authenticated | | RECOMMENDED | | | lines are not authenticated | | RECOMMENDED |
| | as given in the example below | | |
| | | | | | | | | |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
RFC6189 Attribute Analysis RFC6189 Attribute Analysis
5.40. RFC4145 - Connection-Oriented Media 5.40. RFC4145 - Connection-Oriented Media
[RFC4145] describes how to express media transport over TCP using the [RFC4145] describes how to express media transport over TCP using 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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | 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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| altc | The IP Address and port must be the | M | TRANSPORT | | altc | The IP Address and port must be the | M | TRANSPORT |
| | one that corresponds to the m=line | | | | | one that corresponds to the "m=" | | |
| | chosen for setting up the underlying | | | | | line chosen for setting up the | | |
| | transport flow. | | | | | underlying transport flow | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
RFC6947 Attribute Analysis RFC6947 Attribute Analysis
5.42. RFC7195 - SDP Extension for Circuit Switched Bearers in PSTN 5.42. RFC7195 - SDP Extension for Circuit Switched Bearers in PSTN
[RFC7195] describes use cases, requirements, and protocol extensions [RFC7195] describes use cases, requirements, and protocol extensions
for using the Session Description Protocol (SDP) offer/answer model for using 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 | Mux 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 | Mux Category | | Name | Notes | Level | Mux Category |
+------------+----------------+-------+--------------+ +------------+---------------+-------+--------------+
| rtcp-idms | Not Impacted. | M | NORMAL | | rtcp-idms | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------+----------------+-------+--------------+ +------------+---------------+-------+--------------+
RFC7272 Attribute Analysis RFC7272 Attribute Analysis
5.44. RFC5159 - OMA BCAST SDP Attributes 5.44. RFC5159 - 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.
+---------------------+---------------+-------+--------------+ +---------------------+---------------+-------+--------------+
skipping to change at page 37, line 33 skipping to change at page 38, line 33
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 | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
| ike-setup | Attribute MUST be | B | IDENTICAL | | ike-setup | Attribute must be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
| | m=lines | | | | | "m=" lines | | |
| | | | | | | | | |
| psk-fingerprint | Attribute MUST be | B | IDENTICAL | | psk-fingerprint | Attribute must be | B | IDENTICAL |
| | 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 |
| | identical across all the | | | | | identical across all the | | |
| | m=lines | | | | | "m=" lines | | |
| | | | | | | | | |
| ike-esp-udpencap | Attribute MUST be | B | IDENTICAL | | ike-esp-udpencap | Attribute must be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
| | m=lines | | | | | "m=" lines | | |
| | | | | | | | | |
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
RFC6193 Attribute Analysis RFC6193 Attribute Analysis
With the above SDP constraints, a session multiplexed with multiple With the above SDP constraints, a session multiplexed with multiple
m=lines will use only one IPSec association for all of the m= lines. "m=" lines will use only one IPSec association for all of the "m="
lines.
5.46. RFC2326 - Real Time Streaming Protocol 5.46. RFC2326 - Real Time Streaming Protocol
The Real Time Streaming Protocol, or RTSP, is an application-level The Real Time Streaming Protocol, or RTSP, is an application-level
protocol for control over the delivery of data with real-time protocol for control over the delivery of data with real-time
properties. RTSP provides an extensible framework to enable properties. RTSP provides an extensible framework to enable
controlled, on-demand delivery of real-time data, such as audio and controlled, on-demand delivery of real-time data, such as audio and
video. video.
+----------+---------------------------------+-------+--------------+ +----------+---------------------------------+-------+--------------+
skipping to change at page 38, line 35 skipping to change at page 39, line 36
| control | RTSP is not supported for RTP | B | NOT | | control | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED | | | Stream multiplexing | | RECOMMENDED |
| | | | | | | | | |
| mtag | RTSP is not supported for RTP | B | NOT | | mtag | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED | | | Stream multiplexing | | RECOMMENDED |
| | | | | | | | | |
+----------+---------------------------------+-------+--------------+ +----------+---------------------------------+-------+--------------+
RFC2326 Attribute Analysis RFC2326 Attribute Analysis
[RFC2326] defines SDP attributes that are applicable in the
declarative usage of SDP alone. For purposes of this document, only
the Offer/Answer usage of SDP is considered as mandated by
[I-D.ietf-mmusic-sdp-bundle-negotiation].
5.47. RFC6064 - SDP and RTSP Extensions for 3GPP 5.47. RFC6064 - SDP and RTSP Extensions for 3GPP
The Packet-switched Streaming Service (PSS) and the Multimedia The Packet-switched Streaming Service (PSS) and the Multimedia
Broadcast/Multicast Service (MBMS) defined by 3GPP use the Session Broadcast/Multicast Service (MBMS) defined by 3GPP use 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 | Mux Category | | Name | Notes | Level | Mux Category |
skipping to change at page 41, line 24 skipping to change at page 42, line 30
RFC6064 Attribute Analysis RFC6064 Attribute Analysis
[RFC6064] defines SDP attributes that are applicable in the [RFC6064] defines SDP attributes that are applicable in the
declarative usage of SDP alone. For purposes of this document, only declarative usage of SDP alone. For purposes of this document, only
the Offer/Answer usage of SDP is considered as mandated by the Offer/Answer usage of SDP is considered as mandated by
[I-D.ietf-mmusic-sdp-bundle-negotiation]. [I-D.ietf-mmusic-sdp-bundle-negotiation].
5.48. RFC3108 - ATM SDP 5.48. RFC3108 - ATM SDP
RFC3108 [RFC3108] describes conventions for using the Session [RFC3108] describes conventions for using the Session Description
Description Protocol (SDP) described for controlling ATM Bearer Protocol (SDP) described for controlling ATM Bearer Connections, and
Connections, and any associated ATM Adaptation Layer (AAL). any associated ATM Adaptation Layer (AAL).
+------------------------+--------------+-------+--------------+ +------------------------+------------------+-------+---------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------------------+--------------+-------+--------------+ +------------------------+------------------+-------+---------------+
| aalType | Not Impacted | B | NORMAL | | aalType | Refer to notes | B | NOT |
| eecid | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| aalType | Not Impacted | B | NORMAL | | eecid | Refer to notes | B | NOT |
| capability | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| qosClass | Not Impacted | B | NORMAL | | capability | Refer to notes | B | NOT |
| bcob | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| stc | Not Impacted | B | NORMAL | | qosClass | Refer to notes | B | NOT |
| upcc | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| atmQOSparms | Not Impacted | B | NORMAL | | bcob | Refer to notes | B | NOT |
| atmTrfcDesc | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| abrParms | Not Impacted | B | NORMAL | | stc | Refer to notes | B | NOT |
| abrSetup | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| bearerType | Not Impacted | B | NORMAL | | upcc | Refer to notes | B | NOT |
| lij | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| anycast | Not Impacted | B | NORMAL | | atmQOSparms | Refer to notes | B | NOT |
| cache | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| bearerSigIE | Not Impacted | B | NORMAL | | atmTrfcDesc | Refer to notes | B | NOT |
| aalApp | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| cbrRate | Not Impacted | B | NORMAL | | abrParms | Refer to notes | B | NOT |
| sbc | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| clkrec | Not Impacted | B | NORMAL | | abrSetup | Refer to notes | B | NOT |
| fec | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| prtfl | Not Impacted | B | NORMAL | | bearerType | Refer to notes | B | NOT |
| structure | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| cpsSDUsize | Not Impacted | B | NORMAL | | lij | Refer to notes | B | NOT |
| aal2CPS | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| aal2CPSSDUrate | Not Impacted | B | NORMAL | | anycast | Refer to notes | B | NOT |
| aal2sscs3661unassured | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| aal2sscs3661assured | Not Impacted | B | NORMAL | | cache | Refer to notes | B | NOT |
| aal2sscs3662 | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| aal5sscop | Not Impacted | B | NORMAL | | bearerSigIE | Refer to notes | B | NOT |
| atmmap | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| silenceSupp | Not Impacted | B | NORMAL | | aalApp | Refer to notes | B | NOT |
| ecan | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| gc | Not Impacted | B | NORMAL | | cbrRate | Refer to notes | B | NOT |
| profileDesc | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| vsel | Not Impacted | B | NORMAL | | sbc | Refer to notes | B | NOT |
| dsel | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| fsel | Not Impacted | B | NORMAL | | clkrec | Refer to notes | B | NOT |
| onewaySel | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| codecconfig | Not Impacted | B | NORMAL | | fec | Refer to notes | B | NOT |
| isup_usi | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| uiLayer1_Prot | Not Impacted | B | NORMAL | | prtfl | Refer to notes | B | NOT |
| chain | Not Impacted | B | NORMAL | | | below | | RECOMMENDED |
| | | | | | structure | Refer to notes | B | NOT |
+------------------------+--------------+-------+--------------+ | | below | | RECOMMENDED |
| cpsSDUsize | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| aal2CPS | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| aal2CPSSDUrate | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| aal2sscs3661unassured | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| aal2sscs3661assured | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| aal2sscs3662 | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| aal5sscop | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| atmmap | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| silenceSupp | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| ecan | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| gc | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| profileDesc | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| vsel | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| dsel | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| fsel | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| onewaySel | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| codecconfig | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| isup_usi | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| uiLayer1_Prot | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| chain | Refer to notes | B | NOT |
| | below | | RECOMMENDED |
| | | | |
+------------------------+------------------+-------+---------------+
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
single media group. In all cases addressed by RFC3108, a real-time single media group. In all cases addressed by RFC3108, a real-time
media stream (voice, video, voiceband data, pseudo-wire and others) media stream (voice, video, voiceband data, pseudo-wire and others)
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.
[I-D.ietf-mmusic-sdp-bundle-negotiation] is applicable only for
nettypes IN and address types "IP4" or "IP6".
5.49. 3GPP TS 26.114 5.49. 3GPP TS 26.114
[R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and [R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and
interaction interaction
+----------------------+-------------------------+-------+----------+ +----------------------+-------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------------------+-------------------------+-------+----------+ +----------------------+-------------------------+-------+----------+
| 3gpp_sync_info | Usage defined for the | M | NORMAL | | 3gpp_sync_info | Usage defined for the | M | NORMAL |
| | IP Multimedia Subsystem | | | | | IP Multimedia Subsystem | | |
| | | | | | | | | |
| 3gpp_MaxRecvSDUSize | Usage defined for the | M | NORMAL | | 3gpp_MaxRecvSDUSize | Usage defined for the | M | NORMAL |
| | IP Multimedia Subsystem | | | | | IP Multimedia Subsystem | | |
| | | | | | | | | |
skipping to change at page 43, line 23 skipping to change at page 45, line 29
| | | | | | | | | |
+----------------------+-------------------------+-------+----------+ +----------------------+-------------------------+-------+----------+
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 | Mux | | Name | Notes | Level | Mux Category |
| | | | Category | +---------------------+---------------+-------+--------------+
+---------------------+--------------+----------------+-------------+ | PSCid | Not Impacted | S | NORMAL |
| PSCid | Not Impacted | Not-Applicable | NORMAL | | | | | |
| | | | | | bc_service | Not Impacted | S | NORMAL |
| bc_service | Not Impacted | Not-Applicable | NORMAL | | | | | |
| | | | | | bc_program | Not Impacted | S | NORMAL |
| bc_program | Not Impacted | Not-Applicable | NORMAL | | | | | |
| | | | | | bc_service_package | Not Impacted | S | 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 | Mux |
| | | | Category | | | | | Category |
skipping to change at page 45, line 11 skipping to change at page 47, line 11
[R3GPPTS24.229] specifies IP multimedia call control protocol based [R3GPPTS24.229] specifies IP multimedia call control protocol based
on Session Initial protocol and Session Description Protocol. on Session Initial protocol and Session Description Protocol.
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| secondary-realm | secondary-realm must be | M | TRANSPORT | | secondary-realm | secondary-realm must be | M | TRANSPORT |
| | the one that corresponds | | | | | the one that corresponds | | |
| | to the m=line chosen for | | | | | to the "m=" line chosen | | |
| | setting up the underlying | | | | | for setting up the | | |
| | transport flow. | | | | | underlying transport flow | | |
| | | | | | | | | |
| visited-realm | visited-realm must be | M | TRANSPORT | | visited-realm | visited-realm must be | M | TRANSPORT |
| | the one that corresponds | | | | | the one that corresponds | | |
| | to the m=line chosen for | | | | | to the "m=" line chosen | | |
| | setting up the underlying | | | | | for setting up the | | |
| | transport flow. | | | | | 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-att | Not Impacted | M | NORMAL | | omr-s-att | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-m-bw | Not Impacted | M | NORMAL | | omr-m-bw | Not Impacted | M | NORMAL |
skipping to change at page 46, line 43 skipping to change at page 48, line 43
| | | | | | | | | |
| T38VendorInfo | 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 Q.1970
[ITU-T-REC.Q1970] defines BICC IP bearer control protocol. [Q.1970] defines BICC IP bearer control protocol.
+--------+---------------+-------+--------------+ +--------+---------------------------------------+-------+----------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux |
+--------+---------------+-------+--------------+ | | | | Category |
| ipbcp | Not Impacted | S | NORMAL | +--------+---------------------------------------+-------+----------+
| | | | | | ipbcp | ipbcp version identifies type of | S | SPECIAL |
+--------+---------------+-------+--------------+ | | IPBCP message used in BICC (ITU-T | | |
| | Q.1901) environment which are limited | | |
| | to single media payload. Pertinent | | |
| | ITU.T specifications needs to be | | |
| | referred while multiplexing | | |
| | | | |
+--------+---------------------------------------+-------+----------+
ITU-T-REC.Q1970 Attribute Analysis ITU-T Q.1970 Attribute Analysis
5.56. ITU-T H.248.15 5.56. ITU-T H.248.15
ITU-T H.248.15 [H.248.15] defines Gateway Control Protocol SDP H.248 ITU-T H.248.15 [H.248.15] defines Gateway Control Protocol SDP H.248
package attribute package attribute
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| h248item | It is only applicable for | B | SPECIAL | | h248item | It is only applicable for | B | SPECIAL |
| | signaling the inclusion of H.248 | | | | | signaling the inclusion of H.248 | | |
| | extension packages to a gateway | | | | | extension packages to a gateway | | |
| | via the local and remote | | | | | via the local and remote | | |
| | descriptors. The attribute itself | | | | | descriptors. The attribute itself | | |
| | is unaffected by multiplexing, but | | | | | is unaffected by multiplexing, but | | |
| | the packaged referenced in a | | | | | the packaged referenced in a | | |
| | specific use of the attribute may | | | | | specific use of the attribute 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. | | |
| | This is only a concern in | | | | | This is only a concern in | | |
| | environments using a decomposed | | | | | environments using a decomposed | | |
| | server/gateway with H.248 signaled | | | | | server/gateway with H.248 signaled | | |
| | between them. The ITU-T will need | | | | | between them. The ITU-T will need | | |
| | to do further analysis of various | | | | | to do further analysis of various | | |
| | packages when they specify how to | | | | | packages when they specify how to | | |
| | signal the use of multiplexing to | | | | | signal the use of multiplexing to | | |
| | a gateway. | | | | | a gateway | | |
| | | | | | | | | |
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
ITU-T H.248.15 Attribute Analysis ITU-T H.248.15 Attribute Analysis
5.57. RFC4975 - The Message Session Relay Protocol 5.57. RFC4975 - The Message Session Relay Protocol
[RFC4975] the Message Session Relay Protocol, a protocol for [RFC4975] the Message Session Relay Protocol, a protocol for
transmitting a series of related instant messages in the context of a transmitting a series of related instant messages in the context of a
session. Message sessions are treated like any other media stream session. Message sessions are treated like any other media stream
skipping to change at page 48, line 27 skipping to change at page 50, line 33
| | | | | | | | | |
+-----------------------+---------------+-------+--------------+ +-----------------------+---------------+-------+--------------+
RFC4975 Attribute Analysis RFC4975 Attribute Analysis
5.58. Historical Attributes 5.58. 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 | Mux Category | | Name | Notes | Level | Mux Category |
+----------+---------------------+----------------+-----------------+ +----------+----------------------+-------+------------------+
| rtpred1 | Historic | Not-Applicable | NOT RECOMMENDED | | rtpred1 | Historic attributes | M | NOT RECOMMENDED |
| | attributes. | | | | | | | |
| | | | | | rtpred2 | Historic attributes | M | NOT RECOMMENDED |
| rtpred2 | Historic | Not-Applicable | NOT RECOMMENDED | | | | | |
| | attributes. | | | +----------+----------------------+-------+------------------+
| | | | |
+----------+---------------------+----------------+-----------------+
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
[RFC4566] defines the Session Description Protocol (SDP) that is
intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of
multimedia session initiation.
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| bwtype:CT | Not Impacted | S | NORMAL | | bwtype:CT | Not Impacted | S | NORMAL |
| | | | | | | | | |
| bwtype:AS | For the media level usage, the | B | SUM | | bwtype:AS | For the media level usage, the | B | SUM |
| | aggregate of individual bandwidth | | | | | aggregate of individual bandwidth | | |
| | values is considered. | | | | | values is considered | | |
| | | | | | | | | |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
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
skipping to change at page 50, line 27 skipping to change at page 52, line 34
| | 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
sum with maxprate and the per-packet overhead would inflate the value computed sum with maxprate and the per-packet overhead would inflate
significantly. Instead performing multiplication and adding the the value significantly. Instead performing multiplication and
individual values is a more appropriate usage. adding the individual values is a more appropriate usage.
7. rtcp-fb Attribute Analysis 7. rtcp-fb Attribute Analysis
This section analyzes rtcp-fb SDP attributes. This section analyzes rtcp-fb SDP attributes.
7.1. RFC4585 - RTP/AVPF 7.1. RFC4585 - RTP/AVPF
[RFC4585] defines an extension to the Audio-visual Profile (AVP) that [RFC4585] defines an extension to the Audio-visual Profile (AVP) that
enables receivers to provide, statistically, more immediate feedback enables receivers to provide, statistically, more immediate feedback
to the senders and thus allows for short-term adaptation and to the senders and thus allows for short-term adaptation and
efficient feedback-based repair mechanisms to be implemented. efficient feedback-based repair mechanisms to be implemented.
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| Attr | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
| 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 | | |
| | | | | | | | | |
| nack | The attribute value must | M | IDENTICAL-PER-PT | | nack | The attribute value must | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack pli | The attribute value must | M | IDENTICAL-PER-PT | | nack pli | The attribute value must | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack sli | The attribute value must | M | IDENTICAL-PER-PT | | nack sli | The attribute value must | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack | The attribute value must | M | IDENTICAL-PER-PT | | nack | The attribute value must | M | IDENTICAL-PER-PT |
| rpsi | be same for a given codec | | | | rpsi | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack app | Feedback parameters MUST | M | SPECIAL | | nack app | Feedback parameters must | M | SPECIAL |
| | be handled in the app | | | | | be handled in the app | | |
| | specific way when | | | | | specific way when | | |
| | multiplexed | | | | | multiplexed | | |
| | | | | | | | | |
| trr-int | The attribute value must | M | IDENTICAL-PER-PT | | trr-int | The attribute value must | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
RFC4585 Attribute Analysis RFC4585 Attribute Analysis
7.2. RFC5104 - Codec Control Messages in AVPF 7.2. RFC5104 - Codec Control Messages in AVPF
[RFC5104] specifies a few extensions to the messages defined in the [RFC5104] specifies a few extensions to the messages defined in the
Audio-Visual Profile with Feedback (AVPF). They are helpful Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls. in smaller multicast environments and point-to-point calls.
+-------+-------------------------------+-------+-------------------+ +------+--------------------------------+-------+-------------------+
| Attr | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
| 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
[RFC6285] describes a method using the existing RTP and RTP Control
Protocol (RTCP) machinery that reduces the acquisition delay. In
this method, an auxiliary unicast RTP session carrying the Reference
Information to the receiver precedes or accompanies the multicast
stream. This unicast RTP flow can be transmitted at a faster than
natural bitrate to further accelerate the acquisition. The
motivating use case for this capability is multicast applications
that carry real-time compressed audio and video.
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| nack | The attribute value must be | M | IDENTICAL-PER-PT | | nack | The attribute value must be | M | IDENTICAL-PER-PT |
| rai | same for a given codec | | | | rai | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
RFC6285 Attribute Analysis RFC6285 Attribute Analysis
skipping to change at page 54, line 7 skipping to change at page 56, line 7
| nack | The attribute value must be | M | IDENTICAL-PER-PT | | nack | The attribute value must be | M | IDENTICAL-PER-PT |
| pslei | same for a given codec | | | | pslei | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
RFC6642 Attribute Analysis RFC6642 Attribute Analysis
7.6. RFC5104 - Codec Control Messages in AVPF 7.6. RFC5104 - Codec Control Messages in AVPF
[RFC5104] specifies a few extensions to the messages defined in the
Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls.
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Attr | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
| 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 | | |
| | | | | | | | | |
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value must be | M | IDENTICAL-PER-PT |
skipping to change at page 54, line 33 skipping to change at page 56, line 38
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value must be | M | IDENTICAL-PER-PT |
| vbcm | same for a given codec | | | | vbcm | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
RFC5104 Attribute Analysis RFC5104 Attribute Analysis
8. group Attribute Analysis 8. group Attribute Analysis
This section analyzes SDP "group" semantics. This section analyzes SDP "group" attribute 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 | Mux Category | | Name | Notes | Level | Mux Category |
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| group:LS | Not Impacted | S | NORMAL | | group:LS | Not Impacted | S | NORMAL |
skipping to change at page 57, line 20 skipping to change at page 59, line 28
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
RFC7104 Attribute Analysis RFC7104 Attribute Analysis
9. ssrc-group Attribute Analysis 9. ssrc-group Attribute Analysis
This section analyzes "ssrc-group" semantics. This section analyzes "ssrc-group" semantics.
9.1. RFC5576 - Source-Specific SDP Attributes 9.1. RFC5576 - Source-Specific SDP Attributes
[RFC5576] defines a mechanism to describe RTP media sources, which
are identified by their synchronization source (SSRC) identifiers, in
SDP, to associate attributes with these sources, and to express
relationships among sources. It also defines several source-level
attributes that can be used to describe properties of media sources.
+-------------------+---------------+-------+--------------+ +-------------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-------------------+---------------+-------+--------------+ +-------------------+---------------+-------+--------------+
| ssrc-group:FID | Not Impacted | SR | NORMAL | | ssrc-group:FID | Not Impacted | SR | NORMAL |
| | | | | | | | | |
| ssrc-group:FEC | Not Impacted | SR | NORMAL | | ssrc-group:FEC | Not Impacted | SR | NORMAL |
| | | | | | | | | |
| ssrc-groupFEC-FR | Not Impacted | SR | NORMAL | | ssrc-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
[RFC7104] defines the semantics for grouping redundant streams in the
Session Description Protocol (SDP). The semantics defined in this
document are to be used with the SDP Grouping Framework. Grouping
semantics at the Synchronization Source (SSRC) level are also defined
in this document for RTP streams using SSRC multiplexing.
+-----------------+---------------+-------+--------------+ +-----------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-----------------+---------------+-------+--------------+ +-----------------+---------------+-------+--------------+
| ssrc-group:DUP | Not Impacted | SR | NORMAL | | ssrc-group:DUP | Not Impacted | SR | NORMAL |
| | | | | | | | | |
+-----------------+---------------+-------+--------------+ +-----------------+---------------+-------+--------------+
RFC7104 Attribute Analysis RFC7104 Attribute Analysis
10. QoS Mechanism Token Analysis 10. QoS Mechanism Token Analysis
This section analyzes QoS tokes specified with SDP. This section analyzes QoS tokes specified with SDP.
10.1. RFC5432 - QoS Mechanism Selection in SDP 10.1. RFC5432 - QoS Mechanism Selection in SDP
+-------+---------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | [RFC5432] defines procedures to negotiate QOS mechanisms using the
| | | | Category | Session Description Protocol (SDP) offer/answer model.
+-------+---------------------------------------+-------+-----------+
| rsvp | Not Impacted, since QOS mechanisms | B | NORMAL | +-------+---------------+-------+--------------+
| | are applied per flow. | | | | Name | Notes | Level | Mux Category |
| | | | | +-------+---------------+-------+--------------+
| nsis | Not Impacted, since QOS mechanisms | B | NORMAL | | rsvp | Not Impacted | B | NORMAL |
| | are applied per flow. | | | | | | | |
| | | | | | nsis | Not Impacted | B | NORMAL |
+-------+---------------------------------------+-------+-----------+ | | | | |
+-------+---------------+-------+--------------+
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
[RFC4566] defines the Session Description Protocol (SDP) that is
intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of
multimedia session initiation.
+------+------------------------------------+-------+---------------+ +------+------------------------------------+-------+---------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------+------------------------------------+-------+---------------+ +------+------------------------------------+-------+---------------+
| k= | It is NOT recommended to use this | S | NOT | | k= | It is NOT recommended to use this | S | NOT |
| | attribute | | RECOMMENDED | | | attribute | | RECOMMENDED |
| | | | | | | | | |
+------+------------------------------------+-------+---------------+ +------+------------------------------------+-------+---------------+
RFC4566 Attribute Analysis RFC4566 Attribute Analysis
12. content Attribute Analysis 12. content Attribute Analysis
12.1. RFC4796 12.1. RFC4796
[RFC4796] defines a new Session Description Protocol (SDP) media-
level attribute, 'content'. The 'content' attribute defines the
content of the media stream to a more detailed level than the media
description line. The sender of an SDP session description can
attach the 'content' attribute to one or more media streams. The
receiving application can then treat each media stream differently
(e.g., show it on a big or small screen) based on its content.
+------------------+---------------+-------+--------------+ +------------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------------+---------------+-------+--------------+ +------------------+---------------+-------+--------------+
| content:slides | Not Impacted | M | NORMAL | | content:slides | Not Impacted | M | NORMAL |
| | | | | | | | | |
| content:speaker | Not Impacted | M | NORMAL | | content:speaker | Not Impacted | M | NORMAL |
| | | | | | | | | |
| content:main | Not Impacted | M | NORMAL | | content:main | Not Impacted | M | NORMAL |
| | | | | | | | | |
| content:sl | Not Impacted | M | NORMAL | | content:sl | Not Impacted | M | NORMAL |
skipping to change at page 59, line 41 skipping to change at page 62, line 31
| | reuse of SSRCs | | | | | reuse of SSRCs | | |
| | | | | | | | | |
| application/ulpfec | Not recommended for | M | NOT | | application/ulpfec | Not recommended for | M | NOT |
| | multiplexing due to | | RECOMMENDED | | | multiplexing due to | | RECOMMENDED |
| | reuse of SSRCs | | | | | reuse of SSRCs | | |
| | | | | | | | | |
+---------------------+----------------------+-------+--------------+ +---------------------+----------------------+-------+--------------+
RFC5109 Payload Format Analysis RFC5109 Payload Format Analysis
Draft draft-lennox-payload-ulp-ssrc-mux proposes a simple fix to make
it possible to use ULP with multiplexing and ULP is allowed when used
with that.
14. Multiplexing Considerations for Encapsulating Attributes 14. Multiplexing Considerations for Encapsulating Attributes
This sections deals with recommendations for defining the This sections deals with recommendations for defining the
multiplexing characteristics of the SDP attributes that encapsulate multiplexing characteristics of the SDP attributes that encapsulate
other SDP attributes/parameters. Such attributes as of today, for other SDP attributes/parameters. Such attributes as of today, for
example, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of example, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of
a generic framework for indicating and negotiating transport, media a generic framework for indicating and negotiating transport, media
and media format related capabilities in the SDP. and media format related capabilities in the SDP.
The behavior of such attributes under multiplexing is in turn defined The behavior of such attributes under multiplexing is in turn defined
skipping to change at page 60, line 34 skipping to change at page 63, line 21
a=rtpmap:100 VP8/90000 a=rtpmap:100 VP8/90000
a=sqn: 0 a=sqn: 0
a=cdsc: 1 video RTP/AVP 100 a=cdsc: 1 video RTP/AVP 100
a=cpar: a=rtcp-mux a=cpar: a=rtcp-mux
m=video 3456 RTP/AVP 101 m=video 3456 RTP/AVP 101
a=rtpmap:101 VP8/90000 a=rtpmap:101 VP8/90000
a=fmtp:100 max-fr=15;max-fs=1200 a=fmtp:100 max-fr=15;max-fs=1200
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
cpar encapsulated rtcp-mux attribute. encapsulated rtcp-mux attribute.
14.2. RFC5939 Analysis 14.2. RFC5939 Analysis
[RFC5939] defines a general SDP capability negotiation framework. It [RFC5939] defines a general SDP capability negotiation framework. It
also specifies how to provide transport protocols and SDP attributes also specifies how to provide transport protocols and SDP attributes
as capabilities and negotiate them using the framework. as capabilities and negotiate them using the framework.
For this purpose, [RFC5939] defines the following For this purpose, [RFC5939] defines the following
o A set of capabilities for the session and its associated media o A set of capabilities for the session and its associated media
skipping to change at page 61, line 37 skipping to change at page 64, line 22
This section provides recommendations for entities generating and This section provides recommendations for entities generating and
processing SDP under the generic capability negotiation framework as processing SDP under the generic capability negotiation framework as
defined in [RFC5939] under the context of media stream multiplexing. defined in [RFC5939] under the context of media stream multiplexing.
These recommendations are provided for the purposes of enabling the These recommendations are provided for the purposes of enabling the
Offerer to make sure that the generated potential configurations Offerer to make sure that the generated potential configurations
between the multiplexed streams can (easily) be negotiated to be between the multiplexed streams can (easily) be negotiated to be
consistent between those streams. In particular, the procedures aim consistent between those streams. In particular, the procedures aim
to simplify Answerer's procedure to choose potential configurations to simplify Answerer's procedure to choose potential configurations
that are consistent across all the bundled media descriptions. that are consistent across all the multiplexed media descriptions.
A potential configuration selects a set of attributes and parameters A potential configuration selects a set of attributes and parameters
that become part of the media description when negotiated. When that become part of the media description when negotiated. When
multiplexing media descriptions with potential configurations multiplexing media descriptions with potential configurations
specified, there may be a need for coordinating this selection specified, there may be a need for coordinating this selection
between multiplexed media descriptions ensuring right multiplexing between multiplexed media descriptions ensuring right multiplexing
behavior. behavior.
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 multiplexed 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 constructing 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.
"1"). "1").
o For each potential configuration with configuration number x in m- o For each potential configuration with configuration number x in m-
bundle-pcfg, the offerer MUST ensure that if the answerer chooses bundle-pcfg, the offerer MUST ensure that if the answerer chooses
configuration number x in each of the media descriptions in m- configuration number x in each of the media descriptions in m-
bundle-pcfg, then the resulting SDP will have all multiplexing bundle-pcfg, then the resulting SDP will have all multiplexing
constraints satisfied for those media descriptions. constraints satisfied for those media descriptions.
o Since it is nearly impossible to define a generic mechanism for o Since it is nearly impossible to define a generic mechanism for
various capability extensions , this document does't provide various capability extensions, this document does't provide
procedures for dealing with the capability extension attributes. procedures for dealing with the capability extension attributes.
However, Section 14.3 provide analysis of media capability However, Section 14.3 provide analysis of media capability
extension attributes as defined in [RFC6871]. extension attributes as defined in [RFC6871].
The above allows the answerer to easily find multiplexing compatible The above allows the answerer to easily find multiplexing compatible
combinations of potential configurations:- The answerer simply choses combinations of potential configurations:- The answerer simply choses
a potential configuration (number) that is present in all of the a potential configuration (number) that is present in all of the
media descriptions with potential configurations in the bundle. media descriptions with potential configurations in the bundle.
Note that it is still possible for the offerer to provide additional Note that it is still possible for the offerer to provide additional
skipping to change at page 63, line 34 skipping to change at page 66, line 14
14.2.1.2. Example: Attribute Capability Multiplexing 14.2.1.2. Example: Attribute Capability Multiplexing
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
a=acap:1 a=rtcp-mux a=acap:1 a=rtcp-mux
a=acap:2 a=crypto:1 AES_CM_128_HMAC_SHA1_80 a=acap:2 a=crypto:1 AES_CM_128_HMAC_SHA1_80
inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32 inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32
a=group:BUNDLE audio video a=group:BUNDLE audio video
m= audio 49172 RTP/AVP 99 m= audio 49172 RTP/AVP 99
a=mid:audio a=mid:audio
a=pcfg:1 a=1 a=pcfg:1 a=1
a=pcfg:2 a=pcfg:2
m= video 560024 RTP/AVP 100 m= video 560024 RTP/AVP 100
a=mid:video a=mid:video
a=pcfg:1 a=1 a=pcfg:1 a=1
a=pcfg:2 a=2 a=pcfg:2 a=2
skipping to change at page 64, line 23 skipping to change at page 66, line 48
14.3.1. Recommendation: Dealing with Payload Type Numbers 14.3.1. Recommendation: Dealing with Payload Type Numbers
[RFC6871] defines a new payload type ("pt") parameter to be used with [RFC6871] defines a new payload type ("pt") parameter to be used with
the potential, actual and latent configuration parameters. The the potential, actual and latent configuration parameters. The
parameter associates RTP payload type numbers with the referenced parameter associates RTP payload type numbers with the referenced
RTP-based media format capabilities ("a=rmcap") defined in [RFC6871] RTP-based media format capabilities ("a=rmcap") defined in [RFC6871]
and is appropriate only when the transport protocol uses RTP. This and is appropriate only when the transport protocol uses RTP. This
means that the same payload type number can be assigned as part of means that the same payload type number can be assigned as part of
potential or actual configurations in different media descriptions in potential or actual configurations in different media descriptions in
a bundle. There are rules for the usage of identical Payload Type a bundle. There are rules for the usage of identical Payload Type
values across multiplexed m=lines as described in values across multiplexed "m=" lines as described in
[I-D.ietf-mmusic-sdp-bundle-negotiation], which MUST be followed here [I-D.ietf-mmusic-sdp-bundle-negotiation], which must be followed here
as well. As described in Section 14.2.1, the use of identical as well. As described in Section 14.2.1, the use of identical
configuration numbers for compatible configurations in different configuration numbers for compatible configurations in different
media descriptions that are part of the bundle provides a way to media descriptions that are part of the bundle provides a way to
ensure that the answerer can easily pick compatible configurations ensure that the answerer can easily pick compatible configurations
here as well. here as well.
14.3.1.1. Example: Attribute Capability Under Shared Payload Type 14.3.1.1. Example: Attribute Capability Under Shared Payload Type
The attributes (a=rmcap, a=mfcap) follow the above recommendations The attributes (a=rmcap, a=mfcap) follow the above recommendations
under mutliplexing. under multiplexing.
v=0 v=0
o=- 25678 753849 IN IP4 192.0.2.1 o=- 25678 753849 IN IP4 192.0.2.1
s= s=
c=IN IP4 192.0.2.1 c=IN IP4 192.0.2.1
t=0 0 t=0 0
a=creq:med-v0 a=creq:med-v0
m=audio 54322 RTP/AVP 96 m=audio 54322 RTP/AVP 96
a=rtpmap:96 AMR-WB/16000/1 a=rtpmap:96 AMR-WB/16000/1
a=fmtp:96 mode-change-capability=1; max-red=220; a=fmtp:96 mode-change-capability=1; max-red=220;
skipping to change at page 65, line 36 skipping to change at page 67, line 44
a=rmcap:4 audio AMR/8000/1 a=rmcap:4 audio AMR/8000/1
a=rmcap:5 audio OPUS/48000/2 a=rmcap:5 audio OPUS/48000/2
a=mfcap:5 minptime=40 a=mfcap:5 minptime=40
a=mfcap:4 mode-change-capability=1 a=mfcap:4 mode-change-capability=1
a=pcfg:1 m=4 pt=4:97 a=pcfg:1 m=4 pt=4:97
a=pcfg:4 m=5 pt=5:101 a=pcfg:4 m=5 pt=5:101
In the example above, the potential configuration number "1" is In the example above, the potential configuration number "1" is
repeated when referring to media and media format capability used for repeated when referring to media and media format capability used for
the Payload Type 97. This implies that both the media capability 2 the Payload Type 97. This implies that both the media capability 2
and 4 along with their media format capabilities MUST refer to the and 4 along with their media format capabilities must refer to the
same codec configuration , as per the definition of IDENTICAL-PER-PT. same codec configuration, as per the definition of IDENTICAL-PER-PT.
14.3.2. Recommendation: Dealing with Latent Configurations 14.3.2. Recommendation: Dealing with Latent Configurations
[RFC6871] adds the notion of a latent configurations, which provides [RFC6871] adds the notion of a latent configurations, which provides
configuration information that may be used to guide a subsequent configuration information that may be used to guide a subsequent
offer/exchange, e.g. by adding another media stream or use offer/exchange, e.g. by adding another media stream or use
alternative codec combinations not currently offered. Latent alternative codec combinations not currently offered. Latent
configurations have configuration numbers which cannot overlap with configurations have configuration numbers which cannot overlap with
the potential configuration numbers [RFC6871]. Supported the potential configuration numbers [RFC6871]. Supported
combinations of potential and latent configurations are indicated by combinations of potential and latent configurations are indicated by
use of the "a=sescap" attribute, however use of this attribute is not use of the "a=sescap" attribute, however use of this attribute is not
recommended with bundled media, since it requires the use of unique recommended with multiplexed media, since it requires the use of
configuration numbers across the SDP. Taken together, this means unique configuration numbers across the SDP. Taken together, this
there is no well-defined way to indicate supported combinations of means there is no well-defined way to indicate supported combinations
latent configurations, or combinations of latent and potential of latent configurations, or combinations of latent and potential
configurations with bundled media. It is still allowed to use the configurations with multiplexed media. It is still allowed to use
latent configuration attribute, however the limitations above will the latent configuration attribute, however the limitations above
apply. To determine valid combinations, actual negotiation will have will apply. To determine valid combinations, actual negotiation will
to be attempted subsequently instead. have 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 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
skipping to change at page 68, line 19 skipping to change at page 70, line 36
| keywds | NORMAL | | keywds | NORMAL |
| type | NORMAL | | type | NORMAL |
| type:broadcast | NORMAL | | type:broadcast | NORMAL |
| type:H332 | NORMAL | | type:H332 | NORMAL |
| type:meeting | NORMAL | | type:meeting | NORMAL |
| type:moderated | NORMAL | | type:moderated | NORMAL |
| type:test | NORMAL | | type:test | NORMAL |
| charset | NORMAL | | charset | NORMAL |
| charset:iso8895-1 | NORMAL | | charset:iso8895-1 | NORMAL |
| tool | NORMAL | | tool | NORMAL |
| ipbcp | NORMAL | | ipbcp | SPECIAL |
| group | NORMAL | | group | NORMAL |
| ice-lite | NORMAL | | ice-lite | NORMAL |
| ice-options | NORMAL | | ice-options | NORMAL |
| bcastversion | NORMAL | | bcastversion | NORMAL |
| 3GPP-Integrity-Key | NOT RECOMMENDED | | 3GPP-Integrity-Key | NOT RECOMMENDED |
| 3GPP-SDP-Auth | NOT RECOMMENDED | | 3GPP-SDP-Auth | NOT RECOMMENDED |
| alt-group | NOT RECOMMENDED | | alt-group | NOT RECOMMENDED |
| PSCid | NORMAL | | PSCid | NORMAL |
| bc_service | NORMAL | | bc_service | NORMAL |
| bc_program | NORMAL | | bc_program | NORMAL |
skipping to change at page 70, line 49 skipping to change at page 73, line 19
| 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 |
| mid | NORMAL | | mid | NORMAL |
| rtcp | IDENTICAL | | rtcp | IDENTICAL |
| rtcp-fb | IDENTICAL-PER-PT | | rtcp-fb | IDENTICAL-PER-PT |
| label | NORMAL | | label | NORMAL |
| T38VendorInfo | NORMAL | | T38VendorInfo | NORMAL |
| crypto | TRANSPORT | | crypto | TRANSPORT |
| eecid | NORMAL | | eecid | NOT RECOMMENDED |
| aalType | NORMAL | | aalType | NOT RECOMMENDED |
| capability | NORMAL | | capability | NOT RECOMMENDED |
| qosClass | NORMAL | | qosClass | NOT RECOMMENDED |
| bcob | NORMAL | | bcob | NOT RECOMMENDED |
| stc | NORMAL | | stc | NOT RECOMMENDED |
| upcc | NORMAL | | upcc | NOT RECOMMENDED |
| atmQOSparms | NORMAL | | atmQOSparms | NOT RECOMMENDED |
| atmTrfcDesc | NORMAL | | atmTrfcDesc | NOT RECOMMENDED |
| abrParms | NORMAL | | abrParms | NOT RECOMMENDED |
| abrSetup | NORMAL | | abrSetup | NOT RECOMMENDED |
| bearerType | NORMAL | | bearerType | NOT RECOMMENDED |
| lij | NORMAL | | lij | NOT RECOMMENDED |
| anycast | NORMAL | | anycast | NOT RECOMMENDED |
| cache | NORMAL | | cache | NOT RECOMMENDED |
| bearerSigIE | NORMAL | | bearerSigIE | NOT RECOMMENDED |
| aalApp | NORMAL | | aalApp | NOT RECOMMENDED |
| cbrRate | NORMAL | | cbrRate | NOT RECOMMENDED |
| sbc | NORMAL | | sbc | NOT RECOMMENDED |
| clkrec | NORMAL | | clkrec | NOT RECOMMENDED |
| fec | NORMAL | | fec | NOT RECOMMENDED |
| prtfl | NORMAL | | prtfl | NOT RECOMMENDED |
| structure | NORMAL | | structure | NOT RECOMMENDED |
| cpsSDUsize | NORMAL | | cpsSDUsize | NOT RECOMMENDED |
| all2CPS | NORMAL | | all2CPS | NOT RECOMMENDED |
| all2CPSSDUrate | NORMAL | | all2CPSSDUrate | NOT RECOMMENDED |
| aal2sscs3661unassured | NORMAL | | aal2sscs3661unassured | NOT RECOMMENDED |
| aal2sscs3661assured | NORMAL | | aal2sscs3661assured | NOT RECOMMENDED |
| aal2sscs3662 | NORMAL | | aal2sscs3662 | NOT RECOMMENDED |
| aal5sscop | NORMAL | | aal5sscop | NOT RECOMMENDED |
| atmmap | NORMAL | | atmmap | NOT RECOMMENDED |
| silenceSupp | NORMAL | | silenceSupp | NOT RECOMMENDED |
| ecan | NORMAL | | ecan | NOT RECOMMENDED |
| gc | NORMAL | | gc | NOT RECOMMENDED |
| profileDesc | NORMAL | | profileDesc | NOT RECOMMENDED |
| vsel | NORMAL | | vsel | NOT RECOMMENDED |
| dsel | NORMAL | | dsel | NOT RECOMMENDED |
| fsel | NORMAL | | fsel | NOT RECOMMENDED |
| onewaySel | NORMAL | | onewaySel | NOT RECOMMENDED |
| codecConfig | NORMAL | | codecConfig | NOT RECOMMENDED |
| isup_usi | NORMAL | | isup_usi | NOT RECOMMENDED |
| uiLayer1_Prot | NORMAL | | uiLayer1_Prot | NOT RECOMMENDED |
| chain | NORMAL | | chain | NOT RECOMMENDED |
| floorctrl | IDENTICAL | | floorctrl | IDENTICAL |
| confid | NORMAL | | confid | NORMAL |
| userid | NORMAL | | userid | NORMAL |
| floorid | NORMAL | | floorid | NORMAL |
| FEC | NORMAL | | FEC | NORMAL |
| accept-types | 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 |
skipping to change at page 78, line 35 skipping to change at page 81, line 8
| Name | Mux Category | | Name | Mux Category |
+-----------+--------------+ +-----------+--------------+
| sender | NORMAL | | sender | NORMAL |
| direct | NORMAL | | direct | NORMAL |
| IEEE1722 | NORMAL | | IEEE1722 | NORMAL |
+-----------+--------------+ +-----------+--------------+
16. Security Considerations 16. Security Considerations
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 RFCs 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, 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 Wing on suggesting structural Jonathan Lennox, Bo Burman, Ari Keranen, and Dan Wing on suggesting
changes helping improve the document readability. structural 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.24,5.32,5.33,14), Rohan reviews as listed - Flemming Andreasen(5.24,5.32,5.33,14), Rohan
Mahy(5.57), Eric Burger(5.26),Christian Huitema(5.14), Christer Mahy(5.57), Eric Burger(5.26),Christian Huitema(5.14), Christer
Holmberg(5.21,5.26,5.51,5.52), Richard Ejzak (5.44,5.53,5.54), Colin Holmberg(5.21,5.26,5.51,5.52), Richard Ejzak (5.44,5.53,5.54), Colin
Perkins(5.7,5.8,5.9,5.58), Magnus Perkins(5.7,5.8,5.9,5.58), Magnus
westerlund(5.2,5.3,5.9,5.27,5.47,6.1,6.2,6.3,8.3,7), Roni Westerlund(5.2,5.3,5.9,5.27,5.47,6.1,6.2,6.3,8.3,7), Roni
Evens(5.12,5.27,8.4), Subha Dhesikan(5.6,10), Dan Evens(5.12,5.27,8.4), Subha Dhesikan(5.6,10), Dan
Wing(5.7,5.12,5.35,5.39,5.45), Cullen Jennings (5.40), Ali C Wing(5.7,5.12,5.35,5.39,5.45), Cullen Jennings (5.40), Ali C
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 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
(7.2,7.6), Charles Eckel(5.15,5.27,5.28,9.1,8.5), Paul Kyzivat(5.24), (7.2,7.6), Charles Eckel(5.15,5.27,5.28,9.1,8.5), Paul Kyzivat(5.24),
Ian Johansson(5.15), Saravanan Shanmugham(5.11), Paul E Jones(5.30), Ian Johansson(5.15), Saravanan Shanmugham(5.11), Paul E Jones(5.30),
Rajesh Kumar(5.48), Jonathan Lennox(5.36,5,15,9.1,11.1), Mo Rajesh Kumar(5.48), Jonathan Lennox(5.36,5,15,9.1,11.1), Mo
Zanaty(5.4,5.5,5.23,8.1,8.3,8.5,12.1), Christian Huitema (5.14), Qin Zanaty(5.4,5.5,5.23,8.1,8.3,8.5,12.1), Christian Huitema (5.14), Qin
Wu (5.47 PM-Dir review), Hans Stokking(5.43,5.16). Wu (5.47 PM-Dir review), Hans Stokking(5.43,5.16), Christian Groves
(5.48,5.55)
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-05
o Incorporated review comments from Christian Grooves and Ari
Keranen.
o Fixed more nits to prep for the LastCall.
Changes from draft-ietf-mmusic-sdp-mux-attributes-04 Changes from draft-ietf-mmusic-sdp-mux-attributes-04
o Fixed minor nits overall. o Fixed minor nits overall.
o Updated Acknowledgement Sections o Updated Acknowledgement Sections
o Last Call Version. o Last Call Version.
Changes from draft-ietf-mmusic-sdp-mux-attributes-03 Changes from draft-ietf-mmusic-sdp-mux-attributes-03
skipping to change at page 82, line 9 skipping to change at page 84, line 36
[I.D-draft-ietf-dart-dscp-rtp] [I.D-draft-ietf-dart-dscp-rtp]
Black, D. and P. Jones, "The Session Description Protocol Black, D. and P. Jones, "The Session Description Protocol
(SDP) Content Attribute", draft-ietf-dart-dscp-rtp-07 (SDP) Content Attribute", draft-ietf-dart-dscp-rtp-07
(work in progress), September 2014. (work in progress), September 2014.
[IANA] "Session Description Protocol (SDP) Parameters", [IANA] "Session Description Protocol (SDP) Parameters",
<http://www.iana.org/assignments/sdp-parameters/ <http://www.iana.org/assignments/sdp-parameters/
sdp-parameters.xml>. sdp-parameters.xml>.
[ITU-T-REC.Q1970] [Q.1970] "Q.1970 : BICC IP bearer control protocol",
"Q.1970 : BICC IP bearer control protocol",
<https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>. <https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>.
[R3GPPTS183.063] [R3GPPTS183.063]
"TISPAN - IMS based ITPV Stage 3 specification.", "TISPAN - IMS based ITPV Stage 3 specification.",
<http://www.in2eps.com/etispan/ <http://www.in2eps.com/etispan/
tk-etsi-tispan03-183-063.html>. tk-etsi-tispan03-183-063.html>.
[R3GPPTS24.182] [R3GPPTS24.182]
"IP Multimedia Subsystem (IMS) Customized Alerting Tones "IP Multimedia Subsystem (IMS) Customized Alerting Tones
(CAT); Protocol specification", (CAT); Protocol specification",
skipping to change at page 82, line 39 skipping to change at page 85, line 16
"IP multimedia call control protocol based on Session "IP multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol Initiation Protocol (SIP) and Session Description Protocol
(SDP);", (SDP);",
<http://www.3gpp.org/ftp/Specs/html-info/24229.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24229.htm>.
[R3GPPTS26.114] [R3GPPTS26.114]
"IP multimedia Subsystem : Media Handling and "IP multimedia Subsystem : Media Handling and
interaction", interaction",
<http://www.in2eps.com/3g26/tk-3gpp-26-114.html>. <http://www.in2eps.com/3g26/tk-3gpp-26-114.html>.
[RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time
Streaming Protocol (RTSP)", RFC 2326, April 1998.
[RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the [RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the
Session Description Protocol (SDP) for ATM Bearer Session Description Protocol (SDP) for ATM Bearer
Connections", RFC 3108, May 2001. Connections", RFC 3108, May 2001.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, June with Session Description Protocol (SDP)", RFC 3264, June
2002. 2002.
[RFC3312] Camarillo, G., Marshall, W., and J. Rosenberg, [RFC3312] Camarillo, G., Marshall, W., and J. Rosenberg,
"Integration of Resource Management and Session Initiation "Integration of Resource Management and Session Initiation
 End of changes. 140 change blocks. 
472 lines changed or deleted 574 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/