rfc8859xml2.original.xml   rfc8859.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<!ENTITY RFC2119 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.2119.xml">
<!ENTITY RFC2617 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.2617.xml">
<!ENTITY RFC2326 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.2326.xml">
<!ENTITY RFC4566 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4566.xml">
<!ENTITY RFC3108 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3108.xml">
<!ENTITY RFC3264 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3264.xml">
<!ENTITY RFC3312 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3312.xml">
<!ENTITY RFC3407 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3407.xml">
<!ENTITY RFC3524 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3524.xml">
<!ENTITY RFC3550 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3550.xml">
<!ENTITY RFC3556 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3556.xml">
<!ENTITY RFC3605 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3605.xml">
<!ENTITY RFC3611 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3611.xml">
<!ENTITY RFC3711 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3711.xml">
<!ENTITY RFC3890 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.3890.xml">
<!ENTITY RFC4091 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4091.xml">
<!ENTITY RFC4145 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4145.xml">
<!ENTITY RFC4567 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4567.xml">
<!ENTITY RFC4568 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4568.xml">
<!ENTITY RFC4570 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4570.xml">
<!ENTITY RFC4572 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4572.xml">
<!ENTITY RFC4574 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4574.xml">
<!ENTITY RFC4583 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4583.xml">
<!ENTITY RFC4585 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4585.xml">
<!ENTITY RFC4796 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4796.xml">
<!ENTITY RFC4975 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.4975.xml">
<!ENTITY RFC5104 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5104.xml">
<!ENTITY RFC5109 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5109.xml">
<!ENTITY RFC5159 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5159.xml">
<!ENTITY RFC5226 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5226.xml">
<!ENTITY RFC5245 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5245.xml">
<!ENTITY RFC5285 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5285.xml">
<!ENTITY RFC5432 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5432.xml">
<!ENTITY RFC5506 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5506.xml">
<!ENTITY RFC5547 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5547.xml">
<!ENTITY RFC5576 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5576.xml">
<!ENTITY RFC5583 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5583.xml">
<!ENTITY RFC5760 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5760.xml">
<!ENTITY RFC5761 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5761.xml">
<!ENTITY RFC5762 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5762.xml">
<!ENTITY RFC5763 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5763.xml">
<!ENTITY RFC5888 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5888.xml">
<!ENTITY RFC5939 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5939.xml">
<!ENTITY RFC5956 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.5956.xml">
<!ENTITY RFC6064 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6064.xml">
<!ENTITY RFC6128 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6128.xml">
<!ENTITY RFC6189 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6189.xml">
<!ENTITY RFC6193 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6193.xml">
<!ENTITY RFC6230 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6230.xml">
<!ENTITY RFC6236 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6236.xml">
<!ENTITY RFC6284 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6284.xml">
<!ENTITY RFC6285 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6285.xml">
<!ENTITY RFC6364 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6364.xml">
<!ENTITY RFC6642 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6642.xml">
<!ENTITY RFC6679 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6679.xml">
<!ENTITY RFC6714 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6714.xml">
<!ENTITY RFC6773 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6773.xml">
<!ENTITY RFC6787 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6787.xml">
<!ENTITY RFC6849 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6849.xml">
<!ENTITY RFC6871 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6871.xml">
<!ENTITY RFC6947 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.6947.xml">
<!ENTITY RFC7006 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.7006.xml">
<!ENTITY RFC7104 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.7104.xml">
<!ENTITY RFC7197 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.7195.xml">
<!ENTITY RFC7195 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.7197.xml">
<!ENTITY RFC7272 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.7272.xml">
<!ENTITY RFC7273 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.7273.xml">
<!ENTITY I-D.ietf-mmusic-sdp-bundle-negotiation SYSTEM
"http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-mmusic-s
dp-bundle-negotiation.xml">
<!ENTITY I-D.ietf-mmusic-rfc4566bis SYSTEM
"https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-
mmusic-rfc4566bis.xml">
<!ENTITY RFC7266 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.7266.xml">
<!ENTITY RFC7657 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC
.7657.xml">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<?rfc toc="yes" ?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std"
<?rfc symrefs="yes" ?> ipr="trust200902" number="8859" submissionType="IETF" consensus="true"
<?rfc strict="yes" ?> obsoletes="" updates="" xml:lang="en" tocInclude="true" symRefs="true"
<?rfc compact="yes" ?> sortRefs="true" version="3" docName="draft-ietf-mmusic-sdp-mux-attributes-1
<?rfc sortrefs="yes" ?> 7">
<?rfc colonspace="yes" ?>
<?rfc rfcedstyle="no" ?>
<?rfc tocdepth="4"?>
<rfc category="std" docName="draft-ietf-mmusic-sdp-mux-attributes-17" <!-- xml2rfc v2v3 conversion 2.30.0 -->
ipr="trust200902">
<front> <front>
<title abbrev="SDP Attribute Multiplexing">A Framework for SDP Attributes
when Multiplexing</title>
<author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar"> <title abbrev="SDP Attribute Multiplexing">A Framework for Session
Description Protocol (SDP) Attributes When Multiplexing</title>
<seriesInfo name="RFC" value="8859"/>
<author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar">
<organization>Cisco</organization> <organization>Cisco</organization>
<address> <address>
<postal> <postal>
<street>170 West Tasman Drive</street> <street>170 West Tasman Drive</street>
<city>San Jose</city> <city>San Jose</city>
<region>CA</region> <region>CA</region>
<code>95134</code> <code>95134</code>
<country>United States of America</country>
<country>USA</country>
</postal> </postal>
<email>snandaku@cisco.com</email> <email>snandaku@cisco.com</email>
</address> </address>
</author> </author>
<date month="May" year="2020"/>
<date day="28" month="February" year="2018"/> <area>ART</area>
<workgroup>MMUSIC</workgroup>
<area>MMUSIC</area>
<abstract> <abstract>
<t>The purpose of this specification is to provide a framework <t>The purpose of this specification is to provide a framework
for analyzing the multiplexing characteristics of Session Description for analyzing the multiplexing characteristics of Session Description
Protocol (SDP) attributes when SDP is used to negotiate the usage of Protocol (SDP) attributes when SDP is used to negotiate the usage of a
single 5-tuple for sending and receiving media associated with multiple single 5-tuple for sending and receiving media associated with multiple
media descriptions.</t> media descriptions.</t>
<t>This specification also categorizes the existing SDP attributes based <t>This specification also categorizes the existing SDP attributes based
on the framework described herein.</t> on the framework described herein.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section title="Introduction" anchor="sec-intro"> <section anchor="sec-intro" numbered="true" toc="default">
<t> SDP defines several attributes for capturing characteristics that <name>Introduction</name>
apply to the individual media descriptions (described by "m=" lines") <t>SDP defines several attributes for capturing characteristics that
and the overall multimedia session. Typically different media types apply to the individual media descriptions (described by "m=" lines)
and the overall multimedia session. Typically, different media types
(audio, video, etc.) described using different media descriptions (audio, video, etc.) described using different media descriptions
represent separate RTP sessions that are carried over individual represent separate RTP sessions that are carried over individual
transport layer flows. However <xref target="I-D.ietf-mmusic-sdp-bundle- negotiation"/> transport-layer flows. However, <xref target="RFC8843" format="default"/ >
defines a way to use a single address:port combination (BUNDLE address) defines a way to use a single address:port combination (BUNDLE address)
for receiving media associated with multiple SDP media for receiving media associated with multiple SDP media
descriptions. This would, for example allow the usage of a descriptions. This would, for example, allow the usage of a
single set of Interactive Connectivity Establishment (ICE) <xref target= single set of Interactive Connectivity Establishment (ICE) <xref target=
"RFC5245"/> "RFC8445" format="default"/>
candidates for multiple media descriptions. This in turn has made candidates for multiple media descriptions. This, in turn, has made
it necessary to understand the interpretation and usage of the SDP it necessary to understand the interpretation and usage of the SDP
attributes defined for the multiplexed media descriptions.</t> attributes defined for the multiplexed media descriptions.</t>
<t> Given the number of SDP attributes registered with the <t>Given the number of SDP attributes registered with the
<xref target="IANA"></xref> and possibility of new attributes <xref target="IANA" format="default"/> and the possibility of new attrib
utes
being defined in the future, there is need for a framework to being defined in the future, there is need for a framework to
analyze these attributes for their applicability in the transport analyze these attributes for their applicability in the transport
multiplexing use-cases.</t> multiplexing use cases.</t>
<t> The document starts with providing the motivation for <t>The document starts with providing the motivation for
requiring such a framework. This is followed by introduction requiring such a framework. This is followed by introduction
to the SDP attribute analysis framework/procedures, following to the SDP attribute analysis framework and procedures, following
which several sections apply the framework to the SDP which several sections apply the framework to the SDP
attributes registered with the <xref target="IANA"></xref>. attributes registered with the <xref target="IANA" format="default"/>.
</t> </t>
</section> </section>
<section title="Terminology"> <section numbered="true" toc="default">
<t>5-tuple: A collection of the following values: source address, <name>Terminology</name>
<dl>
<dt>5-tuple:</dt><dd>A collection of the following values: source address,
source port, destination address, destination port, and source port, destination address, destination port, and
transport-layer protocol.</t> transport-layer protocol.</dd>
<t>3GPP: Third Generation Partnership Project; see <dt>3GPP:</dt><dd>Third Generation Partnership Project; see
http://www.3gpp.org for more information about this <eref target="https://www.3gpp.org" brackets="angle"/> for more informat
organization.</t> ion about this
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", organization.</dd>
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and </dl>
"OPTIONAL" in this document are to be interpreted as described in <xref <t>
target="RFC2119"></xref>.</t> The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
</section> IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
<section title="Motivation"> NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
<t>The time and complications of setting up ICE <xref RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
target="RFC5245"></xref> and Datagram Transport Layer Security "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
(DTLS) based Secure Real-time Transport Protocol (SRTP) <xref be interpreted as
target="RFC5763"></xref> transports for use by RTP, reasons described in BCP&nbsp;14 <xref target="RFC2119" format="default"/> <xref tar
to conserve ports bindings on the Network Address Translators (NAT), get="RFC8174" format="default"/>
forms a requirement to try and reduce the number of transport when, and only when, they appear in all capitals, as shown here.
level flows needed. This has resulted in the definition of ways, </t>
such as <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref> </section>
<section numbered="true" toc="default">
<name>Motivation</name>
<t>
An effort to reduce the number of necessary transport-level flows is
required because of the time and complications involved in setting up
Secure Real-time Transport Protocol (SRTP) <xref target="RFC5763"/>
transports for use by RTP based on ICE <xref target="RFC8445"/> and
Datagram Transport Layer Security (DTLS). These procedures motivate
conservation of ports bindings on the Network Address Translators (NATs).
This necessity has resulted in the definition of ways,
such as that described in <xref target="RFC8843" format="default"/>,
to multiplex RTP over a single transport flow in order to to multiplex RTP over a single transport flow in order to
preserve network resources such as port numbers. This imposes preserve network resources such as port numbers. This imposes
further restrictions on applicability of the SDP attributes further restrictions on applicability of the SDP attributes
as they are defined today.</t> as they are defined today.</t>
<t>The specific problem is that there are attribute combinations <t>The specific problem is that there are attribute combinations
which make sense when specified on independent "m=" lines -- as that make sense when specified on independent "m=" lines -- as
with classical SDP -- that do not make sense when those with classical SDP -- that do not make sense when those
"m=" lines are then multiplexed over the same transport. To give "m=" lines are then multiplexed over the same transport. To give
an obvious example, ICE permits each "m=" line to have an an obvious example, ICE permits each "m=" line to have an
independently specified ice-ufrag attribute. However, if the independently specified "ice-ufrag" attribute. However, if the
media from multiple "m=" lines is multiplexed over the same ICE media from multiple "m=" lines is multiplexed over the same ICE
component, then the meaning of media-level ice-ufrag component, then the meaning of media-level "ice-ufrag"
attributes becomes muddled.</t> attributes becomes muddled.</t>
<t>At the time of writing this document there are close to 250 SDP <t>At the time of writing this document, there are close to 250 SDP
attributes registered with the <xref target="IANA"></xref> and more attributes registered with the <xref target="IANA" format="default"/>, an
d more
will be added in the future. There is no clearly defined procedure to will be added in the future. There is no clearly defined procedure to
establish the validity/applicability of these attributes when establish the validity/applicability of these attributes when
used with transport multiplexing.</t> used with transport multiplexing.</t>
</section> </section>
<section title="SDP Attribute Analysis Framework" anchor="sec-mux-fwork"> <section anchor="sec-mux-fwork" numbered="true" toc="default">
<name>SDP Attribute Analysis Framework</name>
<t>Attributes in an SDP session description can be defined at the <t>Attributes in an SDP session description can be defined at the
session-level or media-level or source-level. Informally, there are session level, media level, or source level. Informally, there are
various semantic groupings for these attributes. One such grouping various semantic groupings for these attributes. One such grouping
could be notes as below:</t> could be as follows:</t>
<t> <ul spacing="normal">
<list style="symbols"> <li>Attributes related to media content such as media type,
<t>Attributes related to media content such as media type, encoding schemes, and payload types.</li>
encoding schemes and payload types.</t> <li>Attributes specifying media transport characteristics such as
<t>Attributes specifying media transport characteristics like RTP/RTP Control Protocol (RTCP) port numbers, network addresses,
RTP/RTP Control Protocol (RTCP) port numbers, network addresses and QoS.</li>
and QOS.</t> <li>Metadata description attributes capturing session timing and
<t>Metadata description attributes capturing session timing and origin information.</li>
origin information.</t> <li>Attributes establishing relationships between media descriptions,
<t>Attributes establishing relationships between media descriptions such as grouping framework <xref target="RFC5888" format="default"/>.<
such as grouping framework <xref target="RFC5888"/></t> /li>
</list> </ul>
</t>
<t>The proposed framework analyzes the SDP attributes usage <t>The proposed framework analyzes the SDP attributes usage
under multiplexing and assigns each SDP attribute to an appropriate under multiplexing and assigns each SDP attribute to an appropriate
multiplexing category. Since the multiplexing categories defined in multiplexing category. Since the multiplexing categories defined in
this specification are independent of any informal semantic groupings this specification are independent of any informal semantic groupings
of the SDP attributes, the categorizations assigned are normative.</t> of the SDP attributes, the categorizations assigned are normative.</t>
<section numbered="true" toc="default">
<section title="Category: NORMAL"> <name>Category: NORMAL</name>
<t>The attributes in the NORMAL category can be independently <t>The attributes in the NORMAL category can be independently
specified when multiplexed and they retain their original specified when multiplexed, and they retain their original
semantics.</t> semantics.</t>
<t>&nbsp;</t>
<t>In the example given below, the direction and label <t>In the example given below, the direction and label
attributes are independently specified for audio and video attributes are independently specified for audio and video
"m=" lines. These attributes are not impacted by multiplexing "m=" lines. These attributes are not impacted by multiplexing
these media streams over a single transport layer flow.</t> these media streams over a single transport-layer flow.</t>
<figure>
<artwork align="left" alt="" height="" name="" type="" width="" <sourcecode type="sdp">
xml:space="preserve"><![CDATA[
v=0 v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s= s=
c=IN IP4 host.atlanta.example.com c=IN IP4 host.atlanta.example.com
t=0 0 t=0 0
m=audio 49172 RTP/AVP 99 m=audio 49172 RTP/AVP 99
a=sendonly a=sendonly
a=label:1 a=label:1
a=rtpmap:99 iLBC/8000 a=rtpmap:99 iLBC/8000
m=video 49172 RTP/AVP 31 m=video 49172 RTP/AVP 31
a=recvonly a=recvonly
a=label:2 a=label:2
a=rtpmap:31 H261/90000 a=rtpmap:31 H261/90000
]]></artwork> </sourcecode>
</figure>
<t>&nbsp;</t>
</section> </section>
<section title="Category: CAUTION"> <section numbered="true" toc="default">
<t>The attributes in the CAUTION category are advised <name>Category: CAUTION</name>
against multiplexing since their usage under multiplexing <t>It is not advisable to multiplex with the attributes in the CAUTION
category, since their usage under multiplexing
might lead to incorrect behavior.</t> might lead to incorrect behavior.</t>
<t>&nbsp;</t>
<t>Example: Multiplexing media descriptions over a single <t>Example: Multiplexing media descriptions over a single
Datagram Congestion Control Protocol (DCCP) transport Datagram Congestion Control Protocol (DCCP) transport
<xref target="RFC5762"/> is not recommended <xref target="RFC5762" format="default"/> is not recommended,
since DCCP being a connection oriented protocol doesn't since DCCP is a connection-oriented protocol and therefore doesn't
allow multiple connections on the same 5-tuple.</t> allow multiple connections on the same 5-tuple.</t>
<figure>
<artwork align="left" alt="" height="" name="" type="" width="" <sourcecode type="sdp">
xml:space="preserve"><![CDATA[
v=0 v=0
o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com
s= s=
c=IN IP4 client.biloxi.example.com c=IN IP4 client.biloxi.example.com
t=0 0 t=0 0
m=video 5004 DCCP/RTP/AVP 99 m=video 5004 DCCP/RTP/AVP 99
a=rtpmap:99 h261/9000 a=rtpmap:99 h261/9000
a=dccp-service-code:SC=x52545056 a=dccp-service-code:SC=x52545056
a=setup:passive a=setup:passive
a=connection:new a=connection:new
m=video 5004 DCCP/RTP/AVP 100 m=video 5004 DCCP/RTP/AVP 100
a=rtpmap:100 h261/9000 a=rtpmap:100 h261/9000
a=dccp-service-code:SC=x5254504f a=dccp-service-code:SC=x5254504f
a=setup:passive a=setup:passive
a=connection:new a=connection:new
]]></artwork> </sourcecode>
</figure>
<t>&nbsp;</t>
</section> </section>
<section title="Category: IDENTICAL"> <section numbered="true" toc="default">
<t>The attributes and their associated values (if any) in the <name>Category: IDENTICAL</name>
IDENTICAL category MUST be repeated across all the <t>The attributes and their associated values (if any) in the
IDENTICAL category <bcp14>MUST</bcp14> be repeated across all the
media descriptions under multiplexing.</t> media descriptions under multiplexing.</t>
<t>&nbsp;</t>
<t>Attributes such as rtcp-mux fall into this category. Since <t>Attributes such as rtcp-mux fall into this category. Since
RTCP reporting is done per RTP session, RTCP Multiplexing RTCP reporting is done per RTP session, RTCP multiplexing
MUST be enabled for both the audio and video "m=" lines if <bcp14>MUST</bcp14> be enabled for both the audio and video "m=" lines
if
they are transported over a single 5-tuple.</t> they are transported over a single 5-tuple.</t>
<figure>
<artwork align="left" alt="" height="" name="" type="" width="" <sourcecode type="sdp">
xml:space="preserve"><![CDATA[
v=0 v=0
o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com
s= s=
c=IN IP4 client.biloxi.example.com c=IN IP4 client.biloxi.example.com
t=0 0 t=0 0
m=audio 34567 RTP/AVP 97 m=audio 34567 RTP/AVP 97
a=rtcp-mux a=rtcp-mux
m=video 34567 RTP/AVP 31 m=video 34567 RTP/AVP 31
a=rtpmap:31 H261/90000 a=rtpmap:31 H261/90000
a=rtcp-mux a=rtcp-mux
]]></artwork> </sourcecode>
</figure>
<t>&nbsp;</t> <t>Note: Even though IDENTICAL attributes must be repeated across all me
<t>Note: Eventhough IDENTICAL attributes must be repeated across all medi dia
a
descriptions under multiplexing, they might not always be explicitly enco ded across descriptions under multiplexing, they might not always be explicitly enco ded across
all media descriptions. <xref target="I-D.ietf-mmusic-sdp-bundle-negotiat ion"/> all media descriptions. <xref target="RFC8843" format="default"/>
defines rules for when attributes and their values are implicitly applied to media defines rules for when attributes and their values are implicitly applied to media
description.</t> description.</t>
</section> </section>
<section title="Category: SUM"> <section numbered="true" toc="default">
<name>Category: SUM</name>
<t>The attributes in the SUM category can be set as they are <t>The attributes in the SUM category can be set as they are
normally used but software using them in the multiplexing scenario normally used, but software using them in the multiplexing scenario
MUST apply the sum of all the attributes being multiplexed instead of <bcp14>MUST</bcp14> apply the sum of all the attributes being multiplex
ed instead of
trying to use them independently. This is typically used for trying to use them independently. This is typically used for
bandwidth or other rate limiting attributes to the bandwidth or other rate-limiting attributes to the
underlying transport.</t> underlying transport.</t>
<t>&nbsp;</t>
<t> <t>
The software parsing the SDP sample below, should use the The software parsing the SDP sample below should use the
aggregate Application Specific (AS) bandwidth value from the aggregate Application Specific (AS) bandwidth value from the
individual media descriptions to determine the AS value for individual media descriptions to determine the AS value for
the multiplexed session. Thus the calculated AS value would the multiplexed session. Thus the calculated AS value would
be 256+64 kilobits per second for the given example. be 256+64 kilobits per second for the given example.
</t> </t>
<figure>
<artwork align="left" alt="" height="" name="" type="" width="" <sourcecode type="sdp">
xml:space="preserve"><![CDATA[
v=0 v=0
o=test 2890844526 2890842807 IN IP4 client.biloxi.example.com o=test 2890844526 2890842807 IN IP4 client.biloxi.example.com
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
]]></artwork> </sourcecode>
</figure>
<t>&nbsp;</t>
</section> </section>
<section title="Category: TRANSPORT"> <section numbered="true" toc="default">
<t> The attributes in the TRANSPORT category can be set normally <name>Category: TRANSPORT</name>
for multiple items in a multiplexed group but the software MUST <t>The attributes in the TRANSPORT category can be set normally
for multiple items in a multiplexed group, but the software <bcp14>MUST
</bcp14>
pick the one that's associated with the "m=" line whose information is pick the one that's associated with the "m=" line whose information is
used for setting up the underlying transport.</t> used for setting up the underlying transport.</t>
<t>&nbsp;</t>
<t>In the example below, "a=crypto" attribute is defined for both <t>In the example below, the "a=crypto" attribute is defined for both
the audio and the video "m=" lines. The video media line's a=crypto the audio and video "m=" lines. The video media line's a=crypto
attribute is chosen since its mid value (bar) appears first in attribute is chosen since its mid value (bar) appears first in
the a=group:BUNDLE line. This is due to BUNDLE grouping semantic the a=group:BUNDLE line. This is due to the BUNDLE grouping semantic
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref> <xref target="RFC8843" format="default"/>, which mandates that the valu
which mandates the values from "m=" line corresponding to the mid es from
appearing first on the a=group:BUNDLE line to be considered for the "m=" line corresponding to the mid
setting up the RTP Transport.</t> appearing first on the a=group:BUNDLE line be considered for
<figure> setting up the RTP transport.</t>
<artwork align="left" alt="" height="" name="" type="" width=""
xml:space="preserve"><![CDATA[
<sourcecode type="sdp">
v=0 v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s= s=
c=IN IP4 host.atlanta.example.com c=IN IP4 host.atlanta.example.com
t=0 0 t=0 0
a=group:BUNDLE bar foo a=group:BUNDLE bar foo
m=audio 49172 RTP/AVP 99 m=audio 49172 RTP/AVP 99
a=mid:foo a=mid:foo
a=crypto:1 AES_CM_128_HMAC_SHA1_80 a=crypto:1 AES_CM_128_HMAC_SHA1_80
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
]]></artwork> </sourcecode>
</figure>
<t>&nbsp;</t> </section>
</section> <section numbered="true" toc="default">
<section title="Category: INHERIT"> <name>Category: INHERIT</name>
<t>The attributes in the INHERIT category encapsulate other SDP <t>The attributes in the INHERIT category encapsulate other SDP
attributes or parameters. These attributes inherit their multiplexing attributes or parameters. These attributes inherit their multiplexing
characteristics from the attributes or parameters they encapsulate. characteristics from the attributes or parameters they encapsulate.
Such attributes are defined in <xref target="RFC3407"/>, Such attributes are defined in <xref target="RFC3407" format="default"/>
<xref target="RFC5939"/> and <xref target="RFC6871"/> as part of a ,
generic framework for indicating and negotiating transport, media, and <xref target="RFC5939" format="default"/>, and <xref target="RFC6871"
media format related capabilities in the SDP. </t> format="default"/> as part of a
<t>The inheritance manifests itself when the encapsulated attribute or generic framework for indicating and negotiating capabilities in the
SDP related to transport, media, and media format. </t>
<t>The inheritance manifests itself when the encapsulated attribute or
parameter is being leveraged. In the case of SDP Capability Negotiation parameter is being leveraged. In the case of SDP Capability Negotiation
<xref target="RFC5939"/> for example, this occurs when a capability <xref target="RFC5939" format="default"/>, for example, this occurs when a capability
(encapsulating attribute) is used as part of a configuration; the (encapsulating attribute) is used as part of a configuration; the
configuration inherits the multiplexing category of each of its configuration inherits the multiplexing category of each of its
constituent (encapsulated) attributes and parameters. The inherited constituent (encapsulated) attributes and parameters. The inherited
attributes MUST be coherent in order to form a valid configuration from a attributes <bcp14>MUST</bcp14> be coherent in order to form a valid confi
multiplexing point of view (see <xref target="sec-encap"/> for guration from a
multiplexing point of view (see <xref target="sec-encap" format="default"
/> for
further details).</t> further details).</t>
<t>&nbsp;</t>
<figure> <sourcecode type="sdp">
<artwork align="left" alt="" height="" name="" type="" width=""
xml:space="preserve"><![CDATA[
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
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</sourcecode>
]]></artwork>
</figure> <t>In this example, the category IDENTICAL is inherited by
<t>In the above example, the category IDENTICAL is inherited by the cpar-encapsulated "rtcp-mux" attribute.</t>
the cpar encapsulated rtcp-mux attribute.</t>
<t>&nbsp;</t>
</section> </section>
<section title="Category: IDENTICAL-PER-PT"> <section numbered="true" toc="default">
<t> The attributes in the IDENTICAL-PER-PT category define <name>Category: IDENTICAL-PER-PT</name>
the RTP payload configuration on per Payload Type basis and <t>The attributes in the IDENTICAL-PER-PT category define
MUST have identical values across all the media descriptions the RTP payload configuration on the basis of the payload type, and the
for a given RTP Payload Type when repeated. These Payload Types y
identify the same codec configuration as defined in the Section <bcp14>MUST</bcp14> have identical values across all the media descript
10.1.2 of <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/> ions
for a given RTP payload type when repeated.
These payload types
identify the same codec configuration as defined in <xref target="RFC88
43"
sectionFormat="of" section="9.1"/>
under this context.</t> under this context.</t>
<t>&nbsp;</t>
<t>In the SDP example below, Payload Types 96 and 97 are repeated <t>In the SDP example below, Payload Types 96 and 97 are repeated
across all the video "m=" lines and all the payload specific across all the video "m=" lines, and all the payload-specific
parameters (ex: rtpmap, fmtp) are identical parameters (for example, rtpmap and fmtp) are identical.
(Note: some line breaks included are due to formatting only).</t> (Note: some line breaks are due to formatting only.)</t>
<figure>
<artwork align="left" alt="" height="" name="" type="" width=""
xml:space="preserve"><![CDATA[
<sourcecode type="sdp">
v=0 v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s= s=
c=IN IP4 host.atlanta.example.com c=IN IP4 host.atlanta.example.com
t=0 0 t=0 0
a=group:BUNDLE cam1 cam2 a=group:BUNDLE cam1 cam2
m=video 96 97 m=video 96 97
a=mid:cam1 a=mid:cam1
a=rtpmap:96 H264/90000 a=rtpmap:96 H264/90000
a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000; a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000;
skipping to change at line 462 skipping to change at line 377
a=rtpmap:97 H264/90000 a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000; a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000;
max-mbps=7200; max-br=200 max-mbps=7200; max-br=200
m=video 96 97 m=video 96 97
a=mid:cam2 a=mid:cam2
a=rtpmap:96 H264/90000 a=rtpmap:96 H264/90000
a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000; a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000;
max-mbps=108000; max-br=1000 max-mbps=108000; max-br=1000
a=rtpmap:97 H264/90000 a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000; a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000;
max-mbps=7200; max-br=200 max-mbps=7200; max-br=200</sourcecode>
]]></artwork>
</figure> </section>
<t>&nbsp;</t> <section numbered="true" toc="default">
</section> <name>Category: SPECIAL</name>
<section title="Category: SPECIAL"> <t>For the attributes in the SPECIAL category, the text in the
<t>For the attributes in the SPECIAL category, the text in the specification defining the attribute <bcp14>MUST</bcp14> be consulted for
specification defining the attribute MUST be consulted for further further
handling when multiplexed. </t> handling when multiplexed. </t>
<t>As an exampe, for the attribute extmap <xref target="RFC5285"/>, <t>As an example, for the attribute "extmap" <xref target="RFC5285" form
the specification defining the extension needs to be referred to at="default"/>,
the specification defining the extension needs to be consulted to
understand the multiplexing implications.</t> understand the multiplexing implications.</t>
</section>
<section numbered="true" toc="default">
<name>Category: TBD</name>
<t>The attributes in the TBD category have not been analyzed under the
proposed multiplexing framework and <bcp14>SHOULD NOT</bcp14> be multiple
xed.</t>
</section>
</section> </section>
<section title="Category: TBD"> <section anchor="sec-cur-analysis" numbered="true" toc="default">
<t>The attributes in the TBD category have not been analyzed under the <name>Analysis of Existing Attributes</name>
proposed multiplexing framework and SHOULD NOT be multiplexed.</t> <t>This section analyzes attributes listed in <xref target="IANA" format="
</section> default"/>, grouped under the IETF document that
</section>
<section title="Analysis of Existing Attributes" anchor="sec-cur-analysis" >
<t>This section analyzes attributes listed in <xref
target="IANA"/>, grouped under the IETF document that
defines them.</t> defines them.</t>
<t>The "Level" column indicates whether the attribute <t>The "Level" column indicates whether the attribute
is currently specified as:</t> is currently specified as:</t>
<t> <ul spacing="normal">
<list style="symbols"> <li>S -- Session level</li>
<t>S -- Session level</t> <li>M -- Media level</li>
<t>M -- Media level</t> <li>B -- Both (Implies either a session level or a media level attribute
<t>B -- Both (Implies either a session level or a media level attribut )</li>
e)</t> <li>SR -- Source-level (for a single SSRC) <xref target="RFC5576" format
<t>SR -- Source-level (for a single SSRC) <xref target="RFC5576"/></t> ="default"/></li>
</list> </ul>
</t> <t>The "Mux Category" column identifies the multiplexing category
<t>The "Mux Category" column identifies multiplexing category assigned assigned to each attribute, and the "Notes" column captures additional
per attribute and the "Notes" column captures additional
informative details regarding the assigned category, wherever informative details regarding the assigned category, wherever
necessary.</t> necessary.</t>
<section title="RFC4566: SDP">
<t><xref target="RFC4566"/> defines SDP that is intended for describing <section numbered="true" toc="default">
<name>RFC 4566: SDP</name>
<t><xref target="RFC4566" format="default"/> defines SDP that is intende
d for describing
multimedia sessions for the purposes of session announcement, multimedia sessions for the purposes of session announcement,
session invitation, and other forms of multimedia session session invitation, and other forms of multimedia session
initiation.</t> initiation.</t>
<table align="center">
<name>RFC 4566 Attribute Analysis</name>
<thead>
<tr>
<th align="left">Name</th>
<th align="left">Notes</th>
<th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">sendrecv</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">sendonly</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">recvonly</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">inactive</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">cat</td>
<td align="left">Not impacted</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">ptime</td>
<td align="left"> The attribute value <bcp14>MUST</bcp14> be the s
ame
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
<tr>
<td align="left">maxptime</td>
<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
<tr>
<td align="left">orient</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">framerate</td>
<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
<tr>
<td align="left">quality</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">rtpmap</td>
<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
<tr>
<td align="left">fmtp</td>
<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
<tr>
<td align="left">keywds</td>
<td align="left">Not impacted</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">type</td>
<td align="left">Not impacted
</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">type:broadcast</td>
<td align="left">Not impacted
</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">type:H332</td>
<td align="left">Not impacted
</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">type:meeting</td>
<td align="left">Not impacted
</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">type:moderated</td>
<td align="left">Not impacted
</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">type:test</td>
<td align="left">Not impacted
</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">tool</td>
<td align="left">Not impacted
</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">charset</td>
<td align="left">Not impacted
</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">sdplang</td>
<td align="left">Not impacted
</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">lang</td>
<td align="left">Not impacted
</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section>
<texttable title="5.1 RFC4566 Attribute Analysis"> <section numbered="true" toc="default">
<ttcol align='left'>Name</ttcol> <name>RFC 4585: RTP/AVPF</name>
<ttcol align='left'>Notes</ttcol> <t><xref target="RFC4585" format="default"/> defines an extension to
<ttcol align='left'>Level</ttcol>
<ttcol align='left'>Mux Category</ttcol>
<c>sendrecv&nbsp;</c><c>Not impacted&nbsp;</c><c>B&nbsp;</c>
<c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>sendonly&nbsp;</c><c>Not impacted&nbsp;</c><c>B&nbsp;</c>
<c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>recvonly&nbsp;</c><c>Not impacted&nbsp;</c><c>B&nbsp;</c>
<c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>inactive&nbsp;</c><c>Not impacted&nbsp;</c><c>B&nbsp;</c>
<c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>cat&nbsp;</c><c>Not impacted&nbsp;</c><c>S&nbsp;</c>
<c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>ptime&nbsp;</c><c> The attribute value MUST be same
for a given codec configuration&nbsp;</c>
<c>M&nbsp;</c><c>IDENTICAL-PER-PT</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>maxptime&nbsp;</c><c>The attribute value MUST be same
for a given codec configuration&nbsp;</c>
<c>M&nbsp;</c><c>IDENTICAL-PER-PT</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>orient&nbsp;</c><c>Not Impacted
&nbsp;</c><c>M&nbsp;</c><c>NORMAL</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>framerate&nbsp;</c><c>The attribute value MUST be same
for a given codec configuration&nbsp;</c><c>M&nbsp;</c>
<c>IDENTICAL-PER-PT&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>quality&nbsp;</c><c>Not Impacted
&nbsp;</c><c>M&nbsp;</c><c>NORMAL</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>rtpmap&nbsp;</c><c>The attribute value MUST be same
for a given codec configuration&nbsp;</c><c>M&nbsp;</c>
<c>IDENTICAL-PER-PT</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>fmtp&nbsp;</c><c>The attribute value MUST be same
for a given codec configuration&nbsp;</c><c>M&nbsp;</c>
<c>IDENTICAL-PER-PT</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>keywds&nbsp;</c><c>Not impacted&nbsp;</c><c>S&nbsp;</c>
<c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>type&nbsp;</c><c>Not Impacted
&nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>type:broadcast&nbsp;</c><c>Not Impacted
&nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>type:H332&nbsp;</c><c>Not Impacted
&nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>type:meeting&nbsp;</c><c>Not Impacted
&nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>type:moderated&nbsp;</c><c>Not Impacted
&nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>type:test&nbsp;</c><c>Not Impacted
&nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>tool&nbsp;</c><c>Not Impacted
&nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>charset&nbsp;</c><c>Not Impacted
&nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>sdplang&nbsp;</c><c>Not Impacted
&nbsp;</c><c>B&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>lang&nbsp;</c><c>Not Impacted
&nbsp;</c><c>B&nbsp;</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
</texttable>
</section>
<section title="RFC4585: RTP/AVPF">
<t><xref target="RFC4585"/> defines an extension to
the Audio-visual Profile (AVP) that enables receivers to the Audio-visual Profile (AVP) that enables receivers to
provide, statistically, more immediate feedback to the senders provide, statistically, more immediate feedback to the senders
and thus allows for short-term adaptation and efficient and thus allows for short-term adaptation and efficient
feedback-based repair mechanisms to be implemented.</t> feedback-based repair mechanisms to be implemented.</t>
<table align="center">
<texttable title="5.2 RFC4585 Attribute Analysis"> <name>RFC 4585 Attribute Analysis</name>
<ttcol align='left'>Name</ttcol> <thead>
<ttcol align='left'>Notes</ttcol> <tr>
<ttcol align='left'>Level</ttcol> <th align="left">Name</th>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Notes</th>
<c>rtcp-fb&nbsp;</c><c>Since RTCP feedback attributes are Payload Type <th align="left">Level</th>
(PT) scoped, their values MUST be identical for a given PT across <th align="left">Mux Category</th>
the multiplexed "m=" lines.</c><c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
</section> <td align="left">rtcp-fb</td>
<td align="left">Since RTCP feedback attributes are scoped by payl
<section title="RFC5761: Multiplexing RTP and RTCP"> oad type
<t><xref target="RFC5761"/> discusses issues that (PT), their values <bcp14>MUST</bcp14> be identical for a given PT acros
s
the multiplexed "m=" lines.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
</tbody>
</table>
</section>
<section numbered="true" toc="default">
<name>RFC 5761: Multiplexing RTP and RTCP</name>
<t><xref target="RFC5761" format="default"/> discusses issues that
arise when multiplexing RTP data packets and RTP Control arise when multiplexing RTP data packets and RTP Control
Protocol (RTCP) packets on a single UDP port. It describes Protocol (RTCP) packets on a single UDP port. It describes
when such multiplexing is and is not appropriate, and it when such multiplexing is and is not appropriate, and it
explains how the SDP can be used to signal multiplexed sessions.</t> explains how the SDP can be used to signal multiplexed sessions.</t>
<texttable title="5.3 RFC5761 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5761 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>rtcp-mux&nbsp;</c><c>RTP and RTCP Multiplexing affects the <th align="left">Level</th>
entire RTP session&nbsp;</c> <th align="left">Mux Category</th>
<c>M&nbsp;</c><c>IDENTICAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
<td align="left">rtcp-mux</td>
<td align="left">RTP and RTCP multiplexing affects the
entire RTP session.</td>
<td align="left">M</td>
<td align="left">IDENTICAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC3312: Integration of Resource Management and SIP"> <name>RFC 3312: Integration of Resource Management and SIP</name>
<t><xref target="RFC3312"/> defines a generic framework for <t><xref target="RFC3312" format="default"/> defines a generic framewor
k for
preconditions, which are extensible through IANA registration. preconditions, which are extensible through IANA registration.
This document also discusses how network quality of service can be This document also discusses how network quality of service can be
made a precondition for establishment of sessions initiated by the made a precondition for establishment of sessions initiated by the
Session Initiation Protocol (SIP). These preconditions require that Session Initiation Protocol (SIP). These preconditions require that
the participant reserve network resources before continuing with the the participant reserve network resources before continuing with the
session.</t> session.</t>
<texttable title="5.4 RFC3312 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 3312 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>des&nbsp;</c><c>Refer to notes below&nbsp;</c> <th align="left">Level</th>
<c>M&nbsp;</c><c>CAUTION&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>conf&nbsp;</c><c>Refer to notes below&nbsp;</c> <tbody>
<c>M&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">des</td>
<td align="left">Refer to notes below</td>
<c>curr&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
</texttable> <td align="left">conf</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">curr</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
</tbody>
</table>
<t>NOTE: A mismatched set of preconditions across media descriptions <t>NOTE: A mismatched set of preconditions across media descriptions
results in Session establishment failures due to inability results in session establishment failures due to inability
to meet right resource reservations requested.</t> to meet the requested resource reservations.</t>
</section> </section>
<section numbered="true" toc="default">
<name>RFC 4574: SDP "label" Attribute</name>
<section title="RFC4574: SDP Label Attribute "> <t><xref target="RFC4574" format="default"/> defines a new SDP media-lev
<t><xref target="RFC4574"/> defines a new SDP media-level el
attribute: "label". The "label" attribute carries a pointer to attribute: "label". The "label" attribute carries a pointer to
a media stream in the context of an arbitrary network application a media stream in the context of an arbitrary network application
that uses SDP. The sender of the SDP document can attach the "label" that uses SDP. The sender of the SDP document can attach the "label"
attribute to a particular media stream or streams. The attribute to a particular media stream or streams. The
application can then use the provided pointer to refer to application can then use the provided pointer to refer to
each particular media stream in its context.</t> each particular media stream in its context.</t>
<texttable title="5.5 RFC4574 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4574 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>label&nbsp;</c><c>Not Impacted&nbsp;</c><c>M</c><c>NORMAL&nbsp;</c> <th align="left">Level</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <th align="left">Mux Category</th>
</tr>
</texttable> </thead>
<tbody>
<tr>
<td align="left">label</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC5432: QOS Mechanism Selection in SDP"> <name>RFC 5432: QoS Mechanism Selection in SDP</name>
<t><xref target="RFC5432"/> defines procedures to <t><xref target="RFC5432" format="default"/> defines procedures for
negotiate QOS mechanisms using the SDP offer/answer model.</t> negotiating QoS mechanisms using the SDP offer/answer model.</t>
<texttable title="5.6 RFC5432 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5432 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>qos-mech-send&nbsp;</c> <th align="left">Level</th>
<c> Refer to <xref target="SecqostokenAnalysis"/> &nbsp;</c> <th align="left">Mux Category</th>
<c>B</c><c>TRANSPORT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>qos-mech-recv&nbsp;</c> <tr>
<c>Refer to <xref target="SecqostokenAnalysis"/> &nbsp;</c> <td align="left">qos-mech-send</td>
<c>B</c><c>TRANSPORT&nbsp;</c> <td align="left"> Refer to <xref target="SecqostokenAnalysis" form
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> at="default"/>.</td>
<td align="left">B</td>
</texttable> <td align="left">TRANSPORT</td>
</tr>
<tr>
<td align="left">qos-mech-recv</td>
<td align="left">Refer to <xref target="SecqostokenAnalysis" forma
t="default"/>.</td>
<td align="left">B</td>
<td align="left">TRANSPORT</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC4568: SDP Security Descriptions"> <name>RFC 4568: SDP Security Descriptions</name>
<t><xref target="RFC4568"/> defines a SDP cryptographic <t><xref target="RFC4568" format="default"/> defines an SDP cryptographi
c
attribute for unicast media streams. The attribute describes a attribute for unicast media streams. The attribute describes a
cryptographic key and other parameters that serve to cryptographic key and other parameters that serve to
configure security for a unicast media stream in either a configure security for a unicast media stream in either a
single message or a roundtrip exchange.</t> single message or a roundtrip exchange.</t>
<texttable title="5.7 RFC4568 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4568 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>crypto&nbsp;</c><c>crypto attribute MUST be the one that correspond <th align="left">Level</th>
s <th align="left">Mux Category</th>
to the "m=" line chosen for setting up the underlying transport flow < </tr>
/c> </thead>
<c>M&nbsp;</c><c>TRANSPORT&nbsp;</c> <tbody>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">crypto</td>
</texttable> <td align="left">crypto attribute <bcp14>MUST</bcp14> be the one t
hat corresponds
to the "m=" line chosen for setting up the underlying transport
flow. </td>
<td align="left">M</td>
<td align="left">TRANSPORT</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC5762: RTP over DCCP"> <name>RFC 5762: RTP over DCCP</name>
<t>RTP is a widely used transport for real-time multimedia <t>RTP is a widely used transport for real-time multimedia
on IP networks. DCCP is a transport protocol that provides desirable on IP networks. DCCP is a transport protocol that provides desirable
services for real-time applications. <xref target="RFC5762"/> services for real-time applications. <xref target="RFC5762" format="defa ult"/>
specifies a mapping of RTP onto DCCP, along with associated specifies a mapping of RTP onto DCCP, along with associated
signaling, such that real-time applications can make use of signaling, such that real-time applications can make use of
the services provided by DCCP.</t> the services provided by DCCP.</t>
<texttable title="5.8 RFC5762 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5762 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Current</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>dccp-service-code&nbsp;</c><c> If RFC6773 is not being <th align="left">Current</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">dccp-service-code</td>
<td align="left"> If RFC 6773 is not being
used in addition to RFC5762, the port in the "m=" line is a used in addition to RFC5762, the port in the "m=" line is a
DCCP port. DCCP being a connection oriented protocol does DCCP port. Being a connection-oriented protocol, DCCP does
not allow multiple connections on the same not allow multiple connections on the same
5-tuple&nbsp;</c> <c>M&nbsp;</c><c>CAUTION&nbsp;</c><c>&nbsp;</c> 5-tuple.</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">CAUTION</td>
</texttable> </tr>
</tbody>
</table>
<t> <t>
NOTE: If RFC6773 is being used in addition to RFC5762 and provided NOTE: If RFC 6773 is being used in addition to RFC 5762, and the
that DCCP-in-UDP layer has additional demultiplexing, then it DCCP-in-UDP layer has additional demultiplexing, then it
can be possible to use different DCCP service codes for each may be possible to use different DCCP service codes for each
DCCP flow, given each uses a different DCCP port. Although DCCP flow, given each uses a different DCCP port. However,
doing so might conflict with the media type of the "m=" doing so might conflict with the media type of the "m="
line. None of this is standardized yet and it wouldn't work line. None of this is standardized yet, and it wouldn't work
as explained. Hence performing multiplexing is not recommended as explained. Hence performing multiplexing is not recommended
even in this alternate scenario.</t> even in this alternate scenario.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6773: DCCP-UDP Encapsulation"> <name>RFC 6773: DCCP-UDP Encapsulation</name>
<t><xref target="RFC6773"/> specifies an <t><xref target="RFC6773" format="default"/> specifies an
alternative encapsulation of DCCP, referred to as DCCP-UDP. This alternative encapsulation of DCCP, referred to as DCCP-UDP. This
encapsulation allows DCCP to be carried through the current encapsulation allows DCCP to be carried through the current
generation of Network Address Translation (NAT) middle boxes generation of Network Address Translation (NAT) middleboxes
without modification of those middle boxes.</t> without modification of those middleboxes.</t>
<texttable title="5.9 RFC6773 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6773 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>dccp-port&nbsp;</c><c> Multiplexing is not recommended <th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">dccp-port</td>
<td align="left"> Multiplexing is not recommended
due to potential conflict between the port used for DCCP due to potential conflict between the port used for DCCP
en/decapsulation and the RTP&nbsp;</c> <c>M&nbsp;</c> encapsulation/decapsulation and the RTP.</td>
<c>CAUTION&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">CAUTION</td>
</tr>
</tbody>
</table>
</texttable>
<t> <t>
NOTE: RFC6773 is about tunneling DCCP in UDP, with the UDP NOTE: RFC 6773 allows DCCP-UDP encapsulation, with the UDP port
port being the port of the DCCP en-/de-capsulation being the port of the DCCP encapsulation/decapsulation service.
service. This encapsulation allows arbitrary DCCP packets to This encapsulation allows arbitrary DCCP packets to be encapsulated,
be encapsulated and the DCCP port chosen can conflict with and the DCCP port chosen can conflict with
the port chosen for the RTP traffic. For multiplexing several the port chosen for the RTP traffic.
DCCP-in-UDP encapsulations on the same UDP port with no RTP
traffic on the same port implies collapsing several DCCP port Multiplexing several DCCP-in-UDP encapsulations on the same UDP port
spaces together. This can or cannot work depending on the with no RTP traffic on the same port implies collapsing several DCCP
nature of DCCP encapsulation and ports choices thus rendering port spaces together. Whether or not this works depends on the nature
it to be very application dependent. of DCCP encapsulation and ports choices; it is thus very application
dependent.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC5506: Reduced-Size RTCP in RTP Profile"> <name>RFC 5506: Reduced-Size RTCP in RTP Profile</name>
<t><xref target="RFC5506"/> discusses benefits and <t><xref target="RFC5506" format="default"/> discusses benefits and
issues that arise when allowing RTCP packets to be transmitted with issues that arise when allowing RTCP packets to be transmitted with
reduced size.</t> reduced size.</t>
<texttable title="5.10 RFC5506 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5506 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>rtcp-rsize&nbsp;</c><c>Reduced size RTCP affects the <th align="left">Level</th>
entire RTP session&nbsp;</c> <th align="left">Mux Category</th>
<c>M&nbsp;</c><c>IDENTICAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
<td align="left">rtcp-rsize</td>
<td align="left">Reduced-size RTCP affects the
entire RTP session.</td>
<td align="left">M</td>
<td align="left">IDENTICAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6787: Media Resource Control Protocol Version 2"> <name>RFC 6787: Media Resource Control Protocol Version 2</name>
<t>The Media Resource Control Protocol Version 2 (MRCPv2) <t>The Media Resource Control Protocol Version 2 (MRCPv2)
allows client hosts to control media service resources such allows client hosts to control media service resources such
as speech synthesizers, recognizers, verifiers, and as speech synthesizers, recognizers, verifiers, and
identifiers residing in servers on the network. MRCPv2 is identifiers residing in servers on the network. MRCPv2 is
not a "stand-alone" protocol -- it relies on other not a "stand-alone" protocol; it relies on other
protocols, such as the SIP, to coordinate MRCPv2 clients and protocols, such as the SIP, to coordinate MRCPv2 clients and
servers, and manage session between them, and SDP to servers and manage session between them, and SDP to
describe, discover, and exchange capabilities. It also describe, discover, and exchange capabilities. It also
depends on SIP and SDP to establish the media sessions and depends on SIP and SDP to establish the media sessions and
associated parameters between the media source or sink and associated parameters between the media source or sink and
the media server. Once this is done, the MRCPv2 exchange the media server. Once this is done, the MRCPv2 exchange
operates over the control session established above, operates over the control session established above,
allowing the client to control the media processing allowing the client to control the media-processing
resources on the speech resource server. <xref resources on the speech resource server. <xref target="RFC6787" format="
target="RFC6787"/> defines attributes for this default"/> defines attributes for this
purpose.</t> purpose.</t>
<texttable title="5.11 RFC6787 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6787 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>resource&nbsp;</c><c>Not Impacted&nbsp;</c><c>M&nbsp;</c> <th align="left">Level</th>
<c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>channel&nbsp;</c><c>Not Impacted&nbsp;</c><c>M&nbsp;</c> <tbody>
<c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">resource</td>
<td align="left">Not impacted</td>
<c>cmid&nbsp;</c><c>Not Impacted&nbsp;</c><c>M&nbsp;</c> <td align="left">M</td>
<c>NORMAL&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
</texttable> <td align="left">channel</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">cmid</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC5245: ICE"> <name>RFC 8445: ICE</name>
<t><xref target="RFC5245"/> describes a protocol <t><xref target="RFC8445" format="default"/> describes a protocol
for NAT traversal for UDP-based multimedia sessions for NAT traversal for UDP-based multimedia sessions
established with the offer/answer model. established with the offer/answer model.
ICE makes use of the Session Traversal Utilities for NAT ICE makes use of the Session Traversal Utilities for NAT
(STUN) protocol and its extension, Traversal Using Relay NAT (TURN). (STUN) protocol and its extension, Traversal Using Relay NAT (TURN).
ICE can be used by any protocol utilizing the offer/answer model, such a s ICE can be used by any protocol utilizing the offer/answer model, such a s
the SIP.</t> the SIP.</t>
<texttable title="5.12 RFC5245 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 8445 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ice-lite&nbsp;</c><c>Not Impacted&nbsp;</c> <th align="left">Level</th>
<c>S</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>ice-options&nbsp;</c><c>Not Impacted&nbsp;</c> <tbody>
<c>S</c><c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">ice-lite</td>
<td align="left">Not impacted</td>
<c>ice-mismatch&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">S</td>
<c>S</c><c>NORMAL&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>ice-pwd&nbsp;</c><c>ice-pwd MUST be the one that <td align="left">ice-options</td>
<td align="left">Not impacted</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">ice-mismatch</td>
<td align="left">Not impacted</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">ice-pwd</td>
<td align="left">ice-pwd <bcp14>MUST</bcp14> be the one that
corresponds to the "m=" line chosen for setting up the corresponds to the "m=" line chosen for setting up the
underlying transport flow&nbsp;</c> underlying transport flow.</td>
<c>B</c><c>TRANSPORT&nbsp;</c> <td align="left">B</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
<c>ice-ufrag&nbsp;</c><c>ice-ufrag MUST be the one that <tr>
<td align="left">ice-ufrag</td>
<td align="left">ice-ufrag <bcp14>MUST</bcp14> be the one that
corresponds to the "m=" line chosen for setting up the corresponds to the "m=" line chosen for setting up the
underlying transport flow&nbsp;</c> underlying transport flow.</td>
<c>B</c><c>TRANSPORT&nbsp;</c> <td align="left">B</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
<c>candidate&nbsp;</c><c>ice candidate MUST be the one that <tr>
<td align="left">candidate</td>
<td align="left">ice candidate <bcp14>MUST</bcp14> be the one that
corresponds to the "m=" line chosen for setting up the corresponds to the "m=" line chosen for setting up the
underlying transport underlying transport flow.</td>
flow&nbsp;</c><c>M</c><c>TRANSPORT&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
<c>remote-candidates&nbsp;</c><c>ice remote candidate MUST <tr>
<td align="left">remote-candidates</td>
<td align="left">ice remote candidate <bcp14>MUST</bcp14>
be the one that corresponds to the "m=" line chosen for setting be the one that corresponds to the "m=" line chosen for setting
up the underlying transport up the underlying transport flow.</td>
flow&nbsp;</c><c>M</c><c>TRANSPORT&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
</texttable> <tr>
<td align="left">ice2</td>
<td align="left">Not impacted</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section title="RFC5285: RTP Header Extensions"> <section numbered="true" toc="default">
<t><xref target="RFC5285"/> provides a general <name>RFC 5285: RTP Header Extensions</name>
mechanism to use the header extension feature of RTP. <t><xref target="RFC5285" format="default"/> provides a general
mechanism for using the header-extension feature of RTP. (Note: <xref
target="RFC5285"/> has been obsoleted by <xref target="RFC8285"/>.)
It provides the option to use a small number of small extensions It provides the option to use a small number of small extensions
in each RTP packet, where the universe of possible extensions is in each RTP packet, where the universe of possible extensions is
large and registration is de-centralized. The actual extensions in large and registration is decentralized. The actual extensions in
use in a session are signaled in the setup information for use in a session are signaled in the setup information for
that session.</t> that session.</t>
<texttable title="5.13 RFC5285 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5285 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>extmap&nbsp;</c><c>Refer to the document defining the <th align="left">Level</th>
specific RTP Extension&nbsp;</c> <c>B</c><c>SPECIAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
</texttable> <tbody>
<tr>
<td align="left">extmap</td>
<td align="left">Refer to the document defining the
specific RTP extension.</td>
<td align="left">B</td>
<td align="left">SPECIAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC3605: RTCP attribute in SDP "> <name>RFC 3605: RTCP Attribute in SDP</name>
<t>Originally, SDP assumed that RTP and RTCP were carried on <t>Originally, SDP assumed that RTP and RTCP were carried on
consecutive ports. However, this is not always true when consecutive ports. However, this is not always true when
NATs are involved. <xref target="RFC3605"/> specifies an NATs are involved. <xref target="RFC3605" format="default"/> specifie
early mechanism to indicate the RTCP port.</t> s an
<texttable title="5.14 RFC3605 Attribute Analysis"> early mechanism for indicating the RTCP port.</t>
<ttcol align='left'>Name</ttcol> <table align="center">
<ttcol align='left'>Notes</ttcol> <name>RFC 3605 Attribute Analysis</name>
<ttcol align='left'>Level</ttcol> <thead>
<ttcol align='left'>Mux Category</ttcol> <tr>
<th align="left">Name</th>
<c>rtcp&nbsp;</c><c>RTCP Port MUST be the one <th align="left">Notes</th>
<th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">rtcp</td>
<td align="left">RTCP port <bcp14>MUST</bcp14> be the one
that corresponds to the "m=" line chosen for that corresponds to the "m=" line chosen for
setting up the underlying transport flow.&nbsp;</c> setting up the underlying transport flow.</td>
<c>M</c><c>TRANSPORT&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
</texttable> </tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC5576: Source-Specific SDP Attributes"> <name>RFC 5576: Source-Specific SDP Attributes</name>
<t><xref target="RFC5576"/> defines a mechanism to <t><xref target="RFC5576" format="default"/> defines a mechanism for des
describe RTP media sources, which are identified by their cribing RTP
synchronization source (SSRC) identifiers, in SDP, to media sources -- which are identified by their
associate attributes with these sources, and to express synchronization source (SSRC) identifiers -- in SDP, to
associate attributes with these sources and express
relationships among sources. It also defines several relationships among sources. It also defines several
source-level attributes that can be used to describe source-level attributes that can be used to describe
properties of media sources.</t> properties of media sources.</t>
<texttable title="5.15 RFC5576 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5576 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ssrc&nbsp;</c><c>Refer to Notes <th align="left">Level</th>
below&nbsp;</c><c>M</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>ssrc-group&nbsp;</c> <tbody>
<c>Refer to <xref target="sec-ssrc-group"></xref> <tr>
for specific analysis of the grouping semantics&nbsp;</c><c>M</c> <td align="left">ssrc</td>
<c>NORMAL&nbsp;</c> <td align="left">Refer to notes
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> below.</td>
<td align="left">M</td>
<c>cname&nbsp;</c> <c>Not Impacted&nbsp;</c><c>SR</c> <td align="left">NORMAL</td>
<c>NORMAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">ssrc-group</td>
<c>previous-ssrc&nbsp;</c> <td align="left">Refer to <xref target="sec-ssrc-group" format="de
<c>Refer to notes below&nbsp;</c><c>SR</c><c>NORMAL&nbsp;</c> fault"/>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> for specific analysis of the grouping semantics.</td>
<td align="left">M</td>
<c>fmtp&nbsp;</c><c>The attribute value MUST be same for a <td align="left">NORMAL</td>
given codec configuration&nbsp;</c><c>SR</c> </tr>
<c>IDENTICAL-PER-PT&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">cname</td>
</texttable> <td align="left">Not impacted</td>
<td align="left">SR</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">previous-ssrc</td>
<td align="left">Refer to notes below</td>
<td align="left">SR</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">fmtp</td>
<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me for a
given codec configuration.</td>
<td align="left">SR</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
</tbody>
</table>
<t>NOTE: If SSRCs are repeated across "m=" lines being multiplexed, they <t>NOTE: If SSRCs are repeated across "m=" lines being multiplexed, they
MUST all represent the same underlying RTP Source.</t> <bcp14>MUST</bcp14> all represent the same underlying RTP Source.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC7273: RTP Clock Source Signalling"> <name>RFC 7273: RTP Clock Source Signaling</name>
<t><xref target="RFC7273"/> specifies <t><xref target="RFC7273" format="default"/> specifies
SDP signalling that identifies timestamp reference clock sources SDP signaling that identifies timestamp reference clock sources
and SDP signalling that identifies the media clock sources in a and SDP signaling that identifies the media clock sources in a
multimedia session.</t> multimedia session.</t>
<texttable title="5.16 RFC7273 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 7273 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ts-refclk&nbsp;</c><c>Not Impacted&nbsp;</c> <th align="left">Level</th>
<c>B</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>mediaclk&nbsp;</c> <tbody>
<c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">ts-refclk</td>
<td align="left">Not impacted</td>
<c>ts-refclk:ntp&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">B</td>
<c>B</c><c>NORMAL&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>ts-refclk:ptp&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">mediaclk</td>
<c>B</c><c>NORMAL&nbsp;</c> <td align="left">Not impacted</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">B</td>
<td align="left">NORMAL</td>
<c>ts-refclk:gps&nbsp;</c><c>Not Impacted&nbsp;</c> </tr>
<c>B</c><c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">ts-refclk:ntp</td>
<td align="left">Not impacted</td>
<c>ts-refclk:gal&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">B</td>
<c>B</c><c>NORMAL&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>ts-refclk:glonass&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">ts-refclk:ptp</td>
<c>B</c><c>NORMAL&nbsp;</c> <td align="left">Not impacted</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">B</td>
<td align="left">NORMAL</td>
<c>ts-refclk:local&nbsp;</c><c>Not Impacted&nbsp;</c> </tr>
<c>B</c><c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">ts-refclk:gps</td>
<td align="left">Not impacted</td>
<c>ts-refclk:private&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">B</td>
<c>B</c><c>NORMAL&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>mediaclk:sender&nbsp;</c> <td align="left">ts-refclk:gal</td>
<c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c> <td align="left">Not impacted</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">B</td>
<td align="left">NORMAL</td>
<c>mediaclk:direct&nbsp;</c> </tr>
<c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">ts-refclk:glonass</td>
<td align="left">Not impacted</td>
<c>mediaclk:IEEE1722&nbsp;</c> <td align="left">B</td>
<c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
</texttable> <td align="left">ts-refclk:local</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">ts-refclk:private</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">mediaclk:sender</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">mediaclk:direct</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">mediaclk:IEEE1722</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6236: Image Attributes in SDP"> <name>RFC 6236: Image Attributes in SDP</name>
<t><xref target="RFC6236"/> proposes a new generic <t><xref target="RFC6236" format="default"/> proposes a new generic
session setup attribute to make it possible to negotiate session setup attribute to make it possible to negotiate
different image attributes such as image size. A possible different image attributes, such as image size. A possible
use case is to make it possible for a low-end hand-held use case is to make it possible for a low-end handheld
terminal to display video without the need to rescale the terminal to display video without the need to rescale the
image, something that may consume large amounts of memory and image, something that may consume large amounts of memory and
processing power. The document also helps to maintain an processing power. The document also helps to maintain an
optimal bitrate for video as only the image size that is optimal bitrate for video as only the image size that is
desired by the receiver is transmitted.</t> desired by the receiver is transmitted.</t>
<texttable title="5.17 RFC6236 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6236 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>imageattr&nbsp;</c><c>The attribute value MUST be same <th align="left">Level</th>
for a given codec configuration&nbsp;</c><c>M&nbsp;</c> <th align="left">Mux Category</th>
<c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
<td align="left">imageattr</td>
<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC7197: Duplication Delay Attribute in SDP"> <name>RFC 7197: Duplication Delay Attribute in SDP</name>
<t><xref target="RFC7197"/> defines an attribute to <t><xref target="RFC7197" format="default"/> defines an attribute to
indicate the presence of temporally redundant media streams indicate the presence of temporally redundant media streams
and the duplication delay in SDP.</t> and the duplication delay in SDP.</t>
<texttable title="5.18 RFC7197 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 7197 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>duplication-delay&nbsp;</c><c>Not Impacted&nbsp;</c><c>B&nbsp;</c> <th align="left">Level</th>
<c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
</texttable> <tbody>
<tr>
<td align="left">duplication-delay</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC7266: RTCP XR Blocks for MOS Metric Reporting"> <name>RFC 7266: RTCP XR Blocks for MOS Metric Reporting</name>
<t><xref target="RFC7266"/> defines an RTCP Extended Report (XR) Block <t><xref target="RFC7266" format="default"/> defines an RTCP Extended Re
including two new segment types and associated SDP parameters that allow port (XR) Block
the reporting of mean opinion score (MOS) Metrics for use in a that includes two new segment types and associated SDP parameters that a
llow
the reporting of mean opinion score (MOS) metrics for use in a
range of RTP applications.</t> range of RTP applications.</t>
<texttable title="5.19 RFC7266 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 7266 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>calgextmap&nbsp;</c><c>Not Impacted&nbsp;</c><c>B&nbsp;</c> <th align="left">Level</th>
<c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
</texttable> <tbody>
<tr>
<td align="left">calgextmap</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6285: Rapid Acquisition of Multicast RTP Sessions"> <name>RFC 6285: Rapid Acquisition of Multicast RTP Sessions</name>
<t><xref target="RFC6285"/> describes a method <t><xref target="RFC6285" format="default"/> describes a method of
using the existing RTP and RTCP machinery that reduces the using the existing RTP and RTCP machinery that reduces the
acquisition delay. In this method, an auxiliary unicast RTP acquisition delay. In this method, an auxiliary unicast RTP
session carrying the Reference Information to the receiver precedes or session carrying the reference information to the receiver precedes or
accompanies the multicast stream. This unicast RTP flow can accompanies the multicast stream. This unicast RTP flow can
be transmitted at a faster than natural bitrate to further be transmitted at a faster-than-natural bitrate to further
accelerate the acquisition. The motivating use case for accelerate the acquisition. The motivating use case for
this capability is multicast applications that carry this capability is multicast applications that carry
real-time compressed audio and video.</t> real-time compressed audio and video.</t>
<texttable title="5.20 RFC6285 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6285 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>rams-updates&nbsp;</c><c>Not recommended <th align="left">Level</th>
&nbsp;</c><c>M&nbsp;</c><c>CAUTION&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
</texttable> <tbody>
<tr>
<td align="left">rams-updates</td>
<td align="left">Not recommended
</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6230: Media Control Channel Framework"> <name>RFC 6230: Media Control Channel Framework</name>
<t><xref target="RFC6230"/> describes a framework <t><xref target="RFC6230" format="default"/> describes a framework
and protocol for application deployment where the and protocol for application deployment where the
application programming logic and media processing are application programming logic and media processing are
distributed. This implies that application programming distributed. This implies that application programming
logic can seamlessly gain access to appropriate resources logic can seamlessly gain access to appropriate resources
that are not co-located on the same physical network entity. that are not co-located on the same physical network entity.
The framework uses SIP to establish an application-level control The framework uses SIP to establish an application-level control
mechanism between application servers and associated external mechanism between application servers and associated external
servers such as media servers.</t> servers such as media servers.</t>
<texttable title="5.21 RFC6230 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6230 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>cfw-id&nbsp;</c><c>Not Impacted&nbsp;</c> <th align="left">Level</th>
<c>M&nbsp;</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
</texttable> <tbody>
<tr>
<td align="left">cfw-id</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6364: SDP Elements for FEC Framework"> <name>RFC 6364: SDP Elements for FEC Framework</name>
<t><xref target="RFC6364"/> specifies the use of <t><xref target="RFC6364" format="default"/> specifies the use of
SDP to describe the parameters required to signal the SDP to describe the parameters required to signal the
Forward Error Correction (FEC) Framework Configuration Forward Error Correction (FEC) Framework Configuration
Information between the sender(s) and receiver(s). This Information between the sender(s) and receiver(s). This
document also provides examples that show the semantics for document also provides examples that show the semantics for
grouping multiple source and repair flows together for the grouping multiple source and repair flows together for the
applications that simultaneously use multiple instances of the applications that simultaneously use multiple instances of the
FEC Framework.</t> FEC Framework.</t>
<texttable title="5.22 RFC6364 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6364 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>fec-source-flow&nbsp;</c><c>Refer to the document defining specific <th align="left">Level</th>
FEC Scheme&nbsp;</c><c>M&nbsp;</c> <th align="left">Mux Category</th>
<c>SPECIAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>fec-repair-flow&nbsp;</c><c>Refer to the document defining specific <tr>
FEC Scheme&nbsp;</c><c>M&nbsp;</c> <td align="left">fec-source-flow</td>
<c>SPECIAL&nbsp;</c> <td align="left">Refer to the document defining specific
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> FEC scheme.</td>
<td align="left">M</td>
<c>repair-window&nbsp;</c><c>Refer to the document defining specific <td align="left">SPECIAL</td>
FEC Scheme&nbsp;</c><c>M&nbsp;</c> </tr>
<c>SPECIAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">fec-repair-flow</td>
<td align="left">Refer to the document defining specific
</texttable> FEC scheme.</td>
<td align="left">M</td>
<td align="left">SPECIAL</td>
</tr>
<tr>
<td align="left">repair-window</td>
<td align="left">Refer to the document defining specific
FEC scheme.</td>
<td align="left">M</td>
<td align="left">SPECIAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC4796: Content Attribute"> <name>RFC 4796: "content" Attribute</name>
<t><xref target="RFC4796"/> defines a new SDP media-level <t><xref target="RFC4796" format="default"/> defines a new SDP media-lev
attribute, 'content'. The 'content' attribute defines the el
attribute, "content". The "content" attribute defines the
content of the media stream to a more detailed level than content of the media stream to a more detailed level than
the media description line. The sender of an SDP session the media description line. The sender of an SDP session
description can attach the 'content' attribute to one or more 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
stream differently (e.g., show it on a big or small screen) based stream differently (e.g., show it on a big or small screen) based
on its content.</t> on its content.</t>
<texttable title="5.23 RFC4796 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4796 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>content&nbsp;</c><c>Not <th align="left">Level</th>
Impacted&nbsp;</c><c>M&nbsp;</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
</texttable> <tbody>
<tr>
<td align="left">content</td>
<td align="left">Not
impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC3407: SDP Simple Capability Declaration"> <name>RFC 3407: SDP Simple Capability Declaration</name>
<t><xref target="RFC3407"/> defines a set of SDP attributes that enables <t><xref target="RFC3407" format="default"/> defines a set of SDP attrib
SDP to provide a minimal and backwards compatible capability utes that enables
SDP to provide a minimal and backwards-compatible capability
declaration mechanism.</t> declaration mechanism.</t>
<texttable title="5.24 RFC3407 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 3407 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>sqn&nbsp;</c><c>Not Impacted&nbsp;</c> <th align="left">Level</th>
<c>B</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>cdsc&nbsp;</c><c>Not <tbody>
Impacted.&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">sqn</td>
<td align="left">Not impacted</td>
<c>cpar&nbsp;</c><c>Refer to <xref target="sec-encap"/>&nbsp;</c> <td align="left">B</td>
<c>B</c><c>INHERIT&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>cparmin&nbsp;</c><c>Refer to notes below &nbsp;</c> <td align="left">cdsc</td>
<c>B</c><c>SPECIAL&nbsp;</c> <td align="left">Not
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> impacted</td>
<td align="left">B</td>
<c>cparmax&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">NORMAL</td>
<c>B</c><c>SPECIAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
</texttable> <td align="left">cpar</td>
<td align="left">Refer to <xref target="sec-encap" format="default
"/></td>
<td align="left">B</td>
<td align="left">INHERIT</td>
</tr>
<tr>
<td align="left">cparmin</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">SPECIAL</td>
</tr>
<tr>
<td align="left">cparmax</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">SPECIAL</td>
</tr>
</tbody>
</table>
<t> <t>
NOTE: The attributes (a=cparmin and a=cparmax) define minimum NOTE: The attributes "a=cparmin" and "a=cparmax" define minimum
and maximum numerical values associated with the attributes and maximum numerical values associated with the attributes
described in a=cpar.</t> described in "a=cpar".</t>
<t>Since the cpar attribute can either define <t>Since the cpar attribute can either define
a 'b=' attribute or any 'a=' attribute, the multiplexing category a "b=" attribute or any "a=" attribute, the multiplexing category
depends on actual attribute being encapsulated and the implications depends on the actual attribute being encapsulated and the implications
of the numerical values assigned. Hence it is recommended to consult of the numerical values assigned. Hence it is recommended to consult
the specification defining attributes (cparmin/cparmax) to further the specification defining attributes "cparmin" and "cparmax" to furthe r
analyze their behavior under multiplexing.</t> analyze their behavior under multiplexing.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6284: Port Mapping between Unicast and Multicast RTP Se <name>RFC 6284: Port Mapping between Unicast and Multicast RTP Sessions<
ssions"> /name>
<t><xref target="RFC6284"/> presents a port <t><xref target="RFC6284" format="default"/> presents a port-mapping sol
mapping solution that allows RTP receivers to choose their ution that
allows RTP receivers to choose their
own ports for an auxiliary unicast session in RTP own ports for an auxiliary unicast session in RTP
applications using both unicast and multicast services. The applications using both unicast and multicast services. The
solution provides protection against denial-of-service or solution provides protection against denial-of-service or
packet amplification attacks that could be used to cause one packet amplification attacks that could be used to cause one
or more RTP packets to be sent to a victim client.</t> or more RTP packets to be sent to a victim client.</t>
<texttable title="5.25 RFC6284 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6284 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>portmapping-req&nbsp;</c><c>Not recommended, if port mapping is <th align="left">Level</th>
required by the application&nbsp;</c><c>M&nbsp;</c> <th align="left">Mux Category</th>
<c>CAUTION&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
<td align="left">portmapping-req</td>
<td align="left">Not recommended if port mapping is
required by the application</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6714: MSRP-CEMA"> <name>RFC 6714: MSRP-CEMA</name>
<t><xref target="RFC6714"/> defines a Message <t><xref target="RFC6714" format="default"/> defines a Message
Session Relay Protocol (MSRP) extension, Connection Session Relay Protocol (MSRP) extension, Connection
Establishment for Media Anchoring (CEMA). Support of this Establishment for Media Anchoring (CEMA). Support of this
extension is optional. The extension allows middle boxes to extension is optional. The extension allows middleboxes to
anchor the MSRP connection, without the need for middle anchor the MSRP connection without the need for middleboxes to modify
boxes to modify the MSRP messages; thus, it also enables the MSRP messages; thus, it also enables
secure end-to-end MSRP communication in networks where such secure end-to-end MSRP communication in networks where such
middle boxes are deployed. This document also defines a middleboxes are deployed. This document also defines an
SDP attribute, 'msrp-cema', that MSRP endpoints use to indicate SDP attribute, "msrp-cema", that MSRP endpoints use to indicate
support of the CEMA extension.</t> support of the CEMA extension.</t>
<texttable title="5.26 RFC6714 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6714 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>msrp-cema&nbsp;</c><c>Refer to notes below&nbsp;</c><c>M&nbsp;</c> <th align="left">Level</th>
<c>TBD&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<tbody>
<tr>
<td align="left">msrp-cema</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
</tbody>
</table>
</texttable> <t>NOTE: As per <xref target="RFC8843" sectionFormat="of" section="9"/>,
<t>NOTE: As per section 9 of there
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/>, there
exists no publicly available specification that exists no publicly available specification that
defines procedures for multiplexing/demultiplexing MRSP flows defines procedures for multiplexing/demultiplexing MSRP flows
over a single 5-tuple. Once such a specification is available, over a single 5-tuple. Once such a specification is available,
the multiplexing categories assignments for the attributes in this the assignments of multiplexing categories for the attributes in this
section could be revisited.</t> section could be revisited.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC4583: SDP Format for BFCP Streams"> <name>RFC 4583: SDP Format for BFCP Streams</name>
<t><xref target="RFC4583"/> document specifies how <t><xref target="RFC4583" format="default"/> specifies how
to describe Binary Floor Control Protocol (BFCP) streams in to describe Binary Floor Control Protocol (BFCP) streams in
SDP descriptions. User agents using the offer/answer model to SDP descriptions. User agents using the offer/answer model to
establish BFCP streams use this format in their offers and answers.</t> establish BFCP streams use this format in their offers and answers.</t>
<texttable title="5.27 RFC4583 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Level</ttcol>
<ttcol align='left'>Mux Category</ttcol>
<c>floorctrl&nbsp;</c> <!--[rfced] Per mail from Ben Campbell on 2018-12-20, we have updated the
<c>Refer to notes below&nbsp;</c> table below and the one in Section 15.2.4. However, now this document
<c>M&nbsp;</c><c>TBD&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> does not match the IANA registry. Which one is correct? (If this document
<c>&nbsp;</c><c>&nbsp;</c> is correct, we will send a request to IANA to update the registry.)
<c>confid&nbsp;</c><c>Not Impacted&nbsp;</c><c>M&nbsp;</c> > The update is to change the mux-category for 3 BFCP parameters (confid,
<c>NORMAL&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c > userid, and floorid) from “NORMAL” to “TBD”
> -->
<c>userid&nbsp;</c><c>Not <table align="center">
Impacted&nbsp;</c><c>M&nbsp;</c><c>NORMAL&nbsp;</c> <name>RFC 4583 Attribute Analysis</name>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <thead>
<tr>
<th align="left">Name</th>
<th align="left">Notes</th>
<th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">floorctrl</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<c>floorid&nbsp;</c> <tr>
<c>Not Impacted&nbsp;</c> <td align="left">confid</td>
<c>M&nbsp;</c><c>NORMAL&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">userid</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">floorid</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
</tbody>
</table>
<t>NOTE: <xref target="RFC4583"/> has been obsoleted by
<xref target="RFC8856"/>, which redefines the SDP attributes
listed in this section, including the "Mux Category" values. However,
<xref target="RFC8856"/> does not change the "Mux Category"
values of the attributes.</t>
</texttable> <t>NOTE: As per <xref target="RFC8843" sectionFormat="of"
<t>NOTE: As per section 9 of section="9"/>, there exists no publicly available specification that
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/>, there defines procedures for multiplexing/demultiplexing BFCP streams over a
exists no publicly available specification that single 5-tuple. Once such a specification is available, the
defines procedures for multiplexing/demultiplexing BFCP streams assignments of multiplexing categories for the attributes in this
over a single 5-tuple. Once such a specification is available, section could be revisited.</t>
the multiplexing categories assignments for the attributes in this
section could be revisited.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC5547: SDP Offer/Answer for File Transfer"> <name>RFC 5547: SDP Offer/Answer for File Transfer</name>
<t><xref target="RFC5547"/> provides a mechanism <t><xref target="RFC5547" format="default"/> provides a mechanism
to negotiate the transfer of one or more files between two to negotiate the transfer of one or more files between two
endpoints by using the SDP offer/answer model specified in endpoints by using the SDP offer/answer model specified in
<xref target="RFC3264"/>.</t> <xref target="RFC3264" format="default"/>.</t>
<texttable title="5.28 RFC5547 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5547 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>file-selector&nbsp;</c><c>Refer to notes below&nbsp;</c> <th align="left">Level</th>
<c>M</c><c>TBD&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>file-transfer-id&nbsp;</c><c>Refer to notes below&nbsp;</c> <tbody>
<c>M</c><c>TBD&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">file-selector</td>
<td align="left">Refer to notes below</td>
<c>file-disposition&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">TBD</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>file-date&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">file-transfer-id</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">TBD</td>
<c>file-icon&nbsp;</c><c>Refer to notes below&nbsp;</c> </tr>
<c>M</c><c>TBD&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">file-disposition</td>
<td align="left">Refer to notes below</td>
<c>file-range&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">TBD</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
</texttable> <td align="left">file-date</td>
<t>NOTE: As per section 9 of <td align="left">Refer to notes below</td>
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/>, <td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">file-icon</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">file-range</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
</tbody>
</table>
<t>NOTE: As per <xref target="RFC8843" sectionFormat="of" section="9"/>,
there exists no publicly available specification that there exists no publicly available specification that
defines procedures for multiplexing/demultiplexing MRSP flows defines procedures for multiplexing/demultiplexing MSRP flows
over a single 5-tuple. Once such a specification is available, over a single 5-tuple. Once such a specification is available,
the multiplexing categories assignments for attributes in this the assignments of multiplexing categories for attributes in this
section could be revisited.</t> section could be revisited.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6849: SDP and RTP Media Loopback Extension"> <name>RFC 6849: SDP and RTP Media Loopback Extension</name>
<t><xref target="RFC6849"/> adds new SDP media <t><xref target="RFC6849" format="default"/> adds new SDP media
types and attributes, which enable establishment of media types and attributes that enable establishment of media
sessions where the media is looped back to the sessions where the media is looped back to the
transmitter. Such media sessions will serve as monitoring transmitter. Such media sessions will serve as monitoring
and troubleshooting tools by providing the means for and troubleshooting tools by providing the means for
measurement of more advanced Voice over IP (VoIP), Real-time Text, measurement of more advanced Voice over IP (VoIP), real-time text,
and Video over IP performance metrics.</t> and Video over IP performance metrics.</t>
<texttable title="5.29 RFC6849 Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6849 Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>loopback rtp-pkt-loopback&nbsp;</c><c>The attribute value MUST be <th align="left">Level</th>
same for a given codec configuration&nbsp;</c> <th align="left">Mux Category</th>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>loopback rtp-media-loopback&nbsp;</c><c>The attribute value MUST be <tr>
same for a given codec configuration &nbsp;</c> <td align="left">loopback rtp-pkt-loopback</td>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> <td align="left">The attribute value <bcp14>MUST</bcp14> be
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> same for a given codec configuration.</td>
<td align="left">M</td>
<c>loopback-source&nbsp;</c><c>Not Impacted&nbsp;</c><c>M</c> <td align="left">IDENTICAL-PER-PT</td>
<c>NORMAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">loopback rtp-media-loopback</td>
<c>loopback-mirror&nbsp;</c><c>Not Impacted&nbsp;</c><c>M</c> <td align="left">The attribute value <bcp14>MUST</bcp14> be
<c>NORMAL&nbsp;</c> same for a given codec configuration.</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</texttable> </tr>
<tr>
<td align="left">loopback-source</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">loopback-mirror</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC5760: RTCP with Unicast Feedback "> <name>RFC 5760: RTCP with Unicast Feedback</name>
<t><xref target="RFC5760"/> specifies an extension <t><xref target="RFC5760" format="default"/> specifies an extension
to RTCP to use unicast feedback to a multicast sender. The proposed to RTCP to use unicast feedback to a multicast sender. The proposed
extension is useful for single-source multicast sessions extension is useful for single-source multicast sessions
such as Source-Specific Multicast (SSM) communication where such as source-specific multicast (SSM) communication where
the traditional model of many-to-many group communication is the traditional model of many-to-many group communication is
either not available or not desired.</t> either not available or not desired.</t>
<texttable title="5.30 RFC5760 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5760 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>rtcp-unicast&nbsp;</c><c>The attribute MUST be reported <th align="left">Level</th>
across all "m=" lines <th align="left">Mux Category</th>
multiplexed&nbsp;</c><c>M</c><c>IDENTICAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
<td align="left">rtcp-unicast</td>
<td align="left">The attribute <bcp14>MUST</bcp14> be reported
across all multiplexed "m=" lines.</td>
<td align="left">M</td>
<td align="left">IDENTICAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC3611: RTCP XR"> <name>RFC 3611: RTCP XR</name>
<t><xref target="RFC3611"/> defines the Extended <t><xref target="RFC3611" format="default"/> defines the Extended
Report (XR) packet type for RTCP, Report (XR) packet type for RTCP and defines how the use of XR packets
and defines how the use of XR packets can be signaled by an can be signaled by an
application if it employs the Session Description Protocol application if it employs the Session Description Protocol
(SDP).</t> (SDP).</t>
<texttable title="5.31 RFC3611 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 3611 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>rtcp-xr&nbsp;</c><c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</ <th align="left">Level</th>
c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
</texttable> <tbody>
<tr>
<td align="left">rtcp-xr</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC5939: SDP Capability Negotiation"> <name>RFC 5939: SDP Capability Negotiation</name>
<t><xref target="RFC5939"/> defines a general SDP <t><xref target="RFC5939" format="default"/> defines a general SDP
Capability Negotiation framework. It also specifies how to Capability Negotiation framework. It also specifies how to
provide attributes and transport protocols as capabilities provide attributes and transport protocols as capabilities
and negotiate them using the framework. Extensions for and negotiate them using the framework. Extensions for
other types of capabilities (e.g., media types and media other types of capabilities (e.g., media types and media
formats) may be provided in other documents.</t> formats) may be provided in other documents.</t>
<texttable title="5.32 RFC5939 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5939 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>pcfg&nbsp;</c> <th align="left">Level</th>
<c>Refer to <xref target="sec-encap"/> &nbsp;</c> <th align="left">Mux Category</th>
<c>M</c><c>SPECIAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>acfg&nbsp;</c> <tr>
<c>Refer to <xref target="sec-encap"/>&nbsp;</c> <td align="left">pcfg</td>
<c>M</c><c>SPECIAL&nbsp;</c> <td align="left">Refer to <xref target="sec-encap" format="default
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> "/></td>
<td align="left">M</td>
<c>csup&nbsp;</c><c>Not Impacted&nbsp;</c><c>B</c> <td align="left">SPECIAL</td>
<c>NORMAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">acfg</td>
<c>creq&nbsp;</c><c>Not Impacted&nbsp;</c><c>B</c> <td align="left">Refer to <xref target="sec-encap" format="default
<c>NORMAL&nbsp;</c> "/></td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">SPECIAL</td>
<c>acap&nbsp;</c> </tr>
<c>Refer to <xref target="sec-encap"/>&nbsp;</c> <tr>
<c>B</c><c>INHERIT&nbsp;</c> <td align="left">csup</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Not impacted </td>
<td align="left">B</td>
<c>tcap&nbsp;</c> <td align="left">NORMAL</td>
<c>Refer to <xref target="sec-encap"/>&nbsp;</c> </tr>
<c>B</c><c>INHERIT&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">creq</td>
<td align="left">Not impacted</td>
<c>cap-v0&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">B</td>
<c>B</c><c>NORMAL&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
</texttable> <td align="left">acap</td>
<td align="left">Refer to <xref target="sec-encap" format="default
"/></td>
<td align="left">B</td>
<td align="left">INHERIT</td>
</tr>
<tr>
<td align="left">tcap</td>
<td align="left">Refer to <xref target="sec-encap" format="default
"/></td>
<td align="left">B</td>
<td align="left">INHERIT</td>
</tr>
<tr>
<td align="left">cap-v0</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6871: SDP Media Capabilities Negotiation"> <name>RFC 6871: SDP Media Capabilities Negotiation</name>
<t>SDP capability negotiation provides a general framework <t>SDP capability negotiation provides a general framework
for indicating and negotiating capabilities in SDP. The base for indicating and negotiating capabilities in SDP. The base
framework defines only capabilities for negotiating transport framework only defines capabilities for negotiating transport
protocols and attributes. <xref target="RFC6871"></xref> extends the protocols and attributes. <xref target="RFC6871" format="default"/> exte
nds the
framework by defining media capabilities that can be used to framework by defining media capabilities that can be used to
negotiate media types and their associated parameters.</t> negotiate media types and their associated parameters.</t>
<texttable title="5.33 RFC6871 - Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6871 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>rmcap&nbsp;</c> <th align="left">Level</th>
<c>Refer to <xref target="sec-encap"/>&nbsp;</c> <th align="left">Mux Category</th>
<c>B</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>omcap&nbsp;</c><c>Not Impacted&nbsp;</c> <tr>
<c>B</c><c>NORMAL&nbsp;</c> <td align="left">rmcap</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to <xref target="sec-encap" format="default
"/></td>
<c>mfcap&nbsp;</c> <td align="left">B</td>
<c>Refer to <xref target="sec-encap"/>&nbsp;</c> <td align="left">IDENTICAL-PER-PT</td>
<c>B</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">omcap</td>
<c>mscap&nbsp;</c> <td align="left">Not impacted</td>
<c>Refer to <xref target="sec-encap"/>&nbsp;</c> <td align="left">B</td>
<c>B</c><c>INHERIT&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>lcfg&nbsp;</c> <td align="left">mfcap</td>
<c>Refer to <xref target="sec-encap"/>&nbsp;</c> <td align="left">Refer to <xref target="sec-encap" format="default
<c>B</c><c>SPECIAL&nbsp;</c> "/></td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">B</td>
<td align="left">IDENTICAL-PER-PT</td>
<c>sescap&nbsp;</c> </tr>
<c>Refer to notes below&nbsp;</c> <tr>
<c>S</c><c>CAUTION&nbsp;</c> <td align="left">mscap</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to <xref target="sec-encap" format="default
"/></td>
<c>med-v0&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">B</td>
<c>S</c><c>NORMAL&nbsp;</c> <td align="left">INHERIT</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
</texttable> <td align="left">lcfg</td>
<td align="left">Refer to <xref target="sec-encap" format="default
"/></td>
<td align="left">B</td>
<td align="left">SPECIAL</td>
</tr>
<tr>
<td align="left">sescap</td>
<td align="left">Refer to notes below</td>
<td align="left">S</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">med-v0</td>
<td align="left">Not impacted</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
<t>NOTE: The "sescap" attribute is not recommended <t>NOTE: The "sescap" attribute is not recommended
for use with multiplexing. The reason is that it requires the for use with multiplexing. The reason is that it requires the
use of unique configuration numbers across the entire SDP use of unique configuration numbers across the entire SDP
(per <xref target="RFC6871"/>) as opposed to within a media (per <xref target="RFC6871" format="default"/>) as opposed to within a m
description only (per <xref target="RFC5939"/>). As described in edia
<xref target="sec-encap"/>, the use of identical configuration description only (per <xref target="RFC5939" format="default"/>). As des
cribed in
<xref target="sec-encap" format="default"/>, the use of identical config
uration
numbers between multiplexed (bundled) media descriptions is the numbers between multiplexed (bundled) media descriptions is the
default way of indicating compatible configurations in a bundle. default way of indicating compatible configurations in a bundle.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC7006: Miscellaneous Capabilities Negotiation SDP"> <name>RFC 7006: Miscellaneous Capabilities Negotiation in SDP</name>
<t><xref target="RFC7006"/> extends the SDP capability negotiation <t><xref target="RFC7006" format="default"/> extends the SDP Capability
Negotiation
framework to allow endpoints to negotiate three additional SDP framework to allow endpoints to negotiate three additional SDP
capabilities. In particular, this memo provides a mechanism to capabilities. In particular, this memo provides a mechanism to
negotiate bandwidth ("b=" line), connection data ("c=" line), and negotiate bandwidth ("b=" line), connection data ("c=" line), and
session or media titles ("i=" line for each session or media).</t> session or media titles ("i=" line for each session or media).</t>
<texttable title="5.34 RFC7006 - Attribute Analysis "> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 7006 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>bcap&nbsp;</c> <th align="left">Level</th>
<c>Inherit the category SUM as <th align="left">Mux Category</th>
applicable to b= attribute&nbsp;</c> </tr>
<c>B</c><c>INHERIT&nbsp;</c> </thead>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tbody>
<tr>
<c>bcap-v0&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">bcap</td>
<c>B</c><c>NORMAL&nbsp;</c> <td align="left">Inherit the category SUM as
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> applicable to the "b=" attribute</td>
<td align="left">B</td>
<c>ccap&nbsp;</c><c>The connection address type <td align="left">INHERIT</td>
MUST be identical across all the multiplexed </tr>
"m=" lines&nbsp;</c> <tr>
<c>B</c><c>IDENTICAL&nbsp;</c> <td align="left">bcap-v0</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Not impacted</td>
<td align="left">B</td>
<c>ccap-v0&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">NORMAL</td>
<c>B</c><c>NORMAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">ccap</td>
<c>icap&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">The connection address type
<c>B</c><c>NORMAL&nbsp;</c> <bcp14>MUST</bcp14> be identical across all the multiplexed
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> "m=" lines.</td>
<td align="left">B</td>
<c>icap-v0&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">IDENTICAL</td>
<c>B</c><c>NORMAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
</texttable> <td align="left">ccap-v0</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">icap</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">icap-v0</td>
<td align="left">Not impacted</td>
<td align="left">B</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC4567: Key Management Extensions for SDP and RTSP"> <name>RFC 4567: Key Management Extensions for SDP and RTSP</name>
<t><xref target="RFC4567"/> defines general <t><xref target="RFC4567" format="default"/> defines general
extensions for SDP and Real Time Streaming Protocol (RTSP) to extensions for SDP and Real Time Streaming Protocol (RTSP) to
carry messages, as specified by a key management protocol, in carry messages, as specified by a key management protocol, in
order to secure the media. These extensions are presented as order to secure the media. These extensions are presented as
a framework, to be used by one or more key management protocols. As a framework to be used by one or more key management protocols. As
such, their use is meaningful only when complemented by an such, their use is meaningful only when complemented by an
appropriate key management protocol.</t> appropriate key management protocol.</t>
<texttable title="5.35 RFC4567 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4567 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>key-mgmt&nbsp;</c><c>Key management protocol MUST be <th align="left">Level</th>
identical across all the "m=" lines&nbsp;</c><c>B</c> <th align="left">Mux Category</th>
<c>IDENTICAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>mikey&nbsp;</c><c>Key management protocol MUST be <tr>
identical across all the "m=" lines&nbsp;</c><c>B</c> <td align="left">key-mgmt</td>
<c>IDENTICAL&nbsp;</c> <td align="left">Key management protocol <bcp14>MUST</bcp14> be
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> identical across all the "m=" lines.</td>
<td align="left">B</td>
</texttable> <td align="left">IDENTICAL</td>
</tr>
<tr>
<td align="left">mikey</td>
<td align="left">Key management protocol <bcp14>MUST</bcp14> be
identical across all the "m=" lines.</td>
<td align="left">B</td>
<td align="left">IDENTICAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section title="RFC4572: Comedia over TLS in SDP"> <section numbered="true" toc="default">
<t><xref target="RFC4572"/> specifies how to <name>RFC 4572: Comedia over TLS in SDP</name>
<t><xref target="RFC4572" format="default"/> specifies how to
establish secure connection-oriented media transport establish secure connection-oriented media transport
sessions over the Transport Layer Security (TLS) protocol sessions over the Transport Layer Security (TLS) protocol
using SDP. It defines a using SDP. (Note: <xref target="RFC4572"/> has been obsoleted by <xref
new SDP protocol identifier, 'TCP/TLS'. It also defines the target="RFC8122"/>.) It defines a
syntax and semantics for an SDP 'fingerprint' attribute that new SDP protocol identifier, "TCP/TLS". It also defines the
syntax and semantics for an SDP "fingerprint" attribute that
identifies the certificate that will be presented for the identifies the certificate that will be presented for the
TLS session. This mechanism allows media transport over TLS TLS session. This mechanism allows media transport over TLS
connections to be established securely, so long as the connections to be established securely, so long as the
integrity of session descriptions is assured.</t> integrity of session descriptions is assured.</t>
<texttable title="5.36 RFC4572 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4572 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>fingerprint&nbsp;</c><c>fingerprint value MUST be the <th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">fingerprint</td>
<td align="left">fingerprint value <bcp14>MUST</bcp14> be the
one that corresponds to the "m=" line chosen for one that corresponds to the "m=" line chosen for
setting up the underlying transport flow&nbsp;</c> setting up the underlying transport flow.</td>
<c>B</c><c>TRANSPORT&nbsp;</c> <td align="left">B</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
</texttable> </tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC4570: SDP Source Filters"> <name>RFC 4570: SDP Source Filters</name>
<t><xref target="RFC4570"/> describes how to adapt <t><xref target="RFC4570" format="default"/> describes how to adapt
SDP to express one or more source addresses as a source SDP to express one or more source addresses as a source
filter for one or more destination "connection" addresses. filter for one or more destination "connection" addresses.
It defines the syntax and semantics for an SDP "source-filter" It defines the syntax and semantics for an SDP "source-filter"
attribute that may reference either IPv4 or IPv6 address(es) as attribute that may reference either IPv4 or IPv6 address(es) as
either an inclusive or exclusive source list for either multicast or either an inclusive or exclusive source list for either multicast or
unicast destinations. In particular, an inclusive unicast destinations. In particular, an inclusive source filter can be
source-filter can be used to specify a Source-Specific used to specify a source-specific multicast (SSM) session.</t>
Multicast (SSM) session.</t> <table align="center">
<texttable title="5.37 RFC4570 Attribute Analysis"> <name>RFC 4570 Attribute Analysis</name>
<ttcol align='left'>Name</ttcol> <thead>
<ttcol align='left'>Notes</ttcol> <tr>
<ttcol align='left'>Level</ttcol> <th align="left">Name</th>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Notes</th>
<th align="left">Level</th>
<c>source-filter&nbsp;</c><c>The attribute MUST be repeated <th align="left">Mux Category</th>
across all "m=" lines </tr>
multiplexed&nbsp;</c><c>B</c><c>IDENTICAL&nbsp;</c> </thead>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tbody>
<tr>
</texttable> <td align="left">source-filter</td>
<td align="left">The attribute <bcp14>MUST</bcp14> be repeated
across all multiplexed "m=" lines.</td>
<td align="left">B</td>
<td align="left">IDENTICAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6128: RTCP Port for Multicast Sessions"> <name>RFC 6128: RTCP Port for Multicast Sessions</name>
<t>SDP has an attribute that allows RTP applications to specify <t>SDP has an attribute that allows RTP applications to specify
an address and a port associated with the RTCP traffic. In an address and a port associated with the RTCP traffic. In
RTP-based source-specific multicast (SSM) sessions, the same RTP-based source-specific multicast (SSM) sessions, the same
attribute is used to designate the address and the RTCP port attribute is used to designate the address and the RTCP port
of the Feedback Target in the SDP description. However, the of the Feedback Target in the SDP description. However, the
RTCP port associated with the SSM session itself cannot be RTCP port associated with the SSM session itself cannot be
specified by the same attribute to avoid ambiguity, and specified by the same attribute to avoid ambiguity and
thus, is required to be derived from the "m=" line of the thus is required to be derived from the "m=" line of the
media description. Deriving the RTCP port from the "m=" media description. Deriving the RTCP port from the "m="
line imposes an unnecessary restriction. <xref target="RFC6128"/> line imposes an unnecessary restriction. <xref target="RFC6128" format=" default"/>
removes this restriction by introducing a new SDP attribute.</t> removes this restriction by introducing a new SDP attribute.</t>
<texttable title="5.38 RFC6128 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6128 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>multicast-rtcp&nbsp;</c><c>Multicast RTCP port MUST be <th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">multicast-rtcp</td>
<td align="left">Multicast RTCP port <bcp14>MUST</bcp14> be
identical across all the identical across all the
"m=" lines&nbsp;</c><c>B</c><c>IDENTICAL&nbsp;</c> "m=" lines.</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">B</td>
<td align="left">IDENTICAL</td>
</texttable> </tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6189: ZRTP"> <name>RFC 6189: ZRTP</name>
<t><xref target="RFC6189"/> defines ZRTP, a protocol for media <t><xref target="RFC6189" format="default"/> defines ZRTP, a protocol fo
r media
path Diffie-Hellman exchange to agree on a session key and path Diffie-Hellman exchange to agree on a session key and
parameters for establishing unicast SRTP sessions for (VoIP applications parameters for establishing unicast SRTP sessions for VoIP applications.
.</t> </t>
<texttable title="5.39 RFC6189 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6189 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>zrtp-hash&nbsp;</c><c>zrtp-hash attribute MUST be the one <th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">zrtp-hash</td>
<td align="left">The zrtp-hash attribute <bcp14>MUST</bcp14> be th
e one
that corresponds to the "m=" line chosen for setting up that corresponds to the "m=" line chosen for setting up
the underlying transport flow&nbsp;</c><c>M</c> the underlying transport flow.</td>
<c>TRANSPORT&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
</texttable> </tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC4145: Connection-Oriented Media "> <name>RFC 4145: Connection-Oriented Media</name>
<t><xref target="RFC4145"/> describes how to <t><xref target="RFC4145" format="default"/> describes how to
express media transport over TCP using SDP. It defines express media transport over TCP using SDP. It defines
the SDP 'TCP' protocol identifier, the SDP 'setup' attribute, the SDP "TCP" protocol identifier, the SDP "setup" attribute,
which describes the connection setup procedure, and the SDP which describes the connection setup procedure, and the SDP
'connection' attribute, which handles connection "connection" attribute, which handles connection
reestablishment.</t> re-establishment.</t>
<texttable title="5.40 RFC4145 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4145 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>setup&nbsp;</c> <th align="left">Level</th>
<c>The setup attribute MUST be the one that corresponds to the "m=" <th align="left">Mux Category</th>
line chosen for setting up the underlying transport flow.&nbsp;</c> </tr>
<c>B</c><c>TRANSPORT&nbsp;</c> </thead>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tbody>
<tr>
<c>connection&nbsp;</c> <td align="left">setup</td>
<c>The connection attribute MUST be the one that corresponds to the <td align="left">The setup attribute <bcp14>MUST</bcp14> be the on
"m=" line chosen for setting up the underlying transport flow.&nbsp;</ e that corresponds to the "m="
c> line chosen for setting up the underlying transport flow.</td>
<c>B</c><c>TRANSPORT&nbsp;</c> <td align="left">B</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
</texttable> <tr>
<td align="left">connection</td>
<td align="left">The connection attribute <bcp14>MUST</bcp14> be t
he one that corresponds to the
"m=" line chosen for setting up the underlying transport flow.</td>
<td align="left">B</td>
<td align="left">TRANSPORT</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6947: The SDP altc Attribute"> <name>RFC 6947: The SDP "altc" Attribute</name>
<t><xref target="RFC6947"/> proposes a mechanism that allows <t><xref target="RFC6947" format="default"/> proposes a mechanism that a
llows
the same SDP offer to carry multiple IP addresses of different the same SDP offer to carry multiple IP addresses of different
address families (e.g., IPv4 and IPv6). The proposed attribute, address families (e.g., IPv4 and IPv6). The proposed "altc" attribute
the "altc" attribute, solves the backward-compatibility problem solves the backward-compatibility problem
that plagued Alternative Network Address Types (ANAT) due to that plagued Alternative Network Address Types (ANAT) due to
their syntax.</t> their syntax.</t>
<texttable title="5.41 RFC6947 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6947 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>altc&nbsp;</c><c>The IP Address and port MUST be the one <th align="left">Level</th>
that corresponds to the "m=" line chosen for setting up the <th align="left">Mux Category</th>
underlying transport flow&nbsp;</c> </tr>
<c>M</c><c>TRANSPORT&nbsp;</c> </thead>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tbody>
<tr>
</texttable> <td align="left">altc</td>
<td align="left">The IP address and port <bcp14>MUST</bcp14> be th
e ones
that correspond to the "m=" line chosen for setting up the
underlying transport flow.</td>
<td align="left">M</td>
<td align="left">TRANSPORT</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC7195: SDP Extension for Circuit Switched Bearers <name>RFC 7195: SDP Extension for Circuit-Switched Bearers in PS
in PSTN"> TN</name>
<t><xref target="RFC7195"/> describes use cases, requirements, and <t><xref target="RFC7195" format="default"/> describes use cases, requir
protocol extensions for using SDP offer/answer model for establishing ements, and
protocol extensions for using the SDP offer/answer model for establishin
g
audio and video media streams over circuit-switched bearers in the audio and video media streams over circuit-switched bearers in the
Public Switched Telephone Network (PSTN).</t> Public Switched Telephone Network (PSTN).</t>
<texttable title="5.42 RFC7195 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 7195 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>cs-correlation:callerid&nbsp;</c> <th align="left">Level</th>
<c>Refer to notes below&nbsp;</c> <th align="left">Mux Category</th>
<c>M</c><c>TBD&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>cs-correlation:uuie&nbsp;</c> <tr>
<c>Refer to notes below&nbsp;</c> <td align="left">cs-correlation:callerid</td>
<c>M&nbsp;</c><c>TBD&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">TBD</td>
<c>cs-correlation:dtmf&nbsp;</c> </tr>
<c>Refer to notes below&nbsp;</c> <tr>
<c>M</c><c>TBD&nbsp;</c> <td align="left">cs-correlation:uuie</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">cs-correlation:dtmf</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">cs-correlation:external</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
</tbody>
</table>
<c>cs-correlation:external&nbsp;</c> <t>NOTE: <xref target="RFC7195" format="default"/> defines SDP attribute
<c>Refer to notes below&nbsp;</c> s for
<c>M</c><c>TBD&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
</texttable>
<t>NOTE: <xref target="RFC7195"/> defines SDP attributes for
establishing audio and video media streams over circuit-switched establishing audio and video media streams over circuit-switched
bearers by defining a new nettype value "PSTN". However, section 7.2 of bearers by defining a new nettype value, "PSTN". However,
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/> requires the <xref target="RFC8843" sectionFormat="of" section="7.2"/> requires the
"c=" line nettype value of "IN". If in future there exists a specificat "c=" line nettype value to be "IN". If there exists in future a specifi
ion cation
that defines procedures to multiplex media streams over nettype "PSTN", that defines procedures to multiplex media streams over nettype "PSTN",
the multiplexing categories for attributes in this section could be the multiplexing categories for attributes in this section could be
revisited.</t> revisited.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC7272: IDMS Using the RTP Control Protocol (RTCP)"> <name>RFC 7272: IDMS Using the RTP Control Protocol (RTCP)</name>
<t><xref target="RFC7272"/> defines a new RTCP Packet Type and an <t><xref target="RFC7272" format="default"/> defines a new RTCP packet t
ype and an
RTCP Extended Report (XR) Block Type to be used for achieving RTCP Extended Report (XR) Block Type to be used for achieving
Inter-Destination Media Synchronization (IDMS).</t> Inter-Destination Media Synchronization (IDMS).</t>
<texttable title="5.43 RFC7272 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 7272 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>rtcp-idms&nbsp;</c><c>Not Impacted&nbsp;</c> <th align="left">Level</th>
<c>M</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
</texttable> <tbody>
<tr>
<td align="left">rtcp-idms</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section title="RFC5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP <section numbered="true" toc="default">
Attributes"> <name>RFC 5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP Attribu
<t><xref target="RFC5159"/> provides descriptions tes</name>
<t><xref target="RFC5159" format="default"/> provides descriptions
of SDP attributes used by the of SDP attributes used by the
Open Mobile Alliance's Broadcast Service and Content Open Mobile Alliance's "Service and Content Protection for Mobile
Protection specification.</t> Broadcast Services" specification.</t>
<texttable title="5.44 RFC5159 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5159 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>bcastversion&nbsp;</c><c>Not Impacted&nbsp;</c> <th align="left">Level</th>
<c>S</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>stkmstream&nbsp;</c><c>Not Impacted&nbsp;</c> <tbody>
<c>B</c><c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">bcastversion</td>
<td align="left">Not impacted</td>
<c>SRTPAuthentication&nbsp;</c><c>Needs further analysis&nbsp;</c> <td align="left">S</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>SRTPROCTxRate&nbsp;</c><c>Needs further analysis&nbsp;</c> <td align="left">stkmstream</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">Not impacted</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">B</td>
<td align="left">NORMAL</td>
</texttable> </tr>
<tr>
<td align="left">SRTPAuthentication</td>
<td align="left">Needs further analysis</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">SRTPROCTxRate</td>
<td align="left">Needs further analysis</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6193: Media Description for IKE in SDP"> <name>RFC 6193: Media Description for IKE in SDP</name>
<t><xref target="RFC6193"/> specifies how to <t><xref target="RFC6193" format="default"/> specifies how to
establish a media session that represents a virtual private establish a media session that represents a virtual private
network using the Session Initiation Protocol for the network using the Session Initiation Protocol for the
purpose of on-demand media/application sharing between purpose of on-demand media/application sharing between
peers. It extends the protocol identifier of SDP so that it can peers. It extends the protocol identifier of SDP so that it can
negotiate use of the Internet Key Exchange Protocol (IKE) for negotiate use of the Internet Key Exchange Protocol (IKE) for
media sessions in the SDP offer/answer model.</t> media sessions in the SDP offer/answer model.</t>
<texttable title="5.45 RFC6193 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6193 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ike-setup&nbsp;</c><c>Unlikely to use IKE in the context of <th align="left">Level</th>
multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>psk-fingerprint&nbsp;</c><c>Unlikely to use IKE in the context of <tbody>
multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">ike-setup</td>
<td align="left">Unlikely to use IKE in the context of
<c>ike-esp&nbsp;</c><c>Unlikely to use IKE in the context of multiplexing</td>
multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c> <td align="left">B</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">CAUTION</td>
</tr>
<c>ike-esp-udpencap&nbsp;</c><c>Unlikely to use IKE in the context of <tr>
multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c> <td align="left">psk-fingerprint</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Unlikely to use IKE in the context of
multiplexing</td>
</texttable> <td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">ike-esp</td>
<td align="left">Unlikely to use IKE in the context of
multiplexing</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">ike-esp-udpencap</td>
<td align="left">Unlikely to use IKE in the context of
multiplexing</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
</tbody>
</table>
</section> </section>
<section title="RFC2326: Real Time Streaming Protocol"> <!--[rfced] RFC 2326 was obsoleted by RFC 7826. Is the information in the
table still accurate if we update citations?
Original:
This section analyzes attributes listed in [IANA], grouped under the
IETF document that defines them.
...
RFC2326: Real Time Streaming Protocol
-->
<section numbered="true" toc="default">
<name>RFC 2326: Real Time Streaming Protocol</name>
<t>The Real Time Streaming Protocol, or RTSP, is an application-level <t>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 controlled, on-demand delivery of real-time data, such as audio
and video.</t> and video.</t>
<texttable title="5.46 RFC2326 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 2326 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>etag&nbsp;</c><c>RTSP is not supported for RTP Stream <th align="left">Level</th>
multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>range&nbsp;</c><c>RTSP is not supported for RTP Stream <tbody>
multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">etag</td>
<td align="left">RTSP is not supported for RTP stream
<c>control&nbsp;</c><c>RTSP is not supported for RTP Stream multiplexing.</td>
multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c> <td align="left">B</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">CAUTION</td>
</tr>
<c>mtag&nbsp;</c><c>RTSP is not supported for RTP Stream <tr>
multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c> <td align="left">range</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">RTSP is not supported for RTP stream
multiplexing.</td>
</texttable> <td align="left">B</td>
<t>NOTE: <xref target="RFC2326"/> defines SDP attributes that are <td align="left">CAUTION</td>
applicable in the declarative usage of SDP alone. For </tr>
purposes of this document, only the Offer/Answer usage of SDP <tr>
is considered as mandated by <xref <td align="left">control</td>
target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>.</t> <td align="left">RTSP is not supported for RTP stream
multiplexing.</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">mtag</td>
<td align="left">RTSP is not supported for RTP stream
multiplexing.</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
</tbody>
</table>
<t>NOTE: <xref target="RFC2326" format="default"/> defines SDP attribute
s 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 <xref target="RFC8843" format="default"
/>.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC6064: SDP and RTSP Extensions for 3GPP"> <name>RFC 6064: SDP and RTSP Extensions for 3GPP</name>
<t>The Packet-switched Streaming Service (PSS) and the <t>The Packet-switched Streaming Service (PSS) and the
Multimedia Broadcast/Multicast Service (MBMS) defined by Multimedia Broadcast/Multicast Service (MBMS) defined by
3GPP use SDP and RTSP with some extensions. <xref 3GPP use SDP and RTSP with some extensions. <xref target="RFC6064" forma
target="RFC6064"/> provides information about t="default"/> provides information about
these extensions and registers the RTSP and SDP extensions these extensions and registers the RTSP and SDP extensions
with IANA.</t> with IANA.</t>
<texttable title="5.47 RFC6064 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6064 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>X-predecbufsize&nbsp;</c> <th align="left">Level</th>
<c>Refer to notes below&nbsp;</c> <th align="left">Mux Category</th>
<c>M</c><c>CAUTION&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>X-initpredecbufperiod&nbsp;</c> <tr>
<c>Refer to notes below&nbsp;</c> <td align="left">X-predecbufsize</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">CAUTION</td>
<c>X-initpostdecbufperiod&nbsp;</c> </tr>
<c>Refer to notes below&nbsp;</c> <tr>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">X-initpredecbufperiod</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to notes below</td>
<td align="left">M</td>
<c>X-decbyterate</c><c>Refer to notes below&nbsp;</c> <td align="left">CAUTION</td>
<c>M</c><c>CAUTION&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">X-initpostdecbufperiod</td>
<c>3gpp-videopostdecbufsize&nbsp;</c> <td align="left">Refer to notes below</td>
<c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>framesize</c><c>Refer to notes below&nbsp;</c><c>M</c> <td align="left">X-decbyterate</td>
<c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">CAUTION</td>
<c>3GPP-Integrity-Key&nbsp;</c> </tr>
<c>Refer to notes below&nbsp;</c><c>S</c> <tr>
<c>CAUTION&nbsp;</c> <td align="left">3gpp-videopostdecbufsize</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to notes below</td>
<td align="left">M</td>
<c>3GPP-SDP-Auth&nbsp;</c> <td align="left">CAUTION</td>
<c>Refer to notes below&nbsp;</c><c>S</c> </tr>
<c>CAUTION&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">framesize</td>
<td align="left">Refer to notes below</td>
<c>3GPP-SRTP-Config&nbsp;</c> <td align="left">M</td>
<c>Refer to notes below&nbsp;&nbsp;</c><c>M</c> <td align="left">CAUTION</td>
<c>CAUTION&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">3GPP-Integrity-Key</td>
<c>alt&nbsp;</c> <td align="left">Refer to notes below</td>
<c>Refer to notes below&nbsp;</c> <td align="left">S</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>alt-default-id&nbsp;</c> <td align="left">3GPP-SDP-Auth</td>
<c>Refer to notes below&nbsp;</c> <td align="left">Refer to notes below</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">S</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">CAUTION</td>
</tr>
<c>alt-group&nbsp;</c> <tr>
<c>Refer to notes below&nbsp;</c><c>S</c> <td align="left">3GPP-SRTP-Config</td>
<c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">CAUTION</td>
<c>3GPP-Adaptation-Support&nbsp;</c> </tr>
<c>Refer to notes below&nbsp;&nbsp;</c><c>M</c> <tr>
<c>CAUTION&nbsp;</c> <td align="left">alt</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to notes below</td>
<td align="left">M</td>
<c>3GPP-Asset-Information&nbsp;</c> <td align="left">CAUTION</td>
<c>Refer to notes below&nbsp;</c><c>B</c> </tr>
<c>CAUTION&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">alt-default-id</td>
<td align="left">Refer to notes below</td>
<c>mbms-mode&nbsp;</c> <td align="left">M</td>
<c>Refer to notes below&nbsp;</c><c>B</c> <td align="left">CAUTION</td>
<c>CAUTION&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">alt-group</td>
<c>mbms-flowid&nbsp;</c> <td align="left">Refer to notes below</td>
<c>Refer to notes below&nbsp;</c><c>M</c> <td align="left">S</td>
<c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>mbms-repair&nbsp;</c> <td align="left">3GPP-Adaptation-Support</td>
<c>Refer to notes below&nbsp;</c><c>B</c> <td align="left">Refer to notes below</td>
<c>CAUTION&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">CAUTION</td>
</tr>
<c>3GPP-QoE-Metrics&nbsp;</c> <tr>
<c>Refer to notes below&nbsp;</c> <td align="left">3GPP-Asset-Information</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">B</td>
<td align="left">CAUTION</td>
<c>3GPP-QoE-Metrics:Corruption duration&nbsp;</c> </tr>
<c>Refer to notes below&nbsp;</c> <tr>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">mbms-mode</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to notes below</td>
<td align="left">B</td>
<c>3GPP-QoE-Metrics:Rebuffering duration&nbsp;</c> <td align="left">CAUTION</td>
<c>Refer to notes below&nbsp;</c> </tr>
<c>M</c><c>CAUTION&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">mbms-flowid</td>
<td align="left">Refer to notes below</td>
<c>3GPP-QoE-Metrics:Initial buffering duration&nbsp;</c> <td align="left">M</td>
<c>Refer to notes below&nbsp;</c> <td align="left">CAUTION</td>
<c>M</c><c>CAUTION&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">mbms-repair</td>
<c>3GPP-QoE-Metrics:Successive loss of RTP packets&nbsp;</c> <td align="left">Refer to notes below</td>
<c>Refer to notes below&nbsp;</c> <td align="left">B</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>3GPP-QoE-Metrics:Frame rate deviation&nbsp;</c> <td align="left">3GPP-QoE-Metrics</td>
<c>Refer to notes below&nbsp;</c> <td align="left">Refer to notes below</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">CAUTION</td>
</tr>
<c>3GPP-QoE-Metrics:Jitter duration&nbsp;</c> <tr>
<c>Refer to notes below&nbsp;</c> <td align="left">3GPP-QoE-Metrics:Corruption duration</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">CAUTION</td>
<c>3GPP-QoE-Metrics:Content Switch Time&nbsp;</c> </tr>
<c>Refer to notes below&nbsp;</c> <tr>
<c>B</c><c>CAUTION&nbsp;</c> <td align="left">3GPP-QoE-Metrics:Rebuffering duration</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Refer to notes below</td>
<td align="left">M</td>
<c>3GPP-QoE-Metrics:Average Codec Bitrate&nbsp;</c> <td align="left">CAUTION</td>
<c>Refer to notes below&nbsp;</c> </tr>
<c>M</c><c>CAUTION&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">3GPP-QoE-Metrics:Initial buffering duration</td>
<td align="left">Refer to notes below</td>
<c>3GPP-QoE-Metrics:Codec Information&nbsp;</c> <td align="left">M</td>
<c>Refer to notes below&nbsp;</c> <td align="left">CAUTION</td>
<c>M</c><c>CAUTION&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">3GPP-QoE-Metrics:Successive loss of RTP packets</
<c>3GPP-QoE-Metrics:Buffer Status&nbsp;</c> td>
<c>Refer to notes below&nbsp;</c> <td align="left">Refer to notes below</td>
<c>M</c><c>CAUTION&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">CAUTION</td>
</tr>
</texttable> <tr>
<t>NOTE: <xref target="RFC6064"/> defines SDP attributes that are <td align="left">3GPP-QoE-Metrics:Frame rate deviation</td>
applicable in the declarative usage of SDP alone. For <td align="left">Refer to notes below</td>
purposes of this document, only the Offer/Answer usage of SDP <td align="left">M</td>
is considered as mandated by <xref <td align="left">CAUTION</td>
target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>. </tr>
<tr>
<td align="left">3GPP-QoE-Metrics:Jitter duration</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">3GPP-QoE-Metrics:Content Switch Time</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">3GPP-QoE-Metrics:Average Codec Bitrate</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">3GPP-QoE-Metrics:Codec Information</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">3GPP-QoE-Metrics:Buffer Status</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
</tbody>
</table>
<t>NOTE: <xref target="RFC6064" format="default"/> defines SDP attribute
s 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 <xref target="RFC8843" format="default"
/>.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC3108: ATM SDP"> <name>RFC 3108: ATM SDP</name>
<t><xref target="RFC3108"></xref> describes conventions <t><xref target="RFC3108" format="default"/> describes conventions
for using SDP described for controlling ATM Bearer Connections, for using SDP described for controlling ATM bearer connections
and any associated ATM Adaptation Layer (AAL).</t> and any associated ATM Adaptation Layer (AAL).</t>
<texttable title="5.48 RFC3108 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 3108 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>aalType&nbsp;</c><c>Refer to notes below</c> <th align="left">Level</th>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <th align="left">Mux Category</th>
<c>eecid&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> </thead>
<c>capability&nbsp;</c><c>Refer to notes below</c> <tbody>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>qosClass&nbsp;</c><c>Refer to notes below</c> <td align="left">aalType</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>bcob&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>stc&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>upcc&nbsp;</c><c>Refer to notes below</c> <td align="left">eecid</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>atmQOSparms&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>atmTrfcDesc&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>abrParms&nbsp;</c><c>Refer to notes below</c> <td align="left">capability</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>abrSetup&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>bearerType&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>lij&nbsp;</c><c>Refer to notes below</c> <td align="left">qosClass</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>anycast&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>cache&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>bearerSigIE&nbsp;</c><c>Refer to notes below</c> <td align="left">bcob</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>aalApp&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>cbrRate&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>sbc&nbsp;</c><c>Refer to notes below</c> <td align="left">stc</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>clkrec&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>fec&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>prtfl&nbsp;</c><c>Refer to notes below</c> <td align="left">upcc</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>structure&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>cpsSDUsize&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>aal2CPS&nbsp;</c><c>Refer to notes below</c> <td align="left">atmQOSparms</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>aal2CPSSDUrate&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>aal2sscs3661unassured&nbsp;</c> </tr>
<c>Refer to notes below</c> <tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">atmTrfcDesc</td>
<c>aal2sscs3661assured&nbsp;</c> <td align="left">Refer to notes below</td>
<c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>aal2sscs3662&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>aal5sscop&nbsp;</c><c>Refer to notes below</c> <td align="left">abrParms</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>atmmap&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>silenceSupp&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>ecan&nbsp;</c><c>Refer to notes below</c> <td align="left">abrSetup</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>gc&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>profileDesc&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>vsel&nbsp;</c><c>Refer to notes below</c> <td align="left">bearerType</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>dsel&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>fsel&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>onewaySel&nbsp;</c><c>Refer to notes below</c> <td align="left">lij</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>codecconfig&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>isup_usi&nbsp;</c><c>Refer to notes below</c> </tr>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <tr>
<c>uiLayer1_Prot&nbsp;</c><c>Refer to notes below</c> <td align="left">anycast</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">Refer to notes below</td>
<c>chain&nbsp;</c><c>Refer to notes below</c> <td align="left">B</td>
<c>B&nbsp;</c><c>CAUTION&nbsp;</c> <td align="left">CAUTION</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</texttable> <tr>
<t>NOTE: RFC3108 describes conventions for using SDP for <td align="left">cache</td>
characterizing ATM bearer connections using an AAL1, AAL2 or <td align="left">Refer to notes below</td>
AAL5 adaptation layers. For AAL1, AAL2 and AAL5, bearer <td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">bearerSigIE</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">aalApp</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">cbrRate</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">sbc</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">clkrec</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">fec</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">prtfl</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">structure</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">cpsSDUsize</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">aal2CPS</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">aal2CPSSDUrate</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">aal2sscs3661unassured</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">aal2sscs3661assured</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">aal2sscs3662</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">aal5sscop</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">atmmap</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">silenceSupp</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">ecan</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">gc</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">profileDesc</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">vsel</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">dsel</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">fsel</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">onewaySel</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">codecconfig</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">isup_usi</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">uiLayer1_Prot</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">chain</td>
<td align="left">Refer to notes below</td>
<td align="left">B</td>
<td align="left">CAUTION</td>
</tr>
</tbody>
</table>
<t>NOTE: RFC 3108 describes conventions for using SDP for
characterizing ATM bearer connections using an AAL1, AAL2, or
AAL5 adaptation layer. For AAL1, AAL2, and AAL5, bearer
connections can be used to transport single media streams. connections can be used to transport single media streams.
In addition, for AAL1 and AAL2, multiple media streams can be In addition, for AAL1 and AAL2, multiple media streams can be
multiplexed into a bearer connection. For all adaptation types multiplexed into a bearer connection. For all adaptation types
(AAL1, AAL2 and AAL5), bearer connections can be bundled into a single m (AAL1, AAL2, and AAL5), bearer connections can be bundled into a single
edia media
group. In all cases addressed by RFC3108, a real-time media group. In all cases addressed by RFC 3108, a real-time media
stream (voice, video, voiceband data, pseudo-wire, and others) stream (voice, video, voiceband data, pseudowire, 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 connection. RFC 3108 does not address cases where ATM serves
as a low-level transport pipe for IP packets which in turn can as a low-level transport pipe for IP packets that can, in turn,
carry one or more real-time (e.g. VoIP) media sessions with a carry one or more real-time (e.g., VoIP) media sessions with a
life-cycle different from that of the underlying ATM life cycle different from that of the underlying ATM
transport.</t> transport.</t>
</section>
<section title="3GPP TS 26.114">
<t>
<xref target="R3GPPTS26.114"/> specifies IP multimedia subsystem:
Media handling and interaction
</t>
<texttable title="5.49 3GPP TS 26.114 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Level</ttcol>
<ttcol align='left'>Mux Category</ttcol>
<c>3gpp_sync_info&nbsp;</c>
<c>Usage defined for the IP Multimedia Subsystem&nbsp;</c>
<c>M</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
<c>3gpp_MaxRecvSDUSize&nbsp;</c>
<c>Usage defined for the IP Multimedia Subsystem&nbsp;</c>
<c>M</c><c>NORMAL&nbsp;</c>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
</texttable>
</section> </section>
<section title="3GPP TS 183.063"> <section numbered="true" toc="default">
<name>3GPP TS 183.063</name>
<t> <t>
<xref target="R3GPPTS183.063"/> Telecommunications and Internet <xref target="TISPAN" format="default"/> describes Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN); converged Services and Protocols for Advanced Networking (TISPAN);
</t> </t>
<texttable title="5.50 3GPP TS 183.063 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>3GPP TS 183.063 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>PSCid&nbsp;</c><c>Not Impacted&nbsp;</c> <th align="left">Level</th>
<c>S</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>bc_service&nbsp;</c><c>Not Impacted&nbsp;</c> <tbody>
<c>S</c><c>NORMAL&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">PSCid</td>
<td align="left">Not impacted</td>
<c>bc_program&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">S</td>
<c>S</c><c>NORMAL&nbsp;</c> <td align="left">NORMAL</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>bc_service_package&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">bc_service</td>
<c>S</c><c>NORMAL&nbsp;</c> <td align="left">Not impacted</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">S</td>
</texttable> <td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">bc_program</td>
<td align="left">Not impacted</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">bc_service_package</td>
<td align="left">Not impacted</td>
<td align="left">S</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="3GPP TS 24.182"> <name>3GPP TS 24.182</name>
<t> <t>
<xref target="R3GPPTS24.182"/> specifies IP multimedia subsystem <xref target="IMS-CAT" format="default"/> specifies an IP multimedia s
Custom Alerting tones ubsystem for
customized alerting tones.
</t> </t>
<texttable title="5.51 3GPP TS 24.182 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>3GPP TS 24.182 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>g.3gpp.cat&nbsp;</c> <th align="left">Level</th>
<c>Usage defined for the IP Multimedia Subsystem&nbsp;</c> <th align="left">Mux Category</th>
<c>M</c><c>NORMAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
<td align="left">g.3gpp.cat</td>
<td align="left">Usage defined for the IP multimedia subsystem</td
>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="3GPP TS 24.183"> <name>3GPP TS 24.183</name>
<t> <t>
<xref target="R3GPPTS24.183"/> specifies IP multimedia <xref target="IMS-CRS" format="default"/> specifies an IP multimedia
subsystem Custom Ringing Signal subsystem for customized ringing signal.
</t> </t>
<texttable title="5.52 3GPP TS 24.183 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>3GPP TS 24.183 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>g.3gpp.crs&nbsp;</c> <th align="left">Level</th>
<c>Usage defined for the IP Multimedia Subsystem&nbsp;</c> <th align="left">Mux Category</th>
<c>M</c><c>NORMAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
<td align="left">g.3gpp.crs</td>
<td align="left">Usage defined for the IP multimedia subsystem</td
>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="3GPP TS 24.229"> <name>3GPP TS 24.229</name>
<t> <t>
<xref target="R3GPPTS24.229"/> specifies IP multimedia call <xref target="IP-CALL" format="default"/> specifies an IP multimedia ca ll
control protocol based on Session Initial protocol and control protocol based on Session Initial protocol and
Session Description Protocol. Session Description Protocol.
</t> </t>
<texttable title="5.53 3GPP TS 24.229 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>3GPP TS 24.229 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>secondary-realm&nbsp;</c> <th align="left">Level</th>
<c>secondary-realm MUST be the one that corresponds <th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">secondary-realm</td>
<td align="left">secondary-realm <bcp14>MUST</bcp14> be the one t
hat corresponds
to the "m=" line chosen for setting up the underlying to the "m=" line chosen for setting up the underlying
transport flow&nbsp;</c><c>M</c> transport flow.</td>
<c>TRANSPORT&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
<c>visited-realm&nbsp;</c> <tr>
<c>visited-realm MUST be the one that corresponds <td align="left">visited-realm</td>
<td align="left">visited-realm <bcp14>MUST</bcp14> be the one that
corresponds
to the "m=" line chosen for setting up the underlying to the "m=" line chosen for setting up the underlying
transport flow&nbsp;</c><c>M</c> transport flow.</td>
<c>TRANSPORT&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">TRANSPORT</td>
</tr>
<c>omr-m-cksum&nbsp;</c><c>Not Impacted&nbsp;</c> <tr>
<c>M</c><c>NORMAL&nbsp;</c><c>&nbsp;</c> <td align="left">omr-m-cksum</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Not impacted</td>
<td align="left">M</td>
<c>omr-s-cksum&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">NORMAL</td>
<c>M</c><c>NORMAL&nbsp;</c><c>&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">omr-s-cksum</td>
<c>omr-m-att&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">Not impacted</td>
<c>M</c><c>NORMAL&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">NORMAL</td>
</tr>
<c>omr-s-att&nbsp;</c><c>Not Impacted&nbsp;</c> <tr>
<c>M</c><c>NORMAL&nbsp;</c><c>&nbsp;</c> <td align="left">omr-m-att</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Not impacted</td>
<td align="left">M</td>
<c>omr-m-bw&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">NORMAL</td>
<c>M</c><c>NORMAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">omr-s-att</td>
<c>omr-s-bw&nbsp;</c><c>Not Impacted&nbsp;</c> <td align="left">Not impacted</td>
<c>M</c><c>NORMAL&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">NORMAL</td>
</tr>
<c>omr-codecs&nbsp;</c><c>Not Impacted&nbsp;</c> <tr>
<c>M</c><c>NORMAL&nbsp;</c> <td align="left">omr-m-bw</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">Not impacted</td>
</texttable> <td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">omr-s-bw</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
<tr>
<td align="left">omr-codecs</td>
<td align="left">Not impacted</td>
<td align="left">M</td>
<td align="left">NORMAL</td>
</tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="ITU T.38"> <name>ITU T.38</name>
<t> <t>
<xref target="T.38"></xref> defines procedures for <xref target="T.38" format="default"/> defines procedures for
real-time Group 3 facsimile communications over IP networks. real-time Group 3 facsimile communications over IP networks.
</t> </t>
<texttable title="5.54 ITU T.38 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>ITU T.38 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>T38FaxVersion&nbsp;</c><c>Refer to notes below&nbsp;</c> <th align="left">Level</th>
<c>M</c><c>TBD&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>T38MaxBitRate&nbsp;</c><c>Refer to notes below&nbsp;</c> <tbody>
<c>M</c><c>TBD&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">T38FaxVersion</td>
<td align="left">Refer to notes below</td>
<c>T38FaxFillBitRemoval&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">TBD</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>T38FaxTranscodingMMR&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">T38MaxBitRate</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">TBD</td>
<c>T38FaxTranscodingJBIG&nbsp;</c><c>Refer to notes below&nbsp;</c> </tr>
<c>M</c><c>TBD&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">T38FaxFillBitRemoval</td>
<td align="left">Refer to notes below</td>
<c>T38FaxRateManagement&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">TBD</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>T38FaxMaxBuffer&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">T38FaxTranscodingMMR</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">TBD</td>
<c>T38FaxMaxDatagram&nbsp;</c><c>Refer to notes below&nbsp;</c> </tr>
<c>M</c><c>TBD&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">T38FaxTranscodingJBIG</td>
<td align="left">Refer to notes below</td>
<c>T38FaxUdpEC&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">TBD</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>T38FaxMaxIFP&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">T38FaxRateManagement</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">TBD</td>
<c>T38FaxUdpECDepth&nbsp;</c><c>Refer to notes below&nbsp;</c> </tr>
<c>M</c><c>TBD&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">T38FaxMaxBuffer</td>
<td align="left">Refer to notes below</td>
<c>T38FaxUdpFECMaxSpan&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">TBD</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>T38ModemType&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">T38FaxMaxDatagram</td>
<c>M</c><c>TBD&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">TBD</td>
<c>T38VendorInfo&nbsp;</c><c>Refer to notes below&nbsp;</c> </tr>
<c>M</c><c>TBD&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">T38FaxUdpEC</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">T38FaxMaxIFP</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">T38FaxUdpECDepth</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">T38FaxUdpFECMaxSpan</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">T38ModemType</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">T38VendorInfo</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
</tbody>
</table>
</texttable> <t>NOTE: As per <xref target="RFC8843" sectionFormat="of" section="9"/>,
<t>NOTE: As per section 9 of
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/>,
there exists no publicly available specification that defines there exists no publicly available specification that defines
procedures for multiplexing/demultiplexing fax protocols flows over a procedures for multiplexing/demultiplexing fax protocol flows over a
single 5-tuple. Once such a specification is available, the multiplexi ng single 5-tuple. Once such a specification is available, the multiplexi ng
category assignments for the attributes in this section could be revis ited.</t> category assignments for the attributes in this section could be revis ited.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="ITU-T Q.1970"> <name>ITU-T Q.1970</name>
<t> <t>
<xref target="Q.1970"></xref> defines Bearer Independent Call Control ( BICC) <xref target="Q.1970" format="default"/> defines Bearer Independent Cal l Control (BICC)
IP bearer control protocol. IP bearer control protocol.
</t> </t>
<texttable title="5.55 ITU-T Q.1970 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>ITU-T Q.1970 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ipbcp&nbsp;</c><c>ipbcp version identifies type of <th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">ipbcp</td>
<td align="left">ipbcp version identifies the types of
IP bearer control protocol (IPBCP) message used in BICC (ITU-T Q.1901) IP bearer control protocol (IPBCP) message used in BICC (ITU-T Q.1901)
environment which are limited to single media payload. Refer to the pe environment that are limited to single-media payload. Refer to the per
rtinent tinent
ITU-T specifications while multiplexing&nbsp;</c> ITU-T specifications while multiplexing.</td>
<c>S</c><c>SPECIAL&nbsp;</c> <td align="left">S</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">SPECIAL</td>
</texttable> </tr>
</tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="ITU-T H.248.15"> <name>ITU-T H.248.15</name>
<t> <t>
ITU-T H.248.15 <xref target="H.248.15"></xref> defines Gateway Control ITU-T H.248.15 <xref target="H.248.15" format="default"/> defines the
Protocol Gateway Control Protocol
SDP H.248 package attribute SDP H.248 package attribute.
</t> </t>
<texttable title="5.56 ITU-T H.248.15 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>ITU-T H.248.15 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>h248item&nbsp;</c><c>It is only applicable for <th align="left">Level</th>
<th align="left">Mux Category</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">h248item</td>
<td align="left">It is only applicable for
signaling the inclusion of H.248 extension packages to a signaling the inclusion of H.248 extension packages to a
gateway via the local and remote descriptors. The attribute gateway via the local and remote descriptors. The attribute
itself is unaffected by multiplexing, but the packaged itself is unaffected by multiplexing, but the package
referenced in a specific use of the attribute can be referenced in a specific use of the attribute can be
impacted. Further analysis of each package is needed to impacted. Further analysis of each package is needed to
determine if there is an issue. This is only a concern in determine if there is an issue. This is only a concern in
environments using a decomposed server/gateway with H.248 environments using a decomposed server/gateway with H.248
signaled between them. The ITU-T will need to do further signaled between them. The ITU-T will need to do further
analysis of various packages when they specify how to signal analysis of various packages when they specify how to signal
the use of multiplexing to a gateway&nbsp;</c> the use of multiplexing to a gateway.</td>
<c>B</c><c>SPECIAL&nbsp;</c> <td align="left">B</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">SPECIAL</td>
</tr>
</texttable> </tbody>
</table>
</section> </section>
<section numbered="true" toc="default">
<section title="RFC4975: The Message Session Relay Protocol"> <name>RFC 4975: The Message Session Relay Protocol</name>
<t><xref target="RFC4975"/> the Message Session <t><xref target="RFC4975" format="default"/> describes the Message Sessi
on
Relay Protocol, a protocol for transmitting a series of Relay Protocol, a protocol for transmitting a series of
related instant messages in the context of a session. related instant messages in the context of a session.
Message sessions are treated like any other media stream Message sessions are treated like any other media stream
when set up via a rendezvous or session creation protocol when set up via a rendezvous or session-creation protocol
such as the Session Initiation Protocol.</t> such as the Session Initiation Protocol.</t>
<texttable title="5.57 RFC4975 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4975 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>accept-types&nbsp;</c><c>Refer to notes below&nbsp;</c> <th align="left">Level</th>
<c>M&nbsp;</c><c>TBD&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>accept-wrapped-types&nbsp;</c><c>Refer to notes below&nbsp;</c> <tbody>
<c>M&nbsp;</c><c>TBD&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">accept-types</td>
<td align="left">Refer to notes below</td>
<c>max-size&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">M</td>
<c>M&nbsp;</c><c>TBD&nbsp;</c> <td align="left">TBD</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
<tr>
<c>path&nbsp;</c><c>Refer to notes below&nbsp;</c> <td align="left">accept-wrapped-types</td>
<c>M&nbsp;</c><c>TBD&nbsp;</c> <td align="left">Refer to notes below</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">TBD</td>
</texttable> </tr>
<t>NOTE: As per section 9 of <tr>
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/>, <td align="left">max-size</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
<tr>
<td align="left">path</td>
<td align="left">Refer to notes below</td>
<td align="left">M</td>
<td align="left">TBD</td>
</tr>
</tbody>
</table>
<t>NOTE: As per
<xref target="RFC8843" sectionFormat="of" section="9"/>,
there exists no publicly available specification that there exists no publicly available specification that
defines procedures for multiplexing/demultiplexing MRSP flows over defines procedures for multiplexing/demultiplexing MSRP flows over
a single 5-tuple. Once such a specification is available, the multiplex ing a single 5-tuple. Once such a specification is available, the multiplex ing
categories assignments for the attributes in this section could be revi sited.</t> categories assignments for the attributes in this section could be revi sited.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Historical Attributes"> <name>Historical Attributes</name>
<t> <t>
This section specifies analysis for the attributes that are This section specifies analysis for the attributes that are
included for historic usage alone by the <xref included for historic usage alone by the <xref target="IANA" format="d
target="IANA"></xref>. efault"/>.
</t> </t>
<texttable title="5.58 Historical Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>Historical Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>rtpred1&nbsp;</c><c>Historic attributes&nbsp;</c> <th align="left">Level</th>
<c>M</c><c>CAUTION&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>rtpred2&nbsp;</c><c>Historic attributes&nbsp;</c> <tbody>
<c>M</c><c>CAUTION&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">rtpred1</td>
<td align="left">Historic attributes</td>
</texttable> <td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
<tr>
<td align="left">rtpred2</td>
<td align="left">Historic attributes</td>
<td align="left">M</td>
<td align="left">CAUTION</td>
</tr>
</tbody>
</table>
</section> </section>
</section> </section>
<section title="bwtype Attribute Analysis" anchor="SecbwtypeAnalysis" > <section anchor="SecbwtypeAnalysis" numbered="true" toc="default">
<t>This section specifies handling of specific bandwidth attributes <name>bwtype Attribute Analysis</name>
<t>This section specifies handling of specific bandwidth attributes
when used in multiplexing scenarios.</t> when used in multiplexing scenarios.</t>
<section title="RFC4566: SDP"> <section numbered="true" toc="default">
<t><xref target="RFC4566"/> defines SDP that is intended for describing <name>RFC 4566: SDP</name>
<t><xref target="RFC4566" format="default"/> defines SDP that is intende
d for describing
multimedia sessions for the purposes of session announcement, multimedia sessions for the purposes of session announcement,
session invitation, and other forms of multimedia session session invitation, and other forms of multimedia session
initiation.</t> initiation.</t>
<texttable title="6.1 RFC4566 bwtype Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4566 bwtype Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>bwtype:CT&nbsp;</c><c>Not Impacted&nbsp;</c> <th align="left">Level</th>
<c>S</c><c>NORMAL&nbsp;</c> <th align="left">Mux Category</th>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </tr>
</thead>
<c>bwtype:AS&nbsp;</c><c> For the media level usage, <tbody>
the aggregate of individual bandwidth values is considered&nbsp;< <tr>
/c> <td align="left">bwtype:CT</td>
<c>B</c> <td align="left">Not impacted</td>
<c>SUM&nbsp;</c> <td align="left">S</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">NORMAL</td>
</texttable> </tr>
</section> <tr>
<section title="RFC3556: SDP Bandwidth Modifiers for RTCP Bandwidth"> <td align="left">bwtype:AS</td>
<t><xref target="RFC3556"/> defines an extension to <td align="left"> For media-level usage,
the aggregate of individual bandwidth values is considered.</td>
<td align="left">B</td>
<td align="left">SUM</td>
</tr>
</tbody>
</table>
</section>
<section numbered="true" toc="default">
<name>RFC 3556: SDP Bandwidth Modifiers for RTCP Bandwidth</name>
<t><xref target="RFC3556" format="default"/> defines an extension to
SDP to specify two additional modifiers for the bandwidth attribute. The se SDP to specify two additional modifiers for the bandwidth attribute. The se
modifiers may be used to specify the bandwidth allowed for modifiers may be used to specify the bandwidth allowed for
RTCP packets in a RTP session.</t> RTCP packets in an RTP session.</t>
<texttable title="6.2 RFC3556 bwtype Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 3556 bwtype Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>bwtype:RS&nbsp;</c><c>Session level usage represents <th align="left">Level</th>
session aggregate and media level usage indicates SUM of the <th align="left">Mux Category</th>
individual values while multiplexing&nbsp;</c> </tr>
<c>B</c><c>SUM</c> </thead>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tbody>
<tr>
<c>bwtype:RR&nbsp;</c><c>Session level usage represents <td align="left">bwtype:RS</td>
session aggregate and media level usage indicates SUM of the <td align="left">Session-level usage represents
individual values while multiplexing&nbsp;</c> session aggregate, and media-level usage indicates SUM of the
<c>B</c><c>SUM&nbsp;</c> individual values while multiplexing.</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">B</td>
<td align="left">SUM</td>
</texttable> </tr>
</section> <tr>
<section title="RFC3890: Bandwidth Modifier for SDP"> <td align="left">bwtype:RR</td>
<t><xref target="RFC3890"/> defines SDP Transport Independent Application <td align="left">Session-level usage represents
session aggregate, and media-level usage indicates SUM of the
individual values while multiplexing.</td>
<td align="left">B</td>
<td align="left">SUM</td>
</tr>
</tbody>
</table>
</section>
<section numbered="true" toc="default">
<name>RFC 3890: Bandwidth Modifier for SDP</name>
<t><xref target="RFC3890" format="default"/> defines SDP Transport Indep
endent Application
Specific Maximum (TIAS) bandwidth modifier that does not Specific Maximum (TIAS) bandwidth modifier that does not
include transport overhead; instead an additional packet rate include transport overhead; instead, an additional packet-rate
attribute is defined. The transport independent bit-rate attribute is defined. The transport-independent bitrate
value together with the maximum packet rate can then be used value together with the maximum packet rate can then be used
to calculate the real bit-rate over the transport actually to calculate the real bitrate over the transport actually
used.</t> used.</t>
<texttable title="6.3 RFC3890 bwtype Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 3890 bwtype Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>bwtype:TIAS&nbsp;</c><c>The usage of TIAS is not <th align="left">Level</th>
defined under Offer/Answer usage.&nbsp;</c> <th align="left">Mux Category</th>
<c>B</c><c>SPECIAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<c>maxprate&nbsp;</c><c>The usage of TIAS and maxprate <tbody>
is not well defined under multiplexing&nbsp;</c> <tr>
<c>B</c><c>SPECIAL&nbsp;</c> <td align="left">bwtype:TIAS</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">The usage of TIAS is not
defined under offer/answer usage.</td>
</texttable> <td align="left">B</td>
<t>NOTE: The intention of TIAS is that the media <td align="left">SPECIAL</td>
level bit-rate is multiplied with the known per-packet overhead </tr>
<tr>
<td align="left">maxprate</td>
<td align="left">The usage of TIAS and maxprate
is not well defined under multiplexing.</td>
<td align="left">B</td>
<td align="left">SPECIAL</td>
</tr>
</tbody>
</table>
<t>NOTE: The intention of TIAS is that the media-level bitrate is
multiplied with the known per-packet overhead
for the selected transport and the maxprate value to determine for the selected transport and the maxprate value to determine
the worst case bit-rate from the transport to more accurately the worst-case bitrate from the transport to more accurately
capture the required usage. Summing TIAS values independently capture the required usage. Summing TIAS values independently
across "m=" lines and multiplying the computed sum with maxprate across "m=" lines and multiplying the computed sum with maxprate
and the per-packet overhead would inflate the value 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.</t> individual values is a more appropriate usage.</t>
</section> </section>
</section> </section>
<section title="rtcp-fb Attribute Analysis" anchor="SecrtcpfbAnalysis"> <section anchor="SecrtcpfbAnalysis" numbered="true" toc="default">
<t> <name>rtcp-fb Attribute Analysis</name>
<t>
This section analyzes rtcp-fb SDP attributes. This section analyzes rtcp-fb SDP attributes.
</t> </t>
<section numbered="true" toc="default">
<section title="RFC4585: RTP/AVPF"> <name>RFC 4585: RTP/AVPF</name>
<t><xref target="RFC4585"/> defines an extension to <t><xref target="RFC4585" format="default"/> defines an extension to
the Audio-visual Profile (AVP) that enables receivers to the Audio-Visual Profile (AVP) that enables receivers to
provide, statistically, more immediate feedback to the provide, statistically, more immediate feedback to the
senders and thus allows for short-term adaptation and senders; it thus allows for short-term adaptation and implementation of
efficient feedback-based repair mechanisms to be implemented.</t> efficient feedback-based repair mechanisms.</t>
<texttable title="7.1 RFC4585 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 4585 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ack rpsi&nbsp;</c><c>The attribute value MUST be same <th align="left">Level</th>
for a given codec configuration</c> <th align="left">Mux Category</th>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>ack app&nbsp;</c> <tr>
<c>Feedback parameters MUST be handled in the app specific <td align="left">ack rpsi</td>
way when multiplexed</c> <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
<c>M</c><c>SPECIAL&nbsp;</c> me
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> for a given codec configuration.</td>
<td align="left">M</td>
<c>nack&nbsp;</c><c>The attribute value MUST be same <td align="left">IDENTICAL-PER-PT</td>
for a given codec configuration</c> </tr>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> <tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">ack app</td>
<td align="left">Feedback parameters <bcp14>MUST</bcp14> be handle
<c>nack pli&nbsp;</c><c>The attribute value MUST be same d in the app-specific
for a given codec configuration</c> way when multiplexed.</td>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">SPECIAL</td>
</tr>
<c>nack sli&nbsp;</c><c>The attribute value MUST be same <tr>
for a given codec configuration</c> <td align="left">nack</td>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> me
for a given codec configuration.</td>
<c>nack rpsi&nbsp;</c><c>The attribute value MUST be same <td align="left">M</td>
for a given codec configuration </c> <td align="left">IDENTICAL-PER-PT</td>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">nack pli</td>
<c>nack app&nbsp;</c> <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
<c>Feedback parameters MUST be handled in the app specific me
way when multiplexed</c> for a given codec configuration.</td>
<c>M</c><c>SPECIAL&nbsp;</c> <td align="left">M</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">IDENTICAL-PER-PT</td>
</tr>
<c>trr-int&nbsp;</c><c>The attribute value MUST be same <tr>
for a given codec configuration</c> <td align="left">nack sli</td>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> me
</texttable> for a given codec configuration.</td>
</section> <td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
<section title="RFC5104: Codec Control Messages in AVPF"> </tr>
<t><xref target="RFC5104"/> specifies a few <tr>
<td align="left">nack rpsi</td>
<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
<tr>
<td align="left">nack app</td>
<td align="left">Feedback parameters <bcp14>MUST</bcp14> be handle
d in the app specific
way when multiplexed.</td>
<td align="left">M</td>
<td align="left">SPECIAL</td>
</tr>
<tr>
<td align="left">trr-int</td>
<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
</tbody>
</table>
</section>
<section numbered="true" toc="default">
<name>RFC 5104: Codec Control Messages in AVPF</name>
<t><xref target="RFC5104" format="default"/> specifies a few
extensions to the messages defined in the Audio-Visual extensions to the messages defined in the Audio-Visual
Profile with Feedback (AVPF). They are helpful primarily in Profile with Feedback (AVPF). They are helpful primarily in
conversational multimedia scenarios where centralized conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are multipoint functionalities are in use. However, some are
also usable in smaller multicast environments and also usable in smaller multicast environments and
point-to-point calls.</t> point-to-point calls.</t>
<texttable title="7.2 RFC5104 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5104 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ccm&nbsp;</c><c>The attribute value MUST be same <th align="left">Level</th>
for a given codec configuration</c> <th align="left">Mux Category</th>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
</texttable> <tbody>
<tr>
</section> <td align="left">ccm</td>
<section title="RFC6285: Unicast-Based Rapid Acquisition of Multicast RTP S <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
essions (RAMS)"> me
<t><xref target="RFC6285"/> describes a method for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
</tbody>
</table>
</section>
<section numbered="true" toc="default">
<name>RFC 6285: Unicast-Based Rapid Acquisition of Multicast RTP
Sessions (RAMS)</name>
<t><xref target="RFC6285" format="default"/> describes a method of
using the existing RTP and RTCP using the existing RTP and RTCP
machinery that reduces the acquisition delay. In this machinery that reduces the acquisition delay. In this
method, an auxiliary unicast RTP session carrying the method, an auxiliary unicast RTP session carrying the
Reference Information to the receiver precedes or Reference Information to the receiver precedes or
accompanies the multicast stream. This unicast RTP flow can accompanies the multicast stream. This unicast RTP flow can
be transmitted at a faster than natural bitrate to further be transmitted at a faster-than-natural bitrate to further
accelerate the acquisition. The motivating use case for accelerate the acquisition. The motivating use case for
this capability is multicast applications that carry this capability is multicast applications that carry
real-time compressed audio and video.</t> real-time compressed audio and video.</t>
<texttable title="7.3 RFC6285 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6285 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>nack rai&nbsp;</c><c>The attribute value MUST be same <th align="left">Level</th>
for a given codec configuration&nbsp;</c> <th align="left">Mux Category</th>
<c>M&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
</texttable> <tr>
</section> <td align="left">nack rai</td>
<section title="RFC6679: ECN for RTP over UDP/IP"> <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
<t><xref target="RFC6679"/> specifies how Explicit me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
</tbody>
</table>
</section>
<section numbered="true" toc="default">
<name>RFC 6679: ECN for RTP over UDP/IP</name>
<t><xref target="RFC6679" format="default"/> specifies how Explicit
Congestion Notification (ECN) can be used with the RTP running Congestion Notification (ECN) can be used with the RTP running
over UDP, using the RTCP as a feedback mechanism. It defines over UDP, using the RTCP as a feedback mechanism. It defines
a new RTCP Extended Report (XR) block for periodic ECN a new RTCP Extended Report (XR) block for periodic ECN
feedback, a new RTCP transport feedback message for timely feedback, a new RTCP transport feedback message for timely
reporting of congestion events, and a STUN extension used in the optiona l reporting of congestion events, and a STUN extension used in the optiona l
initialization method using ICE.</t> initialization method using ICE.</t>
<texttable title="7.4 RFC6679 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6679 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ecn-capable-rtp&nbsp;</c><c>ECN markup are enabled at the <th align="left">Level</th>
RTP session level&nbsp;</c> <th align="left">Mux Category</th>
<c>M&nbsp;</c><c>IDENTICAL&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<c>nack ecn&nbsp;</c><c>This attribute enables ECN at the RTP <tbody>
session level&nbsp;</c> <tr>
<c>M&nbsp;</c><c>IDENTICAL&nbsp;</c> <td align="left">ecn-capable-rtp</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">ECN markup is enabled at the
</texttable> RTP session level.</td>
<td align="left">M</td>
</section> <td align="left">IDENTICAL</td>
<section title="RFC6642: Third-Party Loss Report"> </tr>
<t>In a large RTP session using the RTCP <tr>
feedback mechanism defined in <xref target="RFC4585"></xref>, <td align="left">nack ecn</td>
<td align="left">This attribute enables ECN at the RTP
session level.</td>
<td align="left">M</td>
<td align="left">IDENTICAL</td>
</tr>
</tbody>
</table>
</section>
<section numbered="true" toc="default">
<name>RFC 6642: Third-Party Loss Report</name>
<t>In a large RTP session using the RTCP
feedback mechanism defined in <xref target="RFC4585" format="default"/>,
a feedback target may experience transient overload if some event a feedback target may experience transient overload if some event
causes a large number of receivers to send feedback at once. causes a large number of receivers to send feedback at once.
This overload is usually avoided by ensuring that feedback 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
feedback implosion. <xref target="RFC6642"></xref> feedback implosion. <xref target="RFC6642" format="default"/> discusses
memo discusses these cases and defines a new RTCP Third-Party these
cases and defines a new RTCP Third-Party
Loss Report that can be used to inform receivers that the Loss Report that can be used to inform receivers that the
feedback target is aware of some loss event, allowing them to feedback target is aware of some loss event, allowing them to
suppress feedback. Associated SDP signaling is also defined.</t> suppress feedback. Associated SDP signaling is also defined.</t>
<texttable title="7.5 RFC6642 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 6642 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>nack tllei&nbsp;</c><c>The attribute value MUST be same <th align="left">Level</th>
for a given codec configuration&nbsp;</c> <th align="left">Mux Category</th>
<c>M&nbsp;</c> </tr>
<c>IDENTICAL-PER-PT&nbsp;</c> </thead>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tbody>
<tr>
<c>nack pslei&nbsp;</c><c>The attribute value MUST be same <td align="left">nack tllei</td>
for a given codec configuration&nbsp;</c> <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
<c>M&nbsp;</c> me
<c>IDENTICAL-PER-PT&nbsp;</c> for a given codec configuration.</td>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</texttable> </tr>
</section> <tr>
<section title="RFC5104: Codec Control Messages in AVPF"> <td align="left">nack pslei</td>
<t><xref target="RFC5104"/> specifies a few <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
me
for a given codec configuration.</td>
<td align="left">M</td>
<td align="left">IDENTICAL-PER-PT</td>
</tr>
</tbody>
</table>
</section>
<section numbered="true" toc="default">
<name>RFC 5104: Codec Control Messages in AVPF</name>
<t><xref target="RFC5104" format="default"/> specifies a few
extensions to the messages defined in the Audio-Visual extensions to the messages defined in the Audio-Visual
Profile with Feedback (AVPF). They are helpful primarily in Profile with Feedback (AVPF). They are helpful primarily in
conversational multimedia scenarios where centralized conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are multipoint functionalities are in use. However, some are
also usable in smaller multicast environments and also usable in smaller multicast environments and
point-to-point calls.</t> point-to-point calls.</t>
<texttable title="7.6 RFC5104 Attribute Analysis"> <table align="center">
<ttcol align='left'>Name</ttcol> <name>RFC 5104 Attribute Analysis</name>
<ttcol align='left'>Notes</ttcol> <thead>
<ttcol align='left'>Level</ttcol> <tr>
<ttcol align='left'>Mux Category</ttcol> <th align="left">Name</th>
<th align="left">Notes</th>
<c>ccm fir&nbsp;</c><c>The attribute value MUST be same <th align="left">Level</th>
for a given codec configuration</c> <th align="left">Mux Category</th>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> </thead>
<tbody>
<c>ccm tmmbr&nbsp;</c><c>The attribute value MUST be same <tr>
for a given codec configuration</c> <td align="left">ccm fir</td>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> <td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> me
for a given codec configuration.</td>
<c>ccm tstr&nbsp;</c><c>The attribute value MUST be same <td align="left">M</td>
for a given codec configuration</c> <td align="left">IDENTICAL-PER-PT</td>
<c>M</c><c>IDENTICAL-PER-PT&nbsp;</c> </tr>
<c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c> <tr>
<td align="left">ccm tmmbr</td>