One document matched: draft-nandakumar-mmusic-sdp-mux-attributes-00.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc strict="yes" ?>
<?rfc compact="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc rfcedstyle="no" ?>
<?rfc tocdepth="4"?>
<rfc category="std" docName="draft-nandakumar-mmusic-sdp-mux-attributes-00"
ipr="trust200902">
<front>
<title abbrev="SDP Attribute Multiplexing">A Framework for SDP Attributes
when Multiplexing</title>
<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>
</postal>
<email>snandaku@cisco.com</email>
</address>
</author>
<author fullname="Cullen Jennings" initials="C." surname="Jennings">
<organization>Cisco</organization>
<address>
<postal>
<street>400 3rd Avenue SW, Suite 350</street>
<city>Calgary</city>
<region>AB</region>
<code>T2P 4H2</code>
<country>Canada</country>
</postal>
<email>fluffy@iii.ca</email>
</address>
</author>
<date day="18" month="February" year="2013" />
<area>RAI</area>
<abstract>
<t>
Communication sessions in RTCWeb are described and negotiated using
Session Description Protocol(SDP)[RFC4566] mechanisms. SDP uses
attributes to describes specific aspects of such a session. These
attributes have different impacts when using varions of multiplexing RTP on
a single transport layer flow.
The scope of this specification is to provide a
framework for analyzing the multiplex characteristics for SDP attributes
and provide multiplexing characteristics of existing attributes.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
SDP<xref target="RFC4566"/> defines several
attributes for describing specific aspects of a multimedia
session. Given the number of SDP attributes registered with IANA
<xref target="IANA"></xref>and the defining new attributes in the
future, there is need for future-proof framework to analyze these
attributes for their applicability in transport multiplexing use-cases.
Few proposed schemes for the same are defined in
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref> and
<xref target="I-D.ietf-avt-multiplexing-rtp"></xref>
</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, following which
several sections applies the framework to the SDP attributes registered
with IANA <xref target="IANA"></xref>
</t>
</section>
<section title="Terminology">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in <xref target="RFC2119"></xref>.</t>
</section>
<section title="Motivation">
<t>
The time and complications of setting up ICE <xref target="RFC5245"></xref>
and DTLS-SRTP <xref target="RFC5763"></xref> transports for use by RTP, and conservation of ports,
forms an requirement to try and reduce the number of transport level flows needed.
This has resulted in the definition of ways 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 these SDP
attributes as they are defined today.
</t>
<t>
The specific problem is that there are attribute combinations which
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-mline to have an independently
specified 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 attributes becomes
muddled.
</t>
<t>
As of today there are close to 180 SDP attributes registered
with the IANA <xref target="IANA"></xref> and more will be added in
the future. There is no clearly defined procedure to establish the
validity/applicability of these attribute when used with multiplexing.
</t>
</section>
<section title="SDP Attribute Analysis Framework">
<t>
An SDP session description consists of a session-level section followed by
zero or more media-level sections that could be broken down into following
high-level categories
</t>
<t>
<list style="symbols">
<t> Attributes related to media content such as media type,
encoding schemes, payload types to name a few.</t>
<t> Attributes specifying media transport characteristics like RTP/RTCP
port, network addresses, QOS and so on.</t>
<t> Attributes Metadata descriptions such as session timing and origin
information.</t>
<t> Attributes establishing relationships between media streams.</t>
</list>
</t>
<t>
The proposed framework classifies each attribute into one of
the following categories:
<list style="hanging">
<t hangText="NORMAL"> Attributes that can be independently
specified when multiplexing and retain their original semantics .</t>
<t></t>
<t hangText="BAD"> Attributes where multiplexing SHOULD NOT be
used if these attributes are in use in the SDP. </t>
<t></t>
<t hangText="IDENTICAL"> Attributes that MUST be identical
across all the media lines being multiplexed.</t>
<t></t>
<t hangText="SUM"> Attributes can be set as they are normally used but
software using them in a multiplex case, MUST apply the sum of all the
attributes being multiplexed instead of trying to use each one. This is
typically used for bandwidth or other rate limiting attributes to the
underlining transport. </t>
<t></t>
<t hangText="TRANSPORT"> Attributes that can be set normally for
multiple items in a multiplexed group but the software MUST pick just
one of the attribute of the given type for use. The one chosen is the
attribute associated with the "m=" lines that represents the information
being used for the transport of the RTP. Readers are advised to refer
Section <xref target="sec-transport">TRANSPORT_EXAMPLE</xref> for an illustration of
this category.
</t>
<t></t>
<t hangText="SPECIAL"> Attributes where the text in the draft must be
consulted to see how they are handled when multiplexing. </t>
</list>
</t>
<t>
The idea behind these categories is to provide recommendations for using
the attributes when multiplexing is being used.
</t>
<t>
<xref target="SecCurrAnalysis"/> analyzes attributes listed in <xref target="IANA">IANA</xref>
grouped under the IETF document that defines them. The "Current" column indicates
whether the attribute is currently specified as:
</t>
<t>
<list style="symbols">
<t>S -- Session level</t>
<t>M -- Media level</t>
<t>B -- Both</t>
<t>SR -- Source-level (for a single SSRC)</t>
</list>
</t>
</section>
<section title="Analysis of Existing Attributes" anchor="SecCurrAnalysis" >
<section title="RFC4566">
<t>
<xref target="RFC4566">RFC4566</xref> defines the Session Description Protocol (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="RFC4566 Attribute Analysis">
<ttcol align='left'>Attr Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>sendrecv </c><c>Not impacted </c><c>B </c>
<c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>sendonly </c><c>Not impacted </c><c>B </c>
<c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>recvonly </c><c>Not impacted </c><c>B </c>
<c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>inactive </c><c>Not impacted </c><c>B </c>
<c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>cat </c><c>Not impacted </c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ptime </c><c>Not Impacted
</c><c>M </c><c>NORMAL</c>
<c> </c><c> </c><c> </c><c> </c>
<c>maxptime </c><c>Not Impacted
</c><c>M </c><c>NORMAL</c>
<c> </c><c> </c><c> </c><c> </c>
<c>orient </c><c>Not Impacted
</c><c>M </c><c>NORMAL</c>
<c> </c><c> </c><c> </c><c> </c>
<c>framerate </c><c>Not Impacted
</c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>quality </c><c>Not Impacted
</c><c>M </c><c>NORMAL</c>
<c> </c><c> </c><c> </c><c> </c>
<c>rtpmap </c><c>Not Impacted
</c><c>M </c><c>NORMAL</c>
<c> </c><c> </c><c> </c><c> </c>
<c>fmtp </c><c>Not Impacted
</c><c>M </c><c>NORMAL</c>
<c> </c><c> </c><c> </c><c> </c>
<c>keywds </c><c>Not impacted </c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>type </c><c>Not Impacted
</c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>tool </c><c>Not Impacted
</c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>charset </c><c>Not Impacted
</c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>sdplang </c><c>Not Impacted
</c><c>B </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>lang </c><c>Not Impacted
</c><c>B </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4585">
<t>
<xref target="RFC4585">RFC4585</xref> 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="RFC4585 Attribute Analysis">
<ttcol align='left'>Attr Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rtcp-fb </c><c>Since RTCP feedback are reported per RTP
Session, this attribute should be repeated across m=
lines</c><c>M</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5761">
<t>
<xref target="RFC5761">RFC5761</xref> 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 Session Description Protocol (SDP) can be used
to signal multiplexed sessions.
</t>
<texttable title="RFC5761 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rtcp-mux </c><c>RTCP muxing should be repeated across all the
m=lines </c><c>M </c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4574">
<t>
<xref target="RFC4574">RFC4574</xref> defines a new Session Description Protocol (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="RFC4574 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>label </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5432">
<t>
<xref target="RFC5432">RFC5432</xref> defines prordures to negotiate QOS mechanisms using the
Session Description Protocol (SDP) offer/answer model.
</t>
<texttable title="RFC5432 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>qos-mech-send </c><c>QOS mechanism should be same across all the
m=lines multiplexed </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>qos-mech-recv </c><c>AQOS mechanism should be same across all the
m=lines multiplexed </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4568">
<t>
<xref target="RFC4568">RFC4568</xref> defines a Session Description Protocol (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="RFC4568 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>crypto </c><c></c><c>M </c><c>TRANSPORT </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
<t>Open Isuse: should this be NORMAL</t>
</section>
<section title="RFC5762">
<t>
The Real-time Transport Protocol (RTP) is a widely used transport for
real-time multimedia on IP networks. The Datagram Congestion Control
Protocol (DCCP) is a transport protocol that provides desirable
services for real-time applications. <xref target="RFC5762">RFC5762</xref>
specifies a mapping of RTP onto DCCP, along with associated signalling,
such that real-time applications can make use of the services provided by DCCP
</t>
<texttable title="RFC5762 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>dccp-service-code </c><c>Not recommended due to DCCP service code
mismatch between different media types </c>
<c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6773">
<t>
<xref target="RFC6773">RFC6773</xref> document specifies an alternative
encapsulation of the Datagram Congestion Control Protocol (DCCP),
referred to as DCCP-UDP. This encapsulation allows DCCP to be carried
through the current generation of Network Address Translation (NAT) middleboxes
without modification of those middleboxes
</t>
<texttable title="RFC6773 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>dccp-port </c><c>Not recommended due to DCCP service code
mismatch between different media types </c>
<c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5506">
<t>
<xref target="RFC5506">RFC5506</xref> discusses benefits and issues that
arise when allowing Real-time Transport Protocol (RTCP) packets to be
transmitted with reduced size.
</t>
<texttable title="RFC5506 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rtcp-rsize </c><c>RTCP reduced size MUST be repeated across all the
m=lines </c><c>M </c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6787">
<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 -- it relies on
other protocols, such as the Session Initiation Protocol (SIP), to
coordinate MRCPv2 clients and servers and manage sessions between
them, and the Session Description Protocol (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 resources on the
speech resource server. <xref target="RFC6787">RFC6787</xref> defines
attributes for this purpose.
</t>
<texttable title="RFC6787 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>resource </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>channel </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c> </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5245">
<t>
<xref target="RFC5245">RFC5245</xref> describes a protocol for
Network Address Translator(NAT) traversal for UDP-based multimedia
sessions established with the offer/answer model. This protocol
is called Interactive Connectivity Establishment (ICE).
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
Session Initiation Protocol (SIP).
</t>
<texttable title="RFC5245 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>ice-lite </c><c>Not Impacted </c>
<c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ice-options </c><c>Not Impacted </c>
<c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ice-options </c><c>Not Impacted </c>
<c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ice-pwd </c><c>Per media-level attribute MUST be used per
underlying transport flow </c>
<c>B</c><c>TRANSPORT </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ice-ufrag </c><c>Per media-level attribute MUST be used per
underlying transport flow </c>
<c>B</c><c>TRANSPORT </c>
<c> </c><c> </c><c> </c><c> </c>
<c>candidate </c><c>Per media-level attribute MUST be used per
underlying transport flow </c><c></c><c>TRANSPORT </c>
<c> </c><c> </c><c> </c><c> </c>
<c>remote-candidates </c><c>Per media-level attribute MUST be used per
underlying transport flow </c><c>M</c><c>TRANSPORT </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5285">
<t>
<xref target="RFC5285">RFC5285</xref> provides a general mechanism to use the header
extension feature of RTP (the Real-Time Transport Protocol). 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. The actual extensions in use in a
session are signaled in the setup information for that session.
</t>
<texttable title="RFC5285 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>extmap </c><c>Specific RTP extension document MUST be referred </c>
<c>B</c><c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC3605">
<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"/> specifies an early mechanism to
indicate the RTCP port.
</t>
<texttable title="RFC3605 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rtcp </c><c>Case1:Same RTCP port is repeated across the m=lines.
Case2:Different RTCP ports renders multiplexing impossible </c><c>M</c>
<c>TRANSPORT </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5576">
<t>
<xref target="RFC5576">RFC5576</xref> defines a mechanism to describe
RTP media sources, which are identified by their synchronization source (SSRC)
identifiers, in SDP, to associate attributes with these 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="RFC5576 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>ssrc </c><c>SSRCs repeated over multiple m=lines is forbidden
if the m-lines are in the same RTP session.
</c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ssrc-group </c><c>Refer to section <xref target="SecssrcgroupAnalysis"></xref>
for specific analysis of the grouping semantics </c><c>M</c><c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>cname </c><c>Not Impacted [Open Issues: what are the rules for CNAME duplication
across sessions?] </c><c>SR</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>previous-ssrc </c><c>SSRCs repeated over multiple m=lines complicates
multiplexing </c><c>SR</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>fmtp </c><c>Not Impacted </c><c>SR</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6236">
<t>
<xref target="RFC6236">RFC6236</xref> proposes a new generic session setup
attribute to make it possible to negotiate different image attributes
such as image size. A possible use case is to make it possible for a low-end hand-
held 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="RFC6236 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>imageattr </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6285">
<t>
<xref target="RFC6285">RFC6285</xref> describes a method using the
existing RTP and RTP Control Protocol (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 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="RFC6285 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rams-updates </c><c>Not recommended </c><c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6230">
<t>
<xref target="RFC6230">RFC6230</xref> 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 the Session Initiation Protocol (SIP) to establish an
application-level control mechanism between application servers and
associated external servers such as media servers.
</t>
<texttable title="RFC6230 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>cfw-id </c><c>Not Applicable </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6364">
<t>
<xref target="RFC6364">RFC6364</xref> specifies the use of the
Session Description Protocol (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="RFC6364 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>fec-source-flow </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>fec-repair-flow </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>repair-window </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4796">
<t>
<xref target="RFC4796">RFC4796</xref> defines a new Session Description Protocol (SDP) media-
level attribute, 'content'. The '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' 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="RFC4796 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>content </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC3407">
<t>
<xref target="RFC3407">RFC3407</xref> defines a set of
Session Description Protocol (SDP) attributes that enables SDP to
provide a minimal and backwards compatible capability declaration mechanism.
</t>
<texttable title="RFC3407 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>sqn </c><c>Not Impacted </c>
<c>B</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>csdc </c><c>Mismatch in the offered capability description MAY fail
multiplexing. </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>cpar </c><c>Mismatch in the offered capability parameters MAY fail
multiplexing. </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>cparmin </c><c>Mismatch in the offered capability parameters MAY fail
multiplexing. </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>cparmax </c><c>Mismatch in the offered capability parameters MAY fail
multiplexing. </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6284">
<t>
<xref target="RFC6284">RFC6284</xref> presents a 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="RFC6284 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>portmapping-req </c><c>Not recommended, if port mapping is
required by the application </c><c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6714">
<t>
<xref target="RFC6714">RFC6714</xref> defines a Message Session Relay Protocol (MSRP)
extension, Connection Establishment for Media Anchoring (CEMA).
Support of this extension is OPTIONAL. The extension allows
middleboxes to anchor the MSRP connection, without the need for
middleboxes to modify the MSRP messages; thus, it also enables secure
end-to-end MSRP communication in networks where such middleboxes are
deployed. This document also defines a Session Description Protocol
(SDP) attribute, 'msrp-cema', that MSRP endpoints use to indicate
support of the CEMA extension.
</t>
<texttable title="RFC6714 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>msrp-cema </c><c>Not recommended due to legacy
interop purposes </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4583">
<t>
<xref target="RFC4583">RFC4583</xref> document specifies how to describe
Binary Floor Control Protocol (BFCP) streams in Session Description Protocol (SDP)
descriptions. User agents using the offer/answer model to establish BFCP streams
use this format in their offers and answers
</t>
<texttable title="RFC4583 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>floorctrl </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>confid </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>userid </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>floorid </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5547">
<t>
<xref target="RFC5547">RFC5547</xref> provides a mechanism to negotiate the transfer of one
or more files between two endpoints by using the Session Description
Protocol (SDP) offer/answer model specified in <xref target="RFC3264"/>.
</t>
<texttable title="RFC5547 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>file-selector </c><c>Not Impacted </c>
<c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>file-transfer-id </c><c>Not Impacted </c>
<c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c> file-disposition </c><c>Not Impacted </c>
<c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c> file-date,file-iconfile-range </c><c>Not Impacted </c>
<c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c> file-iconfile-range </c><c>Not Impacted </c>
<c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>file-iconfile-range </c><c>Not Impacted </c>
<c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="draft-ietf-mmusic-media-loopback">
<t>
<xref target="MEDIA_LOOPBACK"></xref> adds new SDP media types and
attributes, which 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 VoIP, Real-time Text and
Video over IP performance metrics.
</t>
<texttable title="draft-ietf-mmusic-media-loopback Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>loopback rtp-pkt-loopback </c><c>The attribute MUST be repeated across all
m=lines multiplexed </c><c>M</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>loopback rtp-media-loopback </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>loopback-source </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>loopback-mirror </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5760">
<t>
<xref target="RFC5760">RFC5760</xref> specifies an extension to the Real-time Transport
Control Protocol (RTCP) to use unicast feedback to a multicast
sender. The proposed extension is useful for single-source multicast
sessions such as 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="RFC5760 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rtcp-unicast </c><c>The attribute MUST be reported across all
m=lines multiplexed </c><c>M</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC3611">
<t>
<xref target="RFC3611">RFC3611</xref> defines the Extended Report (XR) packet type for the
RTP Control Protocol (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="RFC3611 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rtcp-xr </c><c>The attribute MUST be reported across all
m=lines multiplexed </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5939">
<t>
<xref target="RFC5939">RFC5939</xref> 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="RFC5939 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>pcfg </c><c>Depends on capability being negotiated </c>
<c>M</c><c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>acfg </c><c>Depends on capability being negotiated </c><c>M</c>
<c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>csup </c><c>Depends on capability being negotiated </c><c>B</c>
<c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>creq </c><c>Depends on capability being negotiateds </c><c>B</c>
<c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>acap </c><c>Depends on capability being negotiated </c><c>B</c>
<c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>tcap </c><c>Repeat transport capability across all
m= lines </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="draft-ietf-mmusic-sdp-media-capabilities">
<t>
Session Description Protocol (SDP) capability negotiation provides a
general framework for indicating and negotiating capabilities in SDP.
The base framework defines only capabilities for negotiating
transport protocols and attributes. <xref target="MEDIA_CAP"></xref>
extends the framework by defining media capabilities that can be used to
negotiate media types and their associated parameters.
</t>
<texttable title="draft-ietf-mmusic-sdp-media-capabilities Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rmcap </c><c>Not Impacted </c><c>B</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>omcap </c><c>Not Impacted </c><c>B</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>mfcap </c><c>Not Impacted </c><c>B</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>mscap </c><c>Not Impacted </c><c>B</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>lcfg </c><c>Not Impacted </c><c>B</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>secap </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4567">
<t>
<xref target="RFC4567">RFC4567</xref> defines general extensions for Session Description
Protocol (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, 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="RFC4567 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>key-mgmt </c><c>Key management protocol MUST be identical
across all the m=lines </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4572">
<t>
<xref target="RFC4572">RFC4572</xref> specifies how to establish
secure connection-oriented media transport sessions over the
Transport Layer Security (TLS) protocol using the Session Description Protocol (SDP).
It defines a new SDP protocol identifier, 'TCP/TLS'. It also defines the syntax
and semantics for an SDP 'fingerprint' attribute that identifies the
certificate that will be presented for the 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="RFC4572 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>fingerprint </c><c>Fingerprint value MUST be identical
across all the m=lines </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4570">
<t>
<xref target="RFC4570">RFC4570</xref> describes how to adapt the
Session Description Protocol (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 can be used to specify a
Source-Specific Multicast (SSM) session
</t>
<texttable title="RFC4570 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>source-filter </c><c>he attribute MUST be repeated across all
m=lines multiplexed </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6128">
<t>
The Session Description Protocol (SDP) has an attribute that allows
RTP applications to specify an address and a port associated with the
RTP Control Protocol (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,
and 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">RFC6128</xref>
removes this restriction by introducing a new SDP attribute.
</t>
<texttable title="RFC6128 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>multicast-rtcp </c><c>Multicast RTCP port MUST be
identical across all the m=lines </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6189">
<t>
<xref target="RFC6189">RFC6189</xref> defines ZRTP, a protocol for media path Diffie-Hellman
exchange to agree on a session key and parameters for establishing
unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice
over IP (VoIP) applications.
</t>
<texttable title="RFC6189 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>zrtp-hash </c><c>Complicates if all the m=lines are not
authenticated </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4145">
<t>
<xref target="RFC4145">RFC4145</xref> describes how to express media
transport over TCP using the Session Description Protocol (SDP).
It defines the SDP 'TCP' protocol identifier, the SDP 'setup' attribute,
which describes the connection setup procedure, and the SDP 'connection'
attribute, which handles connection reestablishment.
</t>
<texttable title="RFC4145 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>setup </c><c>Not recommended for multiplexing due to possible
differences in the protocol and media types </c>
<c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>connection </c><c>Not recommended for multiplexing due to possible
differences in the protocol and media types </c>
<c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5159">
<t>
<xref target="RFC5159">RFC5159</xref> provides descriptions of Session Description Protocol
(SDP) attributes used by the Open Mobile Alliance's Broadcast Service
and Content Protection specification.
</t>
<texttable title="RFC5159 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>bcastversion </c><c>Not recommended for multiplexing for
legacy interop purposes </c>
<c>S</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>stkmstream </c><c>Not recommended for multiplexing for
legacy interop purposes </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>SRTPAuthentication </c><c>Not recommended for multiplexing for
legacy interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>SRTPROCTxRate </c><c>Not recommended for multiplexing for
legacy interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6193">
<t>
<xref target="RFC6193">RFC6193</xref> 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 the Session
Description Protocol (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="RFC6193 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>ike-setup </c><c>Attribute MUST be identical
across all the m=lines </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>psk-fingerprint </c><c>Attribute MUST be identical
across all the m=lines </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ike-esp </c><c>Attribute MUST be identical
across all the m=lines </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ike-esp-udpencap </c><c>Attribute MUST be identical
across all the m=lines </c><c>B</c><c>IDENTICAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
<t hangText="Note"> In the case of session multiplexed with multiple m=lines,
this SHOULD create only one IPSEC association for all the m=lines.
</t>
</section>
<section title="RFC6064">
<t>
The Packet-switched Streaming Service (PSS) and the Multimedia
Broadcast/Multicast Service (MBMS) defined by 3GPP use the Session
Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)
with some extensions. <xref target="RFC6064">RFC6064</xref>
provides information about these extensions and registers the RTSP and
SDP extensions with IANA.
</t>
<texttable title="RFC6064 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>X-predecbufsize </c><c>Case1:Aggregate total when video m-lines
are muxed Case2:Multiplexing with audio m=lines is invalid</c>
<c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>X-initpredecbufperiod </c><c>Case1:Aggregate total when video m-lines
are muxed Case2:Multiplexing with audio m=lines is invalid</c>
<c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>X-initpostdecbufperiod </c><c>Case1:Aggregate total when video m-lines
are muxed Case2:Multiplexing with audio m=lines is invalid</c>
<c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>X-decbyterate</c><c>Case1:Aggregate total when video m-lines
are muxed Case2:Multiplexing with audio m=lines is invalid</c>
<c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>3gpp-videopostdecbufsize </c><c>Case1:Aggregate total when video m-lines
are muxed. Case2:Multiplexing with audio m=lines is invalid</c>
<c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>framesize</c><c>Not Impacted</c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>3GPP-Integrity-Key </c><c>Not Impacted</c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>3GPP-SRTP-Config </c><c>Same config SHALL apply to all the m=lines
multiplexed </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>alt,alt-default-id </c><c>Specifying alternate m=lines when session
with mulitple m=lines of different types cannot be clearly specified </c>
<c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>alt-group </c><c>Complicates selection of alternate m=lines
grouped with alt-group on mulitplexing </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>3GPP-Adaptation-Support </c><c>Not recommended for legacy
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>3GPP-QoE-Metricsn </c>
<c>Not recommended for legacy interop purposes </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>3GPP-Asset-Informatio </c><c>Not recommended for legacy interop
purposes </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>mbms-mode </c><c>Not recommended for legacy interop
purposes </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>mbms-flowid </c><c>Multiplexing multiple m=lines complicates
FEC mappings to the transport addresses. </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>mbms-repair </c><c>Not recommended for legacy
interop purposes </c><c>B</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC3108">
<t>
<xref target="RFC3108">RFC3108</xref> describes conventions for using the Session Description
Protocol (SDP) described for controlling ATM Bearer Connections, and
any associated ATM Adaptation Layer (AAL)
</t>
<texttable title="RFC3108 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>aalType </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>eecid </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>aalType </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>capability </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>qosClass </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>bcob </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>stc </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>upcc </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>atmQOSparms </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>atmTrfcDesc </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>abrParms </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>abrSetup </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>bearerType </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>lij </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>anycast </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>cache </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>bearerSigIE </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>aalApp </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>cbrRate </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>sbc </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>clkrec </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>fec </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>prtfl </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>structure </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>cpsSDUsize </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>aal2CPS </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>aal2CPSSDUrate </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>aal2sscs3661unassured </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>aal2sscs3661assured </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>aal2sscs3662 </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>aal5sscop </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>atmmap </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>silenceSupp </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>ecan </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>gc </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>profileDesc </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>vsel </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>dsel </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>fsel </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>onewaySel </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>codecconfig </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>isup_usi </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>isup_usi </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c>chain </c><c>Not recommended for legacy interop
purposes </c><c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="3GPP TS 24.182">
<t>
<xref target="3GPP TS 24.182">3GPP TS 24.182</xref> specifies IP multimedia subsystem Custom Alerting tones
</t>
<texttable title="3GPP TS 24.182 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>g.3gpp.cat </c><c>Not recommended due to interop
purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="3GPP TS 24.183">
<t>
<xref target="3GPP TS 24.183">3GPP TS 24.183</xref>specifies IP multimedia
subsystem Custom Ringing Signal
</t>
<texttable title="3GPP TS 24.183 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>g.3gpp.crs </c><c>Not recommended due to interop
purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="3GPP TS 24.229">
<t>
<xref target="3GPP TS 24.229">3GPP TS 24.229</xref>IP multimedia call control
protocol based on Session Initial protocol and Session Description Protocol.
</t>
<texttable title="3GPP TS 24.229 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>secondary-realm </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>visited realm </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>omr-m-cksum </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>omr-s-cksum </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>omr-m-att </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>omr-s-att </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>omr-s-bw </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>omr-m-att </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>omr-codecs </c><c>Not recommended due to
interop purposes </c><c>M</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="ITU T.38">
<t>
ITU T.38<xref target="T.38"></xref> defines procedures for real-time Group 3
fascimile communications over IP netowrks.
</t>
<texttable title="Historic Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>T38FaxVersion </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>T38MaxBitRate </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>T38FaxFillBitRemoval </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>T38FaxTranscodingMMR </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>T38FaxTranscodingJBIG </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>T38FaxRateManagement </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>T38FaxMaxBuffer </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>T38FaxMaxDatagram </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>T38FaxUdpEC </c><c>Not Impacted </c><c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="ITU-T H.248.15">
<t>
ITU-T H.248.15 <xref target="H.248.15"></xref> defines Gateway Control Protocol
SDP H.248 package attribute
</t>
<texttable title="Historic Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>h248item </c><c>Not recommended for interop purposes </c>
<c>S</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4975">
<t>
<xref target="RFC4975">RFC4975</xref> 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
protocol such as the Session Initiation Protocol.
</t>
<texttable title="RFC4975 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>accept-types </c><c>Not recommended due to incompatible media types </c>
<c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>accept-wrapped-types </c><c>Not recommended due to incompatible media typess </c>
<c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>max-size </c><c>Not recommended due to incompatible media types </c>
<c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>path </c><c>Not recommended due to incompatible media types </c>
<c>M </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="Unknowns">
<t>
This section specifies analysis for the attributes that are included for historic
usage alone by the [IANA_REF]
</t>
<texttable title="Unknowns Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rtpred1 </c><c>Not Applicable </c>
<c>Not-Applcable</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>rtpred2 </c><c>Not Applicable </c>
<c>Not-Applcable</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>PSCid </c><c>Not Applicable </c>
<c>Not-Applcable</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>bc_service </c><c>Not Applicable </c>
<c>Not-Applcable</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>bc_program </c><c>Not Applicable </c>
<c>Not-Applcable</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
<c>bc_service_package </c><c>Not Applicable </c>
<c>Not-Applcable</c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="bwtype Attribute Analysis" anchor="SecbwtypeAnalysis" >
<t>
This section specifies handling of specific bandwidth attributes when
used in multiplexing scenarios.
</t>
<section title="RFC4566">
<texttable title="RFC4566 bwtype Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>bwtype:CT </c><c>Aggregate bandwidth for the conference </c>
<c>S</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>bwtype:AS </c><c>Aggregate RTP session bandwidth </c>
<c>B</c><c>NORMAL,SUM </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC3556">
<t>
<xref target="RFC3556">RFC3556</xref> defines an extension to the
Session Description Protocol (SDP) to specify two additional modifiers
for the bandwidth attribute. These modifiers may be used to specify
the bandwidth allowed for RTP Control Protocol (RTCP) packets in a Real-time
Transport Protocol (RTP) session
</t>
<texttable title="RFC3556 bwtype Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>bwtype:RS </c><c> </c><c>B</c>
<c>NORMAL,SUM;</c>
<c> </c><c> </c><c> </c><c> </c>
<c>bwtype:RR </c><c> </c><c>B</c>
<c>NORMAL,SUM </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC3890">
<t>
<xref target="RFC3890">RFC3890</xref> defines a Session Description Protocol (SDP)
Transport Independent Application Specific Maximum (TIAS) bandwidth modifier
that does not include transport overhead; instead an additional
packet rate attribute is defined. The transport independent bit-rate
value together with the maximum packet rate can then be used to
calculate the real bit-rate over the transport actually used.
</t>
<texttable title="RFC3890 bwtype Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>bwtype:TIAS </c><c>Application MUST SUM bandwidth from all m=lines of same type
and MUST NOT use default values </c><c>B</c><c>SUM </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="rtcp-fb Attribute Analysis" anchor="SecrtcpfbAnalysis">
<t>
This section analyzes rtcp-fb SDP attributes <xref target="RTCP-FB"></xref>.
</t>
<section title="RFC4585">
<t>
<xref target="RFC4585">RFC4585</xref> 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="RFC4585 Attribute Analysis">
<ttcol align='left'>Attr Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>ack </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>app </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>nack </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>trr-int </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5104">
<t>
<xref target="RFC5104">RFC5104</xref> 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="RFC5104 Attribute Analysis">
<ttcol align='left'>Attr Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>ccm </c><c>Not Impacted</c><c>M</c><c>Normal </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="rtcp-fb "ack/nack" Attribute Analysis" anchor="SecacknackAnalysis">
<t>
This section analyzes rtcp-fb SDP attributes specific to ack and nack feedback
types <xref target="ACK-NACK"></xref>.
</t>
<section title="RFC4585">
<t>
<xref target="RFC4585">RFC4585</xref> 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="RFC4585 Attribute Analysis">
<ttcol align='left'>Attr Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>nack sli </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>nack pli </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ack rpsi </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>ack app </c><c> Feedback parameters MUST be handled in the
app specifc way when multiplexed</c><c>M</c><c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>nack rpsi </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>nack app </c><c>Feedback parameters MUST be handled in the
app specifc way when multiplexed</c><c>M</c><c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6285">
<texttable title="RFC6285 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>nack rai </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6679">
<t>
<xref target="RFC6679">RFC6679</xref> specifies how Explicit Congestion Notification (ECN) can be
used with the Real-time Transport Protocol (RTP) running over UDP,
using the RTP Control Protocol (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 Session Traversal Utilities for NAT
(STUN) extension used in the optional initialisation method using
Interactive Connectivity Establishment (ICE)
</t>
<texttable title="RFC6679 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>nack ecn </c><c>Complicates ECN marking when m=lines of different
types are used </c><c>M </c><c>SPECIAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC6642">
<t>
In a large RTP session using the RTP Control Protocol (RTCP) feedback
mechanism defined in RFC 4585 <xref target="RFC4585"></xref>,
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.
RFC6642 <xref target="RFC6642"></xref> memo 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 Session Description Protocol (SDP) signaling is also defined.
</t>
<texttable title="RFC6642 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>tllei </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>pslei </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="Codec Control Messages Analysis" anchor="SecccmAnalysis">
<t>
This section analyzes rtcp-fb Codec Control Message <xref target="CCM"></xref>.
</t>
<section title="RFC5104">
<texttable title="RFC5104 Attribute Analysis">
<ttcol align='left'>Attr Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>fir </c><c>Not Impacted</c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>tmmbr </c><c>Not Impacted</c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>tstr </c><c>Not Impacted</c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>vbcm </c><c>Not Impacted</c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="group Attribute Analysis"
anchor="SecgroupAnalysis">
<t>
This section analyzes SDP "group" semantics <xref target="GROUP-SEM"></xref>.
</t>
<section title="RFC5888">
<t>
<xref target="RFC5888">RFC5888</xref> defines a framework
to group "m" lines in the Session Description Protocol (SDP)
for different purposes.
</t>
<texttable title="RFC5888 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>group:LS </c><c>Not Impacted </c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>group:FID </c><c>Not Impacted </c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC3524">
<t>
<xref target="RFC3524">RFC3524</xref> defines an extension to the
Session Description Protocol (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="RFC3524 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>group:SRF </c><c>Not Impacted </c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC4091">
<t>
<xref target="RFC4091">RFC4091</xref> defines the
Alternative Network Address Types (ANAT) semantics for the
Session Description Protocol (SDP) grouping framework. The
ANAT semantics allow alternative types of network addresses to
establish a particular media stream.
</t>
<texttable title="RFC4091 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>group:ANAT </c><c>Not Impacted </c><c>S </c><c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5956">
<t>
<xref target="RFC5956">RFC5956</xref> defines the semantics for
grouping the associated source and FEC-based (Forward Error Correction)
repair flows in the Session Description Protocol (SDP). The semantics
defined in the document are to be used with the SDP Grouping Framework (RFC 5888).
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 they provide
support for additive repair flows. SSRC-level (Synchronization
Source) grouping semantics are also defined in this document for
Real-time Transport Protocol (RTP) streams using SSRC multiplexing.
</t>
<texttable title="RFC5956 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>group:FEC-FR </c><c>Not Impacted </c><c>S </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
<section title="RFC5583">
<t>
<xref target="RFC5583">RFC5583</xref> defines semantics that allow for
signaling the decoding dependency of different media descriptions with the
same media type in the Session Description Protocol (SDP). This is required, for
example, if media data is separated and transported in different
network streams as a result of the use of a layered or multiple
descriptive media coding process.
</t>
<texttable title="RFC5583 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>depend lay </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>depend mdc </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="ssrc-group Attribute Analysis"
anchor="SecssrcgroupAnalysis">
<t>
This section analyzes "ssrc-group" semantics <xref target="SSRC-GROUP"></xref>.
</t>
<section title="RFC5576">
<texttable title="RFC5576 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>FID </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>FEC </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>FEC-FR </c><c>Not Impacted </c><c>M</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="QoS Mechanism Token Analysis"
anchor="SecqostokenAnalysis">
<t>
This section analyzes QoS tokes specified with SDP<xref target="QOS"></xref>.
</t>
<section title="RFC5432">
<texttable title="RFC5432 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>rsvp </c><c>Not Impacted </c><c>B</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>nsis </c><c>Not Impacted </c><c>B</c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="k= Attribute Analysis" anchor="Seck=Analysis">
<section title="RFC4566">
<texttable title="RFC4566 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>k= </c><c>It is NOT recommended to use this attribute </c><c>S</c>
<c>BAD </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section title="content Atribute Analysis" anchor="SeccontentAnalysis">
<section title="RFC4796">
<texttable title="RFC4796 Attribute Analysis">
<ttcol align='left'>Name</ttcol>
<ttcol align='left'>Notes</ttcol>
<ttcol align='left'>Current</ttcol>
<ttcol align='left'>Category</ttcol>
<c>content:slides </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>content:speaker </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>content:main </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>content:sl </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
<c>content:alt </c><c>Not Impacted </c><c>M </c><c>NORMAL </c>
<c> </c><c> </c><c> </c><c> </c>
</texttable>
</section>
</section>
<section anchor="sec-transport" title="TRANSPORT Category Example">
<t>
The example below explains the usage of "TRANSPORT" category for RFC4586 "crypto"
parameter when SDP Port number based multiplexing is performed for audio and
video streams.
</t>
<figure>
<artwork align="left" alt="" height="" name="" type="" width=""
xml:space="preserve"><![CDATA[
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 second,first
m=audio 49172 RTP/AVP 99
a=mid:one
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:two
a=crypto:1 AES_CM_128_HMAC_SHA1_80
inline:EcGZiNWpFJhQXdspcl1ekcmVCNWpVLcfHAwJSoj|2^20|1:32
a=rtpmap:96 H261/90000
]]></artwork>
</figure>
<t>
In this example, "a=crypto" attribute is defined for both the audio and
the video m=lines.The one that MUST be used for the multiplexed RTP Session is
the one that corresponds to m=line with mid "two" even though the audio m=line with
mid "one" occurs ahead of it. This is due to BUNDLE grouping semantics
<xref target="I-D.ietf-mmusic-sdp-bundle-negotiation"></xref> which
mandates the values from mid occuring first on the a=group:BUNDLE line to be
considered for seting up the RTP Transport.
</t>
</section>
<section title="IANA Considerations">
<t>TBD</t>
<t> Future versions of this specification will ask the IANA to expand to attribute tables
to include an extra column specifying categories from this draft. </t>
</section>
<section title="Security Considerations">
<t>All the attributes which involve security key needs a careful review to ensure
two-time pad vulnerability is not created</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="RFC4566">
<front>
<title>SDP: Session Description Protocol</title>
<author fullname="M. Handley" initials="M." surname="Handley">
<organization></organization>
</author>
<author fullname="V. Jacobson" initials="V."
surname="Jacobson">
<organization></organization>
</author>
<author fullname="C. Perkins" initials="C."
surname="Perkins">
<organization></organization>
</author>
<date month="July" year="2006" />
</front>
<seriesInfo name="RFC" value="4566" />
<format octets="60854"
target="http://http://tools.ietf.org/html/rfc4566.txt" type="TXT" />
</reference>
<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">
<reference anchor="RFC3264">
<front>
<title>An Offer/Answer Model with Session Description Protocol
(SDP)</title>
<author fullname="J. Rosenberg" initials="J." surname="Rosenberg">
<organization></organization>
</author>
<author fullname="H. Schulzrinne" initials="H."
surname="Schulzrinne">
<organization></organization>
</author>
<date month="June" year="2002" />
</front>
<seriesInfo name="RFC" value="3264" />
<format octets="60854"
target="http://www.rfc-editor.org/rfc/rfc3264.txt" type="TXT" />
</reference>
<reference anchor='RFC4585'>
<front>
<title>Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)</title>
<author initials='J.' surname='Ott' fullname='J. Ott'>
<organization /></author>
<author initials='S.' surname='Wenger' fullname='S. Wenger'>
<organization /></author>
<author initials='N.' surname='Sato' fullname='N. Sato'>
<organization /></author>
<author initials='C.' surname='Burmeister' fullname='C. Burmeister'>
<organization /></author>
<author initials='J.' surname='Rey' fullname='J. Rey'>
<organization /></author>
<date year='2006' month='July' />
</front>
<seriesInfo name='RFC' value='4585' />
<format type='TXT' octets='117762' target='http://www.rfc-editor.org/rfc/rfc4585.txt' />
</reference>
<reference anchor="RFC5245">
<front>
<title>Interactive Connectivity Establishment (ICE):
A Protocol for Network Address Translator (NAT) Traversal for
Offer/Answer Protocols</title>
<author fullname="J. Rosenberg" initials="J." surname="Rosenberg">
<organization></organization>
</author>
<date month="July" year="2006" />
</front>
<seriesInfo name="RFC" value="5245" />
<format octets="60854"
target="http://tools.ietf.org/html/rfc5245.txt" type="TXT" />
</reference>
<reference anchor="RFC5506">
<front>
<title>Support for Reduced-Size Real-Time Transport Control Protocol (RTCP):
Opportunities and Consequences</title>
<author fullname="I. Johansson" initials="I." surname="Johansson">
<organization></organization>
</author>
<date month="April" year="2009" />
</front>
<seriesInfo name="RFC" value="5506" />
<format octets="60854"
target="http://tools.ietf.org/html/rfc5506.txt" type="TXT" />
</reference>
<reference anchor="RFC4796">
<front>
<title>The Session Description Protocol (SDP) Content Attribute</title>
<author fullname="J. Hautakorpi" initials="J." surname="Hautakorpi">
<organization></organization>
</author>
<author fullname="G. Camarillo" initials="G." surname="Camarillo">
<organization></organization>
</author>
<date month="February" year="2007" />
</front>
<seriesInfo name="RFC" value="4796" />
<format octets="60854"
target="http://tools.ietf.org/html/rfc4796.txt" type="TXT" />
</reference>
<reference anchor="RFC5761">
<front>
<title>Multiplexing RTP Data and Control Packets on a Single Port</title>
<author fullname="C. Perkins" initials="C." surname="Perkins">
<organization></organization>
</author>
<author fullname="M. Westerlund" initials="M." surname="Westerlund">
<organization></organization>
</author>
<date month="April" year="2010" />
</front>
<seriesInfo name="RFC" value="5761" />
<format octets="60854"
target="http://tools.ietf.org/html/rfc5761.txt" type="TXT" />
</reference>
<reference anchor="RFC3556">
<front>
<title>Session Description Protocol (SDP) Bandwidth Modifiers
for RTP Control Protocol (RTCP) Bandwidth</title>
<author fullname="S. Casner" initials="S." surname="Casner">
<organization></organization>
</author>
<date month="July" year="2003" />
</front>
<seriesInfo name="RFC" value="3556" />
<format octets="60854"
target="http://tools.ietf.org/html/rfc3556.txt" type="TXT" />
</reference>
<reference anchor="RFC5104">
<front>
<title>Codec Control Messages in the
RTP Audio-Visual Profile with Feedback (AVPF)</title>
<author fullname="S. Wenger" initials="S." surname="Wenger">
<organization></organization>
</author>
<author fullname="U. Chandra" initials="U." surname="Chandra">
<organization></organization>
</author>
<author fullname="M. Westerlund" initials="M." surname="Westerlund">
<organization></organization>
</author>
<author fullname="B. Burman" initials="B." surname="Burman">
<organization></organization>
</author>
<date month="February" year="2008" />
</front>
<seriesInfo name="RFC" value="5104" />
<format octets="60854"
target="http://tools.ietf.org/html/rfc5104.txt" type="TXT" />
</reference>
<reference anchor='RFC5888'>
<front>
<title>The Session Description Protocol (SDP) Grouping Framework</title>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<author initials='H.' surname='Schulzrinne' fullname='H. Schulzrinne'>
<organization /></author>
<date year='2010' month='June' />
</front>
<seriesInfo name='RFC' value='5888' />
<format type='TXT' octets='43924' target='http://www.rfc-editor.org/rfc/rfc5888.txt' />
</reference>
<reference anchor='RFC4574'>
<front>
<title>The Session Description Protocol (SDP) Label Attribute</title>
<author initials='O.' surname='Levin' fullname='O. Levin'>
<organization /></author>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<date year='2006' month='August' />
</front>
<seriesInfo name='RFC' value='4574' />
<format type='TXT' octets='13484' target='http://www.rfc-editor.org/rfc/rfc4574.txt' />
</reference>
<reference anchor='RFC5432'>
<front>
<title>Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP)</title>
<author initials='J.' surname='Polk' fullname='J. Polk'>
<organization /></author>
<author initials='S.' surname='Dhesikan' fullname='S. Dhesikan'>
<organization /></author>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<date year='2009' month='March' />
</front>
<seriesInfo name='RFC' value='5432' />
<format type='TXT' octets='17614' target='http://www.rfc-editor.org/rfc/rfc5432.txt' />
</reference>
<reference anchor='RFC4568'>
<front>
<title>Session Description Protocol (SDP) Security Descriptions for Media Streams</title>
<author initials='F.' surname='Andreasen' fullname='F. Andreasen'>
<organization /></author>
<author initials='M.' surname='Baugher' fullname='M. Baugher'>
<organization /></author>
<author initials='D.' surname='Wing' fullname='D. Wing'>
<organization /></author>
<date year='2006' month='July' />
</front>
<seriesInfo name='RFC' value='4568' />
<format type='TXT' octets='107881' target='http://www.rfc-editor.org/rfc/rfc4568.txt' />
</reference>
<reference anchor='RFC5762'>
<front>
<title>RTP and the Datagram Congestion Control Protocol (DCCP)</title>
<author initials='C.' surname='Perkins' fullname='C. Perkins'>
<organization /></author>
<date year='2010' month='April' />
</front>
<seriesInfo name='RFC' value='5762' />
<format type='TXT' octets='37537' target='http://www.rfc-editor.org/rfc/rfc5762.txt' />
</reference>
<reference anchor='RFC6773'>
<front>
<title>DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT Traversal</title>
<author initials='T.' surname='Phelan' fullname='T. Phelan'>
<organization /></author>
<author initials='G.' surname='Fairhurst' fullname='G. Fairhurst'>
<organization /></author>
<author initials='C.' surname='Perkins' fullname='C. Perkins'>
<organization /></author>
<date year='2012' month='November' />
</front>
<seriesInfo name='RFC' value='6773' />
<format type='TXT' octets='45073' target='http://www.rfc-editor.org/rfc/rfc6773.txt' />
</reference>
<reference anchor='RFC6787'>
<front>
<title>Media Resource Control Protocol Version 2 (MRCPv2)</title>
<author initials='D.' surname='Burnett' fullname='D. Burnett'>
<organization /></author>
<author initials='S.' surname='Shanmugham' fullname='S. Shanmugham'>
<organization /></author>
<date year='2012' month='November' />
</front>
<seriesInfo name='RFC' value='6787' />
<format type='TXT' octets='496648' target='http://www.rfc-editor.org/rfc/rfc6787.txt' />
</reference>
<reference anchor='RFC3890'>
<front>
<title>A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)</title>
<author initials='M.' surname='Westerlund' fullname='M. Westerlund'>
<organization /></author>
<date year='2004' month='September' />
</front>
<seriesInfo name='RFC' value='3890' />
<format type='TXT' octets='49894' target='http://www.rfc-editor.org/rfc/rfc3890.txt' />
</reference>
<reference anchor='RFC3605'>
<front>
<title>Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)</title>
<author initials='C.' surname='Huitema' fullname='C. Huitema'>
<organization /></author>
<date year='2003' month='October' />
</front>
<seriesInfo name='RFC' value='3605' />
<format type='TXT' octets='17270' target='http://www.rfc-editor.org/rfc/rfc3605.txt' />
</reference>
<reference anchor='RFC5285'>
<front>
<title>A General Mechanism for RTP Header Extensions</title>
<author initials='D.' surname='Singer' fullname='D. Singer'>
<organization /></author>
<author initials='H.' surname='Desineni' fullname='H. Desineni'>
<organization /></author>
<date year='2008' month='July' />
</front>
<seriesInfo name='RFC' value='5285' />
<format type='TXT' octets='36844' target='http://www.rfc-editor.org/rfc/rfc5285.txt' />
</reference>
<reference anchor='RFC5576'>
<front>
<title>Source-Specific Media Attributes in the Session Description Protocol (SDP)</title>
<author initials='J.' surname='Lennox' fullname='J. Lennox'>
<organization /></author>
<author initials='J.' surname='Ott' fullname='J. Ott'>
<organization /></author>
<author initials='T.' surname='Schierl' fullname='T. Schierl'>
<organization /></author>
<date year='2009' month='June' />
</front>
<seriesInfo name='RFC' value='5576' />
<format type='TXT' octets='40454' target='http://www.rfc-editor.org/rfc/rfc5576.txt' />
</reference>
<reference anchor='RFC6236'>
<front>
<title>Negotiation of Generic Image Attributes in the Session Description Protocol (SDP)</title>
<author initials='I.' surname='Johansson' fullname='I. Johansson'>
<organization /></author>
<author initials='K.' surname='Jung' fullname='K. Jung'>
<organization /></author>
<date year='2011' month='May' />
</front>
<seriesInfo name='RFC' value='6236' />
<format type='TXT' octets='49356' target='http://www.rfc-editor.org/rfc/rfc6236.txt' />
</reference>
<reference anchor='RFC5583'>
<front>
<title>Signaling Media Decoding Dependency in the Session Description Protocol (SDP)</title>
<author initials='T.' surname='Schierl' fullname='T. Schierl'>
<organization /></author>
<author initials='S.' surname='Wenger' fullname='S. Wenger'>
<organization /></author>
<date year='2009' month='July' />
</front>
<seriesInfo name='RFC' value='5583' />
<format type='TXT' octets='40214' target='http://www.rfc-editor.org/rfc/rfc5583.txt' />
</reference>
<reference anchor='RFC6285'>
<front>
<title>Unicast-Based Rapid Acquisition of Multicast RTP Sessions</title>
<author initials='B.' surname='Ver Steeg' fullname='B. Ver Steeg'>
<organization /></author>
<author initials='A.' surname='Begen' fullname='A. Begen'>
<organization /></author>
<author initials='T.' surname='Van Caenegem' fullname='T. Van Caenegem'>
<organization /></author>
<author initials='Z.' surname='Vax' fullname='Z. Vax'>
<organization /></author>
<date year='2011' month='June' />
</front>
<seriesInfo name='RFC' value='6285' />
<format type='TXT' octets='141497' target='http://www.rfc-editor.org/rfc/rfc6285.txt' />
</reference>
<reference anchor='RFC6230'>
<front>
<title>Media Control Channel Framework</title>
<author initials='C.' surname='Boulton' fullname='C. Boulton'>
<organization /></author>
<author initials='T.' surname='Melanchuk' fullname='T. Melanchuk'>
<organization /></author>
<author initials='S.' surname='McGlashan' fullname='S. McGlashan'>
<organization /></author>
<date year='2011' month='May' />
</front>
<seriesInfo name='RFC' value='6230' />
<format type='TXT' octets='112479' target='http://www.rfc-editor.org/rfc/rfc6230.txt' />
</reference>
<reference anchor='RFC6364'>
<front>
<title>Session Description Protocol Elements for the Forward Error Correction (FEC) Framework</title>
<author initials='A.' surname='Begen' fullname='A. Begen'>
<organization /></author>
<date year='2011' month='October' />
</front>
<seriesInfo name='RFC' value='6364' />
<format type='TXT' octets='36160' target='http://www.rfc-editor.org/rfc/rfc6364.txt' />
</reference>
<reference anchor='RFC3407'>
<front>
<title>Session Description Protocol (SDP) Simple Capability Declaration</title>
<author initials='F.' surname='Andreasen' fullname='F. Andreasen'>
<organization /></author>
<date year='2002' month='October' />
</front>
<seriesInfo name='RFC' value='3407' />
<format type='TXT' octets='21133' target='http://www.rfc-editor.org/rfc/rfc3407.txt' />
</reference>
<reference anchor='RFC6284'>
<front>
<title>Port Mapping between Unicast and Multicast RTP Sessions</title>
<author initials='A.' surname='Begen' fullname='A. Begen'>
<organization /></author>
<author initials='D.' surname='Wing' fullname='D. Wing'>
<organization /></author>
<author initials='T.' surname='Van Caenegem' fullname='T. Van Caenegem'>
<organization /></author>
<date year='2011' month='June' />
</front>
<seriesInfo name='RFC' value='6284' />
<format type='TXT' octets='73289' target='http://www.rfc-editor.org/rfc/rfc6284.txt' />
</reference>
<reference anchor='RFC6714'>
<front>
<title>Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)</title>
<author initials='C.' surname='Holmberg' fullname='C. Holmberg'>
<organization /></author>
<author initials='S.' surname='Blau' fullname='S. Blau'>
<organization /></author>
<author initials='E.' surname='Burger' fullname='E. Burger'>
<organization /></author>
<date year='2012' month='August' />
</front>
<seriesInfo name='RFC' value='6714' />
<format type='TXT' octets='50543' target='http://www.rfc-editor.org/rfc/rfc6714.txt' />
</reference>
<reference anchor='RFC6679'>
<front>
<title>Explicit Congestion Notification (ECN) for RTP over UDP</title>
<author initials='M.' surname='Westerlund' fullname='M. Westerlund'>
<organization /></author>
<author initials='I.' surname='Johansson' fullname='I. Johansson'>
<organization /></author>
<author initials='C.' surname='Perkins' fullname='C. Perkins'>
<organization /></author>
<author initials='P.' surname='O'Hanlon' fullname='P. O'Hanlon'>
<organization /></author>
<author initials='K.' surname='Carlberg' fullname='K. Carlberg'>
<organization /></author>
<date year='2012' month='August' />
</front>
<seriesInfo name='RFC' value='6679' />
<format type='TXT' octets='148560' target='http://www.rfc-editor.org/rfc/rfc6679.txt' />
</reference>
<reference anchor='RFC4583'>
<front>
<title>Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams</title>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<date year='2006' month='November' />
</front>
<seriesInfo name='RFC' value='4583' />
<format type='TXT' octets='24150' target='http://www.rfc-editor.org/rfc/rfc4583.txt' />
</reference>
<reference anchor='RFC5547'>
<front>
<title>A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer</title>
<author initials='M.' surname='Garcia-Martin' fullname='M. Garcia-Martin'>
<organization /></author>
<author initials='M.' surname='Isomaki' fullname='M. Isomaki'>
<organization /></author>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<author initials='S.' surname='Loreto' fullname='S. Loreto'>
<organization /></author>
<author initials='P.' surname='Kyzivat' fullname='P. Kyzivat'>
<organization /></author>
<date year='2009' month='May' />
</front>
<seriesInfo name='RFC' value='5547' />
<format type='TXT' octets='112625' target='http://www.rfc-editor.org/rfc/rfc5547.txt' />
</reference>
<reference anchor='RFC5760'>
<front>
<title>RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast Feedback</title>
<author initials='J.' surname='Ott' fullname='J. Ott'>
<organization /></author>
<author initials='J.' surname='Chesterfield' fullname='J. Chesterfield'>
<organization /></author>
<author initials='E.' surname='Schooler' fullname='E. Schooler'>
<organization /></author>
<date year='2010' month='February' />
</front>
<seriesInfo name='RFC' value='5760' />
<format type='TXT' octets='160368' target='http://www.rfc-editor.org/rfc/rfc5760.txt' />
</reference>
<reference anchor='RFC3611'>
<front>
<title>RTP Control Protocol Extended Reports (RTCP XR)</title>
<author initials='T.' surname='Friedman' fullname='T. Friedman'>
<organization /></author>
<author initials='R.' surname='Caceres' fullname='R. Caceres'>
<organization /></author>
<author initials='A.' surname='Clark' fullname='A. Clark'>
<organization /></author>
<date year='2003' month='November' />
</front>
<seriesInfo name='RFC' value='3611' />
<format type='TXT' octets='126736' target='http://www.rfc-editor.org/rfc/rfc3611.txt' />
</reference>
<reference anchor='RFC5939'>
<front>
<title>Session Description Protocol (SDP) Capability Negotiation</title>
<author initials='F.' surname='Andreasen' fullname='F. Andreasen'>
<organization /></author>
<date year='2010' month='September' />
</front>
<seriesInfo name='RFC' value='5939' />
<format type='TXT' octets='188116' target='http://www.rfc-editor.org/rfc/rfc5939.txt' />
</reference>
<reference anchor='RFC4567'>
<front>
<title>Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)</title>
<author initials='J.' surname='Arkko' fullname='J. Arkko'>
<organization /></author>
<author initials='F.' surname='Lindholm' fullname='F. Lindholm'>
<organization /></author>
<author initials='M.' surname='Naslund' fullname='M. Naslund'>
<organization /></author>
<author initials='K.' surname='Norrman' fullname='K. Norrman'>
<organization /></author>
<author initials='E.' surname='Carrara' fullname='E. Carrara'>
<organization /></author>
<date year='2006' month='July' />
</front>
<seriesInfo name='RFC' value='4567' />
<format type='TXT' octets='67693' target='http://www.rfc-editor.org/rfc/rfc4567.txt' />
</reference>
<reference anchor='RFC4572'>
<front>
<title>Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)</title>
<author initials='J.' surname='Lennox' fullname='J. Lennox'>
<organization /></author>
<date year='2006' month='July' />
</front>
<seriesInfo name='RFC' value='4572' />
<format type='TXT' octets='38658' target='http://www.rfc-editor.org/rfc/rfc4572.txt' />
</reference>
<reference anchor='RFC4570'>
<front>
<title>Session Description Protocol (SDP) Source Filters</title>
<author initials='B.' surname='Quinn' fullname='B. Quinn'>
<organization /></author>
<author initials='R.' surname='Finlayson' fullname='R. Finlayson'>
<organization /></author>
<date year='2006' month='July' />
</front>
<seriesInfo name='RFC' value='4570' />
<format type='TXT' octets='28601' target='http://www.rfc-editor.org/rfc/rfc4570.txt' />
</reference>
<reference anchor='RFC6128'>
<front>
<title>RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions</title>
<author initials='A.' surname='Begen' fullname='A. Begen'>
<organization /></author>
<date year='2011' month='February' />
</front>
<seriesInfo name='RFC' value='6128' />
<format type='TXT' octets='11544' target='http://www.rfc-editor.org/rfc/rfc6128.txt' />
</reference>
<reference anchor='RFC6189'>
<front>
<title>ZRTP: Media Path Key Agreement for Unicast Secure RTP</title>
<author initials='P.' surname='Zimmermann' fullname='P. Zimmermann'>
<organization /></author>
<author initials='A.' surname='Johnston' fullname='A. Johnston'>
<organization /></author>
<author initials='J.' surname='Callas' fullname='J. Callas'>
<organization /></author>
<date year='2011' month='April' />
</front>
<seriesInfo name='RFC' value='6189' />
<format type='TXT' octets='293784' target='http://www.rfc-editor.org/rfc/rfc6189.txt' />
</reference>
<reference anchor='RFC4145'>
<front>
<title>TCP-Based Media Transport in the Session Description Protocol (SDP)</title>
<author initials='D.' surname='Yon' fullname='D. Yon'>
<organization /></author>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<date year='2005' month='September' />
</front>
<seriesInfo name='RFC' value='4145' />
<format type='TXT' octets='30225' target='http://www.rfc-editor.org/rfc/rfc4145.txt' />
</reference>
<reference anchor='RFC6193'>
<front>
<title>Media Description for the Internet Key Exchange Protocol (IKE) in the Session Description Protocol (SDP)</title>
<author initials='M.' surname='Saito' fullname='M. Saito'>
<organization /></author>
<author initials='D.' surname='Wing' fullname='D. Wing'>
<organization /></author>
<author initials='M.' surname='Toyama' fullname='M. Toyama'>
<organization /></author>
<date year='2011' month='April' />
</front>
<seriesInfo name='RFC' value='6193' />
<format type='TXT' octets='50201' target='http://www.rfc-editor.org/rfc/rfc6193.txt' />
</reference>
<reference anchor='RFC6642'>
<front>
<title>RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report</title>
<author initials='Q.' surname='Wu' fullname='Q. Wu'>
<organization /></author>
<author initials='F.' surname='Xia' fullname='F. Xia'>
<organization /></author>
<author initials='R.' surname='Even' fullname='R. Even'>
<organization /></author>
<date year='2012' month='June' />
</front>
<seriesInfo name='RFC' value='6642' />
<format type='TXT' octets='29758' target='http://www.rfc-editor.org/rfc/rfc6642.txt' />
</reference>
<reference anchor='RFC6064'>
<front>
<title>SDP and RTSP Extensions Defined for 3GPP Packet-Switched Streaming Service and Multimedia Broadcast/Multicast Service</title>
<author initials='M.' surname='Westerlund' fullname='M. Westerlund'>
<organization /></author>
<author initials='P.' surname='Frojdh' fullname='P. Frojdh'>
<organization /></author>
<date year='2011' month='January' />
</front>
<seriesInfo name='RFC' value='6064' />
<format type='TXT' octets='44810' target='http://www.rfc-editor.org/rfc/rfc6064.txt' />
</reference>
<reference anchor='RFC4091'>
<front>
<title>The Alternative Network Address Types (ANAT) Semantics for the Session Description Protocol (SDP) Grouping Framework</title>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'>
<organization /></author>
<date year='2005' month='June' />
</front>
<seriesInfo name='RFC' value='4091' />
<format type='TXT' octets='12931' target='http://www.rfc-editor.org/rfc/rfc4091.txt' />
</reference>
<reference anchor='RFC5956'>
<front>
<title>Forward Error Correction Grouping Semantics in the Session Description Protocol</title>
<author initials='A.' surname='Begen' fullname='A. Begen'>
<organization /></author>
<date year='2010' month='September' />
</front>
<seriesInfo name='RFC' value='5956' />
<format type='TXT' octets='29530' target='http://www.rfc-editor.org/rfc/rfc5956.txt' />
</reference>
<reference anchor='RFC3108'>
<front>
<title>Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections</title>
<author initials='R.' surname='Kumar' fullname='R. Kumar'>
<organization /></author>
<author initials='M.' surname='Mostafa' fullname='M. Mostafa'>
<organization /></author>
<date year='2001' month='May' />
</front>
<seriesInfo name='RFC' value='3108' />
<format type='TXT' octets='248037' target='http://www.rfc-editor.org/rfc/rfc3108.txt' />
</reference>
<reference anchor='RFC5159'>
<front>
<title>Session Description Protocol (SDP) Attributes for Open Mobile Alliance (OMA) Broadcast (BCAST) Service and Content Protection</title>
<author initials='L.' surname='Dondeti' fullname='L. Dondeti'>
<organization /></author>
<author initials='A.' surname='Jerichow' fullname='A. Jerichow'>
<organization /></author>
<date year='2008' month='March' />
</front>
<seriesInfo name='RFC' value='5159' />
<format type='TXT' octets='13921' target='http://www.rfc-editor.org/rfc/rfc5159.txt' />
</reference>
<reference anchor='RFC3524'>
<front>
<title>Mapping of Media Streams to Resource Reservation Flows</title>
<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
<organization /></author>
<author initials='A.' surname='Monrad' fullname='A. Monrad'>
<organization /></author>
<date year='2003' month='April' />
</front>
<seriesInfo name='RFC' value='3524' />
<format type='TXT' octets='11249' target='http://www.rfc-editor.org/rfc/rfc3524.txt' />
</reference>
<reference anchor='RFC5763'>
<front>
<title>Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)</title>
<author initials='J.' surname='Fischl' fullname='J. Fischl'>
<organization /></author>
<author initials='H.' surname='Tschofenig' fullname='H. Tschofenig'>
<organization /></author>
<author initials='E.' surname='Rescorla' fullname='E. Rescorla'>
<organization /></author>
<date year='2010' month='May' />
</front>
<seriesInfo name='RFC' value='5763' />
<format type='TXT' octets='81546' target='http://www.rfc-editor.org/rfc/rfc5763.txt' />
</reference>
<reference anchor='RFC4975'>
<front>
<title>The Message Session Relay Protocol (MSRP)</title>
<author initials='B.' surname='Campbell' fullname='B. Campbell'>
<organization /></author>
<author initials='R.' surname='Mahy' fullname='R. Mahy'>
<organization /></author>
<author initials='C.' surname='Jennings' fullname='C. Jennings'>
<organization /></author>
<date year='2007' month='September' />
</front>
<seriesInfo name='RFC' value='4975' />
<format type='TXT' octets='144254' target='http://www.rfc-editor.org/rfc/rfc4975.txt' />
</reference>
<reference anchor='MEDIA_LOOPBACK'>
<front>
<title>An Extension to the Session Description Protocol (SDP)
and Real-time Transport Protocol (RTP) for Media Loopback
</title>
<author initials='H.' surname='Kaplan' fullname='H. Kaplan'>
<organization /></author>
<author initials='K.' surname='Hedayat' fullname='K. Hedayat'>
<organization /></author>
<author initials='N.' surname='Venna' fullname='N. Venna'>
<organization /></author>
<author initials='P.' surname='Jones' fullname='P. Jones'>
<organization /></author>
<author initials='N.' surname='Stratton' fullname='N. Stratton'>
<organization /></author>
<date year='2013' month='January' />
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-mmusic-media-loopback-27' />
<format type='TXT' target='http://tools.ietf.org/id/draft-ietf-mmusic-media-loopback-27.txt' />
</reference>
<reference anchor="I-D.ietf-mmusic-sdp-bundle-negotiation">
<front>
<title>Multiplexing Negotiation Using Session Description Protocol (SDP)
Port Numbers</title>
<author fullname="Christer Holmberg" initials="C" surname="Holmberg">
<organization></organization>
</author>
<author fullname="Harald Alvestrand" initials="H" surname="Alvestrand">
<organization></organization>
</author>
<author fullname="Cullen Jennings" initials="C" surname="Jennings">
<organization></organization>
</author>
<date day="18" month="February" year="2013" />
<abstract>
<t>This specification defines a new SDP Grouping Framework extension,
"BUNDLE", that can be used with the Session Description Protocol
(SDP) Offer/Answer mechanism to negotiate the usage of bundled media,
which refers to the usage of a single 5-tuple for media associated
with multiple SDP media descriptions ("m=" lines).</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft"
value="draft-ietf-mmusic-sdp-bundle-negotiation-03" />
<format target="http://tools.ietf.org/html/draft-holmberg-mmusic-sdp-bundle-negotiation-03.txt"
type="TXT" />
</reference>
<reference anchor="I-D.ietf-avt-multiplexing-rtp">
<front>
<title>Multiplexing Scheme for RTP Flows between Access Routers</title>
<author fullname="Khalil M. El-Khatib" initials="K" surname="El-Khatib">
<organization></organization>
</author>
<author fullname="Gang Luo" initials="G" surname="Luo">
<organization></organization>
</author>
<author fullname="Gregor v. Bochmann" initials="G" surname="Bochmann">
<organization></organization>
</author>
<author fullname="Pinjiang Feng" initials="Pinjiang" surname="Feng">
<organization></organization>
</author>
<date day="22" month="October" year="1999" />
<abstract>
<t>This draft proposes a light-weight data driven approach for
multiplexing low bit rate RTP streams at the edge router of the
Internet in order to reduce the RTP/UDP/IP header overhead associated
with each RTP stream. Audio packets from different sources in a local
access network destined to different users in the same remote access
network are multiplexed into one packet, with the original RTP/UDP/IP
header of each packet replaced with a mini-header (2 bytes), resulting
in a reduction of the overhead. Access routers can use the IP telephony
Border Gateway Protocol (TBGP) to exchange the reachability of IP
destinations in their domains.</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft"
value="http://tools.ietf.org/html/draft-ietf-avt-multiplexing-rtp-01" />
<format target="http://tools.ietf.org/html/draft-ietf-avt-multiplexing-rtp-01.txt"
type="TXT" />
</reference>
<reference anchor='MEDIA_CAP'>
<front>
<title>Session Description Protocol (SDP) Media Capabilities Negotiation</title>
<author initials='H.' surname='Kaplan' fullname='R. Gilman'>
<organization /></author>
<author initials='K.' surname='Hedayat' fullname=' R. Even'>
<organization /></author>
<author initials='N.' surname='Venna' fullname='F. Andreasen'>
<organization /></author>
<date year='2013' month='January' />
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-mmusic-sdp-media-capabilities-17' />
<format type='TXT' target='http://tools.ietf.org/id/draft-ietf-mmusic-sdp-media-capabilities-17.txt' />
</reference>
<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 for real-time Group 3 facsimile communication over IP networks</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='H.248.15' target="http://www.itu.int/rec/T-REC-H.248.15">
<front>
<title> Gateway control protocol: SDP H.248 package attribute</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='3GPP TS 24.229' target="http://www.3gpp.org/ftp/Specs/html-info/24229.htm">
<front>
<title>IP multimedia call control protocol based on Session Initiation Protocol (SIP)
and Session Description Protocol (SDP);</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='3GPP TS 24.182' target="http://www.3gpp.org/ftp/Specs/html-info/24182.htm">
<front>
<title>IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='3GPP TS 24.183' target="http://www.3gpp.org/ftp/Specs/html-info/24183.htm">
<front>
<title>IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='RTCP-FB'
target="http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml#sdp-parameters-14">
<front>
<title>Session Description Protocol (SDP) RTCP Feedback attributes</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='ACK-NACK'
target="http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml#sdp-parameters-15">
<front>
<title>Session Description Protocol (SDP) RTCP ACK/NACK Feedback attributes</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='CCM'
target="http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml#sdp-parameters-19">
<front>
<title>Session Description Protocol (SDP) RTCP-FB Codec Control Messages</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='GROUP-SEM'
target="http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml#sdp-parameters-13">
<front>
<title>Session Description Protocol (SDP) "group" semantics</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='SSRC-GROUP'
target="http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml#sdp-parameters-17">
<front>
<title>Session Description Protocol (SDP) "ssrc-group" semantics</title>
<author/>
<date/>
</front>
</reference>
<reference anchor='QOS'
target="http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml#sdp-parameters-20">
<front>
<title>Session Description Protocol (SDP) QoS Mechanism Tokens</title>
<author/>
<date/>
</front>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 19:44:10 |