Diff: rfc8859xml2.original.xml

	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="January" year="2021"/>
	<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 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> </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> </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> </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> </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> </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> </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> </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> </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> </t>
	<t>In the example below, "a=crypto" attribute is defined for both
	the audio and the video "m=" lines. The video media line's a=crypto
	attribute is chosen since its mid value (bar) appears first in
	the a=group:BUNDLE line. This is due to BUNDLE grouping semantic
	<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>
	which mandates the values from "m=" line corresponding to the mid
	appearing first on the a=group:BUNDLE line to be considered for
	setting up the RTP Transport.</t>
	<figure>
	<artwork align="left" alt="" height="" name="" type="" width=""
	xml:space="preserve"><![CDATA[


		<t>In the example below, the "a=crypto" attribute is defined for both
		the audio and video "m=" lines. The video media line's "a=crypto"
		attribute is chosen since its MID value (bar) appears first in
		the "a=group:BUNDLE" line. This is due to the BUNDLE grouping semantic
		<xref target="RFC8843" format="default"/>, which mandates that the valu
		es from
		the "m=" line corresponding to the mid
		appearing first on the "a=group:BUNDLE" line be considered for
		setting up the RTP transport.</t>

		<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> </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> </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> </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> </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> </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 </c><c>Not impacted </c><c>B </c>
	<c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>sendonly </c><c>Not impacted </c><c>B </c>
	<c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>recvonly </c><c>Not impacted </c><c>B </c>
	<c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>inactive </c><c>Not impacted </c><c>B </c>
	<c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>cat </c><c>Not impacted </c><c>S </c>
	<c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>ptime </c><c> The attribute value MUST be same
	for a given codec configuration </c>
	<c>M </c><c>IDENTICAL-PER-PT</c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>maxptime </c><c>The attribute value MUST be same
	for a given codec configuration </c>
	<c>M </c><c>IDENTICAL-PER-PT</c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>orient </c><c>Not Impacted
	</c><c>M </c><c>NORMAL</c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>framerate </c><c>The attribute value MUST be same
	for a given codec configuration </c><c>M </c>
	<c>IDENTICAL-PER-PT </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>quality </c><c>Not Impacted
	</c><c>M </c><c>NORMAL</c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>rtpmap </c><c>The attribute value MUST be same
	for a given codec configuration </c><c>M </c>
	<c>IDENTICAL-PER-PT</c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>fmtp </c><c>The attribute value MUST be same
	for a given codec configuration </c><c>M </c>
	<c>IDENTICAL-PER-PT</c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>keywds </c><c>Not impacted </c><c>S </c>
	<c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>type </c><c>Not Impacted
	</c><c>S </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>type:broadcast </c><c>Not Impacted
	</c><c>S </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>type:H332 </c><c>Not Impacted
	</c><c>S </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>type:meeting </c><c>Not Impacted
	</c><c>S </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>type:moderated </c><c>Not Impacted
	</c><c>S </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>type:test </c><c>Not Impacted
	</c><c>S </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>tool </c><c>Not Impacted
	</c><c>S </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>charset </c><c>Not Impacted
	</c><c>S </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>sdplang </c><c>Not Impacted
	</c><c>B </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>lang </c><c>Not Impacted
	</c><c>B </c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>RTP and RTCP Multiplexing affects the	<th align="left">Level</th>
	entire RTP session </c>	<th align="left">Mux Category</th>
	<c>M </c><c>IDENTICAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Refer to notes below </c>	<th align="left">Level</th>
	<c>M </c><c>CAUTION </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>conf </c><c>Refer to notes below </c>	<tbody>
	<c>M </c><c>CAUTION </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">des</td>
		<td align="left">Refer to notes below</td>
	<c>curr </c><c>Refer to notes below </c>	<td align="left">M</td>
	<c>M </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>	<th align="left">Level</th>
	<c> </c><c> </c><c> </c><c> </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 </c>	<th align="left">Level</th>
	<c> Refer to <xref target="SecqostokenAnalysis"/>  </c>	<th align="left">Mux Category</th>
	<c>B</c><c>TRANSPORT </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>qos-mech-recv </c>	<tr>
	<c>Refer to <xref target="SecqostokenAnalysis"/>  </c>	<td align="left">qos-mech-send</td>
	<c>B</c><c>TRANSPORT </c>	<td align="left"> Refer to <xref target="SecqostokenAnalysis" form
	<c> </c><c> </c><c> </c><c> </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 </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 </c><c>TRANSPORT </c>	<tbody>
	<c> </c><c> </c><c> </c><c> </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 </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 </c> <c>M </c><c>CAUTION </c><c> </c>	5-tuple.</td>
	<c> </c><c> </c><c> </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 </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 </c> <c>M </c>	encapsulation/decapsulation and the RTP.</td>
	<c>CAUTION </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Reduced size RTCP affects the	<th align="left">Level</th>
	entire RTP session </c>	<th align="left">Mux Category</th>
	<c>M </c><c>IDENTICAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c><c>M </c>	<th align="left">Level</th>
	<c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>channel </c><c>Not Impacted </c><c>M </c>	<tbody>
	<c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">resource</td>
		<td align="left">Not impacted</td>
	<c>cmid </c><c>Not Impacted </c><c>M </c>	<td align="left">M</td>
	<c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>S</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>ice-options </c><c>Not Impacted </c>	<tbody>
	<c>S</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">ice-lite</td>
		<td align="left">Not impacted</td>
	<c>ice-mismatch </c><c>Not Impacted </c>	<td align="left">S</td>
	<c>S</c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>ice-pwd </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 </c>	underlying transport flow.</td>
	<c>B</c><c>TRANSPORT </c>	<td align="left">B</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">TRANSPORT</td>
		</tr>
	<c>ice-ufrag </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 </c>	underlying transport flow.</td>
	<c>B</c><c>TRANSPORT </c>	<td align="left">B</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">TRANSPORT</td>
		</tr>
	<c>candidate </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 </c><c>M</c><c>TRANSPORT </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">TRANSPORT</td>
		</tr>
	<c>remote-candidates </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 </c><c>M</c><c>TRANSPORT </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Refer to the document defining the	<th align="left">Level</th>
	specific RTP Extension </c> <c>B</c><c>SPECIAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </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. </c>	setting up the underlying transport flow.</td>
	<c>M</c><c>TRANSPORT </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Refer to Notes	<th align="left">Level</th>
	below </c><c>M</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>ssrc-group </c>	<tbody>
	<c>Refer to <xref target="sec-ssrc-group"></xref>	<tr>
	for specific analysis of the grouping semantics </c><c>M</c>	<td align="left">ssrc</td>
	<c>NORMAL </c>	<td align="left">Refer to notes
	<c> </c><c> </c><c> </c><c> </c>	below.</td>
		<td align="left">M</td>
	<c>cname </c> <c>Not Impacted </c><c>SR</c>	<td align="left">NORMAL</td>
	<c>NORMAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">ssrc-group</td>
	<c>previous-ssrc </c>	<td align="left">Refer to <xref target="sec-ssrc-group" format="de
	<c>Refer to notes below </c><c>SR</c><c>NORMAL </c>	fault"/>
	<c> </c><c> </c><c> </c><c> </c>	for specific analysis of the grouping semantics.</td>
		<td align="left">M</td>
	<c>fmtp </c><c>The attribute value MUST be same for a	<td align="left">NORMAL</td>
	given codec configuration </c><c>SR</c>	</tr>
	<c>IDENTICAL-PER-PT </c>	<tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>B</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>mediaclk </c>	<tbody>
	<c>Not Impacted </c><c>B</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">ts-refclk</td>
		<td align="left">Not impacted</td>
	<c>ts-refclk:ntp </c><c>Not Impacted </c>	<td align="left">B</td>
	<c>B</c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>ts-refclk:ptp </c><c>Not Impacted </c>	<td align="left">mediaclk</td>
	<c>B</c><c>NORMAL </c>	<td align="left">Not impacted</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">B</td>
		<td align="left">NORMAL</td>
	<c>ts-refclk:gps </c><c>Not Impacted </c>	</tr>
	<c>B</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">ts-refclk:ntp</td>
		<td align="left">Not impacted</td>
	<c>ts-refclk:gal </c><c>Not Impacted </c>	<td align="left">B</td>
	<c>B</c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>ts-refclk:glonass </c><c>Not Impacted </c>	<td align="left">ts-refclk:ptp</td>
	<c>B</c><c>NORMAL </c>	<td align="left">Not impacted</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">B</td>
		<td align="left">NORMAL</td>
	<c>ts-refclk:local </c><c>Not Impacted </c>	</tr>
	<c>B</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">ts-refclk:gps</td>
		<td align="left">Not impacted</td>
	<c>ts-refclk:private </c><c>Not Impacted </c>	<td align="left">B</td>
	<c>B</c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>mediaclk:sender </c>	<td align="left">ts-refclk:gal</td>
	<c>Not Impacted </c><c>B</c><c>NORMAL </c>	<td align="left">Not impacted</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">B</td>
		<td align="left">NORMAL</td>
	<c>mediaclk:direct </c>	</tr>
	<c>Not Impacted </c><c>B</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">ts-refclk:glonass</td>
		<td align="left">Not impacted</td>
	<c>mediaclk:IEEE1722 </c>	<td align="left">B</td>
	<c>Not Impacted </c><c>B</c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>The attribute value MUST be same	<th align="left">Level</th>
	for a given codec configuration </c><c>M </c>	<th align="left">Mux Category</th>
	<c>IDENTICAL-PER-PT </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c><c>B </c>	<th align="left">Level</th>
	<c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c><c>B </c>	<th align="left">Level</th>
	<c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not recommended	<th align="left">Level</th>
	</c><c>M </c><c>CAUTION </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>M </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Refer to the document defining specific	<th align="left">Level</th>
	FEC Scheme </c><c>M </c>	<th align="left">Mux Category</th>
	<c>SPECIAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>fec-repair-flow </c><c>Refer to the document defining specific	<tr>
	FEC Scheme </c><c>M </c>	<td align="left">fec-source-flow</td>
	<c>SPECIAL </c>	<td align="left">Refer to the document defining specific
	<c> </c><c> </c><c> </c><c> </c>	FEC scheme.</td>
		<td align="left">M</td>
	<c>repair-window </c><c>Refer to the document defining specific	<td align="left">SPECIAL</td>
	FEC Scheme </c><c>M </c>	</tr>
	<c>SPECIAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not	<th align="left">Level</th>
	Impacted </c><c>M </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>B</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>cdsc </c><c>Not	<tbody>
	Impacted. </c><c>B</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">sqn</td>
		<td align="left">Not impacted</td>
	<c>cpar </c><c>Refer to <xref target="sec-encap"/> </c>	<td align="left">B</td>
	<c>B</c><c>INHERIT </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>cparmin </c><c>Refer to notes below  </c>	<td align="left">cdsc</td>
	<c>B</c><c>SPECIAL </c>	<td align="left">Not
	<c> </c><c> </c><c> </c><c> </c>	impacted</td>
		<td align="left">B</td>
	<c>cparmax </c><c>Refer to notes below </c>	<td align="left">NORMAL</td>
	<c>B</c><c>SPECIAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not recommended, if port mapping is	<th align="left">Level</th>
	required by the application </c><c>M </c>	<th align="left">Mux Category</th>
	<c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Refer to notes below </c><c>M </c>	<th align="left">Level</th>
	<c>TBD </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </c>
	<c>Refer to notes below </c>
	<c>M </c><c>TBD </c><c> </c><c> </c>
	<c> </c><c> </c>

	<c>confid </c><c>Not Impacted </c><c>M </c>
	<c>NORMAL </c><c> </c><c> </c><c> </c><c> </c
	>


	<c>userid </c><c>Not	<table align="center">
	Impacted </c><c>M </c><c>NORMAL </c>	<name>RFC 4583 Attribute Analysis</name>
	<c> </c><c> </c><c> </c><c> </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 </c>	<tr>
	<c>Not Impacted </c>	<td align="left">confid</td>
	<c>M </c><c>NORMAL </c><c> </c><c> </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </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 </c><c>Refer to notes below </c>	<th align="left">Level</th>
	<c>M</c><c>TBD </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>file-transfer-id </c><c>Refer to notes below </c>	<tbody>
	<c>M</c><c>TBD </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">file-selector</td>
		<td align="left">Refer to notes below</td>
	<c>file-disposition </c><c>Refer to notes below </c>	<td align="left">M</td>
	<c>M</c><c>TBD </c>	<td align="left">TBD</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>file-date </c><c>Refer to notes below </c>	<td align="left">file-transfer-id</td>
	<c>M</c><c>TBD </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">TBD</td>
	<c>file-icon </c><c>Refer to notes below </c>	</tr>
	<c>M</c><c>TBD </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">file-disposition</td>
		<td align="left">Refer to notes below</td>
	<c>file-range </c><c>Refer to notes below </c>	<td align="left">M</td>
	<c>M</c><c>TBD </c>	<td align="left">TBD</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>The attribute value MUST be	<th align="left">Level</th>
	same for a given codec configuration </c>	<th align="left">Mux Category</th>
	<c>M</c><c>IDENTICAL-PER-PT </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>loopback rtp-media-loopback </c><c>The attribute value MUST be	<tr>
	same for a given codec configuration  </c>	<td align="left">loopback rtp-pkt-loopback</td>
	<c>M</c><c>IDENTICAL-PER-PT </c>	<td align="left">The attribute value <bcp14>MUST</bcp14> be
	<c> </c><c> </c><c> </c><c> </c>	same for a given codec configuration.</td>
		<td align="left">M</td>
	<c>loopback-source </c><c>Not Impacted </c><c>M</c>	<td align="left">IDENTICAL-PER-PT</td>
	<c>NORMAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">loopback rtp-media-loopback</td>
	<c>loopback-mirror </c><c>Not Impacted </c><c>M</c>	<td align="left">The attribute value <bcp14>MUST</bcp14> be
	<c>NORMAL </c>	same for a given codec configuration.</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>The attribute MUST be reported	<th align="left">Level</th>
	across all "m=" lines	<th align="left">Mux Category</th>
	multiplexed </c><c>M</c><c>IDENTICAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c><c>B</c><c>NORMAL </	<th align="left">Level</th>
	c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </c>	<th align="left">Level</th>
	<c>Refer to <xref target="sec-encap"/>  </c>	<th align="left">Mux Category</th>
	<c>M</c><c>SPECIAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>acfg </c>	<tr>
	<c>Refer to <xref target="sec-encap"/> </c>	<td align="left">pcfg</td>
	<c>M</c><c>SPECIAL </c>	<td align="left">Refer to <xref target="sec-encap" format="default
	<c> </c><c> </c><c> </c><c> </c>	"/></td>
		<td align="left">M</td>
	<c>csup </c><c>Not Impacted </c><c>B</c>	<td align="left">SPECIAL</td>
	<c>NORMAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">acfg</td>
	<c>creq </c><c>Not Impacted </c><c>B</c>	<td align="left">Refer to <xref target="sec-encap" format="default
	<c>NORMAL </c>	"/></td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">SPECIAL</td>
	<c>acap </c>	</tr>
	<c>Refer to <xref target="sec-encap"/> </c>	<tr>
	<c>B</c><c>INHERIT </c>	<td align="left">csup</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Not impacted </td>
		<td align="left">B</td>
	<c>tcap </c>	<td align="left">NORMAL</td>
	<c>Refer to <xref target="sec-encap"/> </c>	</tr>
	<c>B</c><c>INHERIT </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">creq</td>
		<td align="left">Not impacted</td>
	<c>cap-v0 </c><c>Not Impacted </c>	<td align="left">B</td>
	<c>B</c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </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 </c>	<th align="left">Level</th>
	<c>Refer to <xref target="sec-encap"/> </c>	<th align="left">Mux Category</th>
	<c>B</c><c>IDENTICAL-PER-PT </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>omcap </c><c>Not Impacted </c>	<tr>
	<c>B</c><c>NORMAL </c>	<td align="left">rmcap</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Refer to <xref target="sec-encap" format="default
		"/></td>
	<c>mfcap </c>	<td align="left">B</td>
	<c>Refer to <xref target="sec-encap"/> </c>	<td align="left">IDENTICAL-PER-PT</td>
	<c>B</c><c>IDENTICAL-PER-PT </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">omcap</td>
	<c>mscap </c>	<td align="left">Not impacted</td>
	<c>Refer to <xref target="sec-encap"/> </c>	<td align="left">B</td>
	<c>B</c><c>INHERIT </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>lcfg </c>	<td align="left">mfcap</td>
	<c>Refer to <xref target="sec-encap"/> </c>	<td align="left">Refer to <xref target="sec-encap" format="default
	<c>B</c><c>SPECIAL </c>	"/></td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">B</td>
		<td align="left">IDENTICAL-PER-PT</td>
	<c>sescap </c>	</tr>
	<c>Refer to notes below </c>	<tr>
	<c>S</c><c>CAUTION </c>	<td align="left">mscap</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Refer to <xref target="sec-encap" format="default
		"/></td>
	<c>med-v0 </c><c>Not Impacted </c>	<td align="left">B</td>
	<c>S</c><c>NORMAL </c>	<td align="left">INHERIT</td>
	<c> </c><c> </c><c> </c><c> </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 </c>	<th align="left">Level</th>
	<c>Inherit the category SUM as	<th align="left">Mux Category</th>
	applicable to b= attribute </c>	</tr>
	<c>B</c><c>INHERIT </c>	</thead>
	<c> </c><c> </c><c> </c><c> </c>	<tbody>
		<tr>
	<c>bcap-v0 </c><c>Not Impacted </c>	<td align="left">bcap</td>
	<c>B</c><c>NORMAL </c>	<td align="left">Inherit the category SUM as
	<c> </c><c> </c><c> </c><c> </c>	applicable to the "b=" attribute</td>
		<td align="left">B</td>
	<c>ccap </c><c>The connection address type	<td align="left">INHERIT</td>
	MUST be identical across all the multiplexed	</tr>
	"m=" lines </c>	<tr>
	<c>B</c><c>IDENTICAL </c>	<td align="left">bcap-v0</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Not impacted</td>
		<td align="left">B</td>
	<c>ccap-v0 </c><c>Not Impacted </c>	<td align="left">NORMAL</td>
	<c>B</c><c>NORMAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">ccap</td>
	<c>icap </c><c>Not Impacted </c>	<td align="left">The connection address type
	<c>B</c><c>NORMAL </c>	<bcp14>MUST</bcp14> be identical across all the multiplexed
	<c> </c><c> </c><c> </c><c> </c>	"m=" lines.</td>
		<td align="left">B</td>
	<c>icap-v0 </c><c>Not Impacted </c>	<td align="left">IDENTICAL</td>
	<c>B</c><c>NORMAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Key management protocol MUST be	<th align="left">Level</th>
	identical across all the "m=" lines </c><c>B</c>	<th align="left">Mux Category</th>
	<c>IDENTICAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>mikey </c><c>Key management protocol MUST be	<tr>
	identical across all the "m=" lines </c><c>B</c>	<td align="left">key-mgmt</td>
	<c>IDENTICAL </c>	<td align="left">Key management protocol <bcp14>MUST</bcp14> be
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	setting up the underlying transport flow.</td>
	<c>B</c><c>TRANSPORT </c>	<td align="left">B</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>The attribute MUST be repeated	<th align="left">Mux Category</th>
	across all "m=" lines	</tr>
	multiplexed </c><c>B</c><c>IDENTICAL </c>	</thead>
	<c> </c><c> </c><c> </c><c> </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 </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 </c><c>B</c><c>IDENTICAL </c>	"m=" lines.</td>
	<c> </c><c> </c><c> </c><c> </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 </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 </c><c>M</c>	the underlying transport flow.</td>
	<c>TRANSPORT </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </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 </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. </c>	</tr>
	<c>B</c><c>TRANSPORT </c>	</thead>
	<c> </c><c> </c><c> </c><c> </c>	<tbody>
		<tr>
	<c>connection </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. </	e that corresponds to the "m="
	c>	line chosen for setting up the underlying transport flow.</td>
	<c>B</c><c>TRANSPORT </c>	<td align="left">B</td>
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	</tr>
	<c>M</c><c>TRANSPORT </c>	</thead>
	<c> </c><c> </c><c> </c><c> </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 </c>	<th align="left">Level</th>
	<c>Refer to notes below </c>	<th align="left">Mux Category</th>
	<c>M</c><c>TBD </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>cs-correlation:uuie </c>	<tr>
	<c>Refer to notes below </c>	<td align="left">cs-correlation:callerid</td>
	<c>M </c><c>TBD </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">TBD</td>
	<c>cs-correlation:dtmf </c>	</tr>
	<c>Refer to notes below </c>	<tr>
	<c>M</c><c>TBD </c>	<td align="left">cs-correlation:uuie</td>
	<c> </c><c> </c><c> </c><c> </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 </c>	<t>NOTE: <xref target="RFC7195" format="default"/> defines SDP attribute
	<c>Refer to notes below </c>	s for
	<c>M</c><c>TBD </c>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>M</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>S</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>stkmstream </c><c>Not Impacted </c>	<tbody>
	<c>B</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">bcastversion</td>
		<td align="left">Not impacted</td>
	<c>SRTPAuthentication </c><c>Needs further analysis </c>	<td align="left">S</td>
	<c>M</c><c>TBD </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>SRTPROCTxRate </c><c>Needs further analysis </c>	<td align="left">stkmstream</td>
	<c>M</c><c>TBD </c>	<td align="left">Not impacted</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Unlikely to use IKE in the context of	<th align="left">Level</th>
	multiplexing </c><c>B</c><c>CAUTION </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>psk-fingerprint </c><c>Unlikely to use IKE in the context of	<tbody>
	multiplexing </c><c>B</c><c>CAUTION </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">ike-setup</td>
		<td align="left">Unlikely to use IKE in the context of
	<c>ike-esp </c><c>Unlikely to use IKE in the context of	multiplexing</td>
	multiplexing </c><c>B</c><c>CAUTION </c>	<td align="left">B</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">CAUTION</td>
		</tr>
	<c>ike-esp-udpencap </c><c>Unlikely to use IKE in the context of	<tr>
	multiplexing </c><c>B</c><c>CAUTION </c>	<td align="left">psk-fingerprint</td>
	<c> </c><c> </c><c> </c><c> </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">	<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 </c><c>RTSP is not supported for RTP Stream	<th align="left">Level</th>
	multiplexing </c><c>B</c><c>CAUTION </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>range </c><c>RTSP is not supported for RTP Stream	<tbody>
	multiplexing </c><c>B</c><c>CAUTION </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">etag</td>
		<td align="left">RFC 2326 is obsolete.</td>
	<c>control </c><c>RTSP is not supported for RTP Stream	<td align="left">B</td>
	multiplexing </c><c>B</c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>mtag </c><c>RTSP is not supported for RTP Stream	<td align="left">range</td>
	multiplexing </c><c>B</c><c>CAUTION </c>	<td align="left">RFC 2326 is obsolete.</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">B</td>
		<td align="left">CAUTION</td>
	</texttable>	</tr>
	<t>NOTE: <xref target="RFC2326"/> defines SDP attributes that are	<tr>
	applicable in the declarative usage of SDP alone. For	<td align="left">control</td>
	purposes of this document, only the Offer/Answer usage of SDP	<td align="left">RFC 2326 is obsolete.</td>
	is considered as mandated by <xref	<td align="left">B</td>
	target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>.</t>	<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">mtag</td>
		<td align="left">RFC 2326 is obsolete.</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 title="RFC6064: SDP and RTSP Extensions for 3GPP">	<section numbered="true" toc="default">
		<name>RFC 7826: Real-Time Streaming Protocol</name>
		<t>The Real-Time Streaming Protocol, or RTSP, is an application-level
		protocol for control over the delivery of data with real-time
		properties. RTSP provides an extensible framework to enable
		controlled, on-demand delivery of real-time data, such as audio
		and video.</t>
		<table align="center">
		<name>RFC 7826 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">range</td>
		<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">control</td>
		<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="RFC7826" 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 numbered="true" toc="default">
		<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 </c>	<th align="left">Level</th>
	<c>Refer to notes below </c>	<th align="left">Mux Category</th>
	<c>M</c><c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>X-initpredecbufperiod </c>	<tr>
	<c>Refer to notes below </c>	<td align="left">X-predecbufsize</td>
	<c>M</c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">CAUTION</td>
	<c>X-initpostdecbufperiod </c>	</tr>
	<c>Refer to notes below </c>	<tr>
	<c>M</c><c>CAUTION </c>	<td align="left">X-initpredecbufperiod</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Refer to notes below</td>
		<td align="left">M</td>
	<c>X-decbyterate</c><c>Refer to notes below </c>	<td align="left">CAUTION</td>
	<c>M</c><c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">X-initpostdecbufperiod</td>
	<c>3gpp-videopostdecbufsize </c>	<td align="left">Refer to notes below</td>
	<c>Refer to notes below </c>	<td align="left">M</td>
	<c>M</c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>framesize</c><c>Refer to notes below </c><c>M</c>	<td align="left">X-decbyterate</td>
	<c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">CAUTION</td>
	<c>3GPP-Integrity-Key </c>	</tr>
	<c>Refer to notes below </c><c>S</c>	<tr>
	<c>CAUTION </c>	<td align="left">3gpp-videopostdecbufsize</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Refer to notes below</td>
		<td align="left">M</td>
	<c>3GPP-SDP-Auth </c>	<td align="left">CAUTION</td>
	<c>Refer to notes below </c><c>S</c>	</tr>
	<c>CAUTION </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">framesize</td>
		<td align="left">Refer to notes below</td>
	<c>3GPP-SRTP-Config </c>	<td align="left">M</td>
	<c>Refer to notes below  </c><c>M</c>	<td align="left">CAUTION</td>
	<c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">3GPP-Integrity-Key</td>
	<c>alt </c>	<td align="left">Refer to notes below</td>
	<c>Refer to notes below </c>	<td align="left">S</td>
	<c>M</c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>alt-default-id </c>	<td align="left">3GPP-SDP-Auth</td>
	<c>Refer to notes below </c>	<td align="left">Refer to notes below</td>
	<c>M</c><c>CAUTION </c>	<td align="left">S</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">CAUTION</td>
		</tr>
	<c>alt-group </c>	<tr>
	<c>Refer to notes below </c><c>S</c>	<td align="left">3GPP-SRTP-Config</td>
	<c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">CAUTION</td>
	<c>3GPP-Adaptation-Support </c>	</tr>
	<c>Refer to notes below  </c><c>M</c>	<tr>
	<c>CAUTION </c>	<td align="left">alt</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Refer to notes below</td>
		<td align="left">M</td>
	<c>3GPP-Asset-Information </c>	<td align="left">CAUTION</td>
	<c>Refer to notes below </c><c>B</c>	</tr>
	<c>CAUTION </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">alt-default-id</td>
		<td align="left">Refer to notes below</td>
	<c>mbms-mode </c>	<td align="left">M</td>
	<c>Refer to notes below </c><c>B</c>	<td align="left">CAUTION</td>
	<c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">alt-group</td>
	<c>mbms-flowid </c>	<td align="left">Refer to notes below</td>
	<c>Refer to notes below </c><c>M</c>	<td align="left">S</td>
	<c>CAUTION </c>	<td align="left">CAUTION</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>mbms-repair </c>	<td align="left">3GPP-Adaptation-Support</td>
	<c>Refer to notes below </c><c>B</c>	<td align="left">Refer to notes below</td>
	<c>CAUTION </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">CAUTION</td>
		</tr>
	<c>3GPP-QoE-Metrics </c>	<tr>
	<c>Refer to notes below </c>	<td align="left">3GPP-Asset-Information</td>
	<c>M</c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">B</td>
		<td align="left">CAUTION</td>
	<c>3GPP-QoE-Metrics:Corruption duration </c>	</tr>
	<c>Refer to notes below </c>	<tr>
	<c>M</c><c>CAUTION </c>	<td align="left">mbms-mode</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Refer to notes below</td>
		<td align="left">B</td>
	<c>3GPP-QoE-Metrics:Rebuffering duration </c>	<td align="left">CAUTION</td>
	<c>Refer to notes below </c>	</tr>
	<c>M</c><c>CAUTION </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">mbms-flowid</td>
		<td align="left">Refer to notes below</td>
	<c>3GPP-QoE-Metrics:Initial buffering duration </c>	<td align="left">M</td>
	<c>Refer to notes below </c>	<td align="left">CAUTION</td>
	<c>M</c><c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">mbms-repair</td>
	<c>3GPP-QoE-Metrics:Successive loss of RTP packets </c>	<td align="left">Refer to notes below</td>
	<c>Refer to notes below </c>	<td align="left">B</td>
	<c>M</c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>3GPP-QoE-Metrics:Frame rate deviation </c>	<td align="left">3GPP-QoE-Metrics</td>
	<c>Refer to notes below </c>	<td align="left">Refer to notes below</td>
	<c>M</c><c>CAUTION </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">CAUTION</td>
		</tr>
	<c>3GPP-QoE-Metrics:Jitter duration </c>	<tr>
	<c>Refer to notes below </c>	<td align="left">3GPP-QoE-Metrics:Corruption duration</td>
	<c>M</c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">CAUTION</td>
	<c>3GPP-QoE-Metrics:Content Switch Time </c>	</tr>
	<c>Refer to notes below </c>	<tr>
	<c>B</c><c>CAUTION </c>	<td align="left">3GPP-QoE-Metrics:Rebuffering duration</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Refer to notes below</td>
		<td align="left">M</td>
	<c>3GPP-QoE-Metrics:Average Codec Bitrate </c>	<td align="left">CAUTION</td>
	<c>Refer to notes below </c>	</tr>
	<c>M</c><c>CAUTION </c>	<tr>
	<c> </c><c> </c><c> </c><c> </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 </c>	<td align="left">M</td>
	<c>Refer to notes below </c>	<td align="left">CAUTION</td>
	<c>M</c><c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">3GPP-QoE-Metrics:Successive loss of RTP packets</
	<c>3GPP-QoE-Metrics:Buffer Status </c>	td>
	<c>Refer to notes below </c>	<td align="left">Refer to notes below</td>
	<c>M</c><c>CAUTION </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Refer to notes below</c>	<th align="left">Level</th>
	<c>B </c><c>CAUTION </c>	<th align="left">Mux Category</th>
	<c>eecid </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	</thead>
	<c>capability </c><c>Refer to notes below</c>	<tbody>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>qosClass </c><c>Refer to notes below</c>	<td align="left">aalType</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>bcob </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>stc </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>upcc </c><c>Refer to notes below</c>	<td align="left">eecid</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>atmQOSparms </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>atmTrfcDesc </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>abrParms </c><c>Refer to notes below</c>	<td align="left">capability</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>abrSetup </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>bearerType </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>lij </c><c>Refer to notes below</c>	<td align="left">qosClass</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>anycast </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>cache </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>bearerSigIE </c><c>Refer to notes below</c>	<td align="left">bcob</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>aalApp </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>cbrRate </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>sbc </c><c>Refer to notes below</c>	<td align="left">stc</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>clkrec </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>fec </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>prtfl </c><c>Refer to notes below</c>	<td align="left">upcc</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>structure </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>cpsSDUsize </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>aal2CPS </c><c>Refer to notes below</c>	<td align="left">atmQOSparms</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>aal2CPSSDUrate </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>aal2sscs3661unassured </c>	</tr>
	<c>Refer to notes below</c>	<tr>
	<c>B </c><c>CAUTION </c>	<td align="left">atmTrfcDesc</td>
	<c>aal2sscs3661assured </c>	<td align="left">Refer to notes below</td>
	<c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>aal2sscs3662 </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>aal5sscop </c><c>Refer to notes below</c>	<td align="left">abrParms</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>atmmap </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>silenceSupp </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>ecan </c><c>Refer to notes below</c>	<td align="left">abrSetup</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>gc </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>profileDesc </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>vsel </c><c>Refer to notes below</c>	<td align="left">bearerType</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>dsel </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>fsel </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>onewaySel </c><c>Refer to notes below</c>	<td align="left">lij</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>codecconfig </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c>isup_usi </c><c>Refer to notes below</c>	</tr>
	<c>B </c><c>CAUTION </c>	<tr>
	<c>uiLayer1_Prot </c><c>Refer to notes below</c>	<td align="left">anycast</td>
	<c>B </c><c>CAUTION </c>	<td align="left">Refer to notes below</td>
	<c>chain </c><c>Refer to notes below</c>	<td align="left">B</td>
	<c>B </c><c>CAUTION </c>	<td align="left">CAUTION</td>
	<c> </c><c> </c><c> </c><c> </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 </c>
	<c>Usage defined for the IP Multimedia Subsystem </c>
	<c>M</c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	<c>3gpp_MaxRecvSDUSize </c>
	<c>Usage defined for the IP Multimedia Subsystem </c>
	<c>M</c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>S</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>bc_service </c><c>Not Impacted </c>	<tbody>
	<c>S</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">PSCid</td>
		<td align="left">Not impacted</td>
	<c>bc_program </c><c>Not Impacted </c>	<td align="left">S</td>
	<c>S</c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>bc_service_package </c><c>Not Impacted </c>	<td align="left">bc_service</td>
	<c>S</c><c>NORMAL </c>	<td align="left">Not impacted</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">S</td>
	</texttable>	<td align="left">NORMAL</td>
	</section>	</tr>
		<tr>
	<section title="3GPP TS 24.182">	<td align="left">bc_program</td>
	<t>	<td align="left">Not impacted</td>
	<xref target="R3GPPTS24.182"/> specifies IP multimedia subsystem	<td align="left">S</td>
	Custom Alerting tones	<td align="left">NORMAL</td>
	</t>	</tr>
	<texttable title="5.51 3GPP TS 24.182 Attribute Analysis">	<tr>
	<ttcol align='left'>Name</ttcol>	<td align="left">bc_service_package</td>
	<ttcol align='left'>Notes</ttcol>	<td align="left">Not impacted</td>
	<ttcol align='left'>Level</ttcol>	<td align="left">S</td>
	<ttcol align='left'>Mux Category</ttcol>	<td align="left">NORMAL</td>
		</tr>
	<c>g.3gpp.cat </c>	</tbody>
	<c>Usage defined for the IP Multimedia Subsystem </c>	</table>
	<c>M</c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	</texttable>
	</section>	</section>


	<section title="3GPP TS 24.183">	<!-- removed 3GPP TS 24.182 and 3GPP TS 24.183
	<t>	per draft-ietf-mmusic-sdp-mux-attributes-19
	<xref target="R3GPPTS24.183"/> specifies IP multimedia	-->
	subsystem Custom Ringing Signal
	</t>
	<texttable title="5.52 3GPP TS 24.183 Attribute Analysis">
	<ttcol align='left'>Name</ttcol>
	<ttcol align='left'>Notes</ttcol>
	<ttcol align='left'>Level</ttcol>
	<ttcol align='left'>Mux Category</ttcol>

	<c>g.3gpp.crs </c>
	<c>Usage defined for the IP Multimedia Subsystem </c>
	<c>M</c><c>NORMAL </c>
	<c> </c><c> </c><c> </c><c> </c>

	</texttable>
	</section>


	<section title="3GPP TS 24.229">	<section numbered="true" toc="default">
		<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 </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 </c><c>M</c>	transport flow.</td>
	<c>TRANSPORT </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">TRANSPORT</td>
		</tr>
	<c>visited-realm </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 </c><c>M</c>	transport flow.</td>
	<c>TRANSPORT </c><c> </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c>	<td align="left">TRANSPORT</td>
		</tr>
	<c>omr-m-cksum </c><c>Not Impacted </c>	<tr>
	<c>M</c><c>NORMAL </c><c> </c>	<td align="left">omr-m-cksum</td>
	<c> </c><c> </c><c> </c>	<td align="left">Not impacted</td>
		<td align="left">M</td>
	<c>omr-s-cksum </c><c>Not Impacted </c>	<td align="left">NORMAL</td>
	<c>M</c><c>NORMAL </c><c> </c>	</tr>
	<c> </c><c> </c><c> </c>	<tr>
		<td align="left">omr-s-cksum</td>
	<c>omr-m-att </c><c>Not Impacted </c>	<td align="left">Not impacted</td>
	<c>M</c><c>NORMAL </c><c> </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c>	<td align="left">NORMAL</td>
		</tr>
	<c>omr-s-att </c><c>Not Impacted </c>	<tr>
	<c>M</c><c>NORMAL </c><c> </c>	<td align="left">omr-m-att</td>
	<c> </c><c> </c><c> </c>	<td align="left">Not impacted</td>
		<td align="left">M</td>
	<c>omr-m-bw </c><c>Not Impacted </c>	<td align="left">NORMAL</td>
	<c>M</c><c>NORMAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">omr-s-att</td>
	<c>omr-s-bw </c><c>Not Impacted </c>	<td align="left">Not impacted</td>
	<c>M</c><c>NORMAL </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">NORMAL</td>
		</tr>
	<c>omr-codecs </c><c>Not Impacted </c>	<tr>
	<c>M</c><c>NORMAL </c>	<td align="left">omr-m-bw</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Refer to notes below </c>	<th align="left">Level</th>
	<c>M</c><c>TBD </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>T38MaxBitRate </c><c>Refer to notes below </c>	<tbody>
	<c>M</c><c>TBD </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">T38FaxVersion</td>
		<td align="left">Refer to notes below</td>
	<c>T38FaxFillBitRemoval </c><c>Refer to notes below </c>	<td align="left">M</td>
	<c>M</c><c>TBD </c>	<td align="left">TBD</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>T38FaxTranscodingMMR </c><c>Refer to notes below </c>	<td align="left">T38MaxBitRate</td>
	<c>M</c><c>TBD </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">TBD</td>
	<c>T38FaxTranscodingJBIG </c><c>Refer to notes below </c>	</tr>
	<c>M</c><c>TBD </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">T38FaxFillBitRemoval</td>
		<td align="left">Refer to notes below</td>
	<c>T38FaxRateManagement </c><c>Refer to notes below </c>	<td align="left">M</td>
	<c>M</c><c>TBD </c>	<td align="left">TBD</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>T38FaxMaxBuffer </c><c>Refer to notes below </c>	<td align="left">T38FaxTranscodingMMR</td>
	<c>M</c><c>TBD </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">TBD</td>
	<c>T38FaxMaxDatagram </c><c>Refer to notes below </c>	</tr>
	<c>M</c><c>TBD </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">T38FaxTranscodingJBIG</td>
		<td align="left">Refer to notes below</td>
	<c>T38FaxUdpEC </c><c>Refer to notes below </c>	<td align="left">M</td>
	<c>M</c><c>TBD </c>	<td align="left">TBD</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>T38FaxMaxIFP </c><c>Refer to notes below </c>	<td align="left">T38FaxRateManagement</td>
	<c>M</c><c>TBD </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">TBD</td>
	<c>T38FaxUdpECDepth </c><c>Refer to notes below </c>	</tr>
	<c>M</c><c>TBD </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">T38FaxMaxBuffer</td>
		<td align="left">Refer to notes below</td>
	<c>T38FaxUdpFECMaxSpan </c><c>Refer to notes below </c>	<td align="left">M</td>
	<c>M</c><c>TBD </c>	<td align="left">TBD</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>T38ModemType </c><c>Refer to notes below </c>	<td align="left">T38FaxMaxDatagram</td>
	<c>M</c><c>TBD </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">TBD</td>
	<c>T38VendorInfo </c><c>Refer to notes below </c>	</tr>
	<c>M</c><c>TBD </c>	<tr>
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	ITU-T specifications while multiplexing.</td>
	<c>S</c><c>SPECIAL </c>	<td align="left">S</td>
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	the use of multiplexing to a gateway.</td>
	<c>B</c><c>SPECIAL </c>	<td align="left">B</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Refer to notes below </c>	<th align="left">Level</th>
	<c>M </c><c>TBD </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>accept-wrapped-types </c><c>Refer to notes below </c>	<tbody>
	<c>M </c><c>TBD </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">accept-types</td>
		<td align="left">Refer to notes below</td>
	<c>max-size </c><c>Refer to notes below </c>	<td align="left">M</td>
	<c>M </c><c>TBD </c>	<td align="left">TBD</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>path </c><c>Refer to notes below </c>	<td align="left">accept-wrapped-types</td>
	<c>M </c><c>TBD </c>	<td align="left">Refer to notes below</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Historic attributes </c>	<th align="left">Level</th>
	<c>M</c><c>CAUTION </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>rtpred2 </c><c>Historic attributes </c>	<tbody>
	<c>M</c><c>CAUTION </c>	<tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>S</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>bwtype:AS </c><c> For the media level usage,	<tbody>
	the aggregate of individual bandwidth values is considered <	<tr>
	/c>	<td align="left">bwtype:CT</td>
	<c>B</c>	<td align="left">Not impacted</td>
	<c>SUM </c>	<td align="left">S</td>
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	</tr>
	<c>B</c><c>SUM</c>	</thead>
	<c> </c><c> </c><c> </c><c> </c>	<tbody>
		<tr>
	<c>bwtype:RR </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 </c>	session aggregate, and media-level usage indicates SUM of the
	<c>B</c><c>SUM </c>	individual values while multiplexing.</td>
	<c> </c><c> </c><c> </c><c> </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 </c><c>The usage of TIAS is not	<th align="left">Level</th>
	defined under Offer/Answer usage. </c>	<th align="left">Mux Category</th>
	<c>B</c><c>SPECIAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
	<c>maxprate </c><c>The usage of TIAS and maxprate	<tbody>
	is not well defined under multiplexing </c>	<tr>
	<c>B</c><c>SPECIAL </c>	<td align="left">bwtype:TIAS</td>
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>ack app </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 </c>	me
	<c> </c><c> </c><c> </c><c> </c>	for a given codec configuration.</td>
		<td align="left">M</td>
	<c>nack </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 </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">ack app</td>
		<td align="left">Feedback parameters <bcp14>MUST</bcp14> be handle
	<c>nack pli </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 </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">SPECIAL</td>
		</tr>
	<c>nack sli </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 </c>	<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
	<c> </c><c> </c><c> </c><c> </c>	me
		for a given codec configuration.</td>
	<c>nack rpsi </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 </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">nack pli</td>
	<c>nack app </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 </c>	<td align="left">M</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">IDENTICAL-PER-PT</td>
		</tr>
	<c>trr-int </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 </c>	<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	</tr>
	<c> </c><c> </c><c> </c><c> </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 </c><c>ECN markup are enabled at the	<th align="left">Level</th>
	RTP session level </c>	<th align="left">Mux Category</th>
	<c>M </c><c>IDENTICAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
	<c>nack ecn </c><c>This attribute enables ECN at the RTP	<tbody>
	session level </c>	<tr>
	<c>M </c><c>IDENTICAL </c>	<td align="left">ecn-capable-rtp</td>
	<c> </c><c> </c><c> </c><c> </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 </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>	</tr>
	<c>IDENTICAL-PER-PT </c>	</thead>
	<c> </c><c> </c><c> </c><c> </c>	<tbody>
		<tr>
	<c>nack pslei </c><c>The attribute value MUST be same	<td align="left">nack tllei</td>
	for a given codec configuration </c>	<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
	<c>M </c>	me
	<c>IDENTICAL-PER-PT </c>	for a given codec configuration.</td>
	<c> </c><c> </c><c> </c><c> </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 </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 </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
		<tbody>
	<c>ccm tmmbr </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 </c>	<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
	<c> </c><c> </c><c> </c><c> </c>	me
		for a given codec configuration.</td>
	<c>ccm tstr </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 </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">ccm tmmbr</td>
	<c>ccm vbcm </c><c>The attribute value MUST be same	<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
	for a given codec configuration</c>	me
	<c>M</c><c>IDENTICAL-PER-PT </c>	for a given codec configuration.</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
	</texttable>	<td align="left">IDENTICAL-PER-PT</td>
	</section>	</tr>
	</section>	<tr>
	<section title="group Attribute Analysis"	<td align="left">ccm tstr</td>
	anchor="SecgroupAnalysis">	<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
	<t>	me
	This section analyzes SDP "group" attribute semantics	for a given codec configuration.</td>
	<xref target="RFC5888"/>.	<td align="left">M</td>
	</t>	<td align="left">IDENTICAL-PER-PT</td>
	<section title="RFC5888: SDP Grouping Framework">	</tr>
	<t>	<tr>
	<xref target="RFC5888"/> defines a framework	<td align="left">ccm vbcm</td>
	to group "m" lines in SDP for different purposes.	<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
	</t>	me
	<texttable title="8.1 RFC5888 Attribute Analysis">	for a given codec configuration.</td>
	<ttcol align='left'>Name</ttcol>	<td align="left">M</td>
	<ttcol align='left'>Notes</ttcol>	<td align="left">IDENTICAL-PER-PT</td>
	<ttcol align='left'>Level</ttcol>	</tr>
	<ttcol align='left'>Mux Category</ttcol>	</tbody>
		</table>
	<c>group:LS </c><c>Not Impacted </c>	</section>
	<c>S </c><c>NORMAL </c>	</section>
	<c> </c><c> </c><c> </c><c> </c>	<section anchor="SecgroupAnalysis" numbered="true" toc="default">
		<name>group Attribute Analysis</name>
	<c>group:FID </c><c>Not Impacted </c>	<t>
	<c>S </c><c>NORMAL </c>	This section analyzes SDP "group" attribute semantics
	<c> </c><c> </c><c> </c><c> </c>	<xref target="RFC5888" format="default"/>.
		</t>
		<section numbered="true" toc="default">
		<name>RFC 5888: SDP Grouping Framework</name>


	</texttable>	<t>
	</section>	<xref target="RFC5888" format="default"/> defines a framework
	<section title="RFC3524: Mapping Media Streams to	to group "m=" lines in SDP for different purposes.
	Resource Reservation Flows">	</t>
	<t><xref target="RFC3524"/> defines an extension to	<table align="center">
		<name>RFC 5888 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">group:LS</td>
		<td align="left">Not impacted</td>
		<td align="left">S</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">group:FID</td>
		<td align="left">Not impacted</td>
		<td align="left">S</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>RFC 3524: Mapping Media Streams to Resource Reservation Flows</nam
		e>
		<t><xref target="RFC3524" format="default"/> defines an extension to
	the SDP grouping framework. It allows requesting a group of media	the SDP grouping framework. It allows requesting a group of media
	streams to be mapped into a single resource reservation flow. The SDP sy ntax	streams to be mapped into a single resource reservation flow. The SDP sy ntax
	needed is defined, as well as a new "semantics" attribute	needed is defined, as well as a new "semantics" attribute
	called Single Reservation Flow (SRF).</t>	called Single Reservation Flow (SRF).</t>

	<texttable title="8.2 RFC3524 Attribute Analysis">	<table align="center">
	<ttcol align='left'>Name</ttcol>	<name>RFC 3524 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>group:SRF </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>S </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	</texttable>	<tbody>
	</section>	<tr>
		<td align="left">group:SRF</td>
		<td align="left">Not impacted</td>
		<td align="left">S</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>


	<section title="RFC4091: ANAT Semantics">	<section numbered="true" toc="default">
	<t>	<name>RFC 4091: ANAT Semantics</name>
	<xref target="RFC4091"/> defines ANAT semantics for the	<t>
	SDP grouping framework. The ANAT semantics allow alternative	<xref target="RFC4091" format="default"/> defines ANAT semantics for th
		e
		SDP grouping framework. (Note: <xref target="RFC4091"/> has been
		obsoleted by <xref
		target="RFC8445"/>.) The ANAT semantics allow alternative
	types of network addresses to establish a particular media stream.	types of network addresses to establish a particular media stream.

	</t>	</t>
	<texttable title="8.3 RFC4091 Attribute Analysis">	<table align="center">
	<ttcol align='left'>Name</ttcol>	<name>RFC 4091 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>group:ANAT </c><c>ANAT semantics is obsoleted  </c>	<th align="left">Level</th>
	<c>S </c>	<th align="left">Mux Category</th>
	<c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
	</texttable>	<tbody>
		<tr>
	</section>	<td align="left">group:ANAT</td>
		<td align="left">ANAT semantics is obsoleted.</td>
	<section title="RFC5956: FEC Grouping Semantics in SDP">	<td align="left">S</td>
	<t><xref target="RFC5956"/> defines the semantics	<td align="left">CAUTION</td>
	for grouping the associated source and FEC-based (Forward	</tr>
	Error Correction) repair flows in SDP. The semantics defined	</tbody>
	in the document are to be used with the SDP Grouping Framework	</table>
	<xref target="RFC5888"/>. These	</section>
		<section numbered="true" toc="default">
		<name>RFC 5956: FEC Grouping Semantics in SDP</name>
		<t><xref target="RFC5956" format="default"/> defines the semantics
		for grouping the associated source and FEC-based repair flows in
		SDP. The semantics defined in the document are to be used with the SDP
		Grouping Framework
		<xref target="RFC5888" format="default"/>. These
	semantics allow the description of grouping relationships	semantics allow the description of grouping relationships
	between the source and repair flows when one or more source	between the source and repair flows when one or more source

	and/or repair flows are associated in the same group, and	and/or repair flows are associated in the same group; they also
	they provide support for additive repair flows. SSRC-level	provide support for additive repair flows. SSRC-level
	(Synchronization Source) grouping semantics are also defined	grouping semantics are also defined
	in this document for RTP streams using SSRC multiplexing.</t>	in this document for RTP streams using SSRC multiplexing.</t>

	<texttable title="8.4 RFC5956 Attribute Analysis">	<table align="center">
	<ttcol align='left'>Name</ttcol>	<name>RFC 5956 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>group:FEC-FR </c><c>Not Impacted </c><c>S </c>	<th align="left">Level</th>
	<c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	</texttable>	<tbody>
	</section>	<tr>
	<section title="RFC5583: Signaling Media Decoding Dependency in SDP">	<td align="left">group:FEC-FR</td>
	<t><xref target="RFC5583"/> defines semantics that	<td align="left">Not impacted</td>
		<td align="left">S</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>RFC 5583: Signaling Media Decoding Dependency in SDP</name>
		<t><xref target="RFC5583" format="default"/> defines semantics that
	allow for signaling the decoding dependency of different	allow for signaling the decoding dependency of different
	media descriptions with the same media type in SDP. This is	media descriptions with the same media type in SDP. This is
	required, for example, if media data is separated and transported	required, for example, if media data is separated and transported

	in different network streams as a result of the use of a layered or	in different network streams as a result of using a layered or
	multiple descriptive media coding process.</t>	multiple descriptive media coding process.</t>

	<texttable title="8.5 RFC5583 Attribute Analysis">	<table align="center">
	<ttcol align='left'>Name</ttcol>	<name>RFC 5583 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>group:DDP </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>S </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>depend lay </c><c>The attribute value MUST be same	<tbody>
	for a given codec configuration  </c><c>M</c>	<tr>
	<c>IDENTICAL-PER-PT </c>	<td align="left">group:DDP</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Not impacted</td>
		<td align="left">S</td>
	<c>depend mdc </c><c>The attribute value MUST be same	<td align="left">NORMAL</td>
	for a given codec configuration </c><c>M</c>	</tr>
	<c>IDENTICAL-PER-PT </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">depend lay</td>
	</texttable>	<td align="left">The attribute value <bcp14>MUST</bcp14> be the sa
	</section>	me
	<section title="RFC7104: Duplication Grouping Semantics in the SDP">	for a given codec configuration.</td>
	<t><xref target="RFC7104"/> defines the semantics for	<td align="left">M</td>
	grouping redundant streams in SDP, The semantics defined in this	<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">depend mdc</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 7104: Duplication Grouping Semantics in the SDP</name>
		<t><xref target="RFC7104" format="default"/> defines the semantics for
		grouping redundant streams in SDP. The semantics defined in this
	document are to be used with the SDP Grouping Framework. Grouping	document are to be used with the SDP Grouping Framework. Grouping

	semantics at the SSRC)level are also defined in this document for	semantics at the synchronization source (SSRC) level are also
	RTP	defined in this document for RTP
	streams using SSRC multiplexing.</t>	streams using SSRC multiplexing.</t>

	<texttable title="8.6 RFC7104 Attribute Analysis">	<table align="center">
	<ttcol align='left'>Name</ttcol>	<name>RFC 7104 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>group:DUP </c><c>Not Impacted </c><c>S </c>	<th align="left">Level</th>
	<c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
	</texttable>	</thead>
	</section>	<tbody>
	</section>	<tr>
	<section title="ssrc-group Attribute Analysis"	<td align="left">group:DUP</td>
	anchor="sec-ssrc-group">	<td align="left">Not impacted</td>
	<t>	<td align="left">S</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		</section>
		<section anchor="sec-ssrc-group" numbered="true" toc="default">
		<name>ssrc-group Attribute Analysis</name>
		<t>
	This section analyzes "ssrc-group" semantics.	This section analyzes "ssrc-group" semantics.

	</t>	</t>
	<section title="RFC5576: Source-Specific SDP Attributes">	<section numbered="true" toc="default">
	<t><xref target="RFC5576"/> defines a mechanism to	<name>RFC 5576: Source-Specific SDP Attributes</name>
	describe RTP media sources, which are identified by their	<t><xref target="RFC5576" format="default"/> defines a mechanism for
	synchronization source (SSRC) identifiers, in SDP, to	describing RTP 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="9.1 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-group:FID </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>SR</c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>ssrc-group:FEC </c><c>Not Impacted </c>	<tbody>
	<c>SR</c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">ssrc-group:FID</td>
		<td align="left">Not impacted</td>
	<c>ssrc-group:FEC-FR </c><c>Not Impacted </c>	<td align="left">SR</td>
	<c>SR</c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	</texttable>	<td align="left">ssrc-group:FEC</td>
	</section>	<td align="left">Not impacted</td>
	<section title="RFC7104: Duplication Grouping Semantics in the SDP">	<td align="left">SR</td>
	<t><xref target="RFC7104"/> defines the semantics for	<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">ssrc-group:FEC-FR</td>
		<td align="left">Not impacted</td>
		<td align="left">SR</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>RFC 7104: Duplication Grouping Semantics in the SDP</name>
		<t><xref target="RFC7104" format="default"/> defines the semantics for
	grouping redundant streams in SDP.	grouping redundant streams in SDP.
	The semantics defined in this document are to be used with the SDP	The semantics defined in this document are to be used with the SDP

	Grouping Framework. Grouping semantics at the Synchronization Source	Grouping Framework. Grouping semantics at the synchronization source
	(SSRC) level are also defined in this document for RTP streams using	(SSRC) level are also defined in this document for RTP streams using
	SSRC multiplexing.</t>	SSRC multiplexing.</t>

	<texttable title="9.2 RFC7104 Attribute Analysis">	<table align="center">
	<ttcol align='left'>Name</ttcol>	<name>RFC 7104 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-group:DUP </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>SR</c>	<th align="left">Mux Category</th>
	<c>NORMAL </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	</thead>
	</texttable>	<tbody>
	</section>	<tr>
	</section>	<td align="left">ssrc-group:DUP</td>
	<section title="QoS Mechanism Token Analysis"	<td align="left">Not impacted</td>
	anchor="SecqostokenAnalysis">	<td align="left">SR</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		</section>
		<section anchor="SecqostokenAnalysis" numbered="true" toc="default">
		<name>QoS Mechanism Token Analysis</name>
	<t>	<t>
	This section analyzes QoS tokes specified with SDP.	This section analyzes QoS tokes specified with SDP.
	</t>	</t>

	<section title="RFC5432: QoS Mechanism Selection in SDP">	<section numbered="true" toc="default">
	<t><xref target="RFC5432"/> defines procedures to	<name>RFC 5432: QoS Mechanism Selection in SDP</name>
	negotiate QOS mechanisms using the SDP offer/answer model.</t>	<t><xref target="RFC5432" format="default"/> defines procedures to
	<texttable title="10.1 RFC5432 Attribute Analysis">	negotiate QoS mechanisms using the SDP offer/answer model.</t>
	<ttcol align='left'>Name</ttcol>	<table align="center">
	<ttcol align='left'>Notes</ttcol>	<name>RFC 5432 Attribute Analysis</name>
	<ttcol align='left'>Level</ttcol>	<thead>
	<ttcol align='left'>Mux Category</ttcol>	<tr>
		<th align="left">Name</th>
	<c>rsvp </c><c>rsvp attribute 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">rsvp</td>
		<td align="left">rsvp attribute <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 </c>	setting up the underlying transport flow.</td>
	<c>B</c><c>TRANSPORT </c>	<td align="left">B</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">TRANSPORT</td>
		</tr>
	<c>nsis </c><c>rsvp attribute MUST be the one	<tr>
		<td align="left">nsis</td>
		<td align="left">rsvp attribute <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 </c>	setting up the underlying transport.</td>
	<c>B</c><c>TRANSPORT </c>	<td align="left">B</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">TRANSPORT</td>
	</texttable>	</tr>
	<t>NOTE: A single Differentiated Services Code Point (DSCP) code	</tbody>
	point per flow being multiplexed doesn't impact multiplexing since	</table>
	QOS mechanisms are signaled/scoped per flow. For scenarios that involv
	e	<t>NOTE: A single Differentiated Services Code Point (DSCP) for each
	having different DSCP code points for packets being transmitted over	flow being multiplexed doesn't impact multiplexing, since QoS
	the same 5-tuple, issues as discussed in	mechanisms are signaled/scoped per flow. For scenarios that involve
	<xref target="RFC7657"/> need to be	having different DSCP code points for packets being transmitted over
	taken into consideration.</t>	the same 5-tuple, issues as discussed in <xref target="RFC7657"
		format="default"/> need to be taken into consideration.</t>
	</section>	</section>
	</section>	</section>

	<section title="k= Attribute Analysis" anchor="SeckAnalysis">	<section anchor="SeckAnalysis" numbered="true" toc="default">
	<section title="RFC4566: SDP">	<name>k= Attribute Analysis</name>
	<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>

	<texttable title="11.1 RFC4566 Attribute Analysis">	<table align="center">
	<ttcol align='left'>Name</ttcol>	<name>RFC 4566 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>k= </c>	<th align="left">Level</th>
	<c>It is not recommended to use this attribute under multiplexing&nbsp	<th align="left">Mux Category</th>
	;</c><c>S</c>	</tr>
	<c>CAUTION </c>	</thead>
	<c> </c><c> </c><c> </c><c> </c>	<tbody>
		<tr>
	</texttable>	<td align="left">k=</td>
		<td align="left">It is not recommended to use this attribute under
		multiplexing.</td>
		<td align="left">S</td>
		<td align="left">CAUTION</td>
		</tr>
		</tbody>
		</table>
	</section>	</section>
	</section>	</section>

	<section title="content Attribute Analysis" anchor="SeccontentAnalysis">	<section anchor="SeccontentAnalysis" numbered="true" toc="default">
	<section title="RFC4796">	<name>content Attribute Analysis</name>
	<t><xref target="RFC4796"/> defines a new SDP media-level attribute,	<section numbered="true" toc="default">
	'content'. The 'content' attribute defines the content of the media	<name>RFC 4796</name>
		<t><xref target="RFC4796" format="default"/> defines a new SDP media-lev
		el attribute,
		"content". The "content" attribute defines the content of the media
	stream to a more detailed level than the media description	stream to a more detailed level than the media description
	line. The sender of an SDP session description can attach	line. The sender of an SDP session description can attach

	the 'content' attribute to one or more media streams. The	the "content" attribute to one or more media streams. The
	receiving application can then treat each media stream	receiving application can then treat each media stream
	differently (e.g., show it on a big or small screen) based	differently (e.g., show it on a big or small screen) based
	on its content.</t>	on its content.</t>

	<texttable title="12.1 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:slides </c><c>Not Impacted </c>	<th align="left">Level</th>
	<c>M </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		</thead>
	<c>content:speaker </c><c>Not Impacted </c>	<tbody>
	<c>M </c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">content:slides</td>
		<td align="left">Not impacted</td>
	<c>content:main </c><c>Not Impacted </c>	<td align="left">M</td>
	<c>M </c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c> </c><c> </c><c> </c><c> </c>	</tr>
		<tr>
	<c>content:sl </c><c>Not Impacted </c>	<td align="left">content:speaker</td>
	<c>M </c><c>NORMAL </c>	<td align="left">Not impacted</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">NORMAL</td>
	<c>content:alt </c><c>Not Impacted </c>	</tr>
	<c>M </c><c>NORMAL </c>	<tr>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">content:main</td>
		<td align="left">Not impacted</td>
	</texttable>	<td align="left">M</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">content:sl</td>
		<td align="left">Not impacted</td>
		<td align="left">M</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">content:alt</td>
		<td align="left">Not impacted</td>
		<td align="left">M</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
	</section>	</section>

	</section>


	<section anchor="sec-pay" title="Payload Formats">	<section numbered="true" toc="default">
		<name>3GPP TS 24.182</name>
		<t>
		<xref target="IMS-CAT" format="default"/> specifies an IP multimedia s
		ubsystem for
		customized alerting tones.
		</t>
		<table align="center">
		<name>3GPP TS 24.182 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">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 numbered="true" toc="default">
		<name>3GPP TS 24.183</name>
		<t>
		<xref target="IMS-CRS" format="default"/> specifies an IP multimedia
		subsystem for customized ringing signal.
		</t>
		<table align="center">
		<name>3GPP TS 24.183 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">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 title="RFC5109: RTP Payload Format for Generic FEC">	</section>
	<t><xref target="RFC5109"/> describes a payload	<section anchor="sec-pay" numbered="true" toc="default">
		<name>Payload Formats</name>
		<section numbered="true" toc="default">
		<name>RFC 5109: RTP Payload Format for Generic FEC</name>
		<t><xref target="RFC5109" format="default"/> describes a payload
	format for generic Forward Error Correction (FEC) for media	format for generic Forward Error Correction (FEC) for media
	data encapsulated in RTP. It is based on the exclusive-or	data encapsulated in RTP. It is based on the exclusive-or
	(parity) operation. The payload format allows end systems	(parity) operation. The payload format allows end systems
	to apply protection using various protection lengths and	to apply protection using various protection lengths and
	levels, in addition to using various protection group sizes	levels, in addition to using various protection group sizes
	to adapt to different media and channel characteristics. It	to adapt to different media and channel characteristics. It
	enables complete recovery of the protected packets or	enables complete recovery of the protected packets or

	partial recovery of the critical parts of the payload	partial recovery of the critical parts of the payload,
	depending on the packet loss situation.</t>	depending on the packet loss situation.</t>

		<table align="center">
	<texttable title="13.1 RFC5109 Payload Format Analysis">	<name>RFC 5109 Payload Format 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>audio/ulpfec </c>	<th align="left">Mux Category</th>
	<c>Not recommended for multiplexing due to reuse of SSRCs </c>	</tr>
	<c>M</c><c>CAUTION </c>	</thead>
	<c> </c><c> </c><c> </c><c> </c>	<tbody>
		<tr>
	<c>video/ulpfec </c>	<td align="left">audio/ulpfec</td>
	<c>Not recommended for multiplexing due to reuse of SSRCs </c>	<td align="left">Not recommended for multiplexing due to reuse of
	<c>M</c><c>CAUTION </c>	SSRCs.</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">M</td>
		<td align="left">CAUTION</td>
	<c>text/ulpfec </c>	</tr>
	<c>Not recommended for multiplexing due to reuse of SSRCs </c>	<tr>
	<c>M</c><c>CAUTION </c>	<td align="left">video/ulpfec</td>
	<c> </c><c> </c><c> </c><c> </c>	<td align="left">Not recommended for multiplexing due to reuse of
		SSRCs.</td>
	<c>application/ulpfec </c>	<td align="left">M</td>
	<c>Not recommended for multiplexing due to reuse of SSRCs </c>	<td align="left">CAUTION</td>
	<c>M</c><c>CAUTION </c>	</tr>
	<c> </c><c> </c><c> </c><c> </c>	<tr>
		<td align="left">text/ulpfec</td>
	</texttable>	<td align="left">Not recommended for multiplexing due to reuse of
	</section>	SSRCs.</td>
		<td align="left">M</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">application/ulpfec</td>
		<td align="left">Not recommended for multiplexing due to reuse of
		SSRCs.</td>
		<td align="left">M</td>
		<td align="left">CAUTION</td>
		</tr>
		</tbody>
		</table>
	</section>	</section>

	<section title="Multiplexing Considerations for Encapsulating Attributes"	</section>
	anchor="sec-encap">	<section anchor="sec-encap" numbered="true" toc="default">
	<t>This sections deals with recommendations for defining the	<name>Multiplexing Considerations for Encapsulating Attributes</name>
		<t>This section deals with recommendations for defining the
	multiplexing characteristics of the SDP attributes that	multiplexing characteristics of the SDP attributes that

	encapsulate other SDP attributes/parameters. Such	encapsulate other SDP attributes/parameters. As of today, such
	attributes as of today, for example, are defined in	attributes, for example, are defined in
	<xref target="RFC3407"/>, <xref target="RFC5939"/> and	<xref target="RFC3407" format="default"/>, <xref target="RFC5939" for
	<xref target="RFC6871"/> as part of a generic	mat="default"/> and
	framework for indicating and negotiating transport, media,	<xref target="RFC6871" format="default"/> as part of a generic
	and media format related capabilities in the SDP.</t>	framework for indicating and negotiating transport-, media-,
	<t>The behavior of such attributes under multiplexing is in	and media-format-related capabilities in the SDP.</t>
	turn defined by the multiplexing behavior of the attributes	<t>The behavior of such attributes under multiplexing is, in
	they encapsulate which are made known once the Offer/Answer	turn, defined by the multiplexing behavior of the attributes
		they encapsulate, which are made known once the offer/answer
	negotiation process is completed.</t>	negotiation process is completed.</t>

	<section title="RFC3407: cpar Attribute Analysis">	<section numbered="true" toc="default">
	<t> <xref target="RFC3407"/> capability parameter	<name>RFC 3407: cpar Attribute Analysis</name>
	attribute (a=cpar) encapsulates b= (bandwidth) or an	<t>The <xref target="RFC3407" format="default"/> capability parameter
	a= attribute. For bandwidth attribute encapsulation,	attribute "a=cpar" encapsulates a "b=" (bandwidth) or an
	the category SUM is inherited. For the case of a= attribute,	"a=" attribute. For bandwidth attribute encapsulation,
		the category SUM is inherited. For the case of "a=" attribute,
	the category corresponding to the SDP attribute being	the category corresponding to the SDP attribute being
	encapsulated is inherited.	encapsulated is inherited.

	</t>	</t>
	<t>	<sourcecode type="sdp">
	<figure>
	<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=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
	</t>	inherited for the cpar-encapsulated "rtcp-mux"
	<t> In the above example,the category IDENTICAL is
	inherited for the cpar encapsulated rtcp-mux
	attribute. </t>	attribute. </t>

	<t> </t>	<t></t>
	</section>	</section>
	<section title="RFC5939 Analysis">	<section numbered="true" toc="default">
	<t><xref target="RFC5939"/> defines a general SDP	<name>RFC 5939 Analysis</name>
		<t><xref target="RFC5939" format="default"/> defines a general SDP
	capability negotiation framework. It also specifies	capability negotiation framework. It also specifies
	how to provide transport protocols and SDP attributes	how to provide transport protocols and SDP attributes
	as capabilities and negotiate them using the	as capabilities and negotiate them using the
	framework.</t>	framework.</t>

	<t>For this purpose, <xref target="RFC5939"/> defines the followin	<t>For this purpose, <xref target="RFC5939" format="default"/> defines t
	g	he following:
	<list style="symbols">	</t>
	<t>A set of capabilities for the session and its	<ul spacing="normal">
	associated media stream components, supported	<li>A set of capabilities for the session and its
	by each side. The attribute ("a=acap") defines	associated media-stream components, supported
		by each side. The attribute "a=acap" defines
	how to list an attribute name and its	how to list an attribute name and its
	associated value (if any) as a capability. The	associated value (if any) as a capability. The

	attribute ("a=tcap") defines how to list	attribute "a=tcap" defines how to list
	transport protocols (e.g., "RTP/AVP") as	transport protocols (e.g., "RTP/AVP") as

	capabilities.</t>	capabilities.</li>
	<t>A set of potential configurations ("a=pcfg") provided	<li>A set of potential configurations ("a=pcfg") provided
	by the offerer to indicate which combinations of those	by the offerer to indicate which combinations of those
	capabilities can be used for the session and its	capabilities can be used for the session and its
	associated media stream components. Potential	associated media stream components. Potential
	configurations are not ready for use until fully	configurations are not ready for use until fully

	negotiated. They provide an alternative that MAY	negotiated. They provide an alternative that <bcp14>MAY</bcp
	be used, subject to SDP capability negotiation	14>
	procedures. In particular the answerer MAY choose	be used, subject to SDP capability-negotiation
		procedures. In particular, the answerer <bcp14>MAY</bcp14> c
		hoose
	one of the potential configurations for use as part	one of the potential configurations for use as part

	of the current Offer/Answer exchange.</t>	of the current offer/answer exchange.</li>
	<t>An actual configuration ("a=acfg") for the session	<li>An actual configuration ("a=acfg") for the session
	and its associated media stream components. The	and its associated media stream components. The
	actual configuration identifies the potential	actual configuration identifies the potential
	configuration that was negotiated for use. Use	configuration that was negotiated for use. Use
	of an actual configuration does not require	of an actual configuration does not require

	any further negotiation.</t>	any further negotiation.</li>
	<t>A negotiation process that takes the current	<li>A negotiation process that takes the current
	actual and the set of potential configurations	actual and the set of potential configurations
	(combinations of capabilities) as input and	(combinations of capabilities) as input and
	provides the negotiated actual configurations	provides the negotiated actual configurations

	as output. In <xref target="RFC5939"/> the	as output. In <xref target="RFC5939" format="default"/>, the
	negotiation process is done independently for	negotiation process is done independently for

	each media description.</t>	each media description.</li>
	</list>	</ul>
	</t>	<section anchor="sec-cap-neg-proc" numbered="true" toc="default">
	<section title="Recommendation: Procedures for Potential Configura	<name>Recommendation: Procedures for Potential Configuration Pairing</
	tion Pairing"	name>
	anchor="sec-cap-neg-proc">	<t>This section provides recommendations for entities
	<t>This section provides recommendations for entities
	generating and processing SDP under the generic	generating and processing SDP under the generic

	capability negotiation framework as defined in	capability-negotiation framework as defined in
	<xref target="RFC5939"/> under the context of media	<xref target="RFC5939" format="default"/> under the context of m
	stream multiplexing.</t>	edia-stream
	<t>These recommendations are provided for the purposes	multiplexing.</t>
	of enabling the Offerer to make sure that the	<t>These recommendations are provided for the purposes
		of enabling the offerer to make sure that the
	generated potential configurations between the	generated potential configurations between the
	multiplexed streams can (easily) be negotiated to be	multiplexed streams can (easily) be negotiated to be
	consistent between those streams. In particular, the	consistent between those streams. In particular, the

	procedures aim to simplify Answerer's procedure to choose	procedures aim to simplify the answerer's procedure for choosing
	potential configurations that are consistent across	potential configurations that are consistent across
	all the multiplexed media descriptions.</t>	all the multiplexed media descriptions.</t>

	<t>A potential configuration selects a set of attributes	<t>A potential configuration selects a set of attributes
	and parameters that become part of the media description	and parameters that become part of the media description
	when negotiated. When multiplexing media descriptions with	when negotiated. When multiplexing media descriptions with

	potential configurations specified, there MAY be a need	potential configurations specified, there <bcp14>MAY</bcp14> be a need
	for coordinating this selection between multiplexed media	for coordinating this selection between multiplexed media
	descriptions to ensure the right multiplexing behavior.</t>	descriptions to ensure the right multiplexing behavior.</t>

	<t> Although it is possible to analyze the various potential	<t>Although it is possible to analyze the various potential
	configurations in multiplexed media descriptions to find combina tions	configurations in multiplexed media descriptions to find combina tions
	that satisfy such constraints, it can quickly become complicated	that satisfy such constraints, it can quickly become complicated
	to do so. </t>	to do so. </t>

	<t> The procedures defined in <xref target="RFC5939"/> state	<t>The procedures defined in <xref target="RFC5939" format="default"/> state
	that each potential configuration in the SDP has a unique	that each potential configuration in the SDP has a unique

	configuration number, however the scope of uniqueness is	configuration number; however, the scope of uniqueness is
	limited to each media description. To make it simple for the	limited to each media description. To make it simple for the
	answerer to chose valid combinations of potential configurations	answerer to chose valid combinations of potential configurations

	across media descriptions in a given bundle group, we provide a	across media descriptions in a given BUNDLE group, we provide a
	simple rule for constructing potential configurations	simple rule for constructing potential configurations:
	<list style="symbols">	</t>
	<t> Let m-bundle be the set of media descriptions that form	<ul spacing="normal">
	a given bundle .</t>	<li>Let m-bundle be the set of media descriptions that form
	<t> Let m-bundle-pcfg be the set of media descriptions in	a given bundle.</li>
	m-bundle that include one or more potential configurations.<	<li>Let m-bundle-pcfg be the set of media descriptions in
	/t>	m-bundle that include one or more potential configurations.<
	<t> Each media description in m-bundle-pcfg MUST have at	/li>
		<li>Each media description in m-bundle-pcfg <bcp14>MUST</bcp14> have
		at
	least one potential configuration with the same configuratio n	least one potential configuration with the same configuratio n

	number (e.g. "1").</t>	number (e.g., "1").</li>
	<t> For each potential configuration with configuration numb	<li>For each potential configuration with configuration number x
	er x	in m-bundle-pcfg, the offerer <bcp14>MUST</bcp14> ensure tha
	in m-bundle-pcfg, the offerer MUST ensure that if the answer	t if the answerer
	er
	chooses configuration number x in each of the media descript ions	chooses configuration number x in each of the media descript ions
	in m-bundle-pcfg, then the resulting SDP will have all multi plexing	in m-bundle-pcfg, then the resulting SDP will have all multi plexing

	constraints satisfied for those media descriptions.</t>	constraints satisfied for those media descriptions.</li>
	<t> Since it is nearly impossible to define a generic	<li>Since it is nearly impossible to define a generic
	mechanism for various capability extensions, this	mechanism for various capability extensions, this

	document does't provide procedures for dealing	document doesn't provide procedures for dealing
	with the capability extension attributes. However,	with the capability-extension attributes. However,
	<xref target="med-cap-analysis"/> provide	<xref target="med-cap-analysis" format="default"/> provides
	analysis of media capability extension attributes	analysis of media-capability-extension attributes
	as defined in <xref target="RFC6871"/>. </t>	as defined in <xref target="RFC6871" format="default"/>. </l
	</list>	i>
	</t>	</ul>
	<t> The above allows the answerer to easily find multiplexing	<t>The above allows the answerer to easily find multiplexing-compatibl
	compatible	e
	combinations of potential configurations: The answerer simply	combinations of potential configurations. The answerer simply
	choses a	chooses a
	potential configuration (number) that is present in all of the media	potential configuration (number) that is present in all of the media
	descriptions with potential configurations in the bundle.</t>	descriptions with potential configurations in the bundle.</t>

	<t> Note that it is still possible for the offerer to provide additional	<t>Note that it is still possible for the offerer to provide additiona l
	potential configurations with independent configuration number s. The	potential configurations with independent configuration number s. The
	answerer will have to perform more complicated analysis to det ermine	answerer will have to perform more complicated analysis to det ermine
	valid multiplexed combinations of those.</t>	valid multiplexed combinations of those.</t>

	<section title="Example: Transport Capability Multiplexing">	<section numbered="true" toc="default">
	<figure title="">	<name>Example: Transport-Capability Multiplexing</name>
	<artwork><![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=tcap:1 RTP/SAVPF	a=tcap:1 RTP/SAVPF
	a=tcap:2 RTP/SAVP	a=tcap:2 RTP/SAVP
	a=group:BUNDLE audio video	a=group:BUNDLE audio video
	m=audio	m=audio
	a=mid:audio	a=mid:audio
	a=pcfg:1 t=1	a=pcfg:1 t=1
	a=pcfg:2	a=pcfg:2
	m=video	m=video
	a=mid:video	a=mid:video
	a=pcfg:1 t=1	a=pcfg:1 t=1
	a=pcfg:2 t=2	a=pcfg:2 t=2

	]]></artwork>	</sourcecode>
	</figure>
	<t>In the example above, the potential configurations that offer	<t>In this example, the potential configurations that offer
	transport protocol capability of RTP/SAVPF has the same configuratio	transport-protocol capability of RTP/SAVPF have the same configurati
	n	on
	number "1" in both the audio and video media descriptions.</t>	number "1" in both the audio and video media descriptions.</t>
	</section>	</section>

	<section title="Example: Attribute Capability Multiplexing">	<section numbered="true" toc="default">
	<figure title="">	<name>Example: Attribute-Capability Multiplexing</name>
	<artwork><![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=acap:1 a=rtcp-mux	a=acap:1 a=rtcp-mux
	a=acap:2 a=crypto:1 AES_CM_128_HMAC_SHA1_80	a=acap:2 a=crypto:1 AES_CM_128_HMAC_SHA1_80
	inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj\|2^20\|1:32	inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj\|2^20\|1:32
	a=group:BUNDLE audio video	a=group:BUNDLE audio video
	m=audio 49172 RTP/AVP 99	m=audio 49172 RTP/AVP 99
	a=mid:audio	a=mid:audio
	a=pcfg:1 a=1	a=pcfg:1 a=1
	a=pcfg:2	a=pcfg:2
	m=video 560024 RTP/AVP 100	m=video 560024 RTP/AVP 100
	a=mid:video	a=mid:video
	a=pcfg:1 a=1	a=pcfg:1 a=1
	a=pcfg:2 a=2	a=pcfg:2 a=2

	]]></artwork>	</sourcecode>
	</figure>	<t>In this example, the potential configuration number "1" is
	<t>In the example above, the potential configuration number "1" is
	repeated while referring to attribute capability a=rtcp-mux, since	repeated while referring to attribute capability a=rtcp-mux, since
	the behavior is IDENTICAL for the attribute a=rtcp-mux under	the behavior is IDENTICAL for the attribute a=rtcp-mux under
	multiplexing.</t>	multiplexing.</t>
	</section>	</section>
	</section>	</section>
	</section>	</section>

	<section title = "RFC6871 Analysis" anchor="med-cap-analysis">	<section anchor="med-cap-analysis" numbered="true" toc="default">
	<t><xref target="RFC6871"/> extends the capability negotiation	<name>RFC 6871 Analysis</name>
	framework described in <xref target="RFC5939"/> by	<t><xref target="RFC6871" format="default"/> extends the capability nego
		tiation
		framework described in <xref target="RFC5939" format="default"/> by
	defining media capabilities that can be used to indicate	defining media capabilities that can be used to indicate
	and negotiate media types and their associated format	and negotiate media types and their associated format
	parameters. It also allows indication of latent configurations	parameters. It also allows indication of latent configurations
	and session capabilities.</t>	and session capabilities.</t>

	<section title="Recommendation: Dealing with Payload Type Numbers">	<section numbered="true" toc="default">
	<t><xref target="RFC6871"/> defines a new payload type ("pt") paramete	<name>Recommendation: Dealing with Payload Type Numbers</name>
	r	<t><xref target="RFC6871" format="default"/> defines a new payload typ
		e parameter ("pt")
	to be used with the potential, actual, and latent configuration parame ters.	to be used with the potential, actual, and latent configuration parame ters.
	The parameter associates RTP payload type numbers with the	The parameter associates RTP payload type numbers with the

	referenced RTP-based media format capabilities ("a=rmcap") defined	referenced RTP-based media-format capabilities ("a=rmcap") defined
	in <xref target="RFC6871"/> and is appropriate only when the transport	in <xref target="RFC6871" format="default"/> and is appropriate only w
	protocol	hen the
		transport protocol
	uses RTP. This means that the same payload type number can be	uses RTP. This means that the same payload type number can be
	assigned as part of potential or actual configurations in different	assigned as part of potential or actual configurations in different
	media descriptions in a bundle. There are rules for the usage of	media descriptions in a bundle. There are rules for the usage of

	identical Payload Type values across multiplexed "m=" lines as	identical payload type values across multiplexed "m=" lines,
	described in <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"></x	described in <xref target="RFC8843" format="default"/>,
	ref>,	which must be followed here, as well. As described in
	which must be followed here as well. As described in	<xref target="sec-cap-neg-proc" format="default"/>, the use of identic
	<xref target="sec-cap-neg-proc"/>, the use of identical	al
	configuration numbers for compatible configurations in	configuration numbers for compatible configurations in
	different media descriptions that are part of the bundle provides	different media descriptions that are part of the bundle provides
	a way to ensure that the answerer can easily pick compatible	a way to ensure that the answerer can easily pick compatible

	configurations here as well.</t>	configurations here, as well.</t>
	<section title="Example: Attribute Capability Under Shared Payload Typ	<section numbered="true" toc="default">
	e">	<name>Example: Attribute Capability under Shared Payload Type</name>
	<t>The attributes (a=rmcap, a=mfcap) follow the above	<t>The attributes "a=rmcap" and "a=mfcap" follow the above
	recommendations under multiplexing.</t>	recommendations under multiplexing.</t>

	<figure title="">	<sourcecode type="sdp">
	<artwork><![CDATA[
	v=0	v=0
	o=- 25678 753849 IN IP4 192.0.2.1	o=- 25678 753849 IN IP4 192.0.2.1
	s=	s=
	c=IN IP4 192.0.2.1	c=IN IP4 192.0.2.1
	t=0 0	t=0 0
	a=creq:med-v0	a=creq:med-v0
	m=audio 54322 RTP/AVP 96	m=audio 54322 RTP/AVP 96
	a=rtpmap:96 AMR-WB/16000/1	a=rtpmap:96 AMR-WB/16000/1
	a=fmtp:96 mode-change-capability=1; max-red=220;	a=fmtp:96 mode-change-capability=1; max-red=220;
	mode-set=0,2,4,7	mode-set=0,2,4,7

	skipping to change at line 3438 ¶	skipping to change at line 4548 ¶
	m=audio 54322 RTP/AVP 96	m=audio 54322 RTP/AVP 96
	a=rtpmap:96 AMR-WB/16000/1	a=rtpmap:96 AMR-WB/16000/1
	a=fmtp:96 mode-change-capability=1; max-red=220;	a=fmtp:96 mode-change-capability=1; max-red=220;
	mode-set=0,2,4,7	mode-set=0,2,4,7
	a=rmcap:4 audio AMR/8000/1	a=rmcap:4 audio AMR/8000/1
	a=rmcap:5 audio OPUS/48000/2	a=rmcap:5 audio OPUS/48000/2
	a=mfcap:5 minptime=40	a=mfcap:5 minptime=40
	a=mfcap:4 mode-change-capability=1	a=mfcap:4 mode-change-capability=1
	a=pcfg:1 m=4 pt=4:97	a=pcfg:1 m=4 pt=4:97
	a=pcfg:4 m=5 pt=5:101	a=pcfg:4 m=5 pt=5:101

	]]>	</sourcecode>
	</artwork>
	</figure>	<t>In this example, the potential configuration
	<t>In the example above, the potential configuration	number "1" is repeated when referring to media and media-format
	number "1" is repeated when referring to media and media	capability used for the Payload Type 96. This
	format capability used for the Payload Type 96. This	implies that both media capabilities 2 and 4, along
	implies that both the media capability 2 and 4 along	with their media-format capabilities, <bcp14>MUST</bcp14> refer to t
	with their media format capabilities MUST refer to the	he
	same codec configuration, as per the definition of	same codec configuration, as per the definition of
	IDENTICAL-PER-PT.</t>	IDENTICAL-PER-PT.</t>
	</section>	</section>
	</section>	</section>

	<section title="Recommendation: Dealing with Latent Configurations">	<section numbered="true" toc="default">
	<t><xref target="RFC6871"/> adds the notion of a latent configurations	<name>Recommendation: Dealing with Latent Configurations</name>
	,	<t><xref target="RFC6871" format="default"/> adds the notion of a late
	which provides configuration information that may be used to guide a	nt
	subsequent offer/exchange, e.g. by adding another media stream or use	configuration that provides configuration information that may be
		used to guide a
		subsequent offer/exchange -- e.g., by adding another media stream or u
		sing
	alternative codec combinations not currently offered. Latent configura tions	alternative codec combinations not currently offered. Latent configura tions

	have configuration numbers which cannot overlap with the potential con	have configuration numbers that cannot overlap with the potential conf
	figuration	iguration
	numbers <xref target="RFC6871"/>. Supported combinations of potential	numbers <xref target="RFC6871" format="default"/>. Supported combinati
	and	ons of potential and
	latent configurations are indicated by use of the "a=sescap" attribute	latent configurations are indicated by use of the "a=sescap" attribute
	,	;
	however use of this attribute is not recommended with multiplexed medi	however, use of this attribute is not recommended with multiplexed med
	a,	ia,
	since it requires the use of unique configuration numbers across the S DP.	since it requires the use of unique configuration numbers across the S DP.
	Taken together, this means there is no well-defined way to indicate su pported	Taken together, this means there is no well-defined way to indicate su pported
	combinations of latent configurations, or combinations of latent and p otential	combinations of latent configurations, or combinations of latent and p otential
	configurations with multiplexed media. It is still allowed to	configurations with multiplexed media. It is still allowed to

	use the latent configuration attribute, however the limitations	use the latent configuration attribute; however, the limitations
	above will apply. To determine valid combinations, actual	above will apply. To determine valid combinations, actual
	negotiation will have to be attempted subsequently instead.</t>	negotiation will have to be attempted subsequently instead.</t>
	</section>	</section>

	</section>
	</section>	</section>

	<section title="IANA Considerations">	</section>
	<t>[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number	<section numbered="true" toc="default">
	of this document.]</t>	<name>IANA Considerations</name>
	<t> <xref target="sec-mux-cat-iana"/> defines a new subregistry to be	<t><xref target="sec-mux-cat-iana" format="default"/> defines a new
	added by the IANA for identifying the initial registrations for	subregistry, which has been
	various multiplexing categories applicable, as proposed in this document.	added by the IANA, for identifying the initial registrations for
	</t>	various multiplexing categories applicable, as described in this document
	<t>IANA is also requested to add a new column named "Mux Category"	.</t>
		<t>IANA has added a new column named "Mux Category"
	to several of the subregistries in the "Session Description Protocol	to several of the subregistries in the "Session Description Protocol

	(SDP) Parameters" registry. The tables in <xref target="sec-mux-cat-value	(SDP) Parameters" registry. The tables in <xref target="sec-mux-cat-value
	s-iana"/>	s-iana" format="default"/>
	identify name of an entry in the existing subregistry and specify the	identify the names of entries in the existing subregistry and specify the
	value to be put in the new "Mux Category" column of the associated IANA	value to be put in the new "Mux Category" column of the associated IANA

	registry.</t>	registry for each.</t>
	<section title="New 'Multiplexing Categories' subregistry " anchor="sec-m	<section anchor="sec-mux-cat-iana" numbered="true" toc="default">
	ux-cat-iana">	<name>New "Multiplexing Categories" Subregistry</name>
	<t>A new sub-registry needs to be defined called the	<t>A new subregistry has been created. It is called "Multiplexing
	"Multiplexing Categories", with the following registrations	Categories" and has the following registrations
	created initially: "NORMAL", "CAUTION",	initially:</t>
	"IDENTICAL", "TRANSPORT", "SUM", "INHERIT", "IDENTICAL-PER-PT", "SPECI	<table align="left">
	AL"	<thead>
	and "TBD" as defined in this document.</t>	<tr>
	<t>Initial value registration for "Multiplexing Categories".</t>	<th align="left">Multiplexing Categories</th>
		<th align="left">Reference</th>
	<texttable align="left">	</tr>
	<ttcol align='left'>Multiplexing Categories</ttcol>	</thead>
	<ttcol align='left'>Reference</ttcol>	<tbody>
	<c>NORMAL </c><c> RFCXXXX</c>	<tr>
	<c>CAUTION </c><c> RFCXXXX</c>	<td align="left">NORMAL</td>
	<c>IDENTICAL </c><c> RFCXXXX</c>	<td align="left">RFC 8859</td>
	<c>TRANSPORT </c><c> RFCXXXX</c>	</tr>
	<c>SUM </c><c> RFCXXXX</c>	<tr>
	<c>INHERIT </c><c> RFCXXXX</c>	<td align="left">CAUTION</td>
	<c>IDENTICAL-PER-PT </c><c> RFCXXXX</c>	<td align="left">RFC 8859</td>
	<c>SPECIAL </c><c> RFCXXXX</c>	</tr>
	<c>TBD </c><c> RFCXXXX</c>	<tr>
	</texttable>	<td align="left">IDENTICAL</td>
		<td align="left">RFC 8859</td>
		</tr>
		<tr>
		<td align="left">TRANSPORT</td>
		<td align="left">RFC 8859</td>
		</tr>
		<tr>
		<td align="left">SUM</td>
		<td align="left">RFC 8859</td>
		</tr>
		<tr>
		<td align="left">INHERIT</td>
		<td align="left">RFC 8859</td>
		</tr>
		<tr>
		<td align="left">IDENTICAL-PER-PT</td>
		<td align="left">RFC 8859</td>
		</tr>
		<tr>
		<td align="left">SPECIAL</td>
		<td align="left">RFC 8859</td>
		</tr>
		<tr>
		<td align="left">TBD</td>
		<td align="left">RFC 8859</td>
		</tr>
		</tbody>
		</table>


	<t> Further entries can be registered using Standard Actions policies	<t>Further entries can be registered using Standard Actions policies
	outlined in <xref target="RFC5226"/>, which requires IESG review and	outlined in <xref target="RFC8126" format="default"/>, which requires I
	approval and standards-track IETF RFC publication.</t>	ESG review and
	<t> Each registration needs to indicate the multiplexing category value	approval and Standards Track IETF RFC publication.</t>
	to be added to the "Multiplexing Categories" subregistry as defined	<t>Each registration needs to indicate the multiplexing category value
		to be added to the "Multiplexing Categories" subregistry, as defined
	in this section.</t>	in this section.</t>

	<t> Such a registration MUST also indicate the applicability of the	<t>Such a registration <bcp14>MUST</bcp14> also indicate the applicabili ty of the
	newly defined multiplexing category value to various subregistries	newly defined multiplexing category value to various subregistries

	defined at the "Session Description Protocol (SDP) Parameters" registry .</t>	defined in the "Session Description Protocol (SDP) Parameters" registry .</t>
	</section>	</section>

	<section title="'Mux Category' column for subregistries"	<section anchor="sec-mux-cat-values-iana" toc="default" numbered="true">
	anchor="sec-mux-cat-values-iana" toc="default">	<name>"Mux Category" Column for Subregistries</name>
	<t> Each sub-section identifies a subregistry in the "Session Descriptio	<t>Each subsection identifies a subregistry of the "Session Description
	n
	Protocol (SDP) Parameters" registry. The tables list the column that	Protocol (SDP) Parameters" registry. The tables list the column that
	identifies the SDP attribute name/Token/Value from the corresponding	identifies the SDP attribute name/Token/Value from the corresponding
	subregistries and the values to be used for the new "Mux Category" colum n	subregistries and the values to be used for the new "Mux Category" colum n
	to be added.</t>	to be added.</t>

	<t> For the entries in the existing subregistries, under the "Session De	<t>Entries in the existing subregistries of the "Session Description
	scription	Protocol (SDP) Parameters" registry that lack a value for the
	Protocol (SDP) Parameters" registry, that lack a value for the
	"Mux Category" in this specification will get a value of "TBD".</t>	"Mux Category" in this specification will get a value of "TBD".</t>

	<t> The registration policy for updates to the 'Mux Category' column val	<t>The registration policy for updates to the "Mux Category" column valu
	ues	es
	for existing parameters, or when registering new parameters, are beyond	for existing parameters, or when registering new parameters, is beyond t
	the	he
	scope of this document. The registration policy for the affected table is	scope of this document. The registration policy for the affected table is

	defined in <xref target="I-D.ietf-mmusic-rfc4566bis"/>.</t>	defined in <xref target="RFC8866" format="default"/>.</t>
		<section numbered="true" toc="default">
	<section title="Table: SDP bwtype">	<name>Table: SDP bwtype</name>
	<t>The following values are to be added to the 'SDP bwtype' subregistry	<t>The following values have been added to the "bwtype" subregistry
	in the "Session Description Protocol (SDP) Parameters" registry.	of the "Session Description Protocol (SDP) Parameters" registry.
	The references should be updated to point at this RFC as well	The references have been updated to point to this RFC as well
	as the previous references.</t>	as the previous references.</t>

	<texttable align="left">	<table align="left">
	<ttcol align='left'>SDP Name</ttcol>	<thead>
	<ttcol align='left'>Mux Category</ttcol>	<tr>
	<c>CT </c><c>NORMAL </c>	<th align="left">SDP Name</th>
	<c>AS </c><c>SUM </c>	<th align="left">Mux Category</th>
	<c>RS </c><c>SUM </c>	</tr>
	<c>RR </c><c>SUM </c>	</thead>
	<c>TIAS </c><c>SPECIAL </c>	<tbody>
	</texttable>	<tr>
	</section>	<td align="left">CT</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">AS</td>
		<td align="left">SUM</td>
		</tr>
		<tr>
		<td align="left">RS</td>
		<td align="left">SUM</td>
		</tr>
		<tr>
		<td align="left">RR</td>
		<td align="left">SUM</td>
		</tr>
		<tr>
		<td align="left">TIAS</td>
		<td align="left">SPECIAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: attribute-name</name>
		<t>The following values have been added to the "attribute-name"
		(formerly "att-field") subregistry of the "Session Description
		Protocol (SDP) Parameters" registry. The references have been
		updated to point to this RFC as well as the previous references.</t>


	<section title="Table: att-field (session level)">	<t>NOTE: The attributes from <xref target="I-D.ietf-rmt-flute-sdp" for
	<t>The following values are to be added to the "att-field (session level	mat="default"/>
	)"	("flute-tsi", "flute-ch", "FEC-declaration", "FEC-OTI-extension",
	subregistry in the "Session Description Protocol (SDP) Parameters" regis	"content-desc") were not analyzed for their multiplexing behavior,
	try.	due to the expired status of the draft. For the purposes of this
	The references should be updated to point at this RFC as well as the pre	specification, the multiplexing category of "TBD" is assigned. </t>
	vious
	references.</t>
	<texttable align="left">
	<ttcol align='left'>SDP Name</ttcol>
	<ttcol align='left'>Mux Category</ttcol>
	<c>cat </c><c>NORMAL </c>
	<c>keywds </c><c>NORMAL </c>
	<c>type </c><c>NORMAL </c>
	<c>type:broadcast </c><c>NORMAL </c>
	<c>type:H332 </c><c>NORMAL </c>
	<c>type:meeting </c><c>NORMAL </c>
	<c>type:moderated </c><c>NORMAL </c>
	<c>type:test </c><c>NORMAL </c>
	<c>charset </c><c>NORMAL </c>
	<c>charset:iso8895-1 </c><c>NORMAL </c>
	<c>tool </c><c>NORMAL </c>
	<c>ipbcp </c><c>SPECIAL </c>
	<c>group </c><c>NORMAL </c>
	<c>ice-lite </c><c>NORMAL </c>
	<c>ice-options </c><c>NORMAL </c>
	<c>bcastversion </c><c>NORMAL </c>
	<c>3GPP-Integrity-Key </c><c>CAUTION </c>
	<c>3GPP-SDP-Auth </c><c>CAUTION </c>
	<c>alt-group </c><c>CAUTION </c>
	<c>PSCid </c><c>NORMAL </c>
	<c>bc_service </c><c>NORMAL </c>
	<c>bc_program </c><c>NORMAL </c>
	<c>bc_service_package </c><c>NORMAL </c>
	<c>sescap </c><c>CAUTION </c>
	<c>rtsp-ice-d-m </c><c>TBD </c>
	</texttable>
	</section>
	<section title="Table: att-field (both session and media level)">
	<t> The following values are to be added to the "att-field (both session
	and media level)" subregistry in the "Session Description Protocol (SDP)
	Parameters" registry. The references should be updated to point at this
	RFC
	as well as the previous references. </t>
	<t> NOTE: The attributes from draft-ietf-rmt-flute-sdp ('flute-tsi',
	'flute-ch', 'FEC-declaration', 'FEC-OTI-extension', 'content-desc') were
	not analyzed for their multiplexing behavior due to the expired status o
	f the
	draft. For purposes of this specification, the multiplexing category
	of 'TBD' is assigned. </t>


	<texttable align="left">	<!-- [rfced] Follow-up question re:
	<ttcol align='left'>SDP Name</ttcol>	2. "etag" row from section 15.2.2. needs to be removed as well
	<ttcol align='left'>Mux Category</ttcol>
	<c>recvonly </c><c>NORMAL </c>
	<c>sendrecv </c><c>NORMAL </c>
	<c>sendonly </c><c>NORMAL </c>
	<c>sdplang </c><c>NORMAL </c>
	<c>lang </c><c>NORMAL </c>
	<c>h248item </c><c>SPECIAL </c>
	<c>sqn </c><c>NORMAL </c>
	<c>cdsc </c><c>NORMAL </c>
	<c>cpar </c><c>INHERIT </c>
	<c>cparmin </c><c>SPECIAL </c>
	<c>cparmax </c><c>SPECIAL </c>
	<c>rtcp-xr </c><c>NORMAL </c>
	<c>maxprate </c><c>SPECIAL </c>
	<c>setup </c><c>TRANSPORT </c>
	<c>connection </c><c>TRANSPORT </c>
	<c>key-mgmt </c><c>IDENTICAL </c>
	<c>source-filter </c><c>IDENTICAL </c>
	<c>inactive </c><c>NORMAL </c>
	<c>fingerprint </c><c>TRANSPORT </c>
	<c>flute-tsi </c><c>TBD </c>
	<c>flute-ch </c><c>TBD </c>
	<c>FEC-declaration </c><c>TBD </c>
	<c>FEC-OTI-extension </c><c>TBD </c>
	<c>content-desc </c><c>TBD </c>
	<c>ice-pwd </c><c>TRANSPORT </c>
	<c>ice-ufrag </c><c>TRANSPORT </c>
	<c>stkmstream </c><c>NORMAL </c>
	<c>extmap </c><c>SPECIAL </c>
	<c>qos-mech-send </c><c>TRANSPORT </c>
	<c>qos-mech-recv </c><c>TRANSPORT </c>
	<c>csup </c><c>NORMAL </c>
	<c>creq </c><c>NORMAL </c>
	<c>acap </c><c>INHERIT </c>
	<c>tcap </c><c>INHERIT </c>
	<c>3GPP-QoE-Metrics </c><c>CAUTION </c>
	<c>3GPP-Asset-Information </c><c>CAUTION </c>
	<c>mbms-mode </c><c>CAUTION </c>
	<c>mbms-repair </c><c>CAUTION </c>
	<c>ike-setup </c><c>IDENTICAL </c>
	<c>psk-fingerprint </c><c>IDENTICAL </c>
	<c>multicast-rtcp </c><c>IDENTICAL </c>
	<c>rmcap </c><c>IDENTICAL-PER-PT </c>
	<c>omcap </c><c>NORMAL </c>
	<c>mfcap </c><c>IDENTICAL-PER-PT </c>
	<c>mscap </c><c>INHERIT </c>
	<c>3gpp.iut.replication </c><c>TBD </c>
	<c>bcap </c><c>INHERIT </c>
	<c>ccap </c><c>IDENTICAL </c>
	<c>icap </c><c>NORMAL </c>
	<c>3gpp_sync_info </c><c>NORMAL </c>
	<c>3gpp_MaxRecvSDUSize </c><c>NORMAL </c>
	<c>etag </c><c>CAUTION </c>
	<c>duplication-delay </c><c>NORMAL </c>
	<c>range </c><c>CAUTION </c>
	<c>control </c><c>CAUTION </c>
	<c>mtag </c><c>CAUTION </c>
	<c>ts-refclk </c><c>NORMAL </c>
	<c>mediaclk </c><c>NORMAL </c>
	<c>calgextmap </c><c>NORMAL </c>
	</texttable>
	</section>
	<section title="Table: att-field (media level only)">
	<t> The following values are to be added to the
	"att-field (media level only)" registry in the
	"Session Description Protocol (SDP) Parameters" registry.
	The references should be updated to point at this RFC as
	well as the previous references. </t>


	<texttable align="left">	The IANA registry
	<ttcol align='left'>SDP Name</ttcol>	(https://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml#sdp-att-fiel
	<ttcol align='left'>Mux Category</ttcol>	d)
	<c>ptime </c><c>IDENTICAL-PER-PT </c>	lists this document as a reference for etag. So, should the etag row be
	<c>orient </c><c>NORMAL </c>	restored in Section 15.2.2, or should the IANA registry be updated to remove
	<c>orient:portrait </c><c>NORMAL </c>	this document as a reference? (If the latter, we will send a request to
	<c>orient:landscape </c><c>NORMAL </c>	IANA.)
	<c>orient:seascape </c><c>NORMAL </c>	-->
	<c>framerate </c><c>IDENTICAL-PER-PT </c>
	<c>quality </c><c>NORMAL </c>
	<c>rtpmap </c><c>IDENTICAL-PER-PT </c>
	<c>fmtp </c><c>IDENTICAL-PER-PT </c>
	<c>rtpred1 </c><c>CAUTION </c>
	<c>rtpred2 </c><c>CAUTION </c>
	<c>T38FaxVersion </c><c>TBD </c>
	<c>T38MaxBitRate </c><c>TBD </c>
	<c>T38FaxFillBitRemoval </c><c>TBD </c>
	<c>T38FaxTranscodingMMR </c><c>TBD </c>
	<c>T38FaxTranscodingJBIG </c><c>TBD </c>
	<c>T38FaxRateManagement </c><c>TBD </c>
	<c>T38FaxMaxBuffer </c><c>TBD </c>
	<c>T38FaxMaxDatagram </c><c>TBD </c>
	<c>T38FaxUdpEC </c><c>TBD </c>
	<c>maxptime </c><c>IDENTICAL-PER-PT </c>
	<c>des </c><c>CAUTION </c>
	<c>curr </c><c>CAUTION </c>
	<c>conf </c><c>CAUTION </c>
	<c>mid </c><c>NORMAL </c>
	<c>rtcp </c><c>TRANSPORT </c>
	<c>rtcp-fb </c><c>IDENTICAL-PER-PT </c>
	<c>label </c><c>NORMAL </c>
	<c>T38VendorInfo </c><c>TBD </c>
	<c>crypto </c><c>TRANSPORT </c>
	<c>eecid </c><c>CAUTION </c>
	<c>aalType </c><c>CAUTION </c>
	<c>capability </c><c>CAUTION </c>
	<c>qosClass </c><c>CAUTION </c>
	<c>bcob </c><c>CAUTION </c>
	<c>stc </c><c>CAUTION </c>
	<c>upcc </c><c>CAUTION </c>
	<c>atmQOSparms </c><c>CAUTION </c>
	<c>atmTrfcDesc </c><c>CAUTION </c>
	<c>abrParms </c><c>CAUTION </c>
	<c>abrSetup </c><c>CAUTION </c>
	<c>bearerType </c><c>CAUTION </c>
	<c>lij </c><c>CAUTION </c>
	<c>anycast </c><c>CAUTION </c>
	<c>cache </c><c>CAUTION </c>
	<c>bearerSigIE </c><c>CAUTION </c>
	<c>aalApp </c><c>CAUTION </c>
	<c>cbrRate </c><c>CAUTION </c>
	<c>sbc </c><c>CAUTION </c>
	<c>clkrec </c><c>CAUTION </c>
	<c>fec </c><c>CAUTION </c>
	<c>prtfl </c><c>CAUTION </c>
	<c>structure </c><c>CAUTION </c>
	<c>cpsSDUsize </c><c>CAUTION </c>
	<c>all2CPS </c><c>CAUTION </c>
	<c>all2CPSSDUrate </c><c>CAUTION </c>
	<c>aal2sscs3661unassured </c><c>CAUTION </c>
	<c>aal2sscs3661assured </c><c>CAUTION </c>
	<c>aal2sscs3662 </c><c>CAUTION </c>
	<c>aal5sscop </c><c>CAUTION </c>
	<c>atmmap </c><c>CAUTION </c>
	<c>silenceSupp </c><c>CAUTION </c>
	<c>ecan </c><c>CAUTION </c>
	<c>gc </c><c>CAUTION </c>
	<c>profileDesc </c><c>CAUTION </c>
	<c>vsel </c><c>CAUTION </c>
	<c>dsel </c><c>CAUTION </c>
	<c>fsel </c><c>CAUTION </c>
	<c>onewaySel </c><c>CAUTION </c>
	<c>codecconfig </c><c>CAUTION </c>
	<c>isup_usi </c><c>CAUTION </c>
	<c>uiLayer1_Prot </c><c>CAUTION </c>
	<c>chain </c><c>CAUTION </c>
	<c>floorctrl </c><c>TBD </c>
	<c>confid </c><c>NORMAL </c>
	<c>userid </c><c>NORMAL </c>
	<c>floorid </c><c>NORMAL </c>
	<c>FEC </c><c>NORMAL </c>
	<c>accept-types </c><c>TBD </c>
	<c>accept-wrapped-types </c><c>TBD </c>
	<c>max-size </c><c>TBD </c>
	<c>path </c><c>TBD </c>
	<c>dccp-service-code </c><c>CAUTION </c>
	<c>rtcp-mux </c><c>IDENTICAL </c>
	<c>candidate </c><c>TRANSPORT </c>
	<c>ice-mismatch </c><c>NORMAL </c>
	<c>remote-candidates </c><c>TRANSPORT </c>
	<c>SRTPAuthentication </c><c>TBD </c>
	<c>SRTPROCTxRate </c><c>TBD </c>
	<c>rtcp-rsize </c><c>IDENTICAL </c>
	<c>file-selector </c><c>TBD </c>
	<c>file-transfer-id </c><c>TBD </c>
	<c>file-disposition </c><c>TBD </c>
	<c>file-date </c><c>TBD </c>
	<c>file-icon </c><c>TBD </c>
	<c>file-range </c><c>TBD </c>
	<c>depend </c><c>IDENTICAL-PER-PT </c>
	<c>ssrc </c><c>NORMAL </c>
	<c>ssrc-group </c><c>NORMAL </c>
	<c>rtcp-unicast </c><c>IDENTICAL </c>
	<c>pcfg </c><c>SPECIAL </c>
	<c>acfg </c><c>SPECIAL </c>
	<c>zrtp-hash </c><c>TRANSPORT </c>
	<c>X-predecbufsize </c><c>CAUTION </c>
	<c>X-initpredecbufperiod </c><c>CAUTION </c>
	<c>X-initpostdecbufperiod </c><c>CAUTION </c>
	<c>X-decbyterate </c><c>CAUTION </c>
	<c>3gpp-videopostdecbufsize </c><c>CAUTION </c>
	<c>framesize </c><c>CAUTION </c>
	<c>3GPP-SRTP-Config </c><c>CAUTION </c>
	<c>alt </c><c>CAUTION </c>
	<c>alt-default-id </c><c>CAUTION </c>
	<c>3GPP-Adaption-Support </c><c>CAUTION </c>
	<c>mbms-flowid </c><c>CAUTION </c>
	<c>fec-source-flow </c><c>SPECIAL </c>
	<c>fec-repair-flow </c><c>SPECIAL </c>
	<c>repair-window </c><c>SPECIAL </c>
	<c>rams-updates </c><c>CAUTION </c>
	<c>imageattr </c><c>IDENTICAL-PER-PT </c>
	<c>cfw-id </c><c>NORMAL </c>
	<c>portmapping-req </c><c>CAUTION </c>
	<c>g.3gpp.cat </c><c>NORMAL </c>
	<c>g.3gpp.crs </c><c>NORMAL </c>
	<c>ecn-capable-rtp </c><c>IDENTICAL </c>
	<c>visited-realm </c><c>TRANSPORT </c>
	<c>secondary-realm </c><c>TRANSPORT </c>
	<c>omr-s-cksum </c><c>NORMAL </c>
	<c>omr-m-cksum </c><c>NORMAL </c>
	<c>omr-codecs </c><c>NORMAL </c>
	<c>omr-m-att </c><c>NORMAL </c>
	<c>omr-s-att </c><c>NORMAL </c>
	<c>omr-m-bw </c><c>NORMAL </c>
	<c>omr-s-bw </c><c>NORMAL </c>
	<c>msrp-cema </c><c>TBD </c>
	<c>dccp-port </c><c>CAUTION </c>
	<c>resource </c><c>NORMAL </c>
	<c>channel </c><c>NORMAL </c>
	<c>cmid </c><c>NORMAL </c>
	<c>content </c><c>NORMAL </c>
	<c>lcfg </c><c>SPECIAL </c>
	<c>loopback </c><c>NORMAL </c>
	<c>loopback-source </c><c>NORMAL </c>
	<c>loopback-mirror </c><c>NORMAL </c>
	<c>chatroom </c><c>TBD </c>
	<c>altc </c><c>TRANSPORT </c>
	<c>T38FaxMaxIFP </c><c>TBD </c>
	<c>T38FaxUdpECDepth </c><c>TBD </c>
	<c>T38FaxUdpFECMaxSpan </c><c>TBD </c>
	<c>T38ModemType </c><c>TBD </c>
	<c>cs-correlation </c><c>TBD </c>
	<c>rtcp-idms </c><c>NORMAL </c>
	</texttable>
	</section>
	<section title="Table: att-field (source level)">
	<t>The following values are to be added to the
	"att-field (source level)" registry in the
	"Session Description Protocol (SDP) Parameters" registry.
	The references should be updated to point at this RFC as
	well as the previous references. </t>


	<texttable align="left">	<table align="left">
	<ttcol align='left'>SDP Name</ttcol>	<thead>
	<ttcol align='left'>Mux Category</ttcol>	<tr>
	<c>cname </c><c>NORMAL </c>	<th align="left">SDP Name</th>
	<c>previous-ssrc </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c>fmtp </c><c>IDENTICAL-PER-PT </c>	</tr>
	<c>ts-refclk </c><c>NORMAL </c>	</thead>
	<c>mediaclk </c><c>NORMAL </c>	<tbody>
	</texttable>	<tr>
	</section>	<td align="left">cat</td>
	<section title="Table: content SDP Parameters">	<td align="left">NORMAL</td>
	<t>The following values are to be added to the	</tr>
	"content SDP Parameters" subregistry in the	<tr>
	"Session Description Protocol (SDP) Parameters" registry.	<td align="left">keywds</td>
	The references should be updated to point at this RFC	<td align="left">NORMAL</td>
	as well as the previous references. </t>	</tr>
		<tr>
		<td align="left">type</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">type:broadcast</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">type:H332</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">type:meeting</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">type:moderated</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">type:test</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">charset</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">charset:iso8895-1</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">tool</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">ipbcp</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">group</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">ice-lite</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">ice-options</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">bcastversion</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">3GPP-Integrity-Key</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">3GPP-SDP-Auth</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">alt-group</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">PSCid</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">bc_service</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">bc_program</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">bc_service_package</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">sescap</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">rtsp-ice-d-m</td>
		<td align="left">TBD</td>
		</tr>


	<texttable align="left">	<!-- (both session and media level) -->
	<ttcol align='left'>SDP Name</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<td align="left">recvonly</td>
	<c>slides </c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c>speaker </c><c>NORMAL </c>	</tr>
	<c>sl </c><c>NORMAL </c>	<tr>
	<c>main </c><c>NORMAL </c>	<td align="left">sendrecv</td>
	<c>alt </c><c>NORMAL </c>	<td align="left">NORMAL</td>
	</texttable>	</tr>
	</section>	<tr>
	<section title="Table: Semantics for the 'group' SDP Attribute">	<td align="left">sendonly</td>
	<t>The following values are to be added to the	<td align="left">NORMAL</td>
	"Semantics for the "group" SDP Attribute" subregistry in the	</tr>
		<tr>
		<td align="left">sdplang</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">lang</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">h248item</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">sqn</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">cdsc</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">cpar</td>
		<td align="left">INHERIT</td>
		</tr>
		<tr>
		<td align="left">cparmin</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">cparmax</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">rtcp-xr</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">maxprate</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">setup</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">connection</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">key-mgmt</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">source-filter</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">inactive</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">fingerprint</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">flute-tsi</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">flute-ch</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">FEC-declaration</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">FEC-OTI-extension</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">content-desc</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">ice-pwd</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">ice-ufrag</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">stkmstream</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">extmap</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">qos-mech-send</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">qos-mech-recv</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">csup</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">creq</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">acap</td>
		<td align="left">INHERIT</td>
		</tr>
		<tr>
		<td align="left">tcap</td>
		<td align="left">INHERIT</td>
		</tr>
		<tr>
		<td align="left">3GPP-QoE-Metrics</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">3GPP-Asset-Information</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">mbms-mode</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">mbms-repair</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">ike-setup</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">psk-fingerprint</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">multicast-rtcp</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">rmcap</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">omcap</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">mfcap</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">mscap</td>
		<td align="left">INHERIT</td>
		</tr>
		<tr>
		<td align="left">3gpp.iut.replication</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">bcap</td>
		<td align="left">INHERIT</td>
		</tr>
		<tr>
		<td align="left">ccap</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">icap</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">etag</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">duplication-delay</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">range</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">control</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">mtag</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">ts-refclk</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">mediaclk</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">calgextmap</td>
		<td align="left">NORMAL</td>
		</tr>

		<!-- (media level only) -->

		<tr>
		<td align="left">ptime</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">orient</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">orient:portrait</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">orient:landscape</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">orient:seascape</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">framerate</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">quality</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">rtpmap</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">fmtp</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">rtpred1</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">rtpred2</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">T38FaxVersion</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38MaxBitRate</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxFillBitRemoval</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxTranscodingMMR</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxTranscodingJBIG</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxRateManagement</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxMaxBuffer</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxMaxDatagram</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxUdpEC</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">maxptime</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">des</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">curr</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">conf</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">mid</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">rtcp</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">rtcp-fb</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">label</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">T38VendorInfo</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">crypto</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">eecid</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">aalType</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">capability</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">qosClass</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">bcob</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">stc</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">upcc</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">atmQOSparms</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">atmTrfcDesc</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">abrParms</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">abrSetup</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">bearerType</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">lij</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">anycast</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">cache</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">bearerSigIE</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">aalApp</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">cbrRate</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">sbc</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">clkrec</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">fec</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">prtfl</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">structure</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">cpsSDUsize</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">aal2CPS</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">aal2CPSSDUrate</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">aal2sscs3661unassured</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">aal2sscs3661assured</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">aal2sscs3662</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">aal5sscop</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">atmmap</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">silenceSupp</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">ecan</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">gc</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">profileDesc</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">vsel</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">dsel</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">fsel</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">onewaySel</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">codecconfig</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">isup_usi</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">uiLayer1_Prot</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">chain</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">floorctrl</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">confid</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">userid</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">floorid</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">FEC</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">accept-types</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">accept-wrapped-types</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">max-size</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">path</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">dccp-service-code</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">rtcp-mux</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">candidate</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">ice-mismatch</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">remote-candidates</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">SRTPAuthentication</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">SRTPROCTxRate</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">rtcp-rsize</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">file-selector</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">file-transfer-id</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">file-disposition</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">file-date</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">file-icon</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">file-range</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">depend</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">ssrc</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">ssrc-group</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">rtcp-unicast</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">pcfg</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">acfg</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">zrtp-hash</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">X-predecbufsize</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">X-initpredecbufperiod</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">X-initpostdecbufperiod</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">X-decbyterate</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">3gpp-videopostdecbufsize</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">framesize</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">3GPP-SRTP-Config</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">alt</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">alt-default-id</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">3GPP-Adaption-Support</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">mbms-flowid</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">fec-source-flow</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">fec-repair-flow</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">repair-window</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">rams-updates</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">imageattr</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">cfw-id</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">portmapping-req</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">ecn-capable-rtp</td>
		<td align="left">IDENTICAL</td>
		</tr>
		<tr>
		<td align="left">visited-realm</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">secondary-realm</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">omr-s-cksum</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">omr-m-cksum</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">omr-codecs</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">omr-m-att</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">omr-s-att</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">omr-m-bw</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">omr-s-bw</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">msrp-cema</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">dccp-port</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">resource</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">channel</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">cmid</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">content</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">lcfg</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">loopback</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">loopback-source</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">loopback-mirror</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">chatroom</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">altc</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">T38FaxMaxIFP</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxUdpECDepth</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38FaxUdpFECMaxSpan</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">T38ModemType</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">cs-correlation</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">rtcp-idms</td>
		<td align="left">NORMAL</td>
		</tr>

		<!-- (source level)-->

		<tr>
		<td align="left">cname</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">previous-ssrc</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">fmtp</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">ts-refclk</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">mediaclk</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: content SDP Parameters</name>
		<t>The following values have been added to the
		"content SDP Parameters" subregistry of the
	"Session Description Protocol (SDP) Parameters" registry.	"Session Description Protocol (SDP) Parameters" registry.

	The references should be updated to point at this RFC as well as	The references have been updated to point to this RFC
		as well as the previous references. </t>
		<table align="left">
		<thead>
		<tr>
		<th align="left">SDP Name</th>
		<th align="left">Mux Category</th>
		</tr>
		</thead>
		<tbody>
		<tr>
		<td align="left">slides</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">speaker</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">sl</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">main</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">alt</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">g.3gpp.cat</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">g.3gpp.crs</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: Semantics for the "group" SDP Attribute</name>
		<t>The following values have been added to the
		"Semantics for the 'group' SDP Attribute" subregistry of the
		"Session Description Protocol (SDP) Parameters" registry.
		The references have been updated to point to this RFC as well as
	the previous references.</t>	the previous references.</t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Token</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Token</th>
	<c>LS </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c>FID </c><c>NORMAL </c>	</tr>
	<c>SRF </c><c>NORMAL </c>	</thead>
	<c>ANAT </c><c>CAUTION </c>	<tbody>
	<c>FEC </c><c>NORMAL </c>	<tr>
	<c>FEC-FR </c><c>NORMAL </c>	<td align="left">LS</td>
	<c>CS </c><c>NORMAL </c>	<td align="left">NORMAL</td>
	<c>DDP </c><c>NORMAL </c>	</tr>
	<c>DUP </c><c>NORMAL </c>	<tr>
	</texttable>	<td align="left">FID</td>
	</section>	<td align="left">NORMAL</td>
	<section title="Table: 'rtcp-fb' Attribute Values">	</tr>
	<t>The following values are to be added to the	<tr>
	" 'rtcp-fb' Attribute Values" subregistry in the	<td align="left">SRF</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">ANAT</td>
		<td align="left">CAUTION</td>
		</tr>
		<tr>
		<td align="left">FEC</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">FEC-FR</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">CS</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">DDP</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">DUP</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: "rtcp-fb" Attribute Values</name>
		<t>The following values have been added to the
		"'rtcp-fb' Attribute Values" subregistry of the
	"Session Description Protocol (SDP) Parameters" registry.	"Session Description Protocol (SDP) Parameters" registry.

	The references should be updated to point at this RFC as well as	The references have been updated to point to this RFC as well as
	the previous references.</t>	the previous references.</t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Value Name</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Value Name</th>
	<c>ack </c><c>IDENTICAL-PER-PT </c>	<th align="left">Mux Category</th>
	<c>app </c><c>SPECIAL </c>	</tr>
	<c>ccm </c><c>IDENTICAL-PER-PT </c>	</thead>
	<c>nack </c><c>IDENTICAL-PER-PT </c>	<tbody>
	<c>trr-int </c><c>IDENTICAL-PER-PT </c>	<tr>
	</texttable>	<td align="left">ack</td>
	</section>	<td align="left">IDENTICAL-PER-PT</td>
	<section title="Table: 'ack' and 'nack' Attribute Values">	</tr>
	<t>The following values are to be added to the	<tr>
	" 'ack' and 'nack' Attribute Values" subregistry in the	<td align="left">app</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">ccm</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">nack</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">trr-int</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: "ack" and "nack" Attribute Values</name>
		<t>The following values have been added to the
		"'ack' and 'nack' Attribute Values" subregistry of the
	"Session Description Protocol (SDP) Parameters" registry.	"Session Description Protocol (SDP) Parameters" registry.

	The references should be updated to point at this RFC as	The references have been updated to point to this RFC as
	well as the previous references.</t>	well as the previous references.</t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Value Name</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Value Name</th>
	<c>sli </c><c>IDENTICAL-PER-PT </c>	<th align="left">Mux Category</th>
	<c>pli </c><c>IDENTICAL-PER-PT </c>	</tr>
	<c>rpsi </c><c>IDENTICAL-PER-PT </c>	</thead>
	<c>app </c><c>SPECIAL </c>	<tbody>
	<c>rai </c><c>IDENTICAL-PER-PT </c>	<tr>
	<c>tllei </c><c>IDENTICAL-PER-PT </c>	<td align="left">sli</td>
	<c>pslei </c><c>IDENTICAL-PER-PT </c>	<td align="left">IDENTICAL-PER-PT</td>
	<c>ecn </c><c>IDENTICAL </c>	</tr>
	</texttable>	<tr>
	</section>	<td align="left">pli</td>
	<section title="Table: 'depend' SDP Attribute Values">	<td align="left">IDENTICAL-PER-PT</td>
		</tr>
	<t> The following values are to be added to the	<tr>
	" 'depend' SDP Attribute Values" subregistry in the	<td align="left">rpsi</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">app</td>
		<td align="left">SPECIAL</td>
		</tr>
		<tr>
		<td align="left">rai</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">tllei</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">pslei</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">ecn</td>
		<td align="left">IDENTICAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: "depend" SDP Attribute Values</name>
		<t>The following values have been added to the
		"'depend' SDP Attribute Values" subregistry of the
	"Session Description Protocol (SDP) Parameters" registry.	"Session Description Protocol (SDP) Parameters" registry.

	The references should be updated to point at this RFC	The references have been updated to point to this RFC
	as well as the previous references. </t>	as well as the previous references. </t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Token</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Token</th>
	<c>lay </c><c>IDENTICAL-PER-PT </c>	<th align="left">Mux Category</th>
	<c>mdc </c><c>IDENTICAL-PER-PT </c>	</tr>
	</texttable>	</thead>
	</section>	<tbody>
	<section title="Table: 'cs-correlation' Attribute Values">	<tr>
		<td align="left">lay</td>
	<t> The following values are to be added to the	<td align="left">IDENTICAL-PER-PT</td>
	" "cs-correlation" Attribute Values" subregistry in the	</tr>
		<tr>
		<td align="left">mdc</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: "cs-correlation" Attribute Values</name>
		<t>The following values have been added to the
		"'cs-correlation' Attribute Values" subregistry of the
	"Session Description Protocol (SDP) Parameters" registry.	"Session Description Protocol (SDP) Parameters" registry.

	The references should be updated to point at this RFC	The references have been updated to point to this RFC
	as well as the previous references. </t>	as well as the previous references. </t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Value</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Value</th>
	<c>callerid </c><c>TBD </c>	<th align="left">Mux Category</th>
	<c>uuie </c><c>TBD </c>	</tr>
	<c>dtmf </c><c>TBD </c>	</thead>
	<c>external </c><c>TBD </c>	<tbody>
	</texttable>	<tr>
	</section>	<td align="left">callerid</td>
	<section title="Table: Semantics for the 'ssrc-group' SDP Attribute">	<td align="left">TBD</td>
		</tr>
	<t> The following values are to be added to the	<tr>
	Semantics for the "Semantics for the "ssrc-group" SDP Attribute"	<td align="left">uuie</td>
	subregistry in the "Session Description Protocol (SDP) Parameters"	<td align="left">TBD</td>
	registry. The references should be updated to point at this RFC	</tr>
		<tr>
		<td align="left">dtmf</td>
		<td align="left">TBD</td>
		</tr>
		<tr>
		<td align="left">external</td>
		<td align="left">TBD</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: Semantics for the "ssrc-group" SDP Attribute</name>
		<t>The following values have been added to the "Semantics for the
		'ssrc-group' SDP Attribute"
		subregistry of the "Session Description Protocol (SDP) Parameters"
		registry. The references have been updated to point to this RFC
	as well as the previous references. </t>	as well as the previous references. </t>

		<table align="left">
		<thead>
		<tr>
		<th align="left">Token</th>
		<th align="left">Mux Category</th>
		</tr>
		</thead>
		<tbody>
		<tr>
		<td align="left">FID</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">FEC</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">FEC-FR</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">DUP</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>


	<texttable align="left">	</section>
	<ttcol align='left'>Token</ttcol>	<section numbered="true" toc="default">
	<ttcol align='left'>Mux Category</ttcol>	<name>Table: SDP/RTSP Key Management Protocol Identifiers</name>
	<c>FID </c><c>NORMAL </c>	<t>The following values have been added to the
	<c>FEC </c><c>NORMAL </c>
	<c>FEC-FR </c><c>NORMAL </c>
	<c>DUP </c><c>NORMAL </c>
	</texttable>
	</section>
	<section title="Table: SDP/RTSP key management protocol identifiers">
	<t>The following values are to be added to the
	"SDP/RTSP key management protocol identifiers" subregistry	"SDP/RTSP key management protocol identifiers" subregistry

	in the "Session Description Protocol (SDP) Parameters" registry.	of the "Session Description Protocol (SDP) Parameters" registry.
	The references should be updated to point at this RFC as well as	The references have been updated to point to this RFC as well as
	the previous references.</t>	the previous references.</t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Value Name</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Value Name</th>
	<c>mikey </c><c>IDENTICAL </c>	<th align="left">Mux Category</th>
	</texttable>	</tr>
	</section>	</thead>
	<section title="Table: Codec Control Messages">	<tbody>
	<t> The following values are to be added to the	<tr>
	"Codec Control Messages" subregistry in the	<td align="left">mikey</td>
		<td align="left">IDENTICAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: Codec Control Messages</name>
		<t>The following values have been added to the
		"Codec Control Messages" subregistry of the
	"Session Description Protocol (SDP) Parameters" registry.	"Session Description Protocol (SDP) Parameters" registry.

	The references should be updated to point at this RFC	The references have been updated to point to this RFC
	as well as the previous references. </t>	as well as the previous references. </t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Value Name</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Value Name</th>
	<c>fir </c><c>IDENTICAL-PER-PT </c>	<th align="left">Mux Category</th>
	<c>tmmbr </c><c>IDENTICAL-PER-PT </c>	</tr>
	<c>tstr </c><c>IDENTICAL-PER-PT </c>	</thead>
	<c>vbcm </c><c>IDENTICAL-PER-PT </c>	<tbody>
	</texttable>	<tr>
	</section>	<td align="left">fir</td>
	<section title="Table: QoS Mechanism Tokens">	<td align="left">IDENTICAL-PER-PT</td>
	<t> The following values are to be added to the	</tr>
	"QoS Mechanism Tokens" subregistry in the	<tr>
		<td align="left">tmmbr</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">tstr</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		<tr>
		<td align="left">vbcm</td>
		<td align="left">IDENTICAL-PER-PT</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: QoS Mechanism Tokens</name>
		<t>The following values have been added to the
		"QoS Mechanism Tokens" subregistry of the
	"Session Description Protocol (SDP) Parameters" registry.	"Session Description Protocol (SDP) Parameters" registry.

	The references should be updated to point at this RFC	The references have been updated to point to this RFC
	as well as the previous references. </t>	as well as the previous references. </t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>QoS Mechanism</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">QoS Mechanism</th>
	<c>rsvp </c><c>TRANSPORT </c>	<th align="left">Mux Category</th>
	<c>nsis </c><c>TRANSPORT </c>	</tr>
	</texttable>	</thead>
	</section>	<tbody>
	<section title="Table: SDP Capability Negotiation Option Tags">	<tr>
	<t> The following values are to be added to the	<td align="left">rsvp</td>
		<td align="left">TRANSPORT</td>
		</tr>
		<tr>
		<td align="left">nsis</td>
		<td align="left">TRANSPORT</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: SDP Capability Negotiation Option Tags</name>
		<t>The following values have been added to the
	"SDP Capability Negotiation Option Tags" subregistry	"SDP Capability Negotiation Option Tags" subregistry

	in the "Session Description Protocol (SDP) Parameters" registry.	of the "Session Description Protocol (SDP) Parameters" registry.
	The references should be updated to point at this RFC	The references have been updated to point to this RFC
	as well as the previous references. </t>	as well as the previous references. </t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Option Tag</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Option Tag</th>
	<c>cap-v0 </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c>med-v0 </c><c>NORMAL </c>	</tr>
	<c>bcap-v0 </c><c>NORMAL </c>	</thead>
	<c>ccap-v0 </c><c>NORMAL </c>	<tbody>
	<c>icap-v0 </c><c>NORMAL </c>	<tr>
	</texttable>	<td align="left">cap-v0</td>
	</section>	<td align="left">NORMAL</td>
	<section title="Table: Timestamp Reference Clock Source Parameters">	</tr>
	<t> The following values are to be added to the	<tr>
		<td align="left">med-v0</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">bcap-v0</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">ccap-v0</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">icap-v0</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: Timestamp Reference Clock Source Parameters</name>
		<t>The following values have been added to the
	"Timestamp Reference Clock Source Parameters" subregistry	"Timestamp Reference Clock Source Parameters" subregistry

	in the "Session Description Protocol (SDP) Parameters" registry.	of the "Session Description Protocol (SDP) Parameters" registry.
	The references should be updated to point at this RFC as well as	The references have been updated to point to this RFC as well as
	the previous references. </t>	the previous references. </t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Name</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Name</th>
	<c>ntp </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c>ptp </c><c>NORMAL </c>	</tr>
	<c>gps </c><c>NORMAL </c>	</thead>
	<c>gal </c><c>NORMAL </c>	<tbody>
	<c>glonass </c><c>NORMAL </c>	<tr>
	<c>local </c><c>NORMAL </c>	<td align="left">ntp</td>
	<c>private </c><c>NORMAL </c>	<td align="left">NORMAL</td>
	</texttable>	</tr>
	</section>	<tr>
	<section title="Table: Media Clock Source Parameters">	<td align="left">ptp</td>
	<t> The following values are to be added to the	<td align="left">NORMAL</td>
	"Media Clock Source Parameters" subegistry	</tr>
	in the "Session Description Protocol (SDP) Parameters"	<tr>
	registry. The references should be updated to point at	<td align="left">gps</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">gal</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">glonass</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">local</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">private</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section numbered="true" toc="default">
		<name>Table: Media Clock Source Parameters</name>
		<t>The following values have been added to the
		"Media Clock Source Parameters" subregistry
		of the "Session Description Protocol (SDP) Parameters"
		registry. The references have been updated to point to
	this RFC as well as the previous references. </t>	this RFC as well as the previous references. </t>

		<table align="left">
	<texttable align="left">	<thead>
	<ttcol align='left'>Name</ttcol>	<tr>
	<ttcol align='left'>Mux Category</ttcol>	<th align="left">Name</th>
	<c>sender </c><c>NORMAL </c>	<th align="left">Mux Category</th>
	<c>direct </c><c>NORMAL </c>	</tr>
	<c>IEEE1722 </c><c>NORMAL </c>	</thead>
	</texttable>	<tbody>
		<tr>
		<td align="left">sender</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">direct</td>
		<td align="left">NORMAL</td>
		</tr>
		<tr>
		<td align="left">IEEE1722</td>
		<td align="left">NORMAL</td>
		</tr>
		</tbody>
		</table>
		</section>
	</section>	</section>
	</section>	</section>

	</section>	<section numbered="true" toc="default">
	<section title="Security Considerations">	<name>Security Considerations</name>
	<t>	<t>

	The primary security for RTP including the way it is used here	The primary security considerations for RTP, including the way it is use
	is described in <xref target="RFC3550"/> and <xref target="RFC3711"/>.	d here,
		are described in <xref target="RFC3550" format="default"/> and <xref tar
		get="RFC3711" format="default"/>.
	</t>	</t>

	<t>	<t>
	When multiplexing SDP attributes with the category "CAUTION", the	When multiplexing SDP attributes with the category "CAUTION", the

	implementations should be aware of possible issues as described in	implementations should be aware of possible issues described in
	this specification.	this specification.
	</t>	</t>

	</section>
	<section title="Acknowledgments">
	<t>
	I would like to thank Cullen Jennings, Flemming Andreasen
	for suggesting the categories, contributing text and reviewing
	the draft. I would also link to thank Magnus Westerlund,
	Christer Holmberg, Jonathan Lennox, Bo Burman, Ari Keranen, and
	Dan Wing on suggesting structural changes helping improve the
	document readability.
	</t>
	<t>
	I would like also to thank following experts on their inputs and
	reviews as listed - Flemming Andreasen(5.24,5.32,5.33,14), Rohan Mahy(5.
	57),
	Eric Burger(5.26),Christian Huitema(5.14), Christer Holmberg(5.21,5.26,5
	.51,5.52),
	Richard Ejzak (5.44,5.53,5.54), Colin Perkins(5.7,5.8,5.9,5.58),
	Magnus Westerlund(5.2,5.3,5.9,5.27,5.47,6.1,6.2,6.3,8.3,7),
	Roni Evens(5.12,5.27,8.4), Subha Dhesikan(5.6,10),
	Dan Wing(5.7,5.12,5.35,5.39,5.45), Cullen Jennings (5.40),
	Ali C Begen(5.1,5.20,5.22,5.25,5.38,7.3,8.2,8.4,8.6,9.2,13.1),
	Bo Burman (7.2,7.6), Charles Eckel(5.15,5.27,5.28,9.1,8.5),
	Paul Kyzivat(5.24), Ian Johansson(5.15), Saravanan Shanmugham(5.11),
	Paul E Jones(5.30), Rajesh Kumar(5.48), Jonathan Lennox(5.36,5,15,9.1,11
	.1),
	Mo Zanaty(5.4,5.5,5.23,8.1,8.3,8.5,12.1), Christian Huitema (5.14),
	Qin Wu (5.47 PM-Dir review), Hans Stokking(5.43,5.16),
	Christian Groves (5.48,5.55), Thomas Stach.
	</t>
	<t>
	I would like to thank Chris Lonvick for the SECDIR review, Dan Romascanu
	for th Gen-ART review and Sabrina Tanamal for the IANA review.
	</t>
	<t>
	Thanks to Ben Campbell for AD review suggestions. Thanks to Spencer Dawki
	ns,
	Stephen Farrel, Alissa Cooper, Mirja Kuehlewind and the entire IESG exper
	ts
	for their reviews.
	</t>
	</section>
	<section title="Change Log">
	<t>[RFC EDITOR NOTE: Please remove this section when publishing]</t>
	<t>Changes draft-ietf-mmusic-sdp-mux-attributes-16
	<list style="symbols">
	<t>
	Added a clarification note on when to encode IDENTICAL attribute
	s
	as suggested by Christer.
	</t>
	</list>
	</t>
	<t>Changes draft-ietf-mmusic-sdp-mux-attributes-15
	<list style="symbols">
	<t>
	Updated Mux category for floorctrl to TBD
	</t>
	</list>
	</t>
	<t>Changes draft-ietf-mmusic-sdp-mux-attributes-14
	<list style="symbols">
	<t>
	Incorporated Comments from IESG review :
	<list style="symbols">
	<t>Updated security considerations section to fix the
	incositencies (Spencer's review)</t>
	<t>Updated section 5.36 to align the text with 5.39
	(Stephen's review)</t>
	<t>Updated IANA registration section to make RFC4566bis
	a informative dependency (IETF 98 followup)</t>
	<t>Updated Section 5 to expand 'B' level SDP attributes
	(Dan's review)</t>
	</list>
	</t>
	</list>
	</t>
	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-10 - draft-ietf-mmusi
	c-sdp-mux-attributes-13
	<list style="symbols">
	<t>
	Incorporated Comments from WGLC review and AD Evaluation
	</t>
	</list>
	</t>
	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-10
	<list style="symbols">
	<t>
	Incorporated Comments from Bo Burman for publication request
	</t>
	</list>
	</t>
	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-08 to draft-ietf-mmus
	ic-sdp-mux-attributes-10
	<list style="symbols">
	<t>
	Minor nits and version update to advert expiration
	</t>
	</list>
	</t>
	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-06 to draft-ietf-mmus
	ic-sdp-mux-attributes-08
	<list style="symbols">
	<t>
	Assigned TBD category to all the attributes for whom there
	exists no specification on multiplexing behavior over the
	underlying transport protocol today.
	</t>
	<t>
	Incorporated comments from Flemming and Ari (post last call)
	</t>
	</list>
	</t>

	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-06
	<list style="symbols">
	<t>
	Incorporated last call review comments from Thomas Stach and
	Ari Keranen.
	</t>
	<t>
	Fixed more nits to prep for the LastCall.
	</t>
	</list>
	</t>

	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-05
	<list style="symbols">
	<t>
	Incorporated review comments from Christian Grooves and
	Ari Keranen.
	</t>
	<t>
	Fixed more nits to prep for the LastCall.
	</t>
	</list>
	</t>

	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-04
	<list style="symbols">
	<t>
	Fixed minor nits overall.
	</t>
	<t>
	Updated Acknowledgement Sections
	</t>
	<t>
	Last Call Version.
	</t>
	</list>
	</t>

	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-03
	<list style="symbols">
	<t>
	More re-work on the IANA section.
	</t>
	<t>
	Clean ups preparing for the last call.
	</t>
	</list>
	</t>
	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-02
	<list style="symbols">
	<t>
	Incorporated suggestions from Flemming on Capability Negotiation.
	</t>
	<t>
	Closed open issues from IETF90
	</t>
	<t>
	Added IANA section to list the categories for all the SDP attributes
	anlayzed
	</t>
	<t>
	Lots of cleanup
	</t>
	<t>
	Reformatted Refernces section to use short-form notation
	</t>
	</list>
	</t>
	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-01
	<list style="symbols">
	<t>
	Updated section 15 to provide detailed recommendation on dealing
	with encapsulating attributes. Also updated sections 5.20,
	5.28, 5.29 to refer to Section 15.
	</t>
	<t>
	Added new categories IDENTICAL-PER-PT and INHERIT
	</t>
	<t>
	Updated Sections 16 to add the new categories.
	</t>
	<t>
	Updated Sections 5.1, 5.14, 5.15, 5.38, 8.5 to reflect the
	category IDENTICAL-PER-PT.
	</t>
	<t>
	Reformatted section 4 to add individual categories to their
	own sections.
	</t>
	</list>
	</t>
	<t>Changes from draft-ietf-mmusic-sdp-mux-attributes-00
	<list style="symbols">
	<t>
	Added Section 15 to provide recommendations on multiplexing
	SDP encapsulating attributes. Also updated sections 5.20,
	5.28, 5.29 to refer to Section 15.
	</t>
	<t>
	Updated Section 5.38 to incorporate PM-dir review inputs from
	Qin Wu
	</t>
	<t>
	Updated Sections 5.2,5.14,8.5 to refer to BUNDLE draft for more clar
	ity.
	</t>
	<t>
	Fixed few nits regarding sentence clarity and fill-in the NOTES
	section where information was lacking.
	</t>
	</list>
	</t>
	<t>Changes from draft-nandakumar-mmusic-mux-attributes-05
	<list style="symbols">
	<t>
	Renamed the document to be a WG document.
	</t>
	<t>
	Added Section 14.
	</t>
	<t>
	Updated Open Issues based on IETF88 discussions.
	</t>
	</list>
	</t>
	<t>Changes from draft-nandakumar-mmusic-mux-attributes-04
	<list style="symbols">
	<t>
	Added few OPEN ISSUES that needs to be discussed.
	</t>
	<t>
	Updated sections 5.10,5.23,5,24,5,25,7.2,9.1,5.12,5.27,8.4,
	5.44,5.11,5.4,5.19,10.1,10.5,5.21,10.4,15.1
	</t>
	<t>
	Updated Table Column name Current to Level and improved TRANSPORT
	category explanation on suggestions form Dan Wing.
	</t>
	<t>
	Grouped all the rtcp-fb attribute analysis under a single section
	as suggested by Magnus/
	</t>
	</list>
	</t>

	<t>Changes from draft-nandakumar-mmusic-mux-attributes-03
	<list style="symbols">
	<t> Maintenance change to clean up grammatical nits and wordings.
	</t>
	</list>
	</t>

	<t>Changes from draft-nandakumar-mmusic-mux-attributes-02
	<list style="symbols">
	<t>Updated Sections 5.3,5.5,5.6,5.7,5.9,5.8,5.11,5.13,5.22,5.34,
	5.37,5.40,5.41,5.42,5.43,5.44,5.45,6.1,6.2,6.3,8,3,12.1 based on the
	inputs from the respective RFC Authors.
	</t>
	</list>
	</t>
	<t>Changes from draft-nandakumar-mmusic-mux-attributes-01
	<list style="symbols">
	<t>Replaced Category BAD with NOT-RECOMMENDED.</t>
	<t>Added Category TBD.</t>
	<t>Updated IANA Consideration Section.</t>
	</list>
	</t>
	<t>Changes from draft-nandakumar-mmusic-mux-attributes-00
	<list style="symbols">
	<t>Added new section for dealing with FEC payload types.</t>
	</list>
	</t>
	</section>	</section>
	</middle>	</middle>


	<back>	<back>

	<references title="Normative References">
	&RFC4566;
	&RFC5226;
	&I-D.ietf-mmusic-sdp-bundle-negotiation;

	<reference anchor="RFC2119">
	<front>
	<title abbrev="RFC Key Words">Key words for use in RFCs to Indicate
	Requirement Levels</title>


	<author fullname="Scott Bradner" initials="S." surname="Bradner">	<displayreference target="I-D.ietf-rmt-flute-sdp" to="FLUTE"/>
	<organization>Harvard University</organization>	<references>
		<name>References</name>
	<address>	<references>
	<postal>	<name>Normative References</name>
	<street>1350 Mass. Ave.</street>	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4566.xml"/>
	<street>Cambridge</street>	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.8126.xml"/>
	<street>MA 02138</street>	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
	</postal>	ence.RFC.8174.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
	<phone>- +1 617 495 3864</phone>	ence.RFC.2119.xml"/>


	<email>sob@harvard.edu</email>	<!-- draft-ietf-mmusic-sdp-bundle-negotiation (RFC 8843) -->
	</address>	<reference anchor="RFC8843" target="https://www.rfc-editor.org/info/rfc8843"
	</author>	>
		<front>
		<title>Negotiating Media Multiplexing Using the Session Description Prot
		ocol (SDP)</title>
		<author initials="C" surname="Holmberg" fullname="Christer Holmberg">
		<organization/>
		</author>
		<author initials="H" surname="Alvestrand" fullname="Harald Alvestrand">
		<organization/>
		</author>
		<author initials="C" surname="Jennings" fullname="Cullen Jennings">
		<organization/>
		</author>
		<date month="January" year="2021"/>
		</front>
		<seriesInfo name="RFC" value="8843"/>
		<seriesInfo name="DOI" value="10.17487/RFC8843"/>
		</reference>


	<date month="March" year="1997" />	</references>
		<references>
		<name>Informative References</name>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.2326.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3108.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3264.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3312.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3407.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3524.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3550.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3556.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3605.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3611.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3711.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.3890.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4091.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4145.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4567.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4568.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4570.xml"/>
		<xi:include
		href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.
		4572.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.8122.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4574.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4583.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4585.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4796.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.4975.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5104.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5109.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5159.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.8445.xml"/>
		<xi:include
		href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.
		5285.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.8285.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5432.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5506.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5547.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5576.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5583.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5760.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5761.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5762.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5763.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5888.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5939.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.5956.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6064.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6128.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6189.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6193.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6230.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6236.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6284.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6285.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6364.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6642.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6679.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6714.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6773.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6787.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6849.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6871.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.6947.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7006.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7104.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7197.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7195.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7272.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7273.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7266.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7657.xml"/>
		<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
		ence.RFC.7826.xml"/>


	<area>General</area>	<!-- draft-ietf-mmusic-rfc4566bis (RFC 8866) -->
		<reference anchor="RFC8866" target="https://www.rfc-editor.org/info/rfc8
		866">
		<front>
		<title>SDP: Session Description Protocol</title>
		<author initials="A" surname="Begen" fullname="Ali Begen">
		<organization/>
		</author>
		<author initials="P" surname="Kyzivat" fullname="Paul Kyzivat">
		<organization/>
		</author>
		<author initials="C" surname="Perkins" fullname="Colin Perkins">
		<organization/>
		</author>
		<author initials="M" surname="Handley" fullname="Mark Handley">
		<organization/>
		</author>
		<date month="January" year="2021"/>
		</front>
		<seriesInfo name="RFC" value="8866"/>
		<seriesInfo name="DOI" value="10.17487/RFC8866"/>
		</reference>


	<keyword>keyword</keyword>	<reference anchor="IANA" target="https://www.iana.org/assignments/sdp-pa
	</front>	rameters">
		<front>
		<title>Session Description Protocol (SDP) Parameters</title>
		<author>
		<organization>IANA</organization>
		</author>
		<date/>
		</front>
		</reference>
		<reference anchor="T.38" target="https://www.itu.int/rec/T-REC-T.38/e">
		<front>
		<title>Procedures for real-time Group 3 facsimile communication over
		IP networks</title>
		<seriesInfo name="ITU-T Recommendation" value="T.38"/>
		<author>
		<organization>ITU-T</organization>
		</author>
		<date month="November" year="2015"/>
		</front>
		</reference>
		<reference anchor="H.248.15" target="https://www.itu.int/rec/T-REC-H.248
		.15">
		<front>
		<title>Gateway control protocol: SDP ITU-T H.248 package attribute</
		title>
		<seriesInfo name="ITU-T Recommendation" value="H.248.15"/>
		<author>
		<organization>ITU-T</organization>
		</author>
		<date month="March" year="2013"/>
		</front>
		</reference>
		<reference anchor="Q.1970" target="https://www.itu.int/rec/T-REC-Q.1970-
		200609-I/en">
		<front>
		<title>Q.1970: BICC IP bearer control protocol</title>
		<seriesInfo name="ITU-T Recommendation" value="Q.1970"/>
		<author>
		<organization>ITU-T</organization>
		</author>
		<date month="September" year="2006"/>
		</front>
		</reference>


	<seriesInfo name="BCP" value="14" />	<reference anchor="IP-CALL" target="https://www.3gpp.org/ftp/Specs/html-
		info/24229.htm">
		<front>
		<title>IP multimedia call control protocol based on
		Session Initiation Protocol (SIP)
		and Session Description Protocol (SDP); Stage 3</title>
		<seriesInfo name="Specification" value="24.229"/>
		<author>
		<organization>3GPP</organization>
		</author>
		<date month="September" year="2016"/>
		</front>
		</reference>
		<reference anchor="TISPAN" target="https://www.etsi.org/deliver/etsi_ts/
		183000_183099/183063/02.01.00_60/ts_183063v020100p.pdf">
		<front>
		<title> Telecommunications and Internet converged Services and
		Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3
		specification</title>
		<seriesInfo name="Technical Specification" value="183 063 V2.1.0"/>
		<author>
		<organization>ETSI</organization>
		</author>
		<date month="June" year="2008"/>
		</front>
		</reference>
		<reference anchor="IMS-CAT" target="https://www.3gpp.org/ftp/Specs/html-
		info/24182.htm">
		<front>
		<title>IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT)
		;
		Protocol specification</title>
		<seriesInfo name="Specification" value="24.182"/>
		<author>
		<organization>3GPP</organization>
		</author>
		<date month="January" year="2015"/>
		</front>
		<seriesInfo name="Specification" value="24.182"/>
		</reference>
		<reference anchor="IMS-CRS" target="https://www.3gpp.org/ftp/Specs/html-
		info/24183.htm">
		<front>
		<title>IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS)
		;
		Protocol specification</title>
		<author>
		<organization>3GPP</organization>
		</author>
		<date month="September" year="2016"/>
		</front>
		<seriesInfo name="Specification" value="24.183"/>
		</reference>


	<seriesInfo name="RFC" value="2119" />	<!-- draft-ietf-rmt-flute-sdp-03 is expired -->


	<format octets="4723"	<xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-rm
	target="http://www.rfc-editor.org/rfc/rfc2119.txt" type="TXT" />	t-flute-sdp.xml"/>


	<format octets="17491"	<!-- draft-ietf-bfcpbis-rfc4583bis: 8856 -->
	target="http://xml.resource.org/public/rfc/html/rfc2119.html"	<reference anchor='RFC8856' target="https://www.rfc-editor.org/info/rfc8856">
	type="HTML" />	<front>
		<title>Session Description Protocol (SDP) Format for Binary Floor Control
		Protocol (BFCP) Streams</title>
		<author initials='G' surname='Camarillo' fullname='Gonzalo Camarillo'>
		<organization />
		</author>
		<author initials='T' surname='Kristensen' fullname='Tom Kristensen'>
		<organization />
		</author>
		<author initials='C.' surname='Holmberg' fullname='Christer Holmberg'>
		<organization />
		</author>
		<date month='January' year='2021' />
		</front>
		<seriesInfo name="RFC" value="8856"/>
		<seriesInfo name="DOI" value="10.17487/RFC8856"/>
		</reference>


	<format octets="5777"	</references>
	target="http://xml.resource.org/public/rfc/xml/rfc2119.xml"
	type="XML" />
	</reference>
	</references>	</references>

		<section numbered="false" toc="default">
		<name>Acknowledgements</name>
		<t>
		I would like to thank <contact fullname="Cullen Jennings"/> and
		<contact fullname="Flemming Andreasen"/>
		for suggesting the categories, contributing text, and reviewing
		the draft of this document. I would also like to thank <contact
		fullname="Magnus Westerlund"/>,
		<contact fullname="Christer Holmberg"/>, <contact fullname="Jonathan
		Lennox"/>, <contact fullname="Bo Burman"/>, <contact fullname="Ari Kerä
		nen"/>, and
		<contact fullname="Dan Wing"/> for suggesting structural changes that im
		proved the
		document's readability.
		</t>
		<t>
		I would like also to thank the following experts for their inputs
		and
		reviews as listed: </t>


	<references title="Informative References">	<ul empty="true" spacing="compact">
	&RFC2326;	<li><t><contact fullname="Flemming Andreasen"/> (5.24, 5.32, 5.33, 14),</
	&RFC3108;	t></li>
	&RFC3264;	<li><t><contact fullname="Rohan Mahy"/> (5.54),</t></li>
	&RFC3312;	<li><t><contact fullname="Eric Burger"/> (5.26),</t></li>
	&RFC3407;	<li><t><contact fullname="Christian Huitema"/> (5.14),</t></li>
	&RFC3524;	<li><t><contact fullname="Christer Holmberg"/> (5.21, 5.26, 12.2, 12.3),<
	&RFC3550;	/t></li>
	&RFC3556;	<li><t><contact fullname="Richard Ejzak"/> (5.44, 5.50, 5.51),</t></li>
	&RFC3605;	<li><t><contact fullname="Colin Perkins"/> (5.7, 5.8, 5.9, 5.55),</t></li
	&RFC3611;	>
	&RFC3711;	<li><t><contact fullname="Magnus Westerlund"/> (5.2, 5.3, 5.9, 5.27, 5.4
	&RFC3890;	7, 6.1 - 6.3, 8.3, 7),</t></li>
	&RFC4091;	<li><t><contact fullname="Roni Even"/> (5.12, 5.27, 8.4),</t></li>
	&RFC4145;	<li><t><contact fullname="Subha Dhesikan"/> (5.6, 10),</t></li>
	&RFC4567;	<li><t><contact fullname="Dan Wing"/> (5.7, 5.12, 5.35, 5.39, 5.45),</t>
	&RFC4568;	</li>
	&RFC4570;	<li><t><contact fullname="Cullen Jennings"/> (5.40),</t></li>
	&RFC4572;	<li><t><contact fullname="Ali C Begen"/> (5.1, 5.20, 5.22, 5.25, 5.38, 7
	&RFC4574;	.3, 8.2, 8.4, 8.6, 9.2, 13.1),</t></li>
	&RFC4583;	<li><t><contact fullname="Bo Burman"/> (7.2, 7.6),</t></li>
	&RFC4585;	<li><t><contact fullname="Charles Eckel"/> (5.15, 5.27, 5.28, 9.1, 8.5),<
	&RFC4796;	/t></li>
	&RFC4975;	<li><t><contact fullname="Paul Kyzivat"/> (5.24),</t></li>
	&RFC5104;	<li><t><contact fullname="Ian Johansson"/> (5.15),</t></li>
	&RFC5109;	<li><t><contact fullname="Saravanan Shanmugham"/> (5.11),</t></li>
	&RFC5159;	<li><t><contact fullname="Paul E Jones"/> (5.30),</t></li>
	&RFC5245;	<li><t><contact fullname="Rajesh Kumar"/> (5.48),</t></li>
	&RFC5285;	<li><t><contact fullname="Jonathan Lennox"/> (5.36, 5, 15, 9.1, 11.1),</t
	&RFC5432;	></li>
	&RFC5506;	<li><t><contact fullname="Mo Zanaty"/> (5.4, 5.5, 5.23, 8.1, 8.3, 8.5, 1
	&RFC5547;	2.1),</t></li>
	&RFC5576;	<li><t><contact fullname="Christian Huitema "/> (5.14),</t></li>
	&RFC5583;	<li><t><contact fullname="Qin Wu"/> (5.47, PM-Dir review),</t></li>
	&RFC5760;	<li><t><contact fullname="Hans Stokking"/> (5.43, 5.16),</t></li>
	&RFC5761;	<li><t><contact fullname="Christian Groves"/> (5.48, 5.52), and</t></li>
	&RFC5762;	<li><t><contact fullname="Thomas Stach"/>.</t></li>
	&RFC5763;	</ul>
	&RFC5888;
	&RFC5939;
	&RFC5956;
	&RFC6064;
	&RFC6128;
	&RFC6189;
	&RFC6193;
	&RFC6230;
	&RFC6236;
	&RFC6284;
	&RFC6285;
	&RFC6364;
	&RFC6642;
	&RFC6679;
	&RFC6714;
	&RFC6773;
	&RFC6787;
	&RFC6849;
	&RFC6871;
	&RFC6947;
	&RFC7006;
	&RFC7104;
	&RFC7195;
	&RFC7197;
	&RFC7272;
	&RFC7273;
	&RFC7266;
	&RFC7657;
	&I-D.ietf-mmusic-rfc4566bis;

	<reference anchor='IANA'
	target="http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xm
	l">
	<front>
	<title>Session Description Protocol (SDP) Parameters</title>
	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor='T.38' target="http://www.itu.int/rec/T-REC-T.38/e">
	<front>
	<title>Procedures for real-time Group 3 facsimile communication over I
	P networks</title>
	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor='H.248.15' target="http://www.itu.int/rec/T-REC-H.248.15
	">
	<front>
	<title> Gateway control protocol: SDP H.248 package attribute</title>
	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor='Q.1970'
	target="https://www.itu.int/rec/T-REC-Q.1970-200609-I/en">
	<front>
	<title> Q.1970 : BICC IP bearer control protocol</title>
	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor='R3GPPTS26.114'
	target="http://www.3gpp.org/DynaReport/26114.htm">
	<front>
	<title>IP multimedia Subsystem : Media Handling and interaction</title
	>
	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor='R3GPPTS24.229'
	target="http://www.3gpp.org/ftp/Specs/html-info/24229.htm">
	<front>
	<title>IP multimedia call control protocol based on
	Session Initiation Protocol (SIP)
	and Session Description Protocol (SDP);</title>
	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor='R3GPPTS183.063'
	target="http://www.etsi.org/deliver/etsi_ts/183000_183099/183063/02.01.0
	0_60/ts_183063v020100p.pdf">
	<front>
	<title> TISPAN - IMS based ITPV Stage 3 specification.</title>

	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor='R3GPPTS24.182'
	target="http://www.3gpp.org/ftp/Specs/html-info/24182.htm">
	<front>
	<title>IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT);
	Protocol specification</title>
	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor='R3GPPTS24.183'
	target="http://www.3gpp.org/ftp/Specs/html-info/24183.htm">
	<front>
	<title>IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS);
	Protocol specification</title>
	<author/>
	<date/>
	</front>
	</reference>


	</references>	<t>
		I would like to thank <contact fullname="Chris Lonvick"/> for the SECD
		IR
		review, <contact fullname="Dan Romascanu"/>
		for the Gen-ART review, and <contact fullname="Sabrina Tanamal"/> for
		the IANA review.
		</t>
		<t>
		Thanks to <contact fullname="Ben Campbell"/> for Area Director review
		suggestions. Thanks to <contact fullname="Spencer Dawkins"/>,
		<contact fullname="Stephen Farrel"/>, <contact fullname="Alissa Cooper"/>
		,
		<contact fullname="Mirja Kühlewind"/>, and the entire IESG
		for their reviews.
		</t>
		</section>
	</back>	</back>
	</rfc>	</rfc>

End of changes. 397 change blocks.
	3814 lines changed or deleted	5882 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/