rfc8859v7.txt   rfc8859.txt 
skipping to change at line 114 skipping to change at line 114
5.38. RFC 6128: RTCP Port for Multicast Sessions 5.38. RFC 6128: RTCP Port for Multicast Sessions
5.39. RFC 6189: ZRTP 5.39. RFC 6189: ZRTP
5.40. RFC 4145: Connection-Oriented Media 5.40. RFC 4145: Connection-Oriented Media
5.41. RFC 6947: The SDP "altc" Attribute 5.41. RFC 6947: The SDP "altc" Attribute
5.42. RFC 7195: SDP Extension for Circuit-Switched Bearers in 5.42. RFC 7195: SDP Extension for Circuit-Switched Bearers in
PSTN PSTN
5.43. RFC 7272: IDMS Using the RTP Control Protocol (RTCP) 5.43. RFC 7272: IDMS Using the RTP Control Protocol (RTCP)
5.44. RFC 5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP 5.44. RFC 5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP
Attributes Attributes
5.45. RFC 6193: Media Description for IKE in SDP 5.45. RFC 6193: Media Description for IKE in SDP
5.46. RFC 7826: Real-Time Streaming Protocol 5.46. RFC 2326: Real Time Streaming Protocol
5.47. RFC 6064: SDP and RTSP Extensions for 3GPP 5.47. RFC 7826: Real-Time Streaming Protocol
5.48. RFC 3108: ATM SDP 5.48. RFC 6064: SDP and RTSP Extensions for 3GPP
5.49. 3GPP TS 183.063 5.49. RFC 3108: ATM SDP
5.50. 3GPP TS 24.229 5.50. 3GPP TS 183.063
5.51. ITU T.38 5.51. 3GPP TS 24.229
5.52. ITU-T Q.1970 5.52. ITU T.38
5.53. ITU-T H.248.15 5.53. ITU-T Q.1970
5.54. RFC 4975: The Message Session Relay Protocol 5.54. ITU-T H.248.15
5.55. Historical Attributes 5.55. RFC 4975: The Message Session Relay Protocol
5.56. Historical Attributes
6. bwtype Attribute Analysis 6. bwtype Attribute Analysis
6.1. RFC 4566: SDP 6.1. RFC 4566: SDP
6.2. RFC 3556: SDP Bandwidth Modifiers for RTCP Bandwidth 6.2. RFC 3556: SDP Bandwidth Modifiers for RTCP Bandwidth
6.3. RFC 3890: Bandwidth Modifier for SDP 6.3. RFC 3890: Bandwidth Modifier for SDP
7. rtcp-fb Attribute Analysis 7. rtcp-fb Attribute Analysis
7.1. RFC 4585: RTP/AVPF 7.1. RFC 4585: RTP/AVPF
7.2. RFC 5104: Codec Control Messages in AVPF 7.2. RFC 5104: Codec Control Messages in AVPF
7.3. RFC 6285: Unicast-Based Rapid Acquisition of Multicast RTP 7.3. RFC 6285: Unicast-Based Rapid Acquisition of Multicast RTP
Sessions (RAMS) Sessions (RAMS)
7.4. RFC 6679: ECN for RTP over UDP/IP 7.4. RFC 6679: ECN for RTP over UDP/IP
skipping to change at line 1674 skipping to change at line 1675
+------------------+----------------------------+-------+----------+ +------------------+----------------------------+-------+----------+
| ike-esp | Unlikely to use IKE in the | B | CAUTION | | ike-esp | Unlikely to use IKE in the | B | CAUTION |
| | context of multiplexing | | | | | context of multiplexing | | |
+------------------+----------------------------+-------+----------+ +------------------+----------------------------+-------+----------+
| ike-esp-udpencap | Unlikely to use IKE in the | B | CAUTION | | ike-esp-udpencap | Unlikely to use IKE in the | B | CAUTION |
| | context of multiplexing | | | | | context of multiplexing | | |
+------------------+----------------------------+-------+----------+ +------------------+----------------------------+-------+----------+
Table 45: RFC 6193 Attribute Analysis Table 45: RFC 6193 Attribute Analysis
5.46. RFC 7826: Real-Time Streaming Protocol 5.46. RFC 2326: Real Time Streaming Protocol
The Real Time Streaming Protocol, or RTSP, is an application-level
protocol for control over the delivery of data with real-time
properties. RTSP provides an extensible framework to enable
controlled, on-demand delivery of real-time data, such as audio and
video.
+=========+=======================+=======+==============+
| Name | Notes | Level | Mux Category |
+=========+=======================+=======+==============+
| etag | RFC 2326 is obsolete. | B | CAUTION |
+---------+-----------------------+-------+--------------+
| range | RFC 2326 is obsolete. | B | CAUTION |
+---------+-----------------------+-------+--------------+
| control | RFC 2326 is obsolete. | B | CAUTION |
+---------+-----------------------+-------+--------------+
| mtag | RFC 2326 is obsolete. | B | CAUTION |
+---------+-----------------------+-------+--------------+
Table 46: RFC 2326 Attribute Analysis
NOTE: [RFC2326] defines SDP attributes that are applicable in the
declarative usage of SDP alone. For the purposes of this document,
only the offer/answer usage of SDP is considered to be mandated by
[RFC8843].
5.47. RFC 7826: Real-Time Streaming Protocol
The Real-Time Streaming Protocol, or RTSP, is an application-level The Real-Time Streaming Protocol, or RTSP, is an application-level
protocol for control over the delivery of data with real-time protocol for control over the delivery of data with real-time
properties. RTSP provides an extensible framework to enable properties. RTSP provides an extensible framework to enable
controlled, on-demand delivery of real-time data, such as audio and controlled, on-demand delivery of real-time data, such as audio and
video. video.
+=========+===========================+=======+==============+ +=========+===========================+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+=========+===========================+=======+==============+ +=========+===========================+=======+==============+
| range | RTSP is not supported for | B | CAUTION | | range | RTSP is not supported for | B | CAUTION |
| | RTP stream multiplexing. | | | | | RTP stream multiplexing. | | |
+---------+---------------------------+-------+--------------+ +---------+---------------------------+-------+--------------+
| control | RTSP is not supported for | B | CAUTION | | control | RTSP is not supported for | B | CAUTION |
| | RTP stream multiplexing. | | | | | RTP stream multiplexing. | | |
+---------+---------------------------+-------+--------------+ +---------+---------------------------+-------+--------------+
| mtag | RTSP is not supported for | B | CAUTION | | mtag | RTSP is not supported for | B | CAUTION |
| | RTP stream multiplexing. | | | | | RTP stream multiplexing. | | |
+---------+---------------------------+-------+--------------+ +---------+---------------------------+-------+--------------+
Table 46: RFC 7826 Attribute Analysis Table 47: RFC 7826 Attribute Analysis
NOTE: [RFC7826] defines SDP attributes that are applicable in the NOTE: [RFC7826] defines SDP attributes that are applicable in the
declarative usage of SDP alone. For the purposes of this document, declarative usage of SDP alone. For the purposes of this document,
only the offer/answer usage of SDP is considered to be mandated by only the offer/answer usage of SDP is considered to be mandated by
[RFC8843]. [RFC8843].
5.47. RFC 6064: SDP and RTSP Extensions for 3GPP 5.48. RFC 6064: 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 SDP and RTSP Broadcast/Multicast Service (MBMS) defined by 3GPP use SDP and RTSP
with some extensions. [RFC6064] provides information about these with some extensions. [RFC6064] provides information about these
extensions and registers the RTSP and SDP extensions with IANA. extensions and registers the RTSP and SDP extensions with IANA.
+==============================+=============+=======+==============+ +==============================+=============+=======+==============+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+==============================+=============+=======+==============+ +==============================+=============+=======+==============+
skipping to change at line 1798 skipping to change at line 1826
| 3GPP-QoE-Metrics:Average | Refer to | M | CAUTION | | 3GPP-QoE-Metrics:Average | Refer to | M | CAUTION |
| Codec Bitrate | notes below | | | | Codec Bitrate | notes below | | |
+------------------------------+-------------+-------+--------------+ +------------------------------+-------------+-------+--------------+
| 3GPP-QoE-Metrics:Codec | Refer to | M | CAUTION | | 3GPP-QoE-Metrics:Codec | Refer to | M | CAUTION |
| Information | notes below | | | | Information | notes below | | |
+------------------------------+-------------+-------+--------------+ +------------------------------+-------------+-------+--------------+
| 3GPP-QoE-Metrics:Buffer | Refer to | M | CAUTION | | 3GPP-QoE-Metrics:Buffer | Refer to | M | CAUTION |
| Status | notes below | | | | Status | notes below | | |
+------------------------------+-------------+-------+--------------+ +------------------------------+-------------+-------+--------------+
Table 47: RFC 6064 Attribute Analysis Table 48: RFC 6064 Attribute Analysis
NOTE: [RFC6064] defines SDP attributes that are applicable in the NOTE: [RFC6064] defines SDP attributes that are applicable in the
declarative usage of SDP alone. For the purposes of this document, declarative usage of SDP alone. For the purposes of this document,
only the offer/answer usage of SDP is considered to be mandated by only the offer/answer usage of SDP is considered to be mandated by
[RFC8843]. [RFC8843].
5.48. RFC 3108: ATM SDP 5.49. RFC 3108: ATM SDP
[RFC3108] describes conventions for using SDP described for [RFC3108] describes conventions for using SDP described for
controlling ATM bearer connections and any associated ATM Adaptation controlling ATM bearer connections and any associated ATM Adaptation
Layer (AAL). Layer (AAL).
+=======================+=============+=======+==============+ +=======================+=============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+=======================+=============+=======+==============+ +=======================+=============+=======+==============+
| aalType | Refer to | B | CAUTION | | aalType | Refer to | B | CAUTION |
| | notes below | | | | | notes below | | |
skipping to change at line 1944 skipping to change at line 1972
| isup_usi | Refer to | B | CAUTION | | isup_usi | Refer to | B | CAUTION |
| | notes below | | | | | notes below | | |
+-----------------------+-------------+-------+--------------+ +-----------------------+-------------+-------+--------------+
| uiLayer1_Prot | Refer to | B | CAUTION | | uiLayer1_Prot | Refer to | B | CAUTION |
| | notes below | | | | | notes below | | |
+-----------------------+-------------+-------+--------------+ +-----------------------+-------------+-------+--------------+
| chain | Refer to | B | CAUTION | | chain | Refer to | B | CAUTION |
| | notes below | | | | | notes below | | |
+-----------------------+-------------+-------+--------------+ +-----------------------+-------------+-------+--------------+
Table 48: RFC 3108 Attribute Analysis Table 49: RFC 3108 Attribute Analysis
NOTE: RFC 3108 describes conventions for using SDP for characterizing NOTE: RFC 3108 describes conventions for using SDP for characterizing
ATM bearer connections using an AAL1, AAL2, or AAL5 adaptation layer. ATM bearer connections using an AAL1, AAL2, or AAL5 adaptation layer.
For AAL1, AAL2, and AAL5, bearer connections can be used to transport For AAL1, AAL2, and AAL5, bearer connections can be used to transport
single media streams. In addition, for AAL1 and AAL2, multiple media single media streams. In addition, for AAL1 and AAL2, multiple media
streams can be multiplexed into a bearer connection. For all streams can be multiplexed into a bearer connection. For all
adaptation types (AAL1, AAL2, and AAL5), bearer connections can be adaptation types (AAL1, AAL2, and AAL5), bearer connections can be
bundled into a single media group. In all cases addressed by RFC bundled into a single media group. In all cases addressed by RFC
3108, a real-time media stream (voice, video, voiceband data, 3108, a real-time media stream (voice, video, voiceband data,
pseudowire, and others) or a multiplex of media streams is mapped pseudowire, and others) or a multiplex of media streams is mapped
directly into an ATM connection. RFC 3108 does not address cases directly into an ATM connection. RFC 3108 does not address cases
where ATM serves as a low-level transport pipe for IP packets that where ATM serves as a low-level transport pipe for IP packets that
can, in turn, carry one or more real-time (e.g., VoIP) media sessions can, in turn, carry one or more real-time (e.g., VoIP) media sessions
with a life cycle different from that of the underlying ATM with a life cycle different from that of the underlying ATM
transport. transport.
5.49. 3GPP TS 183.063 5.50. 3GPP TS 183.063
[TISPAN] describes Telecommunications and Internet converged Services [TISPAN] describes Telecommunications and Internet converged Services
and Protocols for Advanced Networking (TISPAN); and Protocols for Advanced Networking (TISPAN);
+====================+==============+=======+==============+ +====================+==============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+====================+==============+=======+==============+ +====================+==============+=======+==============+
| PSCid | Not impacted | S | NORMAL | | PSCid | Not impacted | S | NORMAL |
+--------------------+--------------+-------+--------------+ +--------------------+--------------+-------+--------------+
| bc_service | Not impacted | S | NORMAL | | bc_service | Not impacted | S | NORMAL |
+--------------------+--------------+-------+--------------+ +--------------------+--------------+-------+--------------+
| bc_program | Not impacted | S | NORMAL | | bc_program | Not impacted | S | NORMAL |
+--------------------+--------------+-------+--------------+ +--------------------+--------------+-------+--------------+
| bc_service_package | Not impacted | S | NORMAL | | bc_service_package | Not impacted | S | NORMAL |
+--------------------+--------------+-------+--------------+ +--------------------+--------------+-------+--------------+
Table 49: 3GPP TS 183.063 Attribute Analysis Table 50: 3GPP TS 183.063 Attribute Analysis
5.50. 3GPP TS 24.229 5.51. 3GPP TS 24.229
[IP-CALL] specifies an IP multimedia call control protocol based on [IP-CALL] specifies an IP multimedia call control protocol based on
Session Initial protocol and Session Description Protocol. Session Initial protocol and Session Description Protocol.
+=================+============================+=======+===========+ +=================+============================+=======+===========+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+=================+============================+=======+===========+ +=================+============================+=======+===========+
| secondary-realm | secondary-realm MUST be | M | TRANSPORT | | secondary-realm | secondary-realm MUST be | M | TRANSPORT |
| | the one that corresponds | | | | | the one that corresponds | | |
skipping to change at line 2016 skipping to change at line 2044
+-----------------+----------------------------+-------+-----------+ +-----------------+----------------------------+-------+-----------+
| omr-s-att | Not impacted | M | NORMAL | | omr-s-att | Not impacted | M | NORMAL |
+-----------------+----------------------------+-------+-----------+ +-----------------+----------------------------+-------+-----------+
| omr-m-bw | Not impacted | M | NORMAL | | omr-m-bw | Not impacted | M | NORMAL |
+-----------------+----------------------------+-------+-----------+ +-----------------+----------------------------+-------+-----------+
| omr-s-bw | Not impacted | M | NORMAL | | omr-s-bw | Not impacted | M | NORMAL |
+-----------------+----------------------------+-------+-----------+ +-----------------+----------------------------+-------+-----------+
| omr-codecs | Not impacted | M | NORMAL | | omr-codecs | Not impacted | M | NORMAL |
+-----------------+----------------------------+-------+-----------+ +-----------------+----------------------------+-------+-----------+
Table 50: 3GPP TS 24.229 Attribute Analysis Table 51: 3GPP TS 24.229 Attribute Analysis
5.51. ITU T.38 5.52. ITU T.38
[T.38] defines procedures for real-time Group 3 facsimile [T.38] defines procedures for real-time Group 3 facsimile
communications over IP networks. communications over IP networks.
+=======================+=============+=======+==============+ +=======================+=============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+=======================+=============+=======+==============+ +=======================+=============+=======+==============+
| T38FaxVersion | Refer to | M | TBD | | T38FaxVersion | Refer to | M | TBD |
| | notes below | | | | | notes below | | |
+-----------------------+-------------+-------+--------------+ +-----------------------+-------------+-------+--------------+
skipping to change at line 2069 skipping to change at line 2097
| T38FaxUdpFECMaxSpan | Refer to | M | TBD | | T38FaxUdpFECMaxSpan | Refer to | M | TBD |
| | notes below | | | | | notes below | | |
+-----------------------+-------------+-------+--------------+ +-----------------------+-------------+-------+--------------+
| T38ModemType | Refer to | M | TBD | | T38ModemType | Refer to | M | TBD |
| | notes below | | | | | notes below | | |
+-----------------------+-------------+-------+--------------+ +-----------------------+-------------+-------+--------------+
| T38VendorInfo | Refer to | M | TBD | | T38VendorInfo | Refer to | M | TBD |
| | notes below | | | | | notes below | | |
+-----------------------+-------------+-------+--------------+ +-----------------------+-------------+-------+--------------+
Table 51: ITU T.38 Attribute Analysis Table 52: ITU T.38 Attribute Analysis
NOTE: As per Section 9 of [RFC8843], there exists no publicly NOTE: As per Section 9 of [RFC8843], there exists no publicly
available specification that defines procedures for multiplexing/ available specification that defines procedures for multiplexing/
demultiplexing fax protocol flows over a single 5-tuple. Once such a demultiplexing fax protocol flows over a single 5-tuple. Once such a
specification is available, the multiplexing category assignments for specification is available, the multiplexing category assignments for
the attributes in this section could be revisited. the attributes in this section could be revisited.
5.52. ITU-T Q.1970 5.53. ITU-T Q.1970
[Q.1970] defines Bearer Independent Call Control (BICC) IP bearer [Q.1970] defines Bearer Independent Call Control (BICC) IP bearer
control protocol. control protocol.
+=======+=====================================+=======+==========+ +=======+=====================================+=======+==========+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+=======+=====================================+=======+==========+ +=======+=====================================+=======+==========+
| ipbcp | ipbcp version identifies the types | S | SPECIAL | | ipbcp | ipbcp version identifies the types | S | SPECIAL |
| | of IP bearer control protocol | | | | | of IP bearer control protocol | | |
| | (IPBCP) message used in BICC (ITU-T | | | | | (IPBCP) message used in BICC (ITU-T | | |
| | Q.1901) environment that are | | | | | Q.1901) environment that are | | |
| | limited to single-media payload. | | | | | limited to single-media payload. | | |
| | Refer to the pertinent ITU-T | | | | | Refer to the pertinent ITU-T | | |
| | specifications while multiplexing. | | | | | specifications while multiplexing. | | |
+-------+-------------------------------------+-------+----------+ +-------+-------------------------------------+-------+----------+
Table 52: ITU-T Q.1970 Attribute Analysis Table 53: ITU-T Q.1970 Attribute Analysis
5.53. ITU-T H.248.15 5.54. ITU-T H.248.15
ITU-T H.248.15 [H.248.15] defines the Gateway Control Protocol SDP ITU-T H.248.15 [H.248.15] defines the Gateway Control Protocol SDP
H.248 package attribute. H.248 package attribute.
+==========+=====================================+=======+==========+ +==========+=====================================+=======+==========+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+==========+=====================================+=======+==========+ +==========+=====================================+=======+==========+
| h248item | It is only applicable for | B | SPECIAL | | h248item | It is only applicable for | B | SPECIAL |
| | signaling the inclusion of H.248 | | | | | signaling the inclusion of H.248 | | |
skipping to change at line 2127 skipping to change at line 2155
| | is an issue. This is only a | | | | | is an issue. This is only a | | |
| | concern in environments using a | | | | | concern in environments using a | | |
| | decomposed server/gateway with | | | | | decomposed server/gateway with | | |
| | H.248 signaled between them. The | | | | | H.248 signaled between them. The | | |
| | ITU-T will need to do further | | | | | ITU-T will need to do further | | |
| | analysis of various packages when | | | | | analysis of various packages when | | |
| | they specify how to signal the | | | | | they specify how to signal the | | |
| | use of multiplexing to a gateway. | | | | | use of multiplexing to a gateway. | | |
+----------+-------------------------------------+-------+----------+ +----------+-------------------------------------+-------+----------+
Table 53: ITU-T H.248.15 Attribute Analysis Table 54: ITU-T H.248.15 Attribute Analysis
5.54. RFC 4975: The Message Session Relay Protocol 5.55. RFC 4975: The Message Session Relay Protocol
[RFC4975] describes the Message Session Relay Protocol, a protocol [RFC4975] describes the Message Session Relay Protocol, a protocol
for transmitting a series of related instant messages in the context for transmitting a series of related instant messages in the context
of a session. Message sessions are treated like any other media of a session. Message sessions are treated like any other media
stream when set up via a rendezvous or session-creation protocol such stream when set up via a rendezvous or session-creation protocol such
as the Session Initiation Protocol. as the Session Initiation Protocol.
+======================+=============+=======+==============+ +======================+=============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+======================+=============+=======+==============+ +======================+=============+=======+==============+
skipping to change at line 2153 skipping to change at line 2181
| accept-wrapped-types | Refer to | M | TBD | | accept-wrapped-types | Refer to | M | TBD |
| | notes below | | | | | notes below | | |
+----------------------+-------------+-------+--------------+ +----------------------+-------------+-------+--------------+
| max-size | Refer to | M | TBD | | max-size | Refer to | M | TBD |
| | notes below | | | | | notes below | | |
+----------------------+-------------+-------+--------------+ +----------------------+-------------+-------+--------------+
| path | Refer to | M | TBD | | path | Refer to | M | TBD |
| | notes below | | | | | notes below | | |
+----------------------+-------------+-------+--------------+ +----------------------+-------------+-------+--------------+
Table 54: RFC 4975 Attribute Analysis Table 55: RFC 4975 Attribute Analysis
NOTE: As per Section 9 of [RFC8843], there exists no publicly NOTE: As per Section 9 of [RFC8843], there exists no publicly
available specification that defines procedures for multiplexing/ available specification that defines procedures for multiplexing/
demultiplexing MSRP flows over a single 5-tuple. Once such a demultiplexing MSRP flows over a single 5-tuple. Once such a
specification is available, the multiplexing categories assignments specification is available, the multiplexing categories assignments
for the attributes in this section could be revisited. for the attributes in this section could be revisited.
5.55. Historical Attributes 5.56. Historical Attributes
This section specifies analysis for the attributes that are included This section specifies analysis for the attributes that are included
for historic usage alone by the [IANA]. for historic usage alone by the [IANA].
+=========+=====================+=======+==============+ +=========+=====================+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+=========+=====================+=======+==============+ +=========+=====================+=======+==============+
| rtpred1 | Historic attributes | M | CAUTION | | rtpred1 | Historic attributes | M | CAUTION |
+---------+---------------------+-------+--------------+ +---------+---------------------+-------+--------------+
| rtpred2 | Historic attributes | M | CAUTION | | rtpred2 | Historic attributes | M | CAUTION |
+---------+---------------------+-------+--------------+ +---------+---------------------+-------+--------------+
Table 55: Historical Attribute Analysis Table 56: Historical Attribute Analysis
6. bwtype Attribute Analysis 6. bwtype Attribute Analysis
This section specifies handling of specific bandwidth attributes when This section specifies handling of specific bandwidth attributes when
used in multiplexing scenarios. used in multiplexing scenarios.
6.1. RFC 4566: SDP 6.1. RFC 4566: SDP
[RFC4566] defines SDP that is intended for describing multimedia [RFC4566] defines SDP that is intended for describing multimedia
sessions for the purposes of session announcement, session sessions for the purposes of session announcement, session
skipping to change at line 2198 skipping to change at line 2226
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+===========+=================================+=======+==========+ +===========+=================================+=======+==========+
| bwtype:CT | Not impacted | S | NORMAL | | bwtype:CT | Not impacted | S | NORMAL |
+-----------+---------------------------------+-------+----------+ +-----------+---------------------------------+-------+----------+
| bwtype:AS | For media-level usage, the | B | SUM | | bwtype:AS | For media-level usage, the | B | SUM |
| | aggregate of individual | | | | | aggregate of individual | | |
| | bandwidth values is considered. | | | | | bandwidth values is considered. | | |
+-----------+---------------------------------+-------+----------+ +-----------+---------------------------------+-------+----------+
Table 56: RFC 4566 bwtype Analysis Table 57: RFC 4566 bwtype Analysis
6.2. RFC 3556: SDP Bandwidth Modifiers for RTCP Bandwidth 6.2. RFC 3556: SDP Bandwidth Modifiers for RTCP Bandwidth
[RFC3556] defines an extension to SDP to specify two additional [RFC3556] defines an extension to SDP to specify two additional
modifiers for the bandwidth attribute. These modifiers may be used modifiers for the bandwidth attribute. These modifiers may be used
to specify the bandwidth allowed for RTCP packets in an RTP session. to specify the bandwidth allowed for RTCP packets in an RTP session.
+===========+================================+=======+==========+ +===========+================================+=======+==========+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
skipping to change at line 2223 skipping to change at line 2251
| | the individual values while | | | | | the individual values while | | |
| | multiplexing. | | | | | multiplexing. | | |
+-----------+--------------------------------+-------+----------+ +-----------+--------------------------------+-------+----------+
| bwtype:RR | Session-level usage represents | B | SUM | | bwtype:RR | Session-level usage represents | B | SUM |
| | session aggregate, and media- | | | | | session aggregate, and media- | | |
| | level usage indicates SUM of | | | | | level usage indicates SUM of | | |
| | the individual values while | | | | | the individual values while | | |
| | multiplexing. | | | | | multiplexing. | | |
+-----------+--------------------------------+-------+----------+ +-----------+--------------------------------+-------+----------+
Table 57: RFC 3556 bwtype Analysis Table 58: RFC 3556 bwtype Analysis
6.3. RFC 3890: Bandwidth Modifier for SDP 6.3. RFC 3890: Bandwidth Modifier for SDP
[RFC3890] defines SDP Transport Independent Application Specific [RFC3890] defines SDP Transport Independent Application Specific
Maximum (TIAS) bandwidth modifier that does not include transport Maximum (TIAS) bandwidth modifier that does not include transport
overhead; instead, an additional packet-rate attribute is defined. overhead; instead, an additional packet-rate attribute is defined.
The transport-independent bitrate value together with the maximum The transport-independent bitrate value together with the maximum
packet rate can then be used to calculate the real bitrate over the packet rate can then be used to calculate the real bitrate over the
transport actually used. transport actually used.
skipping to change at line 2247 skipping to change at line 2275
+=============+==================================+=======+==========+ +=============+==================================+=======+==========+
| bwtype:TIAS | The usage of TIAS is not | B | SPECIAL | | bwtype:TIAS | The usage of TIAS is not | B | SPECIAL |
| | defined under offer/answer | | | | | defined under offer/answer | | |
| | usage. | | | | | usage. | | |
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
| maxprate | The usage of TIAS and | B | SPECIAL | | maxprate | The usage of TIAS and | B | SPECIAL |
| | maxprate is not well | | | | | maxprate is not well | | |
| | defined under multiplexing. | | | | | defined under multiplexing. | | |
+-------------+----------------------------------+-------+----------+ +-------------+----------------------------------+-------+----------+
Table 58: RFC 3890 bwtype Analysis Table 59: RFC 3890 bwtype Analysis
NOTE: The intention of TIAS is that the media-level bitrate is NOTE: The intention of TIAS is that the media-level bitrate is
multiplied with the known per-packet overhead for the selected multiplied with the known per-packet overhead for the selected
transport and the maxprate value to determine the worst-case bitrate transport and the maxprate value to determine the worst-case bitrate
from the transport to more accurately capture the required usage. from the transport to more accurately capture the required usage.
Summing TIAS values independently across "m=" lines and multiplying Summing TIAS values independently across "m=" lines and multiplying
the computed sum with maxprate and the per-packet overhead would the computed sum with maxprate and the per-packet overhead would
inflate the value significantly. Instead, performing multiplication inflate the value significantly. Instead, performing multiplication
and adding the individual values is a more appropriate usage. and adding the individual values is a more appropriate usage.
skipping to change at line 2305 skipping to change at line 2333
+---------+-----------------------------+-------+------------------+ +---------+-----------------------------+-------+------------------+
| nack | Feedback parameters MUST be | M | SPECIAL | | nack | Feedback parameters MUST be | M | SPECIAL |
| app | handled in the app specific | | | | app | handled in the app specific | | |
| | way when multiplexed. | | | | | way when multiplexed. | | |
+---------+-----------------------------+-------+------------------+ +---------+-----------------------------+-------+------------------+
| trr-int | The attribute value MUST be | M | IDENTICAL-PER-PT | | trr-int | The attribute value MUST be | M | IDENTICAL-PER-PT |
| | the same for a given codec | | | | | the same for a given codec | | |
| | configuration. | | | | | configuration. | | |
+---------+-----------------------------+-------+------------------+ +---------+-----------------------------+-------+------------------+
Table 59: RFC 4585 Attribute Analysis Table 60: RFC 4585 Attribute Analysis
7.2. RFC 5104: Codec Control Messages in AVPF 7.2. RFC 5104: Codec Control Messages in AVPF
[RFC5104] specifies a few extensions to the messages defined in the [RFC5104] specifies a few extensions to the messages defined in the
Audio-Visual Profile with Feedback (AVPF). They are helpful Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls. in smaller multicast environments and point-to-point calls.
+======+==========================+=======+==================+ +======+==========================+=======+==================+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+======+==========================+=======+==================+ +======+==========================+=======+==================+
| ccm | The attribute value MUST | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST | M | IDENTICAL-PER-PT |
| | be the same for a given | | | | | be the same for a given | | |
| | codec configuration. | | | | | codec configuration. | | |
+------+--------------------------+-------+------------------+ +------+--------------------------+-------+------------------+
Table 60: RFC 5104 Attribute Analysis Table 61: RFC 5104 Attribute Analysis
7.3. RFC 6285: Unicast-Based Rapid Acquisition of Multicast RTP 7.3. RFC 6285: Unicast-Based Rapid Acquisition of Multicast RTP
Sessions (RAMS) Sessions (RAMS)
[RFC6285] describes a method of using the existing RTP and RTCP [RFC6285] describes a method of using the existing RTP and RTCP
machinery that reduces the acquisition delay. In this method, an machinery that reduces the acquisition delay. In this method, an
auxiliary unicast RTP session carrying the Reference Information to auxiliary unicast RTP session carrying the Reference Information to
the receiver precedes or accompanies the multicast stream. This the receiver precedes or accompanies the multicast stream. This
unicast RTP flow can be transmitted at a faster-than-natural bitrate unicast RTP flow can be transmitted at a faster-than-natural bitrate
to further accelerate the acquisition. The motivating use case for to further accelerate the acquisition. The motivating use case for
skipping to change at line 2345 skipping to change at line 2373
compressed audio and video. compressed audio and video.
+======+==========================+=======+==================+ +======+==========================+=======+==================+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+======+==========================+=======+==================+ +======+==========================+=======+==================+
| nack | The attribute value MUST | M | IDENTICAL-PER-PT | | nack | The attribute value MUST | M | IDENTICAL-PER-PT |
| rai | be the same for a given | | | | rai | be the same for a given | | |
| | codec configuration. | | | | | codec configuration. | | |
+------+--------------------------+-------+------------------+ +------+--------------------------+-------+------------------+
Table 61: RFC 6285 Attribute Analysis Table 62: RFC 6285 Attribute Analysis
7.4. RFC 6679: ECN for RTP over UDP/IP 7.4. RFC 6679: ECN for RTP over UDP/IP
[RFC6679] specifies how Explicit Congestion Notification (ECN) can be [RFC6679] specifies how Explicit Congestion Notification (ECN) can be
used with the RTP running over UDP, using the RTCP as a feedback used with the RTP running over UDP, using the 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
timely reporting of congestion events, and a STUN extension used in timely reporting of congestion events, and a STUN extension used in
the optional initialization method using ICE. the optional initialization method using ICE.
skipping to change at line 2367 skipping to change at line 2395
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+=================+============================+=======+===========+ +=================+============================+=======+===========+
| ecn-capable-rtp | ECN markup is enabled at | M | IDENTICAL | | ecn-capable-rtp | ECN markup is enabled at | M | IDENTICAL |
| | the RTP session level. | | | | | the RTP session level. | | |
+-----------------+----------------------------+-------+-----------+ +-----------------+----------------------------+-------+-----------+
| nack ecn | This attribute enables ECN | M | IDENTICAL | | nack ecn | This attribute enables ECN | M | IDENTICAL |
| | at the RTP session level. | | | | | at the RTP session level. | | |
+-----------------+----------------------------+-------+-----------+ +-----------------+----------------------------+-------+-----------+
Table 62: RFC 6679 Attribute Analysis Table 63: RFC 6679 Attribute Analysis
7.5. RFC 6642: Third-Party Loss Report 7.5. RFC 6642: Third-Party Loss Report
In a large RTP session using the RTCP feedback mechanism defined in In a large RTP session using the RTCP feedback mechanism defined in
[RFC4585], a feedback target may experience transient overload if [RFC4585], a feedback target may experience transient overload if
some event causes a large number of receivers to send feedback at some event causes a large number of receivers to send feedback at
once. This overload is usually avoided by ensuring that feedback once. This overload is usually avoided by ensuring that feedback
reports are forwarded to all receivers, allowing them to avoid reports are forwarded to all receivers, allowing them to avoid
sending duplicate feedback reports. However, there are cases where sending duplicate feedback reports. However, there are cases where
it is not recommended to forward feedback reports, and this may allow it is not recommended to forward feedback reports, and this may allow
skipping to change at line 2395 skipping to change at line 2423
+=======+==========================+=======+==================+ +=======+==========================+=======+==================+
| nack | The attribute value MUST | M | IDENTICAL-PER-PT | | nack | The attribute value MUST | M | IDENTICAL-PER-PT |
| tllei | be the same for a given | | | | tllei | be the same for a given | | |
| | codec configuration. | | | | | codec configuration. | | |
+-------+--------------------------+-------+------------------+ +-------+--------------------------+-------+------------------+
| nack | The attribute value MUST | M | IDENTICAL-PER-PT | | nack | The attribute value MUST | M | IDENTICAL-PER-PT |
| pslei | be the same for a given | | | | pslei | be the same for a given | | |
| | codec configuration. | | | | | codec configuration. | | |
+-------+--------------------------+-------+------------------+ +-------+--------------------------+-------+------------------+
Table 63: RFC 6642 Attribute Analysis Table 64: RFC 6642 Attribute Analysis
7.6. RFC 5104: Codec Control Messages in AVPF 7.6. RFC 5104: Codec Control Messages in AVPF
[RFC5104] specifies a few extensions to the messages defined in the [RFC5104] specifies a few extensions to the messages defined in the
Audio-Visual Profile with Feedback (AVPF). They are helpful Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls. in smaller multicast environments and point-to-point calls.
+=======+==========================+=======+==================+ +=======+==========================+=======+==================+
skipping to change at line 2425 skipping to change at line 2453
+-------+--------------------------+-------+------------------+ +-------+--------------------------+-------+------------------+
| ccm | The attribute value MUST | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST | M | IDENTICAL-PER-PT |
| tstr | be the same for a given | | | | tstr | be the same for a given | | |
| | codec configuration. | | | | | codec configuration. | | |
+-------+--------------------------+-------+------------------+ +-------+--------------------------+-------+------------------+
| ccm | The attribute value MUST | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST | M | IDENTICAL-PER-PT |
| vbcm | be the same for a given | | | | vbcm | be the same for a given | | |
| | codec configuration. | | | | | codec configuration. | | |
+-------+--------------------------+-------+------------------+ +-------+--------------------------+-------+------------------+
Table 64: RFC 5104 Attribute Analysis Table 65: RFC 5104 Attribute Analysis
8. group Attribute Analysis 8. group Attribute Analysis
This section analyzes SDP "group" attribute semantics [RFC5888]. This section analyzes SDP "group" attribute semantics [RFC5888].
8.1. RFC 5888: SDP Grouping Framework 8.1. RFC 5888: SDP Grouping Framework
[RFC5888] defines a framework to group "m=" lines in SDP for [RFC5888] defines a framework to group "m=" lines in SDP for
different purposes. different purposes.
+===========+==============+=======+==============+ +===========+==============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+===========+==============+=======+==============+ +===========+==============+=======+==============+
| group:LS | Not impacted | S | NORMAL | | group:LS | Not impacted | S | NORMAL |
+-----------+--------------+-------+--------------+ +-----------+--------------+-------+--------------+
| group:FID | Not impacted | S | NORMAL | | group:FID | Not impacted | S | NORMAL |
+-----------+--------------+-------+--------------+ +-----------+--------------+-------+--------------+
Table 65: RFC 5888 Attribute Analysis Table 66: RFC 5888 Attribute Analysis
8.2. RFC 3524: Mapping Media Streams to Resource Reservation Flows 8.2. RFC 3524: Mapping Media Streams to Resource Reservation Flows
[RFC3524] defines an extension to the SDP grouping framework. It [RFC3524] defines an extension to the SDP grouping framework. It
allows requesting a group of media streams to be mapped into a single allows requesting a group of media streams to be mapped into a single
resource reservation flow. The SDP syntax needed is defined, as well resource reservation flow. The SDP syntax needed is defined, as well
as a new "semantics" attribute called Single Reservation Flow (SRF). as a new "semantics" attribute called Single Reservation Flow (SRF).
+===========+==============+=======+==============+ +===========+==============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+===========+==============+=======+==============+ +===========+==============+=======+==============+
| group:SRF | Not impacted | S | NORMAL | | group:SRF | Not impacted | S | NORMAL |
+-----------+--------------+-------+--------------+ +-----------+--------------+-------+--------------+
Table 66: RFC 3524 Attribute Analysis Table 67: RFC 3524 Attribute Analysis
8.3. RFC 4091: ANAT Semantics 8.3. RFC 4091: ANAT Semantics
[RFC4091] defines ANAT semantics for the SDP grouping framework. [RFC4091] defines ANAT semantics for the SDP grouping framework.
(Note: [RFC4091] has been obsoleted by [RFC8445].) The ANAT (Note: [RFC4091] has been obsoleted by [RFC8445].) The ANAT
semantics allow alternative types of network addresses to establish a semantics allow alternative types of network addresses to establish a
particular media stream. particular media stream.
+============+==============================+=======+==============+ +============+==============================+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+============+==============================+=======+==============+ +============+==============================+=======+==============+
| group:ANAT | ANAT semantics is obsoleted. | S | CAUTION | | group:ANAT | ANAT semantics is obsoleted. | S | CAUTION |
+------------+------------------------------+-------+--------------+ +------------+------------------------------+-------+--------------+
Table 67: RFC 4091 Attribute Analysis Table 68: RFC 4091 Attribute Analysis
8.4. RFC 5956: FEC Grouping Semantics in SDP 8.4. RFC 5956: FEC Grouping Semantics in SDP
[RFC5956] defines the semantics for grouping the associated source [RFC5956] defines the semantics for grouping the associated source
and FEC-based repair flows in SDP. The semantics defined in the and FEC-based repair flows in SDP. The semantics defined in the
document are to be used with the SDP Grouping Framework [RFC5888]. document are to be used with the SDP Grouping Framework [RFC5888].
These semantics allow the description of grouping relationships These semantics allow the description of grouping relationships
between the source and repair flows when one or more source and/or between the source and repair flows when one or more source and/or
repair flows are associated in the same group; they also provide repair flows are associated in the same group; they also provide
support for additive repair flows. SSRC-level grouping semantics are support for additive repair flows. SSRC-level grouping semantics are
also defined in this document for RTP streams using SSRC also defined in this document for RTP streams using SSRC
multiplexing. multiplexing.
+==============+==============+=======+==============+ +==============+==============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+==============+==============+=======+==============+ +==============+==============+=======+==============+
| group:FEC-FR | Not impacted | S | NORMAL | | group:FEC-FR | Not impacted | S | NORMAL |
+--------------+--------------+-------+--------------+ +--------------+--------------+-------+--------------+
Table 68: RFC 5956 Attribute Analysis Table 69: RFC 5956 Attribute Analysis
8.5. RFC 5583: Signaling Media Decoding Dependency in SDP 8.5. RFC 5583: Signaling Media Decoding Dependency in SDP
[RFC5583] defines semantics that allow for signaling the decoding [RFC5583] defines semantics that allow for signaling the decoding
dependency of different media descriptions with the same media type dependency of different media descriptions with the same media type
in SDP. This is required, for example, if media data is separated in SDP. This is required, for example, if media data is separated
and transported in different network streams as a result of using a and transported in different network streams as a result of using a
layered or multiple descriptive media coding process. layered or multiple descriptive media coding process.
+===========+==========================+=======+==================+ +===========+==========================+=======+==================+
skipping to change at line 2518 skipping to change at line 2546
+-----------+--------------------------+-------+------------------+ +-----------+--------------------------+-------+------------------+
| depend | The attribute value MUST | M | IDENTICAL-PER-PT | | depend | The attribute value MUST | M | IDENTICAL-PER-PT |
| lay | be the same for a given | | | | lay | be the same for a given | | |
| | codec configuration. | | | | | codec configuration. | | |
+-----------+--------------------------+-------+------------------+ +-----------+--------------------------+-------+------------------+
| depend | The attribute value MUST | M | IDENTICAL-PER-PT | | depend | The attribute value MUST | M | IDENTICAL-PER-PT |
| mdc | be the same for a given | | | | mdc | be the same for a given | | |
| | codec configuration. | | | | | codec configuration. | | |
+-----------+--------------------------+-------+------------------+ +-----------+--------------------------+-------+------------------+
Table 69: RFC 5583 Attribute Analysis Table 70: RFC 5583 Attribute Analysis
8.6. RFC 7104: Duplication Grouping Semantics in the SDP 8.6. RFC 7104: Duplication Grouping Semantics in the SDP
[RFC7104] defines the semantics for grouping redundant streams in [RFC7104] defines the semantics for grouping redundant streams in
SDP. The semantics defined in this document are to be used with the SDP. The semantics defined in this document are to be used with the
SDP Grouping Framework. Grouping semantics at the synchronization SDP Grouping Framework. Grouping semantics at the synchronization
source (SSRC) level are also defined in this document for RTP streams source (SSRC) level are also defined in this document for RTP streams
using SSRC multiplexing. using SSRC multiplexing.
+===========+==============+=======+==============+ +===========+==============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+===========+==============+=======+==============+ +===========+==============+=======+==============+
| group:DUP | Not impacted | S | NORMAL | | group:DUP | Not impacted | S | NORMAL |
+-----------+--------------+-------+--------------+ +-----------+--------------+-------+--------------+
Table 70: RFC 7104 Attribute Analysis Table 71: RFC 7104 Attribute Analysis
9. ssrc-group Attribute Analysis 9. ssrc-group Attribute Analysis
This section analyzes "ssrc-group" semantics. This section analyzes "ssrc-group" semantics.
9.1. RFC 5576: Source-Specific SDP Attributes 9.1. RFC 5576: Source-Specific SDP Attributes
[RFC5576] defines a mechanism for describing RTP media sources -- [RFC5576] defines a mechanism for describing RTP media sources --
which are identified by their synchronization source (SSRC) which are identified by their synchronization source (SSRC)
identifiers -- in SDP, to associate attributes with these sources and identifiers -- in SDP, to associate attributes with these sources and
skipping to change at line 2559 skipping to change at line 2587
+===================+==============+=======+==============+ +===================+==============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+===================+==============+=======+==============+ +===================+==============+=======+==============+
| ssrc-group:FID | Not impacted | SR | NORMAL | | ssrc-group:FID | Not impacted | SR | NORMAL |
+-------------------+--------------+-------+--------------+ +-------------------+--------------+-------+--------------+
| ssrc-group:FEC | Not impacted | SR | NORMAL | | ssrc-group:FEC | Not impacted | SR | NORMAL |
+-------------------+--------------+-------+--------------+ +-------------------+--------------+-------+--------------+
| ssrc-group:FEC-FR | Not impacted | SR | NORMAL | | ssrc-group:FEC-FR | Not impacted | SR | NORMAL |
+-------------------+--------------+-------+--------------+ +-------------------+--------------+-------+--------------+
Table 71: RFC 5576 Attribute Analysis Table 72: RFC 5576 Attribute Analysis
9.2. RFC 7104: Duplication Grouping Semantics in the SDP 9.2. RFC 7104: Duplication Grouping Semantics in the SDP
[RFC7104] defines the semantics for grouping redundant streams in [RFC7104] defines the semantics for grouping redundant streams in
SDP. The semantics defined in this document are to be used with the SDP. The semantics defined in this document are to be used with the
SDP Grouping Framework. Grouping semantics at the synchronization SDP Grouping Framework. Grouping semantics at the synchronization
source (SSRC) level are also defined in this document for RTP streams source (SSRC) level are also defined in this document for RTP streams
using SSRC multiplexing. using SSRC multiplexing.
+================+==============+=======+==============+ +================+==============+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+================+==============+=======+==============+ +================+==============+=======+==============+
| ssrc-group:DUP | Not impacted | SR | NORMAL | | ssrc-group:DUP | Not impacted | SR | NORMAL |
+----------------+--------------+-------+--------------+ +----------------+--------------+-------+--------------+
Table 72: RFC 7104 Attribute Analysis Table 73: RFC 7104 Attribute Analysis
10. QoS Mechanism Token Analysis 10. QoS Mechanism Token Analysis
This section analyzes QoS tokes specified with SDP. This section analyzes QoS tokes specified with SDP.
10.1. RFC 5432: QoS Mechanism Selection in SDP 10.1. RFC 5432: QoS Mechanism Selection in SDP
[RFC5432] defines procedures to negotiate QoS mechanisms using the [RFC5432] defines procedures to negotiate QoS mechanisms using the
SDP offer/answer model. SDP offer/answer model.
skipping to change at line 2601 skipping to change at line 2629
| | that corresponds to the "m=" | | | | | that corresponds to the "m=" | | |
| | line chosen for setting up the | | | | | line chosen for setting up the | | |
| | underlying transport flow. | | | | | underlying transport flow. | | |
+------+--------------------------------+-------+-----------+ +------+--------------------------------+-------+-----------+
| nsis | rsvp attribute MUST be the one | B | TRANSPORT | | nsis | rsvp attribute MUST be the one | B | TRANSPORT |
| | that corresponds to the "m=" | | | | | that corresponds to the "m=" | | |
| | line chosen for setting up the | | | | | line chosen for setting up the | | |
| | underlying transport. | | | | | underlying transport. | | |
+------+--------------------------------+-------+-----------+ +------+--------------------------------+-------+-----------+
Table 73: RFC 5432 Attribute Analysis Table 74: RFC 5432 Attribute Analysis
NOTE: A single Differentiated Services Code Point (DSCP) for each NOTE: A single Differentiated Services Code Point (DSCP) for each
flow being multiplexed doesn't impact multiplexing, since QoS flow being multiplexed doesn't impact multiplexing, since QoS
mechanisms are signaled/scoped per flow. For scenarios that involve mechanisms are signaled/scoped per flow. For scenarios that involve
having different DSCP code points for packets being transmitted over having different DSCP code points for packets being transmitted over
the same 5-tuple, issues as discussed in [RFC7657] need to be taken the same 5-tuple, issues as discussed in [RFC7657] need to be taken
into consideration. into consideration.
11. k= Attribute Analysis 11. k= Attribute Analysis
skipping to change at line 2625 skipping to change at line 2653
sessions for the purposes of session announcement, session sessions for the purposes of session announcement, session
invitation, and other forms of multimedia session initiation. invitation, and other forms of multimedia session initiation.
+======+===================================+=======+==============+ +======+===================================+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+======+===================================+=======+==============+ +======+===================================+=======+==============+
| k= | It is not recommended to use this | S | CAUTION | | k= | It is not recommended to use this | S | CAUTION |
| | attribute under multiplexing. | | | | | attribute under multiplexing. | | |
+------+-----------------------------------+-------+--------------+ +------+-----------------------------------+-------+--------------+
Table 74: RFC 4566 Attribute Analysis Table 75: RFC 4566 Attribute Analysis
12. content Attribute Analysis 12. content Attribute Analysis
12.1. RFC 4796 12.1. RFC 4796
[RFC4796] defines a new SDP media-level attribute, "content". The [RFC4796] defines a new SDP media-level attribute, "content". The
"content" attribute defines the content of the media stream to a more "content" attribute defines the content of the media stream to a more
detailed level than the media description line. The sender of an SDP detailed level than the media description line. The sender of an SDP
session description can attach the "content" attribute to one or more session description can attach the "content" attribute to one or more
media streams. The receiving application can then treat each media media streams. The receiving application can then treat each media
skipping to change at line 2653 skipping to change at line 2681
+-----------------+--------------+-------+--------------+ +-----------------+--------------+-------+--------------+
| content:speaker | Not impacted | M | NORMAL | | content:speaker | Not impacted | M | NORMAL |
+-----------------+--------------+-------+--------------+ +-----------------+--------------+-------+--------------+
| content:main | Not impacted | M | NORMAL | | content:main | Not impacted | M | NORMAL |
+-----------------+--------------+-------+--------------+ +-----------------+--------------+-------+--------------+
| content:sl | Not impacted | M | NORMAL | | content:sl | Not impacted | M | NORMAL |
+-----------------+--------------+-------+--------------+ +-----------------+--------------+-------+--------------+
| content:alt | Not impacted | M | NORMAL | | content:alt | Not impacted | M | NORMAL |
+-----------------+--------------+-------+--------------+ +-----------------+--------------+-------+--------------+
Table 75: RFC 4796 Attribute Analysis Table 76: RFC 4796 Attribute Analysis
12.2. 3GPP TS 24.182 12.2. 3GPP TS 24.182
[IMS-CAT] specifies an IP multimedia subsystem for customized [IMS-CAT] specifies an IP multimedia subsystem for customized
alerting tones. alerting tones.
+============+=========================+=======+==============+ +============+=========================+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+============+=========================+=======+==============+ +============+=========================+=======+==============+
| g.3gpp.cat | Usage defined for the | M | NORMAL | | g.3gpp.cat | Usage defined for the | M | NORMAL |
| | IP multimedia subsystem | | | | | IP multimedia subsystem | | |
+------------+-------------------------+-------+--------------+ +------------+-------------------------+-------+--------------+
Table 76: 3GPP TS 24.182 Attribute Analysis Table 77: 3GPP TS 24.182 Attribute Analysis
12.3. 3GPP TS 24.183 12.3. 3GPP TS 24.183
[IMS-CRS] specifies an IP multimedia subsystem for customized ringing [IMS-CRS] specifies an IP multimedia subsystem for customized ringing
signal. signal.
+============+=========================+=======+==============+ +============+=========================+=======+==============+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+============+=========================+=======+==============+ +============+=========================+=======+==============+
| g.3gpp.crs | Usage defined for the | M | NORMAL | | g.3gpp.crs | Usage defined for the | M | NORMAL |
| | IP multimedia subsystem | | | | | IP multimedia subsystem | | |
+------------+-------------------------+-------+--------------+ +------------+-------------------------+-------+--------------+
Table 77: 3GPP TS 24.183 Attribute Analysis Table 78: 3GPP TS 24.183 Attribute Analysis
13. Payload Formats 13. Payload Formats
13.1. RFC 5109: RTP Payload Format for Generic FEC 13.1. RFC 5109: RTP Payload Format for Generic FEC
[RFC5109] describes a payload format for generic Forward Error [RFC5109] describes a payload format for generic Forward Error
Correction (FEC) for media data encapsulated in RTP. It is based on Correction (FEC) for media data encapsulated in RTP. It is based on
the exclusive-or (parity) operation. The payload format allows end the exclusive-or (parity) operation. The payload format allows end
systems to apply protection using various protection lengths and systems to apply protection using various protection lengths and
levels, in addition to using various protection group sizes to adapt levels, in addition to using various protection group sizes to adapt
skipping to change at line 2717 skipping to change at line 2745
+--------------+---------------------+-------+----------+ +--------------+---------------------+-------+----------+
| text/ulpfec | Not recommended for | M | CAUTION | | text/ulpfec | Not recommended for | M | CAUTION |
| | multiplexing due to | | | | | multiplexing due to | | |
| | reuse of SSRCs. | | | | | reuse of SSRCs. | | |
+--------------+---------------------+-------+----------+ +--------------+---------------------+-------+----------+
| application/ | Not recommended for | M | CAUTION | | application/ | Not recommended for | M | CAUTION |
| ulpfec | multiplexing due to | | | | ulpfec | multiplexing due to | | |
| | reuse of SSRCs. | | | | | reuse of SSRCs. | | |
+--------------+---------------------+-------+----------+ +--------------+---------------------+-------+----------+
Table 78: RFC 5109 Payload Format Analysis Table 79: RFC 5109 Payload Format Analysis
14. Multiplexing Considerations for Encapsulating Attributes 14. Multiplexing Considerations for Encapsulating Attributes
This section deals with recommendations for defining the multiplexing This section deals with recommendations for defining the multiplexing
characteristics of the SDP attributes that encapsulate other SDP characteristics of the SDP attributes that encapsulate other SDP
attributes/parameters. As of today, such attributes, for example, attributes/parameters. As of today, such attributes, for example,
are defined in [RFC3407], [RFC5939] and [RFC6871] as part of a are defined in [RFC3407], [RFC5939] and [RFC6871] as part of a
generic framework for indicating and negotiating transport-, media-, generic framework for indicating and negotiating transport-, media-,
and media-format-related capabilities in the SDP. and media-format-related capabilities in the SDP.
skipping to change at line 3031 skipping to change at line 3059
+-------------------------+-----------+ +-------------------------+-----------+
| INHERIT | RFC 8859 | | INHERIT | RFC 8859 |
+-------------------------+-----------+ +-------------------------+-----------+
| IDENTICAL-PER-PT | RFC 8859 | | IDENTICAL-PER-PT | RFC 8859 |
+-------------------------+-----------+ +-------------------------+-----------+
| SPECIAL | RFC 8859 | | SPECIAL | RFC 8859 |
+-------------------------+-----------+ +-------------------------+-----------+
| TBD | RFC 8859 | | TBD | RFC 8859 |
+-------------------------+-----------+ +-------------------------+-----------+
Table 79 Table 80
Further entries can be registered using Standard Actions policies Further entries can be registered using Standard Actions policies
outlined in [RFC8126], which requires IESG review and approval and outlined in [RFC8126], which requires IESG review and approval and
Standards Track IETF RFC publication. Standards Track IETF RFC publication.
Each registration needs to indicate the multiplexing category value Each registration needs to indicate the multiplexing category value
to be added to the "Multiplexing Categories" subregistry, as defined to be added to the "Multiplexing Categories" subregistry, as defined
in this section. in this section.
Such a registration MUST also indicate the applicability of the newly Such a registration MUST also indicate the applicability of the newly
skipping to change at line 3083 skipping to change at line 3111
+----------+--------------+ +----------+--------------+
| AS | SUM | | AS | SUM |
+----------+--------------+ +----------+--------------+
| RS | SUM | | RS | SUM |
+----------+--------------+ +----------+--------------+
| RR | SUM | | RR | SUM |
+----------+--------------+ +----------+--------------+
| TIAS | SPECIAL | | TIAS | SPECIAL |
+----------+--------------+ +----------+--------------+
Table 80 Table 81
15.2.2. Table: attribute-name 15.2.2. Table: attribute-name
The following values have been added to the "attribute-name" The following values have been added to the "attribute-name"
(formerly "att-field") subregistry of the "Session Description (formerly "att-field") subregistry of the "Session Description
Protocol (SDP) Parameters" registry. The references have been Protocol (SDP) Parameters" registry. The references have been
updated to point to this RFC as well as the previous references. updated to point to this RFC as well as the previous references.
NOTE: The attributes from [FLUTE] ("flute-tsi", "flute-ch", "FEC- NOTE: The attributes from [FLUTE] ("flute-tsi", "flute-ch", "FEC-
declaration", "FEC-OTI-extension", "content-desc") were not analyzed declaration", "FEC-OTI-extension", "content-desc") were not analyzed
skipping to change at line 3249 skipping to change at line 3277
| mscap | INHERIT | | mscap | INHERIT |
+--------------------------+------------------+ +--------------------------+------------------+
| 3gpp.iut.replication | TBD | | 3gpp.iut.replication | TBD |
+--------------------------+------------------+ +--------------------------+------------------+
| bcap | INHERIT | | bcap | INHERIT |
+--------------------------+------------------+ +--------------------------+------------------+
| ccap | IDENTICAL | | ccap | IDENTICAL |
+--------------------------+------------------+ +--------------------------+------------------+
| icap | NORMAL | | icap | NORMAL |
+--------------------------+------------------+ +--------------------------+------------------+
| etag | CAUTION |
+--------------------------+------------------+
| duplication-delay | NORMAL | | duplication-delay | NORMAL |
+--------------------------+------------------+ +--------------------------+------------------+
| range | CAUTION | | range | CAUTION |
+--------------------------+------------------+ +--------------------------+------------------+
| control | CAUTION | | control | CAUTION |
+--------------------------+------------------+ +--------------------------+------------------+
| mtag | CAUTION | | mtag | CAUTION |
+--------------------------+------------------+ +--------------------------+------------------+
| ts-refclk | NORMAL | | ts-refclk | NORMAL |
+--------------------------+------------------+ +--------------------------+------------------+
skipping to change at line 3572 skipping to change at line 3602
+--------------------------+------------------+ +--------------------------+------------------+
| previous-ssrc | NORMAL | | previous-ssrc | NORMAL |
+--------------------------+------------------+ +--------------------------+------------------+
| fmtp | IDENTICAL-PER-PT | | fmtp | IDENTICAL-PER-PT |
+--------------------------+------------------+ +--------------------------+------------------+
| ts-refclk | NORMAL | | ts-refclk | NORMAL |
+--------------------------+------------------+ +--------------------------+------------------+
| mediaclk | NORMAL | | mediaclk | NORMAL |
+--------------------------+------------------+ +--------------------------+------------------+
Table 81 Table 82
15.2.3. Table: content SDP Parameters 15.2.3. Table: content SDP Parameters
The following values have been added to the "content SDP Parameters" The following values have been added to the "content SDP Parameters"
subregistry of the "Session Description Protocol (SDP) Parameters" subregistry of the "Session Description Protocol (SDP) Parameters"
registry. The references have been updated to point to this RFC as registry. The references have been updated to point to this RFC as
well as the previous references. well as the previous references.
+============+==============+ +============+==============+
| SDP Name | Mux Category | | SDP Name | Mux Category |
skipping to change at line 3599 skipping to change at line 3629
+------------+--------------+ +------------+--------------+
| main | NORMAL | | main | NORMAL |
+------------+--------------+ +------------+--------------+
| alt | NORMAL | | alt | NORMAL |
+------------+--------------+ +------------+--------------+
| g.3gpp.cat | NORMAL | | g.3gpp.cat | NORMAL |
+------------+--------------+ +------------+--------------+
| g.3gpp.crs | NORMAL | | g.3gpp.crs | NORMAL |
+------------+--------------+ +------------+--------------+
Table 82 Table 83
15.2.4. Table: Semantics for the "group" SDP Attribute 15.2.4. Table: Semantics for the "group" SDP Attribute
The following values have been added to the "Semantics for the The following values have been added to the "Semantics for the
'group' SDP Attribute" subregistry of the "Session Description 'group' SDP Attribute" subregistry of the "Session Description
Protocol (SDP) Parameters" registry. The references have been Protocol (SDP) Parameters" registry. The references have been
updated to point to this RFC as well as the previous references. updated to point to this RFC as well as the previous references.
+========+==============+ +========+==============+
| Token | Mux Category | | Token | Mux Category |
skipping to change at line 3630 skipping to change at line 3660
+--------+--------------+ +--------+--------------+
| FEC-FR | NORMAL | | FEC-FR | NORMAL |
+--------+--------------+ +--------+--------------+
| CS | NORMAL | | CS | NORMAL |
+--------+--------------+ +--------+--------------+
| DDP | NORMAL | | DDP | NORMAL |
+--------+--------------+ +--------+--------------+
| DUP | NORMAL | | DUP | NORMAL |
+--------+--------------+ +--------+--------------+
Table 83 Table 84
15.2.5. Table: "rtcp-fb" Attribute Values 15.2.5. Table: "rtcp-fb" Attribute Values
The following values have been added to the "'rtcp-fb' Attribute The following values have been added to the "'rtcp-fb' Attribute
Values" subregistry of the "Session Description Protocol (SDP) Values" subregistry of the "Session Description Protocol (SDP)
Parameters" registry. The references have been updated to point to Parameters" registry. The references have been updated to point to
this RFC as well as the previous references. this RFC as well as the previous references.
+============+==================+ +============+==================+
| Value Name | Mux Category | | Value Name | Mux Category |
skipping to change at line 3653 skipping to change at line 3683
+------------+------------------+ +------------+------------------+
| app | SPECIAL | | app | SPECIAL |
+------------+------------------+ +------------+------------------+
| ccm | IDENTICAL-PER-PT | | ccm | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
| nack | IDENTICAL-PER-PT | | nack | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
| trr-int | IDENTICAL-PER-PT | | trr-int | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
Table 84 Table 85
15.2.6. Table: "ack" and "nack" Attribute Values 15.2.6. Table: "ack" and "nack" Attribute Values
The following values have been added to the "'ack' and 'nack' The following values have been added to the "'ack' and 'nack'
Attribute Values" subregistry of the "Session Description Protocol Attribute Values" subregistry of the "Session Description Protocol
(SDP) Parameters" registry. The references have been updated to (SDP) Parameters" registry. The references have been updated to
point to this RFC as well as the previous references. point to this RFC as well as the previous references.
+============+==================+ +============+==================+
| Value Name | Mux Category | | Value Name | Mux Category |
skipping to change at line 3682 skipping to change at line 3712
+------------+------------------+ +------------+------------------+
| rai | IDENTICAL-PER-PT | | rai | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
| tllei | IDENTICAL-PER-PT | | tllei | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
| pslei | IDENTICAL-PER-PT | | pslei | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
| ecn | IDENTICAL | | ecn | IDENTICAL |
+------------+------------------+ +------------+------------------+
Table 85 Table 86
15.2.7. Table: "depend" SDP Attribute Values 15.2.7. Table: "depend" SDP Attribute Values
The following values have been added to the "'depend' SDP Attribute The following values have been added to the "'depend' SDP Attribute
Values" subregistry of the "Session Description Protocol (SDP) Values" subregistry of the "Session Description Protocol (SDP)
Parameters" registry. The references have been updated to point to Parameters" registry. The references have been updated to point to
this RFC as well as the previous references. this RFC as well as the previous references.
+=======+==================+ +=======+==================+
| Token | Mux Category | | Token | Mux Category |
+=======+==================+ +=======+==================+
| lay | IDENTICAL-PER-PT | | lay | IDENTICAL-PER-PT |
+-------+------------------+ +-------+------------------+
| mdc | IDENTICAL-PER-PT | | mdc | IDENTICAL-PER-PT |
+-------+------------------+ +-------+------------------+
Table 86 Table 87
15.2.8. Table: "cs-correlation" Attribute Values 15.2.8. Table: "cs-correlation" Attribute Values
The following values have been added to the "'cs-correlation' The following values have been added to the "'cs-correlation'
Attribute Values" subregistry of the "Session Description Protocol Attribute Values" subregistry of the "Session Description Protocol
(SDP) Parameters" registry. The references have been updated to (SDP) Parameters" registry. The references have been updated to
point to this RFC as well as the previous references. point to this RFC as well as the previous references.
+==========+==============+ +==========+==============+
| Value | Mux Category | | Value | Mux Category |
+==========+==============+ +==========+==============+
| callerid | TBD | | callerid | TBD |
+----------+--------------+ +----------+--------------+
| uuie | TBD | | uuie | TBD |
+----------+--------------+ +----------+--------------+
| dtmf | TBD | | dtmf | TBD |
+----------+--------------+ +----------+--------------+
| external | TBD | | external | TBD |
+----------+--------------+ +----------+--------------+
Table 87 Table 88
15.2.9. Table: Semantics for the "ssrc-group" SDP Attribute 15.2.9. Table: Semantics for the "ssrc-group" SDP Attribute
The following values have been added to the "Semantics for the 'ssrc- The following values have been added to the "Semantics for the 'ssrc-
group' SDP Attribute" subregistry of the "Session Description group' SDP Attribute" subregistry of the "Session Description
Protocol (SDP) Parameters" registry. The references have been Protocol (SDP) Parameters" registry. The references have been
updated to point to this RFC as well as the previous references. updated to point to this RFC as well as the previous references.
+========+==============+ +========+==============+
| Token | Mux Category | | Token | Mux Category |
+========+==============+ +========+==============+
| FID | NORMAL | | FID | NORMAL |
+--------+--------------+ +--------+--------------+
| FEC | NORMAL | | FEC | NORMAL |
+--------+--------------+ +--------+--------------+
| FEC-FR | NORMAL | | FEC-FR | NORMAL |
+--------+--------------+ +--------+--------------+
| DUP | NORMAL | | DUP | NORMAL |
+--------+--------------+ +--------+--------------+
Table 88 Table 89
15.2.10. Table: SDP/RTSP Key Management Protocol Identifiers 15.2.10. Table: SDP/RTSP Key Management Protocol Identifiers
The following values have been added to the "SDP/RTSP key management The following values have been added to the "SDP/RTSP key management
protocol identifiers" subregistry of the "Session Description protocol identifiers" subregistry of the "Session Description
Protocol (SDP) Parameters" registry. The references have been Protocol (SDP) Parameters" registry. The references have been
updated to point to this RFC as well as the previous references. updated to point to this RFC as well as the previous references.
+============+==============+ +============+==============+
| Value Name | Mux Category | | Value Name | Mux Category |
+============+==============+ +============+==============+
| mikey | IDENTICAL | | mikey | IDENTICAL |
+------------+--------------+ +------------+--------------+
Table 89 Table 90
15.2.11. Table: Codec Control Messages 15.2.11. Table: Codec Control Messages
The following values have been added to the "Codec Control Messages" The following values have been added to the "Codec Control Messages"
subregistry of the "Session Description Protocol (SDP) Parameters" subregistry of the "Session Description Protocol (SDP) Parameters"
registry. The references have been updated to point to this RFC as registry. The references have been updated to point to this RFC as
well as the previous references. well as the previous references.
+============+==================+ +============+==================+
| Value Name | Mux Category | | Value Name | Mux Category |
+============+==================+ +============+==================+
| fir | IDENTICAL-PER-PT | | fir | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
| tmmbr | IDENTICAL-PER-PT | | tmmbr | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
| tstr | IDENTICAL-PER-PT | | tstr | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
| vbcm | IDENTICAL-PER-PT | | vbcm | IDENTICAL-PER-PT |
+------------+------------------+ +------------+------------------+
Table 90 Table 91
15.2.12. Table: QoS Mechanism Tokens 15.2.12. Table: QoS Mechanism Tokens
The following values have been added to the "QoS Mechanism Tokens" The following values have been added to the "QoS Mechanism Tokens"
subregistry of the "Session Description Protocol (SDP) Parameters" subregistry of the "Session Description Protocol (SDP) Parameters"
registry. The references have been updated to point to this RFC as registry. The references have been updated to point to this RFC as
well as the previous references. well as the previous references.
+===============+==============+ +===============+==============+
| QoS Mechanism | Mux Category | | QoS Mechanism | Mux Category |
+===============+==============+ +===============+==============+
| rsvp | TRANSPORT | | rsvp | TRANSPORT |
+---------------+--------------+ +---------------+--------------+
| nsis | TRANSPORT | | nsis | TRANSPORT |
+---------------+--------------+ +---------------+--------------+
Table 91 Table 92
15.2.13. Table: SDP Capability Negotiation Option Tags 15.2.13. Table: SDP Capability Negotiation Option Tags
The following values have been added to the "SDP Capability The following values have been added to the "SDP Capability
Negotiation Option Tags" subregistry of the "Session Description Negotiation Option Tags" subregistry of the "Session Description
Protocol (SDP) Parameters" registry. The references have been Protocol (SDP) Parameters" registry. The references have been
updated to point to this RFC as well as the previous references. updated to point to this RFC as well as the previous references.
+============+==============+ +============+==============+
| Option Tag | Mux Category | | Option Tag | Mux Category |
skipping to change at line 3817 skipping to change at line 3847
+------------+--------------+ +------------+--------------+
| med-v0 | NORMAL | | med-v0 | NORMAL |
+------------+--------------+ +------------+--------------+
| bcap-v0 | NORMAL | | bcap-v0 | NORMAL |
+------------+--------------+ +------------+--------------+
| ccap-v0 | NORMAL | | ccap-v0 | NORMAL |
+------------+--------------+ +------------+--------------+
| icap-v0 | NORMAL | | icap-v0 | NORMAL |
+------------+--------------+ +------------+--------------+
Table 92 Table 93
15.2.14. Table: Timestamp Reference Clock Source Parameters 15.2.14. Table: Timestamp Reference Clock Source Parameters
The following values have been added to the "Timestamp Reference The following values have been added to the "Timestamp Reference
Clock Source Parameters" subregistry of the "Session Description Clock Source Parameters" subregistry of the "Session Description
Protocol (SDP) Parameters" registry. The references have been Protocol (SDP) Parameters" registry. The references have been
updated to point to this RFC as well as the previous references. updated to point to this RFC as well as the previous references.
+=========+==============+ +=========+==============+
| Name | Mux Category | | Name | Mux Category |
skipping to change at line 3844 skipping to change at line 3874
+---------+--------------+ +---------+--------------+
| gal | NORMAL | | gal | NORMAL |
+---------+--------------+ +---------+--------------+
| glonass | NORMAL | | glonass | NORMAL |
+---------+--------------+ +---------+--------------+
| local | NORMAL | | local | NORMAL |
+---------+--------------+ +---------+--------------+
| private | NORMAL | | private | NORMAL |
+---------+--------------+ +---------+--------------+
Table 93 Table 94
15.2.15. Table: Media Clock Source Parameters 15.2.15. Table: Media Clock Source Parameters
The following values have been added to the "Media Clock Source The following values have been added to the "Media Clock Source
Parameters" subregistry of the "Session Description Protocol (SDP) Parameters" subregistry of the "Session Description Protocol (SDP)
Parameters" registry. The references have been updated to point to Parameters" registry. The references have been updated to point to
this RFC as well as the previous references. this RFC as well as the previous references.
+==========+==============+ +==========+==============+
| Name | Mux Category | | Name | Mux Category |
+==========+==============+ +==========+==============+
| sender | NORMAL | | sender | NORMAL |
+----------+--------------+ +----------+--------------+
| direct | NORMAL | | direct | NORMAL |
+----------+--------------+ +----------+--------------+
| IEEE1722 | NORMAL | | IEEE1722 | NORMAL |
+----------+--------------+ +----------+--------------+
Table 94 Table 95
16. Security Considerations 16. Security Considerations
The primary security considerations for RTP, including the way it is The primary security considerations for RTP, including the way it is
used here, are described in [RFC3550] and [RFC3711]. used here, are described in [RFC3550] and [RFC3711].
When multiplexing SDP attributes with the category "CAUTION", the When multiplexing SDP attributes with the category "CAUTION", the
implementations should be aware of possible issues described in this implementations should be aware of possible issues described in this
specification. specification.
skipping to change at line 3937 skipping to change at line 3967
[IP-CALL] 3GPP, "IP multimedia call control protocol based on [IP-CALL] 3GPP, "IP multimedia call control protocol based on
Session Initiation Protocol (SIP) and Session Description Session Initiation Protocol (SIP) and Session Description
Protocol (SDP); Stage 3", Specification 24.229, September Protocol (SDP); Stage 3", Specification 24.229, September
2016, 2016,
<https://www.3gpp.org/ftp/Specs/html-info/24229.htm>. <https://www.3gpp.org/ftp/Specs/html-info/24229.htm>.
[Q.1970] ITU-T, "Q.1970: BICC IP bearer control protocol", ITU-T [Q.1970] ITU-T, "Q.1970: BICC IP bearer control protocol", ITU-T
Recommendation Q.1970, September 2006, Recommendation Q.1970, September 2006,
<https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>. <https://www.itu.int/rec/T-REC-Q.1970-200609-I/en>.
[RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time
Streaming Protocol (RTSP)", RFC 2326,
DOI 10.17487/RFC2326, April 1998,
<https://www.rfc-editor.org/info/rfc2326>.
[RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the [RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the
Session Description Protocol (SDP) for ATM Bearer Session Description Protocol (SDP) for ATM Bearer
Connections", RFC 3108, DOI 10.17487/RFC3108, May 2001, Connections", RFC 3108, DOI 10.17487/RFC3108, May 2001,
<https://www.rfc-editor.org/info/rfc3108>. <https://www.rfc-editor.org/info/rfc3108>.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
DOI 10.17487/RFC3264, June 2002, DOI 10.17487/RFC3264, June 2002,
<https://www.rfc-editor.org/info/rfc3264>. <https://www.rfc-editor.org/info/rfc3264>.
skipping to change at line 4314 skipping to change at line 4349
IPTV stage 3 specification", Technical Specification 183 IPTV stage 3 specification", Technical Specification 183
063 V2.1.0, June 2008, <https://www.etsi.org/deliver/ 063 V2.1.0, June 2008, <https://www.etsi.org/deliver/
etsi_ts/183000_183099/183063/02.01.00_60/ etsi_ts/183000_183099/183063/02.01.00_60/
ts_183063v020100p.pdf>. ts_183063v020100p.pdf>.
Acknowledgements Acknowledgements
I would like to thank Cullen Jennings and Flemming Andreasen for I would like to thank Cullen Jennings and Flemming Andreasen for
suggesting the categories, contributing text, and reviewing the draft suggesting the categories, contributing text, and reviewing the draft
of this document. I would also like to thank Magnus Westerlund, of this document. I would also like to thank Magnus Westerlund,
Christer Holmberg, Jonathan Lennox, Bo Burman, Ari Keranen, and Dan Christer Holmberg, Jonathan Lennox, Bo Burman, Ari Kerรคnen, and Dan
Wing for suggesting structural changes that improved the document's Wing for suggesting structural changes that improved the document's
readability. readability.
I would like also to thank the following experts for their inputs and I would like also to thank the following experts for their inputs and
reviews as listed: reviews as listed:
Flemming Andreasen (5.24, 5.32, 5.33, 14), Flemming Andreasen (5.24, 5.32, 5.33, 14),
Rohan Mahy (5.54), Rohan Mahy (5.54),
Eric Burger (5.26), Eric Burger (5.26),
Christian Huitema (5.14), Christian Huitema (5.14),
 End of changes. 63 change blocks. 
70 lines changed or deleted 105 lines changed or added

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