draft-ietf-mmusic-sdp-mux-attributes-06.txt   draft-ietf-mmusic-sdp-mux-attributes-07.txt 
Network Working Group S. Nandakumar Network Working Group S. Nandakumar
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track December 11, 2014 Intended status: Standards Track January 16, 2015
Expires: June 14, 2015 Expires: July 20, 2015
A Framework for SDP Attributes when Multiplexing A Framework for SDP Attributes when Multiplexing
draft-ietf-mmusic-sdp-mux-attributes-06 draft-ietf-mmusic-sdp-mux-attributes-07
Abstract Abstract
The Session Description Protocol (SDP) provides mechanisms to The Session Description Protocol (SDP) provides mechanisms to
describe attributes of multimedia sessions and of individual media describe attributes of multimedia sessions and of individual media
streams (e.g., Real-time Transport Protocol (RTP) sessions) within a streams (e.g., Real-time Transport Protocol (RTP) sessions) within a
multimedia session. [I-D.ietf-mmusic-sdp-bundle-negotiation] multimedia session. Typically media associated with individual media
provides SDP extensions to negotiate the usage of single 5-tuple for descriptions ("m=" lines) represent seperate RTP Sessions and thus
sending and receiving media associated with multiple media carried over individual underlying transport layer flows. For
descriptions ("m=" lines). Such a mechanism has made it necessary to scenarios where SDP is used to negotiate the usage of single 5-tuple
understand the semantic implications of the SDP attributes associated for sending and receiving media associated with multiple media
with the RTP Media Streams multiplexed over a single underlying descriptions, it is required to understand the semantic implications
transport layer flow. of the SDP attributes associated with the RTP Media Streams
multiplexed over a single underlying transport layer flow.
The purpose of this specification is to provide a framework for The purpose of this specification is to provide a framework for
analyzing the multiplexing characteristics of SDP attributes. This analyzing the multiplexing characteristics of SDP attributes. This
specification also categorizes the existing SDP attributes based on specification also categorizes the existing SDP attributes based on
the framework described herein. the framework described herein.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 44 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 14, 2015. This Internet-Draft will expire on July 20, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 9, line 10 skipping to change at page 9, line 10
Attributes can be set as they are normally used but software using Attributes can be set as they are normally used but software using
them in the multiplexing scenario, MUST apply the sum of all the them in the multiplexing scenario, MUST apply the sum of all the
attributes being multiplexed instead of trying to use them attributes being multiplexed instead of trying to use them
independently. This is typically used for bandwidth or other rate independently. This is typically used for bandwidth or other rate
limiting attributes to the underlying transport. limiting attributes to the underlying transport.
The software parsing the SDP sample below, should use the aggregate The software parsing the SDP sample below, should use the aggregate
Application Specific (AS) bandwidth value from the individual media Application Specific (AS) bandwidth value from the individual media
descriptions to determine the AS value for the multiplexed session. descriptions to determine the AS value for the multiplexed session.
Thus the calculated AS value would be 256+64 bytes for the given Thus the calculated AS value would be 256+64 kilobits per second for
example. the given example.
v=0 v=0
o=test 2890844526 2890842807 IN IP4 126.16.64.4 o=test 2890844526 2890842807 IN IP4 126.16.64.4
c=IN IP4 client.biloxi.example.com c=IN IP4 client.biloxi.example.com
t=0 0 t=0 0
m=audio 49170 RTP/AVP 0 m=audio 49170 RTP/AVP 0
b=AS:64 b=AS:64
m=video 51372 RTP/AVP 31 m=video 51372 RTP/AVP 31
b=AS:256 b=AS:256
skipping to change at page 10, line 37 skipping to change at page 10, line 37
today, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of a today, are defined in [RFC3407], [RFC5939] and [RFC6871] as part of a
generic framework for indicating and negotiating transport, media and generic framework for indicating and negotiating transport, media and
media format related capabilities in the SDP. media format related capabilities in the SDP.
The inheritance manifests itself when the encapsulated attribute or The inheritance manifests itself when the encapsulated attribute or
parameter is being leveraged. In the case of SDP Capability parameter is being leveraged. In the case of SDP Capability
Negotiation [RFC5939] for example, this occurs when a capability Negotiation [RFC5939] for example, this occurs when a capability
(encapsulating attribute) is used as part of a configuration; the (encapsulating attribute) is used as part of a configuration; the
configuration inherits the multiplexing category of each of its configuration inherits the multiplexing category of each of its
constituent (encapsulated) attributes and parameters. This in turn constituent (encapsulated) attributes and parameters. This in turn
may place constraints on what constitutes a valid configuration from MAY place constraints on what constitutes a valid configuration from
a multiplexing point of view, e.g. because some attributes must be a multiplexing point of view, e.g. because some attributes MUST be
IDENTICAL (see Section 14 for further details). IDENTICAL (see Section 14 for further details).
v=0 v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s= s=
c=IN IP4 host.atlanta.example.com c=IN IP4 host.atlanta.example.com
t=0 0 t=0 0
m=video 3456 RTP/AVP 100 m=video 3456 RTP/AVP 100
a=rtpmap:100 VP8/90000 a=rtpmap:100 VP8/90000
a=fmtp:100 max-fr=30;max-fs=8040 a=fmtp:100 max-fr=30;max-fs=8040
skipping to change at page 12, line 31 skipping to change at page 12, line 31
a=rtpmap:96 H264/90000 a=rtpmap:96 H264/90000
a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000; a=fmtp:96 profile-level-id=42400d; max-fs=3600; max-fps=3000;
max-mbps=108000; max-br=1000 max-mbps=108000; max-br=1000
a=rtpmap:97 H264/90000 a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000; a=fmtp:97 profile-level-id=42400a; max-fs=240; max-fps=3000;
max-mbps=7200; max-br=200 max-mbps=7200; max-br=200
4.8. Category: SPECIAL 4.8. Category: SPECIAL
Attributes where the text in the specification defining the attribute Attributes where the text in the specification defining the attribute
must be consulted for further handling when multiplexed. MUST be consulted for further handling when multiplexed.
As an example, for the attribute extmap, the specification defining As an example, for the attribute extmap, the specification defining
the extension must be referred to understand the multiplexing the extension needs to be referred to understand the multiplexing
implications. implications.
4.9. Category: TBD 4.9. Category: TBD
Attributes that have not been analyzed under the proposed Attributes that have not been analyzed under the proposed
multiplexing framework yet. For the purposes of implementations it multiplexing framework yet. For the purposes of implementations it
is advised to consider "NOT RECOMMENDED" as the category when is advised to consider "NOT RECOMMENDED" as the category when
multiplexing these attributes. multiplexing these attributes.
5. Analysis of Existing Attributes 5. Analysis of Existing Attributes
skipping to change at page 13, line 35 skipping to change at page 13, line 35
| | | | | | | | | |
| sendonly | Not impacted | B | NORMAL | | sendonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| recvonly | Not impacted | B | NORMAL | | recvonly | Not impacted | B | NORMAL |
| | | | | | | | | |
| inactive | Not impacted | B | NORMAL | | inactive | Not impacted | B | NORMAL |
| | | | | | | | | |
| cat | Not impacted | S | NORMAL | | cat | Not impacted | S | NORMAL |
| | | | | | | | | |
| ptime | The attribute value | M | IDENTICAL-PER-PT | | ptime | The attribute value | M | IDENTICAL-PER-PT |
| | must be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| maxptime | The attribute value | M | IDENTICAL-PER-PT | | maxptime | The attribute value | M | IDENTICAL-PER-PT |
| | must be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| orient | Not Impacted | M | NORMAL | | orient | Not Impacted | M | NORMAL |
| | | | | | | | | |
| framerate | The attribute value | M | IDENTICAL-PER-PT | | framerate | The attribute value | M | IDENTICAL-PER-PT |
| | must be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| quality | Not Impacted | M | NORMAL | | quality | Not Impacted | M | NORMAL |
| | | | | | | | | |
| rtpmap | The attribute value | M | IDENTICAL-PER-PT | | rtpmap | The attribute value | M | IDENTICAL-PER-PT |
| | must be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| fmtp | The attribute value | M | IDENTICAL-PER-PT | | fmtp | The attribute value | M | IDENTICAL-PER-PT |
| | must be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| keywds | Not impacted | S | NORMAL | | keywds | Not impacted | S | NORMAL |
| | | | | | | | | |
| type | Not Impacted | S | NORMAL | | type | Not Impacted | S | NORMAL |
| | | | | | | | | |
| type:broadcast | Not Impacted | S | NORMAL | | type:broadcast | Not Impacted | S | NORMAL |
| | | | | | | | | |
| type:H332 | Not Impacted | S | NORMAL | | type:H332 | Not Impacted | S | NORMAL |
skipping to change at page 17, line 34 skipping to change at page 17, line 34
[RFC4568] defines a Session Description Protocol (SDP) cryptographic [RFC4568] defines a Session Description Protocol (SDP) cryptographic
attribute for unicast media streams. The attribute describes a attribute for unicast media streams. The attribute describes a
cryptographic key and other parameters that serve to configure cryptographic key and other parameters that serve to configure
security for a unicast media stream in either a single message or a security for a unicast media stream in either a single message or a
roundtrip exchange. roundtrip exchange.
+---------+------------------------------------+-------+------------+ +---------+------------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------+------------------------------------+-------+------------+ +---------+------------------------------------+-------+------------+
| crypto | crypto attribute must be the one | M | TRANSPORT | | crypto | crypto attribute MUST be the one | M | TRANSPORT |
| | that corresponds to the "m=" line | | | | | that corresponds to the "m=" line | | |
| | chosen for setting up the | | | | | chosen for setting up the | | |
| | underlying transport flow | | | | | underlying transport flow | | |
| | | | | | | | | |
+---------+------------------------------------+-------+------------+ +---------+------------------------------------+-------+------------+
RFC4568 Attribute Analysis RFC4568 Attribute Analysis
5.8. RFC5762 - RTP over DCCP 5.8. RFC5762 - RTP over DCCP
skipping to change at page 18, line 31 skipping to change at page 18, line 31
+--------------------+---------------------+---------+--------------+ +--------------------+---------------------+---------+--------------+
RFC5762 Attribute Analysis RFC5762 Attribute Analysis
If RFC6773 is being used in addition to RFC5762 and provided that If RFC6773 is being used in addition to RFC5762 and provided that
DCCP-in-UDP layer has additional demultiplexing, then it may be DCCP-in-UDP layer has additional demultiplexing, then it may be
possible to use different DCCP service codes for each DCCP flow, possible to use different DCCP service codes for each DCCP flow,
given each uses a different DCCP port. Although doing so might given each uses a different DCCP port. Although doing so might
conflict with the media type of the "m=" line. None of this is conflict with the media type of the "m=" line. None of this is
standardized yet and it wouldn't work as explained. Hence standardized yet and it wouldn't work as explained. Hence
multiplexing must not be performed even in this alternate scenario. multiplexing MUST not be performed even in this alternate scenario.
5.9. RFC6773 - DCCP-UDP Encapsulation 5.9. RFC6773 - DCCP-UDP Encapsulation
[RFC6773] document specifies an alternative encapsulation of the [RFC6773] document specifies an alternative encapsulation of the
Datagram Congestion Control Protocol (DCCP), referred to as DCCP-UDP. Datagram Congestion Control Protocol (DCCP), referred to as DCCP-UDP.
This encapsulation allows DCCP to be carried through the current This encapsulation allows DCCP to be carried through the current
generation of Network Address Translation (NAT) middle boxes without generation of Network Address Translation (NAT) middle boxes without
modification of those middle boxes. modification of those middle boxes.
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
| dccp-port | Multiplexing must not be | M | NOT | | dccp-port | Multiplexing MUST not be | M | NOT |
| | performed due to potential | | RECOMMENDED | | | performed due to potential | | RECOMMENDED |
| | conflict between the port | | | | | conflict between the port | | |
| | used for DCCP | | | | | used for DCCP | | |
| | en/decapsulation and the RTP | | | | | en/decapsulation and the RTP | | |
| | | | | | | | | |
+------------+-------------------------------+-------+--------------+ +------------+-------------------------------+-------+--------------+
RFC6773 Attribute Analysis RFC6773 Attribute Analysis
RFC6773 is about tunneling DCCP in UDP, with the UDP port being the RFC6773 is about tunneling DCCP in UDP, with the UDP port being the
port of the DCCP en-/de-capsulation service. This encapsulation port of the DCCP en-/de-capsulation service. This encapsulation
allows arbitrary DCCP packets to be encapsulated and the DCCP port allows arbitrary DCCP packets to be encapsulated and the DCCP port
chosen may conflict with the port chosen for the RTP traffic. chosen MAY conflict with the port chosen for the RTP traffic.
For multiplexing several DCCP-in-UDP encapsulations on the same UDP For multiplexing several DCCP-in-UDP encapsulations on the same UDP
port, with no RTP traffic on the same port implies collapsing several port, with no RTP traffic on the same port implies collapsing several
DCCP port spaces together. This may or may not work depending on the DCCP port spaces together. This may or may not work depending on the
nature of DCCP encapsulations and ports choices thus rendering it to nature of DCCP encapsulations and ports choices thus rendering it to
be very application dependent. be very application dependent.
5.10. RFC5506 - Reduced-Size RTCP in RTP Profile 5.10. RFC5506 - Reduced-Size RTCP in RTP Profile
[RFC5506] discusses benefits and issues that arise when allowing [RFC5506] discusses benefits and issues that arise when allowing
skipping to change at page 21, line 15 skipping to change at page 21, line 15
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
| ice-lite | Not Impacted | S | NORMAL | | ice-lite | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-options | Not Impacted | S | NORMAL | | ice-options | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-mismatch | Not Impacted | S | NORMAL | | ice-mismatch | Not Impacted | S | NORMAL |
| | | | | | | | | |
| ice-pwd | ice-pwd must be the one | B | TRANSPORT | | ice-pwd | ice-pwd MUST be the one | B | TRANSPORT |
| | that corresponds to the | | | | | that corresponds to the | | |
| | "m=" line chosen for | | | | | "m=" line chosen for | | |
| | setting up the | | | | | setting up the | | |
| | underlying transport | | | | | underlying transport | | |
| | flow | | | | | flow | | |
| | | | | | | | | |
| ice-ufrag | ice-ufrag must be the | B | TRANSPORT | | ice-ufrag | ice-ufrag MUST be the | B | TRANSPORT |
| | one that corresponds to | | | | | one that corresponds to | | |
| | the "m=" line chosen | | | | | the "m=" line chosen | | |
| | for setting up the | | | | | for setting up the | | |
| | underlying transport | | | | | underlying transport | | |
| | flow | | | | | flow | | |
| | | | | | | | | |
| candidate | ice candidate must be | M | TRANSPORT | | candidate | ice candidate MUST be | M | TRANSPORT |
| | the one that | | | | | the one that | | |
| | corresponds to the "m=" | | | | | corresponds to the "m=" | | |
| | line chosen for setting | | | | | line chosen for setting | | |
| | up the underlying | | | | | up the underlying | | |
| | transport flow | | | | | transport flow | | |
| | | | | | | | | |
| remote-candidates | ice remote candidate | M | TRANSPORT | | remote-candidates | ice remote candidate | M | TRANSPORT |
| | must be the one that | | | | | MUST be the one that | | |
| | corresponds to the "m=" | | | | | corresponds to the "m=" | | |
| | line chosen for setting | | | | | line chosen for setting | | |
| | up the underlying | | | | | up the underlying | | |
| | transport flow | | | | | transport flow | | |
| | | | | | | | | |
+--------------------+-------------------------+-------+------------+ +--------------------+-------------------------+-------+------------+
RFC5245 Attribute Analysis RFC5245 Attribute Analysis
5.13. RFC5285 - RTP Header Extensions 5.13. RFC5285 - RTP Header Extensions
skipping to change at page 22, line 12 skipping to change at page 22, line 12
option to use a small number of small extensions in each RTP packet, option to use a small number of small extensions in each RTP packet,
where the universe of possible extensions is large and registration where the universe of possible extensions is large and registration
is de-centralized. The actual extensions in use in a session are is de-centralized. The actual extensions in use in a session are
signaled in the setup information for that session. signaled in the setup information for that session.
+---------+-------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------+-------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
| extmap | Specific RTP extension document | B | SPECIAL | | extmap | Specific RTP extension document | B | SPECIAL |
| | must be referred | | | | | MUST be referred | | |
| | | | | | | | | |
+---------+-------------------------------------+-------+-----------+ +---------+-------------------------------------+-------+-----------+
RFC5285 Attribute Analysis RFC5285 Attribute Analysis
5.14. RFC3605 - RTCP attribute in SDP 5.14. RFC3605 - RTCP attribute in SDP
Originally, SDP assumed that RTP and RTCP were carried on consecutive Originally, SDP assumed that RTP and RTCP were carried on consecutive
ports. However, this is not always true when NATs are involved. ports. However, this is not always true when NATs are involved.
[RFC3605] specifies an early mechanism to indicate the RTCP port. [RFC3605] specifies an early mechanism to indicate the RTCP port.
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| rtcp | Identical attribute value must be | M | IDENTICAL | | rtcp | RTCP Port MUST be the one that | M | TRANSPORT |
| | used since the RTCP port affects the | | | | | corresponds to the "m=" line chosen | | |
| | entire RTP session. | | | | | for setting up the underlying | | |
| | transport flow. | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
RFC3605 Attribute Analysis RFC3605 Attribute Analysis
5.15. RFC5576 - Source-Specific SDP Attributes 5.15. RFC5576 - Source-Specific SDP Attributes
[RFC5576] defines a mechanism to describe RTP media sources, which [RFC5576] defines a mechanism to describe RTP media sources, which
are identified by their synchronization source (SSRC) identifiers, in are identified by their synchronization source (SSRC) identifiers, in
SDP, to associate attributes with these sources, and to express SDP, to associate attributes with these sources, and to express
skipping to change at page 23, line 21 skipping to change at page 23, line 21
| | Section 9 for | | | | | Section 9 for | | |
| | specific analysis of | | | | | specific analysis of | | |
| | the grouping | | | | | the grouping | | |
| | semantics | | | | | semantics | | |
| | | | | | | | | |
| cname | Not Impacted | SR | NORMAL | | cname | Not Impacted | SR | NORMAL |
| | | | | | | | | |
| previous-ssrc | Refer to notes below | SR | NORMAL | | previous-ssrc | Refer to notes below | SR | NORMAL |
| | | | | | | | | |
| fmtp | The attribute value | SR | IDENTICAL-PER-PT | | fmtp | The attribute value | SR | IDENTICAL-PER-PT |
| | must be same for a | | | | | MUST be same for a | | |
| | given codec | | | | | given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+----------------+----------------------+-------+-------------------+ +----------------+----------------------+-------+-------------------+
RFC5576 Attribute Analysis RFC5576 Attribute Analysis
If SSRCs are repeated across "m=" lines being multiplexed, they must If SSRCs are repeated across "m=" lines being multiplexed, they MUST
all represent the same underlying RTP Source. all represent the same underlying RTP Source.
5.16. RFC7273 - RTP Clock Source Signalling 5.16. RFC7273 - RTP Clock Source Signalling
[RFC7273] specifies Session Description Protocol (SDP) signalling [RFC7273] specifies Session Description Protocol (SDP) signalling
that identifies timestamp reference clock sources and SDP signalling that identifies timestamp reference clock sources and SDP signalling
that identifies the media clock sources in a multimedia session. that identifies the media clock sources in a multimedia session.
+------------+---------------+-------+--------------+ +------------+---------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
skipping to change at page 24, line 19 skipping to change at page 24, line 19
A possible use case is to make it possible for a low-end hand-held 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 terminal to display video without the need to rescale the
image,something that may consume large amounts of memory and image,something that may consume large amounts of memory and
processing power. The document also helps to maintain an optimal processing power. The document also helps to maintain an optimal
bitrate for video as only the image size that is desired by the bitrate for video as only the image size that is desired by the
receiver is transmitted. receiver is transmitted.
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
| imageattr | The attribute value must | M | IDENTICAL-PER-PT | | imageattr | The attribute value MUST | M | IDENTICAL-PER-PT |
| | be same for a given | | | | | be same for a given | | |
| | codec configuration | | | | | codec configuration | | |
| | | | | | | | | |
+------------+--------------------------+-------+-------------------+ +------------+--------------------------+-------+-------------------+
RFC6236 Attribute Analysis RFC6236 Attribute Analysis
5.18. RFC7197 - Duplication Delay Attribute in SDP 5.18. RFC7197 - Duplication Delay Attribute in SDP
[RFC7197] defines an attribute to indicate the presence of temporally [RFC7197] defines an attribute to indicate the presence of temporally
skipping to change at page 28, line 37 skipping to change at page 28, line 37
[RFC4583] document specifies how to describe Binary Floor Control [RFC4583] document specifies how to describe Binary Floor Control
Protocol (BFCP) streams in Session Description Protocol (SDP) Protocol (BFCP) streams in Session Description Protocol (SDP)
descriptions. User agents using the offer/answer model to establish descriptions. User agents using the offer/answer model to establish
BFCP streams use this format in their offers and answers. BFCP streams use this format in their offers and answers.
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
| floorctrl | must be repeated across all the | M | IDENTICAL | | floorctrl | The attribute MUST be repeated | M | IDENTICAL |
| | multiplexed "m=" lines | | | | | across all the multiplexed "m=" | | |
| | lines | | |
| | | | | | | | | |
| confid | Not Impacted | M | NORMAL | | confid | Not Impacted | M | NORMAL |
| | | | | | | | | |
| userid | Not Impacted | M | NORMAL | | userid | Not Impacted | M | NORMAL |
| | | | | | | | | |
| floorid | The floorid MUST be globally | M | NORMAL | | floorid | The floorid MUST be globally | M | NORMAL |
| | unique | | | | | unique | | |
| | | | | | | | | |
+------------+---------------------------------+-------+------------+ +------------+---------------------------------+-------+------------+
skipping to change at page 30, line 18 skipping to change at page 30, line 18
Protocol (RTCP) to use unicast feedback to a multicast sender. The Protocol (RTCP) to use unicast feedback to a multicast sender. The
proposed extension is useful for single-source multicast sessions proposed extension is useful for single-source multicast sessions
such as Source-Specific Multicast (SSM) communication where the such as Source-Specific Multicast (SSM) communication where the
traditional model of many-to-many group communication is either not traditional model of many-to-many group communication is either not
available or not desired. available or not desired.
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
| rtcp-unicast | The attribute must be | M | IDENTICAL | | rtcp-unicast | The attribute MUST be | M | IDENTICAL |
| | reported across all "m=" | | | | | reported across all "m=" | | |
| | lines multiplexed | | | | | lines multiplexed | | |
| | | | | | | | | |
+---------------+------------------------------+-------+------------+ +---------------+------------------------------+-------+------------+
RFC5760 Attribute Analysis RFC5760 Attribute Analysis
5.31. RFC3611 - RTCP XR 5.31. RFC3611 - RTCP XR
[RFC3611] defines the Extended Report (XR) packet type for the RTP [RFC3611] defines the Extended Report (XR) packet type for the RTP
skipping to change at page 33, line 14 skipping to change at page 33, line 14
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
| bcap | Inherit the category SUM as | B | INHERIT | | bcap | Inherit the category SUM as | B | INHERIT |
| | applicable to b= attribute | | | | | applicable to b= attribute | | |
| | | | | | | | | |
| bcap-v0 | Not Impacted | B | NORMAL | | bcap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
| ccap | The connection address type must | B | IDENTICAL | | ccap | The connection address type MUST | B | IDENTICAL |
| | be identical across all the | | | | | be identical across all the | | |
| | multiplexed "m=" lines | | | | | multiplexed "m=" lines | | |
| | | | | | | | | |
| ccap-v0 | Not Impacted | B | NORMAL | | ccap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
| icap | Not Impacted | B | NORMAL | | icap | Not Impacted | B | NORMAL |
| | | | | | | | | |
| icap-v0 | Not Impacted | B | NORMAL | | icap-v0 | Not Impacted | B | NORMAL |
| | | | | | | | | |
+----------+-----------------------------------+-------+------------+ +----------+-----------------------------------+-------+------------+
skipping to change at page 33, line 41 skipping to change at page 33, line 41
(SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as (SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as
specified by a key management protocol, in order to secure the media. 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 These extensions are presented as a framework, to be used by one or
more key management protocols. As such, their use is meaningful only more key management protocols. As such, their use is meaningful only
when complemented by an appropriate key management protocol. when complemented by an appropriate key management protocol.
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
| key-mgmt | Key management protocol must be | B | IDENTICAL | | key-mgmt | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the "m=" | | | | | identical across all the "m=" | | |
| | lines | | | | | lines | | |
| | | | | | | | | |
| mikey | Key management protocol must be | B | IDENTICAL | | mikey | Key management protocol MUST be | B | IDENTICAL |
| | identical across all the "m=" | | | | | identical across all the "m=" | | |
| | lines | | | | | lines | | |
| | | | | | | | | |
+-----------+----------------------------------+-------+------------+ +-----------+----------------------------------+-------+------------+
RFC4567 Attribute Analysis RFC4567 Attribute Analysis
5.36. RFC4572 - Comedia over TLS in SDP 5.36. RFC4572 - Comedia over TLS in SDP
[RFC4572] specifies how to establish secure connection-oriented media [RFC4572] specifies how to establish secure connection-oriented media
skipping to change at page 34, line 45 skipping to change at page 34, line 45
syntax and semantics for an SDP "source-filter" attribute that may syntax and semantics for an SDP "source-filter" attribute that may
reference either IPv4 or IPv6 address(es) as either an inclusive or reference either IPv4 or IPv6 address(es) as either an inclusive or
exclusive source list for either multicast or unicast destinations. exclusive source list for either multicast or unicast destinations.
In particular, an inclusive source-filter can be used to specify a In particular, an inclusive source-filter can be used to specify a
Source-Specific Multicast (SSM) session. Source-Specific Multicast (SSM) session.
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
| source-filter | The attribute must be | B | IDENTICAL | | source-filter | The attribute MUST be | B | IDENTICAL |
| | repeated across all "m=" | | | | | repeated across all "m=" | | |
| | lines multiplexed | | | | | lines multiplexed | | |
| | | | | | | | | |
+----------------+-----------------------------+-------+------------+ +----------------+-----------------------------+-------+------------+
RFC4570 Attribute Analysis RFC4570 Attribute Analysis
5.38. RFC6128 - RTCP Port for Multicast Sessions 5.38. RFC6128 - RTCP Port for Multicast Sessions
The Session Description Protocol (SDP) has an attribute that allows The Session Description Protocol (SDP) has an attribute that allows
skipping to change at page 35, line 23 skipping to change at page 35, line 23
itself cannot be specified by the same attribute to avoid ambiguity, 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 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 description. Deriving the RTCP port from the "m=" line imposes an
unnecessary restriction. [RFC6128] removes this restriction by unnecessary restriction. [RFC6128] removes this restriction by
introducing a new SDP attribute. introducing a new SDP attribute.
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
| multicast-rtcp | Multicast RTCP port must | B | IDENTICAL | | multicast-rtcp | Multicast RTCP port MUST | B | IDENTICAL |
| | be identical across all | | | | | be identical across all | | |
| | the "m=" lines | | | | | the "m=" lines | | |
| | | | | | | | | |
+-----------------+----------------------------+-------+------------+ +-----------------+----------------------------+-------+------------+
RFC6128 Attribute Analysis RFC6128 Attribute Analysis
5.39. RFC6189 - ZRTP 5.39. RFC6189 - ZRTP
[RFC6189] defines ZRTP, a protocol for media path Diffie-Hellman [RFC6189] defines ZRTP, a protocol for media path Diffie-Hellman
skipping to change at page 36, line 11 skipping to change at page 36, line 11
[RFC4145] describes how to express media transport over TCP using the [RFC4145] describes how to express media transport over TCP using the
Session Description Protocol (SDP). It defines the SDP 'TCP' Session Description Protocol (SDP). It defines the SDP 'TCP'
protocol identifier, the SDP 'setup' attribute, which describes the protocol identifier, the SDP 'setup' attribute, which describes the
connection setup procedure, and the SDP 'connection' attribute, which connection setup procedure, and the SDP 'connection' attribute, which
handles connection reestablishment. handles connection reestablishment.
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
| setup | must be identical across all | B | IDENTICAL | | setup | The attribute MUST be | B | IDENTICAL |
| | "m=" lines | | | | | identical across all "m=" | | |
| | lines | | |
| | | | | | | | | |
| connection | must be identical across all | B | IDENTICAL | | connection | Thee attribute MUST be | B | IDENTICAL |
| | "m=" lines | | | | | identical across all "m=" | | |
| | lines | | |
| | | | | | | | | |
+-------------+--------------------------------+-------+------------+ +-------------+--------------------------------+-------+------------+
RFC4145 Attribute Analysis RFC4145 Attribute Analysis
5.41. RFC6947 - The SDP ALTC Attribute 5.41. RFC6947 - The SDP ALTC Attribute
[RFC6947] proposes a mechanism that allows the same SDP offer to [RFC6947] proposes a mechanism that allows the same SDP offer to
carry multiple IP addresses of different address families (e.g., IPv4 carry multiple IP addresses of different address families (e.g., IPv4
and IPv6). The proposed attribute, the "altc" attribute, solves the and IPv6). The proposed attribute, the "altc" attribute, solves the
backward-compatibility problem that plagued Alternative Network backward-compatibility problem that plagued Alternative Network
Address Types (ANAT) due to their syntax. Address Types (ANAT) due to their syntax.
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
| altc | The IP Address and port must be the | M | TRANSPORT | | altc | The IP Address and port MUST be the | M | TRANSPORT |
| | one that corresponds to the "m=" | | | | | one that corresponds to the "m=" | | |
| | line chosen for setting up the | | | | | line chosen for setting up the | | |
| | underlying transport flow | | | | | underlying transport flow | | |
| | | | | | | | | |
+-------+--------------------------------------+-------+------------+ +-------+--------------------------------------+-------+------------+
RFC6947 Attribute Analysis RFC6947 Attribute Analysis
5.42. RFC7195 - SDP Extension for Circuit Switched Bearers in PSTN 5.42. RFC7195 - SDP Extension for Circuit Switched Bearers in PSTN
skipping to change at page 38, line 33 skipping to change at page 38, line 33
a virtual private network using the Session Initiation Protocol for a virtual private network using the Session Initiation Protocol for
the purpose of on-demand media/application sharing between peers. It the purpose of on-demand media/application sharing between peers. It
extends the protocol identifier of the Session Description Protocol extends the protocol identifier of the Session Description Protocol
(SDP) so that it can negotiate use of the Internet Key Exchange (SDP) so that it can negotiate use of the Internet Key Exchange
Protocol (IKE) for media sessions in the SDP offer/answer model. Protocol (IKE) for media sessions in the SDP offer/answer model.
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
| ike-setup | Attribute must be | B | IDENTICAL | | ike-setup | Attribute MUST be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
| | "m=" lines | | | | | "m=" lines | | |
| | | | | | | | | |
| psk-fingerprint | Attribute must be | B | IDENTICAL | | psk-fingerprint | Attribute MUST be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
| | "m=" lines | | | | | "m=" lines | | |
| | | | | | | | | |
| ike-esp | Attribute must be | B | IDENTICAL | | ike-esp | Attribute MUST be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
| | "m=" lines | | | | | "m=" lines | | |
| | | | | | | | | |
| ike-esp-udpencap | Attribute must be | B | IDENTICAL | | ike-esp-udpencap | Attribute MUST be | B | IDENTICAL |
| | identical across all the | | | | | identical across all the | | |
| | "m=" lines | | | | | "m=" lines | | |
| | | | | | | | | |
+-------------------+--------------------------+-------+------------+ +-------------------+--------------------------+-------+------------+
RFC6193 Attribute Analysis RFC6193 Attribute Analysis
With the above SDP constraints, a session multiplexed with multiple With the above SDP constraints, a session multiplexed with multiple
"m=" lines will use only one IPSec association for all of the "m=" "m=" lines will use only one IPSec association for all of the "m="
lines. lines.
skipping to change at page 44, line 36 skipping to change at page 44, line 36
| | below | | RECOMMENDED | | | below | | RECOMMENDED |
| | | | | | | | | |
+------------------------+------------------+-------+---------------+ +------------------------+------------------+-------+---------------+
RFC3108 Attribute Analysis RFC3108 Attribute Analysis
RFC3108 describes conventions for using the Session Description RFC3108 describes conventions for using the Session Description
Protocol (SDP) for characterizing ATM bearer connections using an Protocol (SDP) for characterizing ATM bearer connections using an
AAL1, AAL2 or AAL5 adaptation layers. For AAL1, AAL2 and AAL5, AAL1, AAL2 or AAL5 adaptation layers. For AAL1, AAL2 and AAL5,
bearer connections can be used to transport single media streams. In bearer connections can be used to transport single media streams. In
addition, for AAL1 and AAL2, multiple media streams may be addition, for AAL1 and AAL2, multiple media streams MAY be
multiplexed into a bearer connection. For all adaptation types multiplexed into a bearer connection. For all adaptation types
(AAL1, AAL2 and AAL5), bearer connections may be bundled into a (AAL1, AAL2 and AAL5), bearer connections MAY be bundled into a
single media group. In all cases addressed by RFC3108, a real-time single media group. In all cases addressed by RFC3108, a real-time
media stream (voice, video, voiceband data, pseudo-wire and others) media stream (voice, video, voiceband data, pseudo-wire and others)
or a multiplex of media streams is mapped directly into an ATM or a multiplex of media streams is mapped directly into an ATM
connection. RFC3108 does not address cases where ATM serves as a connection. RFC3108 does not address cases where ATM serves as a
low-level transport pipe for IP packets which in turn may carry one low-level transport pipe for IP packets which in turn MAY carry one
or more real-time (e.g. VoIP) media sessions with a life-cycle or more real-time (e.g. VoIP) media sessions with a life-cycle
different from that of the underlying ATM transport. different from that of the underlying ATM transport.
[I-D.ietf-mmusic-sdp-bundle-negotiation] is applicable only for [I-D.ietf-mmusic-sdp-bundle-negotiation] is applicable only for
nettypes IN and address types "IP4" or "IP6". nettypes IN and address types "IP4" or "IP6".
5.49. 3GPP TS 26.114 5.49. 3GPP TS 26.114
[R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and [R3GPPTS26.114] specifies IP multimedia subsystem: Media handling and
interaction interaction
skipping to change at page 47, line 9 skipping to change at page 47, line 9
5.53. 3GPP TS 24.229 5.53. 3GPP TS 24.229
[R3GPPTS24.229] specifies IP multimedia call control protocol based [R3GPPTS24.229] specifies IP multimedia call control protocol based
on Session Initial protocol and Session Description Protocol. on Session Initial protocol and Session Description Protocol.
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| Name | Notes | Level | Mux | | Name | Notes | Level | Mux |
| | | | Category | | | | | Category |
+------------------+---------------------------+-------+------------+ +------------------+---------------------------+-------+------------+
| secondary-realm | secondary-realm must be | M | TRANSPORT | | secondary-realm | secondary-realm MUST be | M | TRANSPORT |
| | the one that corresponds | | | | | the one that corresponds | | |
| | to the "m=" line chosen | | | | | to the "m=" line chosen | | |
| | for setting up the | | | | | for setting up the | | |
| | underlying transport flow | | | | | underlying transport flow | | |
| | | | | | | | | |
| visited-realm | visited-realm must be | M | TRANSPORT | | visited-realm | visited-realm MUST be the | M | TRANSPORT |
| | the one that corresponds | | | | | one that corresponds to | | |
| | to the "m=" line chosen | | | | | the "m=" line chosen for | | |
| | for setting up the | | | | | setting up the underlying | | |
| | underlying transport flow | | | | | transport flow | | |
| | | | | | | | | |
| omr-m-cksum | Not Impacted | M | NORMAL | | omr-m-cksum | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-s-cksum | Not Impacted | M | NORMAL | | omr-s-cksum | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-m-att | Not Impacted | M | NORMAL | | omr-m-att | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-s-att | Not Impacted | M | NORMAL | | omr-s-att | Not Impacted | M | NORMAL |
| | | | | | | | | |
| omr-m-bw | Not Impacted | M | NORMAL | | omr-m-bw | Not Impacted | M | NORMAL |
skipping to change at page 53, line 8 skipping to change at page 53, line 8
7.1. RFC4585 - RTP/AVPF 7.1. RFC4585 - RTP/AVPF
[RFC4585] defines an extension to the Audio-visual Profile (AVP) that [RFC4585] defines an extension to the Audio-visual Profile (AVP) that
enables receivers to provide, statistically, more immediate feedback enables receivers to provide, statistically, more immediate feedback
to the senders and thus allows for short-term adaptation and to the senders and thus allows for short-term adaptation and
efficient feedback-based repair mechanisms to be implemented. efficient feedback-based repair mechanisms to be implemented.
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
| ack rpsi | The attribute value must | M | IDENTICAL-PER-PT | | ack rpsi | The attribute value MUST | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ack app | Feedback parameters must | M | SPECIAL | | ack app | Feedback parameters MUST | M | SPECIAL |
| | be handled in the app | | | | | be handled in the app | | |
| | specific way when | | | | | specific way when | | |
| | multiplexed | | | | | multiplexed | | |
| | | | | | | | | |
| nack | The attribute value must | M | IDENTICAL-PER-PT | | nack | The attribute value MUST | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack pli | The attribute value must | M | IDENTICAL-PER-PT | | nack pli | The attribute value MUST | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack sli | The attribute value must | M | IDENTICAL-PER-PT | | nack sli | The attribute value MUST | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack | The attribute value must | M | IDENTICAL-PER-PT | | nack | The attribute value MUST | M | IDENTICAL-PER-PT |
| rpsi | be same for a given codec | | | | rpsi | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack app | Feedback parameters must | M | SPECIAL | | nack app | Feedback parameters MUST | M | SPECIAL |
| | be handled in the app | | | | | be handled in the app | | |
| | specific way when | | | | | specific way when | | |
| | multiplexed | | | | | multiplexed | | |
| | | | | | | | | |
| trr-int | The attribute value must | M | IDENTICAL-PER-PT | | trr-int | The attribute value MUST | M | IDENTICAL-PER-PT |
| | be same for a given codec | | | | | be same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+----------+----------------------------+-------+-------------------+ +----------+----------------------------+-------+-------------------+
RFC4585 Attribute Analysis RFC4585 Attribute Analysis
7.2. RFC5104 - Codec Control Messages in AVPF 7.2. RFC5104 - Codec Control Messages in AVPF
[RFC5104] specifies a few extensions to the messages defined in the [RFC5104] specifies a few extensions to the messages defined in the
Audio-Visual Profile with Feedback (AVPF). They are helpful Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls. in smaller multicast environments and point-to-point calls.
+------+--------------------------------+-------+-------------------+ +------+--------------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+------+--------------------------------+-------+-------------------+ +------+--------------------------------+-------+-------------------+
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER-PT |
| | same for a given codec | | | | | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+------+--------------------------------+-------+-------------------+ +------+--------------------------------+-------+-------------------+
RFC5104 Attribute Analysis RFC5104 Attribute Analysis
7.3. RFC6285 - Unicast-Based RAMS 7.3. RFC6285 - Unicast-Based RAMS
[RFC6285] describes a method using the existing RTP and RTP Control [RFC6285] describes a method using the existing RTP and RTP Control
skipping to change at page 54, line 30 skipping to change at page 54, line 30
this method, an auxiliary unicast RTP session carrying the Reference this method, an auxiliary unicast RTP session carrying the Reference
Information to the receiver precedes or accompanies the multicast Information to the receiver precedes or accompanies the multicast
stream. This unicast RTP flow can be transmitted at a faster than stream. This unicast RTP flow can be transmitted at a faster than
natural bitrate to further accelerate the acquisition. The natural bitrate to further accelerate the acquisition. The
motivating use case for this capability is multicast applications motivating use case for this capability is multicast applications
that carry real-time compressed audio and video. that carry real-time compressed audio and video.
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
| nack | The attribute value must be | M | IDENTICAL-PER-PT | | nack | The attribute value MUST be | M | IDENTICAL-PER-PT |
| rai | same for a given codec | | | | rai | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+-------+-------------------------------+-------+-------------------+ +-------+-------------------------------+-------+-------------------+
RFC6285 Attribute Analysis RFC6285 Attribute Analysis
7.4. RFC6679 - ECN for RTP over UDP/IP 7.4. RFC6679 - ECN for RTP over UDP/IP
[RFC6679] specifies how Explicit Congestion Notification (ECN) can be [RFC6679] specifies how Explicit Congestion Notification (ECN) can be
skipping to change at page 55, line 39 skipping to change at page 55, line 39
reports, and this may allow feedback implosion. [RFC6642] memo reports, and this may allow feedback implosion. [RFC6642] memo
discusses these cases and defines a new RTCP Third-Party Loss Report discusses these cases and defines a new RTCP Third-Party Loss Report
that can be used to inform receivers that the feedback target is that can be used to inform receivers that the feedback target is
aware of some loss event, allowing them to suppress feedback. aware of some loss event, allowing them to suppress feedback.
Associated Session Description Protocol (SDP) signaling is also Associated Session Description Protocol (SDP) signaling is also
defined. defined.
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| nack | The attribute value must be | M | IDENTICAL-PER-PT | | nack | The attribute value MUST be | M | IDENTICAL-PER-PT |
| tllei | same for a given codec | | | | tllei | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| nack | The attribute value must be | M | IDENTICAL-PER-PT | | nack | The attribute value MUST be | M | IDENTICAL-PER-PT |
| pslei | same for a given codec | | | | pslei | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
RFC6642 Attribute Analysis RFC6642 Attribute Analysis
7.6. RFC5104 - Codec Control Messages in AVPF 7.6. RFC5104 - Codec Control Messages in AVPF
[RFC5104] specifies a few extensions to the messages defined in the [RFC5104] specifies a few extensions to the messages defined in the
Audio-Visual Profile with Feedback (AVPF). They are helpful Audio-Visual Profile with Feedback (AVPF). They are helpful
primarily in conversational multimedia scenarios where centralized primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use. However, some are also usable multipoint functionalities are in use. However, some are also usable
in smaller multicast environments and point-to-point calls. in smaller multicast environments and point-to-point calls.
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER-PT |
| fir | same for a given codec | | | | fir | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER-PT |
| tmmbr | same for a given codec | | | | tmmbr | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER-PT |
| tstr | same for a given codec | | | | tstr | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| ccm | The attribute value must be | M | IDENTICAL-PER-PT | | ccm | The attribute value MUST be | M | IDENTICAL-PER-PT |
| vbcm | same for a given codec | | | | vbcm | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
RFC5104 Attribute Analysis RFC5104 Attribute Analysis
8. group Attribute Analysis 8. group Attribute Analysis
This section analyzes SDP "group" attribute semantics. This section analyzes SDP "group" attribute semantics.
skipping to change at page 58, line 39 skipping to change at page 58, line 39
[RFC5583] defines semantics that allow for signaling the decoding [RFC5583] defines semantics that allow for signaling the decoding
dependency of different media descriptions with the same media type dependency of different media descriptions with the same media type
in the Session Description Protocol (SDP). This is required, for in the Session Description Protocol (SDP). This is required, for
example, if media data is separated and transported in different example, if media data is separated and transported in different
network streams as a result of the use of a layered or multiple network streams as a result of the use of a layered or multiple
descriptive media coding process. descriptive media coding process.
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
| depend | The attribute value must be | M | IDENTICAL-PER-PT | | depend | The attribute value MUST be | M | IDENTICAL-PER-PT |
| lay | same for a given codec | | | | lay | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
| depend | The attribute value must be | M | IDENTICAL-PER-PT | | depend | The attribute value MUST be | M | IDENTICAL-PER-PT |
| mdc | same for a given codec | | | | mdc | same for a given codec | | |
| | configuration | | | | | configuration | | |
| | | | | | | | | |
+--------+------------------------------+-------+-------------------+ +--------+------------------------------+-------+-------------------+
RFC5583 Attribute Analysis RFC5583 Attribute Analysis
8.6. RFC7104 - Duplication Grouping Semantics in the SDP 8.6. RFC7104 - Duplication Grouping Semantics in the SDP
[RFC7104] defines the semantics for grouping redundant streams in the [RFC7104] defines the semantics for grouping redundant streams in the
skipping to change at page 63, line 43 skipping to change at page 63, line 43
stream components, supported by each side. The attribute stream components, supported by each side. The attribute
("a=acap") defines how to list an attribute name and its ("a=acap") defines how to list an attribute name and its
associated value (if any) as a capability. The attribute associated value (if any) as a capability. The attribute
("a=tcap") defines how to list transport protocols (e.g., "RTP/ ("a=tcap") defines how to list transport protocols (e.g., "RTP/
AVP") as capabilities. AVP") as capabilities.
o A set of potential configurations ("a=pcfg") provided by the o A set of potential configurations ("a=pcfg") provided by the
offerer to indicate whcich combination of those capabilities can offerer to indicate whcich combination of those capabilities can
be used for the session and its associated media stream be used for the session and its associated media stream
components. Potential configurations are not ready for use until components. Potential configurations are not ready for use until
fully negotiated. They provide an alternative that may be used, fully negotiated. They provide an alternative that MAY be used,
subject to SDP capability negotiation procedures. In particular subject to SDP capability negotiation procedures. In particular
the answerer may choose one of the potential configurations for the answerer MAY choose one of the potential configurations for
use as part of the current Offer/Answer exchange. use as part of the current Offer/Answer exchange.
o An actual configuration ("a=acfg") for the session and its o An actual configuration ("a=acfg") for the session and its
associated media stream components. The actual configuration associated media stream components. The actual configuration
identifies the potential configuration that was negotiated for identifies the potential configuration that was negotiated for
use. Use of an actual configuration does not require any further use. Use of an actual configuration does not require any further
negotiation. negotiation.
o A negotiation process that takes the current actual and the set of o A negotiation process that takes the current actual and the set of
potential configurations (combinations of capabilities) as input potential configurations (combinations of capabilities) as input
skipping to change at page 64, line 27 skipping to change at page 64, line 27
These recommendations are provided for the purposes of enabling the These recommendations are provided for the purposes of enabling the
Offerer to make sure that the generated potential configurations Offerer to make sure that the generated potential configurations
between the multiplexed streams can (easily) be negotiated to be between the multiplexed streams can (easily) be negotiated to be
consistent between those streams. In particular, the procedures aim consistent between those streams. In particular, the procedures aim
to simplify Answerer's procedure to choose potential configurations to simplify Answerer's procedure to choose potential configurations
that are consistent across all the multiplexed media descriptions. that are consistent across all the multiplexed media descriptions.
A potential configuration selects a set of attributes and parameters A potential configuration selects a set of attributes and parameters
that become part of the media description when negotiated. When that become part of the media description when negotiated. When
multiplexing media descriptions with potential configurations multiplexing media descriptions with potential configurations
specified, there may be a need for coordinating this selection specified, there MAY be a need for coordinating this selection
between multiplexed media descriptions ensuring right multiplexing between multiplexed media descriptions ensuring right multiplexing
behavior. behavior.
Although it is possible to analyze the various potential Although it is possible to analyze the various potential
configurations in multiplexed media descriptions to find combinations configurations in multiplexed media descriptions to find combinations
that satisfy such constraints, it can quickly become complicated to that satisfy such constraints, it can quickly become complicated to
do so. do so.
The procedures defined in [RFC5939] state that each potential The procedures defined in [RFC5939] state that each potential
configuration in the SDP has a unique configuration number, however configuration in the SDP has a unique configuration number, however
skipping to change at page 64, line 50 skipping to change at page 64, line 50
potential configurations across media descriptions in a given bundle potential configurations across media descriptions in a given bundle
group, we provide a simple rule for constructing potential group, we provide a simple rule for constructing potential
configurations configurations
o Let m-bundle be the set of media descriptions that form a given o Let m-bundle be the set of media descriptions that form a given
bundle . bundle .
o Let m-bundle-pcfg be the set of media descriptions in m-bundle o Let m-bundle-pcfg be the set of media descriptions in m-bundle
that include one or more potential configurations. that include one or more potential configurations.
o Each media description in m-bundle-pcfg must have at least one o Each media description in m-bundle-pcfg MUST have at least one
potential configuration with the same configuration number (e.g. potential configuration with the same configuration number (e.g.
"1"). "1").
o For each potential configuration with configuration number x in m- o For each potential configuration with configuration number x in m-
bundle-pcfg, the offerer MUST ensure that if the answerer chooses bundle-pcfg, the offerer MUST ensure that if the answerer chooses
configuration number x in each of the media descriptions in m- configuration number x in each of the media descriptions in m-
bundle-pcfg, then the resulting SDP will have all multiplexing bundle-pcfg, then the resulting SDP will have all multiplexing
constraints satisfied for those media descriptions. constraints satisfied for those media descriptions.
o Since it is nearly impossible to define a generic mechanism for o Since it is nearly impossible to define a generic mechanism for
skipping to change at page 66, line 49 skipping to change at page 66, line 49
[RFC6871] defines a new payload type ("pt") parameter to be used with [RFC6871] defines a new payload type ("pt") parameter to be used with
the potential, actual and latent configuration parameters. The the potential, actual and latent configuration parameters. The
parameter associates RTP payload type numbers with the referenced parameter associates RTP payload type numbers with the referenced
RTP-based media format capabilities ("a=rmcap") defined in [RFC6871] RTP-based media format capabilities ("a=rmcap") defined in [RFC6871]
and is appropriate only when the transport protocol uses RTP. This and is appropriate only when the transport protocol uses RTP. This
means that the same payload type number can be assigned as part of means that the same payload type number can be assigned as part of
potential or actual configurations in different media descriptions in potential or actual configurations in different media descriptions in
a bundle. There are rules for the usage of identical Payload Type a bundle. There are rules for the usage of identical Payload Type
values across multiplexed "m=" lines as described in values across multiplexed "m=" lines as described in
[I-D.ietf-mmusic-sdp-bundle-negotiation], which must be followed here [I-D.ietf-mmusic-sdp-bundle-negotiation], which MUST be followed here
as well. As described in Section 14.2.1, the use of identical as well. As described in Section 14.2.1, the use of identical
configuration numbers for compatible configurations in different configuration numbers for compatible configurations in different
media descriptions that are part of the bundle provides a way to media descriptions that are part of the bundle provides a way to
ensure that the answerer can easily pick compatible configurations ensure that the answerer can easily pick compatible configurations
here as well. here as well.
14.3.1.1. Example: Attribute Capability Under Shared Payload Type 14.3.1.1. Example: Attribute Capability Under Shared Payload Type
The attributes (a=rmcap, a=mfcap) follow the above recommendations The attributes (a=rmcap, a=mfcap) follow the above recommendations
under multiplexing. under multiplexing.
skipping to change at page 67, line 44 skipping to change at page 67, line 44
a=rmcap:4 audio AMR/8000/1 a=rmcap:4 audio AMR/8000/1
a=rmcap:5 audio OPUS/48000/2 a=rmcap:5 audio OPUS/48000/2
a=mfcap:5 minptime=40 a=mfcap:5 minptime=40
a=mfcap:4 mode-change-capability=1 a=mfcap:4 mode-change-capability=1
a=pcfg:1 m=4 pt=4:97 a=pcfg:1 m=4 pt=4:97
a=pcfg:4 m=5 pt=5:101 a=pcfg:4 m=5 pt=5:101
In the example above, the potential configuration number "1" is In the example above, the potential configuration number "1" is
repeated when referring to media and media format capability used for repeated when referring to media and media format capability used for
the Payload Type 97. This implies that both the media capability 2 the Payload Type 97. This implies that both the media capability 2
and 4 along with their media format capabilities must refer to the and 4 along with their media format capabilities MUST refer to the
same codec configuration, as per the definition of IDENTICAL-PER-PT. same codec configuration, as per the definition of IDENTICAL-PER-PT.
14.3.2. Recommendation: Dealing with Latent Configurations 14.3.2. Recommendation: Dealing with Latent Configurations
[RFC6871] adds the notion of a latent configurations, which provides [RFC6871] adds the notion of a latent configurations, which provides
configuration information that may be used to guide a subsequent configuration information that may be used to guide a subsequent
offer/exchange, e.g. by adding another media stream or use offer/exchange, e.g. by adding another media stream or use
alternative codec combinations not currently offered. Latent alternative codec combinations not currently offered. Latent
configurations have configuration numbers which cannot overlap with configurations have configuration numbers which cannot overlap with
the potential configuration numbers [RFC6871]. Supported the potential configuration numbers [RFC6871]. Supported
skipping to change at page 69, line 24 skipping to change at page 69, line 24
| IDENTICAL-PER-PT | RFCXXXX | | IDENTICAL-PER-PT | RFCXXXX |
| SPECIAL | RFCXXXX | | SPECIAL | RFCXXXX |
| TBD | RFCXXXX | | TBD | RFCXXXX |
+-------------------------+-----------+ +-------------------------+-----------+
Further entries may be registered on a first-come first-serve basis. Further entries may be registered on a first-come first-serve basis.
Each registration needs to indicate the multiplexing category value Each registration needs to indicate the multiplexing category value
to be added to the "Multiplexing Categories" subregistry as defined to be added to the "Multiplexing Categories" subregistry as defined
in this section. in this section.
Such a registration must also indicate the applicability of the newly Such a registration MUST also indicate the applicability of the newly
defined multiplexing category value to various subregistries defined defined multiplexing category value to various subregistries defined
at "Session Description Protocol (SDP) Parameters". at "Session Description Protocol (SDP) Parameters".
The general registration procedures of [RFC4566] apply. The general registration procedures of [RFC4566] apply.
15.2. 'Mux Category' column for subregistries 15.2. 'Mux Category' column for subregistries
Each sub-section identifies a subregistry in the "Session Description Each sub-section identifies a subregistry in the "Session Description
Protocol (SDP) Parameters" registry. The tables list the column that Protocol (SDP) Parameters" registry. The tables list the column that
identifies the SDP attribute name/Token/Value from the corresponding identifies the SDP attribute name/Token/Value from the corresponding
skipping to change at page 73, line 14 skipping to change at page 73, line 14
| T38FaxTranscodingJBIG | NORMAL | | T38FaxTranscodingJBIG | NORMAL |
| T38FaxRateManagement | NORMAL | | T38FaxRateManagement | NORMAL |
| T38FaxMaxBuffer | NORMAL | | T38FaxMaxBuffer | NORMAL |
| T38FaxMaxDatagram | NORMAL | | T38FaxMaxDatagram | NORMAL |
| T38FaxUdpEC | NORMAL | | T38FaxUdpEC | NORMAL |
| maxptime | IDENTICAL-PER-PT | | maxptime | IDENTICAL-PER-PT |
| des | NOT RECOMMENDED | | des | NOT RECOMMENDED |
| curr | NOT RECOMMENDED | | curr | NOT RECOMMENDED |
| conf | NOT RECOMMENDED | | conf | NOT RECOMMENDED |
| mid | NORMAL | | mid | NORMAL |
| rtcp | IDENTICAL | | rtcp | TRANSPORT |
| rtcp-fb | IDENTICAL-PER-PT | | rtcp-fb | IDENTICAL-PER-PT |
| label | NORMAL | | label | NORMAL |
| T38VendorInfo | NORMAL | | T38VendorInfo | NORMAL |
| crypto | TRANSPORT | | crypto | TRANSPORT |
| eecid | NOT RECOMMENDED | | eecid | NOT RECOMMENDED |
| aalType | NOT RECOMMENDED | | aalType | NOT RECOMMENDED |
| capability | NOT RECOMMENDED | | capability | NOT RECOMMENDED |
| qosClass | NOT RECOMMENDED | | qosClass | NOT RECOMMENDED |
| bcob | NOT RECOMMENDED | | bcob | NOT RECOMMENDED |
| stc | NOT RECOMMENDED | | stc | NOT RECOMMENDED |
skipping to change at page 81, line 37 skipping to change at page 81, line 37
Perkins(5.7,5.8,5.9,5.58), Magnus Perkins(5.7,5.8,5.9,5.58), Magnus
Westerlund(5.2,5.3,5.9,5.27,5.47,6.1,6.2,6.3,8.3,7), Roni Westerlund(5.2,5.3,5.9,5.27,5.47,6.1,6.2,6.3,8.3,7), Roni
Evens(5.12,5.27,8.4), Subha Dhesikan(5.6,10), Dan Evens(5.12,5.27,8.4), Subha Dhesikan(5.6,10), Dan
Wing(5.7,5.12,5.35,5.39,5.45), Cullen Jennings (5.40), Ali C Wing(5.7,5.12,5.35,5.39,5.45), Cullen Jennings (5.40), Ali C
Begen(5.1,5.20,5.22,5.25,5.38,7.3,8.2,8.4,8.6,9.2,13.1), Bo Burman Begen(5.1,5.20,5.22,5.25,5.38,7.3,8.2,8.4,8.6,9.2,13.1), Bo Burman
(7.2,7.6), Charles Eckel(5.15,5.27,5.28,9.1,8.5), Paul Kyzivat(5.24), (7.2,7.6), Charles Eckel(5.15,5.27,5.28,9.1,8.5), Paul Kyzivat(5.24),
Ian Johansson(5.15), Saravanan Shanmugham(5.11), Paul E Jones(5.30), Ian Johansson(5.15), Saravanan Shanmugham(5.11), Paul E Jones(5.30),
Rajesh Kumar(5.48), Jonathan Lennox(5.36,5,15,9.1,11.1), Mo Rajesh Kumar(5.48), Jonathan Lennox(5.36,5,15,9.1,11.1), Mo
Zanaty(5.4,5.5,5.23,8.1,8.3,8.5,12.1), Christian Huitema (5.14), Qin Zanaty(5.4,5.5,5.23,8.1,8.3,8.5,12.1), Christian Huitema (5.14), Qin
Wu (5.47 PM-Dir review), Hans Stokking(5.43,5.16), Christian Groves Wu (5.47 PM-Dir review), Hans Stokking(5.43,5.16), Christian Groves
(5.48,5.55) (5.48,5.55), Thomas Stach.
18. Change Log 18. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing] [RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-ietf-mmusic-sdp-mux-attributes-05 Changes from draft-ietf-mmusic-sdp-mux-attributes-06
o Incorporated last call review comments from Thomas Stach and Ari
Keranen.
o Fixed more nits to prep for the LastCall.
Changes from draft-ietf-mmusic-sdp-mux-attributes-05
o Incorporated review comments from Christian Grooves and Ari o Incorporated review comments from Christian Grooves and Ari
Keranen. Keranen.
o Fixed more nits to prep for the LastCall. o Fixed more nits to prep for the LastCall.
Changes from draft-ietf-mmusic-sdp-mux-attributes-04 Changes from draft-ietf-mmusic-sdp-mux-attributes-04
o Fixed minor nits overall. o Fixed minor nits overall.
o Updated Acknowledgement Sections o Updated Acknowledgement Sections
skipping to change at page 84, line 9 skipping to change at page 84, line 18
o Updated IANA Consideration Section. o Updated IANA Consideration Section.
Changes from draft-nandakumar-mmusic-mux-attributes-00 Changes from draft-nandakumar-mmusic-mux-attributes-00
o Added new section for dealing with FEC payload types. o Added new section for dealing with FEC payload types.
19. References 19. References
19.1. Normative References 19.1. Normative References
[I-D.ietf-mmusic-sdp-bundle-negotiation]
Holmberg, C., Alvestrand, H., and C. Jennings,
"Negotiating Media Multiplexing Using the Session
Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-
negotiation-12 (work in progress), October 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
19.2. Informative References 19.2. Informative References
[H.248.15] [H.248.15]
"Gateway control protocol: SDP H.248 package attribute", "Gateway control protocol: SDP H.248 package attribute",
<http://www.itu.int/rec/T-REC-H.248.15>. <http://www.itu.int/rec/T-REC-H.248.15>.
[I-D.ietf-mmusic-sdp-bundle-negotiation]
Holmberg, C., Alvestrand, H., and C. Jennings,
"Negotiating Media Multiplexing Using the Session
Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-
negotiation-12 (work in progress), October 2014.
[I.D-draft-ietf-dart-dscp-rtp] [I.D-draft-ietf-dart-dscp-rtp]
Black, D. and P. Jones, "The Session Description Protocol Black, D. and P. Jones, "The Session Description Protocol
(SDP) Content Attribute", draft-ietf-dart-dscp-rtp-07 (SDP) Content Attribute", draft-ietf-dart-dscp-rtp-07
(work in progress), September 2014. (work in progress), September 2014.
[IANA] "Session Description Protocol (SDP) Parameters", [IANA] "Session Description Protocol (SDP) Parameters",
<http://www.iana.org/assignments/sdp-parameters/ <http://www.iana.org/assignments/sdp-parameters/
sdp-parameters.xml>. sdp-parameters.xml>.
[Q.1970] "Q.1970 : BICC IP bearer control protocol", [Q.1970] "Q.1970 : BICC IP bearer control protocol",
 End of changes. 77 change blocks. 
98 lines changed or deleted 109 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/