<?xmlversion="1.0" encoding="US-ASCII"?>version='1.0' encoding='utf-8'?> <!DOCTYPE rfc SYSTEM"rfc2629.dtd" [ <!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-sdp-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"> ]>"rfc2629-xhtml.ent"> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?><?rfc toc="yes" ?> <?rfc symrefs="yes" ?> <?rfc strict="yes" ?> <?rfc compact="yes" ?> <?rfc sortrefs="yes" ?> <?rfc colonspace="yes" ?> <?rfc rfcedstyle="no" ?> <?rfc tocdepth="4"?><rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std"docName="draft-ietf-mmusic-sdp-mux-attributes-17" ipr="trust200902">ipr="trust200902" number="8859" submissionType="IETF" consensus="true" obsoletes="" updates="" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3" docName="draft-ietf-mmusic-sdp-mux-attributes-17"> <!-- xml2rfc v2v3 conversion 2.30.0 --> <front> <title abbrev="SDP Attribute Multiplexing">A Framework forSDPSession Description Protocol (SDP) AttributeswhenWhen Multiplexing</title> <seriesInfo name="RFC" value="8859"/> <author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar"> <organization>Cisco</organization> <address> <postal> <street>170 West Tasman Drive</street> <city>San Jose</city> <region>CA</region> <code>95134</code><country>USA</country><country>United States of America</country> </postal> <email>snandaku@cisco.com</email> </address> </author> <dateday="28" month="February" year="2018"/> <area>MMUSIC</area>month="January" year="2021"/> <area>ART</area> <workgroup>MMUSIC</workgroup> <abstract> <t>The purpose of this specification is to provide a framework for analyzing the multiplexing characteristics of Session Description Protocol (SDP) attributes when SDP is used to negotiate the usage of a single 5-tuple for sending and receiving media associated with multiple media descriptions.</t> <t>This specification also categorizes the existing SDP attributes based on the framework described herein.</t> </abstract> </front> <middle> <sectiontitle="Introduction" anchor="sec-intro"> <t> SDPanchor="sec-intro" numbered="true" toc="default"> <name>Introduction</name> <t>SDP defines several attributes for capturing characteristics that apply to the individual media descriptions (described by "m="lines")lines) and the overall multimedia session.TypicallyTypically, different media types (audio, video, etc.) described using different media descriptions represent separate RTP sessions that are carried over individualtransport layertransport-layer flows.HoweverHowever, <xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>target="RFC8843" format="default"/> defines a way to use a single address:port combination (BUNDLE address) for receiving media associated with multiple SDP media descriptions. This would, forexampleexample, allow the usage of a single set of Interactive Connectivity Establishment (ICE) <xreftarget="RFC5245"/>target="RFC8445" format="default"/> candidates for multiple media descriptions.ThisThis, inturnturn, has made it necessary to understand the interpretation and usage of the SDP attributes defined for the multiplexed media descriptions.</t><t> Given<t>Given the number of SDP attributes registered with the <xreftarget="IANA"></xref>target="IANA" format="default"/> and the possibility of new attributes being defined in the future, there is need for a framework to analyze these attributes for their applicability in the transport multiplexinguse-cases.</t> <t> Theuse cases.</t> <t>The document starts with providing the motivation for requiring such a framework. This is followed by introduction to the SDP attribute analysisframework/procedures,framework and procedures, following which several sections apply the framework to the SDP attributes registered with the <xreftarget="IANA"></xref>.target="IANA" format="default"/>. </t> </section> <sectiontitle="Terminology"> <t>5-tuple: Anumbered="true" toc="default"> <name>Terminology</name> <dl> <dt>5-tuple:</dt><dd>A collection of the following values: source address, source port, destination address, destination port, and transport-layerprotocol.</t> <t>3GPP: Thirdprotocol.</dd> <dt>3GPP:</dt><dd>Third Generation Partnership Project; seehttp://www.3gpp.org<eref target="https://www.3gpp.org" brackets="angle"/> for more information about thisorganization.</t> <t>Theorganization.</dd> </dl> <t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xreftarget="RFC2119"></xref>.</t>target="RFC2119" format="default"/> <xref target="RFC8174" format="default"/> when, and only when, they appear in all capitals, as shown here. </t> </section> <sectiontitle="Motivation"> <t>Thenumbered="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 complicationsofinvolved in setting upICE <xref target="RFC5245"></xref> and Datagram Transport Layer Security (DTLS) basedSecure Real-time Transport Protocol (SRTP) <xreftarget="RFC5763"></xref>target="RFC5763"/> transports for use byRTP, reasons to conserveRTP based on ICE <xref target="RFC8445"/> and Datagram Transport Layer Security (DTLS). These procedures motivate conservation of ports bindings on the Network Address Translators(NAT), forms a requirement to try and reduce the number of transport level flows needed.(NATs). This necessity has resulted in the definition of ways, such as that described in <xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>target="RFC8843" format="default"/>, to multiplex RTP over a single transport flow in order to preserve network resources such as port numbers. This imposes further restrictions on applicability of the SDP attributes as they are defined today.</t> <t>The specific problem is that there are attribute combinationswhichthat make sense when specified on independent "m=" lines -- as with classical SDP -- that do not make sense when those "m=" lines are then multiplexed over the same transport. To give an obvious example, ICE permits each "m=" line to have an independently specifiedice-ufrag"ice-ufrag" attribute. However, if the media from multiple "m=" lines is multiplexed over the same ICE component, then the meaning of media-levelice-ufrag"ice-ufrag" attributes becomes muddled.</t> <t>At the time of writing thisdocumentdocument, there are close to 250 SDP attributes registered with the <xreftarget="IANA"></xref>target="IANA" format="default"/>, and more will be added in the future. There is no clearly defined procedure to establish the validity/applicability of these attributes when used with transport multiplexing.</t> </section> <sectiontitle="SDPanchor="sec-mux-fwork" numbered="true" toc="default"> <name>SDP Attribute AnalysisFramework" anchor="sec-mux-fwork">Framework</name> <t>Attributes in an SDP session description can be defined at thesession-level or media-levelsession level, media level, orsource-level.source level. Informally, there are various semantic groupings for these attributes. One such grouping could benotesasbelow:</t> <t> <list style="symbols"> <t>Attributesfollows:</t> <ul spacing="normal"> <li>Attributes related to media content such as media type, encodingschemesschemes, and payloadtypes.</t> <t>Attributestypes.</li> <li>Attributes specifying media transport characteristicslikesuch as RTP/RTP Control Protocol (RTCP) port numbers, networkaddressesaddresses, andQOS.</t> <t>MetadataQoS.</li> <li>Metadata description attributes capturing session timing and origininformation.</t> <t>Attributesinformation.</li> <li>Attributes establishing relationships between mediadescriptionsdescriptions, such as grouping framework <xreftarget="RFC5888"/></t> </list> </t>target="RFC5888" format="default"/>.</li> </ul> <t>The proposed framework analyzes the SDP attributes usage under multiplexing and assigns each SDP attribute to an appropriate multiplexing category. Since the multiplexing categories defined in this specification are independent of any informal semantic groupings of the SDP attributes, the categorizations assigned are normative.</t> <sectiontitle="Category: NORMAL">numbered="true" toc="default"> <name>Category: NORMAL</name> <t>The attributes in the NORMAL category can be independently specified whenmultiplexedmultiplexed, and they retain their original semantics.</t><t> </t><t>In the example given below, the direction and label attributes are independently specified for audio and video "m=" lines. These attributes are not impacted by multiplexing these media streams over a singletransport layertransport-layer flow.</t><figure> <artwork align="left" alt="" height="" name="" type="" width="" xml:space="preserve"><![CDATA[<sourcecode type="sdp"> v=0 o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com s= c=IN IP4 host.atlanta.example.com t=0 0 m=audio 49172 RTP/AVP 99 a=sendonly a=label:1 a=rtpmap:99 iLBC/8000 m=video 49172 RTP/AVP 31 a=recvonly a=label:2 a=rtpmap:31 H261/90000]]></artwork> </figure> <t> </t></sourcecode> </section> <sectiontitle="Category: CAUTION"> <t>Thenumbered="true" toc="default"> <name>Category: CAUTION</name> <t>It is not advisable to multiplex with the attributes in the CAUTIONcategory are advised against multiplexingcategory, since their usage under multiplexing might lead to incorrect behavior.</t><t> </t><t>Example: Multiplexing media descriptions over a single Datagram Congestion Control Protocol (DCCP) transport <xreftarget="RFC5762"/>target="RFC5762" format="default"/> is notrecommendedrecommended, since DCCPbeingis aconnection orientedconnection-oriented protocol and therefore doesn't allow multiple connections on the same 5-tuple.</t><figure> <artwork align="left" alt="" height="" name="" type="" width="" xml:space="preserve"><![CDATA[<sourcecode type="sdp"> v=0 o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com s= c=IN IP4 client.biloxi.example.com t=0 0 m=video 5004 DCCP/RTP/AVP 99 a=rtpmap:99 h261/9000 a=dccp-service-code:SC=x52545056 a=setup:passive a=connection:new m=video 5004 DCCP/RTP/AVP 100 a=rtpmap:100 h261/9000 a=dccp-service-code:SC=x5254504f a=setup:passive a=connection:new]]></artwork> </figure> <t> </t></sourcecode> </section> <sectiontitle="Category: IDENTICAL">numbered="true" toc="default"> <name>Category: IDENTICAL</name> <t>The attributes and their associated values (if any) in the IDENTICAL categoryMUST<bcp14>MUST</bcp14> be repeated across all the media descriptions under multiplexing.</t><t> </t><t>Attributes such as rtcp-mux fall into this category. Since RTCP reporting is done per RTP session, RTCPMultiplexing MUSTmultiplexing <bcp14>MUST</bcp14> be enabled for both the audio and video "m=" lines if they are transported over a single 5-tuple.</t><figure> <artwork align="left" alt="" height="" name="" type="" width="" xml:space="preserve"><![CDATA[<sourcecode type="sdp"> v=0 o=bob 2890844527 2890844527 IN IP4 client.biloxi.example.com s= c=IN IP4 client.biloxi.example.com t=0 0 m=audio 34567 RTP/AVP 97 a=rtcp-mux m=video 34567 RTP/AVP 31 a=rtpmap:31 H261/90000 a=rtcp-mux]]></artwork> </figure> <t> </t></sourcecode> <t>Note:EventhoughEven though IDENTICAL attributes must be repeated across all media descriptions under multiplexing, they might not always be explicitly encoded across all media descriptions. <xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>target="RFC8843" format="default"/> defines rules for when attributes and their values are implicitly applied to media description.</t> </section> <sectiontitle="Category: SUM">numbered="true" toc="default"> <name>Category: SUM</name> <t>The attributes in the SUM category can be set as they are normallyusedused, but software using them in the multiplexing scenarioMUST<bcp14>MUST</bcp14> apply the sum of all the attributes being multiplexed instead of trying to use them independently. This is typically used for bandwidth or otherrate limitingrate-limiting attributes to the underlying transport.</t><t> </t><t> The software parsing the SDP samplebelow,below should use the aggregate Application Specific (AS) bandwidth value from the individual media descriptions to determine the AS value for the multiplexed session. Thus the calculated AS value would be 256+64 kilobits per second for the given example. </t><figure> <artwork align="left" alt="" height="" name="" type="" width="" xml:space="preserve"><![CDATA[<sourcecode type="sdp"> v=0 o=test 2890844526 2890842807 IN IP4 client.biloxi.example.com c=IN IP4 client.biloxi.example.com t=0 0 m=audio 49170 RTP/AVP 0 b=AS:64 m=video 51372 RTP/AVP 31 b=AS:256]]></artwork> </figure> <t> </t></sourcecode> </section> <sectiontitle="Category: TRANSPORT"> <t> Thenumbered="true" toc="default"> <name>Category: TRANSPORT</name> <t>The attributes in the TRANSPORT category can be set normally for multiple items in a multiplexedgroupgroup, but the softwareMUST<bcp14>MUST</bcp14> pick the one that's associated with the "m=" line whose information is used for setting up the underlying transport.</t><t> </t><t>In the example below, the "a=crypto" attribute is defined for both the audio andthevideo "m=" lines. The video media line'sa=crypto"a=crypto" attribute is chosen since itsmidMID value (bar) appears first in thea=group:BUNDLE"a=group:BUNDLE" line. This is due to the BUNDLE grouping semantic <xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>target="RFC8843" format="default"/>, which mandates that the values from the "m=" line corresponding to the mid appearing first on thea=group:BUNDLE"a=group:BUNDLE" linetobe considered for setting up the RTPTransport.</t> <figure> <artwork align="left" alt="" height="" name="" type="" width="" xml:space="preserve"><![CDATA[transport.</t> <sourcecode type="sdp"> v=0 o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com s= c=IN IP4 host.atlanta.example.com t=0 0 a=group:BUNDLE bar foo m=audio 49172 RTP/AVP 99 a=mid:foo a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 a=rtpmap:99 iLBC/8000 m=video 51374 RTP/AVP 31 a=mid:bar a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32 a=rtpmap:96 H261/90000]]></artwork> </figure> <t> </t></sourcecode> </section> <sectiontitle="Category: INHERIT">numbered="true" toc="default"> <name>Category: INHERIT</name> <t>The attributes in the INHERIT category encapsulate other SDP attributes or parameters. These attributes inherit their multiplexing characteristics from the attributes or parameters they encapsulate. Such attributes are defined in <xreftarget="RFC3407"/>,target="RFC3407" format="default"/>, <xreftarget="RFC5939"/>target="RFC5939" format="default"/>, and <xreftarget="RFC6871"/>target="RFC6871" format="default"/> as part of a generic framework for indicating and negotiating capabilities in the SDP related to transport, media, and mediaformat related capabilities in the SDP.format. </t> <t>The inheritance manifests itself when the encapsulated attribute or parameter is being leveraged. In the case of SDP Capability Negotiation <xreftarget="RFC5939"/>target="RFC5939" format="default"/>, for example, this occurs when a capability (encapsulating attribute) is used as part of a configuration; the configuration inherits the multiplexing category of each of its constituent (encapsulated) attributes and parameters. The inherited attributesMUST<bcp14>MUST</bcp14> be coherent in order to form a valid configuration from a multiplexing point of view (see <xreftarget="sec-encap"/>target="sec-encap" format="default"/> for further details).</t><t> </t> <figure> <artwork align="left" alt="" height="" name="" type="" width="" xml:space="preserve"><![CDATA[<sourcecode type="sdp"> v=0 o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com s= c=IN IP4 host.atlanta.example.com t=0 0 m=video 3456 RTP/AVP 100 a=rtpmap:100 VP8/90000 a=fmtp:100 max-fr=30;max-fs=8040 a=sqn: 0 a=cdsc: 1 video RTP/AVP 100 a=cpar: a=rtcp-mux m=video 3456 RTP/AVP 101 a=rtpmap:101 VP8/90000 a=fmtp:100 max-fr=15;max-fs=1200 a=cdsc: 2 video RTP/AVP 101 a=cpar:a=rtcp-mux ]]></artwork> </figure>a=rtcp-mux</sourcecode> <t>Inthe abovethis example, the category IDENTICAL is inherited by thecpar encapsulated rtcp-muxcpar-encapsulated "rtcp-mux" attribute.</t><t> </t></section> <sectiontitle="Category: IDENTICAL-PER-PT"> <t> Thenumbered="true" toc="default"> <name>Category: IDENTICAL-PER-PT</name> <t>The attributes in the IDENTICAL-PER-PT category define the RTP payload configuration onper Payload Typethe basis of the payload type, andMUSTthey <bcp14>MUST</bcp14> have identical values across all the media descriptions for a given RTPPayload Typepayload type when repeated. ThesePayload Typespayload types identify the same codec configuration as defined inthe Section 10.1.2 of<xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>target="RFC8843" sectionFormat="of" section="9.1"/> under this context.</t><t> </t><t>In the SDP example below, Payload Types 96 and 97 are repeated across all the video "m="lineslines, and all thepayload specificpayload-specific parameters(ex: rtpmap,(for example, rtpmap and fmtp) areidenticalidentical. (Note: some line breaksincludedare due to formattingonly).</t> <figure> <artwork align="left" alt="" height="" name="" type="" width="" xml:space="preserve"><![CDATA[only.)</t> <sourcecode type="sdp"> v=0 o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com s= c=IN IP4 host.atlanta.example.com t=0 0 a=group:BUNDLE cam1 cam2 m=video 96 97 a=mid:cam1 a=rtpmap:96 H264/90000 a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000; max-mbps=108000; max-br=1000 a=rtpmap:97 H264/90000 a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000; max-mbps=7200; max-br=200 m=video 96 97 a=mid:cam2 a=rtpmap:96 H264/90000 a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000; max-mbps=108000; max-br=1000 a=rtpmap:97 H264/90000 a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000; max-mbps=7200;max-br=200 ]]></artwork> </figure> <t> </t>max-br=200</sourcecode> </section> <sectiontitle="Category: SPECIAL">numbered="true" toc="default"> <name>Category: SPECIAL</name> <t>For the attributes in the SPECIAL category, the text in the specification defining the attributeMUST<bcp14>MUST</bcp14> be consulted for further handling when multiplexed. </t> <t>As anexampe,example, for the attributeextmap"extmap" <xreftarget="RFC5285"/>,target="RFC5285" format="default"/>, the specification defining the extension needs to bereferredconsulted to understand the multiplexing implications.</t> </section> <sectiontitle="Category: TBD">numbered="true" toc="default"> <name>Category: TBD</name> <t>The attributes in the TBD category have not been analyzed under the proposed multiplexing framework andSHOULD NOT<bcp14>SHOULD NOT</bcp14> be multiplexed.</t> </section> </section> <sectiontitle="Analysisanchor="sec-cur-analysis" numbered="true" toc="default"> <name>Analysis of ExistingAttributes" anchor="sec-cur-analysis" >Attributes</name> <t>This section analyzes attributes listed in <xreftarget="IANA"/>,target="IANA" format="default"/>, grouped under the IETF document that defines them.</t> <t>The "Level" column indicates whether the attribute is currently specified as:</t><t> <list style="symbols"> <t>S<ul spacing="normal"> <li>S -- Sessionlevel</t> <t>Mlevel</li> <li>M -- Medialevel</t> <t>Blevel</li> <li>B -- Both (Implies either a session level or a media levelattribute)</t> <t>SRattribute)</li> <li>SR -- Source-level (for a single SSRC) <xreftarget="RFC5576"/></t> </list> </t>target="RFC5576" format="default"/></li> </ul> <t>The "Mux Category" column identifies the multiplexing category assignedper attributeto each attribute, and the "Notes" column captures additional informative details regarding the assigned category, wherever necessary.</t> <sectiontitle="RFC4566: SDP">numbered="true" toc="default"> <name>RFC 4566: SDP</name> <t><xreftarget="RFC4566"/>target="RFC4566" format="default"/> defines SDP that is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation.</t><texttable title="5.1 RFC4566 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <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><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 valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c> <c>M </c><c>IDENTICAL-PER-PT</c> <c> </c><c> </c><c> </c><c> </c> <c>maxptime </c><c>Theconfiguration.</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 valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </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>Theconfiguration.</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 valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </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>Theconfiguration.</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 valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c><c>M </c> <c>IDENTICAL-PER-PT</c> <c> </c><c> </c><c> </c><c> </c> <c>fmtp </c><c>Theconfiguration.</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 valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </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>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> <sectiontitle="RFC4585: RTP/AVPF">numbered="true" toc="default"> <name>RFC 4585: RTP/AVPF</name> <t><xreftarget="RFC4585"/>target="RFC4585" format="default"/> defines an extension to the Audio-visual Profile (AVP) that enables receivers to provide, statistically, more immediate feedback to the senders and thus allows for short-term adaptation and efficient feedback-based repair mechanisms to be implemented.</t><texttable title="5.2 RFC4585 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rtcp-fb </c><c>Since<table align="center"> <name>RFC 4585 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">rtcp-fb</td> <td align="left">Since RTCP feedback attributes arePayload Type (PT) scoped,scoped by payload type (PT), their valuesMUST<bcp14>MUST</bcp14> be identical for a given PT across the multiplexed "m="lines.</c><c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>lines.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5761:numbered="true" toc="default"> <name>RFC 5761: Multiplexing RTP andRTCP">RTCP</name> <t><xreftarget="RFC5761"/>target="RFC5761" format="default"/> discusses issues that arise when multiplexing RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port. It describes when such multiplexing is and is not appropriate, and it explains how the SDP can be used to signal multiplexed sessions.</t><texttable title="5.3 RFC5761 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rtcp-mux </c><c>RTP<table align="center"> <name>RFC 5761 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">rtcp-mux</td> <td align="left">RTP and RTCPMultiplexingmultiplexing affects the entire RTPsession </c> <c>M </c><c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>session.</td> <td align="left">M</td> <td align="left">IDENTICAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC3312:numbered="true" toc="default"> <name>RFC 3312: Integration of Resource Management andSIP">SIP</name> <t><xreftarget="RFC3312"/>target="RFC3312" format="default"/> defines a generic framework for preconditions, which are extensible through IANA registration. This document also discusses how network quality of service can be made a precondition for establishment of sessions initiated by the Session Initiation Protocol (SIP). These preconditions require that the participant reserve network resources before continuing with the session.</t><texttable title="5.4 RFC3312 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>des </c><c>Refer to notes below </c> <c>M </c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>conf </c><c>Refer to notes below </c> <c>M </c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>curr </c><c>Refer to notes below </c> <c>M </c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 3312 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">des</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <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 results inSessionsession establishment failures due to inability to meetrightthe requested resourcereservations requested.</t>reservations.</t> </section> <sectiontitle="RFC4574:numbered="true" toc="default"> <name>RFC 4574: SDPLabel Attribute ">"label" Attribute</name> <t><xreftarget="RFC4574"/>target="RFC4574" format="default"/> defines a new SDP media-level attribute: "label". The "label" attribute carries a pointer to a media stream in the context of an arbitrary network application that uses SDP. The sender of the SDP document can attach the "label" attribute to a particular media stream or streams. The application can then use the provided pointer to refer to each particular media stream in its context.</t><texttable title="5.5 RFC4574 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>label </c><c>Not Impacted </c><c>M</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 4574 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">label</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5432: QOSnumbered="true" toc="default"> <name>RFC 5432: QoS Mechanism Selection inSDP">SDP</name> <t><xreftarget="RFC5432"/>target="RFC5432" format="default"/> defines proceduresto negotiate QOSfor negotiating QoS mechanisms using the SDP offer/answer model.</t><texttable title="5.6 RFC5432 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>qos-mech-send </c> <c><table align="center"> <name>RFC 5432 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">qos-mech-send</td> <td align="left"> Refer to <xreftarget="SecqostokenAnalysis"/> </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> <c>qos-mech-recv </c> <c>Refer to <xref target="SecqostokenAnalysis"/> </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>target="SecqostokenAnalysis" format="default"/>.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> <tr> <td align="left">qos-mech-recv</td> <td align="left">Refer to <xref target="SecqostokenAnalysis" format="default"/>.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC4568:numbered="true" toc="default"> <name>RFC 4568: SDP SecurityDescriptions">Descriptions</name> <t><xreftarget="RFC4568"/>target="RFC4568" format="default"/> definesaan SDP cryptographic attribute for unicast media streams. The attribute describes a cryptographic key and other parameters that serve to configure security for a unicast media stream in either a single message or a roundtrip exchange.</t><texttable title="5.7 RFC4568 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>crypto </c><c>crypto<table align="center"> <name>RFC 4568 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">crypto</td> <td align="left">crypto attributeMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow </c> <c>M </c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>flow. </td> <td align="left">M</td> <td align="left">TRANSPORT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5762:numbered="true" toc="default"> <name>RFC 5762: RTP overDCCP">DCCP</name> <t>RTP is a widely used transport for real-time multimedia on IP networks. DCCP is a transport protocol that provides desirable services for real-time applications. <xreftarget="RFC5762"/>target="RFC5762" format="default"/> specifies a mapping of RTP onto DCCP, along with associated signaling, such that real-time applications can make use of the services provided by DCCP.</t><texttable title="5.8 RFC5762 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Current</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>dccp-service-code </c><c><table align="center"> <name>RFC 5762 Attribute Analysis</name> <thead> <tr> <th align="left">Name</th> <th align="left">Notes</th> <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"> IfRFC6773RFC 6773 is not being used in addition to RFC5762, the port in the "m=" line is a DCCP port.DCCP beingBeing aconnection oriented protocolconnection-oriented protocol, DCCP does not allow multiple connections on the same5-tuple </c> <c>M </c><c>CAUTION </c><c> </c> <c> </c><c> </c><c> </c> </texttable>5-tuple.</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> </tbody> </table> <t> NOTE: IfRFC6773RFC 6773 is being used in addition toRFC5762RFC 5762, andprovided thatthe DCCP-in-UDP layer has additional demultiplexing, then itcanmay be possible to use different DCCP service codes for each DCCP flow, given each uses a different DCCP port.AlthoughHowever, doing so might conflict with the media type of the "m=" line. None of this is standardizedyetyet, and it wouldn't work as explained. Hence performing multiplexing is not recommended even in this alternate scenario.</t> </section> <sectiontitle="RFC6773:numbered="true" toc="default"> <name>RFC 6773: DCCP-UDPEncapsulation">Encapsulation</name> <t><xreftarget="RFC6773"/>target="RFC6773" format="default"/> specifies an alternative encapsulation of DCCP, referred to as DCCP-UDP. This encapsulation allows DCCP to be carried through the current generation of Network Address Translation (NAT)middle boxesmiddleboxes without modification of thosemiddle boxes.</t> <texttable title="5.9 RFC6773 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>dccp-port </c><c>middleboxes.</t> <table align="center"> <name>RFC 6773 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">dccp-port</td> <td align="left"> Multiplexing is not recommended due to potential conflict between the port used for DCCPen/decapsulationencapsulation/decapsulation and theRTP </c> <c>M </c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable>RTP.</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> </tbody> </table> <t> NOTE:RFC6773 is about tunneling DCCP in UDP,RFC 6773 allows DCCP-UDP encapsulation, with the UDP port being the port of the DCCPen-/de-capsulationencapsulation/decapsulation service. This encapsulation allows arbitrary DCCP packets to beencapsulatedencapsulated, and the DCCP port chosen can conflict with the port chosen for the RTP traffic.For multiplexingMultiplexing several DCCP-in-UDP encapsulations on the same UDP port with no RTP traffic on the same port implies collapsing several DCCP port spaces together.This canWhether orcannot work dependingnot this works depends on the nature of DCCP encapsulation and portschoices thus renderingchoices; itto beis thus very application dependent. </t> </section> <sectiontitle="RFC5506:numbered="true" toc="default"> <name>RFC 5506: Reduced-Size RTCP in RTPProfile">Profile</name> <t><xreftarget="RFC5506"/>target="RFC5506" format="default"/> discusses benefits and issues that arise when allowing RTCP packets to be transmitted with reduced size.</t><texttable title="5.10 RFC5506 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rtcp-rsize </c><c>Reduced size<table align="center"> <name>RFC 5506 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">rtcp-rsize</td> <td align="left">Reduced-size RTCP affects the entire RTPsession </c> <c>M </c><c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>session.</td> <td align="left">M</td> <td align="left">IDENTICAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6787:numbered="true" toc="default"> <name>RFC 6787: Media Resource Control Protocol Version2">2</name> <t>The Media Resource Control Protocol Version 2 (MRCPv2) allows client hosts to control media service resources such as speech synthesizers, recognizers, verifiers, and identifiers residing in servers on the network. MRCPv2 is not a "stand-alone"protocol --protocol; it relies on other protocols, such as the SIP, to coordinate MRCPv2 clients andservers,servers and manage session between them, and SDP to describe, discover, and exchange capabilities. It also depends on SIP and SDP to establish the media sessions and associated parameters between the media source or sink and the media server. Once this is done, the MRCPv2 exchange operates over the control session established above, allowing the client to control themedia processingmedia-processing resources on the speech resource server. <xreftarget="RFC6787"/>target="RFC6787" format="default"/> defines attributes for this purpose.</t><texttable title="5.11 RFC6787 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>resource </c><c>Not Impacted </c><c>M </c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>channel </c><c>Not Impacted </c><c>M </c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>cmid </c><c>Not Impacted </c><c>M </c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 6787 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">resource</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <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> <sectiontitle="RFC5245: ICE">numbered="true" toc="default"> <name>RFC 8445: ICE</name> <t><xreftarget="RFC5245"/>target="RFC8445" format="default"/> describes a protocol for NAT traversal for UDP-based multimedia sessions established with the offer/answer model. ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN). ICE can be used by any protocol utilizing the offer/answer model, such as the SIP.</t><texttable title="5.12 RFC5245 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ice-lite </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ice-options </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ice-mismatch </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ice-pwd </c><c>ice-pwd MUST<table align="center"> <name>RFC 8445 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">ice-lite</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> <tr> <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 underlying transportflow </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> <c>ice-ufrag </c><c>ice-ufrag MUSTflow.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> <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 underlying transportflow </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> <c>candidate </c><c>iceflow.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> <tr> <td align="left">candidate</td> <td align="left">ice candidateMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow </c><c>M</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> <c>remote-candidates </c><c>iceflow.</td> <td align="left">M</td> <td align="left">TRANSPORT</td> </tr> <tr> <td align="left">remote-candidates</td> <td align="left">ice remote candidateMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow </c><c>M</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>flow.</td> <td align="left">M</td> <td align="left">TRANSPORT</td> </tr> <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> <sectiontitle="RFC5285:numbered="true" toc="default"> <name>RFC 5285: RTP HeaderExtensions">Extensions</name> <t><xreftarget="RFC5285"/>target="RFC5285" format="default"/> provides a general mechanismto usefor using theheader extensionheader-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 in each RTP packet, where the universe of possible extensions is large and registration isde-centralized.decentralized. The actual extensions in use in a session are signaled in the setup information for that session.</t><texttable title="5.13 RFC5285 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>extmap </c><c>Refer<table align="center"> <name>RFC 5285 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">extmap</td> <td align="left">Refer to the document defining the specific RTPExtension </c> <c>B</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>extension.</td> <td align="left">B</td> <td align="left">SPECIAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC3605:numbered="true" toc="default"> <name>RFC 3605: RTCPattributeAttribute inSDP ">SDP</name> <t>Originally, SDP assumed that RTP and RTCP were carried on consecutive ports. However, this is not always true when NATs are involved. <xreftarget="RFC3605"/>target="RFC3605" format="default"/> specifies an early mechanismto indicatefor indicating the RTCP port.</t><texttable title="5.14 RFC3605 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rtcp </c><c>RTCP Port MUST<table align="center"> <name>RFC 3605 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">rtcp</td> <td align="left">RTCP port <bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow. </c> <c>M</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>flow.</td> <td align="left">M</td> <td align="left">TRANSPORT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5576:numbered="true" toc="default"> <name>RFC 5576: Source-Specific SDPAttributes">Attributes</name> <t><xreftarget="RFC5576"/>target="RFC5576" format="default"/> defines a mechanismto describefor describing RTP mediasources,sources -- which are identified by their synchronization source (SSRC)identifiers,identifiers -- in SDP, to associate attributes with thesesources,sources andtoexpress relationships among sources. It also defines several source-level attributes that can be used to describe properties of media sources.</t><texttable title="5.15 RFC5576 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ssrc </c><c>Refer to Notes below </c><c>M</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ssrc-group </c> <c>Refer<table align="center"> <name>RFC 5576 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">ssrc</td> <td align="left">Refer to notes below.</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ssrc-group</td> <td align="left">Refer to <xreftarget="sec-ssrc-group"></xref>target="sec-ssrc-group" format="default"/> for specific analysis of the groupingsemantics </c><c>M</c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>cname </c> <c>Not Impacted </c><c>SR</c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>previous-ssrc </c> <c>Refer to notes below </c><c>SR</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>fmtp </c><c>Thesemantics.</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">cname</td> <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 valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c><c>SR</c> <c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>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, theyMUST<bcp14>MUST</bcp14> all represent the same underlying RTP Source.</t> </section> <sectiontitle="RFC7273:numbered="true" toc="default"> <name>RFC 7273: RTP Clock SourceSignalling">Signaling</name> <t><xreftarget="RFC7273"/>target="RFC7273" format="default"/> specifies SDPsignallingsignaling that identifies timestamp reference clock sources and SDPsignallingsignaling that identifies the media clock sources in a multimedia session.</t><texttable title="5.16 RFC7273 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ts-refclk </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>mediaclk </c> <c>Not Impacted </c><c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ts-refclk:ntp </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ts-refclk:ptp </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ts-refclk:gps </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ts-refclk:gal </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ts-refclk:glonass </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ts-refclk:local </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ts-refclk:private </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>mediaclk:sender </c> <c>Not Impacted </c><c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>mediaclk:direct </c> <c>Not Impacted </c><c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>mediaclk:IEEE1722 </c> <c>Not Impacted </c><c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 7273 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">ts-refclk</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">mediaclk</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ts-refclk:ntp</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ts-refclk:ptp</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ts-refclk:gps</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ts-refclk:gal</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ts-refclk:glonass</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <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> <sectiontitle="RFC6236:numbered="true" toc="default"> <name>RFC 6236: Image Attributes inSDP">SDP</name> <t><xreftarget="RFC6236"/>target="RFC6236" format="default"/> proposes a new generic session setup attribute to make it possible to negotiate different imageattributesattributes, such as image size. A possible use case is to make it possible for a low-endhand-heldhandheld terminal to display video without the need to rescale the image, something that may consume large amounts of memory and processing power. The document also helps to maintain an optimal bitrate for video as only the image size that is desired by the receiver is transmitted.</t><texttable title="5.17 RFC6236 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>imageattr </c><c>The<table align="center"> <name>RFC 6236 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">imageattr</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c><c>M </c> <c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>configuration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC7197:numbered="true" toc="default"> <name>RFC 7197: Duplication Delay Attribute inSDP">SDP</name> <t><xreftarget="RFC7197"/>target="RFC7197" format="default"/> defines an attribute to indicate the presence of temporally redundant media streams and the duplication delay in SDP.</t><texttable title="5.18 RFC7197 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>duplication-delay </c><c>Not Impacted </c><c>B </c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 7197 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">duplication-delay</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC7266:numbered="true" toc="default"> <name>RFC 7266: RTCP XR Blocks for MOS MetricReporting">Reporting</name> <t><xreftarget="RFC7266"/>target="RFC7266" format="default"/> defines an RTCP Extended Report (XR) Blockincludingthat includes two new segment types and associated SDP parameters that allow the reporting of mean opinion score (MOS)Metricsmetrics for use in a range of RTP applications.</t><texttable title="5.19 RFC7266 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>calgextmap </c><c>Not Impacted </c><c>B </c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 7266 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">calgextmap</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6285:numbered="true" toc="default"> <name>RFC 6285: Rapid Acquisition of Multicast RTPSessions">Sessions</name> <t><xreftarget="RFC6285"/>target="RFC6285" format="default"/> describes a method of using the existing RTP and RTCP machinery that reduces the acquisition delay. In this method, an auxiliary unicast RTP session carrying theReference Informationreference information to the receiver precedes or accompanies the multicast stream. This unicast RTP flow can be transmitted at afaster than naturalfaster-than-natural bitrate to further accelerate the acquisition. The motivating use case for this capability is multicast applications that carry real-time compressed audio and video.</t><texttable title="5.20 RFC6285 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rams-updates </c><c>Not<table align="center"> <name>RFC 6285 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">rams-updates</td> <td align="left">Not recommended </c><c>M </c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable></td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6230:numbered="true" toc="default"> <name>RFC 6230: Media Control ChannelFramework">Framework</name> <t><xreftarget="RFC6230"/>target="RFC6230" format="default"/> describes a framework and protocol for application deployment where the application programming logic and media processing are distributed. This implies that application programming logic can seamlessly gain access to appropriate resources that are not co-located on the same physical network entity. The framework uses SIP to establish an application-level control mechanism between application servers and associated external servers such as media servers.</t><texttable title="5.21 RFC6230 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>cfw-id </c><c>Not Impacted </c> <c>M </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 6230 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">cfw-id</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6364:numbered="true" toc="default"> <name>RFC 6364: SDP Elements for FECFramework">Framework</name> <t><xreftarget="RFC6364"/>target="RFC6364" format="default"/> specifies the use of SDP to describe the parameters required to signal the Forward Error Correction (FEC) Framework Configuration Information between the sender(s) and receiver(s). This document also provides examples that show the semantics for grouping multiple source and repair flows together for the applications that simultaneously use multiple instances of the FEC Framework.</t><texttable title="5.22 RFC6364 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>fec-source-flow </c><c>Refer<table align="center"> <name>RFC 6364 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">fec-source-flow</td> <td align="left">Refer to the document defining specific FECScheme </c><c>M </c> <c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>fec-repair-flow </c><c>Referscheme.</td> <td align="left">M</td> <td align="left">SPECIAL</td> </tr> <tr> <td align="left">fec-repair-flow</td> <td align="left">Refer to the document defining specific FECScheme </c><c>M </c> <c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>repair-window </c><c>Referscheme.</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 FECScheme </c><c>M </c> <c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>scheme.</td> <td align="left">M</td> <td align="left">SPECIAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC4796: Content Attribute">numbered="true" toc="default"> <name>RFC 4796: "content" Attribute</name> <t><xreftarget="RFC4796"/>target="RFC4796" format="default"/> defines a new SDP media-level attribute,'content'."content". The'content'"content" attribute defines the content of the media stream to a more detailed level than the media description line. The sender of an SDP session description can attach the'content'"content" attribute to one or more media streams. The receiving application can then treat each media stream differently (e.g., show it on a big or small screen) based on its content.</t><texttable title="5.23 RFC4796 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>content </c><c>Not Impacted </c><c>M </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 4796 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">content</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC3407:numbered="true" toc="default"> <name>RFC 3407: SDP Simple CapabilityDeclaration">Declaration</name> <t><xreftarget="RFC3407"/>target="RFC3407" format="default"/> defines a set of SDP attributes that enables SDP to provide a minimal andbackwards compatiblebackwards-compatible capability declaration mechanism.</t><texttable title="5.24 RFC3407 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>sqn </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>cdsc </c><c>Not Impacted. </c><c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>cpar </c><c>Refer to <xref target="sec-encap"/> </c> <c>B</c><c>INHERIT </c> <c> </c><c> </c><c> </c><c> </c> <c>cparmin </c><c>Refer to notes below </c> <c>B</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>cparmax </c><c>Refer to notes below </c> <c>B</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 3407 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">sqn</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">cdsc</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <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> NOTE: The attributes(a=cparmin"a=cparmin" anda=cparmax)"a=cparmax" define minimum and maximum numerical values associated with the attributes described ina=cpar.</t>"a=cpar".</t> <t>Since the cpar attribute can either define a'b='"b=" attribute or any'a='"a=" attribute, the multiplexing category depends on the actual attribute being encapsulated and the implications of the numerical values assigned. Hence it is recommended to consult the specification defining attributes(cparmin/cparmax)"cparmin" and "cparmax" to further analyze their behavior under multiplexing.</t> </section> <sectiontitle="RFC6284:numbered="true" toc="default"> <name>RFC 6284: Port Mapping between Unicast and Multicast RTPSessions">Sessions</name> <t><xreftarget="RFC6284"/>target="RFC6284" format="default"/> presents aport mappingport-mapping solution that allows RTP receivers to choose their own ports for an auxiliary unicast session in RTP applications using both unicast and multicast services. The solution provides protection against denial-of-service or packet amplification attacks that could be used to cause one or more RTP packets to be sent to a victim client.</t><texttable title="5.25 RFC6284 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>portmapping-req </c><c>Not recommended,<table align="center"> <name>RFC 6284 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">portmapping-req</td> <td align="left">Not recommended if port mapping is required by theapplication </c><c>M </c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable>application</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6714: MSRP-CEMA">numbered="true" toc="default"> <name>RFC 6714: MSRP-CEMA</name> <t><xreftarget="RFC6714"/>target="RFC6714" format="default"/> defines a Message Session Relay Protocol (MSRP) extension, Connection Establishment for Media Anchoring (CEMA). Support of this extension is optional. The extension allowsmiddle boxesmiddleboxes to anchor the MSRPconnection,connection without the need formiddle boxesmiddleboxes to modify the MSRP messages; thus, it also enables secure end-to-end MSRP communication in networks where suchmiddle boxesmiddleboxes are deployed. This document also definesaan SDP attribute,'msrp-cema',"msrp-cema", that MSRP endpoints use to indicate support of the CEMA extension.</t><texttable title="5.26 RFC6714 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>msrp-cema </c><c>Refer to notes below </c><c>M </c> <c>TBD </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 6714 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">msrp-cema</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 persection 9 of<xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>,target="RFC8843" sectionFormat="of" section="9"/>, there exists no publicly available specification that defines procedures for multiplexing/demultiplexingMRSPMSRP flows over a single 5-tuple. Once such a specification is available, the assignments of multiplexing categoriesassignmentsfor the attributes in this section could be revisited.</t> </section> <sectiontitle="RFC4583:numbered="true" toc="default"> <name>RFC 4583: SDP Format for BFCPStreams">Streams</name> <t><xreftarget="RFC4583"/> documenttarget="RFC4583" format="default"/> specifies how to describe Binary Floor Control Protocol (BFCP) streams in SDP descriptions. User agents using the offer/answer model to 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 Impacted </c><c>M </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>floorid </c> <c>Not Impacted </c> <c>M </c><c>NORMAL </c><c> </c><c> </c> <c> </c><c> </c> </texttable><table align="center"> <name>RFC 4583 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">floorctrl</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">confid</td> <td align="left">Refer to notes below</td> <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:As per section 9 of<xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>,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> <t>NOTE: As per <xref target="RFC8843" sectionFormat="of" section="9"/>, there exists no publicly available specification that defines procedures for multiplexing/demultiplexing BFCP streams over a single 5-tuple. Once such a specification is available, the assignments of multiplexing categoriesassignmentsfor the attributes in this section could be revisited.</t> </section> <sectiontitle="RFC5547:numbered="true" toc="default"> <name>RFC 5547: SDP Offer/Answer for FileTransfer">Transfer</name> <t><xreftarget="RFC5547"/>target="RFC5547" format="default"/> provides a mechanism to negotiate the transfer of one or more files between two endpoints by using the SDP offer/answer model specified in <xreftarget="RFC3264"/>.</t> <texttable title="5.28 RFC5547 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>file-selector </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>file-transfer-id </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>file-disposition </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>file-date </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>file-icon </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>file-range </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> </texttable>target="RFC3264" format="default"/>.</t> <table align="center"> <name>RFC 5547 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">file-selector</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-transfer-id</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-disposition</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-date</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-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 persection 9 of<xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>,target="RFC8843" sectionFormat="of" section="9"/>, there exists no publicly available specification that defines procedures for multiplexing/demultiplexingMRSPMSRP flows over a single 5-tuple. Once such a specification is available, the assignments of multiplexing categoriesassignmentsfor attributes in this section could be revisited.</t> </section> <sectiontitle="RFC6849:numbered="true" toc="default"> <name>RFC 6849: SDP and RTP Media LoopbackExtension">Extension</name> <t><xreftarget="RFC6849"/>target="RFC6849" format="default"/> adds new SDP media types andattributes, whichattributes that enable establishment of media sessions where the media is looped back to the transmitter. Such media sessions will serve as monitoring and troubleshooting tools by providing the means for measurement of more advanced Voice over IP (VoIP),Real-time Text,real-time text, and Video over IP performance metrics.</t><texttable title="5.29 RFC6849 Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>loopback rtp-pkt-loopback </c><c>The<table align="center"> <name>RFC 6849 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">loopback rtp-pkt-loopback</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be same for a given codecconfiguration </c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>loopback rtp-media-loopback </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">loopback rtp-media-loopback</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be same for a given codecconfiguration </c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>loopback-source </c><c>Not Impacted </c><c>M</c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>loopback-mirror </c><c>Not Impacted </c><c>M</c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>configuration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </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> <sectiontitle="RFC5760:numbered="true" toc="default"> <name>RFC 5760: RTCP with UnicastFeedback ">Feedback</name> <t><xreftarget="RFC5760"/>target="RFC5760" format="default"/> specifies an extension to RTCP to use unicast feedback to a multicast sender. The proposed extension is useful for single-source multicast sessions such asSource-Specific Multicastsource-specific multicast (SSM) communication where the traditional model of many-to-many group communication is either not available or not desired.</t><texttable title="5.30 RFC5760 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rtcp-unicast </c><c>The<table align="center"> <name>RFC 5760 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">rtcp-unicast</td> <td align="left">The attributeMUST<bcp14>MUST</bcp14> be reported across all multiplexed "m="lines multiplexed </c><c>M</c><c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>lines.</td> <td align="left">M</td> <td align="left">IDENTICAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC3611:numbered="true" toc="default"> <name>RFC 3611: RTCPXR">XR</name> <t><xreftarget="RFC3611"/>target="RFC3611" format="default"/> defines the Extended Report (XR) packet type forRTCP,RTCP and defines how the use of XR packets can be signaled by an application if it employs the Session Description Protocol (SDP).</t><texttable title="5.31 RFC3611 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rtcp-xr </c><c>Not Impacted </c><c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 3611 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">rtcp-xr</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5939:numbered="true" toc="default"> <name>RFC 5939: SDP CapabilityNegotiation">Negotiation</name> <t><xreftarget="RFC5939"/>target="RFC5939" format="default"/> defines a general SDP Capability Negotiation framework. It also specifies how to provide attributes and transport protocols as capabilities and negotiate them using the framework. Extensions for other types of capabilities (e.g., media types and media formats) may be provided in other documents.</t><texttable title="5.32 RFC5939 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>pcfg </c> <c>Refer to <xref target="sec-encap"/> </c> <c>M</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>acfg </c> <c>Refer to <xref target="sec-encap"/> </c> <c>M</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>csup </c><c>Not Impacted </c><c>B</c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>creq </c><c>Not Impacted </c><c>B</c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>acap </c> <c>Refer to <xref target="sec-encap"/> </c> <c>B</c><c>INHERIT </c> <c> </c><c> </c><c> </c><c> </c> <c>tcap </c> <c>Refer to <xref target="sec-encap"/> </c> <c>B</c><c>INHERIT </c> <c> </c><c> </c><c> </c><c> </c> <c>cap-v0 </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 5939 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">pcfg</td> <td align="left">Refer to <xref target="sec-encap" format="default"/></td> <td align="left">M</td> <td align="left">SPECIAL</td> </tr> <tr> <td align="left">acfg</td> <td align="left">Refer to <xref target="sec-encap" format="default"/></td> <td align="left">M</td> <td align="left">SPECIAL</td> </tr> <tr> <td align="left">csup</td> <td align="left">Not impacted </td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">creq</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <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> <sectiontitle="RFC6871:numbered="true" toc="default"> <name>RFC 6871: SDP Media CapabilitiesNegotiation">Negotiation</name> <t>SDP capability negotiation provides a general framework for indicating and negotiating capabilities in SDP. The base frameworkdefinesonly defines capabilities for negotiating transport protocols and attributes. <xreftarget="RFC6871"></xref>target="RFC6871" format="default"/> extends the framework by defining media capabilities that can be used to negotiate media types and their associated parameters.</t><texttable title="5.33 RFC6871 - Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rmcap </c> <c>Refer to <xref target="sec-encap"/> </c> <c>B</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>omcap </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>mfcap </c> <c>Refer to <xref target="sec-encap"/> </c> <c>B</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>mscap </c> <c>Refer to <xref target="sec-encap"/> </c> <c>B</c><c>INHERIT </c> <c> </c><c> </c><c> </c><c> </c> <c>lcfg </c> <c>Refer to <xref target="sec-encap"/> </c> <c>B</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>sescap </c> <c>Refer to notes below </c> <c>S</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>med-v0 </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 6871 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">rmcap</td> <td align="left">Refer to <xref target="sec-encap" format="default"/></td> <td align="left">B</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">omcap</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">mfcap</td> <td align="left">Refer to <xref target="sec-encap" format="default"/></td> <td align="left">B</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">mscap</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">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 for use with multiplexing. The reason is that it requires the use of unique configuration numbers across the entire SDP (per <xreftarget="RFC6871"/>)target="RFC6871" format="default"/>) as opposed to within a media description only (per <xreftarget="RFC5939"/>).target="RFC5939" format="default"/>). As described in <xreftarget="sec-encap"/>,target="sec-encap" format="default"/>, the use of identical configuration numbers between multiplexed (bundled) media descriptions is the default way of indicating compatible configurations in a bundle. </t> </section> <sectiontitle="RFC7006:numbered="true" toc="default"> <name>RFC 7006: Miscellaneous Capabilities NegotiationSDP">in SDP</name> <t><xreftarget="RFC7006"/>target="RFC7006" format="default"/> extends the SDPcapability negotiationCapability Negotiation framework to allow endpoints to negotiate three additional SDP capabilities. In particular, this memo provides a mechanism to negotiate bandwidth ("b=" line), connection data ("c=" line), and session or media titles ("i=" line for each session or media).</t><texttable title="5.34 RFC7006 - Attribute Analysis "> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>bcap </c> <c>Inherit<table align="center"> <name>RFC 7006 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">bcap</td> <td align="left">Inherit the category SUM as applicable tob= attribute </c> <c>B</c><c>INHERIT </c> <c> </c><c> </c><c> </c><c> </c> <c>bcap-v0 </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ccap </c><c>Thethe "b=" attribute</td> <td align="left">B</td> <td align="left">INHERIT</td> </tr> <tr> <td align="left">bcap-v0</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ccap</td> <td align="left">The connection address typeMUST<bcp14>MUST</bcp14> be identical across all the multiplexed "m="lines </c> <c>B</c><c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ccap-v0 </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>icap </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>icap-v0 </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>lines.</td> <td align="left">B</td> <td align="left">IDENTICAL</td> </tr> <tr> <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> <sectiontitle="RFC4567:numbered="true" toc="default"> <name>RFC 4567: Key Management Extensions for SDP andRTSP">RTSP</name> <t><xreftarget="RFC4567"/>target="RFC4567" format="default"/> defines general extensions for SDP andReal TimeReal-Time Streaming Protocol (RTSP) to carry messages, as specified by a key management protocol, in order to secure the media. These extensions are presented as aframework,framework to be used by one or more key management protocols. As such, their use is meaningful only when complemented by an appropriate key management protocol.</t><texttable title="5.35 RFC4567 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>key-mgmt </c><c>Key<table align="center"> <name>RFC 4567 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">key-mgmt</td> <td align="left">Key management protocolMUST<bcp14>MUST</bcp14> be identical across all the "m="lines </c><c>B</c> <c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> <c>mikey </c><c>Keylines.</td> <td align="left">B</td> <td align="left">IDENTICAL</td> </tr> <tr> <td align="left">mikey</td> <td align="left">Key management protocolMUST<bcp14>MUST</bcp14> be identical across all the "m="lines </c><c>B</c> <c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>lines.</td> <td align="left">B</td> <td align="left">IDENTICAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC4572:numbered="true" toc="default"> <name>RFC 4572: Comedia over TLS inSDP">SDP</name> <t><xreftarget="RFC4572"/>target="RFC4572" format="default"/> specifies how to establish secure connection-oriented media transport sessions over the Transport Layer Security (TLS) protocol using SDP. (Note: <xref target="RFC4572"/> has been obsoleted by <xref target="RFC8122"/>.) It defines a new SDP protocol identifier,'TCP/TLS'."TCP/TLS". It also defines the syntax and semantics for an SDP'fingerprint'"fingerprint" attribute that identifies the certificate that will be presented for the TLS session. This mechanism allows media transport over TLS connections to be established securely, so long as the integrity of session descriptions is assured.</t><texttable title="5.36 RFC4572 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>fingerprint </c><c>fingerprint<table align="center"> <name>RFC 4572 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">fingerprint</td> <td align="left">fingerprint valueMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>flow.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC4570:numbered="true" toc="default"> <name>RFC 4570: SDP SourceFilters">Filters</name> <t><xreftarget="RFC4570"/>target="RFC4570" format="default"/> describes how to adapt SDP to express one or more source addresses as a source filter for one or more destination "connection" addresses. It defines the syntax and semantics for an SDP "source-filter" attribute that may reference either IPv4 or IPv6 address(es) as either an inclusive or exclusive source list for either multicast or unicast destinations. In particular, an inclusivesource-filtersource filter can be used to specify aSource-Specific Multicastsource-specific multicast (SSM) session.</t><texttable title="5.37 RFC4570 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>source-filter </c><c>The<table align="center"> <name>RFC 4570 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">source-filter</td> <td align="left">The attributeMUST<bcp14>MUST</bcp14> be repeated across all multiplexed "m="lines multiplexed </c><c>B</c><c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>lines.</td> <td align="left">B</td> <td align="left">IDENTICAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6128:numbered="true" toc="default"> <name>RFC 6128: RTCP Port for MulticastSessions">Sessions</name> <t>SDP has an attribute that allows RTP applications to specify an address and a port associated with the RTCP traffic. In RTP-based source-specific multicast (SSM) sessions, the same attribute is used to designate the address and the RTCP port of the Feedback Target in the SDP description. However, the RTCP port associated with the SSM session itself cannot be specified by the same attribute to avoidambiguity,ambiguity andthus,thus is required to be derived from the "m=" line of the media description. Deriving the RTCP port from the "m=" line imposes an unnecessary restriction. <xreftarget="RFC6128"/>target="RFC6128" format="default"/> removes this restriction by introducing a new SDP attribute.</t><texttable title="5.38 RFC6128 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>multicast-rtcp </c><c>Multicast<table align="center"> <name>RFC 6128 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">multicast-rtcp</td> <td align="left">Multicast RTCP portMUST<bcp14>MUST</bcp14> be identical across all the "m="lines </c><c>B</c><c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>lines.</td> <td align="left">B</td> <td align="left">IDENTICAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6189: ZRTP">numbered="true" toc="default"> <name>RFC 6189: ZRTP</name> <t><xreftarget="RFC6189"/>target="RFC6189" format="default"/> defines ZRTP, a protocol for media path Diffie-Hellman exchange to agree on a session key and parameters for establishing unicast SRTP sessions for(VoIPVoIP applications.</t><texttable title="5.39 RFC6189 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>zrtp-hash </c><c>zrtp-hash<table align="center"> <name>RFC 6189 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">zrtp-hash</td> <td align="left">The zrtp-hash attributeMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow </c><c>M</c> <c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>flow.</td> <td align="left">M</td> <td align="left">TRANSPORT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC4145:numbered="true" toc="default"> <name>RFC 4145: Connection-OrientedMedia ">Media</name> <t><xreftarget="RFC4145"/>target="RFC4145" format="default"/> describes how to express media transport over TCP using SDP. It defines the SDP'TCP'"TCP" protocol identifier, the SDP'setup'"setup" attribute, which describes the connection setup procedure, and the SDP'connection'"connection" attribute, which handles connectionreestablishment.</t> <texttable title="5.40 RFC4145 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>setup </c> <c>There-establishment.</t> <table align="center"> <name>RFC 4145 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">setup</td> <td align="left">The setup attributeMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow. </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> <c>connection </c> <c>Theflow.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> <tr> <td align="left">connection</td> <td align="left">The connection attributeMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow. </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>flow.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6947:numbered="true" toc="default"> <name>RFC 6947: The SDPaltc Attribute">"altc" Attribute</name> <t><xreftarget="RFC6947"/>target="RFC6947" format="default"/> proposes a mechanism that allows the same SDP offer to carry multiple IP addresses of different address families (e.g., IPv4 and IPv6). The proposedattribute, the"altc"attribute,attribute solves the backward-compatibility problem that plagued Alternative Network Address Types (ANAT) due to their syntax.</t><texttable title="5.41 RFC6947 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>altc </c><c>The<table align="center"> <name>RFC 6947 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">altc</td> <td align="left">The IPAddressaddress and portMUST<bcp14>MUST</bcp14> be theoneones thatcorrespondscorrespond to the "m=" line chosen for setting up the underlying transportflow </c> <c>M</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>flow.</td> <td align="left">M</td> <td align="left">TRANSPORT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC7195:numbered="true" toc="default"> <name>RFC 7195: SDP Extension forCircuit SwitchedCircuit-Switched Bearers inPSTN">PSTN</name> <t><xreftarget="RFC7195"/>target="RFC7195" format="default"/> describes use cases, requirements, and protocol extensions for using the SDP offer/answer model for establishing audio and video media streams over circuit-switched bearers in the Public Switched Telephone Network (PSTN).</t><texttable title="5.42 RFC7195 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>cs-correlation:callerid </c> <c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>cs-correlation:uuie </c> <c>Refer to notes below </c> <c>M </c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>cs-correlation:dtmf </c> <c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>cs-correlation:external </c> <c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 7195 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">cs-correlation:callerid</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:uuie</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: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> <t>NOTE: <xreftarget="RFC7195"/>target="RFC7195" format="default"/> defines SDP attributes for establishing audio and video media streams over circuit-switched bearers by defining a new nettypevaluevalue, "PSTN". However,section 7.2 of<xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>target="RFC8843" sectionFormat="of" section="7.2"/> requires the "c=" line nettype valueofto be "IN". Ifin futurethere exists in future a specification that defines procedures to multiplex media streams over nettype "PSTN", the multiplexing categories for attributes in this section could be revisited.</t> </section> <sectiontitle="RFC7272:numbered="true" toc="default"> <name>RFC 7272: IDMS Using the RTP Control Protocol(RTCP)">(RTCP)</name> <t><xreftarget="RFC7272"/>target="RFC7272" format="default"/> defines a new RTCPPacket Typepacket type and an RTCP Extended Report (XR) Block Type to be used for achieving Inter-Destination Media Synchronization (IDMS).</t><texttable title="5.43 RFC7272 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rtcp-idms </c><c>Not Impacted </c> <c>M</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 7272 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">rtcp-idms</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5159:numbered="true" toc="default"> <name>RFC 5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDPAttributes">Attributes</name> <t><xreftarget="RFC5159"/>target="RFC5159" format="default"/> provides descriptions of SDP attributes used by the Open Mobile Alliance'sBroadcast Service"Service and Content Protection for Mobile Broadcast Services" specification.</t><texttable title="5.44 RFC5159 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>bcastversion </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>stkmstream </c><c>Not Impacted </c> <c>B</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>SRTPAuthentication </c><c>Needs<table align="center"> <name>RFC 5159 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">bcastversion</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">stkmstream</td> <td align="left">Not impacted</td> <td align="left">B</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">SRTPAuthentication</td> <td align="left">Needs furtheranalysis </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>SRTPROCTxRate </c><c>Needsanalysis</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">SRTPROCTxRate</td> <td align="left">Needs furtheranalysis </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> </texttable>analysis</td> <td align="left">M</td> <td align="left">TBD</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6193:numbered="true" toc="default"> <name>RFC 6193: Media Description for IKE inSDP">SDP</name> <t><xreftarget="RFC6193"/>target="RFC6193" format="default"/> specifies how to establish a media session that represents a virtual private network using the Session Initiation Protocol for the purpose of on-demand media/application sharing between peers. It extends the protocol identifier of SDP so that it can negotiate use of the Internet Key Exchange Protocol (IKE) for media sessions in the SDP offer/answer model.</t><texttable title="5.45 RFC6193 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ike-setup </c><c>Unlikely<table align="center"> <name>RFC 6193 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">ike-setup</td> <td align="left">Unlikely to use IKE in the context ofmultiplexing </c><c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>psk-fingerprint </c><c>Unlikelymultiplexing</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">psk-fingerprint</td> <td align="left">Unlikely to use IKE in the context ofmultiplexing </c><c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>ike-esp </c><c>Unlikelymultiplexing</td> <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 ofmultiplexing </c><c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>ike-esp-udpencap </c><c>Unlikelymultiplexing</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 ofmultiplexing </c><c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable>multiplexing</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> </tbody> </table> </section> <sectiontitle="RFC2326:numbered="true" toc="default"> <name>RFC 2326: Real Time StreamingProtocol">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><texttable title="5.46 RFC2326 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>etag </c><c>RTSP<table align="center"> <name>RFC 2326 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">etag</td> <td align="left">RFC 2326 is obsolete.</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">range</td> <td align="left">RFC 2326 is obsolete.</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">control</td> <td align="left">RFC 2326 is obsolete.</td> <td align="left">B</td> <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 attributes that are applicable in the declarative usage of SDP alone. For the purposes of this document, only the offer/answer usage of SDP isnot supportedconsidered to be mandated by <xref target="RFC8843" format="default"/>.</t> </section> <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 forRTP Stream multiplexing </c><c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>range </c><c>RTSPcontrol 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 RTPStream multiplexing </c><c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>control </c><c>RTSPstream 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 RTPStream multiplexing </c><c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>mtag </c><c>RTSPstream 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 RTPStream multiplexing </c><c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable>stream multiplexing.</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> </tbody> </table> <t>NOTE: <xreftarget="RFC2326"/>target="RFC7826" format="default"/> defines SDP attributes that are applicable in the declarative usage of SDP alone. For the purposes of this document, only theOffer/Answeroffer/answer usage of SDP is consideredasto be mandated by <xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>.</t>target="RFC8843" format="default"/>.</t> </section> <sectiontitle="RFC6064:numbered="true" toc="default"> <name>RFC 6064: SDP and RTSP Extensions for3GPP">3GPP</name> <t>The Packet-switched Streaming Service (PSS) and the Multimedia Broadcast/Multicast Service (MBMS) defined by 3GPP use SDP and RTSP with some extensions. <xreftarget="RFC6064"/>target="RFC6064" format="default"/> provides information about these extensions and registers the RTSP and SDP extensions with IANA.</t><texttable title="5.47 RFC6064 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>X-predecbufsize </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>X-initpredecbufperiod </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>X-initpostdecbufperiod </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>X-decbyterate</c><c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3gpp-videopostdecbufsize </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>framesize</c><c>Refer to notes below </c><c>M</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-Integrity-Key </c> <c>Refer to notes below </c><c>S</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-SDP-Auth </c> <c>Refer to notes below </c><c>S</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-SRTP-Config </c> <c>Refer to notes below </c><c>M</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>alt </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>alt-default-id </c> <c>Refer<table align="center"> <name>RFC 6064 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">X-predecbufsize</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">X-initpredecbufperiod</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">X-initpostdecbufperiod</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">X-decbyterate</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-videopostdecbufsize</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">framesize</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-Integrity-Key</td> <td align="left">Refer to notes below</td> <td align="left">S</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">3GPP-SDP-Auth</td> <td align="left">Refer to notes below</td> <td align="left">S</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">3GPP-SRTP-Config</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">alt</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">alt-default-id</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">alt-group</td> <td align="left">Refer to notes below</td> <td align="left">S</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">3GPP-Adaptation-Support</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-Asset-Information</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">mbms-mode</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">mbms-flowid</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">mbms-repair</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</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:Corruption 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:Rebuffering 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:Initial buffering duration</td> <td align="left">Refer to notesbelow </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>alt-group </c> <c>Referbelow</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">3GPP-QoE-Metrics:Successive loss of RTP packets</td> <td align="left">Refer to notesbelow </c><c>S</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-Adaptation-Support </c> <c>Referbelow</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">3GPP-QoE-Metrics:Frame rate deviation</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: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 notesbelow </c><c>M</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-Asset-Information </c> <c>Refer to notes below </c><c>B</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>mbms-mode </c> <c>Refer to notes below </c><c>B</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>mbms-flowid </c> <c>Refer to notes below </c><c>M</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>mbms-repair </c> <c>Refer to notes below </c><c>B</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Corruption duration </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Rebuffering duration </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Initial buffering duration </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Successive loss of RTP packets </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Frame rate deviation </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Jitter duration </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Content Switch Time </c> <c>Refer to notes below </c> <c>B</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Averagebelow</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">3GPP-QoE-Metrics:Average CodecBitrate </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Codec Information </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>3GPP-QoE-Metrics:Buffer Status </c> <c>Refer to notes below </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable>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: <xreftarget="RFC6064"/>target="RFC6064" format="default"/> defines SDP attributes that are applicable in the declarative usage of SDP alone. For the purposes of this document, only theOffer/Answeroffer/answer usage of SDP is consideredasto be mandated by <xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>.target="RFC8843" format="default"/>. </t> </section> <sectiontitle="RFC3108:numbered="true" toc="default"> <name>RFC 3108: ATMSDP">SDP</name> <t><xreftarget="RFC3108"></xref>target="RFC3108" format="default"/> describes conventions for using SDP described for controlling ATMBearer Connections,bearer connections and any associated ATM Adaptation Layer (AAL).</t><texttable title="5.48 RFC3108 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>aalType </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>eecid </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>capability </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>qosClass </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>bcob </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>stc </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>upcc </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>atmQOSparms </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>atmTrfcDesc </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>abrParms </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>abrSetup </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>bearerType </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>lij </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>anycast </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>cache </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>bearerSigIE </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>aalApp </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>cbrRate </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>sbc </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>clkrec </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>fec </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>prtfl </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>structure </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>cpsSDUsize </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>aal2CPS </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>aal2CPSSDUrate </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>aal2sscs3661unassured </c> <c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>aal2sscs3661assured </c> <c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>aal2sscs3662 </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>aal5sscop </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>atmmap </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>silenceSupp </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>ecan </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>gc </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>profileDesc </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>vsel </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>dsel </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>fsel </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>onewaySel </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>codecconfig </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>isup_usi </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>uiLayer1_Prot </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c>chain </c><c>Refer to notes below</c> <c>B </c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 3108 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">aalType</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">eecid</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">capability</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">qosClass</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">bcob</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">stc</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">upcc</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">atmQOSparms</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">atmTrfcDesc</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">abrParms</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">abrSetup</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">bearerType</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">lij</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">anycast</td> <td align="left">Refer to notes below</td> <td align="left">B</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">cache</td> <td align="left">Refer to notes below</td> <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:RFC3108RFC 3108 describes conventions for using SDP for characterizing ATM bearer connections using an AAL1,AAL2AAL2, or AAL5 adaptationlayers.layer. For AAL1,AAL2AAL2, and AAL5, bearer connections can be used to transport single media streams. In addition, for AAL1 and AAL2, multiple media streams can be multiplexed into a bearer connection. For all adaptation types (AAL1,AAL2AAL2, and AAL5), bearer connections can be bundled into a single media group. In all cases addressed byRFC3108,RFC 3108, a real-time media stream (voice, video, voiceband data,pseudo-wire,pseudowire, and others) or a multiplex of media streams is mapped directly into an ATM connection.RFC3108RFC 3108 does not address cases where ATM serves as a low-level transport pipe for IP packetswhichthat can, inturn canturn, carry one or more real-time(e.g.(e.g., VoIP) media sessions with alife-cyclelife cycle different from that of the underlying ATM transport.</t> </section> <sectiontitle="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 title="3GPPnumbered="true" toc="default"> <name>3GPP TS183.063">183.063</name> <t> <xreftarget="R3GPPTS183.063"/>target="TISPAN" format="default"/> describes Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); </t><texttable title="5.50 3GPP<table align="center"> <name>3GPP TS 183.063 AttributeAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>PSCid </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>bc_service </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>bc_program </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>bc_service_package </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>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">PSCid</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">bc_service</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">bc_program</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">bc_service_package</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section><section title="3GPP TS 24.182"> <t> <xref target="R3GPPTS24.182"/> specifies IP multimedia subsystem Custom Alerting tones </t> <texttable title="5.51<!-- removed 3GPP TS 24.182Attribute 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.cat </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.183"> <t> <xref target="R3GPPTS24.183"/> specifies IP multimedia subsystem Custom Ringing Signal </t> <texttable title="5.52and 3GPP TS 24.183Attribute 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>per draft-ietf-mmusic-sdp-mux-attributes-19 --> <sectiontitle="3GPPnumbered="true" toc="default"> <name>3GPP TS24.229">24.229</name> <t> <xreftarget="R3GPPTS24.229"/>target="IP-CALL" format="default"/> specifies an IP multimedia call control protocol based on Session Initial protocol and Session Description Protocol. </t><texttable title="5.53 3GPP<table align="center"> <name>3GPP TS 24.229 AttributeAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>secondary-realm </c> <c>secondary-realm MUSTAnalysis</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">secondary-realm</td> <td align="left">secondary-realm <bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow </c><c>M</c> <c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> <c>visited-realm </c> <c>visited-realm MUSTflow.</td> <td align="left">M</td> <td align="left">TRANSPORT</td> </tr> <tr> <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 transportflow </c><c>M</c> <c>TRANSPORT </c><c> </c> <c> </c><c> </c><c> </c> <c>omr-m-cksum </c><c>Not Impacted </c> <c>M</c><c>NORMAL </c><c> </c> <c> </c><c> </c><c> </c> <c>omr-s-cksum </c><c>Not Impacted </c> <c>M</c><c>NORMAL </c><c> </c> <c> </c><c> </c><c> </c> <c>omr-m-att </c><c>Not Impacted </c> <c>M</c><c>NORMAL </c><c> </c> <c> </c><c> </c><c> </c> <c>omr-s-att </c><c>Not Impacted </c> <c>M</c><c>NORMAL </c><c> </c> <c> </c><c> </c><c> </c> <c>omr-m-bw </c><c>Not Impacted </c> <c>M</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>omr-s-bw </c><c>Not Impacted </c> <c>M</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>omr-codecs </c><c>Not Impacted </c> <c>M</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>flow.</td> <td align="left">M</td> <td align="left">TRANSPORT</td> </tr> <tr> <td align="left">omr-m-cksum</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">omr-s-cksum</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">omr-m-att</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">omr-s-att</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">omr-m-bw</td> <td align="left">Not impacted</td> <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> <sectiontitle="ITU T.38">numbered="true" toc="default"> <name>ITU T.38</name> <t> <xreftarget="T.38"></xref>target="T.38" format="default"/> defines procedures for real-time Group 3 facsimile communications over IP networks. </t><texttable title="5.54 ITU<table align="center"> <name>ITU T.38 AttributeAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>T38FaxVersion </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38MaxBitRate </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxFillBitRemoval </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxTranscodingMMR </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxTranscodingJBIG </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxRateManagement </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxMaxBuffer </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxMaxDatagram </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxUdpEC </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxMaxIFP </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxUdpECDepth </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38FaxUdpFECMaxSpan </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38ModemType </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>T38VendorInfo </c><c>Refer to notes below </c> <c>M</c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> </texttable>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">T38FaxVersion</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">T38MaxBitRate</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">T38FaxFillBitRemoval</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">T38FaxTranscodingMMR</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">T38FaxTranscodingJBIG</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">T38FaxRateManagement</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">T38FaxMaxBuffer</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">T38FaxMaxDatagram</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <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> <t>NOTE: As persection 9 of<xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>,target="RFC8843" sectionFormat="of" section="9"/>, there exists no publicly available specification that defines procedures for multiplexing/demultiplexing faxprotocolsprotocol flows over a single 5-tuple. Once such a specification is available, the multiplexing category assignments for the attributes in this section could be revisited.</t> </section> <sectiontitle="ITU-T Q.1970">numbered="true" toc="default"> <name>ITU-T Q.1970</name> <t> <xreftarget="Q.1970"></xref>target="Q.1970" format="default"/> defines Bearer Independent Call Control (BICC) IP bearer control protocol. </t><texttable title="5.55 ITU-T<table align="center"> <name>ITU-T Q.1970 AttributeAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ipbcp </c><c>ipbcpAnalysis</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">ipbcp</td> <td align="left">ipbcp version identifiestypethe types of IP bearer control protocol (IPBCP) message used in BICC (ITU-T Q.1901) environmentwhichthat are limited tosingle mediasingle-media payload. Refer to the pertinent ITU-T specifications whilemultiplexing </c> <c>S</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>multiplexing.</td> <td align="left">S</td> <td align="left">SPECIAL</td> </tr> </tbody> </table> </section> <sectiontitle="ITU-T H.248.15">numbered="true" toc="default"> <name>ITU-T H.248.15</name> <t> ITU-T H.248.15 <xreftarget="H.248.15"></xref>target="H.248.15" format="default"/> defines the Gateway Control Protocol SDP H.248 packageattributeattribute. </t><texttable title="5.56 ITU-T<table align="center"> <name>ITU-T H.248.15 AttributeAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>h248item </c><c>ItAnalysis</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">h248item</td> <td align="left">It is only applicable for signaling the inclusion of H.248 extension packages to a gateway via the local and remote descriptors. The attribute itself is unaffected by multiplexing, but thepackagedpackage referenced in a specific use of the attribute can be impacted. Further analysis of each package is needed to determine if there is an issue. This is only a concern in environments using a decomposed server/gateway with H.248 signaled between them. The ITU-T will need to do further analysis of various packages when they specify how to signal the use of multiplexing to agateway </c> <c>B</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>gateway.</td> <td align="left">B</td> <td align="left">SPECIAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC4975:numbered="true" toc="default"> <name>RFC 4975: The Message Session RelayProtocol">Protocol</name> <t><xreftarget="RFC4975"/>target="RFC4975" format="default"/> describes the Message Session Relay Protocol, a protocol for transmitting a series of related instant messages in the context of a session. Message sessions are treated like any other media stream when set up via a rendezvous orsession creationsession-creation protocol such as the Session Initiation Protocol.</t><texttable title="5.57 RFC4975 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>accept-types </c><c>Refer to notes below </c> <c>M </c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>accept-wrapped-types </c><c>Refer to notes below </c> <c>M </c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>max-size </c><c>Refer to notes below </c> <c>M </c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> <c>path </c><c>Refer to notes below </c> <c>M </c><c>TBD </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 4975 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">accept-types</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <td align="left">accept-wrapped-types</td> <td align="left">Refer to notes below</td> <td align="left">M</td> <td align="left">TBD</td> </tr> <tr> <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 persection 9 of<xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"/>,target="RFC8843" sectionFormat="of" section="9"/>, there exists no publicly available specification that defines procedures for multiplexing/demultiplexingMRSPMSRP flows over a single 5-tuple. Once such a specification is available, the multiplexing categories assignments for the attributes in this section could be revisited.</t> </section> <sectiontitle="Historical Attributes">numbered="true" toc="default"> <name>Historical Attributes</name> <t> This section specifies analysis for the attributes that are included for historic usage alone by the <xreftarget="IANA"></xref>.target="IANA" format="default"/>. </t><texttable title="5.58 Historical Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rtpred1 </c><c>Historic attributes </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>rtpred2 </c><c>Historic attributes </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>Historical 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">rtpred1</td> <td align="left">Historic attributes</td> <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> <sectiontitle="bwtype Attribute Analysis"anchor="SecbwtypeAnalysis">numbered="true" toc="default"> <name>bwtype Attribute Analysis</name> <t>This section specifies handling of specific bandwidth attributes when used in multiplexing scenarios.</t> <sectiontitle="RFC4566: SDP">numbered="true" toc="default"> <name>RFC 4566: SDP</name> <t><xreftarget="RFC4566"/>target="RFC4566" format="default"/> defines SDP that is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation.</t><texttable title="6.1 RFC4566<table align="center"> <name>RFC 4566 bwtypeAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>bwtype:CT </c><c>Not Impacted </c> <c>S</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>bwtype:AS </c><c>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">bwtype:CT</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">bwtype:AS</td> <td align="left"> Forthe media levelmedia-level usage, the aggregate of individual bandwidth values isconsidered </c> <c>B</c> <c>SUM </c> <c> </c><c> </c><c> </c><c> </c> </texttable>considered.</td> <td align="left">B</td> <td align="left">SUM</td> </tr> </tbody> </table> </section> <sectiontitle="RFC3556:numbered="true" toc="default"> <name>RFC 3556: SDP Bandwidth Modifiers for RTCPBandwidth">Bandwidth</name> <t><xreftarget="RFC3556"/>target="RFC3556" format="default"/> defines an extension to SDP to specify two additional modifiers for the bandwidth attribute. These modifiers may be used to specify the bandwidth allowed for RTCP packets inaan RTP session.</t><texttable title="6.2 RFC3556<table align="center"> <name>RFC 3556 bwtypeAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>bwtype:RS </c><c>Session levelAnalysis</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">bwtype:RS</td> <td align="left">Session-level usage represents sessionaggregateaggregate, andmedia levelmedia-level usage indicates SUM of the individual values whilemultiplexing </c> <c>B</c><c>SUM</c> <c> </c><c> </c><c> </c><c> </c> <c>bwtype:RR </c><c>Session levelmultiplexing.</td> <td align="left">B</td> <td align="left">SUM</td> </tr> <tr> <td align="left">bwtype:RR</td> <td align="left">Session-level usage represents sessionaggregateaggregate, andmedia levelmedia-level usage indicates SUM of the individual values whilemultiplexing </c> <c>B</c><c>SUM </c> <c> </c><c> </c><c> </c><c> </c> </texttable>multiplexing.</td> <td align="left">B</td> <td align="left">SUM</td> </tr> </tbody> </table> </section> <sectiontitle="RFC3890:numbered="true" toc="default"> <name>RFC 3890: Bandwidth Modifier forSDP">SDP</name> <t><xreftarget="RFC3890"/>target="RFC3890" format="default"/> defines SDP Transport Independent Application Specific Maximum (TIAS) bandwidth modifier that does not include transport overhead;insteadinstead, an additionalpacket ratepacket-rate attribute is defined. Thetransport independent bit-ratetransport-independent bitrate value together with the maximum packet rate can then be used to calculate the realbit-ratebitrate over the transport actually used.</t><texttable title="6.3 RFC3890<table align="center"> <name>RFC 3890 bwtypeAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>bwtype:TIAS </c><c>TheAnalysis</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">bwtype:TIAS</td> <td align="left">The usage of TIAS is not defined underOffer/Answer usage. </c> <c>B</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>maxprate </c><c>Theoffer/answer usage.</td> <td align="left">B</td> <td align="left">SPECIAL</td> </tr> <tr> <td align="left">maxprate</td> <td align="left">The usage of TIAS and maxprate is not well defined undermultiplexing </c> <c>B</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>multiplexing.</td> <td align="left">B</td> <td align="left">SPECIAL</td> </tr> </tbody> </table> <t>NOTE: The intention of TIAS is that themedia level bit-ratemedia-level bitrate is multiplied with the known per-packet overhead for the selected transport and the maxprate value to determine theworst case bit-rateworst-case bitrate from the transport to more accurately capture the required usage. Summing TIAS values independently across "m=" lines and multiplying the computed sum with maxprate and the per-packet overhead would inflate the value significantly.InsteadInstead, performing multiplication and adding the individual values is a more appropriate usage.</t> </section> </section> <sectiontitle="rtcp-fbanchor="SecrtcpfbAnalysis" numbered="true" toc="default"> <name>rtcp-fb AttributeAnalysis" anchor="SecrtcpfbAnalysis">Analysis</name> <t> This section analyzes rtcp-fb SDP attributes. </t> <sectiontitle="RFC4585: RTP/AVPF">numbered="true" toc="default"> <name>RFC 4585: RTP/AVPF</name> <t><xreftarget="RFC4585"/>target="RFC4585" format="default"/> defines an extension to theAudio-visualAudio-Visual Profile (AVP) that enables receivers to provide, statistically, more immediate feedback to thesenders andsenders; it thus allows for short-term adaptation and implementation of efficient feedback-based repairmechanisms to be implemented.</t> <texttable title="7.1 RFC4585 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ack rpsi </c><c>Themechanisms.</t> <table align="center"> <name>RFC 4585 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">ack rpsi</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>ack app </c> <c>Feedbackconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">ack app</td> <td align="left">Feedback parametersMUST<bcp14>MUST</bcp14> be handled in theapp specificapp-specific way whenmultiplexed</c> <c>M</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>nack </c><c>Themultiplexed.</td> <td align="left">M</td> <td align="left">SPECIAL</td> </tr> <tr> <td align="left">nack</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>nack pli </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">nack pli</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>nack sli </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">nack sli</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>nack rpsi </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">nack rpsi</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>nack app </c> <c>Feedbackconfiguration.</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 parametersMUST<bcp14>MUST</bcp14> be handled in the app specific way whenmultiplexed</c> <c>M</c><c>SPECIAL </c> <c> </c><c> </c><c> </c><c> </c> <c>trr-int </c><c>Themultiplexed.</td> <td align="left">M</td> <td align="left">SPECIAL</td> </tr> <tr> <td align="left">trr-int</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>configuration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5104:numbered="true" toc="default"> <name>RFC 5104: Codec Control Messages inAVPF">AVPF</name> <t><xreftarget="RFC5104"/>target="RFC5104" format="default"/> specifies a few extensions to the messages defined in the Audio-Visual Profile with Feedback (AVPF). They are helpful primarily in conversational multimedia scenarios where centralized multipoint functionalities are in use. However, some are also usable in smaller multicast environments and point-to-point calls.</t><texttable title="7.2 RFC5104 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ccm </c><c>The<table align="center"> <name>RFC 5104 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">ccm</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>configuration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6285:numbered="true" toc="default"> <name>RFC 6285: Unicast-Based Rapid Acquisition of Multicast RTP Sessions(RAMS)">(RAMS)</name> <t><xreftarget="RFC6285"/>target="RFC6285" format="default"/> describes a method of using the existing RTP and RTCP machinery that reduces the acquisition delay. In this method, an auxiliary unicast RTP session carrying the Reference Information to the receiver precedes or accompanies the multicast stream. This unicast RTP flow can be transmitted at afaster than naturalfaster-than-natural bitrate to further accelerate the acquisition. The motivating use case for this capability is multicast applications that carry real-time compressed audio and video.</t><texttable title="7.3 RFC6285 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>nack rai </c><c>The<table align="center"> <name>RFC 6285 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">nack rai</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c> <c>M </c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>configuration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6679:numbered="true" toc="default"> <name>RFC 6679: ECN for RTP overUDP/IP">UDP/IP</name> <t><xreftarget="RFC6679"/>target="RFC6679" format="default"/> specifies how Explicit Congestion Notification (ECN) can be used with the RTP running over UDP, using the RTCP as a feedback mechanism. It defines a new RTCP Extended Report (XR) block for periodic ECN feedback, a new RTCP transport feedback message for timely reporting of congestion events, and a STUN extension used in the optional initialization method using ICE.</t><texttable title="7.4 RFC6679 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ecn-capable-rtp </c><c>ECN<table align="center"> <name>RFC 6679 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">ecn-capable-rtp</td> <td align="left">ECN markupareis enabled at the RTP sessionlevel </c> <c>M </c><c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> <c>nack ecn </c><c>Thislevel.</td> <td align="left">M</td> <td align="left">IDENTICAL</td> </tr> <tr> <td align="left">nack ecn</td> <td align="left">This attribute enables ECN at the RTP sessionlevel </c> <c>M </c><c>IDENTICAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable>level.</td> <td align="left">M</td> <td align="left">IDENTICAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC6642:numbered="true" toc="default"> <name>RFC 6642: Third-Party LossReport">Report</name> <t>In a large RTP session using the RTCP feedback mechanism defined in <xreftarget="RFC4585"></xref>,target="RFC4585" format="default"/>, a feedback target may experience transient overload if some event causes a large number of receivers to send feedback at once. This overload is usually avoided by ensuring that feedback reports are forwarded to all receivers, allowing them to avoid sending duplicate feedback reports. However, there are cases where it is not recommended to forward feedback reports, and this may allow feedback implosion. <xreftarget="RFC6642"></xref> memotarget="RFC6642" format="default"/> discusses these cases and defines a new RTCP Third-Party Loss Report that can be used to inform receivers that the feedback target is aware of some loss event, allowing them to suppress feedback. Associated SDP signaling is also defined.</t><texttable title="7.5 RFC6642 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>nack tllei </c><c>The<table align="center"> <name>RFC 6642 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">nack tllei</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c> <c>M </c> <c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>nack pslei </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">nack pslei</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c> <c>M </c> <c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>configuration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5104:numbered="true" toc="default"> <name>RFC 5104: Codec Control Messages inAVPF">AVPF</name> <t><xreftarget="RFC5104"/>target="RFC5104" format="default"/> specifies a few extensions to the messages defined in the Audio-Visual Profile with Feedback (AVPF). They are helpful primarily in conversational multimedia scenarios where centralized multipoint functionalities are in use. However, some are also usable in smaller multicast environments and point-to-point calls.</t><texttable title="7.6 RFC5104 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ccm fir </c><c>The<table align="center"> <name>RFC 5104 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">ccm fir</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>ccm tmmbr </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">ccm tmmbr</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>ccm tstr </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">ccm tstr</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>ccm vbcm </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">ccm vbcm</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration</c> <c>M</c><c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>configuration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> </section> <sectiontitle="groupanchor="SecgroupAnalysis" numbered="true" toc="default"> <name>group AttributeAnalysis" anchor="SecgroupAnalysis">Analysis</name> <t> This section analyzes SDP"group""group" attribute semantics <xreftarget="RFC5888"/>.target="RFC5888" format="default"/>. </t> <sectiontitle="RFC5888:numbered="true" toc="default"> <name>RFC 5888: SDP GroupingFramework">Framework</name> <t> <xreftarget="RFC5888"/>target="RFC5888" format="default"/> defines a framework to group"m""m=" lines in SDP for different purposes. </t><texttable title="8.1 RFC5888 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>group:LS </c><c>Not Impacted </c> <c>S </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>group:FID </c><c>Not Impacted </c> <c>S </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><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> <sectiontitle="RFC3524:numbered="true" toc="default"> <name>RFC 3524: Mapping Media Streams to Resource ReservationFlows">Flows</name> <t><xreftarget="RFC3524"/>target="RFC3524" format="default"/> defines an extension to the SDP grouping framework. It allows requesting a group of media streams to be mapped into a single resource reservation flow. The SDP syntax needed is defined, as well as a new "semantics" attribute called Single Reservation Flow (SRF).</t><texttable title="8.2 RFC3524 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>group:SRF </c><c>Not Impacted </c> <c>S </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 3524 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:SRF</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC4091:numbered="true" toc="default"> <name>RFC 4091: ANATSemantics">Semantics</name> <t> <xreftarget="RFC4091"/>target="RFC4091" format="default"/> defines ANAT semantics for the 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. </t><texttable title="8.3 RFC4091 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>group:ANAT </c><c>ANAT<table align="center"> <name>RFC 4091 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:ANAT</td> <td align="left">ANAT semantics isobsoleted </c> <c>S </c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable>obsoleted.</td> <td align="left">S</td> <td align="left">CAUTION</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5956:numbered="true" toc="default"> <name>RFC 5956: FEC Grouping Semantics inSDP">SDP</name> <t><xreftarget="RFC5956"/>target="RFC5956" format="default"/> defines the semantics for grouping the associated source and FEC-based(Forward Error Correction)repair flows in SDP. The semantics defined in the document are to be used with the SDP Grouping Framework <xreftarget="RFC5888"/>.target="RFC5888" format="default"/>. These semantics allow the description of grouping relationships between the source and repair flows when one or more source and/or repair flows are associated in the samegroup, andgroup; they also provide support for additive repair flows. SSRC-level(Synchronization Source)grouping semantics are also defined in this document for RTP streams using SSRC multiplexing.</t><texttable title="8.4 RFC5956 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>group:FEC-FR </c><c>Not Impacted </c><c>S </c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 5956 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:FEC-FR</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> <sectiontitle="RFC5583:numbered="true" toc="default"> <name>RFC 5583: Signaling Media Decoding Dependency inSDP">SDP</name> <t><xreftarget="RFC5583"/>target="RFC5583" format="default"/> defines semantics that allow for signaling the decoding dependency of different media descriptions with the same media type in SDP. This is required, for example, if media data is separated and transported in different network streams as a result ofthe use ofusing a layered or multiple descriptive media coding process.</t><texttable title="8.5 RFC5583 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>group:DDP </c><c>Not Impacted </c> <c>S </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>depend lay </c><c>The<table align="center"> <name>RFC 5583 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:DDP</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">depend lay</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c><c>M</c> <c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> <c>depend mdc </c><c>Theconfiguration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">depend mdc</td> <td align="left">The attribute valueMUST<bcp14>MUST</bcp14> be the same for a given codecconfiguration </c><c>M</c> <c>IDENTICAL-PER-PT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>configuration.</td> <td align="left">M</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> <sectiontitle="RFC7104:numbered="true" toc="default"> <name>RFC 7104: Duplication Grouping Semantics in theSDP">SDP</name> <t><xreftarget="RFC7104"/>target="RFC7104" format="default"/> defines the semantics for grouping redundant streams inSDP,SDP. The semantics defined in this document are to be used with the SDP Grouping Framework. Grouping semantics at theSSRC)levelsynchronization source (SSRC) level are also defined in this document for RTP streams using SSRC multiplexing.</t><texttable title="8.6 RFC7104 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>group:DUP </c><c>Not Impacted </c><c>S </c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 7104 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:DUP</td> <td align="left">Not impacted</td> <td align="left">S</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> </section> <sectiontitle="ssrc-groupanchor="sec-ssrc-group" numbered="true" toc="default"> <name>ssrc-group AttributeAnalysis" anchor="sec-ssrc-group">Analysis</name> <t> This section analyzes "ssrc-group" semantics. </t> <sectiontitle="RFC5576:numbered="true" toc="default"> <name>RFC 5576: Source-Specific SDPAttributes">Attributes</name> <t><xreftarget="RFC5576"/>target="RFC5576" format="default"/> defines a mechanismto describefor describing RTP mediasources,sources -- which are identified by their synchronization source (SSRC)identifiers,identifiers -- in SDP, to associate attributes with thesesources,sources andtoexpress relationships among sources. It also defines several source-level attributes that can be used to describe properties of media sources.</t><texttable title="9.1 RFC5576 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ssrc-group:FID </c><c>Not Impacted </c> <c>SR</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ssrc-group:FEC </c><c>Not Impacted </c> <c>SR</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>ssrc-group:FEC-FR </c><c>Not Impacted </c> <c>SR</c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 5576 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">ssrc-group:FID</td> <td align="left">Not impacted</td> <td align="left">SR</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ssrc-group:FEC</td> <td align="left">Not impacted</td> <td align="left">SR</td> <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> <sectiontitle="RFC7104:numbered="true" toc="default"> <name>RFC 7104: Duplication Grouping Semantics in theSDP">SDP</name> <t><xreftarget="RFC7104"/>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 semantics at theSynchronization Sourcesynchronization source (SSRC) level are also defined in this document for RTP streams using SSRC multiplexing.</t><texttable title="9.2 RFC7104 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ssrc-group:DUP </c><c>Not Impacted </c> <c>SR</c> <c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 7104 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">ssrc-group:DUP</td> <td align="left">Not impacted</td> <td align="left">SR</td> <td align="left">NORMAL</td> </tr> </tbody> </table> </section> </section> <sectiontitle="QoSanchor="SecqostokenAnalysis" numbered="true" toc="default"> <name>QoS Mechanism TokenAnalysis" anchor="SecqostokenAnalysis">Analysis</name> <t> This section analyzes QoS tokes specified with SDP. </t> <sectiontitle="RFC5432:numbered="true" toc="default"> <name>RFC 5432: QoS Mechanism Selection inSDP">SDP</name> <t><xreftarget="RFC5432"/>target="RFC5432" format="default"/> defines procedures to negotiateQOSQoS mechanisms using the SDP offer/answer model.</t><texttable title="10.1 RFC5432 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rsvp </c><c>rsvp<table align="center"> <name>RFC 5432 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">rsvp</td> <td align="left">rsvp attributeMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlying transportflow </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> <c>nsis </c><c>rsvpflow.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> <tr> <td align="left">nsis</td> <td align="left">rsvp attributeMUST<bcp14>MUST</bcp14> be the one that corresponds to the "m=" line chosen for setting up the underlyingtransport </c> <c>B</c><c>TRANSPORT </c> <c> </c><c> </c><c> </c><c> </c> </texttable>transport.</td> <td align="left">B</td> <td align="left">TRANSPORT</td> </tr> </tbody> </table> <t>NOTE: A single Differentiated Services Code Point (DSCP)code point perfor each flow being multiplexed doesn't impactmultiplexingmultiplexing, sinceQOSQoS mechanisms are signaled/scoped per flow. For scenarios that involve having different DSCP code points for packets being transmitted over the same 5-tuple, issues as discussed in <xreftarget="RFC7657"/>target="RFC7657" format="default"/> need to be taken into consideration.</t> </section> </section> <sectiontitle="k=anchor="SeckAnalysis" numbered="true" toc="default"> <name>k= AttributeAnalysis" anchor="SeckAnalysis">Analysis</name> <sectiontitle="RFC4566: SDP">numbered="true" toc="default"> <name>RFC 4566: SDP</name> <t><xreftarget="RFC4566"/>target="RFC4566" format="default"/> defines SDP that is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation.</t><texttable title="11.1 RFC4566 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>k= </c> <c>It<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">k=</td> <td align="left">It is not recommended to use this attribute undermultiplexing </c><c>S</c> <c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable>multiplexing.</td> <td align="left">S</td> <td align="left">CAUTION</td> </tr> </tbody> </table> </section> </section> <sectiontitle="contentanchor="SeccontentAnalysis" numbered="true" toc="default"> <name>content AttributeAnalysis" anchor="SeccontentAnalysis">Analysis</name> <sectiontitle="RFC4796">numbered="true" toc="default"> <name>RFC 4796</name> <t><xreftarget="RFC4796"/>target="RFC4796" format="default"/> defines a new SDP media-level attribute,'content'."content". The'content'"content" attribute defines the content of the media stream to a more detailed level than the media description line. The sender of an SDP session description can attach the'content'"content" attribute to one or more media streams. The receiving application can then treat each media stream differently (e.g., show it on a big or small screen) based on its content.</t><texttable title="12.1 RFC4796 Attribute Analysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>content:slides </c><c>Not Impacted </c> <c>M </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>content:speaker </c><c>Not Impacted </c> <c>M </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>content:main </c><c>Not Impacted </c> <c>M </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>content:sl </c><c>Not Impacted </c> <c>M </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> <c>content:alt </c><c>Not Impacted </c> <c>M </c><c>NORMAL </c> <c> </c><c> </c><c> </c><c> </c> </texttable><table align="center"> <name>RFC 4796 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">content:slides</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">content:speaker</td> <td align="left">Not impacted</td> <td align="left">M</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">content:main</td> <td align="left">Not impacted</td> <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 numbered="true" toc="default"> <name>3GPP TS 24.182</name> <t> <xref target="IMS-CAT" format="default"/> specifies an IP multimedia subsystem 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> <section anchor="sec-pay"title="Payload Formats">numbered="true" toc="default"> <name>Payload Formats</name> <sectiontitle="RFC5109:numbered="true" toc="default"> <name>RFC 5109: RTP Payload Format for GenericFEC">FEC</name> <t><xreftarget="RFC5109"/>target="RFC5109" format="default"/> describes a payload format for generic Forward Error Correction (FEC) for media data encapsulated in RTP. It is based on the exclusive-or (parity) operation. The payload format allows end systems to apply protection using various protection lengths and levels, in addition to using various protection group sizes to adapt to different media and channel characteristics. It enables complete recovery of the protected packets or partial recovery of the critical parts of thepayloadpayload, depending on the packet loss situation.</t><texttable title="13.1 RFC5109<table align="center"> <name>RFC 5109 Payload FormatAnalysis"> <ttcol align='left'>Name</ttcol> <ttcol align='left'>Notes</ttcol> <ttcol align='left'>Level</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>audio/ulpfec </c> <c>NotAnalysis</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">audio/ulpfec</td> <td align="left">Not recommended for multiplexing due to reuse ofSSRCs </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>video/ulpfec </c> <c>NotSSRCs.</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">video/ulpfec</td> <td align="left">Not recommended for multiplexing due to reuse ofSSRCs </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>text/ulpfec </c> <c>NotSSRCs.</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> <tr> <td align="left">text/ulpfec</td> <td align="left">Not recommended for multiplexing due to reuse ofSSRCs </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> <c>application/ulpfec </c> <c>NotSSRCs.</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 ofSSRCs </c> <c>M</c><c>CAUTION </c> <c> </c><c> </c><c> </c><c> </c> </texttable>SSRCs.</td> <td align="left">M</td> <td align="left">CAUTION</td> </tr> </tbody> </table> </section> </section> <sectiontitle="Multiplexinganchor="sec-encap" numbered="true" toc="default"> <name>Multiplexing Considerations for EncapsulatingAttributes" anchor="sec-encap">Attributes</name> <t>Thissectionssection deals with recommendations for defining the multiplexing characteristics of the SDP attributes that encapsulate other SDP attributes/parameters.Such attributes asAs of today, such attributes, for example, are defined in <xreftarget="RFC3407"/>,target="RFC3407" format="default"/>, <xreftarget="RFC5939"/>target="RFC5939" format="default"/> and <xreftarget="RFC6871"/>target="RFC6871" format="default"/> as part of a generic framework for indicating and negotiatingtransport, media,transport-, media-, andmedia format relatedmedia-format-related capabilities in the SDP.</t> <t>The behavior of such attributes under multiplexingisis, inturnturn, defined by the multiplexing behavior of the attributes theyencapsulateencapsulate, which are made known once theOffer/Answeroffer/answer negotiation process is completed.</t> <sectiontitle="RFC3407:numbered="true" toc="default"> <name>RFC 3407: cpar AttributeAnalysis"> <t>Analysis</name> <t>The <xreftarget="RFC3407"/>target="RFC3407" format="default"/> capability parameter attribute(a=cpar)"a=cpar" encapsulatesb=a "b=" (bandwidth) or ana="a=" attribute. For bandwidth attribute encapsulation, the category SUM is inherited. For the case ofa="a=" attribute, the category corresponding to the SDP attribute being encapsulated is inherited. </t><t> <figure> <artwork align="left" alt="" height="" name="" type="" width="" xml:space="preserve"><![CDATA[<sourcecode type="sdp"> v=0 o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com s= c=IN IP4 host.atlanta.example.com t=0 0 m=video 3456 RTP/AVP 100 a=rtpmap:100 VP8/90000 a=sqn: 0 a=cdsc: 1 video RTP/AVP 100 a=cpar: a=rtcp-mux m=video 3456 RTP/AVP 101 a=rtpmap:101 VP8/90000 a=fmtp:100 max-fr=15;max-fs=1200 a=cdsc: 2 video RTP/AVP 101 a=cpar:a=rtcp-mux ]]></artwork> </figure> </t> <t> Ina=rtcp-mux</sourcecode> <t>In this example, theabove example,thecategory IDENTICAL is inherited for thecpar encapsulated rtcp-muxcpar-encapsulated "rtcp-mux" attribute. </t><t> </t><t></t> </section> <sectiontitle="RFC5939 Analysis">numbered="true" toc="default"> <name>RFC 5939 Analysis</name> <t><xreftarget="RFC5939"/>target="RFC5939" format="default"/> defines a general SDP capability negotiation framework. It also specifies how to provide transport protocols and SDP attributes as capabilities and negotiate them using the framework.</t> <t>For this purpose, <xreftarget="RFC5939"/>target="RFC5939" format="default"/> defines thefollowing <list style="symbols"> <t>Afollowing: </t> <ul spacing="normal"> <li>A set of capabilities for the session and its associatedmedia streammedia-stream components, supported by each side. The attribute("a=acap")"a=acap" defines how to list an attribute name and its associated value (if any) as a capability. The attribute("a=tcap")"a=tcap" defines how to list transport protocols (e.g., "RTP/AVP") ascapabilities.</t> <t>Acapabilities.</li> <li>A set of potential configurations ("a=pcfg") provided by the offerer to indicate which combinations of those capabilities can be used for the session and its associated media stream components. Potential configurations are not ready for use until fully negotiated. They provide an alternative thatMAY<bcp14>MAY</bcp14> be used, subject to SDPcapability negotiationcapability-negotiation procedures. Inparticularparticular, the answererMAY<bcp14>MAY</bcp14> choose one of the potential configurations for use as part of the currentOffer/Answer exchange.</t> <t>Anoffer/answer exchange.</li> <li>An actual configuration ("a=acfg") for the session and its associated media stream components. The actual configuration identifies the potential configuration that was negotiated for use. Use of an actual configuration does not require any furthernegotiation.</t> <t>Anegotiation.</li> <li>A negotiation process that takes the current actual and the set of potential configurations (combinations of capabilities) as input and provides the negotiated actual configurations as output. In <xreftarget="RFC5939"/>target="RFC5939" format="default"/>, the negotiation process is done independently for each mediadescription.</t> </list> </t>description.</li> </ul> <sectiontitle="Recommendation:anchor="sec-cap-neg-proc" numbered="true" toc="default"> <name>Recommendation: Procedures for Potential ConfigurationPairing" anchor="sec-cap-neg-proc">Pairing</name> <t>This section provides recommendations for entities generating and processing SDP under the genericcapability negotiationcapability-negotiation framework as defined in <xreftarget="RFC5939"/>target="RFC5939" format="default"/> under the context ofmedia streammedia-stream multiplexing.</t> <t>These recommendations are provided for the purposes of enabling theOffererofferer to make sure that the generated potential configurations between the multiplexed streams can (easily) be negotiated to be consistent between those streams. In particular, the procedures aim to simplifyAnswerer'sthe answerer's procedureto choosefor choosing potential configurations that are consistent across all the multiplexed media descriptions.</t> <t>A potential configuration selects a set of attributes and parameters that become part of the media description when negotiated. When multiplexing media descriptions with potential configurations specified, thereMAY<bcp14>MAY</bcp14> be a need for coordinating this selection between multiplexed media descriptions to ensure the right multiplexing behavior.</t><t> Although<t>Although it is possible to analyze the various potential configurations in multiplexed media descriptions to find combinations that satisfy such constraints, it can quickly become complicated to do so. </t><t> The<t>The procedures defined in <xreftarget="RFC5939"/>target="RFC5939" format="default"/> state that each potential configuration in the SDP has a unique configurationnumber, howevernumber; however, the scope of uniqueness is limited to each media description. To make it simple for the answerer to chose valid combinations of potential configurations across media descriptions in a givenbundleBUNDLE group, we provide a simple rule for constructing potentialconfigurations <list style="symbols"> <t> Letconfigurations: </t> <ul spacing="normal"> <li>Let m-bundle be the set of media descriptions that form a givenbundle .</t> <t> Letbundle.</li> <li>Let m-bundle-pcfg be the set of media descriptions in m-bundle that include one or more potentialconfigurations.</t> <t> Eachconfigurations.</li> <li>Each media description in m-bundle-pcfgMUST<bcp14>MUST</bcp14> have at least one potential configuration with the same configuration number(e.g. "1").</t> <t> For(e.g., "1").</li> <li>For each potential configuration with configuration number x in m-bundle-pcfg, the offererMUST<bcp14>MUST</bcp14> ensure that if the answerer chooses configuration number x in each of the media descriptions in m-bundle-pcfg, then the resulting SDP will have all multiplexing constraints satisfied for those mediadescriptions.</t> <t> Sincedescriptions.</li> <li>Since it is nearly impossible to define a generic mechanism for various capability extensions, this documentdoes'tdoesn't provide procedures for dealing with thecapability extensioncapability-extension attributes. However, <xreftarget="med-cap-analysis"/> providetarget="med-cap-analysis" format="default"/> provides analysis ofmedia capability extensionmedia-capability-extension attributes as defined in <xreftarget="RFC6871"/>. </t> </list> </t> <t> Thetarget="RFC6871" format="default"/>. </li> </ul> <t>The above allows the answerer to easily findmultiplexing compatiblemultiplexing-compatible combinations of potentialconfigurations:configurations. The answerer simplychoseschooses a potential configuration (number) that is present in all of the media descriptions with potential configurations in the bundle.</t><t> Note<t>Note that it is still possible for the offerer to provide additional potential configurations with independent configuration numbers. The answerer will have to perform more complicated analysis to determine valid multiplexed combinations of those.</t> <sectiontitle="Example: Transport Capability Multiplexing"> <figure title=""> <artwork><![CDATA[numbered="true" toc="default"> <name>Example: Transport-Capability Multiplexing</name> <sourcecode type="sdp"> v=0 o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com s= c=IN IP4 host.atlanta.example.com t=0 0 a=tcap:1 RTP/SAVPF a=tcap:2 RTP/SAVP a=group:BUNDLE audio video m=audio a=mid:audio a=pcfg:1 t=1 a=pcfg:2 m=video a=mid:video a=pcfg:1 t=1 a=pcfg:2 t=2]]></artwork> </figure></sourcecode> <t>Inthe example above,this example, the potential configurations that offertransport protocoltransport-protocol capability of RTP/SAVPFhashave the same configuration number "1" in both the audio and video media descriptions.</t> </section> <sectiontitle="Example: Attribute Capability Multiplexing"> <figure title=""> <artwork><![CDATA[numbered="true" toc="default"> <name>Example: Attribute-Capability Multiplexing</name> <sourcecode type="sdp"> v=0 o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com s= c=IN IP4 host.atlanta.example.com t=0 0 a=acap:1 a=rtcp-mux a=acap:2 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32 a=group:BUNDLE audio video m=audio 49172 RTP/AVP 99 a=mid:audio a=pcfg:1 a=1 a=pcfg:2 m=video 560024 RTP/AVP 100 a=mid:video a=pcfg:1 a=1 a=pcfg:2 a=2]]></artwork> </figure></sourcecode> <t>Inthe example above,this example, the potential configuration number "1" is repeated while referring to attribute capability a=rtcp-mux, since the behavior is IDENTICAL for the attribute a=rtcp-mux under multiplexing.</t> </section> </section> </section> <sectiontitle = "RFC6871 Analysis" anchor="med-cap-analysis">anchor="med-cap-analysis" numbered="true" toc="default"> <name>RFC 6871 Analysis</name> <t><xreftarget="RFC6871"/>target="RFC6871" format="default"/> extends the capability negotiation framework described in <xreftarget="RFC5939"/>target="RFC5939" format="default"/> by defining media capabilities that can be used to indicate and negotiate media types and their associated format parameters. It also allows indication of latent configurations and session capabilities.</t> <sectiontitle="Recommendation:numbered="true" toc="default"> <name>Recommendation: Dealing with Payload TypeNumbers">Numbers</name> <t><xreftarget="RFC6871"/>target="RFC6871" format="default"/> defines a new payload type("pt")parameter ("pt") to be used with the potential, actual, and latent configuration parameters. The parameter associates RTP payload type numbers with the referenced RTP-basedmedia formatmedia-format capabilities ("a=rmcap") defined in <xreftarget="RFC6871"/>target="RFC6871" format="default"/> and is appropriate only when the transport protocol uses RTP. This means that the same payload type number can be assigned as part of potential or actual configurations in different media descriptions in a bundle. There are rules for the usage of identicalPayload Typepayload type values across multiplexed "m="lines aslines, described in <xreftarget="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>,target="RFC8843" format="default"/>, which must be followedherehere, as well. As described in <xreftarget="sec-cap-neg-proc"/>,target="sec-cap-neg-proc" format="default"/>, the use of identical configuration numbers for compatible configurations in different media descriptions that are part of the bundle provides a way to ensure that the answerer can easily pick compatible configurationsherehere, as well.</t> <sectiontitle="Example:numbered="true" toc="default"> <name>Example: Attribute CapabilityUnderunder Shared PayloadType">Type</name> <t>The attributes(a=rmcap, a=mfcap)"a=rmcap" and "a=mfcap" follow the above recommendations under multiplexing.</t><figure title=""> <artwork><![CDATA[<sourcecode type="sdp"> v=0 o=- 25678 753849 IN IP4 192.0.2.1 s= c=IN IP4 192.0.2.1 t=0 0 a=creq:med-v0 m=audio 54322 RTP/AVP 96 a=rtpmap:96 AMR-WB/16000/1 a=fmtp:96 mode-change-capability=1; max-red=220; mode-set=0,2,4,7 a=rmcap:1,3 audio AMR-WB/16000/1 a=rmcap:2 audio AMR/8000/1 a=mfcap:1,2 mode-change-capability=1 a=mfcap:3 mode-change-capability=2 a=pcfg:1 m=1 pt=1:96 a=pcfg:2 m=2 pt=2:97 a=pcfg:3 m=3 pt=3:98 m=audio 54322 RTP/AVP 96 a=rtpmap:96 AMR-WB/16000/1 a=fmtp:96 mode-change-capability=1; max-red=220; mode-set=0,2,4,7 a=rmcap:4 audio AMR/8000/1 a=rmcap:5 audio OPUS/48000/2 a=mfcap:5 minptime=40 a=mfcap:4 mode-change-capability=1 a=pcfg:1 m=4 pt=4:97 a=pcfg:4 m=5 pt=5:101]]> </artwork> </figure></sourcecode> <t>Inthe example above,this example, the potential configuration number "1" is repeated when referring to media andmedia formatmedia-format capability used for the Payload Type 96. This implies that boththemediacapabilitycapabilities 2 and44, along with theirmedia format capabilities MUSTmedia-format capabilities, <bcp14>MUST</bcp14> refer to the same codec configuration, as per the definition of IDENTICAL-PER-PT.</t> </section> </section> <sectiontitle="Recommendation:numbered="true" toc="default"> <name>Recommendation: Dealing with LatentConfigurations">Configurations</name> <t><xreftarget="RFC6871"/>target="RFC6871" format="default"/> adds the notion of a latentconfigurations, whichconfiguration that provides configuration information that may be used to guide a subsequentoffer/exchange, e.g.offer/exchange -- e.g., by adding another media stream oruseusing alternative codec combinations not currently offered. Latent configurations have configuration numberswhichthat cannot overlap with the potential configuration numbers <xreftarget="RFC6871"/>.target="RFC6871" format="default"/>. Supported combinations of potential and latent configurations are indicated by use of the "a=sescap"attribute, howeverattribute; however, use of this attribute is not recommended with multiplexed media, since it requires the use of unique configuration numbers across the SDP. Taken together, this means there is no well-defined way to indicate supported combinations of latent configurations, or combinations of latent and potential configurations with multiplexed media. It is still allowed to use the latent configurationattribute, howeverattribute; however, the limitations above will apply. To determine valid combinations, actual negotiation will have to be attempted subsequently instead.</t> </section> </section> </section> <sectiontitle="IANA Considerations"> <t>[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this document.]</t> <t> <xref target="sec-mux-cat-iana"/>numbered="true" toc="default"> <name>IANA Considerations</name> <t><xref target="sec-mux-cat-iana" format="default"/> defines a newsubregistry to besubregistry, which has been added by theIANAIANA, for identifying the initial registrations for various multiplexing categories applicable, asproposeddescribed in this document.</t> <t>IANAis also requested to addhas added a new column named "Mux Category" to several of the subregistries in the "Session Description Protocol (SDP) Parameters" registry. The tables in <xreftarget="sec-mux-cat-values-iana"/>target="sec-mux-cat-values-iana" format="default"/> identifynamethe names ofan entryentries in the existing subregistry and specify the value to be put in the new "Mux Category" column of the associated IANAregistry.</t>registry for each.</t> <sectiontitle="New 'Multiplexing Categories' subregistry " anchor="sec-mux-cat-iana">anchor="sec-mux-cat-iana" numbered="true" toc="default"> <name>New "Multiplexing Categories" Subregistry</name> <t>A newsub-registry needs to be definedsubregistry has been created. It is calledthe"MultiplexingCategories", withCategories" and has the following registrationscreated initially: "NORMAL", "CAUTION", "IDENTICAL", "TRANSPORT", "SUM", "INHERIT", "IDENTICAL-PER-PT", "SPECIAL" and "TBD" as defined in this document.</t> <t>Initial value registration for "Multiplexing Categories".</t> <texttableinitially:</t> <table align="left"><ttcol align='left'>Multiplexing Categories</ttcol> <ttcol align='left'>Reference</ttcol> <c>NORMAL </c><c> RFCXXXX</c> <c>CAUTION </c><c> RFCXXXX</c> <c>IDENTICAL </c><c> RFCXXXX</c> <c>TRANSPORT </c><c> RFCXXXX</c> <c>SUM </c><c> RFCXXXX</c> <c>INHERIT </c><c> RFCXXXX</c> <c>IDENTICAL-PER-PT </c><c> RFCXXXX</c> <c>SPECIAL </c><c> RFCXXXX</c> <c>TBD </c><c> RFCXXXX</c> </texttable> <t> Further<thead> <tr> <th align="left">Multiplexing Categories</th> <th align="left">Reference</th> </tr> </thead> <tbody> <tr> <td align="left">NORMAL</td> <td align="left">RFC 8859</td> </tr> <tr> <td align="left">CAUTION</td> <td align="left">RFC 8859</td> </tr> <tr> <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 outlined in <xreftarget="RFC5226"/>,target="RFC8126" format="default"/>, which requires IESG review and approval andstandards-trackStandards Track IETF RFC publication.</t><t> Each<t>Each registration needs to indicate the multiplexing category value to be added to the "Multiplexing Categories"subregistrysubregistry, as defined in this section.</t><t> Such<t>Such a registrationMUST<bcp14>MUST</bcp14> also indicate the applicability of the newly defined multiplexing category value to various subregistries definedatin the "Session Description Protocol (SDP) Parameters" registry.</t> </section> <sectiontitle="'Mux Category' column for subregistries"anchor="sec-mux-cat-values-iana"toc="default"> <t> Each sub-sectiontoc="default" numbered="true"> <name>"Mux Category" Column for Subregistries</name> <t>Each subsection identifies a subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The tables list the column that identifies the SDP attribute name/Token/Value from the corresponding subregistries and the values to be used for the new "Mux Category" column to be added.</t><t> For the entries<t>Entries in the existingsubregistries, undersubregistries of the "Session Description Protocol (SDP) Parameters"registry,registry that lack a value for the "Mux Category" in this specification will get a value of "TBD".</t><t> The<t>The registration policy for updates to the'Mux Category'"Mux Category" column values for existing parameters, or when registering new parameters,areis beyond the scope of this document. The registration policy for the affected table is defined in <xreftarget="I-D.ietf-mmusic-rfc4566bis"/>.</t>target="RFC8866" format="default"/>.</t> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: SDPbwtype">bwtype</name> <t>The following valuesare to behave been added to the'SDP bwtype'"bwtype" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references.</t><texttable<table align="left"><ttcol align='left'>SDP Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>CT </c><c>NORMAL </c> <c>AS </c><c>SUM </c> <c>RS </c><c>SUM </c> <c>RR </c><c>SUM </c> <c>TIAS </c><c>SPECIAL </c> </texttable> </section> <section title="Table: att-field (session level)"><thead> <tr> <th align="left">SDP Name</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <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 valuesare to behave been added to the"att-field (session level)""attribute-name" (formerly "att-field") subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous 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><t>NOTE: Thefollowing values are to be addedattributes from <xref target="I-D.ietf-rmt-flute-sdp" format="default"/> ("flute-tsi", "flute-ch", "FEC-declaration", "FEC-OTI-extension", "content-desc") were not analyzed for their multiplexing behavior, due 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 ofexpired status of the draft. For the purposes of this specification, the multiplexing category of'TBD'"TBD" is assigned. </t><texttable align="left"> <ttcol align='left'>SDP Name</ttcol> <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<!-- [rfced] Follow-up question re: 2. "etag" row from section 15.2.2. needs tothe "att-field (media level only)" registry in the "Session Description Protocol (SDP) Parameters" registry. The references shouldbeupdated to point at this RFCremoved as well The IANA registry (https://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml#sdp-att-field) lists this document as a reference for etag. So, should theprevious references. </t> <texttable align="left"> <ttcol align='left'>SDP Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ptime </c><c>IDENTICAL-PER-PT </c> <c>orient </c><c>NORMAL </c> <c>orient:portrait </c><c>NORMAL </c> <c>orient:landscape </c><c>NORMAL </c> <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 toetag row beadded to the "att-field (source level)" registryrestored inthe "Session Description Protocol (SDP) Parameters" registry. The referencesSection 15.2.2, or should the IANA registry be updated topoint atremove thisRFC as welldocument as a reference? (If theprevious references. </t> <texttablelatter, we will send a request to IANA.) --> <table align="left"><ttcol align='left'>SDP Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>cname </c><c>NORMAL </c> <c>previous-ssrc </c><c>NORMAL </c> <c>fmtp </c><c>IDENTICAL-PER-PT </c> <c>ts-refclk </c><c>NORMAL </c> <c>mediaclk </c><c>NORMAL </c> </texttable><thead> <tr> <th align="left">SDP Name</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">cat</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">keywds</td> <td align="left">NORMAL</td> </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> <!-- (both session and media level) --> <tr> <td align="left">recvonly</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">sendrecv</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">sendonly</td> <td align="left">NORMAL</td> </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> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: content SDPParameters">Parameters</name> <t>The following valuesare to behave been added to the "content SDP Parameters" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>SDP Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>slides </c><c>NORMAL </c> <c>speaker </c><c>NORMAL </c> <c>sl </c><c>NORMAL </c> <c>main </c><c>NORMAL </c> <c>alt </c><c>NORMAL </c> </texttable><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> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: Semantics for the'group'"group" SDPAttribute">Attribute</name> <t>The following valuesare to behave been added to the "Semantics for the"group"'group' SDP Attribute" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references.</t><texttable<table align="left"><ttcol align='left'>Token</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>LS </c><c>NORMAL </c> <c>FID </c><c>NORMAL </c> <c>SRF </c><c>NORMAL </c> <c>ANAT </c><c>CAUTION </c> <c>FEC </c><c>NORMAL </c> <c>FEC-FR </c><c>NORMAL </c> <c>CS </c><c>NORMAL </c> <c>DDP </c><c>NORMAL </c> <c>DUP </c><c>NORMAL </c> </texttable><thead> <tr> <th align="left">Token</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">LS</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">FID</td> <td align="left">NORMAL</td> </tr> <tr> <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> <sectiontitle="Table: 'rtcp-fb'numbered="true" toc="default"> <name>Table: "rtcp-fb" AttributeValues">Values</name> <t>The following valuesare to behave been added to the" 'rtcp-fb'"'rtcp-fb' Attribute Values" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references.</t><texttable<table align="left"><ttcol align='left'>Value Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ack </c><c>IDENTICAL-PER-PT </c> <c>app </c><c>SPECIAL </c> <c>ccm </c><c>IDENTICAL-PER-PT </c> <c>nack </c><c>IDENTICAL-PER-PT </c> <c>trr-int </c><c>IDENTICAL-PER-PT </c> </texttable><thead> <tr> <th align="left">Value Name</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">ack</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">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> <sectiontitle="Table: 'ack'numbered="true" toc="default"> <name>Table: "ack" and'nack'"nack" AttributeValues">Values</name> <t>The following valuesare to behave been added to the" 'ack'"'ack' and 'nack' Attribute Values" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references.</t><texttable<table align="left"><ttcol align='left'>Value Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>sli </c><c>IDENTICAL-PER-PT </c> <c>pli </c><c>IDENTICAL-PER-PT </c> <c>rpsi </c><c>IDENTICAL-PER-PT </c> <c>app </c><c>SPECIAL </c> <c>rai </c><c>IDENTICAL-PER-PT </c> <c>tllei </c><c>IDENTICAL-PER-PT </c> <c>pslei </c><c>IDENTICAL-PER-PT </c> <c>ecn </c><c>IDENTICAL </c> </texttable><thead> <tr> <th align="left">Value Name</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">sli</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">pli</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <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> <sectiontitle="Table: 'depend'numbered="true" toc="default"> <name>Table: "depend" SDP AttributeValues"> <t> TheValues</name> <t>The following valuesare to behave been added to the" 'depend'"'depend' SDP Attribute Values" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>Token</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>lay </c><c>IDENTICAL-PER-PT </c> <c>mdc </c><c>IDENTICAL-PER-PT </c> </texttable><thead> <tr> <th align="left">Token</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">lay</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <tr> <td align="left">mdc</td> <td align="left">IDENTICAL-PER-PT</td> </tr> </tbody> </table> </section> <sectiontitle="Table: 'cs-correlation'numbered="true" toc="default"> <name>Table: "cs-correlation" AttributeValues"> <t> TheValues</name> <t>The following valuesare to behave been added to the" "cs-correlation""'cs-correlation' Attribute Values" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>Value</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>callerid </c><c>TBD </c> <c>uuie </c><c>TBD </c> <c>dtmf </c><c>TBD </c> <c>external </c><c>TBD </c> </texttable><thead> <tr> <th align="left">Value</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">callerid</td> <td align="left">TBD</td> </tr> <tr> <td align="left">uuie</td> <td align="left">TBD</td> </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> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: Semantics for the'ssrc-group'"ssrc-group" SDPAttribute"> <t> TheAttribute</name> <t>The following valuesare to behave been added to theSemantics for the"Semantics for the"ssrc-group"'ssrc-group' SDP Attribute" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>Token</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>FID </c><c>NORMAL </c> <c>FEC </c><c>NORMAL </c> <c>FEC-FR </c><c>NORMAL </c> <c>DUP </c><c>NORMAL </c> </texttable><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> </section> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: SDP/RTSPkey management protocol identifiers">Key Management Protocol Identifiers</name> <t>The following valuesare to behave been added to the "SDP/RTSP key management protocol identifiers" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references.</t><texttable<table align="left"><ttcol align='left'>Value Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>mikey </c><c>IDENTICAL </c> </texttable><thead> <tr> <th align="left">Value Name</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">mikey</td> <td align="left">IDENTICAL</td> </tr> </tbody> </table> </section> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: Codec ControlMessages"> <t> TheMessages</name> <t>The following valuesare to behave been added to the "Codec Control Messages" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>Value Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>fir </c><c>IDENTICAL-PER-PT </c> <c>tmmbr </c><c>IDENTICAL-PER-PT </c> <c>tstr </c><c>IDENTICAL-PER-PT </c> <c>vbcm </c><c>IDENTICAL-PER-PT </c> </texttable><thead> <tr> <th align="left">Value Name</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">fir</td> <td align="left">IDENTICAL-PER-PT</td> </tr> <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> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: QoS MechanismTokens"> <t> TheTokens</name> <t>The following valuesare to behave been added to the "QoS Mechanism Tokens" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>QoS Mechanism</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>rsvp </c><c>TRANSPORT </c> <c>nsis </c><c>TRANSPORT </c> </texttable><thead> <tr> <th align="left">QoS Mechanism</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <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> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: SDP Capability Negotiation OptionTags"> <t> TheTags</name> <t>The following valuesare to behave been added to the "SDP Capability Negotiation Option Tags" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>Option Tag</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>cap-v0 </c><c>NORMAL </c> <c>med-v0 </c><c>NORMAL </c> <c>bcap-v0 </c><c>NORMAL </c> <c>ccap-v0 </c><c>NORMAL </c> <c>icap-v0 </c><c>NORMAL </c> </texttable><thead> <tr> <th align="left">Option Tag</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">cap-v0</td> <td align="left">NORMAL</td> </tr> <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> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: Timestamp Reference Clock SourceParameters"> <t> TheParameters</name> <t>The following valuesare to behave been added to the "Timestamp Reference Clock Source Parameters" subregistryinof the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>ntp </c><c>NORMAL </c> <c>ptp </c><c>NORMAL </c> <c>gps </c><c>NORMAL </c> <c>gal </c><c>NORMAL </c> <c>glonass </c><c>NORMAL </c> <c>local </c><c>NORMAL </c> <c>private </c><c>NORMAL </c> </texttable><thead> <tr> <th align="left">Name</th> <th align="left">Mux Category</th> </tr> </thead> <tbody> <tr> <td align="left">ntp</td> <td align="left">NORMAL</td> </tr> <tr> <td align="left">ptp</td> <td align="left">NORMAL</td> </tr> <tr> <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> <sectiontitle="Table:numbered="true" toc="default"> <name>Table: Media Clock SourceParameters"> <t> TheParameters</name> <t>The following valuesare to behave been added to the "Media Clock Source Parameters"subegistry insubregistry of the "Session Description Protocol (SDP) Parameters" registry. The referencesshould behave been updated to pointatto this RFC as well as the previous references. </t><texttable<table align="left"><ttcol align='left'>Name</ttcol> <ttcol align='left'>Mux Category</ttcol> <c>sender </c><c>NORMAL </c> <c>direct </c><c>NORMAL </c> <c>IEEE1722 </c><c>NORMAL </c> </texttable><thead> <tr> <th align="left">Name</th> <th align="left">Mux Category</th> </tr> </thead> <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> <sectiontitle="Security Considerations">numbered="true" toc="default"> <name>Security Considerations</name> <t> The primary security considerations forRTPRTP, including the way it is usedhere ishere, are described in <xreftarget="RFC3550"/>target="RFC3550" format="default"/> and <xreftarget="RFC3711"/>.target="RFC3711" format="default"/>. </t> <t> When multiplexing SDP attributes with the category "CAUTION", the implementations should be aware of possible issuesasdescribed in this specification. </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</middle> <back> <displayreference target="I-D.ietf-rmt-flute-sdp" to="FLUTE"/> <references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4566.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <!-- draft-ietf-mmusic-sdp-bundle-negotiation (RFC 8843) --> <reference anchor="RFC8843" target="https://www.rfc-editor.org/info/rfc8843"> <front> <title>Negotiating Media Multiplexing Using theIANA review. </t> <t> Thanks to Ben Campbell for AD review suggestions. Thanks to Spencer Dawkins, Stephen Farrel, Alissa Cooper, Mirja Kuehlewind and the entire IESG experts 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 attributes 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-mmusic-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-mmusic-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-mmusic-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 clarity. </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> </middle> <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"> <organization>Harvard University</organization> <address> <postal> <street>1350 Mass. Ave.</street> <street>Cambridge</street> <street>MA 02138</street> </postal> <phone>- +1 617 495 3864</phone> <email>sob@harvard.edu</email> </address> </author> <date month="March" year="1997" /> <area>General</area> <keyword>keyword</keyword> </front> <seriesInfo name="BCP" value="14" /> <seriesInfo name="RFC" value="2119" /> <format octets="4723" target="http://www.rfc-editor.org/rfc/rfc2119.txt" type="TXT" /> <format octets="17491" target="http://xml.resource.org/public/rfc/html/rfc2119.html" type="HTML" /> <format octets="5777" target="http://xml.resource.org/public/rfc/xml/rfc2119.xml" type="XML" /> </reference> </references> <references title="Informative References"> &RFC2326; &RFC3108; &RFC3264; &RFC3312; &RFC3407; &RFC3524; &RFC3550; &RFC3556; &RFC3605; &RFC3611; &RFC3711; &RFC3890; &RFC4091; &RFC4145; &RFC4567; &RFC4568; &RFC4570; &RFC4572; &RFC4574; &RFC4583; &RFC4585; &RFC4796; &RFC4975; &RFC5104; &RFC5109; &RFC5159; &RFC5245; &RFC5285; &RFC5432; &RFC5506; &RFC5547; &RFC5576; &RFC5583; &RFC5760; &RFC5761; &RFC5762; &RFC5763; &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.xml"> <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>ProceduresSession Description Protocol (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> </references> <references> <name>Informative References</name> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2326.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3108.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3264.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3312.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3407.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3524.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3556.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3605.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3611.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3711.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3890.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4091.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4145.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4567.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4568.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.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/reference.RFC.8122.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4574.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4583.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4585.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4796.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4975.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5104.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5109.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5159.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.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/reference.RFC.8285.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5432.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5506.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5547.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5576.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5583.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5760.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5761.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5762.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5763.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5888.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5939.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5956.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6064.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6128.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6189.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6193.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6230.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6236.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6284.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6285.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6364.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6642.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6679.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6714.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6773.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6787.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6849.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6871.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6947.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7006.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7104.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7197.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7195.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7272.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7273.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7266.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7657.xml"/> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7826.xml"/> <!-- draft-ietf-mmusic-rfc4566bis (RFC 8866) --> <reference anchor="RFC8866" target="https://www.rfc-editor.org/info/rfc8866"> <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> <reference anchor="IANA" target="https://www.iana.org/assignments/sdp-parameters"> <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><author/> <date/><seriesInfo name="ITU-T Recommendation" value="T.38"/> <author> <organization>ITU-T</organization> </author> <date month="November" year="2015"/> </front> </reference> <referenceanchor='H.248.15' target="http://www.itu.int/rec/T-REC-H.248.15">anchor="H.248.15" target="https://www.itu.int/rec/T-REC-H.248.15"> <front><title> Gateway<title>Gateway control protocol: SDP ITU-T H.248 package attribute</title><author/> <date/><seriesInfo name="ITU-T Recommendation" value="H.248.15"/> <author> <organization>ITU-T</organization> </author> <date month="March" year="2013"/> </front> </reference> <referenceanchor='Q.1970'anchor="Q.1970" target="https://www.itu.int/rec/T-REC-Q.1970-200609-I/en"> <front><title> Q.1970 :<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/><seriesInfo name="ITU-T Recommendation" value="Q.1970"/> <author> <organization>ITU-T</organization> </author> <date month="September" year="2006"/> </front> </reference> <referenceanchor='R3GPPTS24.229' target="http://www.3gpp.org/ftp/Specs/html-info/24229.htm">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);</title> <author/> <date/>(SDP); Stage 3</title> <seriesInfo name="Specification" value="24.229"/> <author> <organization>3GPP</organization> </author> <date month="September" year="2016"/> </front> </reference> <referenceanchor='R3GPPTS183.063' target="http://www.etsi.org/deliver/etsi_ts/183000_183099/183063/02.01.00_60/ts_183063v020100p.pdf">anchor="TISPAN" target="https://www.etsi.org/deliver/etsi_ts/183000_183099/183063/02.01.00_60/ts_183063v020100p.pdf"> <front> <title>TISPAN - IMS based ITPV StageTelecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3specification.</title> <author/> <date/>specification</title> <seriesInfo name="Technical Specification" value="183 063 V2.1.0"/> <author> <organization>ETSI</organization> </author> <date month="June" year="2008"/> </front> </reference> <referenceanchor='R3GPPTS24.182' target="http://www.3gpp.org/ftp/Specs/html-info/24182.htm">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><author/> <date/><seriesInfo name="Specification" value="24.182"/> <author> <organization>3GPP</organization> </author> <date month="January" year="2015"/> </front> <seriesInfo name="Specification" value="24.182"/> </reference> <referenceanchor='R3GPPTS24.183' target="http://www.3gpp.org/ftp/Specs/html-info/24183.htm">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/> <date/><author> <organization>3GPP</organization> </author> <date month="September" year="2016"/> </front> <seriesInfo name="Specification" value="24.183"/> </reference> <!-- draft-ietf-rmt-flute-sdp-03 is expired --> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-rmt-flute-sdp.xml"/> <!-- draft-ietf-bfcpbis-rfc4583bis: 8856 --> <reference anchor='RFC8856' target="https://www.rfc-editor.org/info/rfc8856"> <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> </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 improved the document's readability. </t> <t> I would like also to thank the following experts for their inputs and reviews as listed: </t> <ul empty="true" spacing="compact"> <li><t><contact fullname="Flemming Andreasen"/> (5.24, 5.32, 5.33, 14),</t></li> <li><t><contact fullname="Rohan Mahy"/> (5.54),</t></li> <li><t><contact fullname="Eric Burger"/> (5.26),</t></li> <li><t><contact fullname="Christian Huitema"/> (5.14),</t></li> <li><t><contact fullname="Christer Holmberg"/> (5.21, 5.26, 12.2, 12.3),</t></li> <li><t><contact fullname="Richard Ejzak"/> (5.44, 5.50, 5.51),</t></li> <li><t><contact fullname="Colin Perkins"/> (5.7, 5.8, 5.9, 5.55),</t></li> <li><t><contact fullname="Magnus Westerlund"/> (5.2, 5.3, 5.9, 5.27, 5.47, 6.1 - 6.3, 8.3, 7),</t></li> <li><t><contact fullname="Roni Even"/> (5.12, 5.27, 8.4),</t></li> <li><t><contact fullname="Subha Dhesikan"/> (5.6, 10),</t></li> <li><t><contact fullname="Dan Wing"/> (5.7, 5.12, 5.35, 5.39, 5.45),</t></li> <li><t><contact fullname="Cullen Jennings"/> (5.40),</t></li> <li><t><contact fullname="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),</t></li> <li><t><contact fullname="Bo Burman"/> (7.2, 7.6),</t></li> <li><t><contact fullname="Charles Eckel"/> (5.15, 5.27, 5.28, 9.1, 8.5),</t></li> <li><t><contact fullname="Paul Kyzivat"/> (5.24),</t></li> <li><t><contact fullname="Ian Johansson"/> (5.15),</t></li> <li><t><contact fullname="Saravanan Shanmugham"/> (5.11),</t></li> <li><t><contact fullname="Paul E Jones"/> (5.30),</t></li> <li><t><contact fullname="Rajesh Kumar"/> (5.48),</t></li> <li><t><contact fullname="Jonathan Lennox"/> (5.36, 5, 15, 9.1, 11.1),</t></li> <li><t><contact fullname="Mo Zanaty"/> (5.4, 5.5, 5.23, 8.1, 8.3, 8.5, 12.1),</t></li> <li><t><contact fullname="Christian Huitema "/> (5.14),</t></li> <li><t><contact fullname="Qin Wu"/> (5.47, PM-Dir review),</t></li> <li><t><contact fullname="Hans Stokking"/> (5.43, 5.16),</t></li> <li><t><contact fullname="Christian Groves"/> (5.48, 5.52), and</t></li> <li><t><contact fullname="Thomas Stach"/>.</t></li> </ul> <t> I would like to thank <contact fullname="Chris Lonvick"/> for the SECDIR 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> </rfc>