draft-ietf-mmusic-sdp-mux-attributes-03.txt   draft-ietf-mmusic-sdp-mux-attributes-04.txt 
Network Working Group S. Nandakumar Network Working Group S. Nandakumar
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track October 20, 2014 Intended status: Standards Track October 24, 2014
Expires: April 23, 2015 Expires: April 27, 2015
A Framework for SDP Attributes when Multiplexing A Framework for SDP Attributes when Multiplexing
draft-ietf-mmusic-sdp-mux-attributes-03 draft-ietf-mmusic-sdp-mux-attributes-04
Abstract Abstract
The Session Description Protocol (SDP) provides mechanisms to The Session Description Protocol (SDP) provides mechanisms to
describe attributes of multimedia sessions and of individual media describe attributes of multimedia sessions and of individual media
streams (e.g., Real-time Transport Protocol (RTP) sessions) within a streams (e.g., Real-time Transport Protocol (RTP) sessions) within a
multimedia session. In the RTCWeb WG, there is a need to use a multimedia session. In the RTCWeb WG, there is a need to use a
single 5-tuple for sending and receiving media associated with single 5-tuple for sending and receiving media associated with
multiple media descriptions ("m=" lines). Such a requirement has multiple media descriptions ("m=" lines). Such a requirement has
raised concerns over the semantic implications of the SDP attributes raised concerns over the semantic implications of the SDP attributes
associated with the RTP Media Streams multiplexed over a single associated with the RTP Media Streams multiplexed over a single
transport layer flow. underlying transport layer flow.
The scope of this specification is to provide a framework for The scope of this specification is to provide a framework for
analyzing the multiplexing characteristics of SDP attributes. The analyzing the multiplexing characteristics of SDP attributes. This
specification also categorizes existing attributes based on the specification also categorizes the existing SDP attributes based on
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 April 23, 2015. This Internet-Draft will expire on April 27, 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 3, line 17 skipping to change at page 3, line 17
5.14. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 21 5.14. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 21
5.15. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 21 5.15. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 21
5.16. RFC7273 - RTP Clock Source Signalling . . . . . . . . . . 22 5.16. RFC7273 - RTP Clock Source Signalling . . . . . . . . . . 22
5.17. RFC6236 - Image Attributes in SDP . . . . . . . . . . . . 23 5.17. RFC6236 - Image Attributes in SDP . . . . . . . . . . . . 23
5.18. RFC7197 - Duplication Delay Attribute in SDP . . . . . . 23 5.18. RFC7197 - Duplication Delay Attribute in SDP . . . . . . 23
5.19. RFC7226 - RTCP XR Blocks for MOS Metric Reporting . . . 23 5.19. RFC7226 - RTCP XR Blocks for MOS Metric Reporting . . . 23
5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions . . 24 5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions . . 24
5.21. RFC6230 - Media Control Channel Framework . . . . . . . . 24 5.21. RFC6230 - Media Control Channel Framework . . . . . . . . 24
5.22. RFC6364 - SDP Elements for FEC Framework . . . . . . . . 25 5.22. RFC6364 - SDP Elements for FEC Framework . . . . . . . . 25
5.23. RFC4796 - Content Attribute . . . . . . . . . . . . . . . 25 5.23. RFC4796 - Content Attribute . . . . . . . . . . . . . . . 25
5.24. RFC3407 - SDP Simple Capability Declaration . . . . . . . 25 5.24. RFC3407 - SDP Simple Capability Declaration . . . . . . . 26
5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP 5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP
Sessions . . . . . . . . . . . . . . . . . . . . . . . . 26 Sessions . . . . . . . . . . . . . . . . . . . . . . . . 26
5.26. RFC6714 - MSRP-CEMA . . . . . . . . . . . . . . . . . . . 26 5.26. RFC6714 - MSRP-CEMA . . . . . . . . . . . . . . . . . . . 27
5.27. RFC4583 - SDP Format for BFCP Streams . . . . . . . . . . 27 5.27. RFC4583 - SDP Format for BFCP Streams . . . . . . . . . . 27
5.28. RFC5547 - SDP Offer/Answer for File Transfer . . . . . . 27 5.28. RFC5547 - SDP Offer/Answer for File Transfer . . . . . . 28
5.29. RFC6489 - SDP and RTP Media Loopback Extension . . . . . 28 5.29. RFC6849 - SDP and RTP Media Loopback Extension . . . . . 28
5.30. RFC5760 - RTCP with Unicast Feedback . . . . . . . . . . 28 5.30. RFC5760 - RTCP with Unicast Feedback . . . . . . . . . . 29
5.31. RFC3611 - RTCP XR . . . . . . . . . . . . . . . . . . . . 29 5.31. RFC3611 - RTCP XR . . . . . . . . . . . . . . . . . . . . 29
5.32. RFC5939 - SDP Capability Negotiation . . . . . . . . . . 29 5.32. RFC5939 - SDP Capability Negotiation . . . . . . . . . . 29
5.33. RFC6871- SDP Media Capabilities Negotiation . . . . . . . 30 5.33. RFC6871- SDP Media Capabilities Negotiation . . . . . . . 30
5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP . . 31 5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP . . 31
5.35. RFC4567 - Key Management Extensions for SDP and RTSP . . 32 5.35. RFC4567 - Key Management Extensions for SDP and RTSP . . 32
5.36. RFC4572 - Comedia over TLS in SDP . . . . . . . . . . . . 33 5.36. RFC4572 - Comedia over TLS in SDP . . . . . . . . . . . . 33
5.37. RFC4570 - SDP Source Filters . . . . . . . . . . . . . . 33 5.37. RFC4570 - SDP Source Filters . . . . . . . . . . . . . . 33
5.38. RFC6128 - RTCP Port for Multicast Sessions . . . . . . . 34 5.38. RFC6128 - RTCP Port for Multicast Sessions . . . . . . . 34
5.39. RFC6189 - ZRTP . . . . . . . . . . . . . . . . . . . . . 34 5.39. RFC6189 - ZRTP . . . . . . . . . . . . . . . . . . . . . 34
5.40. RFC4145 - Connection-Oriented Media . . . . . . . . . . . 35 5.40. RFC4145 - Connection-Oriented Media . . . . . . . . . . . 35
5.41. RFC6947 - The SDP ALTC Attribute . . . . . . . . . . . . 35 5.41. RFC6947 - The SDP ALTC Attribute . . . . . . . . . . . . 35
5.42. RFC7195 - SDP Extension for Circuit Switched Bearers 5.42. RFC7195 - SDP Extension for Circuit Switched Bearers
in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 36 in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP) . . 36 5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP) . . 36
5.44. RFC5159 - OMA BCAST SDP Attributes . . . . . . . . . . . 37 5.44. RFC5159 - OMA BCAST SDP Attributes . . . . . . . . . . . 37
5.45. RFC6193 - Media Description for IKE in SDP . . . . . . . 37 5.45. RFC6193 - Media Description for IKE in SDP . . . . . . . 37
5.46. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 38 5.46. RFC2326 - Real Time Streaming Protocol . . . . . . . . . 38
5.47. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 41 5.47. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 39
5.48. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 42 5.48. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 42
5.49. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 43 5.49. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 43
5.50. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 43 5.50. 3GPP TS 183.063 . . . . . . . . . . . . . . . . . . . . . 44
5.51. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 43 5.51. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 44
5.52. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 44 5.52. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 44
5.53. ITU-T-REC.Q1970 . . . . . . . . . . . . . . . . . . . . . 45 5.53. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 45
5.54. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 46 5.54. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 46
5.55. RFC4975 - The Message Session Relay Protocol . . . . . . 46 5.55. ITU-T-REC.Q1970 . . . . . . . . . . . . . . . . . . . . . 46
5.56. Historical . . . . . . . . . . . . . . . . . . . . . . . 47 5.56. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 47
5.57. RFC4975 - The Message Session Relay Protocol . . . . . . 47
6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 48 5.58. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 48
6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 48 5.59. Historical Attributes . . . . . . . . . . . . . . . . . . 48
6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 48 6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 49
6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 49 6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 49
7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 50 6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 49
7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 50 6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 50
7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 51 7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 51
7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 52 7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 51
7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 52 7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 52
7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 53 7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 53
7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 54 7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 53
8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 54 7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 54
8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 54 7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 55
8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 55
8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 55
8.2. RFC3524 - Mapping Media Streams to Resource 8.2. RFC3524 - Mapping Media Streams to Resource
Reservation Flows . . . . . . . . . . . . . . . . . . . . 55 Reservation Flows . . . . . . . . . . . . . . . . . . . . 56
8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 55 8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 56
8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 55 8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 56
8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 56 8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 57
8.6. RFC7104 - Duplication Grouping Semantics in the SDP . . 56 8.6. RFC7104 - Duplication Grouping Semantics in the SDP . . 57
9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 57 9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 58
9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 57 9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 58
9.2. RFC7104 - Duplication Grouping Semantics in the SDP . . . 57 9.2. RFC7104 - Duplication Grouping Semantics in the SDP . . . 58
10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 57 10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 58
10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 57 10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 58
11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 58 11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 59
11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 58 11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 59
12. content Atribute Analysis . . . . . . . . . . . . . . . . . . 58 12. content Attribute Analysis . . . . . . . . . . . . . . . . . 59
12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 58 12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 59
13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 59 13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 60
13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 59 13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 60
14. Multiplexing Considerations for Encapsulating 14. Multiplexing Considerations for Encapsulating Attributes . . 60
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 59 14.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 61
14.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 60 14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 61
14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 60
14.2.1. Recommendation - Procedures for Potential 14.2.1. Recommendation - Procedures for Potential
Configuration Pairing . . . . . . . . . . . . . . . 61 Configuration Pairing . . . . . . . . . . . . . . . 62
14.2.1.1. Example: Transport Capability Multiplexing . . . 62 14.2.1.1. Example: Transport Capability Multiplexing . . . 63
14.2.1.2. Example: Attribute Capability Multiplexing . . . 63 14.2.1.2. Example: Attribute Capability Multiplexing . . . 64
14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 64 14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 65
14.3.1. Recommendation: Dealing with Payload Type Numbers . 64 14.3.1. Recommendation: Dealing with Payload Type Numbers . 65
14.3.1.1. Example: Attribute Capability Under Shared 14.3.1.1. Example: Attribute Capability Under Shared
Payload Type . . . . . . . . . . . . . . . . . . 64 Payload Type . . . . . . . . . . . . . . . . . . 65
14.3.2. Recommendation: Dealing with Latent Configurations . 65 14.3.2. Recommendation: Dealing with Latent Configurations . 66
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67
15.1. New Column 'Mux Category' . . . . . . . . . . . . . . . 66 15.1. New 'Multiplexing Categories' subregistry . . . . . . . 67
15.2. 'Mux Category' values for SDP Registries . . . . . . . . 67 15.2. 'Mux Category' column for subregistries . . . . . . . . 68
15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 67 15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 68
15.2.2. Table: att-field . . . . . . . . . . . . . . . . . . 68 15.2.2. Table: att-field (session level) . . . . . . . . . . 68
15.2.3. Table: content SDP Parameters . . . . . . . . . . . 73 15.2.3. Table: att-field (both session and media level) . . 69
15.2.4. Table: Semantics for the 'group' SDP Attribute . . . 73 15.2.4. Table: att-field (media level only) . . . . . . . . 71
15.2.5. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 74 15.2.5. Table: att-field (source level) . . . . . . . . . . 74
15.2.6. Table: 'ack' and 'nack' Attribute Values . . . . . . 74 15.2.6. Table: content SDP Parameters . . . . . . . . . . . 74
15.2.7. Table: 'depend' SDP Attribute Values . . . . . . . . 75 15.2.7. Table: Semantics for the 'group' SDP Attribute . . . 75
15.2.8. Table: 'cs-correlation' Attribute Values . . . . . . 75 15.2.8. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 75
15.2.9. Table: Semantics for the 'ssrc-group' SDP Attribute 75 15.2.9. Table: 'ack' and 'nack' Attribute Values . . . . . . 76
15.2.10. Table: SDP/RTSP key management protocol identifiers 76 15.2.10. Table: 'depend' SDP Attribute Values . . . . . . . . 76
15.2.11. Table: Codec Control Messages . . . . . . . . . . . 76 15.2.11. Table: 'cs-correlation' Attribute Values . . . . . . 76
15.2.12. Table: QoS Mechanism Tokens . . . . . . . . . . . . 76 15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute 77
15.2.13. Table: SDP Capability Negotiation Option Tags . . . 77 15.2.13. Table: SDP/RTSP key management protocol identifiers 77
15.2.14. Table: Timestamp Reference Clock Source Parameters . 77 15.2.14. Table: Codec Control Messages . . . . . . . . . . . 77
15.2.15. Table: Media Clock Source Parameters . . . . . . . . 77 15.2.15. Table: QoS Mechanism Tokens . . . . . . . . . . . . 78
16. Security Considerations . . . . . . . . . . . . . . . . . . . 78 15.2.16. Table: SDP Capability Negotiation Option Tags . . . 78
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 78 15.2.17. Table: Timestamp Reference Clock Source Parameters . 78
18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 78 15.2.18. Table: Media Clock Source Parameters . . . . . . . . 79
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 80 16. Security Considerations . . . . . . . . . . . . . . . . . . . 79
19.1. Normative References . . . . . . . . . . . . . . . . . . 80 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 79
19.2. Informative References . . . . . . . . . . . . . . . . . 81 18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 80
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 87 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 82
19.1. Normative References . . . . . . . . . . . . . . . . . . 82
19.2. Informative References . . . . . . . . . . . . . . . . . 82
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 88
1. Introduction 1. Introduction
Real-Time Communication Web (RTCWeb) framework requires Real-time Real-Time Communication Web (RTCWeb) framework requires Real-time
Transport Protocol (RTP) as the media transport protocol and Session Transport Protocol (RTP) as the media transport protocol and Session
Description Protocol (SDP) [RFC4566] for describing and negotiating Description Protocol (SDP) [RFC4566] for describing and negotiating
multi-media communication sessions. multi-media communication sessions.
SDP defines several attributes for capturing characteristics that SDP defines several attributes for capturing characteristics that
apply to the individual media descriptions (described by "m=" lines") apply to the individual media descriptions (described by "m=" lines")
and the overall multimedia session. Typically different media types and the overall multimedia session. Typically different media types
(audio, video etc) described using different media descriptions (audio, video etc) described using different media descriptions
represent separate RTP Sessions that are carried over individual represent separate RTP Sessions that are carried over individual
transport layer flows. However in the IETF RTCWEB WG, a need to use transport layer flows. However in the IETF RTCWEB WG, a need to use
a single 5-tuple for sending and receiving media associated with a single 5-tuple for sending and receiving media associated with
multiple SDP media descriptions ("m=" lines) has been identified. multiple SDP media descriptions ("m=" lines) has been identified.
This would e.g. allow the usage of a single set of Interactive This would for e.g. allow the usage of a single set of Interactive
Connectivity Establishment (ICE) [RFC5245] candidates for multiple Connectivity Establishment (ICE) [RFC5245] candidates for multiple
media descriptions. This in turn has made necessary to understand media descriptions. This in turn has made necessary to understand
the interpretation and usage of the SDP attributes defined for the the interpretation and usage of the SDP attributes defined for the
multiplexed media descriptions. multiplexed media descriptions.
Given the number of SDP attributes registered with the IANA [IANA] Given the number of SDP attributes registered with the [IANA] and
and possibility of new attributes being defined in the future, there possibility of new attributes being defined in the future, there is
is need for generic future-proof framework to analyze these need for generic future-proof framework to analyze these attributes
attributes for their applicability in the transport multiplexing use- for their applicability in the transport multiplexing use-cases.
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 IANA applies the framework to the SDP attributes registered with the
[IANA] [IANA].
2. Terminology 2. Terminology
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. these SDP attributes as they are defined today.
The specific problem is that there are attribute combinations which The specific problem is that there are attribute combinations which
make sense when specified on independent m-lines -- as with classical make sense when specified on independent "m= "lines -- as with
SDP -- that do not make sense when those m-lines are then multiplexed classical SDP -- that do not make sense when those "m="" lines are
over the same transport. To give an obvious example, ICE permits then multiplexed over the same transport. To give an obvious
each m=line to have an independently specified ice-ufrag attribute. example, ICE permits each "m=" line to have an independently
However, if the media from multiple m-lines is multiplexed over the specified ice-ufrag attribute. However, if the media from multiple
same ICE component, then the meaning of media-level ice-ufrag "m=" lines is multiplexed over the same ICE component, then the
attributes becomes muddled. meaning of media-level ice-ufrag attributes becomes muddled.
As of today there are close to 250 SDP attributes registered with the As of today there are close to 250 SDP attributes registered with the
IANA [IANA] and more will be added in the future. There is no [IANA] and more will be added in the future. There is no clearly
clearly defined procedure to establish the validity/applicability of defined procedure to establish the validity/applicability of these
these attribute when used with transport multiplexing. attribute when used with transport multiplexing.
4. SDP Attribute Analysis Framework 4. SDP Attribute Analysis Framework
Attributes in an SDP session description can be defined at the Attributes in an SDP session description can be defined at the
session-level and media-level. These attributes could be session-level and media-level. These attributes could be
semantically grouped as noted below. semantically grouped as noted below.
o Attributes related to media content such as media type, encoding o Attributes related to media content such as media type, encoding
schemes, payload types. schemes, payload types.
o Attributes specifying media transport characteristics like RTP/ o Attributes specifying media transport characteristics like RTP/
RTCP port numbers, network addresses, QOS. RTCP port numbers, network addresses, QOS.
o Metadata description attributes capturing session timing and o Metadata description attributes capturing session timing and
origin information. origin information.
o Attributes establishing relationships between media streams such o Attributes establishing relationships between media streams such
as grouping framework as grouping framework
With the above semantic grouping as the 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
skipping to change at page 8, line 43 skipping to change at page 8, line 45
t=0 0 t=0 0
m=audio 34567 RTP/AVP 97 m=audio 34567 RTP/AVP 97
a=rtcp-mux a=rtcp-mux
m=video 34567 RTP/AVP 31 m=video 34567 RTP/AVP 31
a=rtpmap:31 H261/90000 a=rtpmap:31 H261/90000
a=rtcp-mux a=rtcp-mux
4.4. Category: SUM 4.4. Category: SUM
Attributes can be set as they are normally used but software using Attributes can be set as they are normally used but software using
them in a multiplex case, MUST apply the sum of all the attributes them in the multiplexing scenario, MUST apply the sum of all the
being multiplexed instead of trying to use each one. This is attributes being multiplexed instead of trying to use them
typically used for bandwidth or other rate limiting attributes to the independently. This is typically used for bandwidth or other rate
underlining transport. limiting attributes to the underlying transport.
The software parsing the SDP sample below, should use the aggregate The software parsing the SDP sample below, should use the aggregate
Application Specific (AS) bandwidth value from the individual media Application Specific (AS) bandwidth value from the individual media
descriptions to determine the AS value for the multiplexed session. descriptions to determine the AS value for the multiplexed session.
Thus the calculated AS value would be 256+64 bytes for the given Thus the calculated AS value would be 256+64 bytes for the given
example. example.
v=0 v=0
o=test 2890844526 2890842807 IN IP4 126.16.64.4 o=test 2890844526 2890842807 IN IP4 126.16.64.4
c=IN IP4 client.biloxi.example.com c=IN IP4 client.biloxi.example.com
skipping to change at page 10, line 18 skipping to change at page 10, line 18
These attributes inherit their multiplexing characteristics from the These attributes inherit their multiplexing characteristics from the
attributes or parameters they encapsulate. Such attributes as of attributes or parameters they encapsulate. Such attributes as of
today, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of a today, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of a
generic framework for indicating and negotiating transport, media and generic framework for indicating and negotiating transport, media and
media format related capabilities in the SDP. media format related capabilities in the SDP.
The inheritance manifests itself when the encapsulated attribute or The inheritance manifests itself when the encapsulated attribute or
parameter is being leveraged. In the case of SDP Capability parameter is being leveraged. In the case of SDP Capability
Negotiation [RFC5939] for example, this occurs when a capability Negotiation [RFC5939] for example, this occurs when a capability
(encapsulating attribute) is used as part of a configuration; the (encapsulating attribute) is used as part of a configuration; the
configuration inherits the multiplexing Category of each of its configuration inherits the multiplexing category of each of its
constituent (encapsulated) attributes and parameters. This in turn constituent (encapsulated) attributes and parameters. This in turn
may place constraints on what constitutes a valid configuartion from may place constraints on what constitutes a valid configuration from
a multiplexing point of view, e.g. because some attributes must be a multiplexing point of view, e.g. because some attributes must be
IDENTICAL (see Section 15 for further details). IDENTICAL (see Section 14 for further details).
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=video 3456 RTP/AVP 100 m=video 3456 RTP/AVP 100
a=rtpmap:100 VP8/90000 a=rtpmap:100 VP8/90000
a=fmtp:100 max-fr=30;max-fs=8040 a=fmtp:100 max-fr=30;max-fs=8040
a=sqn: 0 a=sqn: 0
skipping to change at page 11, line 40 skipping to change at page 11, line 40
Attributes where the text in the source draft must be consulted for Attributes where the text in the source draft must be consulted for
further handling when multiplexed. 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. multiplexing framework yet. For the purposes of implementations it
is advised to consider "NOT RECOMMENDED" as the category when
multiplexing these attributes.
5. Analysis of Existing Attributes 5. Analysis of Existing Attributes
This section analyzes attributes listed in IANA [IANA] grouped under This section analyzes attributes listed in [IANA] grouped under the
the IETF document that defines them. The "Level" column indicates IETF document that defines them. The "Level" column indicates
whether the attribute is currently specified as: whether the attribute is currently specified as:
o S -- Session level o S -- Session level
o M -- Media level o M -- Media level
o B -- Both o B -- Both
o SR -- Source-level (for a single SSRC) o SR -- Source-level (for a single SSRC)
5.1. RFC4566 - SDP: Session Description Protocol 5.1. RFC4566 - SDP: Session Description Protocol
[RFC4566] defines the Session Description Protocol (SDP) that is [RFC4566] defines the Session Description Protocol (SDP) that is
intended for describing multimedia sessions for the purposes of intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of session announcement, session invitation, and other forms of
multimedia session initiation multimedia session initiation.
+-----------------+---------------------+-------+-------------------+ +-----------------+---------------------+-------+-------------------+
| Attr Name | Notes | Level | Category | | Attr Name | Notes | Level | Category |
+-----------------+---------------------+-------+-------------------+ +-----------------+---------------------+-------+-------------------+
| sendrecv | Not impacted | B | NORMAL | | sendrecv | Not impacted | B | NORMAL |
| | | | | | | | | |
| sendonly | Not impacted | B | NORMAL | | sendonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| recvonly | Not impacted | B | NORMAL | | recvonly | Not impacted | B | NORMAL |
| | | | | | | | | |
skipping to change at page 15, line 5 skipping to change at page 15, line 5
5.4. RFC3312 - Integration of Resource Management and (SIP) 5.4. RFC3312 - Integration of Resource Management and (SIP)
[RFC3312] defines a generic framework for preconditions, which are [RFC3312] defines a generic framework for preconditions, which are
extensible through IANA registration. This document also discusses extensible through IANA registration. This document also discusses
how network quality of service can be made a precondition for how network quality of service can be made a precondition for
establishment of sessions initiated by the Session Initiation establishment of sessions initiated by the Session Initiation
Protocol (SIP). These preconditions require that the participant Protocol (SIP). These preconditions require that the participant
reserve network resources before continuing with the session. reserve network resources before continuing with the session.
+-------+-----------------------+-------+-----------------+ +-------+-----------------------+-------+------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------+-----------------------+-------+-----------------+ +-------+-----------------------+-------+------------------+
| des | Refer to notes below | M | NOT RECOMMEDED | | des | Refer to notes below | M | NOT RECOMMENDED |
| | | | | | | | | |
| conf | Refer to notes below | M | NOT RECOMMEDED | | conf | Refer to notes below | M | NOT RECOMMENDED |
| | | | | | | | | |
| curr | Refer to notes below | M | NOT RECOMMEDED | | curr | Refer to notes below | M | NOT RECOMMENDED |
| | | | | | | | | |
+-------+-----------------------+-------+-----------------+ +-------+-----------------------+-------+------------------+
RFC3312 Attribute Analysis RFC3312 Attribute Analysis
A mismatched set of Preconditions across media descriptions results A mismatched set of Preconditions across media descriptions results
in Session establishment failures due to inability to meet the right in Session establishment failures due to inability to meet the right
resource reservations requested. resource reservations requested.
5.5. RFC4574 - SDP Label Attribute 5.5. RFC4574 - SDP Label Attribute
[RFC4574] defines a new Session Description Protocol (SDP) media- [RFC4574] defines a new Session Description Protocol (SDP) media-
skipping to change at page 16, line 5 skipping to change at page 16, line 5
| | | | | | | | | |
+--------+---------------+-------+----------+ +--------+---------------+-------+----------+
RFC4574 Attribute Analysis RFC4574 Attribute Analysis
5.6. RFC5432 - QoS Mechanism Selection in SDP 5.6. RFC5432 - QoS Mechanism Selection in SDP
[RFC5432] defines procedures to negotiate QOS mechanisms using the [RFC5432] defines procedures to negotiate QOS mechanisms using the
Session Description Protocol (SDP) offer/answer model. Session Description Protocol (SDP) offer/answer model.
+----------------+-------------------------------+-------+----------+ +----------------+------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+----------------+-------------------------------+-------+----------+ +----------------+------------------------+-------+----------+
| qos-mech-send | A single DSCP code point per | B | NORMAL | | qos-mech-send | Refer to notes below | B | NORMAL |
| | flow being multiplexed | | | | | | | |
| | doesn't impact multiplexing | | | | qos-mech-recv | Refer to notes below. | B | NORMAL |
| | since QOS mechanisms are | | | | | | | |
| | signaled/scoped per flow. | | | +----------------+------------------------+-------+----------+
| | | | |
| qos-mech-recv | A single DSCP code point per | B | NORMAL |
| | flow being multiplexed | | |
| | doesn't impact multiplexing | | |
| | since QOS mechanisms are | | |
| | signaled/scoped per flow. | | |
| | | | |
+----------------+-------------------------------+-------+----------+
RFC5432 Attribute Analysis RFC5432 Attribute Analysis
For scenarios that involves having different DSCP for packets being A single DSCP code point per flow being multiplexed doesn't impact
transmitted over the same 5-tuple, i.e. what is being in the same multiplexing since QOS mechanisms are signaled/scoped per flow.For
bundle, has issues as discussed in [I.D-draft-ietf-dart-dscp-rtp] scenarios that involves having different DSCP for packets being
transmitted over the same 5-tuple, has issues as discussed in
[I.D-draft-ietf-dart-dscp-rtp]
5.7. RFC4568 - SDP Security Descriptions 5.7. RFC4568 - SDP Security Descriptions
[RFC4568] defines a Session Description Protocol (SDP) cryptographic [RFC4568] defines a Session Description Protocol (SDP) cryptographic
attribute for unicast media streams. The attribute describes a attribute for unicast media streams. The attribute describes a
cryptographic key and other parameters that serve to configure cryptographic key and other parameters that serve to configure
security for a unicast media stream in either a single message or a security for a unicast media stream in either a single message or a
roundtrip exchange. roundtrip exchange.
+---------+------------------------------------+-------+------------+ +---------+------------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------+------------------------------------+-------+------------+ +---------+------------------------------------+-------+------------+
| crypto | crypto attribute must be the one | M | TRANSPORT | | crypto | crypto attribute must be the one | M | TRANSPORT |
| | that corresponds to the m=line | | | | | that corresponds to the "m=" line | | |
| | chosen for setting up the | | | | | chosen for setting up the | | |
| | underlying transport flow | | | | | underlying transport flow | | |
| | | | | | | | | |
+---------+------------------------------------+-------+------------+ +---------+------------------------------------+-------+------------+
RFC4568 Attribute Analysis RFC4568 Attribute Analysis
5.8. RFC5762 - RTP over DCCP 5.8. RFC5762 - RTP over DCCP
The Real-time Transport Protocol (RTP) is a widely used transport for The Real-time Transport Protocol (RTP) is a widely used transport for
real-time multimedia on IP networks. The Datagram Congestion Control real-time multimedia on IP networks. The Datagram Congestion Control
Protocol (DCCP) is a transport protocol that provides desirable Protocol (DCCP) is a transport protocol that provides desirable
services for real-time applications. [RFC5762] specifies a mapping services for real-time applications. [RFC5762] specifies a mapping
of RTP onto DCCP, along with associated signaling, such that real- of RTP onto DCCP, along with associated signaling, such that real-
time applications can make use of the services provided by DCCP time applications can make use of the services provided by DCCP.
+--------------------+---------------------+---------+--------------+ +--------------------+---------------------+---------+--------------+
| Name | Notes | Current | Category | | Name | Notes | Current | 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 a | | | | | in the "m=" line is | | |
| | DCCP port. DCCP | | | | | a DCCP port. DCCP | | |
| | being a connection | | | | | being a connection | | |
| | oriented protocol, | | | | | oriented protocol, | | |
| | does not allow | | | | | 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 | Category | | Name | Notes | Level | 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 tunnelling DCCP in UDP, with the UDP port Since RFC6773 is about tunneling DCCP in UDP, with the UDP port being
being the port of the DCCP en-/de-capsulation service. This the port of the DCCP en-/de-capsulation service. This encapsulation
encapsulation allows arbitrary DCCP packets to be encapsulated and allows arbitrary DCCP packets to be encapsulated and the DCCP port
the DCCP port choosen MAY conflict with the port chosen for the RTP chosen MAY conflict with the port chosen for the RTP traffic.
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 choses thus rendering it to
be very application dependant. be very application dependent.
5.10. RFC5506 - Reduced-Size RTCP in RTP Profile 5.10. RFC5506 - Reduced-Size RTCP in RTP Profile
[RFC5506] discusses benefits and issues that arise when allowing [RFC5506] discusses benefits and issues that arise when allowing
Real-time Transport Protocol (RTCP) packets to be transmitted with Real-time Transport Protocol (RTCP) packets to be transmitted with
reduced size. reduced size.
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
skipping to change at page 19, line 21 skipping to change at page 19, line 12
speech resource server. [RFC6787] defines attributes for this speech resource server. [RFC6787] defines attributes for this
purpose. purpose.
+-----------+---------------+-------+----------+ +-----------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-----------+---------------+-------+----------+ +-----------+---------------+-------+----------+
| resource | Not Impacted | M | NORMAL | | resource | Not Impacted | M | NORMAL |
| | | | | | | | | |
| channel | Not Impacted | M | NORMAL | | channel | Not Impacted | M | NORMAL |
| | | | | | | | | |
| cmid | Not Impacted | M | NORMAL |
| | | | |
+-----------+---------------+-------+----------+ +-----------+---------------+-------+----------+
RFC6787 Attribute Analysis RFC6787 Attribute Analysis
5.12. RFC5245 - Interactive Connectivity Establishment (ICE) 5.12. RFC5245 - Interactive Connectivity Establishment (ICE)
[RFC5245] describes a protocol for Network Address Translator(NAT) [RFC5245] describes a protocol for Network Address Translator(NAT)
traversal for UDP-based multimedia sessions established with the traversal for UDP-based multimedia sessions established with the
offer/answer model. This protocol is called Interactive Connectivity offer/answer model. This protocol is called Interactive Connectivity
Establishment (ICE). ICE makes use of the Session Traversal Establishment (ICE). ICE makes use of the Session Traversal
skipping to change at page 22, line 10 skipping to change at page 22, line 10
are identified by their synchronization source (SSRC) identifiers, in are identified by their synchronization source (SSRC) identifiers, in
SDP, to associate attributes with these sources, and to express SDP, to associate attributes with these sources, and to express
relationships among sources. It also defines several source-level relationships among sources. It also defines several source-level
attributes that can be used to describe properties of media sources. attributes that can be used to describe properties of media sources.
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
| ssrc | Refer to Notes below | M | NORMAL | | ssrc | Refer to Notes below | M | NORMAL |
| | | | | | | | | |
| ssrc-group | Refer to section | M | SPECIAL | | ssrc-group | Refer to section | M | NORMAL |
| | Section 9 for | | | | | Section 9 for | | |
| | specific analysis of | | | | | specific analysis of | | |
| | the grouping | | | | | the grouping | | |
| | semantics | | | | | semantics | | |
| | | | | | | | | |
| cname | Not Impacted [Open | SR | NORMAL | | cname | Not Impacted | SR | NORMAL |
| | Issues: what are the | | |
| | rules for CNAME | | |
| | duplication across | | |
| | sessions?] | | |
| | | | | | | | | |
| previous-ssrc | Refer to notes below | SR | NORMAL | | previous-ssrc | Refer to notes below | SR | NORMAL |
| | | | | | | | | |
| 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 | | |
| | | | | | | | | |
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
skipping to change at page 22, line 42 skipping to change at page 22, line 38
If SSRCs are repeated across m=lines being multiplexed, they MUST all If SSRCs are repeated across m=lines being multiplexed, they MUST all
represent the same underlying RTP Source. represent the same underlying RTP Source.
5.16. RFC7273 - RTP Clock Source Signalling 5.16. RFC7273 - RTP Clock Source Signalling
[RFC7273] specifies Session Description Protocol (SDP) signalling [RFC7273] specifies Session Description Protocol (SDP) signalling
that identifies timestamp reference clock sources and SDP signalling that identifies timestamp reference clock sources and SDP signalling
that identifies the media clock sources in a multimedia session. that identifies the media clock sources in a multimedia session.
+------------+---------------+-----------+----------+ +------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------+---------------+-----------+----------+ +------------+---------------+-------+----------+
| ts-refclk | Not Impacted | S, M, SR | NORMAL | | ts-refclk | Not Impacted | B | NORMAL |
| | | | | | | | | |
| mediaclk | Not Impacted | S,, M, SR | NORMAL | | mediaclk | Not Impacted | B | NORMAL |
| | | | | | | | | |
+------------+---------------+-----------+----------+ +------------+---------------+-------+----------+
RFC7273 Attribute Analysis RFC7273 Attribute Analysis
5.17. RFC6236 - Image Attributes in SDP 5.17. RFC6236 - Image Attributes in SDP
[RFC6236] proposes a new generic session setup attribute to make it [RFC6236] proposes a new generic session setup attribute to make it
possible to negotiate different image attributes such as image size. possible to negotiate different image attributes such as image size.
A possible use case is to make it possible for a low-end hand-held A possible use case is to make it possible for a low-end hand-held
terminal to display video without the need to rescale the terminal to display video without the need to rescale the
image,something that may consume large amounts of memory and image,something that may consume large amounts of memory and
skipping to change at page 23, line 31 skipping to change at page 23, line 31
| | codec configuration | | | | | codec configuration | | |
| | | | | | | | | |
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
RFC6236 Attribute Analysis RFC6236 Attribute Analysis
5.18. RFC7197 - Duplication Delay Attribute in SDP 5.18. RFC7197 - Duplication Delay Attribute in SDP
[RFC7197] defines an attribute to indicate the presence of temporally [RFC7197] defines an attribute to indicate the presence of temporally
redundant media streams and the duplication delay in the Session redundant media streams and the duplication delay in the Session
Description Protocol Description Protocol.
+--------------------+---------------+-------+----------+ +--------------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+--------------------+---------------+-------+----------+ +--------------------+---------------+-------+----------+
| duplication-delay | Not Impacted | B | NORMAL | | duplication-delay | Not Impacted | B | NORMAL |
| | | | | | | | | |
+--------------------+---------------+-------+----------+ +--------------------+---------------+-------+----------+
RFC7197 Attribute Analysis RFC7197 Attribute Analysis
skipping to change at page 25, line 15 skipping to change at page 25, line 15
5.22. RFC6364 - SDP Elements for FEC Framework 5.22. RFC6364 - SDP Elements for FEC Framework
[RFC6364] specifies the use of the Session Description Protocol (SDP) [RFC6364] specifies the use of the Session Description Protocol (SDP)
to describe the parameters required to signal the Forward Error to describe the parameters required to signal the Forward Error
Correction (FEC) Framework Configuration Information between the Correction (FEC) Framework Configuration Information between the
sender(s) and receiver(s). This document also provides examples that sender(s) and receiver(s). This document also provides examples that
show the semantics for grouping multiple source and repair flows show the semantics for grouping multiple source and repair flows
together for the applications that simultaneously use multiple together for the applications that simultaneously use multiple
instances of the FEC Framework. instances of the FEC Framework.
+------------------+-------+-------+----------+ +------------------+-----------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------------+-------+-------+----------+ +------------------+-----------------------------+-------+----------+
| fec-source-flow | | M | SPECIAL | | fec-source-flow | Specific FEC scheme | M | SPECIAL |
| | | | | | | document needs to be | | |
| fec-repair-flow | | M | SPECIAL | | | referred | | |
| | | | | | | | | |
| repair-window | | M | SPECIAL | | fec-repair-flow | Specific FEC scheme | M | SPECIAL |
| | | | | | | document needs to be | | |
+------------------+-------+-------+----------+ | | referred | | |
| | | | |
| repair-window | Specific FEC scheme | M | SPECIAL |
| | document needs to be | | |
| | referred | | |
| | | | |
+------------------+-----------------------------+-------+----------+
RFC6364 Attribute Analysis RFC6364 Attribute Analysis
5.23. RFC4796 - Content Attribute 5.23. RFC4796 - Content Attribute
[RFC4796] defines a new Session Description Protocol (SDP) media- [RFC4796] defines a new Session Description Protocol (SDP) media-
level attribute, 'content'. The 'content' attribute defines the level attribute, 'content'. The 'content' attribute defines the
content of the media stream to a more detailed level than the media content of the media stream to a more detailed level than the media
description line. The sender of an SDP session description can description line. The sender of an SDP session description can
attach the 'content' attribute to one or more media streams. The attach the 'content' attribute to one or more media streams. The
skipping to change at page 26, line 25 skipping to change at page 26, line 31
| | | | | | | | | |
| cparmax | Refer to notes below | B | SPECIAL | | cparmax | Refer to notes below | B | SPECIAL |
| | | | | | | | | |
+----------+------------------------+-------+----------+ +----------+------------------------+-------+----------+
RFC3407 Attribute Analysis RFC3407 Attribute Analysis
Since the attributes (a=cparmin and a=cparmax) define minimum and Since the attributes (a=cparmin and a=cparmax) define minimum and
maximum numerical values associated with the attributes described in maximum numerical values associated with the attributes described in
a=cpar, it is recommended to consult the document defining the a=cpar, it is recommended to consult the document defining the
attribute for dealing under media stream multiplexing. attribute.
5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP Sessions 5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP Sessions
[RFC6284] presents a port mapping solution that allows RTP receivers [RFC6284] presents a port mapping solution that allows RTP receivers
to choose their own ports for an auxiliary unicast session in RTP to choose their own ports for an auxiliary unicast session in RTP
applications using both unicast and multicast services. The solution applications using both unicast and multicast services. The solution
provides protection against denial-of-service or packet amplification provides protection against denial-of-service or packet amplification
attacks that could be used to cause one or more RTP packets to be attacks that could be used to cause one or more RTP packets to be
sent to a victim client sent to a victim client.
+------------------+-------------------------+-------+--------------+ +------------------+-------------------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------------+-------------------------+-------+--------------+ +------------------+-------------------------+-------+--------------+
| portmapping-req | Not recommended, if | M | NOT | | portmapping-req | Not recommended, if | M | NOT |
| | port mapping is | | RECOMMENDED | | | port mapping is | | RECOMMENDED |
| | required by the | | | | | required by the | | |
| | application | | | | | application | | |
| | | | | | | | | |
+------------------+-------------------------+-------+--------------+ +------------------+-------------------------+-------+--------------+
skipping to change at page 27, line 25 skipping to change at page 27, line 31
| | | | | | | | | |
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
RFC6714 Attribute Analysis RFC6714 Attribute Analysis
5.27. RFC4583 - SDP Format for BFCP Streams 5.27. RFC4583 - SDP Format for BFCP Streams
[RFC4583] document specifies how to describe Binary Floor Control [RFC4583] document specifies how to describe Binary Floor Control
Protocol (BFCP) streams in Session Description Protocol (SDP) Protocol (BFCP) streams in Session Description Protocol (SDP)
descriptions. User agents using the offer/answer model to establish descriptions. User agents using the offer/answer model to establish
BFCP streams use this format in their offers and answers BFCP streams use this format in their offers and answers.
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | 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 |
skipping to change at page 28, line 22 skipping to change at page 28, line 28
| file-disposition | Not Impacted | M | NORMAL | | file-disposition | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-date | Not Impacted | M | NORMAL | | file-date | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-iconfile-range | Not Impacted | M | NORMAL | | file-iconfile-range | Not Impacted | M | NORMAL |
| | | | | | | | | |
+----------------------+---------------+-------+----------+ +----------------------+---------------+-------+----------+
RFC5547 Attribute Analysis RFC5547 Attribute Analysis
5.29. RFC6489 - SDP and RTP Media Loopback Extension 5.29. RFC6849 - SDP and RTP Media Loopback Extension
[RFC6489] adds new SDP media types and attributes, which enable [RFC6849] adds new SDP media types and attributes, which enable
establishment of media sessions where the media is looped back to the establishment of media sessions where the media is looped back to the
transmitter. Such media sessions will serve as monitoring and transmitter. Such media sessions will serve as monitoring and
troubleshooting tools by providing the means for measurement of more troubleshooting tools by providing the means for measurement of more
advanced VoIP, Real-time Text and Video over IP performance metrics. advanced VoIP, Real-time Text and Video over IP performance metrics.
+------------------------------+----------------+-------+----------+ +------------------------------+----------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------------------------+----------------+-------+----------+ +------------------------------+----------------+-------+----------+
| loopback rtp-pkt-loopback | Not Impacted | M | NORMAL | | loopback rtp-pkt-loopback | Not Impacted | M | NORMAL |
| | | | | | | | | |
| loopback rtp-media-loopback | Not Impacted | M | NORMAL | | loopback rtp-media-loopback | Not Impacted | M | NORMAL |
| | | | | | | | | |
| loopback-source | Not Impacted | M | NORMAL | | loopback-source | Not Impacted | M | NORMAL |
| | | | | | | | | |
| loopback-mirror | Not Impacted | M | NORMAL | | loopback-mirror | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------------------------+----------------+-------+----------+ +------------------------------+----------------+-------+----------+
An Extension to the Session Description Protocol (SDP) and Real-time RFC6849 Analysis
Transport Protocol (RTP) for Media Loopback
5.30. RFC5760 - RTCP with Unicast Feedback 5.30. RFC5760 - RTCP with Unicast Feedback
[RFC5760] specifies an extension to the Real-time Transport Control [RFC5760] specifies an extension to the Real-time Transport Control
Protocol (RTCP) to use unicast feedback to a multicast sender. The Protocol (RTCP) to use unicast feedback to a multicast sender. The
proposed extension is useful for single-source multicast sessions proposed extension is useful for single-source multicast sessions
such as Source-Specific Multicast (SSM) communication where the such as Source-Specific Multicast (SSM) communication where the
traditional model of many-to-many group communication is either not traditional model of many-to-many group communication is either not
available or not desired. available or not desired.
skipping to change at page 31, line 24 skipping to change at page 31, line 24
| mscap | Refer to Section Section 14 | B | INHERIT | | mscap | Refer to Section Section 14 | B | INHERIT |
| | | | | | | | | |
| lcfg | Refer to Section Section 14 | B | SPECIAL | | lcfg | Refer to Section Section 14 | B | SPECIAL |
| | | | | | | | | |
| sescap | Refer to Section Section 14 | S | NOT RECOMMENDED | | sescap | Refer to Section Section 14 | S | NOT RECOMMENDED |
| | | | | | | | | |
| med-v0 | Not Impacted | S | NORMAL | | med-v0 | Not Impacted | S | NORMAL |
| | | | | | | | | |
+---------+-----------------------------+-------+-------------------+ +---------+-----------------------------+-------+-------------------+
Session Description Protocol (SDP) Media Capabilities Negotiation RFC6871 - Attribute Analysis
The "sescap" attribute is NOT RECOMMENDED for use with multiplexing. The "sescap" attribute is NOT RECOMMENDED for use with multiplexing.
The reason is that it requires the use of unique configuration The reason is that it requires the use of unique configuration
numbers across the entire SDP (per [RFC6871] as opposed to within a numbers across the entire SDP (per [RFC6871] as opposed to within a
media description only (per [RFC5939]). As described in Section 15, media description only (per [RFC5939]). As described in Section 14,
the use of identical configuration numbers between multiplxed the use of identical configuration numbers between multiplxed
(bundled) media descriptions is the default way of indicating (bundled) media descriptions is the default way of indicating
compatible configurations in a bundle. compatible configurations in a bundle.
5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP 5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP
[RFC7006] extends the SDP capability negotiation framework to allow [RFC7006] extends the SDP capability negotiation framework to allow
endpoints to negotiate three additional SDP capabilities. In endpoints to negotiate three additional SDP capabilities. In
particular, this memo provides a mechanism to negotiate bandwidth particular, this memo provides a mechanism to negotiate bandwidth
("b=" line), connection data ("c=" line), and session or media titles ("b=" line), connection data ("c=" line), and session or media titles
skipping to change at page 32, line 25 skipping to change at page 32, line 25
| | 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 |
| | | | | | | | | |
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
Miscellaneous Capabilities Negotiation in the Session Description RFC7006 - Attribute Analysis
Protocol (SDP)
5.35. RFC4567 - Key Management Extensions for SDP and RTSP 5.35. RFC4567 - Key Management Extensions for SDP and RTSP
[RFC4567] defines general extensions for Session Description Protocol [RFC4567] defines general extensions for Session Description Protocol
(SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as (SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as
specified by a key management protocol, in order to secure the media. specified by a key management protocol, in order to secure the media.
These extensions are presented as a framework, to be used by one or These extensions are presented as a framework, to be used by one or
more key management protocols. As such, their use is meaningful only more key management protocols. As such, their use is meaningful only
when complemented by an appropriate key management protocol. when complemented by an appropriate key management protocol.
skipping to change at page 33, line 38 skipping to change at page 33, line 38
5.37. RFC4570 - SDP Source Filters 5.37. RFC4570 - SDP Source Filters
[RFC4570] describes how to adapt the Session Description Protocol [RFC4570] describes how to adapt the Session Description Protocol
(SDP) to express one or more source addresses as a source filter for (SDP) to express one or more source addresses as a source filter for
one or more destination "connection" addresses. It defines the one or more destination "connection" addresses. It defines the
syntax and semantics for an SDP "source-filter" attribute that may syntax and semantics for an SDP "source-filter" attribute that may
reference either IPv4 or IPv6 address(es) as either an inclusive or reference either IPv4 or IPv6 address(es) as either an inclusive or
exclusive source list for either multicast or unicast destinations. exclusive source list for either multicast or unicast destinations.
In particular, an inclusive source-filter can be used to specify a In particular, an inclusive source-filter can be used to specify a
Source-Specific Multicast (SSM) session Source-Specific Multicast (SSM) session.
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| source-filter | The attribute MUST be | B | IDENTICAL | | source-filter | The attribute MUST be | B | IDENTICAL |
| | repeated across all m=lines | | | | | repeated across all m=lines | | |
| | multiplexed | | | | | multiplexed | | |
| | | | | | | | | |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
skipping to change at page 38, line 31 skipping to change at page 38, line 31
| | 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. RFC6064 - SDP and RTSP Extensions for 3GPP 5.46. RFC2326 - Real Time Streaming Protocol
The Real Time Streaming Protocol, or RTSP, is an application-level
protocol for control over the delivery of data with real-time
properties. RTSP provides an extensible framework to enable
controlled, on-demand delivery of real-time data, such as audio and
video.
+----------+---------------------------------+-------+--------------+
| Name | Notes | Level | Category |
+----------+---------------------------------+-------+--------------+
| etag | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED |
| | | | |
| range | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED |
| | | | |
| control | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED |
| | | | |
| mtag | RTSP is not supported for RTP | B | NOT |
| | Stream multiplexing | | RECOMMENDED |
| | | | |
+----------+---------------------------------+-------+--------------+
RFC2326 Attribute Analysis
5.47. RFC6064 - SDP and RTSP Extensions for 3GPP
The Packet-switched Streaming Service (PSS) and the Multimedia The Packet-switched Streaming Service (PSS) and the Multimedia
Broadcast/Multicast Service (MBMS) defined by 3GPP use the Session Broadcast/Multicast Service (MBMS) defined by 3GPP use the Session
Description Protocol (SDP) and Real Time Streaming Protocol (RTSP) Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)
with some extensions. [RFC6064] provides information about these with some extensions. [RFC6064] provides information about these
extensions and registers the RTSP and SDP extensions with IANA. extensions and registers the RTSP and SDP extensions with IANA.
+-------------------------------+------------+-------+--------------+ +-------------------------------+------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------------------------+------------+-------+--------------+ +-------------------------------+------------+-------+--------------+
skipping to change at page 39, line 29 skipping to change at page 40, line 22
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-SDP-Auth | Refer to | S | NOT | | 3GPP-SDP-Auth | Refer to | S | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-SRTP-Config | Refer to | M | NOT | | 3GPP-SRTP-Config | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| alt,alt-default-id | Refer to | M | NOT | | alt | Refer to | M | NOT |
| | notes | | RECOMMENDED |
| | below | | |
| | | | |
| alt-default-id | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| alt-group | Refer to | M | NOT | | alt-group | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
| | | | | | | | | |
| 3GPP-Adaptation-Support | Refer to | M | NOT | | 3GPP-Adaptation-Support | Refer to | M | NOT |
| | notes | | RECOMMENDED | | | notes | | RECOMMENDED |
| | below | | | | | below | | |
skipping to change at page 41, line 10 skipping to change at page 42, line 7
| | | | | | | | | |
+-------------------------------+------------+-------+--------------+ +-------------------------------+------------+-------+--------------+
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.47. RFC3108 - ATM SDP 5.48. RFC3108 - ATM SDP
RFC3108 [RFC3108] describes conventions for using the Session RFC3108 [RFC3108] describes conventions for using the Session
Description Protocol (SDP) described for controlling ATM Bearer Description Protocol (SDP) described for controlling ATM Bearer
Connections, and any associated ATM Adaptation Layer (AAL) Connections, and any associated ATM Adaptation Layer (AAL).
+------------------------+--------------+-------+----------+ +------------------------+--------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------------------+--------------+-------+----------+ +------------------------+--------------+-------+----------+
| aalType | Not Impacted | B | NORMAL | | aalType | Not Impacted | B | NORMAL |
| eecid | Not Impacted | B | NORMAL | | eecid | Not Impacted | B | NORMAL |
| aalType | Not Impacted | B | NORMAL | | aalType | Not Impacted | B | NORMAL |
| capability | Not Impacted | B | NORMAL | | capability | Not Impacted | B | NORMAL |
| qosClass | Not Impacted | B | NORMAL | | qosClass | Not Impacted | B | NORMAL |
| bcob | Not Impacted | B | NORMAL | | bcob | Not Impacted | B | NORMAL |
skipping to change at page 42, line 34 skipping to change at page 43, line 32
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.
5.48. 3GPP TS 26.114 5.49. 3GPP TS 26.114
[R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and [R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and
interaction interaction
+----------------------+-------------------------+-------+----------+ +----------------------+-------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+----------------------+-------------------------+-------+----------+ +----------------------+-------------------------+-------+----------+
| 3gpp_sync_info | Usage defined for the | M | NORMAL | | 3gpp_sync_info | Usage defined for the | M | NORMAL |
| | IP Multimedia Subsystem | | | | | IP Multimedia Subsystem | | |
| | | | | | | | | |
| 3gpp_MaxRecvSDUSize | Usage defined for the | M | NORMAL | | 3gpp_MaxRecvSDUSize | Usage defined for the | M | NORMAL |
| | IP Multimedia Subsystem | | | | | IP Multimedia Subsystem | | |
| | | | | | | | | |
+----------------------+-------------------------+-------+----------+ +----------------------+-------------------------+-------+----------+
3GPP TS 24.182 Attribute Analysis 3GPP TS 26.114 Attribute Analysis
5.49. 3GPP TS 24.182 5.50. 3GPP TS 183.063
[R3GPPTS183.063] Telecommunications and Internet converged Services
and Protocols for Advanced Networking (TISPAN);
+---------------------+---------------+----------------+----------+
| Name | Notes | Level | Category |
+---------------------+---------------+----------------+----------+
| PSCid | Not Impacted | Not-ApplIcable | NORMAL |
| | | | |
| bc_service | Not Impacted | Not-AppIlcable | NORMAL |
| | | | |
| bc_program | Not Impacted | Not-AppIlcable | NORMAL |
| | | | |
| bc_service_package | Not Impacted | Not-Appilcable | NORMAL |
| | | | |
+---------------------+---------------+----------------+----------+
3GPP TS 183.063 Attribute Analysis
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 | Category | | Name | Notes | Level | Category |
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
| g.3gpp.cat | Usage defined for the IP | M | NORMAL | | g.3gpp.cat | Usage defined for the IP | M | NORMAL |
| | Multimedia Subsystem | | | | | Multimedia Subsystem | | |
| | | | | | | | | |
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
3GPP TS 24.182 Attribute Analysis 3GPP TS 24.182 Attribute Analysis
5.50. 3GPP TS 24.183 5.52. 3GPP TS 24.183
[R3GPPTS24.183] specifies IP multimedia subsystem Custom Ringing [R3GPPTS24.183] specifies IP multimedia subsystem Custom Ringing
Signal Signal
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
| g.3gpp.crs | Usage defined for the IP | M | NORMAL | | g.3gpp.crs | Usage defined for the IP | M | NORMAL |
| | Multimedia Subsystem | | | | | Multimedia Subsystem | | |
| | | | | | | | | |
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
3GPP TS 24.183 Attribute Analysis 3GPP TS 24.183 Attribute Analysis
skipping to change at page 43, line 35 skipping to change at page 45, line 14
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
| g.3gpp.crs | Usage defined for the IP | M | NORMAL | | g.3gpp.crs | Usage defined for the IP | M | NORMAL |
| | Multimedia Subsystem | | | | | Multimedia Subsystem | | |
| | | | | | | | | |
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
3GPP TS 24.183 Attribute Analysis 3GPP TS 24.183 Attribute Analysis
5.51. 3GPP TS 24.229 5.53. 3GPP TS 24.229
[R3GPPTS24.229] specifies IP multimedia call control protocol based [R3GPPTS24.229] specifies IP multimedia call control protocol based
on Session Initial protocol and Session Description Protocol. on Session Initial protocol and Session Description Protocol.
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| secondary-realm | Per media-level attribute | M | TRANSPORT | | secondary-realm | Per media-level attribute | M | TRANSPORT |
| | MUST be used per | | | | | MUST be used per | | |
| | underlying transport | | | | | underlying transport | | |
skipping to change at page 44, line 34 skipping to change at page 46, line 5
| omr-s-bw | Not Impacted | M | NORMAL | | omr-s-bw | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-m-att | Not Impacted | M | NORMAL | | omr-m-att | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-codecs | Not Impacted | M | NORMAL | | omr-codecs | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
3GPP TS 24.229 Attribute Analysis 3GPP TS 24.229 Attribute Analysis
5.52. ITU T.38 5.54. ITU T.38
[T.38] defines procedures for real-time Group 3 facsimile [T.38] defines procedures for real-time Group 3 facsimile
communications over IP networks. communications over IP networks.
+------------------------+---------------+-------+----------+ +------------------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------------------+---------------+-------+----------+ +------------------------+---------------+-------+----------+
| T38FaxVersion | Not Impacted | S | NORMAL | | T38FaxVersion | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38MaxBitRate | Not Impacted | S | NORMAL | | T38MaxBitRate | Not Impacted | S | NORMAL |
skipping to change at page 45, line 36 skipping to change at page 46, line 41
| T38FaxMaxIFP | Not Impacted | S | NORMAL | | T38FaxMaxIFP | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxUdpECDepth | Not Impacted | S | NORMAL | | T38FaxUdpECDepth | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxUdpFECMaxSpan | Not Impacted | S | NORMAL | | T38FaxUdpFECMaxSpan | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38ModemType | Not Impacted | S | NORMAL | | T38ModemType | Not Impacted | S | NORMAL |
| | | | | | | | | |
+------------------------+---------------+-------+----------+ +------------------------+---------------+-------+----------+
Historic 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.53. ITU-T-REC.Q1970 5.55. ITU-T-REC.Q1970
[ITU-T-REC.Q1970] defines BICC IP bearer control protocol. [ITU-T-REC.Q1970] defines BICC IP bearer control protocol.
+--------+---------------+-------+----------+ +--------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+--------+---------------+-------+----------+ +--------+---------------+-------+----------+
| ipbcp | Not Impacted | S | NORMAL | | ipbcp | Not Impacted | S | NORMAL |
| | | | | | | | | |
+--------+---------------+-------+----------+ +--------+---------------+-------+----------+
ITU-T-REC.Q1970 Attribute Analysis ITU-T-REC.Q1970 Attribute Analysis
5.54. ITU-T H.248.15 5.56. ITU-T H.248.15
ITU-T H.248.15 [H.248.15] defines Gateway Control Protocol SDP H.248 ITU-T H.248.15 [H.248.15] defines Gateway Control Protocol SDP H.248
package attribute package attribute
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
| h248item | It is also only applicable for | B | SPECIAL | | h248item | It is also 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 | | |
skipping to change at page 46, line 35 skipping to change at page 47, line 44
| | 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. | | |
| | | | | | | | | |
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
Historic Attribute Analysis ITU-T H.248.15 Attribute Analysis
5.55. RFC4975 - The Message Session Relay Protocol 5.57. RFC4975 - The Message Session Relay Protocol
[RFC4975] the Message Session Relay Protocol, a protocol for [RFC4975] the Message Session Relay Protocol, a protocol for
transmitting a series of related instant messages in the context of a transmitting a series of related instant messages in the context of a
session. Message sessions are treated like any other media stream session. Message sessions are treated like any other media stream
when set up via a rendezvous or session creation protocol such as the when set up via a rendezvous or session creation protocol such as the
Session Initiation Protocol. Session Initiation Protocol.
+-----------------------+---------------+-------+----------+ +-----------------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-----------------------+---------------+-------+----------+ +-----------------------+---------------+-------+----------+
skipping to change at page 47, line 20 skipping to change at page 48, line 20
| accept-wrapped-types | Not Impacted | M | NORMAL | | accept-wrapped-types | Not Impacted | M | NORMAL |
| | | | | | | | | |
| max-size | Not Impacted | M | NORMAL | | max-size | Not Impacted | M | NORMAL |
| | | | | | | | | |
| path | Not Impacted | M | NORMAL | | path | Not Impacted | M | NORMAL |
| | | | | | | | | |
+-----------------------+---------------+-------+----------+ +-----------------------+---------------+-------+----------+
RFC4975 Attribute Analysis RFC4975 Attribute Analysis
5.56. Historical 5.58. RFC4574 - SDP Label Attribute
[RFC4574] defines a new Session Description Protocol (SDP) media-
level attribute: "label". The "label" attribute carries a pointer to
a media stream in the context of an arbitrary network application
that uses SDP. The sender of the SDP document can attach the "label"
attribute to a particular media stream or streams. The application
can then use the provided pointer to refer to each particular media
stream in its context.
+--------+---------------+-------+----------+
| Name | Notes | Level | Category |
+--------+---------------+-------+----------+
| label | Not Impacted | M | NORMAL |
| | | | |
+--------+---------------+-------+----------+
RFC4574 Attribute Analysis
5.59. Historical Attributes
This section specifies analysis for the attributes that are included This section specifies analysis for the attributes that are included
for historic usage alone by the [IANA]. for historic usage alone by the [IANA].
+---------------------+--------------+---------------+--------------+ +----------+---------------------+----------------+-----------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------------------+--------------+---------------+--------------+ +----------+---------------------+----------------+-----------------+
| rtpred1 | Historic | Not-Applcable | NOT | | rtpred1 | Historic | Not-Applicable | NOT RECOMMENDED |
| | attributes. | | RECOMMENDED | | | attributes. | | |
| | | | | | | | | |
| rtpred2 | Historic | Not-Applcable | NOT | | rtpred2 | Historic | Not-Applicable | NOT RECOMMENDED |
| | attributes. | | RECOMMENDED | | | attributes. | | |
| | | | | | | | | |
| PSCid | Not | Not-Applcable | NORMAL | +----------+---------------------+----------------+-----------------+
| | Applicable | | |
| | | | |
| bc_service | Not | Not-Applcable | NORMAL |
| | Applicable | | |
| | | | |
| bc_program | Not | Not-Applcable | NORMAL |
| | Applicable | | |
| | | | |
| bc_service_package | Not | Not-Applcable | NORMAL |
| | Applicable | | |
| | | | |
+---------------------+--------------+---------------+--------------+
Unknowns Attribute Analysis Historical Attribute Analysis
6. bwtype Attribute Analysis 6. bwtype Attribute Analysis
This section specifies handling of specific bandwidth attributes when This section specifies handling of specific bandwidth attributes when
used in multiplexing scenarios. used in multiplexing scenarios.
6.1. RFC4566 - SDP: Session Description Protocol 6.1. RFC4566 - SDP: Session Description Protocol
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
skipping to change at page 48, line 35 skipping to change at page 49, line 48
| 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 [RFC3556] defines an extension to the Session Description [RFC3556] defines an extension to the Session Description Protocol
Protocol (SDP) to specify two additional modifiers for the bandwidth (SDP) to specify two additional modifiers for the bandwidth
attribute. These modifiers may be used to specify the bandwidth attribute. These modifiers may be used to specify the bandwidth
allowed for RTP Control Protocol (RTCP) packets in a Real-time allowed for RTP Control Protocol (RTCP) packets in a Real-time
Transport Protocol (RTP) session Transport Protocol (RTP) session.
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| bwtype:RS | Session level usage represents | B | NORMAL | | bwtype:RS | Session level usage represents | B | NORMAL |
| | session aggregate and media level | | | | | session aggregate and media level | | |
| | usage indicates SUM of the | | | | | usage indicates SUM of the | | |
| | individual values while | | | | | individual values while | | |
| | multiplexing | | | | | multiplexing | | |
| | | | | | | | | |
| bwtype:RR | Session level usage represents | B | NORMAL | | bwtype:RR | Session level usage represents | B | NORMAL |
skipping to change at page 49, line 25 skipping to change at page 50, line 26
| | usage indicates SUM of the | | | | | usage indicates SUM of the | | |
| | individual values while | | | | | individual values while | | |
| | multiplexing | | | | | multiplexing | | |
| | | | | | | | | |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
RFC3556 bwtype Analysis RFC3556 bwtype Analysis
6.3. RFC3890 - Bandwidth Modifier for SDP 6.3. RFC3890 - Bandwidth Modifier for SDP
RFC3890 [RFC3890] defines a Session Description Protocol (SDP) [RFC3890] defines a Session Description Protocol (SDP) Transport
Transport Independent Application Specific Maximum (TIAS) bandwidth Independent Application Specific Maximum (TIAS) bandwidth modifier
modifier that does not include transport overhead; instead an that does not include transport overhead; instead an additional
additional packet rate attribute is defined. The transport packet rate attribute is defined. The transport independent bit-rate
independent bit-rate value together with the maximum packet rate can value together with the maximum packet rate can then be used to
then be used to calculate the real bit-rate over the transport calculate the real bit-rate over the transport actually used.
actually used.
+--------------+---------------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+--------------+---------------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
| bwtype:TIAS | The usage of TIAS is not | B | SPECIAL | | bwtype:TIAS | The usage of TIAS is not | B | SPECIAL |
| | clearly defined Offer/Answer | | | | | clearly defined | | |
| | usage. | | | | | Offer/Answer usage. | | |
| | | | | | | | | |
| maxprate | The usage of TIAS and maxprate | B | SPECIAL | | bwtype:maxprate | The usage of TIAS and | B | SPECIAL |
| | is not well defined under | | | | | maxprate is not well | | |
| | multiplexing | | | | | defined under multiplexing | | |
| | | | | | | | | |
+--------------+---------------------------------+-------+----------+ +------------------+-----------------------------+-------+----------+
RFC3890 bwtype Analysis RFC3890 bwtype Analysis
The intention of TIAS is that the media level bit-rate is multiplied The intention of TIAS is that the media level bit-rate is multiplied
with the known per-packet overhead for the selected transport and the with the known per-packet overhead for the selected transport and the
maxprate value to determine the worst case bit-rate from the maxprate value to determine the worst case bit-rate from the
transport to more accurately capture the required usage. Summing transport to more accurately capture the required usage. Summing
TIAS values independently across m=lines and multiplying the computed TIAS values independently across m=lines and multiplying the computed
sum with maxprate and the per-packet overhead would inflate the value sum with maxprate and the per-packet overhead would inflate the value
significantly. Instead performing multiplication and adding the significantly. Instead performing multiplication and adding the
individual values is a more appropriate usage. This still ignores individual values is a more appropriate usage. This still ignores
the fact that this is a send side declaration, and not intended for the fact that this is a send side declaration, and not intended for
receiver negotiation. receiver negotiation.
7. rtcp-fb Attribute Analysis 7. rtcp-fb Attribute Analysis
This section analyzes rtcp-fb SDP attributes. This section analyzes rtcp-fb SDP attributes.
7.1. RFC4585 - RTP/AVPF 7.1. RFC4585 - RTP/AVPF
RFC4585 [RFC4585] defines an extension to the Audio-visual Profile [RFC4585] defines an extension to the Audio-visual Profile (AVP) that
(AVP) that enables receivers to provide, statistically, more enables receivers to provide, statistically, more immediate feedback
immediate feedback to the senders and thus allows for short-term to the senders and thus allows for short-term adaptation and
adaptation and efficient feedback-based repair mechanisms to be efficient feedback-based repair mechanisms to be implemented.
implemented.
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| Attr | Notes | Level | Category | | Attr | Notes | Level | Category |
| Name | | | | | Name | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| ack rpsi | The attribute value must | M | IDENTICAL-PER-PT | | ack rpsi | The attribute value must | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ack app | Feedback parameters MUST | M | SPECIAL | | ack app | Feedback parameters MUST | M | SPECIAL |
skipping to change at page 51, line 49 skipping to change at page 52, line 49
| 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 [RFC5104] specifies a few extensions to the messages defined [RFC5104] specifies a few extensions to the messages defined in the
in the Audio-Visual Profile with Feedback (AVPF). They are helpful Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls. in smaller multicast environments and point-to-point calls.
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| Attr | Notes | Level | Category | | Attr | Notes | Level | Category |
| Name | | | | | Name | | | |
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value must be | M | IDENTICAL-PER-PT |
| | same for a given codec | | | | | same for a given codec | | |
skipping to change at page 52, line 34 skipping to change at page 53, line 34
| nack | The attribute value must be | M | IDENTICAL-PER-PT | | nack | The attribute value must be | M | IDENTICAL-PER-PT |
| rai | same for a given codec | | | | rai | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
RFC6285 Attribute Analysis RFC6285 Attribute Analysis
7.4. RFC6679 - ECN for RTP over UDP/IP 7.4. RFC6679 - ECN for RTP over UDP/IP
RFC6679 [RFC6679] specifies how Explicit Congestion Notification [RFC6679] specifies how Explicit Congestion Notification (ECN) can be
(ECN) can be used with the Real-time Transport Protocol (RTP) running used with the Real-time Transport Protocol (RTP) running over UDP,
over UDP, using the RTP Control Protocol (RTCP) as a feedback using the RTP Control Protocol (RTCP) as a feedback mechanism. It
mechanism. It defines a new RTCP Extended Report (XR) block for defines a new RTCP Extended Report (XR) block for periodic ECN
periodic ECN feedback, a new RTCP transport feedback message for feedback, a new RTCP transport feedback message for timely reporting
timely reporting of congestion events, and a Session Traversal of congestion events, and a Session Traversal Utilities for NAT
Utilities for NAT (STUN) extension used in the optional (STUN) extension used in the optional initialization method using
initialization method using Interactive Connectivity Establishment Interactive Connectivity Establishment (ICE).
(ICE)
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| ecn-capable-rtp | ECN markup are enabled at | M | IDENTICAL | | ecn-capable-rtp | ECN markup are enabled at | M | IDENTICAL |
| | the RTP Session level | | | | | the RTP Session level | | |
| | | | | | | | | |
| nack ecn | This attribute enables | M | IDENTICAL | | nack ecn | This attribute enables | M | IDENTICAL |
| | ECN at the RTP session | | | | | ECN at the RTP session | | |
| | level | | | | | level | | |
| | | | | | | | | |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
RFC6679 Attribute Analysis RFC6679 Attribute Analysis
7.5. RFC6642 - Third-Party Loss Report 7.5. RFC6642 - Third-Party Loss Report
In a large RTP session using the RTP Control Protocol (RTCP) feedback In a large RTP session using the RTP Control Protocol (RTCP) feedback
mechanism defined in RFC 4585 [RFC4585], a feedback target may mechanism defined in [RFC4585], a feedback target may experience
experience transient overload if some event causes a large number of transient overload if some event causes a large number of receivers
receivers to send feedback at once. This overload is usually avoided to send feedback at once. This overload is usually avoided by
by ensuring that feedback reports are forwarded to all receivers, ensuring that feedback reports are forwarded to all receivers,
allowing them to avoid sending duplicate feedback reports. However, allowing them to avoid sending duplicate feedback reports. However,
there are cases where it is not recommended to forward feedback there are cases where it is not recommended to forward feedback
reports, and this may allow feedback implosion. RFC6642 [RFC6642] reports, and this may allow feedback implosion. [RFC6642] memo
memo discusses these cases and defines a new RTCP Third-Party Loss discusses these cases and defines a new RTCP Third-Party Loss Report
Report that can be used to inform receivers that the feedback target that can be used to inform receivers that the feedback target is
is aware of some loss event, allowing them to suppress feedback. aware of some loss event, allowing them to suppress feedback.
Associated Session Description Protocol (SDP) signaling is also Associated Session Description Protocol (SDP) signaling is also
defined. defined.
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| nack | The attribute value must be | M | IDENTICAL-PER-PT | | nack | The attribute value must be | M | IDENTICAL-PER-PT |
| tllei | same for a given codec | | | | tllei | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
skipping to change at page 54, line 37 skipping to change at page 55, line 37
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
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" semantics.
8.1. RFC5888 - SDP Grouping Framework 8.1. RFC5888 - SDP Grouping Framework
RFC5888 [RFC5888] defines a framework to group "m" lines in the [RFC5888] defines a framework to group "m" lines in the Session
Session Description Protocol (SDP) for different purposes. Description Protocol (SDP) for different purposes.
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
| group:LS | Not Impacted | S | NORMAL | | group:LS | Not Impacted | S | NORMAL |
| | | | | | | | | |
| group:FID | Not Impacted | S | NORMAL | | group:FID | Not Impacted | S | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
RFC5888 Attribute Analysis RFC5888 Attribute Analysis
8.2. RFC3524 - Mapping Media Streams to Resource Reservation Flows 8.2. RFC3524 - Mapping Media Streams to Resource Reservation Flows
RFC3524 [RFC3524] defines an extension to the Session Description [RFC3524] defines an extension to the Session Description Protocol
Protocol (SDP) grouping framework. It allows requesting a group of (SDP) grouping framework. It allows requesting a group of media
media streams to be mapped into a single resource reservation flow. streams to be mapped into a single resource reservation flow. The
The SDP syntax needed is defined, as well as a new "semantics" SDP syntax needed is defined, as well as a new "semantics" attribute
attribute called Single Reservation Flow (SRF). called Single Reservation Flow (SRF).
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
| group:SRF | Not Impacted | S | NORMAL | | group:SRF | Not Impacted | S | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
RFC3524 Attribute Analysis RFC3524 Attribute Analysis
8.3. RFC4091 - ANAT Semantics 8.3. RFC4091 - ANAT Semantics
RFC4091 [RFC4091] defines the Alternative Network Address Types [RFC4091] defines the Alternative Network Address Types (ANAT)
(ANAT) semantics for the Session Description Protocol (SDP) grouping semantics for the Session Description Protocol (SDP) grouping
framework. The ANAT semantics allow alternative types of network framework. The ANAT semantics allow alternative types of network
addresses to establish a particular media stream. addresses to establish a particular media stream.
+-------------+---------------------------+-------+-----------------+ +-------------+---------------------------+-------+-----------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------+---------------------------+-------+-----------------+ +-------------+---------------------------+-------+-----------------+
| group:ANAT | ANAT semantics is | S | NOT RECOMMENDED | | group:ANAT | ANAT semantics is | S | NOT RECOMMENDED |
| | obseleted | | | | | obseleted | | |
| | | | | | | | | |
+-------------+---------------------------+-------+-----------------+ +-------------+---------------------------+-------+-----------------+
RFC4091 Attribute Analysis RFC4091 Attribute Analysis
8.4. RFC5956 - FEC Grouping Semantics in SDP 8.4. RFC5956 - FEC Grouping Semantics in SDP
RFC5956 [RFC5956] defines the semantics for grouping the associated [RFC5956] defines the semantics for grouping the associated source
source and FEC-based (Forward Error Correction) repair flows in the and FEC-based (Forward Error Correction) repair flows in the Session
Session Description Protocol (SDP). The semantics defined in the Description Protocol (SDP). The semantics defined in the document
document are to be used with the SDP Grouping Framework (RFC 5888). are to be used with the SDP Grouping Framework (RFC 5888). These
These semantics allow the description of grouping relationships semantics allow the description of grouping relationships between the
between the source and repair flows when one or more source and/or source and repair flows when one or more source and/or repair flows
repair flows are associated in the same group, and they provide are associated in the same group, and they provide support for
support for additive repair flows. SSRC-level (Synchronization additive repair flows. SSRC-level (Synchronization Source) grouping
Source) grouping semantics are also defined in this document for semantics are also defined in this document for Real-time Transport
Real-time Transport Protocol (RTP) streams using SSRC multiplexing. Protocol (RTP) streams using SSRC multiplexing.
+---------------+---------------+-------+----------+ +---------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------------+---------------+-------+----------+ +---------------+---------------+-------+----------+
| group:FEC-FR | Not Impacted | S | NORMAL | | group:FEC-FR | Not Impacted | S | NORMAL |
| | | | | | | | | |
+---------------+---------------+-------+----------+ +---------------+---------------+-------+----------+
RFC5956 Attribute Analysis RFC5956 Attribute Analysis
8.5. RFC5583 - Signaling Media Decoding Dependency in SDP 8.5. RFC5583 - Signaling Media Decoding Dependency in SDP
RFC5583 [RFC5583] defines semantics that allow for signaling the [RFC5583] defines semantics that allow for signaling the decoding
decoding dependency of different media descriptions with the same dependency of different media descriptions with the same media type
media type in the Session Description Protocol (SDP). This is in the Session Description Protocol (SDP). This is required, for
required, for example, if media data is separated and transported in example, if media data is separated and transported in different
different network streams as a result of the use of a layered or network streams as a result of the use of a layered or multiple
multiple descriptive media coding process. descriptive media coding process.
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| depend | The attribute value must be | M | IDENTICAL-PER-PT | | depend | The attribute value must be | M | IDENTICAL-PER-PT |
| lay | same for a given codec | | | | lay | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| depend | The attribute value must be | M | IDENTICAL-PER-PT | | depend | The attribute value must be | M | IDENTICAL-PER-PT |
| mdc | same for a given codec | | | | mdc | same for a given codec | | |
skipping to change at page 57, line 23 skipping to change at page 58, line 23
9. ssrc-group Attribute Analysis 9. ssrc-group Attribute Analysis
This section analyzes "ssrc-group" semantics. This section analyzes "ssrc-group" semantics.
9.1. RFC5576 - Source-Specific SDP Attributes 9.1. RFC5576 - Source-Specific SDP Attributes
+-------------------+---------------+-------+----------+ +-------------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------------+---------------+-------+----------+ +-------------------+---------------+-------+----------+
| ssrc-group:FID | Not Impacted | M | NORMAL | | ssrc-group:FID | Not Impacted | SR | NORMAL |
| | | | | | | | | |
| ssrc-group:FEC | Not Impacted | M | NORMAL | | ssrc-group:FEC | Not Impacted | SR | NORMAL |
| | | | | | | | | |
| ssrc-groupFEC-FR | Not Impacted | M | NORMAL | | ssrc-groupFEC-FR | Not Impacted | SR | NORMAL |
| | | | | | | | | |
+-------------------+---------------+-------+----------+ +-------------------+---------------+-------+----------+
RFC5576 Attribute Analysis RFC5576 Attribute Analysis
9.2. RFC7104 - Duplication Grouping Semantics in the SDP 9.2. RFC7104 - Duplication Grouping Semantics in the SDP
+-----------------+---------------+-------+----------+ +-----------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-----------------+---------------+-------+----------+ +-----------------+---------------+-------+----------+
| ssrc-group:DUP | Not Impacted | M | 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
skipping to change at page 58, line 31 skipping to change at page 59, line 31
+------+------------------------------------+-------+---------------+ +------+------------------------------------+-------+---------------+
| Name | Notes | Level | Category | | Name | Notes | Level | 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 Atribute Analysis 12. content Attribute Analysis
12.1. RFC4796 12.1. RFC4796
+------------------+---------------+-------+----------+ +------------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | 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 |
| | | | | | | | | |
skipping to change at page 60, line 12 skipping to change at page 61, line 12
a generic framework for indicating and negotiating transport, media a generic framework for indicating and negotiating transport, media
and media format related capabilities in the SDP. and media format related capabilities in the SDP.
The behavior of such attributes under multiplexing is in turn defined The behavior of such attributes under multiplexing is in turn defined
by the multiplexing behavior of the attributes they encapsulate which by the multiplexing behavior of the attributes they encapsulate which
are made known once the Offer/Answer negotiation process is are made known once the Offer/Answer negotiation process is
completed. completed.
14.1. RFC3407 - cpar Attribute Analysis 14.1. RFC3407 - cpar Attribute Analysis
RFC3407 capability parameter attribute (a=cpar) encapsulates b= [RFC3407] capability parameter attribute (a=cpar) encapsulates b=
(bandwidth) or an a= attribute. For bandwidth attribute (bandwidth) or an a= attribute. For bandwidth attribute
encapsulation, the category SUM is inherited. For the case of a= encapsulation, the category SUM is inherited. For the case of a=
attribute, the category corresponding to the SDP attribute being attribute, the category corresponding to the SDP attribute being
encapsulated is inherited. encapsulated is inherited.
v=0 v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s= s=
c=IN IP4 host.atlanta.example.com c=IN IP4 host.atlanta.example.com
t=0 0 t=0 0
skipping to change at page 61, line 36 skipping to change at page 62, line 36
14.2.1. Recommendation - Procedures for Potential Configuration Pairing 14.2.1. Recommendation - Procedures for Potential Configuration Pairing
This section provides recommendations for entities generating and This section provides recommendations for entities generating and
processing SDP under the generic capability negotiation framework as processing SDP under the generic capability negotiation framework as
defined in [RFC5939] under the context of media stream multiplexing. defined in [RFC5939] under the context of media stream multiplexing.
These recommendations are provided for the purposes of enabling the These recommendations are provided for the purposes of enabling the
Offerer to make sure that the generated potential configurations Offerer to make sure that the generated potential configurations
between the multiplexed streams can (easily) be negotiated to be between the multiplexed streams can (easily) be negotiated to be
consistent between those streams. In particular, the procedures aim consistent between those streams. In particular, the procedures aim
to simply 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 bundled 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
skipping to change at page 62, line 29 skipping to change at page 63, line 29
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 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
potential configurations with independent configuration numbers. The potential configurations with independent configuration numbers. The
answerer will have to perform more complicated analysis to determine answerer will have to perform more complicated analysis to determine
skipping to change at page 63, line 45 skipping to change at page 64, line 45
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
In the example above, the potential configuration number 1 is In the example above, the potential configuration number "1" is
repeated while referring to attribute capability a=rtcp-mux, since repeated while referring to attribute capability a=rtcp-mux, since
the behavior is IDENTICAL for the attribute a=rtcp-mux under the behavior is IDENTICAL for the attribute a=rtcp-mux under
multiplexing. multiplexing.
14.3. RFC6871 Analysis 14.3. RFC6871 Analysis
[RFC6871] extends capability negotiation framework described in [RFC6871] extends capability negotiation framework described in
[RFC5939] by defining media capabilities that can be used to indicate [RFC5939] by defining media capabilities that can be used to indicate
and negotiate media types and their associated format parameters. It and negotiate media types and their associated format parameters. It
also allows indication of latent configurations and session also allows indication of latent configurations and session
capabilities (the latter of which is not recommended for use with capabilities.
bundled media as described in Section 5.29).
14.3.1. Recommendation: Dealing with Payload Type Numbers 14.3.1. Recommendation: Dealing with Payload Type Numbers
RFC 6871 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 [I-D.ietf-mmusic- values across multiplexed m=lines as described in
sdp-bundle-negotiation], which MUST be followed here as well. As [I-D.ietf-mmusic-sdp-bundle-negotiation], which MUST be followed here
described in Section 15.2, the use of identical configuration numbers as well. As described in Section 14.2.1, the use of identical
for compatible configurations in different media descriptions that configuration numbers for compatible configurations in different
are part of the bundle provides a way to ensure that the answerer can media descriptions that are part of the bundle provides a way to
easily pick compatible configurations here as well. ensure that the answerer can easily pick compatible configurations
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 mutliplexing.
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;
mode-set=0,2,4,7 mode-set=0,2,4,7
skipping to change at page 65, line 33 skipping to change at page 66, line 33
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;
mode-set=0,2,4,7 mode-set=0,2,4,7
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
RFC 6871 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 bundled media, since it requires the use of unique
configuration numbers across the SDP. Taken together, this means configuration numbers across the SDP. Taken together, this means
there is no well-defined way to indicate supported combinations of there is no well-defined way to indicate supported combinations of
skipping to change at page 66, line 17 skipping to change at page 67, line 16
latent configuration attribute, however the limitations above will latent configuration attribute, however the limitations above will
apply. To determine valid combinations, actual negotiation will have apply. To determine valid combinations, actual negotiation will have
to be attempted subsequently instead. to be attempted subsequently instead.
15. IANA Considerations 15. IANA Considerations
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
document.] document.]
The IANA is requested to add a new column named "Mux Category" to all The IANA is requested to add a new column named "Mux Category" to all
several of the registries in the "Session Description Protocol (SDP) several of the subregistries in the "Session Description Protocol
Parameters". Section Section 15.1 defines the new registry for (SDP) Parameters" registry. Section 15.1 defines a new subregistry
identifying the initial registrations for "Mux Category" as proposed for identifying the initial registrations for various multiplexing
in this document. The tables in Section 15.2 identify name of an categories applicable as proposed in this document.
entry in the existing registry and specify the value to put in the
new "Mux Category" column of the associated IANA registry. Any
entries in the existing tables that do not have a value for the "Mux
Category" specified in this RFC will get a value of "TBD". Future
specifications can change the "TBD" entries to the correct value.
15.1. New Column 'Mux Category' The tables in Section 15.2 identify name of an entry in the existing
subregistry and specify the value to put in the new "Mux Category"
column of the associated IANA registry. Any entries in the existing
tables that do not have a value for the "Mux Category" specified in
this RFC will get a value of "TBD". Future specifications can change
the "TBD" entries to the correct value.
A new registry needs to be setup for specifying possible values for 15.1. New 'Multiplexing Categories' subregistry
the "Mux Category" column, with the following registrations created
initially: "NORMAL", "NOT RECOMMENDED", "IDENTICAL", "TRANSPORT",
"IDENTICAL-PER-PT", SPECIAL" and "TBD" as defined in this document.
Initial value registration for the column "Mux Category". A new sub-registry needs to be defined called the "Multiplexing
Categories", with the following registrations created initially:
"NORMAL", "NOT RECOMMENDED", "IDENTICAL", "TRANSPORT", "IDENTICAL-
PER-PT", "SPECIAL" and "TBD" as defined in this document.
Value name: NORMAL Initial value registration for "Mux Category".
Reference : RFCXXXX
Value name: NOT RECOMMENDED +-------------------------+-----------+
Reference : RFCXXXX | Multiplexing Categories | Reference |
+-------------------------+-----------+
| NORMAL | RFCXXXX |
| NOT RECOMMENDED | RFCXXXX |
| IDENTICAL | RFCXXXX |
| TRANSPORT | RFCXXXX |
| IDENTICAL-PER-PT | RFCXXXX |
| SPECIAL | RFCXXXX |
| TBD | RFCXXXX |
+-------------------------+-----------+
Value name: IDENTICAL Further entries may be registered on a first-come first-serve basis.
Reference : RFCXXXX Each registration needs to indicate the multiplexing category value
to be added to the "Multiplexing Categories" subregistry as defined
in this section.
Value name: TRANSPORT Such a registration must also indicate the applicability of the newly
Reference : RFCXXXX defined multiplexing category value to various subregistries defined
at "Session Description Protocol (SDP) Parameters".
Value name: IDENTICAL-PER-PT The general registration procedures of [RFC4566] apply.
Reference : RFCXXXX
Value name: SPECIAL 15.2. 'Mux Category' column for subregistries
Reference : RFCXXXX
Value name: TBD Each sub-section identifies a subregistry in the "Session Description
Reference : RFCXXXX Protocol (SDP) Parameters" registry. The tables list the column that
identifies the SDP attribute name/Token/Value from the corresponding
subregistries and the values to be used for the new "Mux Category"
column to be added.
Further entries may be registered on a first-come first-serve basis. 15.2.1. Table: SDP bwtype
Each registration needs to indicate the "Mux Category" value and
identify the entries in the existing registries defined at "Session
Description Protocol (SDP) Parameters" to which the newly registered
"Mux Category" applies. For each new registration, it is mandatory
that a permanent, stable, and publicly accessible document exists
that specifies the semantics of the registered parameter in the
context of multiplexing and its applicability to existing registered
SDP parameters as stated above. The general registration procedures
of [RFC4566] apply.
15.2. 'Mux Category' values for SDP Registries The following values are to be added to the 'SDP bwtype' subregistry
in the "Session Description Protocol (SDP) Parameters" registry. The
references should be updated to point at this RFC as well as the
previous references.
The various sub-sections below assigns the values to be used for the +----------+--------------+
"Mux Category" column for the corresponding registries idenfied. | SDP Name | Mux Category |
+----------+--------------+
| CT | NORMAL |
| AS | SUM |
| RS | NORMAL |
| RR | NORMAL |
| TIAS | SPECIAL |
+----------+--------------+
15.2.1. Table: SDP bwtype 15.2.2. Table: att-field (session level)
The following values are to be added to the 'SDP bwtype' registry in The following values are to be added to the "att-field (session
the "Session Description Protocol (SDP) Parameters. The references level)" subregistry in the "Session Description Protocol (SDP)
should be updated to point at this RFC as well as the previous Parameters registry. The references should be updated to point at
references. this RFC as well as the previous references.
+-------+--------------+ +---------------------+------------------+
| Type | Mux Category | | SDP Name | Mux Category |
+-------+--------------+ +---------------------+------------------+
| CT | NORMAL | | cat | NORMAL |
| AS | SUM | | keywds | NORMAL |
| RS | NORMAL | | type | NORMAL |
| RR | NORMAL | | type:broadcast | NORMAL |
| TIAS | SPECIAL | | type:H332 | NORMAL |
+-------+--------------+ | type:meeting | NORMAL |
| type:moderated | NORMAL |
| type:test | NORMAL |
| charset | NORMAL |
| charset:iso8895-1 | NORMAL |
| tool | NORMAL |
| ipbcp | NORMAL |
| group | NORMAL |
| ice-lite | NORMAL |
| ice-options | NORMAL |
| bcastversion | NORMAL |
| 3GPP-Integrity-Key | NOT RECOMMENDED |
| 3GPP-SDP-Auth | NOT RECOMMENDED |
| alt-group | NOT RECOMMENDED |
| PSCid | NORMAL |
| bc_service | NORMAL |
| bc_program | NORMAL |
| bc_service_package | NORMAL |
| sescap | NOT RECOMMENDED |
| rtsp-ice-d-m | NOT RECOMMENDED |
+---------------------+------------------+
15.2.2. Table: att-field 15.2.3. Table: att-field (both session and media level)
The following values are to be added to the 'att-field' registry in The following values are to be added to the "att-field (both session
the "Session Description Protocol (SDP) Parameters. The references and media level)" subregistry in the "Session Description Protocol
should be updated to point at this RFC as well as the previous (SDP) Parameters registry. The references should be updated to point
references. at this RFC as well as the previous references.
+-------------------------+-------------------+
| SDP Name | Mux Category |
+-------------------------+-------------------+
| recvonly | NORMAL |
| sendrecv | NORMAL |
| sendonly | NORMAL |
| sdplang | NORMAL |
| lang | NORMAL |
| h248item | SPECIAL |
| sqn | NORMAL |
| cdsc | NORMAL |
| cpar | INHERIT |
| cparmin | SPECIAL |
| cparmax | SPECIAL |
| rtcp-xr | NORMAL |
| maxprate | SPECIAL |
| setup | IDENTICAL |
| connection | IDENTICAL |
| key-mgmt | IDENTICAL |
| source-filter | IDENTICAL |
| inactive | NORMAL |
| fingerprint | TRANSPORT |
| flute-tsi | TBD |
| flute-ch | TBD |
| FEC-declaration | TBD |
| FEC-OTI-extension | TBD |
| content-desc | TBD |
| ice-pwd | TRANSPORT |
| ice-ufrag | TRANSPORT |
| stkmstream | NORMAL |
| qos-mech-send | NORMAL |
| qos-mech-recv | NORMAL |
| csup | NORMAL |
| creq | NORMAL |
| acap | INHERIT |
| tcap | INHERIT |
| 3GPP-QoE-Metrics | NOT RECOMMENDED |
| 3GPP-Asset-Information | NOT RECOMMENDED |
| mbms-mode | NOT RECOMMENDED |
| mbms-repair | NOT RECOMMENDED |
| ike-setup | IDENTICAL |
| psk-fingerprint | IDENTICAL |
| multicast-rtcp | IDENTICAL |
| rmcap | IDENTICAL-PER-PT |
| omcap | NORMAL |
| mfcap | IDENTICAL-PER-PT |
| mscap | INHERIT |
| bcap | INHERIT |
| ccap | IDENTICAL |
| icap | NORMAL |
| 3gpp_sync_info | NORMAL |
| 3gpp_MaxRecvSDUSize | NORMAL |
| etag | NOT RECOMMENDED |
| duplication-delay | NORMAL |
| range | NOT RECOMMENDED |
| control | NOT RECOMMENDED |
| mtag | NOT RECOMMENDED |
| ts-refclk | NORMAL |
| mediaclk | NORMAL |
| calgextmap | NORMAL |
+-------------------------+-------------------+
15.2.4. Table: att-field (media level only)
The following values are to be added to the "att-field (media level
only" registry in the "Session Description Protocol (SDP) Parameters
registry. The references should be updated to point at this RFC as
well as the previous references.
+---------------------------+-------------------+ +---------------------------+-------------------+
| SDP Name | Mux Category | | SDP Name | Mux Category |
+---------------------------+-------------------+ +---------------------------+-------------------+
| cat | NORMAL |
| keywds | NORMAL |
| type | NORMAL |
| type:broadcast | NORMAL |
| type:H332 | NORMAL |
| type:meeting | NORMAL |
| type:moderated | NORMAL |
| type:test | NORMAL |
| charset | NORMAL |
| charset:iso8895-1 | NORMAL |
| tool | NORMAL |
| ipbcp | NORMAL |
| group | NORMAL |
| ice-lite | NORMAL |
| ice-options | NORMAL |
| bcastversion | NORMAL |
| 3GPP-Integrity-Key | NOT RECOMMENDED |
| 3GPP-SDP-Auth | NOT RECOMMENDED |
| alt-group | NOT RECOMMENDED |
| PSCid | NORMAL |
| bc_service | NORMAL |
| bc_program | NORMAL |
| bc_service_package | NORMAL |
| sescap | NOT RECOMMENDED |
| rtsp-ice-d-m | TBD |
| recvonly | NORMAL |
| sendrecv | NORMAL |
| sendonly | NORMAL |
| sdplang | NORMAL |
| lang | NORMAL |
| h248item | SPECIAL |
| sqn | NORMAL |
| cdsc | NORMAL |
| cpar | INHERIT |
| cparmin | SPECIAL |
| cparmax | SPECIAL |
| rtcp-xr | NORMAL |
| maxprate | SPECIAL |
| setup | IDENTICAL |
| connection | IDENTICAL |
| key-mgmt | IDENTICAL |
| source-filter | IDENTICAL |
| inactive | NORMAL |
| fingerprint | TRANSPORT |
| flute-tsi | TBD |
| flute-ch | TBD |
| FEC-declaration | TBD |
| FEC-OTI-extension | TBD |
| content-desc | TBD |
| ice-pwd | TRANSPORT |
| ice-ufrag | TRANSPORT |
| stkmstream | NORMAL |
| qos-mech-send | NORMAL |
| qos-mech-recv | NORMAL |
| csup | NORMAL |
| creq | NORMAL |
| acap | INHERIT |
| tcap | INHERIT |
| 3GPP-QoE-Metrics | NOT RECOMMENDED |
| 3GPP-Asset-Information | NOT RECOMMENDED |
| mbms-mode | NORMAL |
| mbms-repair | NORMAL |
| ike-setup | IDENTICAL |
| psk-fingerprint | IDENTICAL |
| multicast-rtcp | IDENTICAL |
| rmcap | IDENTICAL-PER-PT |
| omcap | NORMAL |
| mfcap | IDENTICAL-PER-PT |
| mscap | INHERIT |
| bcap | INHERIT |
| ccap | IDENTICAL |
| icap | NORMAL |
| 3gpp_sync_info | NORMAL |
| 3gpp_MaxRecvSDUSize | NORMAL |
| etag | TBD |
| duplication-delay | NORMAL |
| range | TBD |
| control | TBD |
| mtag | TBD |
| ts-refclk | NORMAL |
| mediaclk | NORMAL |
| calgextmap | NORMAL |
| ptime | IDENTICAL-PER-PT | | ptime | IDENTICAL-PER-PT |
| orient | NORMAL | | orient | NORMAL |
| orient:portrait | NORMAL | | orient:portrait | NORMAL |
| orient:landscape | NORMAL | | orient:landscape | NORMAL |
| orient:seascape | NORMAL | | orient:seascape | NORMAL |
| framerate | IDENTICAL-PER-PT | | framerate | IDENTICAL-PER-PT |
| quality | NORMAL | | quality | NORMAL |
| rtpmap | IDENTICAL-PER-PT | | rtpmap | IDENTICAL-PER-PT |
| fmtp | IDENTICAL-PER-PT | | fmtp | IDENTICAL-PER-PT |
| rtpred1 | NOT RECOMMENDED | | rtpred1 | NOT RECOMMENDED |
skipping to change at page 70, line 31 skipping to change at page 71, line 38
| T38FaxVersion | NORMAL | | T38FaxVersion | NORMAL |
| T38MaxBitRate | NORMAL | | T38MaxBitRate | NORMAL |
| T38MaxBitRate | NORMAL | | T38MaxBitRate | NORMAL |
| T38FaxTranscodingMMR | NORMAL | | T38FaxTranscodingMMR | NORMAL |
| T38FaxTranscodingJBIG | NORMAL | | T38FaxTranscodingJBIG | NORMAL |
| T38FaxRateManagement | NORMAL | | T38FaxRateManagement | NORMAL |
| T38FaxMaxBuffer | NORMAL | | T38FaxMaxBuffer | NORMAL |
| T38FaxMaxDatagram | NORMAL | | T38FaxMaxDatagram | NORMAL |
| T38FaxUdpEC | NORMAL | | T38FaxUdpEC | NORMAL |
| maxptime | IDENTICAL-PER-PT | | maxptime | IDENTICAL-PER-PT |
| des | NORMAL | | des | NOT RECOMMENDED |
| curr | NORMAL | | curr | NOT RECOMMENDED |
| conf | NORMAL | | 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 | NORMAL |
| aalType | NORMAL | | aalType | NORMAL |
| capability | NORMAL | | capability | NORMAL |
| qosClass | NORMAL | | qosClass | NORMAL |
skipping to change at page 72, line 38 skipping to change at page 73, line 45
| mbms-flowid | NOT RECOMMENDED | | mbms-flowid | NOT RECOMMENDED |
| fec-source-flow | SPECIAL | | fec-source-flow | SPECIAL |
| fec-repair-flow | SPECIAL | | fec-repair-flow | SPECIAL |
| repair-window | SPECIAL | | repair-window | SPECIAL |
| rams-updates | NOT RECOMMENDED | | rams-updates | NOT RECOMMENDED |
| imageattr | IDENTICAL-PER-PT | | imageattr | IDENTICAL-PER-PT |
| cfw-id | NORMAL | | cfw-id | NORMAL |
| portmapping-req | NOT RECOMMENDED | | portmapping-req | NOT RECOMMENDED |
| g.3gpp.cat | NORMAL | | g.3gpp.cat | NORMAL |
| g.3gpp.crs | NORMAL | | g.3gpp.crs | NORMAL |
| ecm-capable-rtp | IDENTICAL-PER-PT | | ecn-capable-rtp | IDENTICAL |
| visited-realm | TRANSPORT | | visited-realm | TRANSPORT |
| secondary-realm | TRANSPORT | | secondary-realm | TRANSPORT |
| omr-s-cksum | NORMAL | | omr-s-cksum | NORMAL |
| omr-m-Cksum | NORMAL | | omr-m-cksum | NORMAL |
| omr-codecs | NORMAL | | omr-codecs | NORMAL |
| omr-codecs | NORMAL | | omr-codecs | NORMAL |
| omr-m-att | NORMAL | | omr-m-att | NORMAL |
| omr-m-bw | NORMAL | | omr-m-bw | NORMAL |
| omr-s-bw | NORMAL | | omr-s-bw | NORMAL |
| msrcp-cema | NORMAL | | msrcp-cema | NORMAL |
| dccp-port | NOT RECOMMENDED | | dccp-port | NOT RECOMMENDED |
| resource | NORMAL | | resource | NORMAL |
| channel | NORMAL | | channel | NORMAL |
| cmid | NORMAL | | cmid | NORMAL |
skipping to change at page 73, line 18 skipping to change at page 74, line 25
| loopback-source | NORMAL | | loopback-source | NORMAL |
| loopback-mirror | NORMAL | | loopback-mirror | NORMAL |
| chatroom | TBD | | chatroom | TBD |
| altc | TRANSPORT | | altc | TRANSPORT |
| T38FaxMaxIFP | NORMAL | | T38FaxMaxIFP | NORMAL |
| T38FaxUdpECDepth | NORMAL | | T38FaxUdpECDepth | NORMAL |
| T38FaxUdpFECMaxSpan | NORMAL | | T38FaxUdpFECMaxSpan | NORMAL |
| T38ModemType | NORMAL | | T38ModemType | NORMAL |
| cs-correlation | NORMAL | | cs-correlation | NORMAL |
| rtcpidms | NORMAL | | rtcpidms | NORMAL |
| cname | NORMAL |
| previous-ssrc | NORMAL |
| fmtp | IDENTICAL-PER-PT |
+---------------------------+-------------------+ +---------------------------+-------------------+
15.2.3. Table: content SDP Parameters 15.2.5. Table: att-field (source level)
The following values are to be added to the 'content SDP Parameters' The following values are to be added to the "att-field (source
registry in the "Session Description Protocol (SDP) Parameters. The level)" registry in the "Session Description Protocol (SDP)
references should be updated to point at this RFC as well as the Parameters registry. The references should be updated to point at
previous references. this RFC as well as the previous references.
+----------------+-------------------+
| SDP Name | Mux Category |
+----------------+-------------------+
| cname | NORMAL |
| previous-ssrc | NORMAL |
| fmtp | IDENTICAL-PER-PT |
| ts-refclk | NORMAL |
| mediaclk | NORMAL |
+----------------+-------------------+
15.2.6. Table: content SDP Parameters
The following values are to be added to the "content SDP Parameters"
subregistry in the "Session Description Protocol (SDP) Parameters
registry. The references should be updated to point at this RFC as
well as the previous references.
+----------+--------------+ +----------+--------------+
| SDP Name | Mux Category | | SDP Name | Mux Category |
+----------+--------------+ +----------+--------------+
| slides | NORMAL | | slides | NORMAL |
| speaker | NORMAL | | speaker | NORMAL |
| sl | NORMAL | | sl | NORMAL |
| main | NORMAL | | main | NORMAL |
| alt | NORMAL | | alt | NORMAL |
+----------+--------------+ +----------+--------------+
15.2.4. Table: Semantics for the 'group' SDP Attribute 15.2.7. Table: Semantics for the 'group' SDP Attribute
The following values are to be added to the Semantics for the "group" The following values are to be added to the "Semantics for the
SDP Attribute registry in the "Session Description Protocol (SDP) "group" SDP Attribute" subregistry in the "Session Description
Parameters. The references should be updated to point at this RFC as Protocol (SDP) Parameters registry. The references should be updated
well as the previous references. to point at this RFC as well as the previous references.
+---------+------------------+ +---------+------------------+
| Token | Mux Category | | Token | Mux Category |
+---------+------------------+ +---------+------------------+
| LS | NORMAL | | LS | NORMAL |
| FID | NORMAL | | FID | NORMAL |
| SRF | NORMAL | | SRF | NORMAL |
| ANAT | NOT RECOMMENDED | | ANAT | NOT RECOMMENDED |
| FEC | NORMAL | | FEC | NORMAL |
| FEC-FR | NORMAL | | FEC-FR | NORMAL |
| CS | NORMAL | | CS | NORMAL |
| DDP | NORMAL | | DDP | NORMAL |
| DUP | NORMAL | | DUP | NORMAL |
+---------+------------------+ +---------+------------------+
15.2.5. Table: 'rtcp-fb' Attribute Values 15.2.8. Table: 'rtcp-fb' Attribute Values
The following values are to be added to the " 'rtcp-fb' Attribute The following values are to be added to the " 'rtcp-fb' Attribute
Values" registry in the "Session Description Protocol (SDP) Values" subregistry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as Parameters registry. The references should be updated to point at
well as the previous references. this RFC as well as the previous references.
+------------+-------------------+ +------------+-------------------+
| Value Name | Mux Category | | Value Name | Mux Category |
+------------+-------------------+ +------------+-------------------+
| ack | IDENTICAL-PER-PT | | ack | IDENTICAL-PER-PT |
| app | SPECIAL | | app | SPECIAL |
| ccm | IDENTICAL-PER-PT | | ccm | IDENTICAL-PER-PT |
| nack | IDENTICAL-PER-PT | | nack | IDENTICAL-PER-PT |
| trr-int | IDENTICAL-PER-PT | | trr-int | IDENTICAL-PER-PT |
+------------+-------------------+ +------------+-------------------+
15.2.6. Table: 'ack' and 'nack' Attribute Values 15.2.9. Table: 'ack' and 'nack' Attribute Values
The following values are to be added to the " 'ack' and 'nack' The following values are to be added to the " 'ack' and 'nack'
Attribute Values" registry in the "Session Description Protocol (SDP) Attribute Values" subregistry in the "Session Description Protocol
Parameters. The references should be updated to point at this RFC as (SDP) Parameters" registry. The references should be updated to
well as the previous references. point at this RFC as well as the previous references.
+------------+-------------------+ +------------+-------------------+
| Value Name | Mux Category | | Value Name | Mux Category |
+------------+-------------------+ +------------+-------------------+
| sli | IDENTICAL-PER-PT | | sli | IDENTICAL-PER-PT |
| pli | IDENTICAL-PER-PT | | pli | IDENTICAL-PER-PT |
| rpsi | IDENTICAL-PER-PT | | rpsi | IDENTICAL-PER-PT |
| app | IDENTICAL-PER-PT | | app | IDENTICAL-PER-PT |
| rai | IDENTICAL-PER-PT | | rai | IDENTICAL-PER-PT |
| tllei | IDENTICAL-PER-PT | | tllei | IDENTICAL-PER-PT |
| pslei | IDENTICAL-PER-PT | | pslei | IDENTICAL-PER-PT |
| ecn | IDENTICAL-PER-PT | | ecn | IDENTICAL |
+------------+-------------------+ +------------+-------------------+
15.2.7. Table: 'depend' SDP Attribute Values 15.2.10. Table: 'depend' SDP Attribute Values
The following values are to be added to the " 'depend' SDP Attribute The following values are to be added to the " 'depend' SDP Attribute
Values" registry in the "Session Description Protocol (SDP) Values" subregistry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as Parameters registry. The references should be updated to point at
well as the previous references. this RFC as well as the previous references.
+-------+--------------+ +-------+-------------------+
| Token | Mux Category | | Token | Mux Category |
+-------+--------------+ +-------+-------------------+
| lay | NORMAL | | lay | IDENTICAL-PER-PT |
| mdc | NORMAL | | mdc | IDENTICAL-PER-PT |
+-------+--------------+ +-------+-------------------+
15.2.8. Table: 'cs-correlation' Attribute Values 15.2.11. Table: 'cs-correlation' Attribute Values
The following values are to be added to the " 'cs-correlation' The following values are to be added to the " "cs-correlation"
Attribute Values" registry in the "Session Description Protocol (SDP) Attribute Values" subregistry in the "Session Description Protocol
Parameters. The references should be updated to point at this RFC as (SDP) Parameters registry. The references should be updated to point
well as the previous references. at this RFC as well as the previous references.
+-----------+--------------+ +-----------+--------------+
| Token | Mux Category | | Value | Mux Category |
+-----------+--------------+ +-----------+--------------+
| callerid | NORMAL | | callerid | NORMAL |
| uuie | NORMAL | | uuie | NORMAL |
| dtmf | NORMAL | | dtmf | NORMAL |
| external | NORMAL | | external | NORMAL |
+-----------+--------------+ +-----------+--------------+
15.2.9. Table: Semantics for the 'ssrc-group' SDP Attribute 15.2.12. Table: Semantics for the 'ssrc-group' SDP Attribute
The following values are to be added to the Semantics for the " The following values are to be added to the Semantics for the
'ssrc-group' SDP Attribute" registry in the "Session Description "Semantics for the "ssrc-group" SDP Attribute" subregistry in the
Protocol (SDP) Parameters. The references should be updated to point "Session Description Protocol (SDP) Parameters registry. The
at this RFC as well as the previous references. references should be updated to point at this RFC as well as the
previous references.
+---------+--------------+ +---------+--------------+
| Token | Mux Category | | Token | Mux Category |
+---------+--------------+ +---------+--------------+
| FID | NORMAL | | FID | NORMAL |
| FEC | NORMAL | | FEC | NORMAL |
| FEC-FR | NORMAL | | FEC-FR | NORMAL |
| DUP | NORMAL | | DUP | NORMAL |
+---------+--------------+ +---------+--------------+
15.2.10. Table: SDP/RTSP key management protocol identifiers 15.2.13. Table: SDP/RTSP key management protocol identifiers
The following values are to be added to the "SDP/RTSP key management The following values are to be added to the "SDP/RTSP key management
protocol identifiers" registry in the "Session Description Protocol protocol identifiers" subregistry in the "Session Description
(SDP) Parameters. The references should be updated to point at this Protocol (SDP) Parameters registry. The references should be updated
RFC as well as the previous references. to point at this RFC as well as the previous references.
+------------+--------------+ +------------+--------------+
| Value Name | Mux Category | | Value Name | Mux Category |
+------------+--------------+ +------------+--------------+
| mikey | IDENTICAL | | mikey | IDENTICAL |
+------------+--------------+ +------------+--------------+
15.2.11. Table: Codec Control Messages 15.2.14. Table: Codec Control Messages
The following values are to be added to the "Codec Control Messages" The following values are to be added to the "Codec Control Messages"
registry in the "Session Description Protocol (SDP) Parameters. The subregistry in the "Session Description Protocol (SDP) Parameters
references should be updated to point at this RFC as well as the registry. The references should be updated to point at this RFC as
previous references. well as the previous references.
+------------+-------------------+ +------------+-------------------+
| Value Name | Mux Category | | Value Name | Mux Category |
+------------+-------------------+ +------------+-------------------+
| fir | IDENTICAL-PER-PT | | fir | IDENTICAL-PER-PT |
| tmmbr | IDENTICAL-PER-PT | | tmmbr | IDENTICAL-PER-PT |
| tstr | IDENTICAL-PER-PT | | tstr | IDENTICAL-PER-PT |
| vbcm | IDENTICAL-PER-PT | | vbcm | IDENTICAL-PER-PT |
+------------+-------------------+ +------------+-------------------+
15.2.12. Table: QoS Mechanism Tokens 15.2.15. Table: QoS Mechanism Tokens
The following values are to be added to the "QoS Mechanism Tokens" The following values are to be added to the "QoS Mechanism Tokens"
registry in the "Session Description Protocol (SDP) Parameters. The subregistry in the "Session Description Protocol (SDP) Parameters
references should be updated to point at this RFC as well as the registry. The references should be updated to point at this RFC as
previous references. well as the previous references.
+---------------+--------------+ +---------------+--------------+
| QoS Mechanism | Mux Category | | QoS Mechanism | Mux Category |
+---------------+--------------+ +---------------+--------------+
| rsvp | NORMAL | | rsvp | NORMAL |
| nsis | NORMAL | | nsis | NORMAL |
+---------------+--------------+ +---------------+--------------+
15.2.13. Table: SDP Capability Negotiation Option Tags 15.2.16. Table: SDP Capability Negotiation Option Tags
The following values are to be added to the "SDP Capability The following values are to be added to the "SDP Capability
Negotiation Option Tags" Registry in the "Session Description Negotiation Option Tags" subregistry in the "Session Description
Protocol (SDP) Parameters. The references should be updated to point Protocol (SDP) Parameters registry. The references should be updated
at this RFC as well as the previous references. to point at this RFC as well as the previous references.
+---------------+--------------+ +---------------+--------------+
| QoS Mechanism | Mux Category | | QoS Mechanism | Mux Category |
+---------------+--------------+ +---------------+--------------+
| cap-v0 | NORMAL | | cap-v0 | NORMAL |
| med-v0 | NORMAL | | med-v0 | NORMAL |
| bcap-v0 | NORMAL | | bcap-v0 | NORMAL |
| ccap-v0 | NORMAL | | ccap-v0 | NORMAL |
| icap-v0 | NORMAL | | icap-v0 | NORMAL |
+---------------+--------------+ +---------------+--------------+
15.2.14. Table: Timestamp Reference Clock Source Parameters 15.2.17. Table: Timestamp Reference Clock Source Parameters
The following values are to be added to the "Timestamp Reference The following values are to be added to the "Timestamp Reference
Clock Source Parameters" Registry in the "Session Description Clock Source Parameters" subregistry in the "Session Description
Protocol (SDP) Parameters. The references should be updated to point Protocol (SDP) Parameters registry. The references should be updated
at this RFC as well as the previous references. to point at this RFC as well as the previous references.
+----------+--------------+ +----------+--------------+
| Name | Mux Category | | Name | Mux Category |
+----------+--------------+ +----------+--------------+
| ntp | NORMAL | | ntp | NORMAL |
| ptp | NORMAL | | ptp | NORMAL |
| gps | NORMAL | | gps | NORMAL |
| gal | NORMAL | | gal | NORMAL |
| glonass | NORMAL | | glonass | NORMAL |
| local | NORMAL | | local | NORMAL |
| private | NORMAL | | private | NORMAL |
+----------+--------------+ +----------+--------------+
15.2.15. Table: Media Clock Source Parameters 15.2.18. Table: Media Clock Source Parameters
The following values are to be added to the "Media Clock Source The following values are to be added to the "Media Clock Source
Parameters" Registry in the "Session Description Protocol (SDP) Parameters" subegistry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as Parameters registry. The references should be updated to point at
well as the previous references. this RFC as well as the previous references.
+-----------+--------------+ +-----------+--------------+
| Name | Mux Category | | Name | Mux Category |
+-----------+--------------+ +-----------+--------------+
| sender | NORMAL | | sender | NORMAL |
| direct | NORMAL | | direct | NORMAL |
| IEEE1722 | NORMAL | | IEEE1722 | NORMAL |
+-----------+--------------+ +-----------+--------------+
16. Security Considerations 16. Security Considerations
skipping to change at page 78, line 27 skipping to change at page 79, line 44
This document does not add any new security considerations beyond the This document does not add any new security considerations beyond the
existing considerations in the RFC for protocols that are being existing considerations in the RFC for protocols that are being
multiplexed together. multiplexed together.
The ways that SRTP streams are keyed is not believed to create any The ways that SRTP streams are keyed is not believed to create any
two-time pad vulnerability for the currently defined SRTP keying two-time pad vulnerability for the currently defined SRTP keying
mechanism. mechanism.
17. Acknowledgments 17. Acknowledgments
I would like to thank Cullen Jennings for suggesting the categories, I would like to thank Cullen Jennings and Flemming Andreasen for
contributing text and reviewing the draft. I would also link to suggesting the categories, contributing text and reviewing the draft.
thank Magnus, Christer, Jonathan Lennox, Bo Burman, and Dan on I would also link to thank Magnus Westerlund, Christer Holmberg,
suggesting structural changes helping improve the document Jonathan Lennox, Bo Burman, and Dan on suggesting structural changes
readability. helping improve the document readability.
I would like also to thank following experts on their inputs and I would like also to thank following experts on their inputs and
reviews as listed - Flemming Andreasen(5.20,5.28,5.29,15), Rohan reviews as listed - Flemming Andreasen(5.20,5.28,5.29,14), Rohan
Mahy(5.45), Eric Burger(5.22),Christian Huitema(5.13), Christer Mahy(5.45), Eric Burger(5.22),Christian Huitema(5.13), Christer
Holmberg(5.17,5.22,5.40,5.41), Richard Ejzak (5.36,5.42,5.43,5.44), Holmberg(5.17,5.22,5.40,5.41), Richard Ejzak (5.36,5.42,5.43,5.44),
Colin Perkins(5.7,5.8), Magnus westerlund(5.2,5.3,5.9,5.26, Colin Perkins(5.7,5.8), Magnus westerlund(5.2,5.3,5.9,5.26,
5.27,6.1,6.2,6.3,8.3,7), Roni Evens(5.12,5.27,8.4), Subha 5.27,6.1,6.2,6.3,8.3,7), Roni Evens(5.12,5.27,8.4), Subha
Dhesikan(5.5,12.1,14), Dan Wing(5.6,5.11,5.30,5.34,5.37), Ali C Dhesikan(5.5,12.1,14), Dan Wing(5.6,5.11,5.30,5.34,5.37), Ali C
Begen(5.1,5.16,5.18,5.21,5.33,8.2,8.4,13.1), Bo Burman (7.2,7.6), Begen(5.1,5.16,5.18,5.21,5.33,8.2,8.4,13.1), Bo Burman (7.2,7.6),
Charles Eckel(5.14,5.23,5.24,9.1,8.5), Paul Kyzivat(5.24), Ian Charles Eckel(5.14,5.23,5.24,9.1,8.5), Paul Kyzivat(5.24), Ian
Johansson(5.15), Saravanan Shanmugham(5.10), Paul E Jones(5.25), Johansson(5.15), Saravanan Shanmugham(5.10), Paul E Jones(5.25),
Rajesh Kumar(5.39), Jonathan Lennox(5.31,5,14,11.1), Mo Rajesh Kumar(5.39), Jonathan Lennox(5.31,5,14,11.1), Mo
Zanaty(5.4,5.19,8.1,8.3,8.5,12.1), Christian Huitema (5.13), Qin Wu Zanaty(5.4,5.19,8.1,8.3,8.5,12.1), Christian Huitema (5.13), Qin Wu
(5.38 PM-Dir review). (5.38 PM-Dir review).
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-03
o More re-work on the IANA section.
o Clean ups preparing for the last call.
Changes from draft-ietf-mmusic-sdp-mux-attributes-02 Changes from draft-ietf-mmusic-sdp-mux-attributes-02
o Incorporated suggestions from Flemming on Capability Negotiation. o Incorporated suggestions from Flemming on Capability Negotiation.
o Closed open issues from IETF90 o Closed open issues from IETF90
o Added IANA section to list the categories for all the SDP o Added IANA section to list the categories for all the SDP
attributes anlayzed attributes anlayzed
o Lots of cleanup o Lots of cleanup
o Reformatted Refernces section to use short-form notation o Reformatted Refernces section to use short-form notation
skipping to change at page 81, line 22 skipping to change at page 82, line 44
Holmberg, C., Alvestrand, H., and C. Jennings, Holmberg, C., Alvestrand, H., and C. Jennings,
"Negotiating Media Multiplexing Using the Session "Negotiating Media Multiplexing Using the Session
Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle- Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-
negotiation-12 (work in progress), October 2014. negotiation-12 (work in progress), October 2014.
[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] "S 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] [ITU-T-REC.Q1970]
"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]
"TISPAN - IMS based ITPV Stage 3 specification.",
<http://www.in2eps.com/etispan/
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",
<http://www.3gpp.org/ftp/Specs/html-info/24182.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24182.htm>.
[R3GPPTS24.183] [R3GPPTS24.183]
"IP Multimedia Subsystem (IMS) Customized Ringing Signal "IP Multimedia Subsystem (IMS) Customized Ringing Signal
(CRS); Protocol specification", (CRS); Protocol specification",
<http://www.3gpp.org/ftp/Specs/html-info/24183.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24183.htm>.
skipping to change at page 85, line 41 skipping to change at page 87, line 17
June 2011. June 2011.
[RFC6285] Ver Steeg, B., Begen, A., Van Caenegem, T., and Z. Vax, [RFC6285] Ver Steeg, B., Begen, A., Van Caenegem, T., and Z. Vax,
"Unicast-Based Rapid Acquisition of Multicast RTP "Unicast-Based Rapid Acquisition of Multicast RTP
Sessions", RFC 6285, June 2011. Sessions", RFC 6285, June 2011.
[RFC6364] Begen, A., "Session Description Protocol Elements for the [RFC6364] Begen, A., "Session Description Protocol Elements for the
Forward Error Correction (FEC) Framework", RFC 6364, Forward Error Correction (FEC) Framework", RFC 6364,
October 2011. October 2011.
[RFC6489] Huston, G., Michaelson, G., and S. Kent, "Certification
Authority (CA) Key Rollover in the Resource Public Key
Infrastructure (RPKI)", BCP 174, RFC 6489, February 2012.
[RFC6642] Wu, Q., Xia, F., and R. Even, "RTP Control Protocol (RTCP) [RFC6642] Wu, Q., Xia, F., and R. Even, "RTP Control Protocol (RTCP)
Extension for a Third-Party Loss Report", RFC 6642, June Extension for a Third-Party Loss Report", RFC 6642, June
2012. 2012.
[RFC6679] Westerlund, M., Johansson, I., Perkins, C., O'Hanlon, P., [RFC6679] Westerlund, M., Johansson, I., Perkins, C., O'Hanlon, P.,
and K. Carlberg, "Explicit Congestion Notification (ECN) and K. Carlberg, "Explicit Congestion Notification (ECN)
for RTP over UDP", RFC 6679, August 2012. for RTP over UDP", RFC 6679, August 2012.
[RFC6714] Holmberg, C., Blau, S., and E. Burger, "Connection [RFC6714] Holmberg, C., Blau, S., and E. Burger, "Connection
Establishment for Media Anchoring (CEMA) for the Message Establishment for Media Anchoring (CEMA) for the Message
Session Relay Protocol (MSRP)", RFC 6714, August 2012. Session Relay Protocol (MSRP)", RFC 6714, August 2012.
[RFC6773] Phelan, T., Fairhurst, G., and C. Perkins, "DCCP-UDP: A [RFC6773] Phelan, T., Fairhurst, G., and C. Perkins, "DCCP-UDP: A
Datagram Congestion Control Protocol UDP Encapsulation for Datagram Congestion Control Protocol UDP Encapsulation for
NAT Traversal", RFC 6773, November 2012. NAT Traversal", RFC 6773, November 2012.
[RFC6787] Burnett, D. and S. Shanmugham, "Media Resource Control [RFC6787] Burnett, D. and S. Shanmugham, "Media Resource Control
Protocol Version 2 (MRCPv2)", RFC 6787, November 2012. Protocol Version 2 (MRCPv2)", RFC 6787, November 2012.
[RFC6849] Kaplan, H., Hedayat, K., Venna, N., Jones, P., and N.
Stratton, "An Extension to the Session Description
Protocol (SDP) and Real-time Transport Protocol (RTP) for
Media Loopback", RFC 6849, February 2013.
[RFC6871] Gilman, R., Even, R., and F. Andreasen, "Session [RFC6871] Gilman, R., Even, R., and F. Andreasen, "Session
Description Protocol (SDP) Media Capabilities Description Protocol (SDP) Media Capabilities
Negotiation", RFC 6871, February 2013. Negotiation", RFC 6871, February 2013.
[RFC6947] Boucadair, M., Kaplan, H., Gilman, R., and S. [RFC6947] Boucadair, M., Kaplan, H., Gilman, R., and S.
Veikkolainen, "The Session Description Protocol (SDP) Veikkolainen, "The Session Description Protocol (SDP)
Alternate Connectivity (ALTC) Attribute", RFC 6947, May Alternate Connectivity (ALTC) Attribute", RFC 6947, May
2013. 2013.
[RFC7006] Garcia-Martin, M., Veikkolainen, S., and R. Gilman, [RFC7006] Garcia-Martin, M., Veikkolainen, S., and R. Gilman,
 End of changes. 161 change blocks. 
557 lines changed or deleted 663 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/