draft-ietf-mmusic-sdp-mux-attributes-02.txt   draft-ietf-mmusic-sdp-mux-attributes-03.txt 
Network Working Group S. Nandakumar Network Working Group S. Nandakumar
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track July 03, 2014 Intended status: Standards Track October 20, 2014
Expires: January 4, 2015 Expires: April 23, 2015
A Framework for SDP Attributes when Multiplexing A Framework for SDP Attributes when Multiplexing
draft-ietf-mmusic-sdp-mux-attributes-02 draft-ietf-mmusic-sdp-mux-attributes-03
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
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 4, 2015. This Internet-Draft will expire on April 23, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 6 4. SDP Attribute Analysis Framework . . . . . . . . . . . . . . 6
4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 6 4.1. Category: NORMAL . . . . . . . . . . . . . . . . . . . . 7
4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 7 4.2. Category: NOT RECOMMENDED . . . . . . . . . . . . . . . . 7
4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 7 4.3. Category: IDENTICAL . . . . . . . . . . . . . . . . . . . 8
4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 8 4.4. Category: SUM . . . . . . . . . . . . . . . . . . . . . . 8
4.5. Category: TRANSPORT . . . . . . . . . . . . . . . . . . . 8 4.5. Category: TRANSPORT . . . . . . . . . . . . . . . . . . . 9
4.6. Category: INHERIT . . . . . . . . . . . . . . . . . . . . 9 4.6. Category: INHERIT . . . . . . . . . . . . . . . . . . . . 10
4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 10 4.7. Category: IDENTICAL-PER-PT . . . . . . . . . . . . . . . 10
4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 10 4.8. Category: SPECIAL . . . . . . . . . . . . . . . . . . . . 11
4.9. Category: TBD . . . . . . . . . . . . . . . . . . . . . . 11
5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 11 5. Analysis of Existing Attributes . . . . . . . . . . . . . . . 11
5.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 11 5.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 12
5.2. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 12 5.2. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 13
5.3. RFC5761 - Multiplexing RTP and RTCP . . . . . . . . . . . 13 5.3. RFC5761 - Multiplexing RTP and RTCP . . . . . . . . . . . 14
5.4. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 13 5.4. RFC3312 - Integration of Resource Management and (SIP) . 14
5.5. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 13 5.5. RFC4574 - SDP Label Attribute . . . . . . . . . . . . . . 15
5.6. RFC4568 - SDP Security Descriptions . . . . . . . . . . . 14 5.6. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 15
5.7. RFC5762 - RTP over DCCP . . . . . . . . . . . . . . . . . 14 5.7. RFC4568 - SDP Security Descriptions . . . . . . . . . . . 16
5.8. RFC6773 - DCCP-UDP Encapsulation . . . . . . . . . . . . 15 5.8. RFC5762 - RTP over DCCP . . . . . . . . . . . . . . . . . 16
5.9. RFC5506 - Reduced-Size RTCP in RTP Profile . . . . . . . 16 5.9. RFC6773 - DCCP-UDP Encapsulation . . . . . . . . . . . . 17
5.10. RFC6787 - Media Resource Control Protocol Version 2 . . . 16 5.10. RFC5506 - Reduced-Size RTCP in RTP Profile . . . . . . . 18
5.11. RFC5245 - Interactive Connectivity Establishment (ICE) . 17 5.11. RFC6787 - Media Resource Control Protocol Version 2 . . . 18
5.12. RFC5285 - RTP Header Extensions . . . . . . . . . . . . . 18 5.12. RFC5245 - Interactive Connectivity Establishment (ICE) . 19
5.13. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 19 5.13. RFC5285 - RTP Header Extensions . . . . . . . . . . . . . 20
5.14. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 19 5.14. RFC3605 - RTCP attribute in SDP . . . . . . . . . . . . . 21
5.15. RFC6236 - Image Attributes in SDP . . . . . . . . . . . . 20 5.15. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 21
5.16. RFC6285 - Rapid Acquisition of Multicast RTP Sessions . . 21 5.16. RFC7273 - RTP Clock Source Signalling . . . . . . . . . . 22
5.17. RFC6230 - Media Control Channel Framework . . . . . . . . 21 5.17. RFC6236 - Image Attributes in SDP . . . . . . . . . . . . 23
5.18. RFC6364 - SDP Elements for FEC Framework . . . . . . . . 22 5.18. RFC7197 - Duplication Delay Attribute in SDP . . . . . . 23
5.19. RFC4796 - Content Attribute . . . . . . . . . . . . . . . 22 5.19. RFC7226 - RTCP XR Blocks for MOS Metric Reporting . . . 23
5.20. RFC3407 - SDP Simple Capability Declaration . . . . . . . 23 5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions . . 24
5.21. RFC6284 - Port Mapping between Unicast and Multicast RTP 5.21. RFC6230 - Media Control Channel Framework . . . . . . . . 24
Sessions . . . . . . . . . . . . . . . . . . . . . . . . 23 5.22. RFC6364 - SDP Elements for FEC Framework . . . . . . . . 25
5.22. RFC6714 - MSRP-CEMA . . . . . . . . . . . . . . . . . . . 24 5.23. RFC4796 - Content Attribute . . . . . . . . . . . . . . . 25
5.23. RFC4583 - SDP Format for BFCP Streams . . . . . . . . . . 24 5.24. RFC3407 - SDP Simple Capability Declaration . . . . . . . 25
5.24. RFC5547 - SDP Offer/Answer for File Transfer . . . . . . 25 5.25. RFC6284 - Port Mapping between Unicast and Multicast RTP
5.25. RFC6489 - SDP and RTP Media Loopback Extension . . . . . 25 Sessions . . . . . . . . . . . . . . . . . . . . . . . . 26
5.26. RFC5760 - RTCP with Unicast Feedback . . . . . . . . . . 26 5.26. RFC6714 - MSRP-CEMA . . . . . . . . . . . . . . . . . . . 26
5.27. RFC3611 - RTCP XR . . . . . . . . . . . . . . . . . . . . 26 5.27. RFC4583 - SDP Format for BFCP Streams . . . . . . . . . . 27
5.28. RFC5939 - SDP Capability Negotiation . . . . . . . . . . 27 5.28. RFC5547 - SDP Offer/Answer for File Transfer . . . . . . 27
5.29. RFC6871- SDP Media Capabilities Negotiation . . . . . . . 27 5.29. RFC6489 - SDP and RTP Media Loopback Extension . . . . . 28
5.30. RFC4567 - Key Management Extensions for SDP and RTSP . . 28 5.30. RFC5760 - RTCP with Unicast Feedback . . . . . . . . . . 28
5.31. RFC4572 - Comedia over TLS in SDP . . . . . . . . . . . . 28 5.31. RFC3611 - RTCP XR . . . . . . . . . . . . . . . . . . . . 29
5.32. RFC4570 - SDP Source Filters . . . . . . . . . . . . . . 29 5.32. RFC5939 - SDP Capability Negotiation . . . . . . . . . . 29
5.33. RFC6128 - RTCP Port for Multicast Sessions . . . . . . . 29 5.33. RFC6871- SDP Media Capabilities Negotiation . . . . . . . 30
5.34. RFC6189 - ZRTP . . . . . . . . . . . . . . . . . . . . . 30 5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP . . 31
5.35. RFC4145 - Connection-Oriented Media . . . . . . . . . . . 31 5.35. RFC4567 - Key Management Extensions for SDP and RTSP . . 32
5.36. RFC5159 - OMA BCAST SDP Attributes . . . . . . . . . . . 31 5.36. RFC4572 - Comedia over TLS in SDP . . . . . . . . . . . . 33
5.37. RFC6193 - Media Description for IKE in SDP . . . . . . . 32 5.37. RFC4570 - SDP Source Filters . . . . . . . . . . . . . . 33
5.38. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 33 5.38. RFC6128 - RTCP Port for Multicast Sessions . . . . . . . 34
5.39. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 35 5.39. RFC6189 - ZRTP . . . . . . . . . . . . . . . . . . . . . 34
5.40. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 36 5.40. RFC4145 - Connection-Oriented Media . . . . . . . . . . . 35
5.41. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 37 5.41. RFC6947 - The SDP ALTC Attribute . . . . . . . . . . . . 35
5.42. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 37 5.42. RFC7195 - SDP Extension for Circuit Switched Bearers
5.43. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 38 in PSTN . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.44. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 39 5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP) . . 36
5.45. RFC4975 - The Message Session Relay Protocol . . . . . . 40 5.44. RFC5159 - OMA BCAST SDP Attributes . . . . . . . . . . . 37
5.46. Historical . . . . . . . . . . . . . . . . . . . . . . . 41 5.45. RFC6193 - Media Description for IKE in SDP . . . . . . . 37
6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 42 5.46. RFC6064 - SDP and RTSP Extensions for 3GPP . . . . . . . 38
6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 42 5.47. RFC3108 - ATM SDP . . . . . . . . . . . . . . . . . . . . 41
6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 42 5.48. 3GPP TS 26.114 . . . . . . . . . . . . . . . . . . . . . 42
6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 43 5.49. 3GPP TS 24.182 . . . . . . . . . . . . . . . . . . . . . 43
7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 44 5.50. 3GPP TS 24.183 . . . . . . . . . . . . . . . . . . . . . 43
7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 44 5.51. 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . 43
7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 45 5.52. ITU T.38 . . . . . . . . . . . . . . . . . . . . . . . . 44
7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 45 5.53. ITU-T-REC.Q1970 . . . . . . . . . . . . . . . . . . . . . 45
7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 45 5.54. ITU-T H.248.15 . . . . . . . . . . . . . . . . . . . . . 46
7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 46 5.55. RFC4975 - The Message Session Relay Protocol . . . . . . 46
7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 46 5.56. Historical . . . . . . . . . . . . . . . . . . . . . . . 47
8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 47
8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 47
8.2. RFC3524 - Mapping Media Streams to Resource Reservation
Flows . . . . . . . . . . . . . . . . . . . . . . . . . . 47
8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 48
8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 48
8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 49
9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 49
9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 49
10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 50
10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 50
11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 50
11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 50
12. content Atribute Analysis . . . . . . . . . . . . . . . . . . 50 6. bwtype Attribute Analysis . . . . . . . . . . . . . . . . . . 48
12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 50 6.1. RFC4566 - SDP: Session Description Protocol . . . . . . . 48
13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 51 6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth . . 48
13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 51 6.3. RFC3890 - Bandwidth Modifier for SDP . . . . . . . . . . 49
14. Multiplexing Media Streams and DSCP Markings . . . . . . . . 52 7. rtcp-fb Attribute Analysis . . . . . . . . . . . . . . . . . 50
14.1. Option A . . . . . . . . . . . . . . . . . . . . . . . . 52 7.1. RFC4585 - RTP/AVPF . . . . . . . . . . . . . . . . . . . 50
14.2. Option B . . . . . . . . . . . . . . . . . . . . . . . . 53 7.2. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 51
15. Multiplexing Considerations for Encapsulating Attributes . . 53 7.3. RFC6285 - Unicast-Based RAMS . . . . . . . . . . . . . . 52
15.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 53 7.4. RFC6679 - ECN for RTP over UDP/IP . . . . . . . . . . . . 52
15.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 54 7.5. RFC6642 - Third-Party Loss Report . . . . . . . . . . . . 53
15.2.1. Recommendations . . . . . . . . . . . . . . . . . . 54 7.6. RFC5104 - Codec Control Messages in AVPF . . . . . . . . 54
15.2.1.1. Recommendation-1: Transport Capability Analysis 55 8. group Attribute Analysis . . . . . . . . . . . . . . . . . . 54
15.2.1.2. Recommendation-2: Attribute Capability Analysis 55 8.1. RFC5888 - SDP Grouping Framework . . . . . . . . . . . . 54
15.2.1.3. Recommendation-3: Sescap Attribute Analysis . . 56 8.2. RFC3524 - Mapping Media Streams to Resource
15.2.1.4. Recommendation-4: Capability Extension Reservation Flows . . . . . . . . . . . . . . . . . . . . 55
Attributes . . . . . . . . . . . . . . . . . . . 56 8.3. RFC4091 - ANAT Semantics . . . . . . . . . . . . . . . . 55
15.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 56 8.4. RFC5956 - FEC Grouping Semantics in SDP . . . . . . . . . 55
15.3.1. Recommendation-5: Attribute Capability Under Shared 8.5. RFC5583 - Signaling Media Decoding Dependency in SDP . . 56
Payload Type . . . . . . . . . . . . . . . . . . . . 56 8.6. RFC7104 - Duplication Grouping Semantics in the SDP . . 56
15.4. Recommendation-6: Offer/Answer Negotiation Expectations 57 9. ssrc-group Attribute Analysis . . . . . . . . . . . . . . . . 57
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 59 9.1. RFC5576 - Source-Specific SDP Attributes . . . . . . . . 57
17. Security Considerations . . . . . . . . . . . . . . . . . . . 60 9.2. RFC7104 - Duplication Grouping Semantics in the SDP . . . 57
18. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60 10. QoS Mechanism Token Analysis . . . . . . . . . . . . . . . . 57
19. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 61 10.1. RFC5432 - QoS Mechanism Selection in SDP . . . . . . . . 57
20. References . . . . . . . . . . . . . . . . . . . . . . . . . 62 11. k= Attribute Analysis . . . . . . . . . . . . . . . . . . . . 58
20.1. Normative References . . . . . . . . . . . . . . . . . . 62 11.1. RFC4566 SDP: Session Description Protocol . . . . . . . 58
20.2. Informative References . . . . . . . . . . . . . . . . . 62 12. content Atribute Analysis . . . . . . . . . . . . . . . . . . 58
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 68 12.1. RFC4796 . . . . . . . . . . . . . . . . . . . . . . . . 58
13. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 59
13.1. RFC5109 - RTP Payload Format for Generic FEC . . . . . . 59
14. Multiplexing Considerations for Encapsulating
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 59
14.1. RFC3407 - cpar Attribute Analysis . . . . . . . . . . . 60
14.2. RFC5939 Analysis . . . . . . . . . . . . . . . . . . . . 60
14.2.1. Recommendation - Procedures for Potential
Configuration Pairing . . . . . . . . . . . . . . . 61
14.2.1.1. Example: Transport Capability Multiplexing . . . 62
14.2.1.2. Example: Attribute Capability Multiplexing . . . 63
14.3. RFC6871 Analysis . . . . . . . . . . . . . . . . . . . . 64
14.3.1. Recommendation: Dealing with Payload Type Numbers . 64
14.3.1.1. Example: Attribute Capability Under Shared
Payload Type . . . . . . . . . . . . . . . . . . 64
14.3.2. Recommendation: Dealing with Latent Configurations . 65
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66
15.1. New Column 'Mux Category' . . . . . . . . . . . . . . . 66
15.2. 'Mux Category' values for SDP Registries . . . . . . . . 67
15.2.1. Table: SDP bwtype . . . . . . . . . . . . . . . . . 67
15.2.2. Table: att-field . . . . . . . . . . . . . . . . . . 68
15.2.3. Table: content SDP Parameters . . . . . . . . . . . 73
15.2.4. Table: Semantics for the 'group' SDP Attribute . . . 73
15.2.5. Table: 'rtcp-fb' Attribute Values . . . . . . . . . 74
15.2.6. Table: 'ack' and 'nack' Attribute Values . . . . . . 74
15.2.7. Table: 'depend' SDP Attribute Values . . . . . . . . 75
15.2.8. Table: 'cs-correlation' Attribute Values . . . . . . 75
15.2.9. Table: Semantics for the 'ssrc-group' SDP Attribute 75
15.2.10. Table: SDP/RTSP key management protocol identifiers 76
15.2.11. Table: Codec Control Messages . . . . . . . . . . . 76
15.2.12. Table: QoS Mechanism Tokens . . . . . . . . . . . . 76
15.2.13. Table: SDP Capability Negotiation Option Tags . . . 77
15.2.14. Table: Timestamp Reference Clock Source Parameters . 77
15.2.15. Table: Media Clock Source Parameters . . . . . . . . 77
16. Security Considerations . . . . . . . . . . . . . . . . . . . 78
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 78
18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 78
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 80
19.1. Normative References . . . . . . . . . . . . . . . . . . 80
19.2. Informative References . . . . . . . . . . . . . . . . . 81
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 87
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")
skipping to change at page 5, line 31 skipping to change at page 6, line 23
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] and [I-D.ietf-mmusic-sdp-bundle-negotiation] to multiplex RTP over a
[I-D.ietf-avt-multiplexing-rtp] to multiplex RTP over a single single transport flow in order to preserve network resources such as
transport flow in order to preserve network resources such as port port numbers. This imposes further restrictions on applicability of
numbers. This imposes further restrictions on applicability of these these SDP attributes as they are defined today.
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 classical
SDP -- that do not make sense when those m-lines are then multiplexed SDP -- that do not make sense when those m-lines are then multiplexed
over the same transport. To give an obvious example, ICE permits over the same transport. To give an obvious example, ICE permits
each m=line to have an independently specified ice-ufrag attribute. each m=line to have an independently specified ice-ufrag attribute.
However, if the media from multiple m-lines is multiplexed over the However, if the media from multiple m-lines is multiplexed over the
same ICE component, then the meaning of media-level ice-ufrag same ICE component, then the meaning of media-level ice-ufrag
attributes becomes muddled. attributes becomes muddled.
skipping to change at page 8, line 20 skipping to change at page 9, line 6
typically used for bandwidth or other rate limiting attributes to the typically used for bandwidth or other rate limiting attributes to the
underlining transport. underlining 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=mhandley 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
t=0 0 t=0 0
m=audio 49170 RTP/AVP 0 m=audio 49170 RTP/AVP 0
b=AS:64 b=AS:64
m=video 51372 RTP/AVP 31 m=video 51372 RTP/AVP 31
b=AS:256 b=AS:256
4.5. Category: TRANSPORT 4.5. Category: TRANSPORT
Attributes that can be set normally for multiple items in a Attributes that can be set normally for multiple items in a
skipping to change at page 9, line 24 skipping to change at page 10, line 7
inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32
a=rtpmap:99 iLBC/8000 a=rtpmap:99 iLBC/8000
m=video 51374 RTP/AVP 31 m=video 51374 RTP/AVP 31
a=mid:bar a=mid:bar
a=crypto:1 AES_CM_128_HMAC_SHA1_80 a=crypto:1 AES_CM_128_HMAC_SHA1_80
inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32 inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32
a=rtpmap:96 H261/90000 a=rtpmap:96 H261/90000
4.6. Category: INHERIT 4.6. Category: INHERIT
Attributes that encapsulate other SDP attributes and their Attributes that encapsulate other SDP attributes or parameters.
multiplexing characteristics are inherited from the attributes they These attributes inherit their multiplexing characteristics from the
encapsulate. Such attributes as of today, are defined in [RFC3407], attributes or parameters they encapsulate. Such attributes as of
[RFC5939] and [RFC6871] as part of a generic framework for indicating today, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of a
and negotiating transport, media and media format related generic framework for indicating and negotiating transport, media and
capabilities in the SDP. media format related capabilities in the SDP.
The inheritance manifests itself when the encapsulated attribute or
parameter is being leveraged. In the case of SDP Capability
Negotiation [RFC5939] for example, this occurs when a capability
(encapsulating attribute) is used as part of a configuration; the
configuration inherits the multiplexing Category of each of its
constituent (encapsulated) attributes and parameters. This in turn
may place constraints on what constitutes a valid configuartion from
a multiplexing point of view, e.g. because some attributes must be
IDENTICAL (see Section 15 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 5 skipping to change at page 11, line 37
4.8. Category: SPECIAL 4.8. Category: SPECIAL
Attributes where the text in the source draft must be consulted for Attributes where the text in the 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
Attributes that have not been analyzed under the proposed
multiplexing framework yet.
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 [IANA] grouped under
the IETF document that defines them. The "Level" column indicates the 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 [RFC4566] defines the Session Description Protocol (SDP) that [RFC4566] defines the Session Description Protocol (SDP) that is
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 |
| | | | | | | | | |
| inactive | Not impacted | B | NORMAL | | inactive | Not impacted | B | NORMAL |
| | | | | | | | | |
| cat | Not impacted | S | NORMAL | | cat | Not impacted | S | NORMAL |
| | | | | | | | | |
| ptime | The attribute value must | M | IDENTICAL-PER-PT | | ptime | The attribute value | M | IDENTICAL-PER-PT |
| | be same for a given | | | | | must be same for a | | |
| | codec configuration | | | | | given codec | | |
| | | | | | | configuration | | |
| maxptime | The attribute value must | M | IDENTICAL-PER-PT | | | | | |
| | be same for a given | | | | maxptime | The attribute value | M | IDENTICAL-PER-PT |
| | codec configuration | | | | | must be same for a | | |
| | | | | | | given codec | | |
| orient | Not Impacted | M | NORMAL | | | configuration | | |
| | | | | | | | | |
| framerate | The attribute value must | M | IDENTICAL-PER-PT | | orient | Not Impacted | M | NORMAL |
| | be same for a given | | | | | | | |
| | codec configuration | | | | framerate | The attribute value | M | IDENTICAL-PER-PT |
| | | | | | | must be same for a | | |
| quality | Not Impacted | M | NORMAL | | | given codec | | |
| | | | | | | configuration | | |
| rtpmap | The attribute value must | M | IDENTICAL-PER-PT | | | | | |
| | be same for a given | | | | quality | Not Impacted | M | NORMAL |
| | codec configuration | | | | | | | |
| | | | | | rtpmap | The attribute value | M | IDENTICAL-PER-PT |
| fmtp | The attribute value must | M | IDENTICAL-PER-PT | | | must be same for a | | |
| | be same for a given | | | | | given codec | | |
| | codec configuration | | | | | configuration | | |
| | | | | | | | | |
| keywds | Not impacted | S | NORMAL | | fmtp | The attribute value | M | IDENTICAL-PER-PT |
| | | | | | | must be same for a | | |
| type | Not Impacted | S | NORMAL | | | given codec | | |
| | | | | | | configuration | | |
| tool | Not Impacted | S | NORMAL | | | | | |
| | | | | | keywds | Not impacted | S | NORMAL |
| charset | Not Impacted | S | NORMAL | | | | | |
| | | | | | type | Not Impacted | S | NORMAL |
| sdplang | Not Impacted | B | NORMAL | | | | | |
| | | | | | type:broadcast | Not Impacted | S | NORMAL |
| lang | Not Impacted | B | NORMAL | | | | | |
| | | | | | type:H332 | Not Impacted | S | NORMAL |
+------------+--------------------------+-------+-------------------+ | | | | |
| type:meeting | Not Impacted | S | NORMAL |
| | | | |
| type:moderated | Not Impacted | S | NORMAL |
| | | | |
| type:test | Not Impacted | S | NORMAL |
| | | | |
| tool | Not Impacted | S | NORMAL |
| | | | |
| charset | Not Impacted | S | NORMAL |
| | | | |
| sdplang | Not Impacted | B | NORMAL |
| | | | |
| lang | Not Impacted | B | NORMAL |
| | | | |
+-----------------+---------------------+-------+-------------------+
RFC4566 Attribute Analysis RFC4566 Attribute Analysis
5.2. RFC4585 - RTP/AVPF 5.2. RFC4585 - RTP/AVPF
RFC4585 [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 | | | |
+----------+-------------------------------------+-------+----------+ +----------+----------------------------+-------+-------------------+
| rtcp-fb | The combination of a particular | M | NORMAL | | rtcp-fb | Since RTCP feedback | M | IDENTICAL-PER-PT |
| | Payload Type along with the m=line | | | | | attributes are Payload | | |
| | identify the scope and | | | | | Type (PT) scoped, their | | |
| | applicability of a given RTCP | | | | | values MUST be identical | | |
| | feedback to a particular RTP | | | | | for a given PT across the | | |
| | Stream. | | | | | multiplexed m=lines. | | |
| | | | | | | | | |
+----------+-------------------------------------+-------+----------+ +----------+----------------------------+-------+-------------------+
RFC4585 Attribute Analysis RFC4585 Attribute Analysis
Since RTCP feedback attributes are Payload Type (PT) scoped, the
usage of identical Payload Type values across multiplexed m=lines is
described in [I-D.ietf-mmusic-sdp-bundle-negotiation].
5.3. RFC5761 - Multiplexing RTP and RTCP 5.3. RFC5761 - Multiplexing RTP and RTCP
RFC5761 [RFC5761] discusses issues that arise when multiplexing RTP [RFC5761] discusses issues that arise when multiplexing RTP data
data packets and RTP Control Protocol (RTCP) packets on a single UDP packets and RTP Control Protocol (RTCP) packets on a single UDP port.
port. It describes when such multiplexing is and is not appropriate, It describes when such multiplexing is and is not appropriate, and it
and it explains how the Session Description Protocol (SDP) can be explains how the Session Description Protocol (SDP) can be used to
used to signal multiplexed sessions. signal multiplexed sessions.
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| rtcp-mux | RTP and RTCP Multiplexing affect | M | IDENTICAL | | rtcp-mux | RTP and RTCP Multiplexing | M | IDENTICAL |
| | the entire RTP Session | | | | | affects the entire RTP Session | | |
| | | | | | | | | |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
RFC5761 Attribute Analysis RFC5761 Attribute Analysis
5.4. RFC4574 - SDP Label Attribute 5.4. RFC3312 - Integration of Resource Management and (SIP)
RFC4574 [RFC4574] defines a new Session Description Protocol (SDP) [RFC3312] defines a generic framework for preconditions, which are
media-level attribute: "label". The "label" attribute carries a extensible through IANA registration. This document also discusses
pointer to a media stream in the context of an arbitrary network how network quality of service can be made a precondition for
application that uses SDP. The sender of the SDP document can attach establishment of sessions initiated by the Session Initiation
the "label" attribute to a particular media stream or streams. The Protocol (SIP). These preconditions require that the participant
application can then use the provided pointer to refer to each reserve network resources before continuing with the session.
particular media stream in its context.
+-------+-----------------------+-------+-----------------+
| Name | Notes | Level | Category |
+-------+-----------------------+-------+-----------------+
| des | Refer to notes below | M | NOT RECOMMEDED |
| | | | |
| conf | Refer to notes below | M | NOT RECOMMEDED |
| | | | |
| curr | Refer to notes below | M | NOT RECOMMEDED |
| | | | |
+-------+-----------------------+-------+-----------------+
RFC3312 Attribute Analysis
A mismatched set of Preconditions across media descriptions results
in Session establishment failures due to inability to meet the right
resource reservations requested.
5.5. 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 | | Name | Notes | Level | Category |
+--------+---------------+-------+----------+ +--------+---------------+-------+----------+
| label | Not Impacted | M | NORMAL | | label | Not Impacted | M | NORMAL |
| | | | | | | | | |
+--------+---------------+-------+----------+ +--------+---------------+-------+----------+
RFC4574 Attribute Analysis RFC4574 Attribute Analysis
5.5. RFC5432 - QoS Mechanism Selection in SDP 5.6. RFC5432 - QoS Mechanism Selection in SDP
RFC5432 [RFC5432] defines procedures to negotiate QOS mechanisms [RFC5432] defines procedures to negotiate QOS mechanisms using the
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 | A single DSCP code point per | B | NORMAL |
| | flow being multiplexed | | | | | flow being multiplexed | | |
| | doesn't impact multiplexing | | | | | doesn't impact multiplexing | | |
| | since QOS mechanisms are | | | | | since QOS mechanisms are | | |
| | signaled/scoped per flow. | | | | | signaled/scoped per flow. | | |
| | | | | | | | | |
| qos-mech-recv | A single DSCP code point per | B | NORMAL | | qos-mech-recv | A single DSCP code point per | B | NORMAL |
| | flow being multiplexed | | | | | flow being multiplexed | | |
| | doesn't impact multiplexing | | | | | doesn't impact multiplexing | | |
| | since QOS mechanisms are | | | | | since QOS mechanisms are | | |
| | signaled/scoped per flow. | | | | | signaled/scoped per flow. | | |
| | | | | | | | | |
+----------------+-------------------------------+-------+----------+ +----------------+-------------------------------+-------+----------+
RFC5432 Attribute Analysis RFC5432 Attribute Analysis
Multiplexing consideration when multiple DSCP code points are defined For scenarios that involves having different DSCP for packets being
per flow can be found in Section 14 transmitted over the same 5-tuple, i.e. what is being in the same
bundle, has issues as discussed in [I.D-draft-ietf-dart-dscp-rtp]
5.6. RFC4568 - SDP Security Descriptions 5.7. RFC4568 - SDP Security Descriptions
RFC4568 [RFC4568] defines a Session Description Protocol (SDP) [RFC4568] defines a Session Description Protocol (SDP) cryptographic
cryptographic attribute for unicast media streams. The attribute attribute for unicast media streams. The attribute describes a
describes a cryptographic key and other parameters that serve to cryptographic key and other parameters that serve to configure
configure security for a unicast media stream in either a single security for a unicast media stream in either a single message or a
message or a roundtrip exchange. roundtrip exchange.
+--------+---------------------------------------+-------+----------+ +---------+------------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+--------+---------------------------------------+-------+----------+ +---------+------------------------------------+-------+------------+
| crypto | Refer to section 6.2.5 of [I-D.ietf-m | M | SPECIAL | | crypto | crypto attribute must be the one | M | TRANSPORT |
| | music-sdp-bundle-negotiation] | | | | | that corresponds to the m=line | | |
| | | | | | | chosen for setting up the | | |
+--------+---------------------------------------+-------+----------+ | | underlying transport flow | | |
| | | | |
+---------+------------------------------------+-------+------------+
RFC4568 Attribute Analysis RFC4568 Attribute Analysis
If the multiplexing scheme cannot ensure unique SSRCs across all the 5.8. RFC5762 - RTP over DCCP
media lines, multiplexing MUST NOT be performed.
5.7. 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 [RFC5762] specifies a services for real-time applications. [RFC5762] specifies a mapping
mapping of RTP onto DCCP, along with associated signaling, such that of RTP onto DCCP, along with associated signaling, such that real-
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 a | | |
| | DCCP port. DCCP | | | | | DCCP port. DCCP | | |
skipping to change at page 15, line 36 skipping to change at page 17, line 36
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.8. RFC6773 - DCCP-UDP Encapsulation 5.9. RFC6773 - DCCP-UDP Encapsulation
RFC6773 [RFC6773] document specifies an alternative encapsulation of [RFC6773] document specifies an alternative encapsulation of the
the Datagram Congestion Control Protocol (DCCP), referred to as DCCP- Datagram Congestion Control Protocol (DCCP), referred to as DCCP-UDP.
UDP. This encapsulation allows DCCP to be carried through the This encapsulation allows DCCP to be carried through the current
current generation of Network Address Translation (NAT) middle boxes generation of Network Address Translation (NAT) middle boxes without
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. | | |
| | | | | | | | | |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
skipping to change at page 16, line 29 skipping to change at page 18, line 29
encapsulation allows arbitrary DCCP packets to be encapsulated and encapsulation allows arbitrary DCCP packets to be encapsulated and
the DCCP port choosen MAY conflict with the port chosen for the RTP the DCCP port choosen 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 dependant.
5.9. RFC5506 - Reduced-Size RTCP in RTP Profile 5.10. RFC5506 - Reduced-Size RTCP in RTP Profile
RFC5506 [RFC5506] discusses benefits and issues that arise when [RFC5506] discusses benefits and issues that arise when allowing
allowing Real-time Transport Protocol (RTCP) packets to be Real-time Transport Protocol (RTCP) packets to be transmitted with
transmitted with reduced size. reduced size.
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| rtcp-rsize | Reduced size RTCP affects the | M | IDENTICAL | | rtcp-rsize | Reduced size RTCP affects the | M | IDENTICAL |
| | entire RTP Session | | | | | entire RTP Session | | |
| | | | | | | | | |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
RFC5506 Attribute Analysis RFC5506 Attribute Analysis
5.10. RFC6787 - Media Resource Control Protocol Version 2 5.11. RFC6787 - Media Resource Control Protocol Version 2
The Media Resource Control Protocol Version 2 (MRCPv2) allows client The Media Resource Control Protocol Version 2 (MRCPv2) allows client
hosts to control media service resources such as speech synthesizers, hosts to control media service resources such as speech synthesizers,
recognizers, verifiers, and identifiers residing in servers on the recognizers, verifiers, and identifiers residing in servers on the
network. MRCPv2 is not a "stand-alone" protocol -- it relies on network. MRCPv2 is not a "stand-alone" protocol -- it relies on
other protocols, such as the Session Initiation Protocol (SIP), to other protocols, such as the Session Initiation Protocol (SIP), to
coordinate MRCPv2 clients and servers and manage sessions between coordinate MRCPv2 clients and servers and manage sessions between
them, and the Session Description Protocol (SDP) to describe, them, and the Session Description Protocol (SDP) to describe,
discover, and exchange capabilities. It also depends on SIP and SDP discover, and exchange capabilities. It also depends on SIP and SDP
to establish the media sessions and associated parameters between the to establish the media sessions and associated parameters between the
media source or sink and the media server. Once this is done, the media source or sink and the media server. Once this is done, the
MRCPv2 exchange operates over the control session established above, MRCPv2 exchange operates over the control session established above,
allowing the client to control the media processing resources on the allowing the client to control the media processing resources on the
speech resource server. RFC6787 [RFC6787] defines attributes for speech resource server. [RFC6787] defines attributes for this
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 |
| | | | | | | | | |
+-----------+---------------+-------+----------+ +-----------+---------------+-------+----------+
RFC6787 Attribute Analysis RFC6787 Attribute Analysis
5.11. RFC5245 - Interactive Connectivity Establishment (ICE) 5.12. RFC5245 - Interactive Connectivity Establishment (ICE)
RFC5245 [RFC5245] describes a protocol for Network Address [RFC5245] describes a protocol for Network Address Translator(NAT)
Translator(NAT) traversal for UDP-based multimedia sessions traversal for UDP-based multimedia sessions established with the
established with the offer/answer model. This protocol is called offer/answer model. This protocol is called Interactive Connectivity
Interactive Connectivity Establishment (ICE). ICE makes use of the Establishment (ICE). ICE makes use of the Session Traversal
Session Traversal Utilities for NAT (STUN) protocol and its Utilities for NAT (STUN) protocol and its extension,Traversal Using
extension,Traversal Using Relay NAT (TURN). ICE can be used by any Relay NAT (TURN). ICE can be used by any protocol utilizing the
protocol utilizing the offer/answer model, such as the Session offer/answer model, such as the Session Initiation Protocol (SIP).
Initiation Protocol (SIP).
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
| ice-lite | Not Impacted | S | NORMAL | | ice-lite | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-options | Not Impacted | S | NORMAL | | ice-options | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-mismatch | Not Impacted | S | NORMAL |
| | | | |
| ice-pwd | ice-pwd MUST be the one | B | TRANSPORT | | ice-pwd | ice-pwd MUST be the one | B | TRANSPORT |
| | that corresponds to the | | | | | that corresponds to the | | |
| | m=line chosen for | | | | | m=line chosen for | | |
| | setting up the | | | | | setting up the | | |
| | underlying transport | | | | | underlying transport | | |
| | flow | | | | | flow | | |
| | | | | | | | | |
| ice-ufrag | ice-ufrag MUST be the | B | TRANSPORT | | ice-ufrag | ice-ufrag MUST be the | B | TRANSPORT |
| | one that corresponds to | | | | | one that corresponds to | | |
| | the m=line chosen for | | | | | the m=line chosen for | | |
skipping to change at page 18, line 46 skipping to change at page 20, line 48
| | corresponds to the | | | | | corresponds to the | | |
| | m=line chosen for | | | | | m=line chosen for | | |
| | setting up the | | | | | setting up the | | |
| | underlying transport | | | | | underlying transport | | |
| | flow | | | | | flow | | |
| | | | | | | | | |
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
RFC5245 Attribute Analysis RFC5245 Attribute Analysis
5.12. RFC5285 - RTP Header Extensions 5.13. RFC5285 - RTP Header Extensions
RFC5285 [RFC5285] provides a general mechanism to use the header [RFC5285] provides a general mechanism to use the header extension
extension feature of RTP (the Real-Time Transport Protocol). It feature of RTP (the Real-Time Transport Protocol). It provides the
provides the option to use a small number of small extensions in each option to use a small number of small extensions in each RTP packet,
RTP packet, where the universe of possible extensions is large and where the universe of possible extensions is large and registration
registration is de-centralized. The actual extensions in use in a is de-centralized. The actual extensions in use in a session are
session are signaled in the setup information for that session. signaled in the setup information for that session.
+---------+--------------------------------------+-------+----------+ +---------+--------------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------+--------------------------------------+-------+----------+ +---------+--------------------------------------+-------+----------+
| extmap | Specific RTP extension document MUST | B | SPECIAL | | extmap | Specific RTP extension document MUST | B | SPECIAL |
| | be referred | | | | | be referred | | |
| | | | | | | | | |
+---------+--------------------------------------+-------+----------+ +---------+--------------------------------------+-------+----------+
RFC5285 Attribute Analysis RFC5285 Attribute Analysis
5.13. RFC3605 - RTCP attribute in SDP 5.14. RFC3605 - RTCP attribute in SDP
Originally, SDP assumed that RTP and RTCP were carried on consecutive Originally, SDP assumed that RTP and RTCP were carried on consecutive
ports. However, this is not always true when NATs are involved. ports. However, this is not always true when NATs are involved.
[RFC3605] specifies an early mechanism to indicate the RTCP port. [RFC3605] specifies an early mechanism to indicate the RTCP port.
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| rtcp | Identical attribute value MUST be | M | IDENTICAL | | rtcp | Identical attribute value MUST be | M | IDENTICAL |
| | used since the RTCP port affects the | | | | | used since the RTCP port affects the | | |
| | entire RTP session. | | | | | entire RTP session. | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
RFC3605 Attribute Analysis RFC3605 Attribute Analysis
5.14. RFC5576 - Source-Specific SDP Attributes 5.15. RFC5576 - Source-Specific SDP Attributes
RFC5576 [RFC5576] defines a mechanism to describe RTP media sources, [RFC5576] defines a mechanism to describe RTP media sources, which
which are identified by their synchronization source (SSRC) are identified by their synchronization source (SSRC) identifiers, in
identifiers, in SDP, to associate attributes with these sources, and SDP, to associate attributes with these sources, and to express
to express relationships among sources. It also defines several relationships among sources. It also defines several source-level
source-level attributes that can be used to describe properties of attributes that can be used to describe properties of media sources.
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 | SPECIAL |
| | Section 9 for | | | | | Section 9 for | | |
| | specific analysis of | | | | | specific analysis of | | |
| | the grouping | | | | | the grouping | | |
skipping to change at page 20, line 34 skipping to change at page 22, line 34
| fmtp | The attribute value | SR | IDENTICAL-PER-PT | | fmtp | The attribute value | SR | IDENTICAL-PER-PT |
| | must be same for a | | | | | must be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
RFC5576 Attribute Analysis RFC5576 Attribute Analysis
If SSRCs are repeated across m=lines being multiplexed, they MUST all If SSRCs are repeated across m=lines being multiplexed, they MUST all
represent the same underlying RTP Source. For more details on represent the same underlying RTP Source.
implications of SSRC values with in the context of multiplexing
please refer to [I-D.ietf-mmusic-sdp-bundle-negotiation]
5.15. RFC6236 - Image Attributes in SDP 5.16. RFC7273 - RTP Clock Source Signalling
RFC6236 [RFC6236] proposes a new generic session setup attribute to [RFC7273] specifies Session Description Protocol (SDP) signalling
make it possible to negotiate different image attributes such as that identifies timestamp reference clock sources and SDP signalling
image size. A possible use case is to make it possible for a low-end that identifies the media clock sources in a multimedia session.
hand-held terminal to display video without the need to rescale the
+------------+---------------+-----------+----------+
| Name | Notes | Level | Category |
+------------+---------------+-----------+----------+
| ts-refclk | Not Impacted | S, M, SR | NORMAL |
| | | | |
| mediaclk | Not Impacted | S,, M, SR | NORMAL |
| | | | |
+------------+---------------+-----------+----------+
RFC7273 Attribute Analysis
5.17. RFC6236 - Image Attributes in SDP
[RFC6236] proposes a new generic session setup attribute to make it
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
terminal to display video without the need to rescale the
image,something that may consume large amounts of memory and image,something that may consume large amounts of memory and
processing power. The document also helps to maintain an optimal processing power. The document also helps to maintain an optimal
bitrate for video as only the image size that is desired by the bitrate for video as only the image size that is desired by the
receiver is transmitted. receiver is transmitted.
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
| imageattr | The attribute value must | M | IDENTICAL-PER-PT | | imageattr | The attribute value must | M | IDENTICAL-PER-PT |
| | be same for a given | | | | | be same for a given | | |
| | codec configuration | | | | | codec configuration | | |
| | | | | | | | | |
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
RFC6236 Attribute Analysis RFC6236 Attribute Analysis
5.16. RFC6285 - Rapid Acquisition of Multicast RTP Sessions 5.18. RFC7197 - Duplication Delay Attribute in SDP
RFC6285 [RFC6285] describes a method using the existing RTP and RTP [RFC7197] defines an attribute to indicate the presence of temporally
Control Protocol (RTCP) machinery that reduces the acquisition delay. redundant media streams and the duplication delay in the Session
In this method, an auxiliary unicast RTP session carrying the Description Protocol
Reference Information to the receiver precedes or accompanies the
multicast stream. This unicast RTP flow can be transmitted at a +--------------------+---------------+-------+----------+
faster than natural bitrate to further accelerate the acquisition. | Name | Notes | Level | Category |
The motivating use case for this capability is multicast applications +--------------------+---------------+-------+----------+
| duplication-delay | Not Impacted | B | NORMAL |
| | | | |
+--------------------+---------------+-------+----------+
RFC7197 Attribute Analysis
5.19. RFC7226 - RTCP XR Blocks for MOS Metric Reporting
[RFC7226] defines an RTP Control Protocol (RTCP) Extended Report (XR)
Block including two new segment types and associated Session
Description Protocol (SDP) parameters that allow the reporting of
mean opinion score (MOS) Metrics for use in a range of RTP
applications.
+-------------+---------------+-------+----------+
| Name | Notes | Level | Category |
+-------------+---------------+-------+----------+
| calgextmap | Not Impacted | B | NORMAL |
| | | | |
+-------------+---------------+-------+----------+
RFC7226 Attribute Analysis
5.20. RFC6285 - Rapid Acquisition of Multicast RTP Sessions
[RFC6285] describes a method using the existing RTP and RTP Control
Protocol (RTCP) machinery that reduces the acquisition delay. In
this method, an auxiliary unicast RTP session carrying the Reference
Information to the receiver precedes or accompanies the multicast
stream. This unicast RTP flow can be transmitted at a faster than
natural bitrate to further accelerate the acquisition. The
motivating use case for this capability is multicast applications
that carry real-time compressed audio and video. that carry real-time compressed audio and video.
+---------------+-------------------+-------+------------------+ +---------------+-------------------+-------+------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------------+-------------------+-------+------------------+ +---------------+-------------------+-------+------------------+
| rams-updates | Not recommended | M | NOT RECOMMENDED | | rams-updates | Not recommended | M | NOT RECOMMENDED |
| | | | | | | | | |
+---------------+-------------------+-------+------------------+ +---------------+-------------------+-------+------------------+
RFC6285 Attribute Analysis RFC6285 Attribute Analysis
5.17. RFC6230 - Media Control Channel Framework 5.21. RFC6230 - Media Control Channel Framework
RFC6230 [RFC6230] describes a framework and protocol for application [RFC6230] describes a framework and protocol for application
deployment where the application programming logic and media deployment where the application programming logic and media
processing are distributed. This implies that application processing are distributed. This implies that application
programming logic can seamlessly gain access to appropriate resources programming logic can seamlessly gain access to appropriate resources
that are not co-located on the same physical network entity. The that are not co-located on the same physical network entity. The
framework uses the Session Initiation Protocol (SIP) to establish an framework uses the Session Initiation Protocol (SIP) to establish an
application-level control mechanism between application servers and application-level control mechanism between application servers and
associated external servers such as media servers. associated external servers such as media servers.
+---------+-----------------+-------+----------+ +---------+-----------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------+-----------------+-------+----------+ +---------+-----------------+-------+----------+
| cfw-id | Not Applicable | M | NORMAL | | cfw-id | Not Applicable | M | NORMAL |
| | | | | | | | | |
+---------+-----------------+-------+----------+ +---------+-----------------+-------+----------+
RFC6230 Attribute Analysis RFC6230 Attribute Analysis
5.18. RFC6364 - SDP Elements for FEC Framework 5.22. RFC6364 - SDP Elements for FEC Framework
RFC6364 [RFC6364] specifies the use of the Session Description [RFC6364] specifies the use of the Session Description Protocol (SDP)
Protocol (SDP) to describe the parameters required to signal the to describe the parameters required to signal the Forward Error
Forward Error Correction (FEC) Framework Configuration Information Correction (FEC) Framework Configuration Information between the
between the sender(s) and receiver(s). This document also provides sender(s) and receiver(s). This document also provides examples that
examples that show the semantics for grouping multiple source and show the semantics for grouping multiple source and repair flows
repair flows together for the applications that simultaneously use together for the applications that simultaneously use multiple
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 | | M | SPECIAL |
| | | | | | | | | |
| fec-repair-flow | | M | SPECIA: | | fec-repair-flow | | M | SPECIAL |
| | | | | | | | | |
| repair-window | | M | SPECIAL | | repair-window | | M | SPECIAL |
| | | | | | | | | |
+------------------+-------+-------+----------+ +------------------+-------+-------+----------+
RFC6364 Attribute Analysis RFC6364 Attribute Analysis
5.19. RFC4796 - Content Attribute 5.23. RFC4796 - Content Attribute
RFC4796 [RFC4796] defines a new Session Description Protocol (SDP) [RFC4796] defines a new Session Description Protocol (SDP) media-
media-level attribute, 'content'. The 'content' attribute defines level attribute, 'content'. The 'content' attribute defines the
the content of the media stream to a more detailed level than the content of the media stream to a more detailed level than the media
media description line. The sender of an SDP session description can description line. The sender of an SDP session description can
attach the 'content' attribute to one or more media streams. The attach the 'content' attribute to one or more media streams. The
receiving application can then treat each media stream differently receiving application can then treat each media stream differently
(e.g., show it on a big or small screen) based on its content. (e.g., show it on a big or small screen) based on its content.
+----------+---------------+-------+----------+ +----------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+----------+---------------+-------+----------+ +----------+---------------+-------+----------+
| content | Not Impacted | M | NORMAL | | content | Not Impacted | M | NORMAL |
| | | | | | | | | |
+----------+---------------+-------+----------+ +----------+---------------+-------+----------+
RFC4796 Attribute Analysis RFC4796 Attribute Analysis
5.20. RFC3407 - SDP Simple Capability Declaration 5.24. RFC3407 - SDP Simple Capability Declaration
RFC3407 [RFC3407] defines a set of Session Description Protocol (SDP) [RFC3407] defines a set of Session Description Protocol (SDP)
attributes that enables SDP to provide a minimal and backwards attributes that enables SDP to provide a minimal and backwards
compatible capability declaration mechanism. compatible capability declaration mechanism.
+----------+------------------------+-------+----------+ +----------+------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+----------+------------------------+-------+----------+ +----------+------------------------+-------+----------+
| sqn | Not Impacted | B | NORMAL | | sqn | Not Impacted | B | NORMAL |
| | | | | | | | | |
| cdsc | Not Impacted. | B | NORMAL | | cdsc | Not Impacted. | B | NORMAL |
| | | | | | | | | |
| cpar | Refer to Section 15 | B | INHERIT | | cpar | Refer to Section 14 | B | INHERIT |
| | | | | | | | | |
| cparmin | Refer to notes below | B | SPECIAL | | cparmin | Refer to notes below | B | SPECIAL |
| | | | | | | | | |
| cparmax | Refer to notes below | B | SPECIAL | | cparmax | Refer to notes below | B | SPECIAL |
| | | | | | | | | |
+----------+------------------------+-------+----------+ +----------+------------------------+-------+----------+
RFC3407 Attribute Analysis RFC3407 Attribute Analysis
Since the attributes (a=cparmin and a=cparmax) defines minimum and Since the attributes (a=cparmin and a=cparmax) define minimum and
maximum numerical values associated with the attributed 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 for dealing under media stream multiplexing.
5.21. 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
to choose their own ports for an auxiliary unicast session in RTP
applications using both unicast and multicast services. The solution
provides protection against denial-of-service or packet amplification
attacks that could be used to cause one or more RTP packets to be
sent to a victim client
RFC6284 [RFC6284] presents a port mapping solution that allows RTP
receivers to choose their own ports for an auxiliary unicast session
in RTP applications using both unicast and multicast services. The
solution provides protection against denial-of-service or packet
amplification attacks that could be used to cause one or more RTP
packets to be 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 | | |
| | | | | | | | | |
+------------------+-------------------------+-------+--------------+ +------------------+-------------------------+-------+--------------+
RFC6284 Attribute Analysis RFC6284 Attribute Analysis
5.22. RFC6714 - MSRP-CEMA 5.26. RFC6714 - MSRP-CEMA
RFC6714 [RFC6714] defines a Message Session Relay Protocol (MSRP) [RFC6714] defines a Message Session Relay Protocol (MSRP) extension,
extension, Connection Establishment for Media Anchoring (CEMA). Connection Establishment for Media Anchoring (CEMA). Support of this
Support of this extension is OPTIONAL. The extension allows middle extension is OPTIONAL. The extension allows middle boxes to anchor
boxes to anchor the MSRP connection, without the need for middle the MSRP connection, without the need for middle boxes to modify the
boxes to modify the MSRP messages; thus, it also enables secure end- MSRP messages; thus, it also enables secure end-to-end MSRP
to-end MSRP communication in networks where such middle boxes are communication in networks where such middle boxes are deployed. This
deployed. This document also defines a Session Description Protocol document also defines a Session Description Protocol (SDP) attribute,
(SDP) attribute, 'msrp-cema', that MSRP endpoints use to indicate 'msrp-cema', that MSRP endpoints use to indicate support of the CEMA
support of the CEMA extension. extension.
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
| msrp-cema | Not Impacted | M | NORMAL | | msrp-cema | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------+---------------+-------+----------+ +------------+---------------+-------+----------+
RFC6714 Attribute Analysis RFC6714 Attribute Analysis
5.23. RFC4583 - SDP Format for BFCP Streams 5.27. RFC4583 - SDP Format for BFCP Streams
RFC4583 [RFC4583] document specifies how to describe Binary Floor [RFC4583] document specifies how to describe Binary Floor Control
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 25, line 21 skipping to change at page 27, line 44
| | | | | | | | | |
| userid | Not Impacted | M | NORMAL | | userid | Not Impacted | M | NORMAL |
| | | | | | | | | |
| floorid | The floorid MUST be globally | M | NORMAL | | floorid | The floorid MUST be globally | M | NORMAL |
| | unique | | | | | unique | | |
| | | | | | | | | |
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
RFC4583 Attribute Analysis RFC4583 Attribute Analysis
5.24. RFC5547 - SDP Offer/Answer for File Transfer 5.28. RFC5547 - SDP Offer/Answer for File Transfer
RFC5547 [RFC5547] provides a mechanism to negotiate the transfer of [RFC5547] provides a mechanism to negotiate the transfer of one or
one or more files between two endpoints by using the Session more files between two endpoints by using the Session Description
Description Protocol (SDP) offer/answer model specified in [RFC3264]. Protocol (SDP) offer/answer model specified in [RFC3264].
+----------------------+---------------+-------+----------+ +----------------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+----------------------+---------------+-------+----------+ +----------------------+---------------+-------+----------+
| file-selector | Not Impacted | M | NORMAL | | file-selector | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-transfer-id | Not Impacted | M | NORMAL | | file-transfer-id | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-disposition | Not Impacted | M | NORMAL | | file-disposition | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-date | Not Impacted | M | NORMAL | | file-date | Not Impacted | M | NORMAL |
| | | | | | | | | |
| file-iconfile-range | Not Impacted | M | NORMAL | | file-iconfile-range | Not Impacted | M | NORMAL |
| | | | | | | | | |
+----------------------+---------------+-------+----------+ +----------------------+---------------+-------+----------+
RFC5547 Attribute Analysis RFC5547 Attribute Analysis
5.25. RFC6489 - SDP and RTP Media Loopback Extension 5.29. RFC6489 - SDP and RTP Media Loopback Extension
[MEDIA_LOOPBACK] adds new SDP media types and attributes, which [RFC6489] adds new SDP media types and attributes, which enable
enable establishment of media sessions where the media is looped back establishment of media sessions where the media is looped back to the
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 An Extension to the Session Description Protocol (SDP) and Real-time
Transport Protocol (RTP) for Media Loopback Transport Protocol (RTP) for Media Loopback
5.26. RFC5760 - RTCP with Unicast Feedback 5.30. RFC5760 - RTCP with Unicast Feedback
RFC5760 [RFC5760] specifies an extension to the Real-time Transport [RFC5760] specifies an extension to the Real-time Transport Control
Control Protocol (RTCP) to use unicast feedback to a multicast Protocol (RTCP) to use unicast feedback to a multicast sender. The
sender. The proposed extension is useful for single-source multicast proposed extension is useful for single-source multicast sessions
sessions such as Source-Specific Multicast (SSM) communication where such as Source-Specific Multicast (SSM) communication where the
the traditional model of many-to-many group communication is either traditional model of many-to-many group communication is either not
not available or not desired. available or not desired.
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| rtcp-unicast | The attribute MUST be | M | IDENTICAL | | rtcp-unicast | The attribute MUST be | M | IDENTICAL |
| | reported across all m=lines | | | | | reported across all m=lines | | |
| | multiplexed | | | | | multiplexed | | |
| | | | | | | | | |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
RFC5760 Attribute Analysis RFC5760 Attribute Analysis
5.27. RFC3611 - RTCP XR 5.31. RFC3611 - RTCP XR
RFC3611 [RFC3611] defines the Extended Report (XR) packet type for [RFC3611] defines the Extended Report (XR) packet type for the RTP
the RTP Control Protocol (RTCP), and defines how the use of XR Control Protocol (RTCP), and defines how the use of XR packets can be
packets can be signaled by an application if it employs the Session signaled by an application if it employs the Session Description
Description Protocol (SDP). Protocol (SDP).
+----------+---------------+-------+----------+ +----------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+----------+---------------+-------+----------+ +----------+---------------+-------+----------+
| rtcp-xr | Not Impacted | B | NORMAL | | rtcp-xr | Not Impacted | B | NORMAL |
| | | | | | | | | |
+----------+---------------+-------+----------+ +----------+---------------+-------+----------+
RFC3611 Attribute Analysis RFC3611 Attribute Analysis
5.28. RFC5939 - SDP Capability Negotiation 5.32. RFC5939 - SDP Capability Negotiation
RFC5939 [RFC5939] defines a general SDP Capability Negotiation [RFC5939] defines a general SDP Capability Negotiation framework. It
framework. It also specifies how to provide attributes and transport also specifies how to provide attributes and transport protocols as
protocols as capabilities and negotiate them using the framework. capabilities and negotiate them using the framework. Extensions for
Extensions for other types of capabilities (e.g., media types and other types of capabilities (e.g., media types and media formats) may
media formats) may be provided in other documents. be provided in other documents.
+-------+-------------------------------+-------+----------+ +---------+-------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------+-------------------------------+-------+----------+ +---------+-------------------------------+-------+----------+
| pcfg | Refer to section Section 15 | M | INHERIT | | pcfg | Refer to Section Section 14 | M | SPECIAL |
| | | | | | | | | |
| acfg | Refer to section Section 15 | M | INHERIT | | acfg | Refer to Section Section 14 | M | SPECIAL |
| | | | | | | | | |
| csup | Not Impacted | B | NORMAL | | csup | Not Impacted | B | NORMAL |
| | | | | | | | | |
| creq | Not Impacted | B | NORMAL | | creq | Not Impacted | B | NORMAL |
| | | | | | | | | |
| acap | Refer to section Section 15 | B | INHERIT | | acap | Refer to section Section 14 | B | INHERIT |
| | | | | | | | | |
| tcap | Refer to section Section 15 | B | INHERIT | | tcap | Refer to section Section 14 | B | INHERIT |
| | | | | | | | | |
+-------+-------------------------------+-------+----------+ | cap-v0 | Not Impacted | B | NORMAL |
| | | | |
+---------+-------------------------------+-------+----------+
RFC5939 Attribute Analysis RFC5939 Attribute Analysis
5.29. RFC6871- SDP Media Capabilities Negotiation 5.33. RFC6871- SDP Media Capabilities Negotiation
Session Description Protocol (SDP) capability negotiation provides a Session Description Protocol (SDP) capability negotiation provides a
general framework for indicating and negotiating capabilities in SDP. general framework for indicating and negotiating capabilities in SDP.
The base framework defines only capabilities for negotiating The base framework defines only capabilities for negotiating
transport protocols and attributes. [RFC6871] extends the framework transport protocols and attributes. [RFC6871] extends the framework
by defining media capabilities that can be used to negotiate media by defining media capabilities that can be used to negotiate media
types and their associated parameters. types and their associated parameters.
+---------+------------------------------+-------+----------+ +---------+-----------------------------+-------+-------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------+------------------------------+-------+----------+ +---------+-----------------------------+-------+-------------------+
| rmcap | Refer to section Section 15 | B | INHERIT | | rmcap | Refer to Section Section 14 | B | IDENTICAL-PER-PT |
| | | | | | | | | |
| omcap | Refer to section Section 15 | B | INHERIT | | omcap | Not Impacted | B | NORMAL |
| | | | | | | | | |
| mfcap | Refer to section Section 15 | B | INHERIT | | mfcap | Refer to Section Section 14 | B | IDENTICAL-PER-PT |
| | | | | | | | | |
| mscap | Refer to section Section 15 | B | INHERIT | | mscap | Refer to Section Section 14 | B | INHERIT |
| | | | | | | | | |
| lcfg | Not Impacted | B | NORMAL | | lcfg | Refer to Section Section 14 | B | SPECIAL |
| | | | | | | | | |
| sescap | Refer to section Section 15 | S | INHERIT | | sescap | Refer to Section Section 14 | S | NOT RECOMMENDED |
| | | | | | | | | |
+---------+------------------------------+-------+----------+ | med-v0 | Not Impacted | S | NORMAL |
| | | | |
+---------+-----------------------------+-------+-------------------+
Session Description Protocol (SDP) Media Capabilities Negotiation Session Description Protocol (SDP) Media Capabilities Negotiation
5.30. RFC4567 - Key Management Extensions for SDP and RTSP The "sescap" attribute is NOT RECOMMENDED for use with multiplexing.
The reason is that it requires the use of unique configuration
numbers across the entire SDP (per [RFC6871] as opposed to within a
media description only (per [RFC5939]). As described in Section 15,
the use of identical configuration numbers between multiplxed
(bundled) media descriptions is the default way of indicating
compatible configurations in a bundle.
RFC4567 [RFC4567] defines general extensions for Session Description 5.34. RFC7006 - Miscellaneous Capabilities Negotiation SDP
Protocol (SDP) and Real Time Streaming Protocol (RTSP) to carry
messages, as specified by a key management protocol, in order to [RFC7006] extends the SDP capability negotiation framework to allow
secure the media. These extensions are presented as a framework, to endpoints to negotiate three additional SDP capabilities. In
be used by one or more key management protocols. As such, their use particular, this memo provides a mechanism to negotiate bandwidth
is meaningful only when complemented by an appropriate key management ("b=" line), connection data ("c=" line), and session or media titles
protocol. ("i=" line for each session or media).
+----------+-----------------------------------+-------+------------+
| Name | Notes | Level | Category |
+----------+-----------------------------------+-------+------------+
| bcap | Inherit the category SUM as | B | INHERIT |
| | applicable to b= attribute | | |
| | | | |
| bcap-v0 | Not Impacted | B | NORMAL |
| | | | |
| ccap | The connection address type MUST | B | IDENTICAL |
| | be identical across all the | | |
| | multiplexed m= lines. | | |
| | | | |
| ccap-v0 | Not Impacted. | B | NORMAL |
| | | | |
| icap | Not Impacted | B | NORMAL |
| | | | |
| icap-v0 | Not Impacted | B | NORMAL |
| | | | |
+----------+-----------------------------------+-------+------------+
Miscellaneous Capabilities Negotiation in the Session Description
Protocol (SDP)
5.35. RFC4567 - Key Management Extensions for SDP and RTSP
[RFC4567] defines general extensions for Session Description Protocol
(SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as
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
more key management protocols. As such, their use is meaningful only
when complemented by an appropriate key management protocol.
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| key-mgmt | Key management protocol MUST be | B | IDENTICAL | | key-mgmt | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the m=lines | | | | | identical across all the m=lines | | |
| | | | | | | | | |
| mikey | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the m=lines | | |
| | | | |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
RFC4567 Attribute Analysis RFC4567 Attribute Analysis
5.31. RFC4572 - Comedia over TLS in SDP 5.36. RFC4572 - Comedia over TLS in SDP
RFC4572 [RFC4572] specifies how to establish secure connection- [RFC4572] specifies how to establish secure connection-oriented media
oriented media transport sessions over the Transport Layer Security transport sessions over the Transport Layer Security (TLS) protocol
(TLS) protocol using the Session Description Protocol (SDP). It using the Session Description Protocol (SDP). It defines a new SDP
defines a new SDP protocol identifier, 'TCP/TLS'. It also defines protocol identifier, 'TCP/TLS'. It also defines the syntax and
the syntax and semantics for an SDP 'fingerprint' attribute that semantics for an SDP 'fingerprint' attribute that identifies the
identifies the certificate that will be presented for the TLS certificate that will be presented for the TLS session. This
session. This mechanism allows media transport over TLS connections mechanism allows media transport over TLS connections to be
to be established securely, so long as the integrity of session established securely, so long as the integrity of session
descriptions is assured. descriptions is assured.
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
| fingerprint | Fingerprint value from the | B | TRANSPORT | | fingerprint | Fingerprint value from the | B | TRANSPORT |
| | m=line defining the | | | | | m=line defining the | | |
| | underlying transport is | | | | | underlying transport is | | |
| | chosen | | | | | chosen | | |
| | | | | | | | | |
+--------------+-------------------------------+-------+------------+ +--------------+-------------------------------+-------+------------+
RFC4572 Attribute Analysis RFC4572 Attribute Analysis
5.32. RFC4570 - SDP Source Filters 5.37. RFC4570 - SDP Source Filters
RFC4570 [RFC4570] describes how to adapt the Session Description [RFC4570] describes how to adapt the Session Description Protocol
Protocol (SDP) to express one or more source addresses as a source (SDP) to express one or more source addresses as a source filter for
filter for one or more destination "connection" addresses. It one or more destination "connection" addresses. It defines the
defines the syntax and semantics for an SDP "source-filter" attribute syntax and semantics for an SDP "source-filter" attribute that may
that may reference either IPv4 or IPv6 address(es) as either an reference either IPv4 or IPv6 address(es) as either an inclusive or
inclusive or exclusive source list for either multicast or unicast exclusive source list for either multicast or unicast destinations.
destinations. In particular, an inclusive source-filter can be used In particular, an inclusive source-filter can be used to specify a
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 | | |
| | | | | | | | | |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
RFC4570 Attribute Analysis RFC4570 Attribute Analysis
5.33. RFC6128 - RTCP Port for Multicast Sessions 5.38. RFC6128 - RTCP Port for Multicast Sessions
The Session Description Protocol (SDP) has an attribute that allows The Session Description Protocol (SDP) has an attribute that allows
RTP applications to specify an address and a port associated with the RTP applications to specify an address and a port associated with the
RTP Control Protocol (RTCP) traffic. In RTP-based source-specific RTP Control Protocol (RTCP) traffic. In RTP-based source-specific
multicast (SSM) sessions, the same attribute is used to designate the multicast (SSM) sessions, the same attribute is used to designate the
address and the RTCP port of the Feedback Target in the SDP address and the RTCP port of the Feedback Target in the SDP
description. However, the RTCP port associated with the SSM session description. However, the RTCP port associated with the SSM session
itself cannot be specified by the same attribute to avoid ambiguity, itself cannot be specified by the same attribute to avoid ambiguity,
and thus, is required to be derived from the "m=" line of the media and thus, is required to be derived from the "m=" line of the media
description. Deriving the RTCP port from the "m=" line imposes an description. Deriving the RTCP port from the "m=" line imposes an
unnecessary restriction. RFC6128 [RFC6128] removes this restriction unnecessary restriction. [RFC6128] removes this restriction by
by introducing a new SDP attribute. introducing a new SDP attribute.
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
| multicast-rtcp | Multicast RTCP port MUST | B | IDENTICAL | | multicast-rtcp | Multicast RTCP port MUST | B | IDENTICAL |
| | be identical across all | | | | | be identical across all | | |
| | the m=lines | | | | | the m=lines | | |
| | | | | | | | | |
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
RFC6128 Attribute Analysis RFC6128 Attribute Analysis
5.34. RFC6189 - ZRTP 5.39. RFC6189 - ZRTP
RFC6189 [RFC6189] defines ZRTP, a protocol for media path Diffie- [RFC6189] defines ZRTP, a protocol for media path Diffie-Hellman
Hellman exchange to agree on a session key and parameters for exchange to agree on a session key and parameters for establishing
establishing unicast Secure Real-time Transport Protocol (SRTP) unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice
sessions for Voice over IP (VoIP) applications. over IP (VoIP) applications.
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| zrtp-hash | Complicates if all the | M | NOT | | zrtp-hash | Complicates if all the | M | NOT |
| | m=lines are not authenticated | | RECOMMENDED | | | m=lines are not authenticated | | RECOMMENDED |
| | as given in the example below | | | | | as given in the example below | | |
| | | | | | | | | |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
skipping to change at page 31, line 19 skipping to change at page 35, line 19
t=0 0 t=0 0
m=audio 3456 RTP/AVP 97 m=audio 3456 RTP/AVP 97
a=rtpmap:97 iLBC/8000 a=rtpmap:97 iLBC/8000
<allOneLine> <allOneLine>
a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2 a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2
df881ae642c371ba46df df881ae642c371ba46df
</allOneLine> </allOneLine>
m=video 34567 RTP/AVP 31 m=video 34567 RTP/AVP 31
a=rtpmap:31 H261/90000 a=rtpmap:31 H261/90000
5.35. RFC4145 - Connection-Oriented Media 5.40. RFC4145 - Connection-Oriented Media
RFC4145 [RFC4145] describes how to express media transport over TCP [RFC4145] describes how to express media transport over TCP using the
using the Session Description Protocol (SDP). It defines the SDP Session Description Protocol (SDP). It defines the SDP 'TCP'
'TCP' protocol identifier, the SDP 'setup' attribute, which describes protocol identifier, the SDP 'setup' attribute, which describes the
the connection setup procedure, and the SDP 'connection' attribute, connection setup procedure, and the SDP 'connection' attribute, which
which handles connection reestablishment. handles connection reestablishment.
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| setup | MUST be identical across all | B | IDENTICAL | | setup | MUST be identical across all | B | IDENTICAL |
| | m=lines | | | | | m=lines | | |
| | | | | | | | | |
| connection | MUST be identical across all | B | IDENTICAL | | connection | MUST be identical across all | B | IDENTICAL |
| | m=lines | | | | | m=lines | | |
| | | | | | | | | |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
RFC4145 Attribute Analysis RFC4145 Attribute Analysis
5.36. RFC5159 - OMA BCAST SDP Attributes 5.41. RFC6947 - The SDP ALTC Attribute
RFC5159 [RFC5159] provides descriptions of Session Description [RFC6947] proposes a mechanism that allows the same SDP offer to
Protocol (SDP) attributes used by the Open Mobile Alliance's carry multiple IP addresses of different address families (e.g., IPv4
Broadcast Service and Content Protection specification. and IPv6). The proposed attribute, the "altc" attribute, solves the
backward-compatibility problem that plagued Alternative Network
Address Types (ANAT) due to their syntax.
+-------+--------------------------------------+-------+------------+
| Name | Notes | Level | Category |
+-------+--------------------------------------+-------+------------+
| altc | The IP Address and port must be the | M | TRANSPORT |
| | one that corresponds to the m=line | | |
| | chosen for setting up the underlying | | |
| | transport flow. | | |
| | | | |
+-------+--------------------------------------+-------+------------+
RFC6947 Attribute Analysis
5.42. RFC7195 - SDP Extension for Circuit Switched Bearers in PSTN
[RFC7195] describes use cases, requirements, and protocol extensions
for using the Session Description Protocol (SDP) offer/answer model
for establishing audio and video media streams over circuit-switched
bearers in the Public Switched Telephone Network (PSTN).
+--------------------------+----------------+-------+----------+
| Name | Notes | Level | Category |
+--------------------------+----------------+-------+----------+
| cs-correlation:callerid | Not Impacted. | M | NORMAL |
| | | | |
| cs-correlation:uuie | Not Impacted. | M | NORMAL |
| | | | |
| cs-correlation:dtmf | Not Impacted. | M | NORMAL |
| | | | |
| cs-correlation:external | Not Impacted. | M | NORMAL |
| | | | |
+--------------------------+----------------+-------+----------+
RFC7195 Attribute Analysis
5.43. RFC7272 - IDMS Using the RTP Control Protocol (RTCP)
[RFC7272] defines a new RTP Control Protocol (RTCP) Packet Type and
an RTCP Extended Report (XR) Block Type to be used for achieving
Inter-Destination Media Synchronization (IDMS).
+------------+----------------+-------+----------+
| Name | Notes | Level | Category |
+------------+----------------+-------+----------+
| rtcp-idms | Not Impacted. | M | NORMAL |
| | | | |
+------------+----------------+-------+----------+
RFC7272 Attribute Analysis
5.44. RFC5159 - OMA BCAST SDP Attributes
[RFC5159] provides descriptions of Session Description Protocol (SDP)
attributes used by the Open Mobile Alliance's Broadcast Service and
Content Protection specification.
+---------------------+---------------+-------+----------+ +---------------------+---------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------------------+---------------+-------+----------+ +---------------------+---------------+-------+----------+
| bcastversion | Not Impacted | S | NORMAL | | bcastversion | Not Impacted | S | NORMAL |
| | | | | | | | | |
| stkmstream | Not Impacted | B | NORMAL | | stkmstream | Not Impacted | B | NORMAL |
| | | | | | | | | |
| SRTPAuthentication | Not Impacted | M | NORMAL | | SRTPAuthentication | Not Impacted | M | NORMAL |
| | | | | | | | | |
| SRTPROCTxRate | Not Impacted | M | NORMAL | | SRTPROCTxRate | Not Impacted | M | NORMAL |
| | | | | | | | | |
+---------------------+---------------+-------+----------+ +---------------------+---------------+-------+----------+
RFC5159 Attribute Analysis RFC5159 Attribute Analysis
5.37. RFC6193 - Media Description for IKE in SDP 5.45. RFC6193 - Media Description for IKE in SDP
RFC6193 [RFC6193] specifies how to establish a media session that [RFC6193] specifies how to establish a media session that represents
represents a virtual private network using the Session Initiation a virtual private network using the Session Initiation Protocol for
Protocol for the purpose of on-demand media/application sharing the purpose of on-demand media/application sharing between peers. It
between peers. It extends the protocol identifier of the Session extends the protocol identifier of the Session Description Protocol
Description Protocol (SDP) so that it can negotiate use of the (SDP) so that it can negotiate use of the Internet Key Exchange
Internet Key Exchange Protocol (IKE) for media sessions in the SDP Protocol (IKE) for media sessions in the SDP offer/answer model.
offer/answer model.
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
| ike-setup | Attribute MUST be | B | IDENTICAL | | ike-setup | Attribute MUST be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
| | m=lines | | | | | m=lines | | |
| | | | | | | | | |
| psk-fingerprint | Attribute MUST be | B | IDENTICAL | | psk-fingerprint | Attribute MUST be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
skipping to change at page 33, line 8 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.38. RFC6064 - SDP and RTSP Extensions for 3GPP 5.46. 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 [RFC6064] provides information about with some extensions. [RFC6064] provides information about these
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 |
+--------------------------+--------------+-------+-----------------+ +-------------------------------+------------+-------+--------------+
| X-predecbufsize | Refer to | M | NOT RECOMMENDED | | X-predecbufsize | Refer to | M | NOT |
| | notes below | | | | | notes | | RECOMMENDED |
| | | | | | | below | | |
| X-initpredecbufperiod | Refer to | M | NOT RECOMMENDED | | | | | |
| | notes below | | | | X-initpredecbufperiod | Refer to | M | NOT |
| | | | | | | notes | | RECOMMENDED |
| X-initpostdecbufperiod | Refer to | M | NOT RECOMMENDED | | | below | | |
| | notes below | | | | | | | |
| | | | | | X-initpostdecbufperiod | Refer to | M | NOT |
| X-decbyterate | Refer to | M | NOT RECOMMENDED | | | notes | | RECOMMENDED |
| | notes below | | | | | below | | |
| | | | | | | | | |
| 3gpp-videopostdecbufsize | Refer to | M | NOT RECOMMENDED | | X-decbyterate | Refer to | M | NOT |
| | notes below | | | | | notes | | RECOMMENDED |
| | | | | | | below | | |
| framesize | The | M | IDENTICAL-PER- | | | | | |
| | attribute | | PT | | 3gpp-videopostdecbufsize | Refer to | M | NOT |
| | value must | | | | | notes | | RECOMMENDED |
| | be same for | | | | | below | | |
| | a given | | | | | | | |
| | codec config | | | | framesize | Refer to | M | NOT |
| | uration | | | | | notes | | RECOMMENDED |
| | | | | | | below | | |
| 3GPP-Integrity-Key | Refer to | S | NOT RECOMMENDED | | | | | |
| | notes below | | | | 3GPP-Integrity-Key | Refer to | S | NOT |
| | | | | | | notes | | RECOMMENDED |
| 3GPP-SRTP-Config | Refer to | M | NOT RECOMMENDED | | | below | | |
| | notes below | | | | | | | |
| | | | | | 3GPP-SDP-Auth | Refer to | S | NOT |
| alt,alt-default-id | Refer to | M | NOT RECOMMENDED | | | notes | | RECOMMENDED |
| | notes below | | | | | below | | |
| | | | | | | | | |
| alt-group | Refer to | M | NOT RECOMMENDED | | 3GPP-SRTP-Config | Refer to | M | NOT |
| | notes below | | | | | notes | | RECOMMENDED |
| | | | | | | below | | |
| 3GPP-Adaptation-Support | Refer to | M | NOT RECOMMENDED | | | | | |
| | notes below | | | | alt,alt-default-id | Refer to | M | NOT |
| | | | | | | notes | | RECOMMENDED |
| 3GPP-Asset-Informatio | Refer to | B | NOT RECOMMENDED | | | below | | |
| | notes below | | | | | | | |
| | | | | | alt-group | Refer to | M | NOT |
| mbms-mode | Refer to | B | NOT RECOMMENDED | | | notes | | RECOMMENDED |
| | notes below | | | | | below | | |
| | | | | | | | | |
| mbms-flowid | MRefer to | M | NOT RECOMMENDED | | 3GPP-Adaptation-Support | Refer to | M | NOT |
| | notes below | | | | | notes | | RECOMMENDED |
| | | | | | | below | | |
| mbms-repair | Refer to | B | NOT RECOMMENDED | | | | | |
| | notes below | | | | 3GPP-Asset-Informatio | Refer to | B | NOT |
| | | | | | | notes | | RECOMMENDED |
| 3GPP-QoE- | Refer to | M | NOT RECOMMENDED | | | below | | |
| Metrics:Corruption | notes below | | | | | | | |
| duration | | | | | mbms-mode | Refer to | B | NOT |
| | | | | | | notes | | RECOMMENDED |
| 3GPP-QoE- | Refer to | M | NOT RECOMMENDED | | | below | | |
| Metrics:Rebuffering | notes below | | | | | | | |
| duration | | | | | mbms-flowid | Refer to | M | NOT |
| | | | | | | notes | | RECOMMENDED |
| 3GPP-QoE-Metrics:Initial | Refer to | M | NOT RECOMMENDED | | | below | | |
| buffering duration | notes below | | | | | | | |
| | | | | | mbms-repair | Refer to | B | NOT |
| 3GPP-QoE- | Refer to | M | NOT RECOMMENDED | | | notes | | RECOMMENDED |
| Metrics:Successive loss | notes below | | | | | below | | |
| of RTP packets | | | | | | | | |
| | | | | | 3GPP-QoE-Metrics:Corruption | Refer to | M | NOT |
| 3GPP-QoE-Metrics:Frame | Refer to | M | NOT RECOMMENDED | | duration | notes | | RECOMMENDED |
| rate deviation | notes below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Jitter | Refer to | M | NOT RECOMMENDED | | 3GPP-QoE-Metrics:Rebuffering | Refer to | M | NOT |
| duration | notes below | | | | duration | notes | | RECOMMENDED |
| | | | | | | below | | |
| 3GPP-QoE-Metrics:Content | Refer to | B | NOT RECOMMENDED | | | | | |
| Switch Time | notes below | | | | 3GPP-QoE-Metrics:Initial | Refer to | M | NOT |
| | | | | | buffering duration | notes | | RECOMMENDED |
| 3GPP-QoE-Metrics:Average | Refer to | M | NOT RECOMMENDED | | | below | | |
| Codec Bitrat | notes below | | | | | | | |
| | | | | | 3GPP-QoE-Metrics:Successive | Refer to | M | NOT |
| 3GPP-QoE-Metrics:Codec | Refer to | M | NOT RECOMMENDED | | loss of RTP packets | notes | | RECOMMENDED |
| Information | notes below | | | | | below | | |
| | | | | | | | | |
| 3GPP-QoE-Metrics:Buffer | Refer to | M | NOT RECOMMENDED | | 3GPP-QoE-Metrics:Frame rate | Refer to | M | NOT |
| Status | notes below | | | | deviation | notes | | RECOMMENDED |
| | | | | | | below | | |
+--------------------------+--------------+-------+-----------------+ | | | | |
| 3GPP-QoE-Metrics:Jitter | Refer to | M | NOT |
| duration | notes | | RECOMMENDED |
| | below | | |
| | | | |
| 3GPP-QoE-Metrics:Content | Refer to | B | NOT |
| Switch Time | notes | | RECOMMENDED |
| | below | | |
| | | | |
| 3GPP-QoE-Metrics:Average | Refer to | M | NOT |
| Codec Bitrat | notes | | RECOMMENDED |
| | below | | |
| | | | |
| 3GPP-QoE-Metrics:Codec | Refer to | M | NOT |
| Information | notes | | RECOMMENDED |
| | below | | |
| | | | |
| 3GPP-QoE-Metrics:Buffer | Refer to | M | NOT |
| Status | notes | | RECOMMENDED |
| | below | | |
| | | | |
+-------------------------------+------------+-------+--------------+
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.39. RFC3108 - ATM SDP 5.47. 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 |
skipping to change at page 36, line 39 skipping to change at page 42, line 34
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.40. 3GPP TS 24.182 5.48. 3GPP TS 26.114
[R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and
interaction
+----------------------+-------------------------+-------+----------+
| Name | Notes | Level | Category |
+----------------------+-------------------------+-------+----------+
| 3gpp_sync_info | Usage defined for the | M | NORMAL |
| | IP Multimedia Subsystem | | |
| | | | |
| 3gpp_MaxRecvSDUSize | Usage defined for the | M | NORMAL |
| | IP Multimedia Subsystem | | |
| | | | |
+----------------------+-------------------------+-------+----------+
3GPP TS 24.182 Attribute Analysis
5.49. 3GPP TS 24.182
[R3GPPTS24.182] specifies IP multimedia subsystem Custom Alerting
tones
3GPP TS 24.182 [R3GPPTS24.182] specifies IP multimedia subsystem
Custom Alerting 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.41. 3GPP TS 24.183 5.50. 3GPP TS 24.183
3GPP TS 24.183 [R3GPPTS24.183]specifies IP multimedia subsystem [R3GPPTS24.183] specifies IP multimedia subsystem Custom Ringing
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
5.42. 3GPP TS 24.229 5.51. 3GPP TS 24.229
3GPP TS 24.229 [R3GPPTS24.229]IP multimedia call control protocol [R3GPPTS24.229] specifies IP multimedia call control protocol based
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 | | |
| | | | | | | | | |
| visited-realm | Per media-level attribute | M | TRANSPORT | | visited-realm | Per media-level attribute | M | TRANSPORT |
| | MUST be used per | | | | | MUST be used per | | |
skipping to change at page 38, line 34 skipping to change at page 44, line 34
| 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.43. ITU T.38 5.52. ITU T.38
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 |
| | | | | | | | | |
| T38FaxFillBitRemoval | Not Impacted | S | NORMAL | | T38FaxFillBitRemoval | Not Impacted | S | NORMAL |
skipping to change at page 39, line 26 skipping to change at page 45, line 26
| T38FaxTranscodingJBIG | Not Impacted | S | NORMAL | | T38FaxTranscodingJBIG | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxRateManagement | Not Impacted | S | NORMAL | | T38FaxRateManagement | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxMaxBuffer | Not Impacted | S | NORMAL | | T38FaxMaxBuffer | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxMaxDatagram | Not Impacted | S | NORMAL | | T38FaxMaxDatagram | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxUdpEC | Not Impacted | S | NORMAL | | T38FaxUdpEC | Not Impacted | S | NORMAL |
| | | | | | | | | |
| T38FaxMaxIFP | Not Impacted | S | NORMAL |
| | | | |
| T38FaxUdpECDepth | Not Impacted | S | NORMAL |
| | | | |
| T38FaxUdpFECMaxSpan | Not Impacted | S | NORMAL |
| | | | |
| T38ModemType | Not Impacted | S | NORMAL |
| | | | |
+------------------------+---------------+-------+----------+ +------------------------+---------------+-------+----------+
Historic Attribute Analysis Historic 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.44. ITU-T H.248.15 5.53. ITU-T-REC.Q1970
[ITU-T-REC.Q1970] defines BICC IP bearer control protocol.
+--------+---------------+-------+----------+
| Name | Notes | Level | Category |
+--------+---------------+-------+----------+
| ipbcp | Not Impacted | S | NORMAL |
| | | | |
+--------+---------------+-------+----------+
ITU-T-REC.Q1970 Attribute Analysis
5.54. 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 | | |
| | via the local and remote | | | | | via the local and remote | | |
| | descriptors. The attribute itself | | | | | descriptors. The attribute itself | | |
| | is unaffected by multiplexing, but | | | | | is unaffected by multiplexing, but | | |
| | the packaged referenced in a | | | | | the packaged referenced in a | | |
skipping to change at page 40, line 15 skipping to change at page 46, line 21
| 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 | | |
| | via the local and remote | | | | | via the local and remote | | |
| | descriptors. The attribute itself | | | | | descriptors. The attribute itself | | |
| | is unaffected by multiplexing, but | | | | | is unaffected by multiplexing, but | | |
| | the packaged referenced in a | | | | | the packaged referenced in a | | |
| | specific use of the attribute may | | | | | specific use of the attribute may | | |
| | be impacted. Further analysis of | | | | | be impacted. Further analysis of | | |
| | each package is needed to | | | | | each package is needed to | | |
| | determine if there is an issue. | | | | | determine if there is an issue. | | |
| | This is only a concern in | | | | | This is only a concern in | | |
| | environments using a decomposed | | | | | environments using a decomposed | | |
| | server/gateway with H.248 signaled | | | | | server/gateway with H.248 signaled | | |
| | between them. The ITU-T will need | | | | | between them. The ITU-T will need | | |
| | to do further analysis of various | | | | | to do further analysis of various | | |
| | packages when they specify how to | | | | | packages when they specify how to | | |
| | signal the use of multiplexing to | | | | | signal the use of multiplexing to | | |
| | a gateway. | | | | | a gateway. | | |
| | | | | | | | | |
+-----------+------------------------------------+-------+----------+ +-----------+------------------------------------+-------+----------+
Historic Attribute Analysis Historic Attribute Analysis
5.45. RFC4975 - The Message Session Relay Protocol 5.55. RFC4975 - The Message Session Relay Protocol
RFC4975 [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 |
+-----------------------+---------------+-------+----------+ +-----------------------+---------------+-------+----------+
| accept-types | Not Impacted | M | NORMAL | | accept-types | Not Impacted | M | NORMAL |
| | | | | | | | | |
| accept-wrapped-types | Not Impacted | M | NORMAL | | accept-wrapped-types | Not Impacted | M | NORMAL |
| | | | | | | | | |
| max-size | Not Impacted | M | NORMAL | | max-size | Not Impacted | M | NORMAL |
| | | | | | | | | |
| path | Not Impacted | M | NORMAL | | path | Not Impacted | M | NORMAL |
| | | | | | | | | |
+-----------------------+---------------+-------+----------+ +-----------------------+---------------+-------+----------+
RFC4975 Attribute Analysis RFC4975 Attribute Analysis
5.46. Historical 5.56. Historical
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-Applcable | NOT |
| | attributes. | | RECOMMENDED | | | attributes. | | RECOMMENDED |
| | | | | | | | | |
| rtpred2 | Historic | Not-Applcable | NOT | | rtpred2 | Historic | Not-Applcable | NOT |
| | attributes. | | RECOMMENDED | | | attributes. | | RECOMMENDED |
| | | | | | | | | |
| PSCid | Not | Not-Applcable | TBD | | PSCid | Not | Not-Applcable | NORMAL |
| | Applicable | | | | | Applicable | | |
| | | | | | | | | |
| bc_service | Not | Not-Applcable | TBD | | bc_service | Not | Not-Applcable | NORMAL |
| | Applicable | | | | | Applicable | | |
| | | | | | | | | |
| bc_program | Not | Not-Applcable | TBD | | bc_program | Not | Not-Applcable | NORMAL |
| | Applicable | | | | | Applicable | | |
| | | | | | | | | |
| bc_service_package | Not | Not-Applcable | TBD | | bc_service_package | Not | Not-Applcable | NORMAL |
| | Applicable | | | | | Applicable | | |
| | | | | | | | | |
+---------------------+--------------+---------------+--------------+ +---------------------+--------------+---------------+--------------+
Unknowns Attribute Analysis Unknowns 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 |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
| bwtype:CT | Aggregate bandwidth for the | S | NORMAL | | bwtype:CT | Not Impacted | S | NORMAL |
| | conference | | |
| | | | | | | | | |
| bwtype:AS | As a session attribute, it | B | NORMAL | | bwtype:AS | As a session attribute, it | B | NORMAL |
| | specifies the session aggregate | | | | | specifies the session aggregate | | |
| | unless media-level b=RR and/or | | | | | unless media-level b=RR and/or | | |
| | b=RS attributes are used. Under | | | | | b=RS attributes are used. Under | | |
| | this interpretation the | | | | | this interpretation the | | |
| | multiplexing scheme has no impact | | | | | multiplexing scheme has no impact | | |
| | and thus NORMAL category applies. | | | | | and thus NORMAL category applies. | | |
| | | | | | | | | |
| bwtype:AS | For the media level usage,the | B | SUM | | bwtype:AS | For the media level usage, the | B | SUM |
| | aggregate of individual bandwidth | | | | | aggregate of individual bandwidth | | |
| | values is considered. | | | | | values is considered. | | |
| | | | | | | | | |
+------------+-----------------------------------+-------+----------+ +------------+-----------------------------------+-------+----------+
RFC4566 bwtype Analysis RFC4566 bwtype Analysis
6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth 6.2. RFC3556 - SDP Bandwidth Modifiers for RTCP Bandwidth
RFC3556 [RFC3556] defines an extension to the Session Description RFC3556 [RFC3556] defines an extension to the Session Description
Protocol (SDP) to specify two additional modifiers for the bandwidth Protocol (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,SUM | | bwtype:RS | Session level usage represents | B | NORMAL |
| | session aggregate and media | | | | | session aggregate and media level | | |
| | level usage indicates SUM of | | | | | usage indicates SUM of the | | |
| | the individual values while | | | | | individual values while | | |
| | multiplexing | | | | | multiplexing | | |
| | | | | | | | | |
| bwtype:RR | Session level usage represents | B | NORMAL,SUM | | bwtype:RR | Session level usage represents | B | NORMAL |
| | session aggregate and media | | | | | session aggregate and media level | | |
| | level usage indicates SUM of | | | | | usage indicates SUM of the | | |
| | 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 [RFC3890] defines a Session Description Protocol (SDP)
Transport Independent Application Specific Maximum (TIAS) bandwidth Transport Independent Application Specific Maximum (TIAS) bandwidth
modifier that does not include transport overhead; instead an modifier that does not include transport overhead; instead an
additional packet rate attribute is defined. The transport additional packet rate attribute is defined. The transport
independent bit-rate value together with the maximum packet rate can independent bit-rate value together with the maximum packet rate can
skipping to change at page 44, line 13 skipping to change at page 50, line 13
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 [RTCP-FB]. 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 [RFC4585] defines an extension to the Audio-visual Profile
(AVP) that enables receivers to provide, statistically, more (AVP) that enables receivers to provide, statistically, more
immediate feedback to the senders and thus allows for short-term immediate feedback to the senders and thus allows for short-term
adaptation and efficient feedback-based repair mechanisms to be adaptation and efficient feedback-based repair mechanisms to be
implemented. implemented.
+----------+-----------------------------------+-------+------------+ +----------+----------------------------+-------+-------------------+
| Attr | Notes | Level | Category | | Attr | Notes | Level | Category |
| Name | | | | | Name | | | |
+----------+-----------------------------------+-------+------------+ +----------+----------------------------+-------+-------------------+
| ack rpsi | Not Impacted | M | NORMAL | | ack rpsi | The attribute value must | M | IDENTICAL-PER-PT |
| | | | | | | be same for a given codec | | |
| ack app | Feedback parameters MUST be | M | SPECIAL | | | configuration | | |
| | handled in the app specific way | | | | | | | |
| | when multiplexed | | | | ack app | Feedback parameters MUST | M | SPECIAL |
| | | | | | | be handled in the app | | |
| nack | Not Impacted | M | NORMAL | | | specific way when | | |
| | | | | | | multiplexed | | |
| nack pli | Not Impacted | M | NORMAL | | | | | |
| | | | | | nack | The attribute value must | M | IDENTICAL-PER-PT |
| nack sli | Not Impacted | M | NORMAL | | | be same for a given codec | | |
| | | | | | | configuration | | |
| nack | Not Impacted | M | NORMAL | | | | | |
| rpsi | | | | | nack pli | The attribute value must | M | IDENTICAL-PER-PT |
| | | | | | | be same for a given codec | | |
| nack app | Feedback parameters MUST be | M | SPECIAL | | | configuration | | |
| | handled in the app specific way | | | | | | | |
| | when multiplexed | | | | nack sli | The attribute value must | M | IDENTICAL-PER-PT |
| | | | | | | be same for a given codec | | |
| trr-int | This attribute applies to RTP | M | IDENTICAL | | | configuration | | |
| | Session as a whole | | | | | | | |
| | | | | | nack | The attribute value must | M | IDENTICAL-PER-PT |
+----------+-----------------------------------+-------+------------+ | rpsi | be same for a given codec | | |
| | configuration | | |
| | | | |
| nack app | Feedback parameters MUST | M | SPECIAL |
| | be handled in the app | | |
| | specific way when | | |
| | multiplexed | | |
| | | | |
| trr-int | The attribute value must | M | IDENTICAL-PER-PT |
| | be same for a given codec | | |
| | 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 [RFC5104] specifies a few extensions to the messages defined
in the Audio-Visual Profile with Feedback (AVPF). They are helpful in the 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 Name | Notes | Level | Category | | Attr | Notes | Level | Category |
+-----------+--------------+-------+----------+ | Name | | | |
| ccm | Not Impacted | M | Normal | +-------+-------------------------------+-------+-------------------+
| | | | | | ccm | The attribute value must be | M | IDENTICAL-PER-PT |
+-----------+--------------+-------+----------+ | | same for a given codec | | |
| | configuration | | |
| | | | |
+-------+-------------------------------+-------+-------------------+
RFC5104 Attribute Analysis RFC5104 Attribute Analysis
7.3. RFC6285 - Unicast-Based RAMS 7.3. RFC6285 - Unicast-Based RAMS
+-----------+---------------+-------+----------+ +-------+-------------------------------+-------+-------------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-----------+---------------+-------+----------+ +-------+-------------------------------+-------+-------------------+
| nack rai | Not Impacted | M | NORMAL | | nack | The attribute value must be | M | IDENTICAL-PER-PT |
| | | | | | rai | same for a given codec | | |
+-----------+---------------+-------+----------+ | | 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 [RFC6679] specifies how Explicit Congestion Notification
(ECN) can be used with the Real-time Transport Protocol (RTP) running (ECN) can be used with the Real-time Transport Protocol (RTP) running
over UDP, using the RTP Control Protocol (RTCP) as a feedback over UDP, using the RTP Control Protocol (RTCP) as a feedback
mechanism. It defines a new RTCP Extended Report (XR) block for mechanism. It defines a new RTCP Extended Report (XR) block for
periodic ECN feedback, a new RTCP transport feedback message for periodic ECN feedback, a new RTCP transport feedback message for
skipping to change at page 46, line 34 skipping to change at page 53, line 34
by ensuring that feedback reports are forwarded to all receivers, by 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 [RFC6642]
memo discusses these cases and defines a new RTCP Third-Party Loss memo discusses these cases and defines a new RTCP Third-Party Loss
Report that can be used to inform receivers that the feedback target Report that can be used to inform receivers that the feedback target
is aware of some loss event, allowing them to suppress feedback. is 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 tllei | Not Impacted | M | NORMAL | | nack | The attribute value must be | M | IDENTICAL-PER-PT |
| | | | | | tllei | same for a given codec | | |
| nack pslei | Not Impacted | M | NORMAL | | | configuration | | |
| | | | | | | | | |
+-------------+---------------+-------+----------+ | nack | The attribute value must be | M | IDENTICAL-PER-PT |
| pslei | same for a given codec | | |
| | configuration | | |
| | | | |
+--------+------------------------------+-------+-------------------+
RFC6642 Attribute Analysis RFC6642 Attribute Analysis
7.6. RFC5104 - Codec Control Messages in AVPF 7.6. RFC5104 - Codec Control Messages in AVPF
+------------+--------------+-------+----------+
| Attr Name | Notes | Level | Category | +--------+------------------------------+-------+-------------------+
+------------+--------------+-------+----------+ | Attr | Notes | Level | Category |
| ccm fir | Not Impacted | M | NORMAL | | Name | | | |
| | | | | +--------+------------------------------+-------+-------------------+
| ccm tmmbr | Not Impacted | M | NORMAL | | ccm | The attribute value must be | M | IDENTICAL-PER-PT |
| | | | | | fir | same for a given codec | | |
| ccm tstr | Not Impacted | M | NORMAL | | | configuration | | |
| | | | | | | | | |
| ccm vbcm | Not Impacted | M | NORMAL | | ccm | The attribute value must be | M | IDENTICAL-PER-PT |
| | | | | | tmmbr | same for a given codec | | |
+------------+--------------+-------+----------+ | | configuration | | |
| | | | |
| ccm | The attribute value must be | M | IDENTICAL-PER-PT |
| tstr | same for a given codec | | |
| | configuration | | |
| | | | |
| ccm | The attribute value must be | M | IDENTICAL-PER-PT |
| vbcm | same for a given codec | | |
| | configuration | | |
| | | | |
+--------+------------------------------+-------+-------------------+
RFC5104 Attribute Analysis RFC5104 Attribute Analysis
8. group Attribute Analysis 8. group Attribute Analysis
This section analyzes SDP "group" semantics [GROUP-SEM]. 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 [RFC5888] defines a framework to group "m" lines in the
Session Description Protocol (SDP) for different purposes. Session 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 |
skipping to change at page 49, line 29 skipping to change at page 56, line 38
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| depend | The attribute value must be | M | IDENTICAL-PER-PT | | depend | The attribute value must be | M | IDENTICAL-PER-PT |
| mdc | same for a given codec | | | | mdc | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
RFC5583 Attribute Analysis RFC5583 Attribute Analysis
The usage of identical Payload Type values across multiplexed m=lines 8.6. RFC7104 - Duplication Grouping Semantics in the SDP
is described in [I-D.ietf-mmusic-sdp-bundle-negotiation].
[RFC7104] defines the semantics for grouping redundant streams in the
Session Description Protocol (SDP). The semantics defined in this
document are to be used with the SDP Grouping Framework. Grouping
semantics at the Synchronization Source (SSRC) level are also defined
in this document for RTP streams using SSRC multiplexing.
+------------+---------------+-------+----------+
| Name | Notes | Level | Category |
+------------+---------------+-------+----------+
| group:DUP | Not Impacted | S | NORMAL |
| | | | |
+------------+---------------+-------+----------+
RFC7104 Attribute Analysis
9. ssrc-group Attribute Analysis 9. ssrc-group Attribute Analysis
This section analyzes "ssrc-group" semantics [SSRC-GROUP]. 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 |
+---------+---------------+-------+----------+ +-------------------+---------------+-------+----------+
| FID | Not Impacted | M | NORMAL | | ssrc-group:FID | Not Impacted | M | NORMAL |
| | | | | | | | | |
| FEC | Not Impacted | M | NORMAL | | ssrc-group:FEC | Not Impacted | M | NORMAL |
| | | | | | | | | |
| FEC-FR | Not Impacted | M | NORMAL | | ssrc-groupFEC-FR | Not Impacted | M | NORMAL |
| | | | | | | | | |
+---------+---------------+-------+----------+ +-------------------+---------------+-------+----------+
RFC5576 Attribute Analysis RFC5576 Attribute Analysis
9.2. RFC7104 - Duplication Grouping Semantics in the SDP
+-----------------+---------------+-------+----------+
| Name | Notes | Level | Category |
+-----------------+---------------+-------+----------+
| ssrc-group:DUP | Not Impacted | M | NORMAL |
| | | | |
+-----------------+---------------+-------+----------+
RFC7104 Attribute Analysis
10. QoS Mechanism Token Analysis 10. QoS Mechanism Token Analysis
This section analyzes QoS tokes specified with SDP[QOS]. This section analyzes QoS tokes specified with SDP.
10.1. RFC5432 - QoS Mechanism Selection in SDP 10.1. RFC5432 - QoS Mechanism Selection in SDP
+-------+----------------------------------------+-------+----------+ +-------+----------------------------------------+-------+----------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+-------+----------------------------------------+-------+----------+ +-------+----------------------------------------+-------+----------+
| rsvp | Not Impacted, since QOS mechanisms are | B | NORMAL | | rsvp | Not Impacted, since QOS mechanisms are | B | NORMAL |
| | applied per flow. | | | | | applied per flow. | | |
| | | | | | | | | |
| nsis | Not Impacted, since QOS mechanisms are | B | NORMAL | | nsis | Not Impacted, since QOS mechanisms are | B | NORMAL |
| | applied per flow. | | | | | applied per flow. | | |
| | | | | | | | | |
+-------+----------------------------------------+-------+----------+ +-------+----------------------------------------+-------+----------+
skipping to change at page 51, line 25 skipping to change at page 59, line 9
| content:alt | Not Impacted | M | NORMAL | | content:alt | Not Impacted | M | NORMAL |
| | | | | | | | | |
+------------------+---------------+-------+----------+ +------------------+---------------+-------+----------+
RFC4796 Attribute Analysis RFC4796 Attribute Analysis
13. Payload Formats 13. Payload Formats
13.1. RFC5109 - RTP Payload Format for Generic FEC 13.1. RFC5109 - RTP Payload Format for Generic FEC
RFC5109 [RFC5109] describes a payload format for generic Forward [RFC5109] describes a payload format for generic Forward Error
Error Correction (FEC) for media data encapsulated in RTP. It is Correction (FEC) for media data encapsulated in RTP. It is based on
based on the exclusive-or (parity) operation. The payload format the exclusive-or (parity) operation. The payload format allows end
allows end systems to apply protection using various protection systems to apply protection using various protection lengths and
lengths and levels, in addition to using various protection group levels, in addition to using various protection group sizes to adapt
sizes to adapt to different media and channel characteristics. It to different media and channel characteristics. It enables complete
enables complete recovery of the protected packets or partial recovery of the protected packets or partial recovery of the critical
recovery of the critical parts of the payload depending on the packet parts of the payload depending on the packet loss situation.
loss situation.
+---------------------+----------------------+-------+--------------+ +---------------------+----------------------+-------+--------------+
| Name | Notes | Level | Category | | Name | Notes | Level | Category |
+---------------------+----------------------+-------+--------------+ +---------------------+----------------------+-------+--------------+
| audio/ulpfec | Not recommended for | M | NOT | | audio/ulpfec | Not recommended for | M | NOT |
| | multiplexing due to | | RECOMMENDED | | | multiplexing due to | | RECOMMENDED |
| | reuse of SSRCs | | | | | reuse of SSRCs | | |
| | | | | | | | | |
| video/ulpfec | Not recommended for | M | NOT | | video/ulpfec | Not recommended for | M | NOT |
| | multiplexing due to | | RECOMMENDED | | | multiplexing due to | | RECOMMENDED |
skipping to change at page 52, line 32 skipping to change at page 59, line 45
| | reuse of SSRCs | | | | | reuse of SSRCs | | |
| | | | | | | | | |
+---------------------+----------------------+-------+--------------+ +---------------------+----------------------+-------+--------------+
RFC5109 Payload Format Analysis RFC5109 Payload Format Analysis
Draft draft-lennox-payload-ulp-ssrc-mux proposes a simple fix to make Draft draft-lennox-payload-ulp-ssrc-mux proposes a simple fix to make
it possible to use ULP with multiplexing and ULP is allowed when used it possible to use ULP with multiplexing and ULP is allowed when used
with that. with that.
14. Multiplexing Media Streams and DSCP Markings 14. Multiplexing Considerations for Encapsulating Attributes
Note: This section does not yet have WG consensus but is included as
a proposal to the WG. There are two options being proposed, A and B.
The authors suggest A.
14.1. Option A
This section provides two rules for multiplexing multiple media
streams with DSCP markings over a single 5-tuple.
Rule 1: Media Streams with markings from different service classes
MUST NOT be multiplexed. For example, a media stream with DSCP
Marking EF MUST NOT be multiplexed with a media stream marked with
AF class. Likewise, a media stream with DSCP marking AF3x MUST
NOT be multiplexed with a media stream marked with AF4x.
Rule 2: Media Streams that belong to the same service class, even
with different drop precedence, MAY be multiplexed. Thus media
streams that all belong to the EF group or all that belong to the
AF4X class can be multiplexed.
For WebRTC applications following the advice in
[I-D.dhesikan-tsvwg-rtcweb-qos], the above rules end up allowing the
audio and video to be multiplexed in many, but not all, cases.
14.2. Option B
Media Streams MAY be multiplexed regardless of what the setting of
the DSCP Per Hop Behavior group (PHB).
15. Multiplexing Considerations for Encapsulating Attributes
This sections deals with recommendations for defining the This sections deals with recommendations for defining the
multiplexing characteristics of the SDP attributes that encapsulate multiplexing characteristics of the SDP attributes that encapsulate
other SDP attributes/parameters. Such attributes as of today, for other SDP attributes/parameters. Such attributes as of today, for
example, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of example, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of
a generic framework for indicating and negotiating transport, media a generic framework for indicating and negotiating transport, media
and media format related capabilities in the SDP. and media format related capabilities in the SDP.
The behavior of such attributes under multiplexing is in turn defined The behavior of such attributes under multiplexing is in turn defined
by the multiplexing behavior of the attributes they encapsulate which by the multiplexing behavior of the attributes they encapsulate which
are made known once the Offer/Answer negotiation process is are made known once the Offer/Answer negotiation process is
completed. completed.
15.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
referenced 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
m=video 3456 RTP/AVP 100 m=video 3456 RTP/AVP 100
a=rtpmap:100 VP8/90000 a=rtpmap:100 VP8/90000
a=sqn: 0 a=sqn: 0
a=cdsc: 1 video RTP/AVP 100 a=cdsc: 1 video RTP/AVP 100
a=cpar: a=rtcp-mux a=cpar: a=rtcp-mux
m=video 3456 RTP/AVP 101 m=video 3456 RTP/AVP 101
a=rtpmap:101 VP8/90000 a=rtpmap:101 VP8/90000
a=fmtp:100 max-fr=15;max-fs=1200 a=fmtp:100 max-fr=15;max-fs=1200
a=cdsc: 2 video RTP/AVP 101 a=cdsc: 2 video RTP/AVP 101
a=cpar: a=rtcp-mux a=cpar: a=rtcp-mux
In the above example ,the category IDENTICAL is inherited for the In the above example ,the category IDENTICAL is inherited for the
cpar encapsulated rtcp-mux attribute. cpar encapsulated rtcp-mux attribute.
15.2. RFC5939 Analysis 14.2. RFC5939 Analysis
[RFC5939] defines a general SDP capability negotiation framework. It [RFC5939] defines a general SDP capability negotiation framework. It
also specifies how to provide transport protocols and SDP attributes also specifies how to provide transport protocols and SDP attributes
as capabilities and negotiate them using the framework. as capabilities and negotiate them using the framework.
For this purpose, [RFC5939] defines the following For this purpose, [RFC5939] defines the following
o A set of capabilities for the session and its associated media o A set of capabilities for the session and its associated media
stream components, supported by each side. The attribute stream components, supported by each side. The attribute
("a=acap") defines how to list an attribute name and its ("a=acap") defines how to list an attribute name and its
associated value (if any) as a capability. The attribute associated value (if any) as a capability. The attribute
("a=tcap") that defines how to list transport protocols (e.g., ("a=tcap") defines how to list transport protocols (e.g., "RTP/
"RTP/AVP") as capabilities. AVP") as capabilities.
o A set of potential configurations indicating which combinations of o A set of potential configurations ("a=pcfg") provided by the
those capabilities can be used for the session and its associated offerer to indicate whcich combination of those capabilities can
media stream components. Potential configurations are not ready be used for the session and its associated media stream
for use. Instead, they provide an alternative that may be used, components. Potential configurations are not ready for use until
subject to further negotiation. fully negotiated. They provide an alternative that may be used,
subject to SDP capability negotiation procedures. In particular
the answerer may choose one of the potential configurations for
use as part of the current Offer/Answer exchange.
o An actual configuration for the session and its associated media o An actual configuration ("a=acfg") for the session and its
stream components, that specifies which combinations of session associated media stream components. The actual configuration
parameters and media stream components can be used currently and identifies the potential configuration that was negotiated for
with what parameters. Use of an actual configuration does not use. Use of an actual configuration does not require any further
require any further negotiation. negotiation.
o A negotiation process that takes the set of actual and potential o A negotiation process that takes the current actual and the set of
configurations (combinations of capabilities) as input and potential configurations (combinations of capabilities) as input
provides the negotiated actual configurations as output. and provides the negotiated actual configurations as output. In
[RFC5939] the negotiation process is done independently for each
media description.
15.2.1. Recommendations 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. consistent between those streams. In particular, the procedures aim
to simply Answerer's procedure to choose potential configurations
that are consistent across all the bundled media descriptions.
15.2.1.1. Recommendation-1: Transport Capability Analysis A potential configuration selects a set of attributes and parameters
that become part of the media description when negotiated. When
multiplexing media descriptions with potential configurations
specified, there may be a need for coordinating this selection
between multiplexed media descriptions ensuring right multiplexing
behavior.
When a transport capability is proposed as a potential configuration Although it is possible to analyze the various potential
under a given media description, it is recommended that all the media configurations in bundled media descriptions to find combinations
descriptions under multiplexing have the same potential configuration that satisfy such constraints, it can quickly become complicated to
number for the given transport capability. do so.
The procedures defined in [RFC5939] state that each potential
configuration in the SDP has a unique configuration number, however
the scope of uniqueness is limited to each media description. To
make it simple for the answerer to chose valid combinations of
potential configurations across media descriptions in a given bundle
group, we provide a simple rule for constructiong potential
configurations:-
o Let m-bundle be the set of media descriptions that form a given
bundle .
o Let m-bundle-pcfg be the set of media descriptions in m-bundle
that include one or more potential configurations.
o Each media description in m-bundle-pcfg MUST have at least one
potential configuration with the same configuration number (e.g.
"1").
o For each potential configuration with configuration number x in m-
bundle-pcfg, the offerer MUST ensure that if the answerer chooses
configuration number x in each of the media descriptions in m-
bundle-pcfg, then the resulting SDP will have all multiplexing
constraints satisfied for those media descriptions.
o Since it is nearly impossible to define a generic mechanism for
various capability extensions , this document does't provide
procedures for dealing with the capability extension attributes.
However, Section Section 14.3 provide analysis of media capability
extension attributes as defined in [RFC6871].
The above allows the answerer to easily find multiplexing compatible
combinations of potential configurations:- The answerer simply choses
a potential configuration (number) that is present in all of the
media descriptions with potential configurations in the bundle.
Note that it is still possible for the offerer to provide additional
potential configurations with independent configuration numbers. The
answerer will have to perform more complicated analysis to determine
valid multiplexed combinations of those.
14.2.1.1. Example: Transport Capability Multiplexing
v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s=
c=IN IP4 host.atlanta.example.com
t=0 0
a=tcap:1 RTP/SAVPF a=tcap:1 RTP/SAVPF
a=tcap:2 RTP/SAVP a=tcap:2 RTP/SAVP
a=group:BUNDLE audio video a=group:BUNDLE audio video
m= audio m= audio
a=mid:audio a=mid:audio
a=pcfg:1 t=1 a=pcfg:1 t=1
a=pcfg:2 a=pcfg:2
m= video m= video
a=mid:video a=mid:video
a=pcfg:1 t=1 a=pcfg:1 t=1
a=pcfg:2 t=2 a=pcfg:2 t=2
In the example above, the potential configurations that Offer In the example above, the potential configurations that offer
transport protocol capability of RTP/SAVPF has the same configuration transport protocol capability of RTP/SAVPF has the same configuration
number "1" in both the audio and video media descriptions. number "1" in both the audio and video media descriptions.
15.2.1.2. Recommendation-2: Attribute Capability Analysis 14.2.1.2. Example: Attribute Capability Multiplexing
For attribute capabilities which are offered as potential
configurations that encapsulate attributes whose value MUST be
IDENTICAL under multiplexing, it is recommended that all the media
descriptions under multiplexing have the same potential configuration
number for the given attribute capability.
v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s=
c=IN IP4 host.atlanta.example.com
t=0 0
a=acap:1 a=rtcp-mux a=acap:1 a=rtcp-mux
a=acap:2 a=crypto:1 AES_CM_128_HMAC_SHA1_80 a=acap:2 a=crypto:1 AES_CM_128_HMAC_SHA1_80
inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32 inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32
a=group:BUNDLE audio video a=group:BUNDLE audio video
m= audio 49172 RTP/AVP 99 m= audio 49172 RTP/AVP 99
a=mid:audio a=mid:audio
a=pcfg:1 a=1 a=pcfg:1 a=1
a=pcfg:2 a=pcfg:2
m= video 560024 RTP/AVP 100 m= video 560024 RTP/AVP 100
a=mid:video a=mid:video
a=pcfg:1 a=1 a=pcfg:1 a=1
a=pcfg:2 a=2 a=pcfg:2 a=2
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.
15.2.1.3. Recommendation-3: Sescap Attribute Analysis 14.3. RFC6871 Analysis
It is recommended that any bundled media descriptions/configurations
are also acceptable combinations of media streams/configurations as
specified by "sescap" attribute.
15.2.1.4. Recommendation-4: Capability Extension Attributes
Since it is nearly impossible to define a generic mechanism for
various capability extensions , this document does't provide
procedures for dealing with the capability extension attributes.
However, Section Section 15.3 provide analysis of media capability
extension attributes as defined in [RFC6871].
15.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. and negotiate media types and their associated format parameters. It
also allows indication of latent configurations and session
capabilities (the latter of which is not recommended for use with
bundled media as described in Section 5.29).
Building upon the analysis from the previous section, following 14.3.1. Recommendation: Dealing with Payload Type Numbers
recommendation is provided for dealing with the attributes defined in
[RFC6871] under multiplexing
15.3.1. Recommendation-5: Attribute Capability Under Shared Payload RFC 6871 defines a new payload type ("pt") parameter to be used with
Type the potential, actual and latent configuration parameters. The
parameter associates RTP payload type numbers with the referenced
RTP-based media format capabilities ("a=rmcap") defined in [RFC6871]
and is appropriate only when the transport protocol uses RTP. This
means that the same payload type number can be assigned as part of
potential or actual configurations in different media descriptions in
a bundle. There are rules for the usage of identical Payload Type
values across multiplexed m=lines as described in [I-D.ietf-mmusic-
sdp-bundle-negotiation], which MUST be followed here as well. As
described in Section 15.2, the use of identical configuration numbers
for compatible configurations in different media descriptions that
are part of the bundle provides a way to ensure that the answerer can
easily pick compatible configurations here as well.
For attribute capabilities which are offered as potential 14.3.1.1. Example: Attribute Capability Under Shared Payload Type
configurations that encapsulate attributes whose value MUST be
IDENTICAL-PER-PT under multiplexing, it is recommended that all the
media descriptions under multiplexing have the same potential
configuration number for the given attribute capability
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
skipping to change at page 57, line 37 skipping to change at page 65, line 37
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
15.4. Recommendation-6: Offer/Answer Negotiation Expectations 14.3.2. Recommendation: Dealing with Latent Configurations
For attributes encapsulated via "a=acap", "a=omcap", "a=mscap" RFC 6871 adds the notion of a latent configurations, which provides
capability attributes and presented as part of potential/actual configuration information that may be used to guide a subsequent
configurations during the Offer/Answer negotiation prodecure, the offer/exchange, e.g. by adding another media stream or use
negotiation MUST ensure that the multiplexing behavior of these alternative codec combinations not currently offered. Latent
capabilities inherit from the behavior of the attribute being configurations have configuration numbers which cannot overlap with
encapsulated. the potential configuration numbers [RFC6871]. Supported
combinations of potential and latent configurations are indicated by
use of the "a=sescap" attribute, however use of this attribute is not
recommended with bundled media, since it requires the use of unique
configuration numbers across the SDP. Taken together, this means
there is no well-defined way to indicate supported combinations of
latent configurations, or combinations of latent and potential
configurations with bundled media. It is still allowed to use the
latent configuration attribute, however the limitations above will
apply. To determine valid combinations, actual negotiation will have
to be attempted subsequently instead.
Example 1: Below SDP example captures the following aspects. 15. IANA Considerations
o The Offerer offers audio and video streams with several different [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
RTP profiles (AVP, SAVP, SAVPF) as potential configurations. document.]
o Valid Answer that corresponds to the SDP answer where the Answerer The IANA is requested to add a new column named "Mux Category" to all
accepts RTP/SAVPF as the default profile for both the media several of the registries in the "Session Description Protocol (SDP)
streams. In this scenario both the media streams can be Parameters". Section Section 15.1 defines the new registry for
successfully multiplexed. identifying the initial registrations for "Mux Category" as proposed
in this document. The tables in Section 15.2 identify name of an
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.
o Invalid Answer wherein the Answerer accepts the profile RTP/SAVPF 15.1. New Column 'Mux Category'
for the audio stream and RTP/AVPF for the video stream. This
scenario results in the failure of the multiplexing as defined in
the section 7.2 of the BUNDLE specification [I-D.ietf-mmusic-sdp-
bundle-negotiation].
<Offer-SDP> A new registry needs to be setup for specifying possible values for
v=0 the "Mux Category" column, with the following registrations created
o=- 25678 753849 IN IP4 192.0.2.1 initially: "NORMAL", "NOT RECOMMENDED", "IDENTICAL", "TRANSPORT",
s= "IDENTICAL-PER-PT", SPECIAL" and "TBD" as defined in this document.
t=0 0
c=IN IP4 192.0.2.1
m=audio 3456 RTP/AVP 98
a=tcap:1 RTP/SAVPF
a=rtpmap:98 OPUS/48000/2
a=pcfg:1 t=1
m=video 51372 RTP/AVP 101
a=rtpmap:101 H264/90000
a=tcap:2 RTP/SAVPF RTP/AVPF
a=pcfg:2 t=2|3
<Valid Answer> Initial value registration for the column "Mux Category".
v=0
o=- 24351 621814 IN IP4 192.0.2.2
s=
m=audio 3456 RTP/SAVPF 98
a=rtpmap:98 OPUS/48000/2
a=acfg:1 t=1
m=video 51372 RTP/SAVPF 101 Value name: NORMAL
a=rtpmap:101 H264/90000 Reference : RFCXXXX
a=acfg:2 t=2
<Invalid Answer> Value name: NOT RECOMMENDED
v=0 Reference : RFCXXXX
o=- 24351 621814 IN IP4 192.0.2.2
s=
m=audio 3456 RTP/SAVPF 98
a=rtpmap:98 OPUS/48000/2
a=acfg:1 t=1
m=video 51372 RTP/AVPF 101 Value name: IDENTICAL
a=rtpmap:101 H264/90000 Reference : RFCXXXX
a=acfg:2 t=3
16. IANA Considerations Value name: TRANSPORT
Reference : RFCXXXX
IANA shall register categories from this specification by expanding Value name: IDENTICAL-PER-PT
the Session Description Protocol (SDP) Parameters table with a column Reference : RFCXXXX
listing categories against each SDP parameter.
+---------------------+ Value name: SPECIAL
| Category | Reference : RFCXXXX
+---------------------+
| NORMAL |
+---------------------+
| NOT RECOMMENDED |
+---------------------+
| IDENTICAL |
+---------------------+
| TRANSPORT |
+---------------------+
| INHERIT |
----------------------+
| IDENTICAL-PER-PT |
+---------------------+
| SPECIAL |
----------------------
17. Security Considerations Value name: TBD
Reference : RFCXXXX
All the attributes which involve security key needs a careful review Further entries may be registered on a first-come first-serve basis.
to ensure two-time pad vulnerability is not created. 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.
18. Acknowledgments 15.2. 'Mux Category' values for SDP Registries
The various sub-sections below assigns the values to be used for the
"Mux Category" column for the corresponding registries idenfied.
15.2.1. Table: SDP bwtype
The following values are to be added to the 'SDP bwtype' registry in
the "Session Description Protocol (SDP) Parameters. The references
should be updated to point at this RFC as well as the previous
references.
+-------+--------------+
| Type | Mux Category |
+-------+--------------+
| CT | NORMAL |
| AS | SUM |
| RS | NORMAL |
| RR | NORMAL |
| TIAS | SPECIAL |
+-------+--------------+
15.2.2. Table: att-field
The following values are to be added to the 'att-field' registry in
the "Session Description Protocol (SDP) Parameters. The references
should be updated to point at this RFC as well as the previous
references.
+---------------------------+-------------------+
| 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 |
| orient | NORMAL |
| orient:portrait | NORMAL |
| orient:landscape | NORMAL |
| orient:seascape | NORMAL |
| framerate | IDENTICAL-PER-PT |
| quality | NORMAL |
| rtpmap | IDENTICAL-PER-PT |
| fmtp | IDENTICAL-PER-PT |
| rtpred1 | NOT RECOMMENDED |
| rtpred2 | NOT RECOMMENDED |
| T38FaxVersion | NORMAL |
| T38MaxBitRate | NORMAL |
| T38MaxBitRate | NORMAL |
| T38FaxTranscodingMMR | NORMAL |
| T38FaxTranscodingJBIG | NORMAL |
| T38FaxRateManagement | NORMAL |
| T38FaxMaxBuffer | NORMAL |
| T38FaxMaxDatagram | NORMAL |
| T38FaxUdpEC | NORMAL |
| maxptime | IDENTICAL-PER-PT |
| des | NORMAL |
| curr | NORMAL |
| conf | NORMAL |
| mid | NORMAL |
| rtcp | IDENTICAL |
| rtcp-fb | IDENTICAL-PER-PT |
| label | NORMAL |
| T38VendorInfo | NORMAL |
| crypto | TRANSPORT |
| eecid | NORMAL |
| aalType | NORMAL |
| capability | NORMAL |
| qosClass | NORMAL |
| bcob | NORMAL |
| stc | NORMAL |
| upcc | NORMAL |
| atmQOSparms | NORMAL |
| atmQOSparms | NORMAL |
| abrParms | NORMAL |
| abrSetup | NORMAL |
| bearerType | NORMAL |
| lij | NORMAL |
| anycast | NORMAL |
| cache | NORMAL |
| bearerSigIE | NORMAL |
| aalApp | NORMAL |
| cbrRate | NORMAL |
| sbc | NORMAL |
| clkrec | NORMAL |
| fec | NORMAL |
| prtfl | NORMAL |
| structure | NORMAL |
| cpsSDUsize | NORMAL |
| all2CPS | NORMAL |
| all2CPSSDUrate | NORMAL |
| aal2sscs3661unassured | NORMAL |
| aal2sscs3661assured | NORMAL |
| aal2sscs3662 | NORMAL |
| aal5sscop | NORMAL |
| atmmap | NORMAL |
| silenceSupp | NORMAL |
| ecan | NORMAL |
| gc | NORMAL |
| profileDesc | NORMAL |
| vsel | NORMAL |
| dsel | NORMAL |
| fsel | NORMAL |
| onewaySel | NORMAL |
| codecConfig | NORMAL |
| isup_usi | NORMAL |
| uiLayer1_Prot | NORMAL |
| chain | NORMAL |
| floorctrl | IDENTICAL |
| confid | NORMAL |
| userid | NORMAL |
| floorid | NORMAL |
| FEC | NORMAL |
| profileDesc | NORMAL |
| accept-types | NORMAL |
| accept-wrapped-types | NORMAL |
| max-size | NORMAL |
| path | NORMAL |
| dccp-service-code | NOT RECOMMENDED |
| rtcp-mux | IDENTICAL |
| candidate | TRANSPORT |
| ice-mismatch | NORMAL |
| remote-candidates | TRANSPORT |
| SRTPAuthentication | NORMAL |
| SRTPROCTxRate | NORMAL |
| rtcp-rsize | IDENTICAL |
| file-selector | NORMAL |
| file-transfer-id | NORMAL |
| file-disposition | NORMAL |
| file-date | NORMAL |
| file-icon | NORMAL |
| file-range | NORMAL |
| depend | IDENTICAL-PER-PT |
| ssrc | NORMAL |
| ssrc-group | NORMAL |
| rtcp-unicast | IDENTICAL |
| pcfg | SPECIAL |
| acfg | SPECIAL |
| zrtp-hash | NOT RECOMMENDED |
| X-predecbufsize | NOT RECOMMENDED |
| X-initpredecbufperiod | NOT RECOMMENDED |
| X-initpostdecbufperiod | NOT RECOMMENDED |
| X-decbyterate | NOT RECOMMENDED |
| 3gpp-videopostdecbufsize | NOT RECOMMENDED |
| framesize | NOT RECOMMENDED |
| 3GPP-SRTP-Config | NOT RECOMMENDED |
| alt | NOT RECOMMENDED |
| alt-default-id | NOT RECOMMENDED |
| 3GPP-Adaption-Support | NOT RECOMMENDED |
| mbms-flowid | NOT RECOMMENDED |
| fec-source-flow | SPECIAL |
| fec-repair-flow | SPECIAL |
| repair-window | SPECIAL |
| rams-updates | NOT RECOMMENDED |
| imageattr | IDENTICAL-PER-PT |
| cfw-id | NORMAL |
| portmapping-req | NOT RECOMMENDED |
| g.3gpp.cat | NORMAL |
| g.3gpp.crs | NORMAL |
| ecm-capable-rtp | IDENTICAL-PER-PT |
| visited-realm | TRANSPORT |
| secondary-realm | TRANSPORT |
| omr-s-cksum | NORMAL |
| omr-m-Cksum | NORMAL |
| omr-codecs | NORMAL |
| omr-codecs | NORMAL |
| omr-m-att | NORMAL |
| omr-m-bw | NORMAL |
| omr-s-bw | NORMAL |
| msrcp-cema | NORMAL |
| dccp-port | NOT RECOMMENDED |
| resource | NORMAL |
| channel | NORMAL |
| cmid | NORMAL |
| content | NORMAL |
| lcfg | SPECIAL |
| loopback | NORMAL |
| loopback-source | NORMAL |
| loopback-mirror | NORMAL |
| chatroom | TBD |
| altc | TRANSPORT |
| T38FaxMaxIFP | NORMAL |
| T38FaxUdpECDepth | NORMAL |
| T38FaxUdpFECMaxSpan | NORMAL |
| T38ModemType | NORMAL |
| cs-correlation | NORMAL |
| rtcpidms | NORMAL |
| cname | NORMAL |
| previous-ssrc | NORMAL |
| fmtp | IDENTICAL-PER-PT |
+---------------------------+-------------------+
15.2.3. Table: content SDP Parameters
The following values are to be added to the 'content SDP Parameters'
registry in the "Session Description Protocol (SDP) Parameters. The
references should be updated to point at this RFC as well as the
previous references.
+----------+--------------+
| SDP Name | Mux Category |
+----------+--------------+
| slides | NORMAL |
| speaker | NORMAL |
| sl | NORMAL |
| main | NORMAL |
| alt | NORMAL |
+----------+--------------+
15.2.4. Table: Semantics for the 'group' SDP Attribute
The following values are to be added to the Semantics for the "group"
SDP Attribute registry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as
well as the previous references.
+---------+------------------+
| Token | Mux Category |
+---------+------------------+
| LS | NORMAL |
| FID | NORMAL |
| SRF | NORMAL |
| ANAT | NOT RECOMMENDED |
| FEC | NORMAL |
| FEC-FR | NORMAL |
| CS | NORMAL |
| DDP | NORMAL |
| DUP | NORMAL |
+---------+------------------+
15.2.5. Table: 'rtcp-fb' Attribute Values
The following values are to be added to the " 'rtcp-fb' Attribute
Values" registry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as
well as the previous references.
+------------+-------------------+
| Value Name | Mux Category |
+------------+-------------------+
| ack | IDENTICAL-PER-PT |
| app | SPECIAL |
| ccm | IDENTICAL-PER-PT |
| nack | IDENTICAL-PER-PT |
| trr-int | IDENTICAL-PER-PT |
+------------+-------------------+
15.2.6. Table: 'ack' and 'nack' Attribute Values
The following values are to be added to the " 'ack' and 'nack'
Attribute Values" registry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as
well as the previous references.
+------------+-------------------+
| Value Name | Mux Category |
+------------+-------------------+
| sli | IDENTICAL-PER-PT |
| pli | IDENTICAL-PER-PT |
| rpsi | IDENTICAL-PER-PT |
| app | IDENTICAL-PER-PT |
| rai | IDENTICAL-PER-PT |
| tllei | IDENTICAL-PER-PT |
| pslei | IDENTICAL-PER-PT |
| ecn | IDENTICAL-PER-PT |
+------------+-------------------+
15.2.7. Table: 'depend' SDP Attribute Values
The following values are to be added to the " 'depend' SDP Attribute
Values" registry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as
well as the previous references.
+-------+--------------+
| Token | Mux Category |
+-------+--------------+
| lay | NORMAL |
| mdc | NORMAL |
+-------+--------------+
15.2.8. Table: 'cs-correlation' Attribute Values
The following values are to be added to the " 'cs-correlation'
Attribute Values" registry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as
well as the previous references.
+-----------+--------------+
| Token | Mux Category |
+-----------+--------------+
| callerid | NORMAL |
| uuie | NORMAL |
| dtmf | NORMAL |
| external | NORMAL |
+-----------+--------------+
15.2.9. Table: Semantics for the 'ssrc-group' SDP Attribute
The following values are to be added to the Semantics for the "
'ssrc-group' SDP Attribute" registry in the "Session Description
Protocol (SDP) Parameters. The references should be updated to point
at this RFC as well as the previous references.
+---------+--------------+
| Token | Mux Category |
+---------+--------------+
| FID | NORMAL |
| FEC | NORMAL |
| FEC-FR | NORMAL |
| DUP | NORMAL |
+---------+--------------+
15.2.10. Table: SDP/RTSP key management protocol identifiers
The following values are to be added to the "SDP/RTSP key management
protocol identifiers" registry in the "Session Description Protocol
(SDP) Parameters. The references should be updated to point at this
RFC as well as the previous references.
+------------+--------------+
| Value Name | Mux Category |
+------------+--------------+
| mikey | IDENTICAL |
+------------+--------------+
15.2.11. Table: Codec Control Messages
The following values are to be added to the "Codec Control Messages"
registry in the "Session Description Protocol (SDP) Parameters. The
references should be updated to point at this RFC as well as the
previous references.
+------------+-------------------+
| Value Name | Mux Category |
+------------+-------------------+
| fir | IDENTICAL-PER-PT |
| tmmbr | IDENTICAL-PER-PT |
| tstr | IDENTICAL-PER-PT |
| vbcm | IDENTICAL-PER-PT |
+------------+-------------------+
15.2.12. Table: QoS Mechanism Tokens
The following values are to be added to the "QoS Mechanism Tokens"
registry in the "Session Description Protocol (SDP) Parameters. The
references should be updated to point at this RFC as well as the
previous references.
+---------------+--------------+
| QoS Mechanism | Mux Category |
+---------------+--------------+
| rsvp | NORMAL |
| nsis | NORMAL |
+---------------+--------------+
15.2.13. Table: SDP Capability Negotiation Option Tags
The following values are to be added to the "SDP Capability
Negotiation Option Tags" Registry in the "Session Description
Protocol (SDP) Parameters. The references should be updated to point
at this RFC as well as the previous references.
+---------------+--------------+
| QoS Mechanism | Mux Category |
+---------------+--------------+
| cap-v0 | NORMAL |
| med-v0 | NORMAL |
| bcap-v0 | NORMAL |
| ccap-v0 | NORMAL |
| icap-v0 | NORMAL |
+---------------+--------------+
15.2.14. Table: Timestamp Reference Clock Source Parameters
The following values are to be added to the "Timestamp Reference
Clock Source Parameters" Registry in the "Session Description
Protocol (SDP) Parameters. The references should be updated to point
at this RFC as well as the previous references.
+----------+--------------+
| Name | Mux Category |
+----------+--------------+
| ntp | NORMAL |
| ptp | NORMAL |
| gps | NORMAL |
| gal | NORMAL |
| glonass | NORMAL |
| local | NORMAL |
| private | NORMAL |
+----------+--------------+
15.2.15. Table: Media Clock Source Parameters
The following values are to be added to the "Media Clock Source
Parameters" Registry in the "Session Description Protocol (SDP)
Parameters. The references should be updated to point at this RFC as
well as the previous references.
+-----------+--------------+
| Name | Mux Category |
+-----------+--------------+
| sender | NORMAL |
| direct | NORMAL |
| IEEE1722 | NORMAL |
+-----------+--------------+
16. Security Considerations
This document does not add any new security considerations beyond the
existing considerations in the RFC for protocols that are being
multiplexed together.
The ways that SRTP streams are keyed is not believed to create any
two-time pad vulnerability for the currently defined SRTP keying
mechanism.
17. Acknowledgments
I would like to thank Cullen Jennings for suggesting the categories, I would like to thank Cullen Jennings for suggesting the categories,
contributing text and reviewing the draft. I would also link to contributing text and reviewing the draft. I would also link to
thank Magnus, Christer, Jonathan Lennox, Bo Burman, and Dan on thank Magnus, Christer, Jonathan Lennox, Bo Burman, and Dan on
suggesting structural changes helping improve the document suggesting structural changes helping improve the document
readability. 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,15), 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
skipping to change at page 61, line 5 skipping to change at page 78, line 47
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).
19. 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-02
o Incorporated suggestions from Flemming on Capability Negotiation.
o Closed open issues from IETF90
o Added IANA section to list the categories for all the SDP
attributes anlayzed
o Lots of cleanup
o Reformatted Refernces section to use short-form notation
Changes from draft-ietf-mmusic-sdp-mux-attributes-01 Changes from draft-ietf-mmusic-sdp-mux-attributes-01
o Updated section 15 to provide detailed recommendation on dealing o Updated section 15 to provide detailed recommendation on dealing
with encapsulating attributes. Also updated sections 5.20, 5.28, with encapsulating attributes. Also updated sections 5.20, 5.28,
5.29 to refer to Section 15. 5.29 to refer to Section 15.
o Added new categories IDENTICAL-PER-PT and INHERIT o Added new categories IDENTICAL-PER-PT and INHERIT
o Updated Sections 16 to add the new categories. o Updated Sections 16 to add the new categories.
skipping to change at page 62, line 36 skipping to change at page 80, line 42
o Replaced Category BAD with NOT RECOMMENDED. o Replaced Category BAD with NOT RECOMMENDED.
o Added Category TBD. o Added Category TBD.
o Updated IANA Consideration Section. o Updated IANA Consideration Section.
Changes from draft-nandakumar-mmusic-mux-attributes-00 Changes from draft-nandakumar-mmusic-mux-attributes-00
o Added new section for dealing with FEC payload types. o Added new section for dealing with FEC payload types.
20. References 19. References
20.1. Normative References 19.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
20.2. Informative References 19.2. Informative References
[ACK-NACK]
"S Description Protocol (SDP) RTCP ACK/NACK Feedback
attributes", <http://www.iana.org/assignments/sdp-
parameters/sdp-parameters.xml#sdp-parameters-15>.
[CCM] "S Description Protocol (SDP) RTCP-FB Codec Control
Messages", <http://www.iana.org/assignments/sdp-
parameters/sdp-parameters.xml#sdp-parameters-19>.
[GROUP-SEM]
"S Description Protocol (SDP) "group" semantics",
<http://www.iana.org/assignments/sdp-parameters/
sdp-parameters.xml#sdp-parameters-13>.
[H.248.15] [H.248.15]
"Gateway control protocol: SDP H.248 package attribute", "Gateway control protocol: SDP H.248 package attribute",
<http://www.itu.int/rec/T-REC-H.248.15>. <http://www.itu.int/rec/T-REC-H.248.15>.
[I-D.dhesikan-tsvwg-rtcweb-qos]
Dhesikan, S., Druta, D., Jones, P., and J. Polk, "DSCP and
other packet markings for RTCWeb QoS", draft-dhesikan-
tsvwg-rtcweb-qos-02 (work in progress), July 2013.
[I-D.ietf-avt-multiplexing-rtp]
El-Khatib, K., Luo, G., Bochmann, G., and Pinjiang. Feng,
"Multiplexing Scheme for RTP Flows between Access
Routers", http://tools.ietf.org/html/
draft-ietf-avt-multiplexing-rtp-01 (work in progress),
October 1999.
[I-D.ietf-mmusic-sdp-bundle-negotiation] [I-D.ietf-mmusic-sdp-bundle-negotiation]
Holmberg, C., Alvestrand, H., and C. Jennings, Holmberg, C., Alvestrand, H., and C. Jennings,
"Multiplexing Negotiation Using Session Description "Negotiating Media Multiplexing Using the Session
Protocol (SDP) Port Numbers", draft-ietf-mmusic-sdp- Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-
bundle-negotiation-03 (work in progress), February 2013. negotiation-12 (work in progress), October 2014.
[I.D-draft-ietf-dart-dscp-rtp]
Black, D. and P. Jones, "The Session Description Protocol
(SDP) Content Attribute", draft-ietf-dart-dscp-rtp-07
(work in progress), September 2014.
[IANA] "S Description Protocol (SDP) Parameters", [IANA] "S Description Protocol (SDP) Parameters",
<http://www.iana.org/assignments/sdp-parameters/ <http://www.iana.org/assignments/sdp-parameters/
sdp-parameters.xml>. sdp-parameters.xml>.
[MEDIA_LOOPBACK] [ITU-T-REC.Q1970]
Kaplan, H., Hedayat, K., Venna, N., Jones, P., and N. "Q.1970 : BICC IP bearer control protocol",
Stratton, "An Extension to the Session Description <https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>.
Protocol (SDP) and Real-time Transport Protocol (RTP) for
Media Loopback", 6489 (work in progress), January 2013.
[QOS] "S Description Protocol (SDP) QoS Mechanism Tokens",
<http://www.iana.org/assignments/sdp-parameters/
sdp-parameters.xml#sdp-parameters-20>.
[R3GPPTS24.182] [R3GPPTS24.182]
"IP Multimedia Subsystem (IMS) Customized Alerting Tones "IP Multimedia Subsystem (IMS) Customized Alerting Tones
(CAT); Protocol specification", (CAT); Protocol specification",
<http://www.3gpp.org/ftp/Specs/html-info/24182.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24182.htm>.
[R3GPPTS24.183] [R3GPPTS24.183]
"IP Multimedia Subsystem (IMS) Customized Ringing Signal "IP Multimedia Subsystem (IMS) Customized Ringing Signal
(CRS); Protocol specification", (CRS); Protocol specification",
<http://www.3gpp.org/ftp/Specs/html-info/24183.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24183.htm>.
[R3GPPTS24.229] [R3GPPTS24.229]
"IP multimedia call control protocol based on Session "IP multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol Initiation Protocol (SIP) and Session Description Protocol
(SDP);", (SDP);",
<http://www.3gpp.org/ftp/Specs/html-info/24229.htm>. <http://www.3gpp.org/ftp/Specs/html-info/24229.htm>.
[R3GPPTS26.114]
"IP multimedia Subsystem : Media Handling and
interaction",
<http://www.in2eps.com/3g26/tk-3gpp-26-114.html>.
[RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the [RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the
Session Description Protocol (SDP) for ATM Bearer Session Description Protocol (SDP) for ATM Bearer
Connections", RFC 3108, May 2001. Connections", RFC 3108, May 2001.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, June with Session Description Protocol (SDP)", RFC 3264, June
2002. 2002.
[RFC3407] Andreasen, F., "S Description Protocol (SDP) Simple [RFC3312] Camarillo, G., Marshall, W., and J. Rosenberg,
"Integration of Resource Management and Session Initiation
Protocol (SIP)", RFC 3312, October 2002.
[RFC3407] Andreasen, F., "Session Description Protocol (SDP) Simple
Capability Declaration", RFC 3407, October 2002. Capability Declaration", RFC 3407, October 2002.
[RFC3524] Camarillo, G. and A. Monrad, "Mapping of Media Streams to [RFC3524] Camarillo, G. and A. Monrad, "Mapping of Media Streams to
Resource Reservation Flows", RFC 3524, April 2003. Resource Reservation Flows", RFC 3524, April 2003.
[RFC3556] Casner, S., "S Description Protocol (SDP) Bandwidth [RFC3556] Casner, S., "Session Description Protocol (SDP) Bandwidth
Modifiers for RTP Control Protocol (RTCP) Bandwidth", RFC Modifiers for RTP Control Protocol (RTCP) Bandwidth", RFC
3556, July 2003. 3556, July 2003.
[RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute [RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute
in Session Description Protocol (SDP)", RFC 3605, October in Session Description Protocol (SDP)", RFC 3605, October
2003. 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", RFC 3611, November Protocol Extended Reports (RTCP XR)", RFC 3611, November
2003. 2003.
skipping to change at page 65, line 18 skipping to change at page 83, line 5
[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in [RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
the Session Description Protocol (SDP)", RFC 4145, the Session Description Protocol (SDP)", RFC 4145,
September 2005. September 2005.
[RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E. [RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E.
Carrara, "Key Management Extensions for Session Carrara, "Key Management Extensions for Session
Description Protocol (SDP) and Real Time Streaming Description Protocol (SDP) and Real Time Streaming
Protocol (RTSP)", RFC 4567, July 2006. Protocol (RTSP)", RFC 4567, July 2006.
[RFC4568] Andreasen, F., Baugher, M., and D. Wing, "S Description [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session
Protocol (SDP) Security Descriptions for Media Streams", Description Protocol (SDP) Security Descriptions for Media
RFC 4568, July 2006. Streams", RFC 4568, July 2006.
[RFC4570] Quinn, B. and R. Finlayson, "S Description Protocol (SDP) [RFC4570] Quinn, B. and R. Finlayson, "Session Description Protocol
Source Filters", RFC 4570, July 2006. (SDP) Source Filters", RFC 4570, July 2006.
[RFC4572] Lennox, J., "Connection-Oriented Media Transport over the [RFC4572] Lennox, J., "Connection-Oriented Media Transport over the
Transport Layer Security (TLS) Protocol in the Session Transport Layer Security (TLS) Protocol in the Session
Description Protocol (SDP)", RFC 4572, July 2006. Description Protocol (SDP)", RFC 4572, July 2006.
[RFC4574] Levin, O. and G. Camarillo, "The Session Description [RFC4574] Levin, O. and G. Camarillo, "The Session Description
Protocol (SDP) Label Attribute", RFC 4574, August 2006. Protocol (SDP) Label Attribute", RFC 4574, August 2006.
[RFC4583] Camarillo, G., "S Description Protocol (SDP) Format for [RFC4583] Camarillo, G., "Session Description Protocol (SDP) Format
Binary Floor Control Protocol (BFCP) Streams", RFC 4583, for Binary Floor Control Protocol (BFCP) Streams", RFC
November 2006. 4583, November 2006.
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,
"Extended RTP Profile for Real-time Transport Control "Extended RTP Profile for Real-time Transport Control
Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, July Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, July
2006. 2006.
[RFC4796] Hautakorpi, J. and G. Camarillo, "The Session Description [RFC4796] Hautakorpi, J. and G. Camarillo, "The Session Description
Protocol (SDP) Content Attribute", RFC 4796, February Protocol (SDP) Content Attribute", RFC 4796, February
2007. 2007.
[RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message [RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message
Session Relay Protocol (MSRP)", RFC 4975, September 2007. Session Relay Protocol (MSRP)", RFC 4975, September 2007.
[RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman, [RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman,
"Codec Control Messages in the RTP Audio-Visual Profile "Codec Control Messages in the RTP Audio-Visual Profile
with Feedback (AVPF)", RFC 5104, February 2008. with Feedback (AVPF)", RFC 5104, February 2008.
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, December 2007. Correction", RFC 5109, December 2007.
[RFC5159] Dondeti, L. and A. Jerichow, "S Description Protocol (SDP) [RFC5159] Dondeti, L. and A. Jerichow, "Session Description Protocol
Attributes for Open Mobile Alliance (OMA) Broadcast (SDP) Attributes for Open Mobile Alliance (OMA) Broadcast
(BCAST) Service and Content Protection", RFC 5159, March (BCAST) Service and Content Protection", RFC 5159, March
2008. 2008.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) (ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245, July Traversal for Offer/Answer Protocols", RFC 5245, April
2006. 2010.
[RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP [RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP
Header Extensions", RFC 5285, July 2008. Header Extensions", RFC 5285, July 2008.
[RFC5432] Polk, J., Dhesikan, S., and G. Camarillo, "Quality of [RFC5432] Polk, J., Dhesikan, S., and G. Camarillo, "Quality of
Service (QoS) Mechanism Selection in the Session Service (QoS) Mechanism Selection in the Session
Description Protocol (SDP)", RFC 5432, March 2009. Description Protocol (SDP)", RFC 5432, March 2009.
[RFC5506] Johansson, I., "Support for Reduced-Size Real-Time [RFC5506] Johansson, I. and M. Westerlund, "Support for Reduced-Size
Transport Control Protocol (RTCP): Opportunities and Real-Time Transport Control Protocol (RTCP): Opportunities
Consequences", RFC 5506, April 2009. and Consequences", RFC 5506, April 2009.
[RFC5547] Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S., [RFC5547] Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S.,
and P. Kyzivat, "A Session Description Protocol (SDP) and P. Kyzivat, "A Session Description Protocol (SDP)
Offer/Answer Mechanism to Enable File Transfer", RFC 5547, Offer/Answer Mechanism to Enable File Transfer", RFC 5547,
May 2009. May 2009.
[RFC5576] Lennox, J., Ott, J., and T. Schierl, "Source-Specific [RFC5576] Lennox, J., Ott, J., and T. Schierl, "Source-Specific
Media Attributes in the Session Description Protocol Media Attributes in the Session Description Protocol
(SDP)", RFC 5576, June 2009. (SDP)", RFC 5576, June 2009.
skipping to change at page 67, line 13 skipping to change at page 84, line 47
Protocol (DCCP)", RFC 5762, April 2010. Protocol (DCCP)", RFC 5762, April 2010.
[RFC5763] Fischl, J., Tschofenig, H., and E. Rescorla, "Framework [RFC5763] Fischl, J., Tschofenig, H., and E. Rescorla, "Framework
for Establishing a Secure Real-time Transport Protocol for Establishing a Secure Real-time Transport Protocol
(SRTP) Security Context Using Datagram Transport Layer (SRTP) Security Context Using Datagram Transport Layer
Security (DTLS)", RFC 5763, May 2010. Security (DTLS)", RFC 5763, May 2010.
[RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description [RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description
Protocol (SDP) Grouping Framework", RFC 5888, June 2010. Protocol (SDP) Grouping Framework", RFC 5888, June 2010.
[RFC5939] Andreasen, F., "S Description Protocol (SDP) Capability [RFC5939] Andreasen, F., "Session Description Protocol (SDP)
Negotiation", RFC 5939, September 2010. Capability Negotiation", RFC 5939, September 2010.
[RFC5956] Begen, A., "Forward Error Correction Grouping Semantics in [RFC5956] Begen, A., "Forward Error Correction Grouping Semantics in
the Session Description Protocol", RFC 5956, September the Session Description Protocol", RFC 5956, September
2010. 2010.
[RFC6064] Westerlund, M. and P. Frojdh, "SDP and RTSP Extensions [RFC6064] Westerlund, M. and P. Frojdh, "SDP and RTSP Extensions
Defined for 3GPP Packet-Switched Streaming Service and Defined for 3GPP Packet-Switched Streaming Service and
Multimedia Broadcast/Multicast Service", RFC 6064, January Multimedia Broadcast/Multicast Service", RFC 6064, January
2011. 2011.
skipping to change at page 68, line 5 skipping to change at page 85, line 37
6236, May 2011. 6236, May 2011.
[RFC6284] Begen, A., Wing, D., and T. Van Caenegem, "Port Mapping [RFC6284] Begen, A., Wing, D., and T. Van Caenegem, "Port Mapping
between Unicast and Multicast RTP Sessions", RFC 6284, between Unicast and Multicast RTP Sessions", RFC 6284,
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., "S 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.
[RFC6871] Gimlan, R., Evan, 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, Febrauary 2013. Negotiation", RFC 6871, February 2013.
[RTCP-FB] "S Description Protocol (SDP) RTCP Feedback attributes", [RFC6947] Boucadair, M., Kaplan, H., Gilman, R., and S.
<http://www.iana.org/assignments/sdp-parameters/ Veikkolainen, "The Session Description Protocol (SDP)
sdp-parameters.xml#sdp-parameters-14>. Alternate Connectivity (ALTC) Attribute", RFC 6947, May
2013.
[SSRC-GROUP] [RFC7006] Garcia-Martin, M., Veikkolainen, S., and R. Gilman,
"S Description Protocol (SDP) "ssrc-group" semantics", "Miscellaneous Capabilities Negotiation in the Session
<http://www.iana.org/assignments/sdp-parameters/ Description Protocol (SDP)", RFC 7006, September 2013.
sdp-parameters.xml#sdp-parameters-17>.
[RFC7104] Begen, A., Cai, Y., and H. Ou, "Duplication Grouping
Semantics in the Session Description Protocol", RFC 7104,
January 2014.
[RFC7195] Garcia-Martin, M. and S. Veikkolainen, "Session
Description Protocol (SDP) Extension for Setting Audio and
Video Media Streams over Circuit-Switched Bearers in the
Public Switched Telephone Network (PSTN)", RFC 7195, May
2014.
[RFC7197] Begen, A., Cai, Y., and H. Ou, "Duplication Delay
Attribute in the Session Description Protocol", RFC 7197,
April 2014.
[RFC7226] Villamizar, C., McDysan, D., Ning, S., Malis, A., and L.
Yong, "Requirements for Advanced Multipath in MPLS
Networks", RFC 7226, May 2014.
[RFC7272] van Brandenburg, R., Stokking, H., van Deventer, O.,
Boronat, F., Montagud, M., and K. Gross, "Inter-
Destination Media Synchronization (IDMS) Using the RTP
Control Protocol (RTCP)", RFC 7272, June 2014.
[RFC7273] Williams, A., Gross, K., van Brandenburg, R., and H.
Stokking, "RTP Clock Source Signalling", RFC 7273, June
2014.
[T.38] "Procedures for real-time Group 3 facsimile communication [T.38] "Procedures for real-time Group 3 facsimile communication
over IP networks", <http://www.itu.int/rec/T-REC-T.38/e>. over IP networks", <http://www.itu.int/rec/T-REC-T.38/e>.
Author's Address Author's Address
Suhas Nandakumar Suhas Nandakumar
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
 End of changes. 203 change blocks. 
898 lines changed or deleted 1777 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/