<?xml version="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 for SDP Session
    Description Protocol (SDP) Attributes
    when When 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>
    <date day="28" month="February" year="2018"/>

    <area>MMUSIC</area> month="May" year="2020"/>
    <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>
    <section title="Introduction" anchor="sec-intro">
       <t> SDP anchor="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. Typically Typically, different media types
        (audio, video, etc.) described using different media descriptions
        represent separate RTP sessions that are carried over individual
        transport layer
        transport-layer flows. However However, <xref target="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, for example example, allow the usage of a
        single set of Interactive Connectivity Establishment (ICE) <xref target="RFC5245"/> target="RFC8445" format="default"/>
        candidates for multiple media descriptions. This This, in turn turn, 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
        <xref target="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
        multiplexing use-cases.</t>
      <t> The use cases.</t>
      <t>The document starts with providing the motivation for
        requiring such a framework. This is followed by introduction
        to the SDP attribute analysis framework/procedures, framework and procedures, following
        which several sections apply the framework to the SDP
        attributes registered with the <xref target="IANA"></xref>. target="IANA" format="default"/>.
      </t>
    </section>
    <section title="Terminology">
      <t>5-tuple: A numbered="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-layer protocol.</t>
       <t>3GPP: Third protocol.</dd>
      <dt>3GPP:</dt><dd>Third Generation Partnership Project; see
        http://www.3gpp.org
        <eref target="https://www.3gpp.org" brackets="angle"/> for more information about this
        organization.</t>
      <t>The
        organization.</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&nbsp;14 <xref
      target="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>

    <section title="Motivation">
      <t>The numbered="true" toc="default">
      <name>Motivation</name>
      <t>
   An effort to reduce the number of necessary transport-level flows is
   required because of the time and complications of involved in setting up ICE <xref
        target="RFC5245"></xref> and Datagram Transport Layer Security
        (DTLS) based
   Secure Real-time Transport Protocol (SRTP) <xref
        target="RFC5763"></xref> target="RFC5763"/>
   transports for use by RTP, reasons
        to conserve RTP based on ICE <xref target="RFC8445"/> and
   Datagram Transport Layer Security (DTLS).  These procedures motivate
   conservation of ports bindings on the Network Address Translators (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 <xref target="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 combinations
        which
        that 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 specified ice-ufrag "ice-ufrag" attribute. However, if the
        media from multiple "m=" lines is multiplexed over the same ICE
        component, then the meaning of media-level ice-ufrag "ice-ufrag"
        attributes becomes muddled.</t>
      <t>At the time of writing this document document, there are close to 250 SDP
      	attributes registered with the <xref target="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>
    <section title="SDP anchor="sec-mux-fwork" numbered="true" toc="default">
      <name>SDP Attribute Analysis Framework" anchor="sec-mux-fwork"> Framework</name>
      <t>Attributes in an SDP session description can be defined at the
       session-level or media-level
       session level, media level, or source-level. source level. Informally, there are
       various semantic groupings for these attributes. One such grouping
       could be notes as below:</t>
	  <t>
       <list style="symbols">
         <t>Attributes follows:</t>
      <ul spacing="normal">
        <li>Attributes related to media content such as media type,
         encoding schemes schemes, and payload types.</t>
         <t>Attributes types.</li>
        <li>Attributes specifying media transport characteristics like such as
          RTP/RTP Control Protocol (RTCP) port numbers, network addresses addresses,
          and QOS.</t>
         <t>Metadata QoS.</li>
        <li>Metadata description attributes capturing session timing and
          origin information.</t>
         <t>Attributes information.</li>
        <li>Attributes establishing relationships between media descriptions descriptions,
          such as grouping framework <xref target="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>
      <section title="Category: NORMAL"> numbered="true" toc="default">
        <name>Category: NORMAL</name>
        <t>The attributes in the NORMAL category can be independently
        specified when multiplexed multiplexed, and they retain their original
        semantics.</t>
         <t>&nbsp;</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 single transport layer transport-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>&nbsp;</t>
</sourcecode>

      </section>
      <section title="Category: CAUTION">
        <t>The numbered="true" toc="default">
        <name>Category: CAUTION</name>
        <t>It is not advisable to multiplex with the attributes in the CAUTION category are advised
         against multiplexing
	category, since their usage under multiplexing
         might lead to incorrect behavior.</t>
        <t>&nbsp;</t>

        <t>Example: Multiplexing media descriptions over a single
         Datagram Congestion Control Protocol (DCCP) transport
         <xref target="RFC5762"/> target="RFC5762" format="default"/> is not recommended recommended,
         since DCCP being is a connection oriented connection-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>&nbsp;</t>
</sourcecode>

      </section>
      <section title="Category: IDENTICAL"> numbered="true" toc="default">
        <name>Category: IDENTICAL</name>
        <t>The attributes and their associated values (if any) in the
         IDENTICAL category MUST <bcp14>MUST</bcp14> be repeated across all the
         media descriptions under multiplexing.</t>
         <t>&nbsp;</t>

        <t>Attributes such as rtcp-mux fall into this category. Since
          RTCP reporting is done per RTP session, RTCP Multiplexing
          MUST multiplexing
          <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>&nbsp;</t>
</sourcecode>

        <t>Note: Eventhough Even though IDENTICAL attributes must be repeated across all media
       descriptions under multiplexing, they might not always be explicitly encoded across
       all media descriptions. <xref target="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>
      <section title="Category: SUM"> numbered="true" toc="default">
        <name>Category: SUM</name>
        <t>The attributes in the SUM category can be set as they are
         normally used used, but software using them in the multiplexing scenario
         MUST
         <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 other rate limiting rate-limiting attributes to the
         underlying transport.</t>
         <t>&nbsp;</t>

        <t>
          The software parsing the SDP sample below, 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>&nbsp;</t>
</sourcecode>

      </section>
      <section title="Category: TRANSPORT">
        <t> The numbered="true" toc="default">
        <name>Category: TRANSPORT</name>
        <t>The attributes in the TRANSPORT category can be set normally
         for multiple items in a multiplexed group group, but the software MUST <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>&nbsp;</t>

        <t>In the example below, the "a=crypto" attribute is defined for both
         the audio and the video "m=" lines. The video media line's a=crypto
         attribute is chosen since its mid value (bar) appears first in
         the a=group:BUNDLE line. This is due to the BUNDLE grouping semantic
         <xref target="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 the a=group:BUNDLE line to be considered for
         setting up the RTP Transport.</t>
       <figure>
         <artwork align="left" alt="" height="" name="" type="" width=""
                   xml:space="preserve"><![CDATA[ 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>&nbsp;</t>
</sourcecode>

      </section>
      <section title="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 <xref target="RFC3407"/>, target="RFC3407" format="default"/>,
        <xref target="RFC5939"/> target="RFC5939" format="default"/>, and <xref target="RFC6871"/> target="RFC6871"
	format="default"/> as part of a
        generic framework for indicating and negotiating capabilities in the
	SDP related to transport, media, and media format 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
       <xref target="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
       attributes MUST <bcp14>MUST</bcp14> be coherent in order to form a valid configuration from a
       multiplexing point of view (see <xref target="sec-encap"/> target="sec-encap" format="default"/> for
       further details).</t>
       <t>&nbsp;</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>In the above this example, the category IDENTICAL is inherited by
       the cpar encapsulated rtcp-mux cpar-encapsulated "rtcp-mux" attribute.</t>
      <t>&nbsp;</t>

      </section>
      <section title="Category: IDENTICAL-PER-PT">
        <t> The numbered="true" toc="default">
        <name>Category: IDENTICAL-PER-PT</name>
        <t>The attributes in the IDENTICAL-PER-PT category define
         the RTP payload configuration on per Payload Type the basis of the payload type, and
         MUST they
         <bcp14>MUST</bcp14> have identical values across all the media descriptions
         for a given RTP Payload Type payload type when repeated.

	 These Payload Types payload types
         identify the same codec configuration as defined in the Section
         10.1.2 of <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/> target="RFC8843"
	 sectionFormat="of" section="9.1"/>
         under this context.</t>
        <t>&nbsp;</t>

        <t>In the SDP example below, Payload Types 96 and 97 are repeated
         across all the video "m=" lines lines, and all the payload specific payload-specific
         parameters (ex: rtpmap, (for example, rtpmap and fmtp) are identical identical.
         (Note: some line breaks included are due to formatting only).</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>&nbsp;</t> max-br=200</sourcecode>

      </section>
      <section title="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 attribute MUST <bcp14>MUST</bcp14> be consulted for further
      handling when multiplexed. </t>
        <t>As an exampe, example, for the attribute extmap "extmap" <xref target="RFC5285"/>, target="RFC5285" format="default"/>,
      the specification defining the extension needs to be referred consulted to
      understand the multiplexing implications.</t>
      </section>
      <section title="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 and SHOULD NOT <bcp14>SHOULD NOT</bcp14> be multiplexed.</t>
      </section>
    </section>
    <section title="Analysis anchor="sec-cur-analysis" numbered="true" toc="default">
      <name>Analysis of Existing Attributes" anchor="sec-cur-analysis" > Attributes</name>
      <t>This section analyzes attributes listed in <xref
      target="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 -- Session level</t>
          <t>M level</li>
        <li>M -- Media level</t>
          <t>B level</li>
        <li>B -- Both (Implies either a session level or a media level attribute)</t>
          <t>SR attribute)</li>
        <li>SR -- Source-level (for a single SSRC) <xref target="RFC5576"/></t>
        </list>
      </t> target="RFC5576" format="default"/></li>
      </ul>
      <t>The "Mux Category" column identifies the multiplexing category
      assigned
      per attribute to each attribute, and the "Notes" column captures additional
      informative details regarding the assigned category, wherever
      necessary.</t>

      <section title="RFC4566: SDP"> numbered="true" toc="default">
        <name>RFC 4566: SDP</name>
        <t><xref target="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&nbsp;</c><c>Not impacted&nbsp;</c><c>B&nbsp;</c>
        <c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>sendonly&nbsp;</c><c>Not impacted&nbsp;</c><c>B&nbsp;</c>
        <c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>recvonly&nbsp;</c><c>Not impacted&nbsp;</c><c>B&nbsp;</c>
        <c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>inactive&nbsp;</c><c>Not impacted&nbsp;</c><c>B&nbsp;</c>
        <c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>cat&nbsp;</c><c>Not impacted&nbsp;</c><c>S&nbsp;</c>
        <c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>ptime&nbsp;</c><c>
        <table align="center">
          <name>RFC 4566 Attribute Analysis</name>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Notes</th>
              <th align="left">Level</th>
              <th align="left">Mux Category</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">sendrecv</td>
              <td align="left">Not impacted</td>
              <td align="left">B</td>
              <td align="left">NORMAL</td>
            </tr>
            <tr>
              <td align="left">sendonly</td>
              <td align="left">Not impacted</td>
              <td align="left">B</td>
              <td align="left">NORMAL</td>
            </tr>
            <tr>
              <td align="left">recvonly</td>
              <td align="left">Not impacted</td>
              <td align="left">B</td>
              <td align="left">NORMAL</td>
            </tr>
            <tr>
              <td align="left">inactive</td>
              <td align="left">Not impacted</td>
              <td align="left">B</td>
              <td align="left">NORMAL</td>
            </tr>
            <tr>
              <td align="left">cat</td>
              <td align="left">Not impacted</td>
              <td align="left">S</td>
              <td align="left">NORMAL</td>
            </tr>
            <tr>
              <td align="left">ptime</td>
              <td align="left"> The attribute value MUST <bcp14>MUST</bcp14> be the same
        for a given codec configuration&nbsp;</c>
        <c>M&nbsp;</c><c>IDENTICAL-PER-PT</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>maxptime&nbsp;</c><c>The configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
            <tr>
              <td align="left">maxptime</td>
              <td align="left">The attribute value MUST <bcp14>MUST</bcp14> be the same
        for a given codec configuration&nbsp;</c>
        <c>M&nbsp;</c><c>IDENTICAL-PER-PT</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>orient&nbsp;</c><c>Not Impacted
          &nbsp;</c><c>M&nbsp;</c><c>NORMAL</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>framerate&nbsp;</c><c>The configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
            <tr>
              <td align="left">orient</td>
              <td align="left">Not impacted</td>
              <td align="left">M</td>
              <td align="left">NORMAL</td>
            </tr>
            <tr>
              <td align="left">framerate</td>
              <td align="left">The attribute value MUST <bcp14>MUST</bcp14> be the same
        for a given codec configuration&nbsp;</c><c>M&nbsp;</c>
        <c>IDENTICAL-PER-PT&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>quality&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>M&nbsp;</c><c>NORMAL</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>rtpmap&nbsp;</c><c>The configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
            <tr>
              <td align="left">quality</td>
              <td align="left">Not impacted</td>
              <td align="left">M</td>
              <td align="left">NORMAL</td>
            </tr>
            <tr>
              <td align="left">rtpmap</td>
              <td align="left">The attribute value MUST <bcp14>MUST</bcp14> be the same
        for a given codec configuration&nbsp;</c><c>M&nbsp;</c>
        <c>IDENTICAL-PER-PT</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>fmtp&nbsp;</c><c>The configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
            <tr>
              <td align="left">fmtp</td>
              <td align="left">The attribute value MUST <bcp14>MUST</bcp14> be the same
        for a given codec configuration&nbsp;</c><c>M&nbsp;</c>
        <c>IDENTICAL-PER-PT</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>keywds&nbsp;</c><c>Not impacted&nbsp;</c><c>S&nbsp;</c>
        <c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>type&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

		    <c>type:broadcast&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

		    <c>type:H332&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

		    <c>type:meeting&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

		    <c>type:moderated&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

		    <c>type:test&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>tool&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>charset&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>S&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>sdplang&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>B&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        <c>lang&nbsp;</c><c>Not Impacted
        &nbsp;</c><c>B&nbsp;</c><c>NORMAL&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

      </texttable> 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>

      <section title="RFC4585: RTP/AVPF"> numbered="true" toc="default">
        <name>RFC 4585: RTP/AVPF</name>
        <t><xref target="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&nbsp;</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 are Payload Type
        (PT) scoped, scoped by payload type
        (PT), their values MUST <bcp14>MUST</bcp14> be identical for a given PT across
        the multiplexed "m=" lines.</c><c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
        <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

      </texttable> lines.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC5761: numbered="true" toc="default">
        <name>RFC 5761: Multiplexing RTP and RTCP"> RTCP</name>
        <t><xref target="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&nbsp;</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 RTCP Multiplexing multiplexing affects the
          entire RTP session&nbsp;</c>
          <c>M&nbsp;</c><c>IDENTICAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> session.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC3312: numbered="true" toc="default">
        <name>RFC 3312: Integration of Resource Management and SIP"> SIP</name>
        <t><xref target="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&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>conf&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>curr&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 in Session session establishment failures due to inability
         to meet right the requested resource reservations requested.</t> reservations.</t>
      </section>
      <section title="RFC4574: numbered="true" toc="default">
        <name>RFC 4574: SDP Label Attribute "> "label" Attribute</name>

        <t><xref target="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&nbsp;</c><c>Not Impacted&nbsp;</c><c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC5432: QOS numbered="true" toc="default">
        <name>RFC 5432: QoS Mechanism Selection in SDP"> SDP</name>
        <t><xref target="RFC5432"/> target="RFC5432" format="default"/> defines procedures to
        negotiate QOS for
        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&nbsp;</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 <xref target="SecqostokenAnalysis"/> &nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>qos-mech-recv&nbsp;</c>
          <c>Refer to <xref target="SecqostokenAnalysis"/> &nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC4568: numbered="true" toc="default">
        <name>RFC 4568: SDP Security Descriptions"> Descriptions</name>
        <t><xref target="RFC4568"/> target="RFC4568" format="default"/> defines a an 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&nbsp;</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 attribute MUST <bcp14>MUST</bcp14> be the one that corresponds
          to the "m=" line chosen for setting up the underlying transport flow </c>
          <c>M&nbsp;</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable>
	  flow. </td>
              <td align="left">M</td>
              <td align="left">TRANSPORT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC5762: numbered="true" toc="default">
        <name>RFC 5762: RTP over DCCP"> 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. <xref target="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&nbsp;</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"> If RFC6773 RFC 6773 is not being
          used in addition to RFC5762, the port in the "m=" line is a
          DCCP port. DCCP being Being a connection oriented protocol connection-oriented protocol, DCCP does
          not allow multiple connections on the same
          5-tuple&nbsp;</c> <c>M&nbsp;</c><c>CAUTION&nbsp;</c><c>&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable>
          5-tuple.</td>
              <td align="left">M</td>
              <td align="left">CAUTION</td>
            </tr>
          </tbody>
        </table>
        <t>
         NOTE: If RFC6773 RFC 6773 is being used in addition to RFC5762 RFC 5762, and provided
         that the
         DCCP-in-UDP layer has additional demultiplexing, then it
         can
         may be possible to use different DCCP service codes for each
         DCCP flow, given each uses a different DCCP port. Although However,
         doing so might conflict with the media type of the "m="
         line. None of this is standardized yet yet, and it wouldn't work
         as explained. Hence performing multiplexing is not recommended
         even in this alternate scenario.</t>
      </section>
      <section title="RFC6773: numbered="true" toc="default">
        <name>RFC 6773: DCCP-UDP Encapsulation"> Encapsulation</name>
        <t><xref target="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 boxes middleboxes
        without modification of those middle 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&nbsp;</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 DCCP
          en/decapsulation
          encapsulation/decapsulation and the RTP&nbsp;</c> <c>M&nbsp;</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 DCCP en-/de-capsulation encapsulation/decapsulation service.
	  This encapsulation allows arbitrary DCCP packets to be encapsulated encapsulated,
	  and the DCCP port chosen can conflict with
         the port chosen for the RTP traffic. For multiplexing

	 Multiplexing 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 can Whether or cannot work depending not this works depends on the nature
	 of DCCP encapsulation and ports choices thus rendering choices; it to be is thus very application
	 dependent.
        </t>
      </section>
      <section title="RFC5506: numbered="true" toc="default">
        <name>RFC 5506: Reduced-Size RTCP in RTP Profile"> Profile</name>
        <t><xref target="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&nbsp;</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 RTP session&nbsp;</c>
          <c>M&nbsp;</c><c>IDENTICAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> session.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6787: numbered="true" toc="default">
        <name>RFC 6787: Media Resource Control Protocol Version 2"> 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 and
        servers,
        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 the media processing media-processing
        resources on the speech resource server. <xref
        target="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&nbsp;</c><c>Not Impacted&nbsp;</c><c>M&nbsp;</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>channel&nbsp;</c><c>Not Impacted&nbsp;</c><c>M&nbsp;</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cmid&nbsp;</c><c>Not Impacted&nbsp;</c><c>M&nbsp;</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC5245: ICE"> numbered="true" toc="default">
        <name>RFC 8445: ICE</name>
        <t><xref target="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&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ice-options&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ice-mismatch&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ice-pwd&nbsp;</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 transport flow&nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ice-ufrag&nbsp;</c><c>ice-ufrag MUST flow.</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 transport flow&nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>candidate&nbsp;</c><c>ice flow.</td>
              <td align="left">B</td>
              <td align="left">TRANSPORT</td>
            </tr>
            <tr>
              <td align="left">candidate</td>
              <td align="left">ice candidate MUST <bcp14>MUST</bcp14> be the one that
          corresponds to the "m=" line chosen for setting up the
          underlying transport
          flow&nbsp;</c><c>M</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>remote-candidates&nbsp;</c><c>ice flow.</td>
              <td align="left">M</td>
              <td align="left">TRANSPORT</td>
            </tr>
            <tr>
              <td align="left">remote-candidates</td>
              <td align="left">ice remote candidate MUST <bcp14>MUST</bcp14>
          be the one that corresponds to the "m=" line chosen for setting
          up the underlying transport
          flow&nbsp;</c><c>M</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>

      <section title="RFC5285: numbered="true" toc="default">
        <name>RFC 5285: RTP Header Extensions"> Extensions</name>
        <t><xref target="RFC5285"/> target="RFC5285" format="default"/> provides a general
        mechanism to use for using the header extension header-extension feature of RTP. (Note: <xref
	target="RFC5285"/> has been obsoleted by <xref target="RFC8285"/>.)
        It provides the option to use a small number of small extensions
        in each RTP packet, where the universe of possible extensions is
        large and registration is de-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&nbsp;</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 RTP Extension&nbsp;</c> <c>B</c><c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> extension.</td>
              <td align="left">B</td>
              <td align="left">SPECIAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC3605: numbered="true" toc="default">
        <name>RFC 3605: RTCP attribute Attribute in SDP "> 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. <xref target="RFC3605"/> target="RFC3605" format="default"/> specifies an
	    early mechanism to indicate for 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&nbsp;</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 transport flow.&nbsp;</c>
          <c>M</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> flow.</td>
              <td align="left">M</td>
              <td align="left">TRANSPORT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC5576: numbered="true" toc="default">
        <name>RFC 5576: Source-Specific SDP Attributes"> Attributes</name>
        <t><xref target="RFC5576"/> target="RFC5576" format="default"/> defines a mechanism to
        describe for describing RTP
	media sources, sources -- which are identified by their
        synchronization source (SSRC) identifiers, identifiers -- in SDP, to
        associate attributes with these sources, sources and to express
        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&nbsp;</c><c>Refer to Notes
          below&nbsp;</c><c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ssrc-group&nbsp;</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 <xref target="sec-ssrc-group"></xref> target="sec-ssrc-group" format="default"/>
          for specific analysis of the grouping semantics&nbsp;</c><c>M</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cname&nbsp;</c> <c>Not Impacted&nbsp;</c><c>SR</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>previous-ssrc&nbsp;</c>
          <c>Refer to notes below&nbsp;</c><c>SR</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>fmtp&nbsp;</c><c>The semantics.</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 value MUST <bcp14>MUST</bcp14> be the same for a
          given codec configuration&nbsp;</c><c>SR</c>
          <c>IDENTICAL-PER-PT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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, they
         MUST
         <bcp14>MUST</bcp14> all represent the same underlying RTP Source.</t>
      </section>
      <section title="RFC7273: numbered="true" toc="default">
        <name>RFC 7273: RTP Clock Source Signalling"> Signaling</name>
        <t><xref target="RFC7273"/> target="RFC7273" format="default"/> specifies
        SDP signalling signaling that identifies  timestamp reference clock sources
        and SDP signalling signaling 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&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mediaclk&nbsp;</c>
          <c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ts-refclk:ntp&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ts-refclk:ptp&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ts-refclk:gps&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ts-refclk:gal&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ts-refclk:glonass&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ts-refclk:local&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ts-refclk:private&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mediaclk:sender&nbsp;</c>
          <c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mediaclk:direct&nbsp;</c>
          <c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mediaclk:IEEE1722&nbsp;</c>
          <c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC6236: numbered="true" toc="default">
        <name>RFC 6236: Image Attributes in SDP"> SDP</name>
        <t><xref target="RFC6236"/> target="RFC6236" format="default"/> proposes a new generic
        session setup attribute to make it possible to negotiate
        different image attributes attributes, such as image size. A possible
        use case is to make it possible for a low-end hand-held handheld
        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&nbsp;</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 value MUST <bcp14>MUST</bcp14> be the same
          for a given codec configuration&nbsp;</c><c>M&nbsp;</c>
          <c>IDENTICAL-PER-PT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC7197: numbered="true" toc="default">
        <name>RFC 7197: Duplication Delay Attribute in SDP"> SDP</name>
        <t><xref target="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&nbsp;</c><c>Not Impacted&nbsp;</c><c>B&nbsp;</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable>
        <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>
      <section title="RFC7266: numbered="true" toc="default">
        <name>RFC 7266: RTCP XR Blocks for MOS Metric Reporting"> Reporting</name>
        <t><xref target="RFC7266"/> target="RFC7266" format="default"/> defines an RTCP Extended Report (XR) Block
        including
        that includes two new segment types and associated SDP parameters that allow
        the reporting of mean opinion score (MOS) Metrics metrics 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&nbsp;</c><c>Not Impacted&nbsp;</c><c>B&nbsp;</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable>
        <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>
      <section title="RFC6285: numbered="true" toc="default">
        <name>RFC 6285: Rapid Acquisition of Multicast RTP Sessions"> Sessions</name>
        <t><xref target="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 reference information to the receiver precedes or
        accompanies the multicast stream. This unicast RTP flow can
        be transmitted at a faster than natural faster-than-natural bitrate to further
        accelerate the acquisition. The motivating use case for
        this capability is multicast applications that carry
        real-time compressed audio and video.</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&nbsp;</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
          &nbsp;</c><c>M&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable>
          </td>
              <td align="left">M</td>
              <td align="left">CAUTION</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6230: numbered="true" toc="default">
        <name>RFC 6230: Media Control Channel Framework"> Framework</name>
        <t><xref target="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&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC6364: numbered="true" toc="default">
        <name>RFC 6364: SDP Elements for FEC Framework"> Framework</name>
        <t><xref target="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&nbsp;</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
           FEC Scheme&nbsp;</c><c>M&nbsp;</c>
          <c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>fec-repair-flow&nbsp;</c><c>Refer scheme.</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
           FEC Scheme&nbsp;</c><c>M&nbsp;</c>
          <c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>repair-window&nbsp;</c><c>Refer scheme.</td>
              <td align="left">M</td>
              <td align="left">SPECIAL</td>
            </tr>
            <tr>
              <td align="left">repair-window</td>
              <td align="left">Refer to the document defining specific
          FEC Scheme&nbsp;</c><c>M&nbsp;</c>
          <c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> scheme.</td>
              <td align="left">M</td>
              <td align="left">SPECIAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC4796: Content Attribute"> numbered="true" toc="default">
        <name>RFC 4796: "content" Attribute</name>
        <t><xref target="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&nbsp;</c><c>Not
          Impacted&nbsp;</c><c>M&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC3407: numbered="true" toc="default">
        <name>RFC 3407: SDP Simple Capability Declaration"> Declaration</name>
        <t><xref target="RFC3407"/> target="RFC3407" format="default"/> defines a set of SDP attributes that enables
        SDP to provide a minimal and backwards compatible backwards-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&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cdsc&nbsp;</c><c>Not
          Impacted.&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cpar&nbsp;</c><c>Refer to <xref target="sec-encap"/>&nbsp;</c>
          <c>B</c><c>INHERIT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cparmin&nbsp;</c><c>Refer to notes below &nbsp;</c>
          <c>B</c><c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cparmax&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>B</c><c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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" and a=cparmax) "a=cparmax" define minimum
         and maximum numerical values associated with the attributes
         described in a=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>
      <section title="RFC6284: numbered="true" toc="default">
        <name>RFC 6284: Port Mapping between Unicast and Multicast RTP Sessions"> Sessions</name>
        <t><xref target="RFC6284"/> target="RFC6284" format="default"/> presents a port
        mapping port-mapping solution that
	allows RTP receivers to choose their
        own ports for an auxiliary unicast session in RTP
        applications using both unicast and multicast services. The
        solution provides protection against denial-of-service or
        packet amplification attacks that could be used to cause one
        or more RTP packets to be sent to a victim client.</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&nbsp;</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 the application&nbsp;</c><c>M&nbsp;</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> application</td>
              <td align="left">M</td>
              <td align="left">CAUTION</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6714: MSRP-CEMA"> numbered="true" toc="default">
        <name>RFC 6714: MSRP-CEMA</name>
        <t><xref target="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 allows middle boxes middleboxes to
        anchor the MSRP connection, connection without the need for middle
        boxes middleboxes to modify
	the MSRP messages; thus, it also enables
        secure end-to-end MSRP communication in networks where such
        middle boxes
        middleboxes are deployed. This document also defines a an
        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&nbsp;</c><c>Refer to notes below&nbsp;</c><c>M&nbsp;</c>
          <c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 per section 9 of <xref target="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 MRSP MSRP flows
         over a single 5-tuple. Once such a specification is available,
         the assignments of multiplexing categories assignments for the attributes in this
         section could be revisited.</t>
      </section>
      <section title="RFC4583: numbered="true" toc="default">
        <name>RFC 4583: SDP Format for BFCP Streams"> Streams</name>
        <t><xref target="RFC4583"/> document target="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&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>TBD&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c>

          <c>confid&nbsp;</c><c>Not Impacted&nbsp;</c><c>M&nbsp;</c>
          <c>NORMAL&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>userid&nbsp;</c><c>Not
          Impacted&nbsp;</c><c>M&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>floorid&nbsp;</c>
          <c>Not Impacted&nbsp;</c>
          <c>M&nbsp;</c><c>NORMAL&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c>

        </texttable>
        <t>NOTE: As per section 9 of
         <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/>, there

<!--[rfced] Per mail from Ben Campbell on 2018-12-20, we have updated the
table below and the one in Section 15.2.4.  However, now this document
does not match the IANA registry. Which one is correct? (If this document
is correct, we will send a request to IANA to update the registry.)

> The update is to change the mux-category for 3 BFCP parameters (confid,
> userid, and floorid) from “NORMAL” to “TBD”
-->

        <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: <xref target="RFC4583"/> has been obsoleted by
	<xref target="RFC8856"/>, which redefines the SDP attributes
	listed in this section, including the "Mux Category" values. However,
	<xref target="RFC8856"/> does not change the "Mux Category"
	values of the attributes.</t>

        <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 categories assignments for the attributes in this
        section could be revisited.</t>
      </section>
      <section title="RFC5547: numbered="true" toc="default">
        <name>RFC 5547: SDP Offer/Answer for File Transfer"> Transfer</name>
        <t><xref target="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
        <xref target="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&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>file-transfer-id&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>file-disposition&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>file-date&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>file-icon&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

		  <c>file-range&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 per section 9 of <xref target="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 MRSP MSRP flows
         over a single 5-tuple. Once such a specification is available,
         the assignments of multiplexing categories assignments for attributes in this
         section could be revisited.</t>
      </section>
      <section title="RFC6849: numbered="true" toc="default">
        <name>RFC 6849: SDP and RTP Media Loopback Extension"> Extension</name>
        <t><xref target="RFC6849"/> target="RFC6849" format="default"/> adds new SDP media
        types and attributes, which attributes 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&nbsp;</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 value MUST <bcp14>MUST</bcp14> be
          same for a given codec configuration&nbsp;</c>
          <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>loopback rtp-media-loopback&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be
          same for a given codec configuration &nbsp;</c>
          <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>loopback-source&nbsp;</c><c>Not Impacted&nbsp;</c><c>M</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>loopback-mirror&nbsp;</c><c>Not Impacted&nbsp;</c><c>M</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC5760: numbered="true" toc="default">
        <name>RFC 5760: RTCP with Unicast Feedback "> Feedback</name>
        <t><xref target="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 as Source-Specific Multicast source-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&nbsp;</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 attribute MUST <bcp14>MUST</bcp14> be reported
          across all multiplexed "m=" lines
          multiplexed&nbsp;</c><c>M</c><c>IDENTICAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> lines.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC3611: numbered="true" toc="default">
        <name>RFC 3611: RTCP XR"> XR</name>
        <t><xref target="RFC3611"/> target="RFC3611" format="default"/> defines the Extended
        Report (XR) packet type for RTCP, 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&nbsp;</c><c>Not Impacted&nbsp;</c><c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC5939: numbered="true" toc="default">
        <name>RFC 5939: SDP Capability Negotiation"> Negotiation</name>
        <t><xref target="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&nbsp;</c>
          <c>Refer to <xref target="sec-encap"/> &nbsp;</c>
          <c>M</c><c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>acfg&nbsp;</c>
          <c>Refer to <xref target="sec-encap"/>&nbsp;</c>
          <c>M</c><c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>csup&nbsp;</c><c>Not Impacted&nbsp;</c><c>B</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>creq&nbsp;</c><c>Not Impacted&nbsp;</c><c>B</c>
          <c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>acap&nbsp;</c>
          <c>Refer to <xref target="sec-encap"/>&nbsp;</c>
          <c>B</c><c>INHERIT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>tcap&nbsp;</c>
          <c>Refer to <xref target="sec-encap"/>&nbsp;</c>
          <c>B</c><c>INHERIT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cap-v0&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC6871: numbered="true" toc="default">
        <name>RFC 6871: SDP Media Capabilities Negotiation"> Negotiation</name>
        <t>SDP capability negotiation provides a general framework
        for indicating and negotiating capabilities in SDP. The base
        framework defines only defines capabilities for negotiating transport
        protocols and attributes. <xref target="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&nbsp;</c>
          <c>Refer to <xref target="sec-encap"/>&nbsp;</c>
          <c>B</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>omcap&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mfcap&nbsp;</c>
          <c>Refer to <xref target="sec-encap"/>&nbsp;</c>
          <c>B</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mscap&nbsp;</c>
          <c>Refer to <xref target="sec-encap"/>&nbsp;</c>
          <c>B</c><c>INHERIT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>lcfg&nbsp;</c>
          <c>Refer to <xref target="sec-encap"/>&nbsp;</c>
          <c>B</c><c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>sescap&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>S</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>med-v0&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 <xref target="RFC6871"/>) target="RFC6871" format="default"/>) as opposed to within a media
        description only (per <xref target="RFC5939"/>). target="RFC5939" format="default"/>). As described in
        <xref target="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>
      <section title="RFC7006: numbered="true" toc="default">
        <name>RFC 7006: Miscellaneous Capabilities Negotiation SDP"> in SDP</name>
        <t><xref target="RFC7006"/> target="RFC7006" format="default"/> extends the SDP capability negotiation Capability 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&nbsp;</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 to b= attribute&nbsp;</c>
          <c>B</c><c>INHERIT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>bcap-v0&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ccap&nbsp;</c><c>The the "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 type
          MUST
          <bcp14>MUST</bcp14> be identical across all the multiplexed
          "m=" lines&nbsp;</c>
          <c>B</c><c>IDENTICAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ccap-v0&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>icap&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>icap-v0&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC4567: numbered="true" toc="default">
        <name>RFC 4567: Key Management Extensions for SDP and RTSP"> RTSP</name>
        <t><xref target="RFC4567"/> target="RFC4567" format="default"/> defines general
        extensions for SDP and Real Time Streaming Protocol (RTSP) to
        carry messages, as specified by a key management protocol, in
        order to secure the media. These extensions are presented as
        a framework, 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&nbsp;</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 protocol MUST <bcp14>MUST</bcp14> be
          identical across all the "m=" lines&nbsp;</c><c>B</c>
          <c>IDENTICAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mikey&nbsp;</c><c>Key lines.</td>
              <td align="left">B</td>
              <td align="left">IDENTICAL</td>
            </tr>
            <tr>
              <td align="left">mikey</td>
              <td align="left">Key management protocol MUST <bcp14>MUST</bcp14> be
          identical across all the "m=" lines&nbsp;</c><c>B</c>
          <c>IDENTICAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> lines.</td>
              <td align="left">B</td>
              <td align="left">IDENTICAL</td>
            </tr>
          </tbody>
        </table>
      </section>

      <section title="RFC4572: numbered="true" toc="default">
        <name>RFC 4572: Comedia over TLS in SDP"> SDP</name>
        <t><xref target="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&nbsp;</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 value MUST <bcp14>MUST</bcp14> be the
          one that corresponds to the "m=" line chosen for
          setting up the underlying transport flow&nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> flow.</td>
              <td align="left">B</td>
              <td align="left">TRANSPORT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC4570: numbered="true" toc="default">
        <name>RFC 4570: SDP Source Filters"> Filters</name>
        <t><xref target="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 inclusive
         source-filter source filter can be
	used to specify a Source-Specific
        Multicast source-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&nbsp;</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 attribute MUST <bcp14>MUST</bcp14> be repeated
          across all multiplexed "m=" lines
          multiplexed&nbsp;</c><c>B</c><c>IDENTICAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> lines.</td>
              <td align="left">B</td>
              <td align="left">IDENTICAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6128: numbered="true" toc="default">
        <name>RFC 6128: RTCP Port for Multicast Sessions"> 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 avoid ambiguity, ambiguity and
        thus,
        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. <xref target="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&nbsp;</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 port MUST <bcp14>MUST</bcp14> be
          identical across all the
          "m=" lines&nbsp;</c><c>B</c><c>IDENTICAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> lines.</td>
              <td align="left">B</td>
              <td align="left">IDENTICAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6189: ZRTP"> numbered="true" toc="default">
        <name>RFC 6189: ZRTP</name>
        <t><xref target="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 (VoIP VoIP 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&nbsp;</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 attribute MUST <bcp14>MUST</bcp14> be the one
          that corresponds to the "m=" line chosen for setting up
          the underlying transport flow&nbsp;</c><c>M</c>
          <c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> flow.</td>
              <td align="left">M</td>
              <td align="left">TRANSPORT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC4145: numbered="true" toc="default">
        <name>RFC 4145: Connection-Oriented Media "> Media</name>
        <t><xref target="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 connection
        reestablishment.</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&nbsp;</c>
          <c>The
        re-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 attribute MUST <bcp14>MUST</bcp14> be the one that corresponds to the "m="
          line chosen for setting up the underlying transport flow.&nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>connection&nbsp;</c>
          <c>The flow.</td>
              <td align="left">B</td>
              <td align="left">TRANSPORT</td>
            </tr>
            <tr>
              <td align="left">connection</td>
              <td align="left">The connection attribute MUST <bcp14>MUST</bcp14> be the one that corresponds to the
          "m=" line chosen for setting up the underlying transport flow.&nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> flow.</td>
              <td align="left">B</td>
              <td align="left">TRANSPORT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6947: numbered="true" toc="default">
        <name>RFC 6947: The SDP altc Attribute"> "altc" Attribute</name>
        <t><xref target="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 proposed attribute,
        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&nbsp;</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 IP Address address and port MUST <bcp14>MUST</bcp14> be the one ones
          that corresponds correspond to the "m=" line chosen for setting up the
          underlying transport flow&nbsp;</c>
          <c>M</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> flow.</td>
              <td align="left">M</td>
              <td align="left">TRANSPORT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC7195: numbered="true" toc="default">
        <name>RFC 7195: SDP Extension for Circuit Switched Circuit-Switched Bearers         in PSTN"> PSTN</name>
        <t><xref target="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&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cs-correlation:uuie&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cs-correlation:dtmf&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>cs-correlation:external&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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: <xref target="RFC7195"/> target="RFC7195" format="default"/> defines SDP attributes for
         establishing audio and video media streams over circuit-switched
         bearers by defining a new nettype value value, "PSTN". However, section 7.2 of
         <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"/> target="RFC8843" sectionFormat="of" section="7.2"/> requires the
         "c=" line nettype value of to be "IN". If in future there 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>
      <section title="RFC7272: numbered="true" toc="default">
        <name>RFC 7272: IDMS Using the RTP Control Protocol (RTCP)"> (RTCP)</name>
        <t><xref target="RFC7272"/> target="RFC7272" format="default"/> defines a new RTCP Packet Type packet 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&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC5159: numbered="true" toc="default">
        <name>RFC 5159: Open Mobile Alliance (OMA) Broadcast (BCAST) SDP Attributes"> Attributes</name>
        <t><xref target="RFC5159"/> target="RFC5159" format="default"/> provides descriptions
        of SDP attributes used by the
        Open Mobile Alliance's Broadcast 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&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>stkmstream&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>B</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>SRTPAuthentication&nbsp;</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 further analysis&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>SRTPROCTxRate&nbsp;</c><c>Needs analysis</td>
              <td align="left">M</td>
              <td align="left">TBD</td>
            </tr>
            <tr>
              <td align="left">SRTPROCTxRate</td>
              <td align="left">Needs further analysis&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> analysis</td>
              <td align="left">M</td>
              <td align="left">TBD</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6193: numbered="true" toc="default">
        <name>RFC 6193: Media Description for IKE in SDP"> SDP</name>
        <t><xref target="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&nbsp;</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 of
          multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>psk-fingerprint&nbsp;</c><c>Unlikely
          multiplexing</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 of
          multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ike-esp&nbsp;</c><c>Unlikely
          multiplexing</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 of
          multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>ike-esp-udpencap&nbsp;</c><c>Unlikely
          multiplexing</td>
              <td align="left">B</td>
              <td align="left">CAUTION</td>
            </tr>
            <tr>
              <td align="left">ike-esp-udpencap</td>
              <td align="left">Unlikely to use IKE in the context of
          multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable>
          multiplexing</td>
              <td align="left">B</td>
              <td align="left">CAUTION</td>
            </tr>
          </tbody>
        </table>
      </section>

<!--[rfced] RFC 2326 was obsoleted by RFC 7826. Is the information in the
table still accurate if we update citations?

Original:
This section analyzes attributes listed in [IANA], grouped under the
IETF document that defines them.
...
RFC2326: Real Time Streaming Protocol
-->
      <section title="RFC2326: numbered="true" toc="default">
        <name>RFC 2326: Real Time Streaming Protocol"> 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&nbsp;</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">RTSP is not supported for RTP Stream
          multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>range&nbsp;</c><c>RTSP stream
          multiplexing.</td>
              <td align="left">B</td>
              <td align="left">CAUTION</td>
            </tr>
            <tr>
              <td align="left">range</td>
              <td align="left">RTSP is not supported for RTP Stream
          multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>control&nbsp;</c><c>RTSP stream
          multiplexing.</td>
              <td align="left">B</td>
              <td align="left">CAUTION</td>
            </tr>
            <tr>
              <td align="left">control</td>
              <td align="left">RTSP is not supported for RTP Stream
          multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mtag&nbsp;</c><c>RTSP stream
          multiplexing.</td>
              <td align="left">B</td>
              <td align="left">CAUTION</td>
            </tr>
            <tr>
              <td align="left">mtag</td>
              <td align="left">RTSP is not supported for RTP Stream
          multiplexing&nbsp;</c><c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> stream
          multiplexing.</td>
              <td align="left">B</td>
              <td align="left">CAUTION</td>
            </tr>
          </tbody>
        </table>
        <t>NOTE: <xref target="RFC2326"/> 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 offer/answer usage of SDP
         is considered as to be mandated by <xref
         target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>.</t> target="RFC8843" format="default"/>.</t>
      </section>
      <section title="RFC6064: numbered="true" toc="default">
        <name>RFC 6064: SDP and RTSP Extensions for 3GPP"> 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. <xref
        target="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&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>X-initpredecbufperiod&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>X-initpostdecbufperiod&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>X-decbyterate</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3gpp-videopostdecbufsize&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>framesize</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 notes below&nbsp;</c><c>M</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-Integrity-Key&nbsp;</c>
          <c>Refer below</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 notes below&nbsp;</c><c>S</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-SDP-Auth&nbsp;</c>
          <c>Refer below</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 notes below&nbsp;</c><c>S</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-SRTP-Config&nbsp;</c>
          <c>Refer to notes below&nbsp;&nbsp;</c><c>M</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>alt&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>alt-default-id&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>alt-group&nbsp;</c>
          <c>Refer to notes below&nbsp;</c><c>S</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-Adaptation-Support&nbsp;</c>
          <c>Refer to notes below&nbsp;&nbsp;</c><c>M</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-Asset-Information&nbsp;</c>
          <c>Refer to notes below&nbsp;</c><c>B</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mbms-mode&nbsp;</c>
          <c>Refer to notes below&nbsp;</c><c>B</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mbms-flowid&nbsp;</c>
          <c>Refer to notes below&nbsp;</c><c>M</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>mbms-repair&nbsp;</c>
          <c>Refer to notes below&nbsp;</c><c>B</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Corruption duration&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Rebuffering duration&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Initial buffering duration&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Successive loss of RTP packets&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Frame rate deviation&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Jitter duration&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Content Switch Time&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>B</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Average below</td>
              <td align="left">B</td>
              <td align="left">CAUTION</td>
            </tr>
            <tr>
              <td align="left">3GPP-QoE-Metrics:Average Codec Bitrate&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Codec Information&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3GPP-QoE-Metrics:Buffer Status&nbsp;</c>
          <c>Refer to notes below&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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: <xref target="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 the Offer/Answer offer/answer usage of SDP
         is considered as to be mandated by <xref
         target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>. target="RFC8843" format="default"/>.
        </t>
      </section>
      <section title="RFC3108: numbered="true" toc="default">
        <name>RFC 3108: ATM SDP"> SDP</name>
        <t><xref target="RFC3108"></xref> target="RFC3108" format="default"/> describes conventions
        for using SDP described for controlling ATM Bearer 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&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>eecid&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>capability&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>qosClass&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>bcob&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>stc&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>upcc&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>atmQOSparms&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>atmTrfcDesc&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>abrParms&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>abrSetup&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>bearerType&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>lij&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>anycast&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>cache&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>bearerSigIE&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>aalApp&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>cbrRate&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>sbc&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>clkrec&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>fec&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>prtfl&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>structure&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>cpsSDUsize&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>aal2CPS&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>aal2CPSSDUrate&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>aal2sscs3661unassured&nbsp;</c>
          <c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>aal2sscs3661assured&nbsp;</c>
          <c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>aal2sscs3662&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>aal5sscop&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>atmmap&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>silenceSupp&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>ecan&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>gc&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>profileDesc&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>vsel&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>dsel&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>fsel&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>onewaySel&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>codecconfig&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>isup_usi&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>uiLayer1_Prot&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>chain&nbsp;</c><c>Refer to notes below</c>
          <c>B&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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: RFC3108 RFC 3108 describes conventions for using SDP for
        characterizing ATM bearer connections using an AAL1, AAL2 AAL2, or
        AAL5 adaptation layers. layer. For AAL1, AAL2 AAL2, 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, AAL2 AAL2, and AAL5), bearer connections can be bundled into a single media
        group. In all cases addressed by RFC3108, 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. RFC3108 RFC 3108 does not address cases where ATM serves
        as a low-level transport pipe for IP packets which that can, in turn can turn,
        carry one or more real-time (e.g. (e.g., VoIP) media sessions with a
        life-cycle
        life cycle different from that of the underlying ATM
        transport.</t>
      </section>

      <section title="3GPP TS 26.114">
        <t>
          <xref target="R3GPPTS26.114"/> specifies IP multimedia subsystem:
          Media handling and interaction
        </t>
        <texttable title="5.49 3GPP TS 26.114 Attribute Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>3gpp_sync_info&nbsp;</c>
          <c>Usage defined for the IP Multimedia Subsystem&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>3gpp_MaxRecvSDUSize&nbsp;</c>
          <c>Usage defined for the IP Multimedia Subsystem&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
        </texttable>
      </section>

      <section title="3GPP numbered="true" toc="default">
        <name>3GPP TS 183.063"> 183.063</name>
        <t>
          <xref target="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 Attribute Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>PSCid&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>bc_service&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>bc_program&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>bc_service_package&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>S</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 numbered="true" toc="default">
        <name>3GPP TS 24.182"> 24.182</name>
        <t>
          <xref target="R3GPPTS24.182"/> target="IMS-CAT" format="default"/> specifies an IP multimedia subsystem
          Custom Alerting tones
        </t>
        <texttable title="5.51 3GPP for
          customized alerting tones.
        </t>
        <table align="center">
          <name>3GPP TS 24.182 Attribute Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>g.3gpp.cat&nbsp;</c>
          <c>Usage 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&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> multimedia subsystem</td>
              <td align="left">M</td>
              <td align="left">NORMAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="3GPP numbered="true" toc="default">
        <name>3GPP TS 24.183"> 24.183</name>
        <t>
          <xref target="R3GPPTS24.183"/> target="IMS-CRS" format="default"/> specifies an IP multimedia
          subsystem Custom Ringing Signal
        </t>
        <texttable title="5.52 3GPP for customized ringing signal.
        </t>
        <table align="center">
          <name>3GPP TS 24.183 Attribute Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>g.3gpp.crs&nbsp;</c>
          <c>Usage 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&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> multimedia subsystem</td>
              <td align="left">M</td>
              <td align="left">NORMAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="3GPP numbered="true" toc="default">
        <name>3GPP TS 24.229"> 24.229</name>
        <t>
         <xref target="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 Attribute Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>secondary-realm&nbsp;</c>
          <c>secondary-realm  MUST 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">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
          transport flow&nbsp;</c><c>M</c>
          <c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>visited-realm&nbsp;</c>
          <c>visited-realm MUST flow.</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
          transport flow&nbsp;</c><c>M</c>
          <c>TRANSPORT&nbsp;</c><c>&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>omr-m-cksum&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c><c>&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>omr-s-cksum&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c><c>&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>omr-m-att&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c><c>&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>omr-s-att&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c><c>&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>omr-m-bw&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>omr-s-bw&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>omr-codecs&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="ITU T.38"> numbered="true" toc="default">
        <name>ITU T.38</name>
        <t>
         <xref target="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 Attribute Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>T38FaxVersion&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38MaxBitRate&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxFillBitRemoval&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxTranscodingMMR&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxTranscodingJBIG&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxRateManagement&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxMaxBuffer&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxMaxDatagram&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxUdpEC&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxMaxIFP&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxUdpECDepth&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38FaxUdpFECMaxSpan&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38ModemType&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>T38VendorInfo&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 per section 9 of <xref target="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 fax protocols protocol 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>
      <section title="ITU-T Q.1970"> numbered="true" toc="default">
        <name>ITU-T Q.1970</name>
        <t>
         <xref target="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 Attribute Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>ipbcp&nbsp;</c><c>ipbcp 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">ipbcp</td>
              <td align="left">ipbcp version identifies type the types of
          IP bearer control protocol (IPBCP) message used in BICC (ITU-T Q.1901)
          environment which that are limited to single media single-media payload. Refer to the pertinent
          ITU-T specifications while multiplexing&nbsp;</c>
          <c>S</c><c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
      </texttable> multiplexing.</td>
              <td align="left">S</td>
              <td align="left">SPECIAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="ITU-T H.248.15"> numbered="true" toc="default">
        <name>ITU-T H.248.15</name>
        <t>
          ITU-T H.248.15 <xref target="H.248.15"></xref> target="H.248.15" format="default"/> defines the Gateway Control Protocol
          SDP H.248 package attribute attribute.
        </t>
        <texttable title="5.56 ITU-T
        <table align="center">
          <name>ITU-T H.248.15 Attribute Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>h248item&nbsp;</c><c>It 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">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 the packaged package
          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 a gateway&nbsp;</c>
          <c>B</c><c>SPECIAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> gateway.</td>
              <td align="left">B</td>
              <td align="left">SPECIAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC4975: numbered="true" toc="default">
        <name>RFC 4975: The Message Session Relay Protocol"> Protocol</name>
        <t><xref target="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 or session creation session-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&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>accept-wrapped-types&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>max-size&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>path&nbsp;</c><c>Refer to notes below&nbsp;</c>
          <c>M&nbsp;</c><c>TBD&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 per section 9 of
         <xref target="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 MRSP MSRP 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>
      <section title="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 <xref
          target="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&nbsp;</c><c>Historic attributes&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>rtpred2&nbsp;</c><c>Historic attributes&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
    <section title="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>
      <section title="RFC4566: SDP"> numbered="true" toc="default">
        <name>RFC 4566: SDP</name>
        <t><xref target="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 bwtype Analysis">
         <ttcol align='left'>Name</ttcol>
         <ttcol align='left'>Notes</ttcol>
         <ttcol align='left'>Level</ttcol>
         <ttcol align='left'>Mux Category</ttcol>

         <c>bwtype:CT&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>S</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>bwtype:AS&nbsp;</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"> For the media level media-level usage,
         the aggregate of individual bandwidth values is considered&nbsp;</c>
          <c>B</c>
         <c>SUM&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
       </texttable> considered.</td>
              <td align="left">B</td>
              <td align="left">SUM</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC3556: numbered="true" toc="default">
        <name>RFC 3556: SDP Bandwidth Modifiers for RTCP Bandwidth"> Bandwidth</name>
        <t><xref target="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 in a an RTP session.</t>
       <texttable title="6.2 RFC3556
        <table align="center">
          <name>RFC 3556 bwtype Analysis">
         <ttcol align='left'>Name</ttcol>
         <ttcol align='left'>Notes</ttcol>
         <ttcol align='left'>Level</ttcol>
         <ttcol align='left'>Mux Category</ttcol>

         <c>bwtype:RS&nbsp;</c><c>Session level 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:RS</td>
              <td align="left">Session-level usage represents
         session aggregate aggregate, and media level media-level usage indicates SUM of the
         individual values while multiplexing&nbsp;</c>
         <c>B</c><c>SUM</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>bwtype:RR&nbsp;</c><c>Session level multiplexing.</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
         session aggregate aggregate, and media level media-level usage indicates SUM of the
         individual values while multiplexing&nbsp;</c>
         <c>B</c><c>SUM&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

       </texttable> multiplexing.</td>
              <td align="left">B</td>
              <td align="left">SUM</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC3890: numbered="true" toc="default">
        <name>RFC 3890: Bandwidth Modifier for SDP"> SDP</name>
        <t><xref target="RFC3890"/> target="RFC3890" format="default"/> defines SDP Transport Independent Application
        Specific Maximum (TIAS) bandwidth modifier that does not
        include transport overhead; instead instead, an additional packet rate packet-rate
        attribute is defined. The transport independent bit-rate transport-independent bitrate
        value together with the maximum packet rate can then be used
        to calculate the real bit-rate bitrate over the transport actually
        used.</t>
       <texttable title="6.3 RFC3890
        <table align="center">
          <name>RFC 3890 bwtype Analysis">
         <ttcol align='left'>Name</ttcol>
         <ttcol align='left'>Notes</ttcol>
         <ttcol align='left'>Level</ttcol>
         <ttcol align='left'>Mux Category</ttcol>

         <c>bwtype:TIAS&nbsp;</c><c>The 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:TIAS</td>
              <td align="left">The usage of TIAS is not
         defined under Offer/Answer usage.&nbsp;</c>
         <c>B</c><c>SPECIAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
         <c>maxprate&nbsp;</c><c>The offer/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 under multiplexing&nbsp;</c>
         <c>B</c><c>SPECIAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 the media
       level bit-rate media-level bitrate is
       multiplied with the known per-packet overhead
       for the selected transport and the maxprate value to determine
       the worst case bit-rate worst-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. Instead Instead, performing multiplication and adding the
       individual values is a more appropriate usage.</t>
      </section>
    </section>
    <section title="rtcp-fb anchor="SecrtcpfbAnalysis" numbered="true" toc="default">
      <name>rtcp-fb Attribute Analysis" anchor="SecrtcpfbAnalysis"> Analysis</name>
      <t>
      This section analyzes rtcp-fb SDP attributes.
      </t>
      <section title="RFC4585: RTP/AVPF"> numbered="true" toc="default">
        <name>RFC 4585: RTP/AVPF</name>
        <t><xref target="RFC4585"/> target="RFC4585" format="default"/> defines an extension to
        the Audio-visual Audio-Visual Profile (AVP) that enables receivers to
        provide, statistically, more immediate feedback to the
        senders and
        senders; it thus allows for short-term adaptation and implementation of
        efficient feedback-based repair mechanisms 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&nbsp;</c><c>The mechanisms.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>ack app&nbsp;</c>
         <c>Feedback configuration.</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 parameters MUST <bcp14>MUST</bcp14> be handled in the app specific app-specific
         way when multiplexed</c>
         <c>M</c><c>SPECIAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>nack&nbsp;</c><c>The multiplexed.</td>
              <td align="left">M</td>
              <td align="left">SPECIAL</td>
            </tr>
            <tr>
              <td align="left">nack</td>
              <td align="left">The attribute value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>nack pli&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>nack sli&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>nack rpsi&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration </c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>nack app&nbsp;</c>
         <c>Feedback configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
            <tr>
              <td align="left">nack app</td>
              <td align="left">Feedback parameters MUST <bcp14>MUST</bcp14> be handled in the app specific
         way when multiplexed</c>
         <c>M</c><c>SPECIAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>trr-int&nbsp;</c><c>The multiplexed.</td>
              <td align="left">M</td>
              <td align="left">SPECIAL</td>
            </tr>
            <tr>
              <td align="left">trr-int</td>
              <td align="left">The attribute value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
       </texttable> configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC5104: numbered="true" toc="default">
        <name>RFC 5104: Codec Control Messages in AVPF"> AVPF</name>
        <t><xref target="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&nbsp;</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 value MUST <bcp14>MUST</bcp14> be the same
        for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
       </texttable> configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6285: numbered="true" toc="default">
        <name>RFC 6285: Unicast-Based Rapid Acquisition of Multicast        RTP Sessions (RAMS)"> (RAMS)</name>
        <t><xref target="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 a faster than natural faster-than-natural bitrate to further
        accelerate the acquisition. The motivating use case for
        this capability is multicast applications that carry
        real-time compressed audio and video.</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&nbsp;</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration&nbsp;</c>
         <c>M&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

       </texttable> configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6679: numbered="true" toc="default">
        <name>RFC 6679: ECN for RTP over UDP/IP"> UDP/IP</name>
        <t><xref target="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&nbsp;</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 markup are is enabled at the
         RTP session level&nbsp;</c>
         <c>M&nbsp;</c><c>IDENTICAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
         <c>nack ecn&nbsp;</c><c>This level.</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
         session level&nbsp;</c>
         <c>M&nbsp;</c><c>IDENTICAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
       </texttable> level.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC6642: numbered="true" toc="default">
        <name>RFC 6642: Third-Party Loss Report"> Report</name>
        <t>In a large RTP session using the RTCP
        feedback mechanism defined in <xref target="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. <xref target="RFC6642"></xref>
        memo target="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&nbsp;</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration&nbsp;</c>
         <c>M&nbsp;</c>
         <c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>nack pslei&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration&nbsp;</c>
         <c>M&nbsp;</c>
         <c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

       </texttable> configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC5104: numbered="true" toc="default">
        <name>RFC 5104: Codec Control Messages in AVPF"> AVPF</name>
        <t><xref target="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&nbsp;</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>ccm tmmbr&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>ccm tstr&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>ccm vbcm&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration</c>
         <c>M</c><c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
       </texttable> configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section title="group anchor="SecgroupAnalysis" numbered="true" toc="default">
      <name>group Attribute Analysis"
     anchor="SecgroupAnalysis"> Analysis</name>
      <t>
       This section analyzes SDP &quot;group&quot; "group" attribute semantics
       <xref target="RFC5888"/>. target="RFC5888" format="default"/>.
      </t>
      <section title="RFC5888: numbered="true" toc="default">
        <name>RFC 5888: SDP Grouping Framework"> Framework</name>

        <t>
         <xref target="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&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>S&nbsp;</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>group:FID&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>S&nbsp;</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

       </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>
      <section title="RFC3524: numbered="true" toc="default">
        <name>RFC 3524: Mapping Media Streams to Resource Reservation Flows">        Flows</name>
        <t><xref target="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&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>S&nbsp;</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

       </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>

      <section title="RFC4091: numbered="true" toc="default">
        <name>RFC 4091: ANAT Semantics"> Semantics</name>
        <t>
         <xref target="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&nbsp;</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 is obsoleted &nbsp;</c>
         <c>S&nbsp;</c>
         <c>CAUTION&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
       </texttable> obsoleted.</td>
              <td align="left">S</td>
              <td align="left">CAUTION</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC5956: numbered="true" toc="default">
        <name>RFC 5956: FEC Grouping Semantics in SDP"> SDP</name>
        <t><xref target="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
        <xref target="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 same group, and group; 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&nbsp;</c><c>Not Impacted&nbsp;</c><c>S&nbsp;</c>
         <c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

       </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>
      <section title="RFC5583: numbered="true" toc="default">
        <name>RFC 5583: Signaling Media Decoding Dependency in SDP"> SDP</name>
        <t><xref target="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 of the use of using 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&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>S&nbsp;</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>depend lay&nbsp;</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration &nbsp;</c><c>M</c>
         <c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>depend mdc&nbsp;</c><c>The configuration.</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 value MUST <bcp14>MUST</bcp14> be the same
         for a given codec configuration&nbsp;</c><c>M</c>
         <c>IDENTICAL-PER-PT&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
       </texttable> configuration.</td>
              <td align="left">M</td>
              <td align="left">IDENTICAL-PER-PT</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section title="RFC7104: numbered="true" toc="default">
        <name>RFC 7104: Duplication Grouping Semantics in the  SDP"> SDP</name>
<!--[rfced] In the passage below, does "this document" refer to RFC 7104 or
the current document?

Original:
[RFC7104] defines the semantics for grouping redundant streams in
SDP. ... Grouping semantics at the Synchronization
Source (SSRC) level are also defined in this document for RTP streams
using SSRC multiplexing.
-->
        <t><xref target="RFC7104"/> target="RFC7104" format="default"/> defines the semantics for
   		grouping redundant streams in SDP, SDP. The semantics defined in this
   		document are to be used with the SDP Grouping Framework. Grouping
   		semantics at the SSRC)level synchronization 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&nbsp;</c><c>Not Impacted&nbsp;</c><c>S&nbsp;</c>
         <c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>
    	</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>
    <section title="ssrc-group anchor="sec-ssrc-group" numbered="true" toc="default">
      <name>ssrc-group Attribute Analysis"
     anchor="sec-ssrc-group"> Analysis</name>
      <t>
     This section analyzes "ssrc-group" semantics.
      </t>
      <section title="RFC5576: numbered="true" toc="default">
        <name>RFC 5576: Source-Specific SDP Attributes"> Attributes</name>
        <t><xref target="RFC5576"/> target="RFC5576" format="default"/> defines a mechanism to
        describe for
        describing RTP media sources, sources -- which are identified by their
        synchronization source (SSRC) identifiers, identifiers -- in SDP, to
        associate attributes with these sources, sources and to express
        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&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>SR</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>ssrc-group:FEC&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>SR</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

         <c>ssrc-group:FEC-FR&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>SR</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
      <section title="RFC7104: numbered="true" toc="default">
        <name>RFC 7104: Duplication Grouping Semantics in the SDP"> SDP</name>
        <t><xref target="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 the Synchronization Source synchronization 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&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>SR</c>
         <c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
    <section title="QoS anchor="SecqostokenAnalysis" numbered="true" toc="default">
      <name>QoS Mechanism Token Analysis"
      anchor="SecqostokenAnalysis"> Analysis</name>
      <t>
        This section analyzes QoS tokes specified with SDP.
      </t>
      <section title="RFC5432: numbered="true" toc="default">
        <name>RFC 5432: QoS Mechanism Selection in SDP"> SDP</name>
        <t><xref target="RFC5432"/> target="RFC5432" format="default"/> defines procedures to
        negotiate QOS QoS 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&nbsp;</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 attribute MUST <bcp14>MUST</bcp14> be the one
          that corresponds to the "m=" line chosen for
          setting up the underlying transport flow&nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>nsis&nbsp;</c><c>rsvp flow.</td>
              <td align="left">B</td>
              <td align="left">TRANSPORT</td>
            </tr>
            <tr>
              <td align="left">nsis</td>
              <td align="left">rsvp attribute MUST <bcp14>MUST</bcp14> be the one
          that corresponds to the "m=" line chosen for
          setting up the underlying transport&nbsp;</c>
          <c>B</c><c>TRANSPORT&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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 per for each
        flow being multiplexed doesn't impact multiplexing multiplexing, since
          QOS QoS
        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 <xref target="RFC7657"/> target="RFC7657"
        format="default"/> need to be taken into consideration.</t>
      </section>
    </section>
    <section title="k= anchor="SeckAnalysis" numbered="true" toc="default">
      <name>k= Attribute Analysis" anchor="SeckAnalysis"> Analysis</name>
      <section title="RFC4566: SDP"> numbered="true" toc="default">
        <name>RFC 4566: SDP</name>
        <t><xref target="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=&nbsp;</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 under multiplexing&nbsp;</c><c>S</c>
          <c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> multiplexing.</td>
              <td align="left">S</td>
              <td align="left">CAUTION</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section title="content anchor="SeccontentAnalysis" numbered="true" toc="default">
      <name>content Attribute Analysis" anchor="SeccontentAnalysis"> Analysis</name>
      <section title="RFC4796"> numbered="true" toc="default">
        <name>RFC 4796</name>
        <t><xref target="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 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&nbsp;</c><c>Not Impacted&nbsp;</c>
         <c>M&nbsp;</c><c>NORMAL&nbsp;</c>
         <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>content:speaker&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>content:main&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>content:sl&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>content:alt&nbsp;</c><c>Not Impacted&nbsp;</c>
          <c>M&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</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>
    <section anchor="sec-pay" title="Payload Formats"> numbered="true" toc="default">
      <name>Payload Formats</name>
      <section title="RFC5109: numbered="true" toc="default">
        <name>RFC 5109: RTP Payload Format for Generic FEC"> FEC</name>
        <t><xref target="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 the payload payload,
        depending on the packet loss situation.</t>

        <texttable title="13.1 RFC5109
        <table align="center">
          <name>RFC 5109 Payload Format Analysis">
          <ttcol align='left'>Name</ttcol>
          <ttcol align='left'>Notes</ttcol>
          <ttcol align='left'>Level</ttcol>
          <ttcol align='left'>Mux Category</ttcol>

          <c>audio/ulpfec&nbsp;</c>
          <c>Not 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">audio/ulpfec</td>
              <td align="left">Not recommended for multiplexing due to reuse of SSRCs&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>video/ulpfec&nbsp;</c>
          <c>Not SSRCs.</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 of SSRCs&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>text/ulpfec&nbsp;</c>
          <c>Not SSRCs.</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 of SSRCs&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

          <c>application/ulpfec&nbsp;</c>
          <c>Not SSRCs.</td>
              <td align="left">M</td>
              <td align="left">CAUTION</td>
            </tr>
            <tr>
              <td align="left">application/ulpfec</td>
              <td align="left">Not recommended for multiplexing due to reuse of SSRCs&nbsp;</c>
          <c>M</c><c>CAUTION&nbsp;</c>
          <c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c><c>&nbsp;</c>

        </texttable> SSRCs.</td>
              <td align="left">M</td>
              <td align="left">CAUTION</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section title="Multiplexing anchor="sec-encap" numbered="true" toc="default">
      <name>Multiplexing Considerations for Encapsulating Attributes"
        anchor="sec-encap"> Attributes</name>
      <t>This sections section deals with recommendations for defining the
           multiplexing characteristics of the SDP attributes that
           encapsulate other SDP attributes/parameters. Such
           attributes as As of today, such
           attributes, for example, are defined in
           <xref target="RFC3407"/>, target="RFC3407" format="default"/>, <xref target="RFC5939"/> target="RFC5939" format="default"/> and
           <xref target="RFC6871"/> target="RFC6871" format="default"/> as part of a generic
           framework for indicating and negotiating transport, media, transport-, media-,
           and media format related media-format-related capabilities in the SDP.</t>
      <t>The behavior of such attributes under multiplexing is is, in
           turn
           turn, defined by the multiplexing behavior of the attributes
           they encapsulate encapsulate, which are made known once the Offer/Answer offer/answer
           negotiation process is completed.</t>
      <section title="RFC3407: numbered="true" toc="default">
        <name>RFC 3407: cpar Attribute Analysis">
             <t> Analysis</name>
        <t>The <xref target="RFC3407"/> target="RFC3407" format="default"/> capability parameter
             attribute (a=cpar) "a=cpar" encapsulates b= a "b=" (bandwidth) or an
             a=
             "a=" attribute. For bandwidth attribute encapsulation,
             the category SUM is inherited. For the case of a= "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> In a=rtcp-mux</sourcecode>

        <t>In this example, the above example,the category IDENTICAL is
             inherited for the cpar encapsulated rtcp-mux cpar-encapsulated "rtcp-mux"
             attribute. </t>
          <t>&nbsp;</t>
        <t></t>
      </section>
      <section title="RFC5939 Analysis"> numbered="true" toc="default">
        <name>RFC 5939 Analysis</name>
        <t><xref target="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, <xref target="RFC5939"/> target="RFC5939" format="default"/> defines the following
                  <list style="symbols">
                    <t>A following:
        </t>
        <ul spacing="normal">
          <li>A set of capabilities for the session and its
                    associated media stream media-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") as
                    capabilities.</t>
                    <t>A
                    capabilities.</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 that MAY <bcp14>MAY</bcp14>
                    be used, subject to SDP capability negotiation capability-negotiation
                    procedures. In particular particular, the answerer MAY <bcp14>MAY</bcp14> choose
                    one of the potential configurations for use as part
                    of the current Offer/Answer exchange.</t>
                    <t>An offer/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 further negotiation.</t>
                    <t>A negotiation.</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 <xref target="RFC5939"/> target="RFC5939" format="default"/>, the
                    negotiation process is done independently for
                    each media description.</t>
                  </list>
              </t> description.</li>
        </ul>
        <section title="Recommendation: anchor="sec-cap-neg-proc" numbered="true" toc="default">
          <name>Recommendation: Procedures for Potential Configuration Pairing"
                  anchor="sec-cap-neg-proc"> Pairing</name>
          <t>This section provides recommendations for entities
                generating and processing SDP under the generic
                capability negotiation
                capability-negotiation framework as defined in
                <xref target="RFC5939"/> target="RFC5939" format="default"/> under the context of media
                stream media-stream
		multiplexing.</t>
          <t>These recommendations are provided for the purposes
                of enabling the Offerer offerer 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 simplify Answerer's the answerer's procedure to choose for 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, there MAY <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 <xref target="RFC5939"/> target="RFC5939" format="default"/> state
                that each potential configuration in the SDP has a unique
                configuration number, however number; however, the scope of uniqueness is
                limited to each media description. To make it simple for the
                answerer to chose valid combinations of potential configurations
                across media descriptions in a given bundle group, we provide a
                simple rule for constructing potential configurations
                  <list style="symbols">
                    <t> Let configurations:
          </t>
          <ul spacing="normal">
            <li>Let m-bundle be the set of media descriptions that form
                    a given bundle .</t>
                    <t> Let bundle.</li>
            <li>Let m-bundle-pcfg be the set of media descriptions in
                    m-bundle that include one or more potential configurations.</t>
                    <t> Each configurations.</li>
            <li>Each media description in m-bundle-pcfg MUST <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 offerer MUST <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 media descriptions.</t>
                    <t> Since descriptions.</li>
            <li>Since it is nearly impossible to define a generic
                    mechanism for various capability extensions, this
                    document does't doesn't provide procedures for dealing
                    with the capability extension capability-extension attributes. However,
                    <xref target="med-cap-analysis"/> provide target="med-cap-analysis" format="default"/> provides
                    analysis of media capability extension media-capability-extension attributes
                    as defined in <xref target="RFC6871"/>. </t>
                    </list>
                  </t>
                  <t> The target="RFC6871" format="default"/>. </li>
          </ul>
          <t>The above allows the answerer to easily find multiplexing compatible multiplexing-compatible
                  combinations of potential configurations: configurations. The answerer simply choses chooses 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>
          <section title="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>In the example above, this example, the potential configurations that offer
            transport protocol
            transport-protocol capability of RTP/SAVPF has have the same configuration
            number "1" in both the audio and video media descriptions.</t>
          </section>
          <section title="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>In the 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>
      <section title = "RFC6871 Analysis" anchor="med-cap-analysis"> anchor="med-cap-analysis" numbered="true" toc="default">
        <name>RFC 6871 Analysis</name>
        <t><xref target="RFC6871"/> target="RFC6871" format="default"/> extends the capability negotiation
        framework described in <xref target="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>
        <section title="Recommendation: numbered="true" toc="default">
          <name>Recommendation: Dealing with Payload Type Numbers"> Numbers</name>
          <t><xref target="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-based media format media-format capabilities ("a=rmcap") defined
          in <xref target="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
          identical Payload Type payload type values across multiplexed "m=" lines as lines,
          described in <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref>, target="RFC8843" format="default"/>,
          which must be followed here here, as well. As described in
          <xref target="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
          configurations here here, as well.</t>
          <section title="Example: numbered="true" toc="default">
            <name>Example: Attribute Capability Under under Shared Payload Type"> 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>In the example above, this example, the potential configuration
            number "1" is repeated when referring to media and media
            format media-format
	    capability used for the Payload Type 96. This
            implies that both the media capability capabilities 2 and 4 4, along
            with their media format capabilities MUST media-format capabilities, <bcp14>MUST</bcp14> refer to the
            same codec configuration, as per the definition of
            IDENTICAL-PER-PT.</t>
          </section>
        </section>
        <section title="Recommendation: numbered="true" toc="default">
          <name>Recommendation: Dealing with Latent Configurations"> Configurations</name>
          <t><xref target="RFC6871"/> target="RFC6871" format="default"/> adds the notion of a latent configurations,
          which
	  configuration that provides configuration information that may be
	  used to guide a
          subsequent offer/exchange, e.g. offer/exchange -- e.g., by adding another media stream or use using
          alternative codec combinations not currently offered. Latent configurations
          have configuration numbers which that cannot overlap with the potential configuration
          numbers <xref target="RFC6871"/>. target="RFC6871" format="default"/>. Supported combinations of potential and
          latent configurations are indicated by use of the "a=sescap" attribute,
          however attribute;
          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 configuration attribute, however attribute; however, the limitations
          above will apply. To determine valid combinations, actual
          negotiation will have to be attempted subsequently instead.</t>
        </section>
      </section>
    </section>
    <section title="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 new subregistry to be
      subregistry, which has been
       added by the IANA IANA, for identifying the initial registrations for
       various multiplexing categories applicable, as proposed described in this document.</t>
      <t>IANA is also requested to add has added a new column named "Mux Category"
       to several of the subregistries in the "Session Description Protocol
       (SDP) Parameters" registry. The tables in <xref target="sec-mux-cat-values-iana"/> target="sec-mux-cat-values-iana" format="default"/>
       identify name the names of an entry entries in the existing subregistry and specify the
       value to be put in the new "Mux Category" column of the associated IANA
       registry.</t>
       registry for each.</t>
      <section title="New 'Multiplexing Categories' subregistry " anchor="sec-mux-cat-iana"> anchor="sec-mux-cat-iana" numbered="true" toc="default">
        <name>New "Multiplexing Categories" Subregistry</name>
        <t>A new sub-registry needs to be defined subregistry has been created. It is called  the "Multiplexing Categories", with
	  Categories" and has the following registrations
          created 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>

          <texttable
          initially:</t>
        <table align="left">
            <ttcol align='left'>Multiplexing Categories</ttcol>
            <ttcol align='left'>Reference</ttcol>
              <c>NORMAL&nbsp;</c><c> RFCXXXX</c>
              <c>CAUTION&nbsp;</c><c> RFCXXXX</c>
              <c>IDENTICAL&nbsp;</c><c> RFCXXXX</c>
              <c>TRANSPORT&nbsp;</c><c> RFCXXXX</c>
              <c>SUM&nbsp;</c><c> RFCXXXX</c>
              <c>INHERIT&nbsp;</c><c> RFCXXXX</c>
              <c>IDENTICAL-PER-PT&nbsp;</c><c> RFCXXXX</c>
              <c>SPECIAL&nbsp;</c><c> RFCXXXX</c>
              <c>TBD&nbsp;</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 <xref target="RFC5226"/>, target="RFC8126" format="default"/>, which requires IESG review and
         approval and standards-track Standards Track IETF RFC publication.</t>
        <t> Each
        <t>Each registration needs to indicate the multiplexing category value
         to be added to the "Multiplexing Categories" subregistry subregistry, as defined
         in this section.</t>
        <t> Such
        <t>Such a registration MUST <bcp14>MUST</bcp14> also indicate the applicability of the
         newly defined multiplexing category value to various subregistries
         defined at in the "Session Description Protocol (SDP) Parameters" registry.</t>
      </section>
      <section title="'Mux Category' column for subregistries" anchor="sec-mux-cat-values-iana" toc="default">
        <t> Each sub-section toc="default" numbered="true">
        <name>"Mux Category" Column for Subregistries</name>
        <t>Each subsection identifies a subregistry in of 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 existing subregistries, under subregistries 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, are is beyond the
        scope of this document. The registration policy  for the affected table is
        defined in <xref target="I-D.ietf-mmusic-rfc4566bis"/>.</t> target="SDP" format="default"/>.</t>
        <section title="Table: numbered="true" toc="default">
          <name>Table: SDP bwtype"> bwtype</name>
          <t>The following values are to be have been added to the 'SDP bwtype' "bwtype" subregistry
         in
         of the "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>AS&nbsp;</c><c>SUM&nbsp;</c>
          <c>RS&nbsp;</c><c>SUM&nbsp;</c>
          <c>RR&nbsp;</c><c>SUM&nbsp;</c>
          <c>TIAS&nbsp;</c><c>SPECIAL&nbsp;</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: att-field</name>
          <t>The following values are to be have been added to the "att-field (session level)" "att-field"
        subregistry in of the "Session Description Protocol (SDP) Parameters" registry.
        The references should be have been updated to point at to 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&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>keywds&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>type&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>type:broadcast&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>type:H332&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>type:meeting&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>type:moderated&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>type:test&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>charset&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>charset:iso8895-1&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>tool&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>ipbcp&nbsp;</c><c>SPECIAL&nbsp;</c>
          <c>group&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>ice-lite&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>ice-options&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>bcastversion&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>3GPP-Integrity-Key&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>3GPP-SDP-Auth&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>alt-group&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>PSCid&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>bc_service&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>bc_program&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>bc_service_package&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>sescap&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>rtsp-ice-d-m&nbsp;</c><c>TBD&nbsp;</c>
        </texttable>
      </section>
      <section title="Table: att-field (both session and media level)">
        <t>

          <t>NOTE: The following values are to be added attributes from <xref target="FLUTE" 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 expired status of the draft. For the purposes of this
          specification, the multiplexing category of "TBD" is assigned. </t>

	  <table align="left">
            <thead>
              <tr>
                <th align="left">SDP Name</th>
                <th align="left">Mux Category</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">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)" 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 of the
        draft. For purposes of this specification, the multiplexing category
        of 'TBD' is assigned. </t>

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

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

        <texttable align="left">
          <ttcol align='left'>SDP Name</ttcol>
          <ttcol align='left'>Mux Category</ttcol>
          <c>cname&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>previous-ssrc&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>fmtp&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>ts-refclk&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>mediaclk&nbsp;</c><c>NORMAL&nbsp;</c>
        </texttable> level)-->

              <tr>
                <td align="left">cname</td>
                <td align="left">NORMAL</td>
              </tr>
              <tr>
                <td align="left">previous-ssrc</td>
                <td align="left">NORMAL</td>
              </tr>
              <tr>
                <td align="left">fmtp</td>
                <td align="left">IDENTICAL-PER-PT</td>
              </tr>
              <tr>
                <td align="left">ts-refclk</td>
                <td align="left">NORMAL</td>
              </tr>
              <tr>
                <td align="left">mediaclk</td>
                <td align="left">NORMAL</td>
              </tr>
            </tbody>
          </table>
        </section>
        <section title="Table: numbered="true" toc="default">
          <name>Table: content SDP Parameters"> Parameters</name>
          <t>The following values are to be have been added to the
         "content SDP Parameters" subregistry in of the
         "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>speaker&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>sl&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>main&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>alt&nbsp;</c><c>NORMAL&nbsp;</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>
            </tbody>
          </table>
        </section>
        <section title="Table: numbered="true" toc="default">
          <name>Table: Semantics for the 'group' "group" SDP Attribute"> Attribute</name>
          <t>The following values are to be have been added to the
         "Semantics for the "group" 'group' SDP Attribute" subregistry in of the
         "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>FID&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>SRF&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>ANAT&nbsp;</c><c>CAUTION&nbsp;</c>
          <c>FEC&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>FEC-FR&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>CS&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>DDP&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>DUP&nbsp;</c><c>NORMAL&nbsp;</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>
        <section title="Table: 'rtcp-fb' numbered="true" toc="default">
          <name>Table: "rtcp-fb" Attribute Values"> Values</name>
          <t>The following values are to be have been added to the
         " 'rtcp-fb'
         "'rtcp-fb' Attribute Values" subregistry in of the
         "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>app&nbsp;</c><c>SPECIAL&nbsp;</c>
          <c>ccm&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>nack&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>trr-int&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</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>
        <section title="Table: 'ack' numbered="true" toc="default">
          <name>Table: "ack" and 'nack' "nack" Attribute Values"> Values</name>
          <t>The following values are to be have been added to the
         " 'ack'
         "'ack' and 'nack' Attribute Values" subregistry in of the
         "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>pli&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>rpsi&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>app&nbsp;</c><c>SPECIAL&nbsp;</c>
          <c>rai&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>tllei&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>pslei&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>ecn&nbsp;</c><c>IDENTICAL&nbsp;</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>
        <section title="Table: 'depend' numbered="true" toc="default">
          <name>Table: "depend" SDP Attribute Values">

        <t> The Values</name>
          <t>The following values are to be have been added to the
         " 'depend'
         "'depend' SDP Attribute Values" subregistry in of the
         "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>mdc&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</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>
        <section title="Table: 'cs-correlation' numbered="true" toc="default">
          <name>Table: "cs-correlation" Attribute Values">

        <t> The Values</name>
          <t>The following values are to be have been added to the
         " "cs-correlation"
         "'cs-correlation' Attribute Values" subregistry in of the
         "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>TBD&nbsp;</c>
          <c>uuie&nbsp;</c><c>TBD&nbsp;</c>
          <c>dtmf&nbsp;</c><c>TBD&nbsp;</c>
          <c>external&nbsp;</c><c>TBD&nbsp;</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>
        <section title="Table: numbered="true" toc="default">
          <name>Table: Semantics for the 'ssrc-group' "ssrc-group" SDP Attribute">

        <t> The Attribute</name>
          <t>The following values are to be have been added to the
         Semantics for the "Semantics for the "ssrc-group"
	'ssrc-group' SDP Attribute"
         subregistry in of the "Session Description Protocol (SDP) Parameters"
         registry. The references should be updated have been updated to point at to 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&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>FEC&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>FEC-FR&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>DUP&nbsp;</c><c>NORMAL&nbsp;</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>
        <section title="Table: numbered="true" toc="default">
          <name>Table: SDP/RTSP key management protocol identifiers"> Key Management Protocol Identifiers</name>
          <t>The following values are to be have been added to the
        "SDP/RTSP key management protocol identifiers" subregistry
        in
        of the  "Session Description Protocol (SDP) Parameters" registry.
        The references should be have been updated to point at to 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&nbsp;</c><c>IDENTICAL&nbsp;</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>
        <section title="Table: numbered="true" toc="default">
          <name>Table: Codec Control Messages">
        <t> The Messages</name>
          <t>The following values are to be have been added to the
         "Codec Control Messages" subregistry in of the
         "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>tmmbr&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>tstr&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</c>
          <c>vbcm&nbsp;</c><c>IDENTICAL-PER-PT&nbsp;</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>
        <section title="Table: numbered="true" toc="default">
          <name>Table: QoS Mechanism Tokens">
        <t> The Tokens</name>
          <t>The following values are to be have been added to the
         "QoS Mechanism Tokens" subregistry in of the
         "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>TRANSPORT&nbsp;</c>
          <c>nsis&nbsp;</c><c>TRANSPORT&nbsp;</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>
        <section title="Table: numbered="true" toc="default">
          <name>Table: SDP Capability Negotiation Option Tags">
        <t> The Tags</name>
          <t>The following values are to be have been added to the
         "SDP Capability Negotiation Option Tags" subregistry
         in
         of the "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>med-v0&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>bcap-v0&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>ccap-v0&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>icap-v0&nbsp;</c><c>NORMAL&nbsp;</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>
        <section title="Table: numbered="true" toc="default">
          <name>Table: Timestamp Reference Clock Source Parameters">
        <t> The Parameters</name>
          <t>The following values are to be have been added to the
         "Timestamp Reference Clock Source Parameters" subregistry
         in
         of the "Session Description Protocol (SDP) Parameters" registry.
         The references should be have been updated to point at to 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&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>ptp&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>gps&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>gal&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>glonass&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>local&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>private&nbsp;</c><c>NORMAL&nbsp;</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>
        <section title="Table: numbered="true" toc="default">
          <name>Table: Media Clock Source Parameters">
        <t> The Parameters</name>
          <t>The following values are to be have been added to the
         "Media Clock Source Parameters" subegistry
         in subregistry
         of the "Session Description Protocol (SDP) Parameters"
         registry. The references should be have been updated to point at to
         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&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>direct&nbsp;</c><c>NORMAL&nbsp;</c>
          <c>IEEE1722&nbsp;</c><c>NORMAL&nbsp;</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>
    <section title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>
        The primary security considerations for RTP RTP, including the way it is used here
        is here,
        are described in <xref target="RFC3550"/> target="RFC3550" format="default"/> and <xref target="RFC3711"/>. target="RFC3711" format="default"/>.
      </t>
      <t>
        When multiplexing SDP attributes with the category "CAUTION", the
        implementations should be aware of possible issues as described 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>
    <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 the IANA 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>Procedures Session 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="April" year="2020"/>
      </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"/>
        <!-- draft-ietf-mmusic-rfc4566bis-35 exists  -->
        <reference anchor="SDP">
          <front>
            <title>SDP: Session Description Protocol</title>
            <seriesInfo name="Work in Progress," value="draft-ietf-mmusic-rfc4566bis-35"/>
            <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="May" day="3" year="2019"/>
          </front>
        </reference>
        <reference anchor="IANA" target="https://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml">
          <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>
        <reference anchor='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>
        <reference anchor='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>

        <reference anchor='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>
        <reference anchor='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 Stage Telecommunications and Internet converged Services and
	  Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification.</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>
        <reference anchor='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>
        <reference anchor='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 -->
        <reference anchor="FLUTE">
          <front>
            <title>SDP Descriptors for FLUTE</title>
            <seriesInfo name="Work in Progress," value="draft-ietf-rmt-flute-sdp-03"/>
            <author initials="R" surname="Walsh" fullname="Rod Walsh">
              <organization/>
            </author>
            <author initials="J" surname="Peltotalo" fullname="Jani Peltotalo">
              <organization/>
            </author>
            <author initials="S" surname="Peltotalo" fullname="Sami Peltotalo">
              <organization/>
            </author>
            <author initials="I" surname="Curcio" fullname="Igor Curcio">
              <organization/>
            </author>
            <author initials="H" surname="Mehta" fullname="Harsh Mehta">
              <organization/>
            </author>
            <date month="September" day="12" year="2012"/>
          </front>
        </reference>

<!-- draft-ietf-bfcpbis-rfc4583bis RFC-to-be 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='May' year='2020' />
</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 Keranen"/>, 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">
	  <li><t>
	    <contact fullname="Flemming Andreasen"/> (5.24, 5.32, 5.33, 14),<br/>
	    <contact fullname="Rohan Mahy"/> (5.56),<br/>
	    <contact fullname="Eric Burger"/> (5.26),<br/>
	    <contact fullname="Christian Huitema"/> (5.14),<br/>
	    <contact fullname="Christer Holmberg"/> (5.21, 5.26, 5.50, 5.51),<br/>
	    <contact fullname="Richard Ejzak"/> (5.44, 5.52, 5.53),<br/>
	    <contact fullname="Colin Perkins"/> (5.7, 5.8, 5.9, 5.57),<br/>
	    <contact fullname="Magnus Westerlund"/> (5.2, 5.3, 5.9, 5.27, 5.47, 6.1 - 6.3, 8.3, 7),<br/>
	    <contact fullname="Roni Evens"/> (5.12, 5.27, 8.4),<br/>
	    <contact fullname="Subha Dhesikan"/> (5.6, 10),<br/>
	    <contact fullname="Dan Wing"/> (5.7, 5.12, 5.35, 5.39, 5.45),<br/>
	    <contact fullname="Cullen Jennings"/> (5.40),<br/>
	    <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),<br/>
	    <contact fullname="Bo Burman"/> (7.2, 7.6),<br/>
	    <contact fullname="Charles Eckel"/> (5.15, 5.27, 5.28, 9.1, 8.5),<br/>
	    <contact fullname="Paul Kyzivat"/> (5.24),<br/>
	    <contact fullname="Ian Johansson"/> (5.15),<br/>
	    <contact fullname="Saravanan Shanmugham"/> (5.11),<br/>
	    <contact fullname="Paul E Jones"/> (5.30),<br/>
	    <contact fullname="Rajesh Kumar"/> (5.48),<br/>
	    <contact fullname="Jonathan Lennox"/> (5.36, 5, 15, 9.1, 11.1),<br/>
	    <contact fullname="Mo Zanaty"/> (5.4, 5.5, 5.23, 8.1, 8.3, 8.5, 12.1),<br/>
	    <contact fullname="Christian Huitema"/> (5.14),<br/>
	    <contact fullname="Qin Wu"/> (5.47, PM-Dir review),<br/>
	    <contact fullname="Hans Stokking"/> (5.43, 5.16),<br/>
	    <contact fullname="Christian Groves"/> (5.48, 5.54), and<br/>
	    <contact fullname="Thomas Stach"/>.<br/>
	  </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>