| 1 |
<pre>Internet Engineering Task Force (IETF) F. Andreasen |
| 2 |
Request for Comments: 5939 Cisco Systems |
| 3 |
Category: Standards Track September 2010 |
| 4 |
ISSN: 2070-1721 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">Session Description Protocol (SDP) Capability Negotiation</span> |
| 8 |
|
| 9 |
Abstract |
| 10 |
|
| 11 |
The Session Description Protocol (SDP) was intended to describe |
| 12 |
multimedia sessions for the purposes of session announcement, session |
| 13 |
invitation, and other forms of multimedia session initiation. SDP |
| 14 |
was not intended to provide capability indication or capability |
| 15 |
negotiation; however, over the years, SDP has seen widespread |
| 16 |
adoption and as a result it has been gradually extended to provide |
| 17 |
limited support for these, notably in the form of the offer/answer |
| 18 |
model defined in <a href="./rfc3264">RFC 3264</a>. SDP does not define how to negotiate one |
| 19 |
or more alternative transport protocols (e.g., RTP profiles) or |
| 20 |
attributes. This makes it difficult to deploy new RTP profiles such |
| 21 |
as Secure RTP or RTP with RTCP-based feedback, negotiate use of |
| 22 |
different security keying mechanisms, etc. It also presents problems |
| 23 |
for some forms of media negotiation. |
| 24 |
|
| 25 |
The purpose of this document is to address these shortcomings by |
| 26 |
extending SDP with capability negotiation parameters and associated |
| 27 |
offer/answer procedures to use those parameters in a backwards |
| 28 |
compatible manner. |
| 29 |
|
| 30 |
The document defines a general SDP Capability Negotiation framework. |
| 31 |
It also specifies how to provide attributes and transport protocols |
| 32 |
as capabilities and negotiate them using the framework. Extensions |
| 33 |
for other types of capabilities (e.g., media types and media formats) |
| 34 |
may be provided in other documents. |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Andreasen Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 55 |
|
| 56 |
|
| 57 |
Status of This Memo |
| 58 |
|
| 59 |
This is an Internet Standards Track document. |
| 60 |
|
| 61 |
This document is a product of the Internet Engineering Task Force |
| 62 |
(IETF). It represents the consensus of the IETF community. It has |
| 63 |
received public review and has been approved for publication by the |
| 64 |
Internet Engineering Steering Group (IESG). Further information on |
| 65 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 66 |
|
| 67 |
Information about the current status of this document, any errata, |
| 68 |
and how to provide feedback on it may be obtained at |
| 69 |
<a href="http://www.rfc-editor.org/info/rfc5939">http://www.rfc-editor.org/info/rfc5939</a>. |
| 70 |
|
| 71 |
Copyright Notice |
| 72 |
|
| 73 |
Copyright (c) 2010 IETF Trust and the persons identified as the |
| 74 |
document authors. All rights reserved. |
| 75 |
|
| 76 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 77 |
Provisions Relating to IETF Documents |
| 78 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 79 |
publication of this document. Please review these documents |
| 80 |
carefully, as they describe your rights and restrictions with respect |
| 81 |
to this document. Code Components extracted from this document must |
| 82 |
include Simplified BSD License text as described in Section 4.e of |
| 83 |
the Trust Legal Provisions and are provided without warranty as |
| 84 |
described in the Simplified BSD License. |
| 85 |
|
| 86 |
This document may contain material from IETF Documents or IETF |
| 87 |
Contributions published or made publicly available before November |
| 88 |
10, 2008. The person(s) controlling the copyright in some of this |
| 89 |
material may not have granted the IETF Trust the right to allow |
| 90 |
modifications of such material outside the IETF Standards Process. |
| 91 |
Without obtaining an adequate license from the person(s) controlling |
| 92 |
the copyright in such materials, this document may not be modified |
| 93 |
outside the IETF Standards Process, and derivative works of it may |
| 94 |
not be created outside the IETF Standards Process, except to format |
| 95 |
it for publication as an RFC or to translate it into languages other |
| 96 |
than English. |
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Andreasen Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a> |
| 116 |
<a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-7">7</a> |
| 117 |
<a href="#section-3">3</a>. SDP Capability Negotiation Solution .............................<a href="#page-7">7</a> |
| 118 |
<a href="#section-3.1">3.1</a>. SDP Capability Negotiation Model ...........................<a href="#page-7">7</a> |
| 119 |
<a href="#section-3.2">3.2</a>. Solution Overview .........................................<a href="#page-10">10</a> |
| 120 |
<a href="#section-3.3">3.3</a>. Version and Extension Indication Attributes ...............<a href="#page-14">14</a> |
| 121 |
<a href="#section-3.4">3.4</a>. Capability Attributes .....................................<a href="#page-17">17</a> |
| 122 |
<a href="#section-3.5">3.5</a>. Configuration Attributes ..................................<a href="#page-22">22</a> |
| 123 |
<a href="#section-3.6">3.6</a>. Offer/Answer Model Extensions .............................<a href="#page-32">32</a> |
| 124 |
<a href="#section-3.7">3.7</a>. Interactions with ICE .....................................<a href="#page-45">45</a> |
| 125 |
<a href="#section-3.8">3.8</a>. Interactions with SIP Option Tags .........................<a href="#page-47">47</a> |
| 126 |
<a href="#section-3.9">3.9</a>. Processing Media before Answer ............................<a href="#page-48">48</a> |
| 127 |
<a href="#section-3.10">3.10</a>. Indicating Bandwidth Usage ...............................<a href="#page-49">49</a> |
| 128 |
<a href="#section-3.11">3.11</a>. Dealing with Large Number of Potential Configurations ....<a href="#page-50">50</a> |
| 129 |
<a href="#section-3.12">3.12</a>. SDP Capability Negotiation and Intermediaries ............<a href="#page-51">51</a> |
| 130 |
<a href="#section-3.13">3.13</a>. Considerations for Specific Attribute Capabilities .......<a href="#page-52">52</a> |
| 131 |
<a href="#section-3.14">3.14</a>. Relationship to <a href="./rfc3407">RFC 3407</a> .................................<a href="#page-54">54</a> |
| 132 |
<a href="#section-4">4</a>. Examples .......................................................<a href="#page-54">54</a> |
| 133 |
<a href="#section-4.1">4.1</a>. Multiple Transport Protocols ..............................<a href="#page-54">54</a> |
| 134 |
<a href="#section-4.2">4.2</a>. DTLS-SRTP or SRTP with Media-Level Security Descriptions...<a href="#page-58">58</a> |
| 135 |
4.3. Best-Effort SRTP with Session-Level MIKEY and Media-Level |
| 136 |
Security Descriptions .....................................<a href="#page-61">61</a> |
| 137 |
4.4. SRTP with Session-Level MIKEY and Media-Level Security |
| 138 |
Descriptions as Alternatives ..............................<a href="#page-66">66</a> |
| 139 |
<a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-69">69</a> |
| 140 |
<a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-72">72</a> |
| 141 |
<a href="#section-6.1">6.1</a>. New SDP Attributes ........................................<a href="#page-72">72</a> |
| 142 |
<a href="#section-6.2">6.2</a>. New SDP Capability Negotiation Option Tag Registry ........<a href="#page-73">73</a> |
| 143 |
6.3. New SDP Capability Negotiation Potential |
| 144 |
Configuration Parameter Registry ..........................<a href="#page-74">74</a> |
| 145 |
<a href="#section-7">7</a>. Acknowledgments ................................................<a href="#page-74">74</a> |
| 146 |
<a href="#section-8">8</a>. References .....................................................<a href="#page-75">75</a> |
| 147 |
<a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-75">75</a> |
| 148 |
<a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-75">75</a> |
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Andreasen Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 170 |
|
| 171 |
The Session Description Protocol (SDP) was intended to describe |
| 172 |
multimedia sessions for the purposes of session announcement, session |
| 173 |
invitation, and other forms of multimedia session initiation. An SDP |
| 174 |
session description contains one or more media stream descriptions |
| 175 |
with information such as IP address and port, type of media stream |
| 176 |
(e.g., audio or video), transport protocol (possibly including |
| 177 |
profile information, e.g., RTP/AVP or RTP/SAVP), media formats (e.g., |
| 178 |
codecs), and various other session and media stream parameters that |
| 179 |
define the session. |
| 180 |
|
| 181 |
Simply providing media stream descriptions is sufficient for session |
| 182 |
announcements for a broadcast application, where the media stream |
| 183 |
parameters are fixed for all participants. When a participant wants |
| 184 |
to join the session, he obtains the session announcement and uses the |
| 185 |
media descriptions provided, e.g., joins a multicast group and |
| 186 |
receives media packets in the encoding format specified. If the |
| 187 |
media stream description is not supported by the participant, he is |
| 188 |
unable to receive the media. |
| 189 |
|
| 190 |
Such restrictions are not generally acceptable to multimedia session |
| 191 |
invitations, where two or more entities attempt to establish a media |
| 192 |
session, that uses a set of media stream parameters acceptable to all |
| 193 |
participants. First of all, each entity must inform the other of its |
| 194 |
receive address, and secondly, the entities need to agree on the |
| 195 |
media stream parameters to use for the session, e.g., transport |
| 196 |
protocols and codecs. To solve this, <a href="./rfc3264">RFC 3264</a> [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>] defined the |
| 197 |
offer/answer model, whereby an offerer constructs an offer SDP |
| 198 |
session description that lists the media streams, codecs, and other |
| 199 |
SDP parameters that the offerer is willing to use. This offer |
| 200 |
session description is sent to the answerer, which chooses from among |
| 201 |
the media streams, codecs and other session description parameters |
| 202 |
provided, and generates an answer session description with his |
| 203 |
parameters, based on that choice. The answer session description is |
| 204 |
sent back to the offerer thereby completing the session negotiation |
| 205 |
and enabling the establishment of the negotiated media streams. |
| 206 |
|
| 207 |
Taking a step back, we can make a distinction between the |
| 208 |
capabilities supported by each participant, the way in which those |
| 209 |
capabilities can be supported, and the parameters that can actually |
| 210 |
be used for the session. More generally, we can say that we have the |
| 211 |
following: |
| 212 |
|
| 213 |
o A set of capabilities for the session and its associated media |
| 214 |
stream components, supported by each side. The capability |
| 215 |
indications by themselves do not imply a commitment to use the |
| 216 |
capabilities in the session. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Andreasen Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 223 |
|
| 224 |
|
| 225 |
Capabilities can, for example, be that the "RTP/SAVP" profile is |
| 226 |
supported, that the "PCMU" (Pulse Code Modulation mu-law) codec is |
| 227 |
supported, or that the "crypto" attribute is supported with a |
| 228 |
particular value. |
| 229 |
|
| 230 |
o A set of potential configurations indicating which combinations of |
| 231 |
those capabilities can be used for the session and its associated |
| 232 |
media stream components. Potential configurations are not ready |
| 233 |
for use. Instead, they provide an alternative that may be used, |
| 234 |
subject to further negotiation. |
| 235 |
|
| 236 |
A potential configuration can, for example, indicate that the |
| 237 |
"PCMU" codec and the "RTP/SAVP" transport protocol are not only |
| 238 |
supported (i.e., listed as capabilities), but they are offered for |
| 239 |
potential use in the session. |
| 240 |
|
| 241 |
o An actual configuration for the session and its associated media |
| 242 |
stream components, that specifies which combinations of session |
| 243 |
parameters and media stream components can be used currently and |
| 244 |
with what parameters. Use of an actual configuration does not |
| 245 |
require any further negotiation. |
| 246 |
|
| 247 |
An actual configuration can, for example, be that the "PCMU" codec |
| 248 |
and the "RTP/SAVP" transport protocol are offered for use |
| 249 |
currently. |
| 250 |
|
| 251 |
o A negotiation process that takes the set of actual and potential |
| 252 |
configurations (combinations of capabilities) as input and |
| 253 |
provides the negotiated actual configurations as output. |
| 254 |
|
| 255 |
SDP by itself was designed to provide only one of these, namely |
| 256 |
listing of the actual configurations; however, over the years, use of |
| 257 |
SDP has been extended beyond its original scope. Of particular |
| 258 |
importance are the session negotiation semantics that were defined by |
| 259 |
the offer/answer model in <a href="./rfc3264">RFC 3264</a>. In this model, both the offer |
| 260 |
and the answer contain actual configurations; separate capabilities |
| 261 |
and potential configurations are not supported. |
| 262 |
|
| 263 |
Other relevant extensions have been defined as well. <a href="./rfc3407">RFC 3407</a> |
| 264 |
[<a href="./rfc3407" title=""Session Description Protocol (SDP) Simple Capability Declaration"">RFC3407</a>] defined simple capability declarations, which extends SDP |
| 265 |
with a simple and limited set of capability descriptions. Grouping |
| 266 |
of media lines, which defines how media lines in SDP can have other |
| 267 |
semantics than the traditional "simultaneous media streams" |
| 268 |
semantics, was defined in <a href="./rfc5888">RFC 5888</a> [<a href="./rfc5888" title=""The Session Description Protocol (SDP) Grouping Framework"">RFC5888</a>], etc. |
| 269 |
|
| 270 |
Each of these extensions was designed to solve a specific limitation |
| 271 |
of SDP. Since SDP had already been stretched beyond its original |
| 272 |
intent, a more comprehensive capability declaration and negotiation |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Andreasen Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 279 |
|
| 280 |
|
| 281 |
process was intentionally not defined. Instead, work on a "next |
| 282 |
generation" of a protocol to provide session description and |
| 283 |
capability negotiation was initiated [<a href="#ref-SDPng" title=""Session Description and Capability Negotiation"">SDPng</a>]. SDPng defined a |
| 284 |
comprehensive capability negotiation framework and protocol that was |
| 285 |
not bound by existing SDP constraints. SDPng was not designed to be |
| 286 |
backwards compatible with existing SDP and hence required both sides |
| 287 |
to support it, with a graceful fallback to legacy operation when |
| 288 |
needed. This, combined with lack of ubiquitous multipart MIME |
| 289 |
support in the protocols that would carry SDP or SDPng, made it |
| 290 |
challenging to migrate towards SDPng. In practice, SDPng has not |
| 291 |
gained traction and, as of the time of publication of this document, |
| 292 |
work on SDPng has stopped. Existing real-time multimedia |
| 293 |
communication protocols such as SIP, Real Time Streaming Protocol |
| 294 |
(RTSP), Megaco, and Media Gateway Control Protocol (MGCP) continue to |
| 295 |
use SDP. However, SDP does not address an increasingly important |
| 296 |
problem: the ability to negotiate one or more alternative transport |
| 297 |
protocols (e.g., RTP profiles) and associated parameters (e.g., SDP |
| 298 |
attributes). This makes it difficult to deploy new RTP profiles such |
| 299 |
as Secure RTP (SRTP) [<a href="./rfc3711" title=""The Secure Real-time Transport Protocol (SRTP)"">RFC3711</a>], RTP with RTCP-based feedback |
| 300 |
[<a href="./rfc4585" title=""Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)"">RFC4585</a>], etc. The problem is exacerbated by the fact that RTP |
| 301 |
profiles are defined independently. When a new profile is defined |
| 302 |
and N other profiles already exist, there is a potential need for |
| 303 |
defining N additional profiles, since profiles cannot be combined |
| 304 |
automatically. For example, in order to support the plain and Secure |
| 305 |
RTP version of RTP with and without RTCP-based feedback, four |
| 306 |
separate profiles (and hence profile definitions) are needed: RTP/AVP |
| 307 |
[<a href="./rfc3551" title=""RTP Profile for Audio and Video Conferences with Minimal Control"">RFC3551</a>], RTP/SAVP [<a href="./rfc3711" title=""The Secure Real-time Transport Protocol (SRTP)"">RFC3711</a>], RTP/AVPF [<a href="./rfc4585" title=""Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)"">RFC4585</a>], and RTP/SAVPF |
| 308 |
[<a href="./rfc5124" title=""Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)"">RFC5124</a>]. In addition to the pressing profile negotiation problem, |
| 309 |
other important real-life limitations have been found as well. |
| 310 |
Keying material and other parameters, for example, need to be |
| 311 |
negotiated with some of the transport protocols, but not others. |
| 312 |
Similarly, some media formats and types of media streams need to |
| 313 |
negotiate a variety of different parameters. |
| 314 |
|
| 315 |
The purpose of this document is to define a mechanism that enables |
| 316 |
SDP to provide limited support for indicating capabilities and their |
| 317 |
associated potential configurations, and negotiate the use of those |
| 318 |
potential configurations as actual configurations. It is not the |
| 319 |
intent to provide a full-fledged capability indication and |
| 320 |
negotiation mechanism along the lines of SDPng or ITU-T H.245. |
| 321 |
Instead, the focus is on addressing a set of well-known real-life |
| 322 |
limitations. More specifically, the solution provided in this |
| 323 |
document provides a general SDP Capability Negotiation framework that |
| 324 |
is backwards compatible with existing SDP. It also defines |
| 325 |
specifically how to provide attributes and transport protocols as |
| 326 |
capabilities and negotiate them using the framework. Extensions for |
| 327 |
other types of capabilities (e.g., media types and formats) may be |
| 328 |
provided in other documents. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Andreasen Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 335 |
|
| 336 |
|
| 337 |
As mentioned above, SDP is used by several protocols, and hence the |
| 338 |
mechanism should be usable by all of these. One particularly |
| 339 |
important protocol for this problem is the Session Initiation |
| 340 |
Protocol (SIP) [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>]. SIP uses the offer/answer model [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>] |
| 341 |
(which is not specific to SIP) to negotiate sessions and hence the |
| 342 |
mechanism defined here provides the offer/answer procedures to use |
| 343 |
for the capability negotiation framework. |
| 344 |
|
| 345 |
The rest of the document is structured as follows. In <a href="#section-3">Section 3</a>, we |
| 346 |
present the SDP Capability Negotiation solution, which consists of |
| 347 |
new SDP attributes and associated offer/answer procedures. In |
| 348 |
<a href="#section-4">Section 4</a>, we provide examples illustrating its use. In <a href="#section-5">Section 5</a>, |
| 349 |
we provide the security considerations. |
| 350 |
|
| 351 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span> |
| 352 |
|
| 353 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 354 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 355 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 356 |
|
| 357 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. SDP Capability Negotiation Solution</span> |
| 358 |
|
| 359 |
In this section, we first present the conceptual model behind the SDP |
| 360 |
Capability Negotiation framework followed by an overview of the SDP |
| 361 |
Capability Negotiation solution. We then define new SDP attributes |
| 362 |
for the solution and provide its associated updated offer/answer |
| 363 |
procedures. |
| 364 |
|
| 365 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. SDP Capability Negotiation Model</span> |
| 366 |
|
| 367 |
Our model uses the concepts of |
| 368 |
|
| 369 |
o Capabilities |
| 370 |
|
| 371 |
o Potential Configurations |
| 372 |
|
| 373 |
o Actual Configurations |
| 374 |
|
| 375 |
o Negotiation Process |
| 376 |
|
| 377 |
as defined in <a href="#section-1">Section 1</a>. Conceptually, we want to offer not just the |
| 378 |
actual configuration SDP session description (which is done with the |
| 379 |
offer/answer model defined in [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]), but the actual |
| 380 |
configuration SDP session description as well as one or more |
| 381 |
alternative SDP session descriptions, i.e., potential configurations. |
| 382 |
The answerer must choose either the actual configuration or one of |
| 383 |
the potential configurations, and generate an answer SDP session |
| 384 |
description based on that. The offerer may need to perform |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Andreasen Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 391 |
|
| 392 |
|
| 393 |
processing on the answer, which depends on the offer that was chosen |
| 394 |
(actual or potential configuration). The answerer therefore informs |
| 395 |
the offerer which configuration the answerer chose. The process can |
| 396 |
be viewed *conceptually* as follows: |
| 397 |
|
| 398 |
Offerer Answerer |
| 399 |
======= ======== |
| 400 |
|
| 401 |
1) Generate offer with actual |
| 402 |
configuration and alternative |
| 403 |
potential configurations |
| 404 |
2) Send offer with all configurations |
| 405 |
|
| 406 |
+------------+ |
| 407 |
| SDP o1 | |
| 408 |
| (actual | |
| 409 |
| config | |
| 410 |
| |-+ Offer |
| 411 |
+------------+ | -----> 3) Process offered configurations |
| 412 |
| SDP o2 | in order of preference indicated |
| 413 |
| (potential | 4) Generate answer based on chosen |
| 414 |
| config 1) |-+ configuration (e.g., o2), and |
| 415 |
+------------+ | inform offerer which one was |
| 416 |
| SDP o3 | chosen |
| 417 |
| (potential | |
| 418 |
| config 2) |-+ |
| 419 |
+------------+ | |
| 420 |
| SDP ... | |
| 421 |
: : |
| 422 |
|
| 423 |
+------------+ |
| 424 |
| SDP a1 | |
| 425 |
Answer | (actual | |
| 426 |
<----- | config,o2)| |
| 427 |
| | |
| 428 |
5) Process answer based on +------------+ |
| 429 |
the configuration that was |
| 430 |
chosen (o2), as indicated in |
| 431 |
the answer |
| 432 |
|
| 433 |
The above illustrates the conceptual model: the actual solution uses |
| 434 |
a single SDP session description, which contains the actual |
| 435 |
configuration (as with existing SDP session descriptions and the |
| 436 |
offer/answer model defined in [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]) and several new attributes |
| 437 |
and associated procedures, that encode the capabilities and potential |
| 438 |
configurations. A more accurate depiction of the actual offer SDP |
| 439 |
session description is therefore as follows: |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Andreasen Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 447 |
|
| 448 |
|
| 449 |
+--------------------+ |
| 450 |
| SDP o1 | |
| 451 |
| (actual | |
| 452 |
| config | |
| 453 |
| | |
| 454 |
| +-------------+ | |
| 455 |
| | capability 1| | |
| 456 |
| | capability 2| | |
| 457 |
| | ... | | |
| 458 |
| +-------------+ | Offer |
| 459 |
| | -----> |
| 460 |
| +-------------+ | |
| 461 |
| | potential | | |
| 462 |
| | config 1 | | |
| 463 |
| | potential | | |
| 464 |
| | config 2 | | |
| 465 |
| | ... | | |
| 466 |
| +-------------+ | |
| 467 |
| | |
| 468 |
+--------------------+ |
| 469 |
|
| 470 |
The above structure is used for two reasons: |
| 471 |
|
| 472 |
o Backwards compatibility: As noted above, support for multipart |
| 473 |
MIME is not ubiquitous. By encoding both capabilities and |
| 474 |
potential configurations in SDP attributes, we can represent |
| 475 |
everything in a single SDP session description thereby avoiding |
| 476 |
any multipart MIME support issues. Furthermore, since unknown SDP |
| 477 |
attributes are ignored by the SDP recipient, we ensure that |
| 478 |
entities that do not support the framework simply perform the |
| 479 |
regular <a href="./rfc3264">RFC 3264</a> offer/answer procedures. This provides us with |
| 480 |
seamless backwards compatibility. |
| 481 |
|
| 482 |
o Message size efficiency: When we have multiple media streams, |
| 483 |
each of which may potentially use two or more different transport |
| 484 |
protocols with a variety of different associated parameters, the |
| 485 |
number of potential configurations can be large. If each possible |
| 486 |
alternative is represented as a complete SDP session description |
| 487 |
in an offer, we can easily end up with large messages. By |
| 488 |
providing a more compact encoding, we get more efficient message |
| 489 |
sizes. |
| 490 |
|
| 491 |
In the next section, we describe the exact structure and specific SDP |
| 492 |
parameters used to represent this. |
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Andreasen Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Solution Overview</span> |
| 506 |
|
| 507 |
The solution consists of the following: |
| 508 |
|
| 509 |
o Two new SDP attributes to support extensions to the framework |
| 510 |
itself as follows: |
| 511 |
|
| 512 |
o A new attribute ("a=csup") that lists the supported base |
| 513 |
(optionally) and any supported extension options to the |
| 514 |
framework. |
| 515 |
|
| 516 |
o A new attribute ("a=creq") that lists the extensions to the |
| 517 |
framework that are required to be supported by the entity |
| 518 |
receiving the SDP session description in order to do capability |
| 519 |
negotiation. |
| 520 |
|
| 521 |
o Two new SDP attributes used to express capabilities as follows |
| 522 |
(additional attributes can be defined as extensions): |
| 523 |
|
| 524 |
o A new attribute ("a=acap") that defines how to list an |
| 525 |
attribute name and its associated value (if any) as a |
| 526 |
capability. |
| 527 |
|
| 528 |
o A new attribute ("a=tcap") that defines how to list transport |
| 529 |
protocols (e.g., "RTP/AVP") as capabilities. |
| 530 |
|
| 531 |
o Two new SDP attributes to negotiate configurations as follows: |
| 532 |
|
| 533 |
o A new attribute ("a=pcfg") that lists potential configurations |
| 534 |
supported. This is done by reference to the capabilities from |
| 535 |
the SDP session description in question. Extension |
| 536 |
capabilities can be defined and referenced in the potential |
| 537 |
configurations. Alternative potential configurations have an |
| 538 |
explicit ordering associated with them. Also, potential |
| 539 |
configurations are by default preferred over the actual |
| 540 |
configuration included in the "m=" line and its associated |
| 541 |
parameters. |
| 542 |
|
| 543 |
This preference order was chosen to provide maximum backwards |
| 544 |
compatibility for the capability negotiation framework and the |
| 545 |
possible values offered for a session. For example, an entity |
| 546 |
that wants to establish a Secure RTP media stream but is |
| 547 |
willing to accept a plain RTP media stream (assumed to be the |
| 548 |
least common denominator for most endpoints), can offer plain |
| 549 |
RTP in the actual configuration and use the capability |
| 550 |
negotiation extensions to indicate the preference for Secure |
| 551 |
RTP. Entities that do not support the capability negotiation |
| 552 |
extensions or Secure RTP will then default to plain RTP. |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Andreasen Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 559 |
|
| 560 |
|
| 561 |
o A new attribute ("a=acfg") to be used in an answer SDP session |
| 562 |
description. The attribute identifies a potential |
| 563 |
configuration from an offer SDP session description that was |
| 564 |
used as an actual configuration to form the answer SDP session |
| 565 |
description. Extension capabilities can be included as well. |
| 566 |
|
| 567 |
o Extensions to the offer/answer model that allow for capabilities |
| 568 |
and potential configurations to be included in an offer. |
| 569 |
Capabilities can be provided at the session level and the media |
| 570 |
level. Potential configurations can be included only at the media |
| 571 |
level, where they constitute alternative offers that may be |
| 572 |
accepted by the answerer instead of the actual configuration(s) |
| 573 |
included in the "m=" line(s) and associated parameters. The |
| 574 |
mechanisms defined in this document enable potential |
| 575 |
configurations to change the transport protocol, add new |
| 576 |
attributes, as well as remove all existing attributes from the |
| 577 |
actual configuration. The answerer indicates which (if any) of |
| 578 |
the potential configurations it used to form the answer by |
| 579 |
including the actual configuration attribute ("a=acfg") in the |
| 580 |
answer. Capabilities may be included in answers as well, where |
| 581 |
they can aid in guiding a subsequent new offer. |
| 582 |
|
| 583 |
The mechanism is illustrated by the offer/answer exchange below, |
| 584 |
where Alice sends an offer to Bob: |
| 585 |
|
| 586 |
Alice Bob |
| 587 |
|
| 588 |
| (1) Offer (SRTP and RTP) | |
| 589 |
|--------------------------------->| |
| 590 |
| | |
| 591 |
| (2) Answer (SRTP) | |
| 592 |
|<---------------------------------| |
| 593 |
| | |
| 594 |
| (3) Offer (SRTP) | |
| 595 |
|--------------------------------->| |
| 596 |
| | |
| 597 |
| (4) Answer (SRTP) | |
| 598 |
|<---------------------------------| |
| 599 |
| | |
| 600 |
|
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Andreasen Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 615 |
|
| 616 |
|
| 617 |
Alice's offer includes RTP and SRTP as alternatives, where RTP is the |
| 618 |
default (actual configuration), but SRTP is the preferred one |
| 619 |
(potential configuration): |
| 620 |
|
| 621 |
v=0 |
| 622 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 623 |
s= |
| 624 |
c=IN IP4 192.0.2.1 |
| 625 |
t=0 0 |
| 626 |
m=audio 53456 RTP/AVP 0 18 |
| 627 |
a=tcap:1 RTP/SAVP |
| 628 |
a=acap:1 crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 629 |
inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:4 |
| 630 |
a=pcfg:1 t=1 a=1 |
| 631 |
|
| 632 |
The "m=" line indicates that Alice is offering to use plain RTP with |
| 633 |
PCMU or G.729. The capabilities are provided by the "a=tcap" and |
| 634 |
"a=acap" attributes. The transport capability attribute ("a=tcap") |
| 635 |
indicates that Secure RTP under the AVP profile ("RTP/SAVP") is |
| 636 |
supported with an associated transport capability handle of 1. The |
| 637 |
"acap" attribute provides an attribute capability with a handle of 1. |
| 638 |
The attribute capability is a "crypto" attribute, which provides the |
| 639 |
keying material for SRTP using SDP security descriptions [<a href="./rfc4568" title=""Session Description Protocol (SDP) Security Descriptions for Media Streams"">RFC4568</a>]. |
| 640 |
The "a=pcfg" attribute provides the potential configuration included |
| 641 |
in the offer by reference to the capability parameters. One |
| 642 |
alternative is provided; it has a configuration number of 1 and it |
| 643 |
consists of transport protocol capability 1 (i.e., the RTP/SAVP |
| 644 |
profile -- Secure RTP), and the attribute capability 1 (i.e., the |
| 645 |
"crypto" attribute provided). Potential configurations are preferred |
| 646 |
over the actual configuration included in the offer SDP session |
| 647 |
description, and hence Alice is expressing a preference for using |
| 648 |
Secure RTP. |
| 649 |
|
| 650 |
Bob receives the SDP session description offer from Alice. Bob |
| 651 |
supports SRTP and the SDP Capability Negotiation framework, and hence |
| 652 |
he accepts the (preferred) potential configuration for Secure RTP |
| 653 |
provided by Alice and generates the following answer SDP session |
| 654 |
description: |
| 655 |
|
| 656 |
v=0 |
| 657 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 658 |
s= |
| 659 |
c=IN IP4 192.0.2.2 |
| 660 |
t=0 0 |
| 661 |
m=audio 54568 RTP/SAVP 0 18 |
| 662 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 663 |
inline:PS1uQCVeeCFCanVmcjkpPywjNWhcYD0mXXtxaVBR|2^20|1:4 |
| 664 |
a=acfg:1 t=1 a=1 |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Andreasen Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 671 |
|
| 672 |
|
| 673 |
Bob includes the "a=acfg" attribute in the answer to inform Alice |
| 674 |
that he based his answer on an offer using potential configuration 1 |
| 675 |
with transport protocol capability 1 and attribute capability 1 from |
| 676 |
the offer SDP session description (i.e., the RTP/SAVP profile using |
| 677 |
the keying material provided). Bob also includes his keying material |
| 678 |
in a "crypto" attribute. If Bob supported one or more extensions to |
| 679 |
the Capability Negotiation framework, he would have included option |
| 680 |
tags for those in the answer as well (in an "a=csup" attribute). |
| 681 |
|
| 682 |
When Alice receives Bob's answer, session negotiation has completed; |
| 683 |
however, Alice nevertheless generates a new offer using the |
| 684 |
negotiated configuration as the actual configuration. This is done |
| 685 |
purely to assist any intermediaries that may reside between Alice and |
| 686 |
Bob but do not support the SDP Capability Negotiation framework, and |
| 687 |
hence may not understand the negotiation that just took place. |
| 688 |
|
| 689 |
Alice's updated offer includes only SRTP, and it is not using the SDP |
| 690 |
Capability Negotiation framework (Alice could have included the |
| 691 |
capabilities as well if she wanted): |
| 692 |
|
| 693 |
v=0 |
| 694 |
o=- 25678 753850 IN IP4 192.0.2.1 |
| 695 |
s= |
| 696 |
c=IN IP4 192.0.2.1 |
| 697 |
t=0 0 |
| 698 |
m=audio 53456 RTP/SAVP 0 18 |
| 699 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 700 |
inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:4 |
| 701 |
|
| 702 |
The "m=" line now indicates that Alice is offering to use Secure RTP |
| 703 |
with PCMU or G.729. The "crypto" attribute, which provides the SRTP |
| 704 |
keying material, is included with the same value again. |
| 705 |
|
| 706 |
Bob receives the SDP session description offer from Alice, which he |
| 707 |
accepts, and then generates an answer to Alice: |
| 708 |
|
| 709 |
v=0 |
| 710 |
o=- 24351 621815 IN IP4 192.0.2.2 |
| 711 |
s= |
| 712 |
c=IN IP4 192.0.2.2 |
| 713 |
t=0 0 |
| 714 |
m=audio 54568 RTP/SAVP 0 18 |
| 715 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 716 |
inline:PS1uQCVeeCFCanVmcjkpPywjNWhcYD0mXXtxaVBR|2^20|1:4 |
| 717 |
|
| 718 |
Bob includes the same "crypto" attribute as before, and the session |
| 719 |
proceeds without change. Although Bob did not include any |
| 720 |
capabilities in his answer, he could have done so if he wanted. |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Andreasen Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 727 |
|
| 728 |
|
| 729 |
Note that in this particular example, the answerer supported the |
| 730 |
capability negotiation extensions defined here. Had he not, he would |
| 731 |
simply have ignored the new attributes and accepted the (actual |
| 732 |
configuration) offer to use normal RTP. In that case, the following |
| 733 |
answer would have been generated instead: |
| 734 |
|
| 735 |
v=0 |
| 736 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 737 |
s= |
| 738 |
c=IN IP4 192.0.2.2 |
| 739 |
t=0 0 |
| 740 |
m=audio 54568 RTP/AVP 0 18 |
| 741 |
|
| 742 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Version and Extension Indication Attributes</span> |
| 743 |
|
| 744 |
In this section, we present the new attributes associated with |
| 745 |
indicating the SDP Capability Negotiation extensions supported and |
| 746 |
required. |
| 747 |
|
| 748 |
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Supported Capability Negotiation Extensions Attribute</span> |
| 749 |
|
| 750 |
The SDP Capability Negotiation solution allows for capability |
| 751 |
negotiation extensions to be defined. Associated with each such |
| 752 |
extension is an option tag that identifies the extension in question. |
| 753 |
Option tags MUST be registered with IANA per the procedures defined |
| 754 |
in <a href="#section-6.2">Section 6.2</a>. |
| 755 |
|
| 756 |
The Supported Capability Negotiation Extensions attribute ("a=csup") |
| 757 |
contains a comma-separated list of option tags identifying the SDP |
| 758 |
Capability Negotiation extensions supported by the entity that |
| 759 |
generated the SDP session description. The attribute can be provided |
| 760 |
at the session level and the media level, and it is defined as |
| 761 |
follows: |
| 762 |
|
| 763 |
a=csup: <option-tag-list> |
| 764 |
|
| 765 |
<a href="./rfc4566#section-9">RFC 4566, Section 9</a>, provides the ABNF [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] for SDP attributes. |
| 766 |
The "csup" attribute adheres to the <a href="./rfc4566">RFC 4566</a> "attribute" production, |
| 767 |
with an att-value defined as follows: |
| 768 |
|
| 769 |
att-value = option-tag-list |
| 770 |
option-tag-list = option-tag *("," option-tag) |
| 771 |
option-tag = token ; defined in [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] |
| 772 |
|
| 773 |
A special base option tag with a value of "cap-v0" is defined for the |
| 774 |
basic SDP Capability Negotiation framework defined in this document. |
| 775 |
Entities can use this option tag with the "a=csup" attribute to |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Andreasen Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 783 |
|
| 784 |
|
| 785 |
indicate support for the SDP Capability Negotiation framework |
| 786 |
specified in this document. Please note that white space is not |
| 787 |
allowed in this rule. |
| 788 |
|
| 789 |
The following examples illustrate use of the "a=csup" attribute with |
| 790 |
the "cap-v0" option tag and two hypothetical option tags, "foo" and |
| 791 |
"bar" (note the lack of white space): |
| 792 |
|
| 793 |
a=csup:cap-v0 |
| 794 |
|
| 795 |
a=csup:foo |
| 796 |
|
| 797 |
a=csup:bar |
| 798 |
|
| 799 |
a=csup:cap-v0,foo,bar |
| 800 |
|
| 801 |
The "a=csup" attribute can be provided at the session and the media |
| 802 |
level. When provided at the session level, it applies to the entire |
| 803 |
SDP session description. When provided at the media level, it |
| 804 |
applies only to the media description in question (option tags |
| 805 |
provided at the session level apply as well). There MUST NOT be more |
| 806 |
than one "a=csup" attribute at the session level and one at the media |
| 807 |
level (one per media description in the latter case). |
| 808 |
|
| 809 |
Whenever an entity that supports one or more extensions to the SDP |
| 810 |
Capability Negotiation framework generates an SDP session |
| 811 |
description, it SHOULD include the "a=csup" attribute with the option |
| 812 |
tags for the extensions it supports at the session and/or media |
| 813 |
level, unless those option tags are already provided in one or more |
| 814 |
"a=creq" attribute (see <a href="#section-3.3.2">Section 3.3.2</a>) at the relevant levels. |
| 815 |
Inclusion of the base option tag is OPTIONAL; support for the base |
| 816 |
framework can be inferred from presence of the "a=pcfg" attribute |
| 817 |
defined in <a href="#section-3.5.1">Section 3.5.1</a>. |
| 818 |
|
| 819 |
Use of the base option tag may still be useful in some scenarios, |
| 820 |
e.g., when using SIP OPTIONS [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] or generating an answer to an |
| 821 |
offer that did not use the SDP Capability Negotiation framework. |
| 822 |
|
| 823 |
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Required Capability Negotiation Extensions Attribute</span> |
| 824 |
|
| 825 |
The Required Capability Negotiation Extensions attribute ("a=creq") |
| 826 |
contains a comma-separated list of option tags (see <a href="#section-3.3.1">Section 3.3.1</a>) |
| 827 |
specifying the SDP Capability Negotiation extensions that MUST be |
| 828 |
supported by the entity receiving the SDP session description, in |
| 829 |
order for that entity to properly process the SDP Capability |
| 830 |
Negotiation attributes and associated procedures. There is no need |
| 831 |
to include the base option tag ("cap-v0") with the "creq" attribute, |
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Andreasen Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 839 |
|
| 840 |
|
| 841 |
since any entity that supports the "creq" attribute in the first |
| 842 |
place also supports the base option tag. Still, it is permissible to |
| 843 |
do so. |
| 844 |
|
| 845 |
Such functionality may be important if a future version of the |
| 846 |
Capability Negotiation framework were not backwards compatible. |
| 847 |
|
| 848 |
The attribute can be provided at the session level and the media |
| 849 |
level, and it is defined as follows: |
| 850 |
|
| 851 |
a=creq: <option-tag-list> |
| 852 |
|
| 853 |
The "creq" attribute adheres to the <a href="./rfc4566">RFC 4566</a> "attribute" production, |
| 854 |
with an att-value defined as follows: |
| 855 |
|
| 856 |
att-value = option-tag-list |
| 857 |
|
| 858 |
The following examples illustrate use of the "a=creq" attribute with |
| 859 |
the "cap-v0" base option tag and two hypothetical option tags, "foo" |
| 860 |
and "bar" (note the lack of white space): |
| 861 |
|
| 862 |
a=creq:cap-v0 |
| 863 |
a=creq:foo |
| 864 |
|
| 865 |
a=creq:bar |
| 866 |
|
| 867 |
a=creq:cap-v0,foo,bar |
| 868 |
|
| 869 |
The "a=creq" attribute can be provided at the session and the media |
| 870 |
level. When provided at the session level, it applies to the entire |
| 871 |
SDP session description. When provided at the media level, it |
| 872 |
applies only to the media description in question (required option |
| 873 |
tags provided at the session level apply as well). There MUST NOT be |
| 874 |
more than one "a=creq" attribute at the session level and one |
| 875 |
"a=creq" attribute at the media level (one per media description in |
| 876 |
the latter case). |
| 877 |
|
| 878 |
When an entity generates an SDP session description and it requires |
| 879 |
the recipient of that SDP session description to support one or more |
| 880 |
SDP Capability Negotiation extensions (except for the base) at the |
| 881 |
session or media level in order to properly process the SDP |
| 882 |
Capability Negotiation, the "a=creq" attribute MUST be included with |
| 883 |
option tags that identify the required extensions at the session |
| 884 |
and/or media level. If support for an extension is needed only in |
| 885 |
one or more specific potential configurations, the potential |
| 886 |
configuration provides a way to indicate that instead (see <a href="#section-3.5.1">Section</a> |
| 887 |
<a href="#section-3.5.1">3.5.1</a>). Support for the basic negotiation framework is implied by |
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Andreasen Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 895 |
|
| 896 |
|
| 897 |
the presence of an "a=pcfg" attribute (see <a href="#section-3.5.1">Section 3.5.1</a>) and hence |
| 898 |
it is not required to include the "a=creq" attribute with the base |
| 899 |
option tag ("cap-v0"). |
| 900 |
|
| 901 |
A recipient that receives an SDP session description and does not |
| 902 |
support one or more of the required extensions listed in a "creq" |
| 903 |
attribute MUST NOT perform the SDP Capability Negotiation defined in |
| 904 |
this document; instead the recipient MUST proceed as if the SDP |
| 905 |
Capability Negotiation attributes were not included in the first |
| 906 |
place, i.e., the capability negotiation attributes are ignored. In |
| 907 |
that case, if the SDP session description recipient is an SDP |
| 908 |
answerer [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>], the recipient SHOULD include a "csup" attribute |
| 909 |
in the resulting SDP session description answer listing the SDP |
| 910 |
Capability Negotiation extensions it actually supports. |
| 911 |
|
| 912 |
This ensures that introduction of the SDP Capability Negotiation |
| 913 |
mechanism by itself does not lead to session failures |
| 914 |
|
| 915 |
For non-supported extensions provided at the session level, this |
| 916 |
implies that SDP Capability Negotiation MUST NOT be performed at all. |
| 917 |
For non-supported extensions at the media level, this implies that |
| 918 |
SDP Capability Negotiation MUST NOT be performed for the media stream |
| 919 |
in question. |
| 920 |
|
| 921 |
An entity that does not support the SDP Capability Negotiation |
| 922 |
framework at all, will ignore these attributes (as well as the |
| 923 |
other SDP Capability Negotiation attributes) and not perform any |
| 924 |
SDP Capability Negotiation in the first place. |
| 925 |
|
| 926 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Capability Attributes</span> |
| 927 |
|
| 928 |
In this section, we present the new attributes associated with |
| 929 |
indicating the capabilities for use by the SDP Capability |
| 930 |
Negotiation. |
| 931 |
|
| 932 |
<span class="h4"><a class="selflink" id="section-3.4.1" href="#section-3.4.1">3.4.1</a>. Attribute Capability Attribute</span> |
| 933 |
|
| 934 |
Attributes and their associated values can be expressed as |
| 935 |
capabilities by use of a new attribute capability attribute |
| 936 |
("a=acap"), which is defined as follows: |
| 937 |
|
| 938 |
a=acap: <att-cap-num> <att-par> |
| 939 |
|
| 940 |
where <att-cap-num> is an integer between 1 and 2^31-1 (both |
| 941 |
included) used to number the attribute capability and <att-par> is an |
| 942 |
attribute ("a=") in its "<attribute>" or "<attribute>:<value>" form, |
| 943 |
i.e., excluding the "a=" part (see [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>]). The attribute can be |
| 944 |
provided at the session level and the media level. |
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Andreasen Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 951 |
|
| 952 |
|
| 953 |
The "acap" attribute adheres to the <a href="./rfc4566">RFC 4566</a> "attribute" production, |
| 954 |
with an att-value defined as follows: |
| 955 |
|
| 956 |
att-value = att-cap-num 1*WSP att-par |
| 957 |
att-cap-num = 1*10(DIGIT) ;defined in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] |
| 958 |
att-par = attribute ;defined in [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] |
| 959 |
|
| 960 |
Note that white space is not permitted before the att-cap-num. |
| 961 |
|
| 962 |
When the attribute capability contains a session-level attribute, |
| 963 |
that "acap" attribute can only be provided at the session level. |
| 964 |
Conversely, media-level attributes can be provided in attribute |
| 965 |
capabilities at either the media level or session level. The base |
| 966 |
SDP Capability Negotiation framework however only defines procedures |
| 967 |
for use of media-level attribute capabilities at the media level. |
| 968 |
Implementations that conform only to the base framework MUST NOT |
| 969 |
generate media-level attribute capabilities at the session level; |
| 970 |
however, extensions may change this (see, e.g., [<a href="#ref-SDPMedCap">SDPMedCap</a>] for one |
| 971 |
such extension) and hence all implementations MUST still be prepared |
| 972 |
to receive such capabilities (see <a href="#section-3.6.2">Section 3.6.2</a> for processing |
| 973 |
rules). |
| 974 |
|
| 975 |
Each occurrence of the "acap" attribute in the entire session |
| 976 |
description MUST use a different value of <att-cap-num>. Consecutive |
| 977 |
numbering of the <att-cap-num> values is not required. |
| 978 |
|
| 979 |
There is a need to be able to reference both session-level and |
| 980 |
media-level attributes in potential configurations at the media |
| 981 |
level, and this provides for a simple solution to avoiding overlap |
| 982 |
between the references (handles) to each attribute capability. |
| 983 |
|
| 984 |
The <att-cap-num> values provided are independent of similar |
| 985 |
<cap-num> values provided for other types of capabilities, i.e., they |
| 986 |
form a separate name-space for attribute capabilities. |
| 987 |
|
| 988 |
The following examples illustrate use of the "acap" attribute: |
| 989 |
|
| 990 |
a=acap:1 ptime:20 |
| 991 |
|
| 992 |
a=acap:2 ptime:30 |
| 993 |
|
| 994 |
a=acap:3 key-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAyONQ6gAA |
| 995 |
AAAGEEoo2pee4hp2UaDX8ZE22YwKAAAPZG9uYWxkQGR1Y2suY29tAQAAAAAAAQAk0 |
| 996 |
JKpgaVkDaawi9whVBtBt0KZ14ymNuu62+Nv3ozPLygwK/GbAV9iemnGUIZ19fWQUO |
| 997 |
SrzKTAv9zV |
| 998 |
|
| 999 |
a=acap:4 crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 1000 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Andreasen Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
The first two attribute capabilities provide attribute values for the |
| 1010 |
ptime attribute. The third provides SRTP parameters by using |
| 1011 |
Multimedia Internet KEYing (MIKEY) [<a href="./rfc3830" title=""MIKEY: Multimedia Internet KEYing"">RFC3830</a>] with the "key-mgmt" |
| 1012 |
attribute [<a href="./rfc4567" title=""Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)"">RFC4567</a>]. The fourth provides SRTP parameters by use of |
| 1013 |
security descriptions with the "crypto" attribute [<a href="./rfc4568" title=""Session Description Protocol (SDP) Security Descriptions for Media Streams"">RFC4568</a>]. Note |
| 1014 |
that the line-wrapping and new-lines in example three and four are |
| 1015 |
provided for formatting reasons only -- they are not permitted in |
| 1016 |
actual SDP session descriptions. |
| 1017 |
|
| 1018 |
Readers familiar with <a href="./rfc3407">RFC 3407</a> may notice the similarity between |
| 1019 |
the <a href="./rfc3407">RFC 3407</a> "cpar" attribute and the above. There are however a |
| 1020 |
couple of important differences, notably that the "acap" attribute |
| 1021 |
contains a handle that enables referencing it and it furthermore |
| 1022 |
supports only attributes (the "cpar" attribute defined in <a href="./rfc3407">RFC 3407</a> |
| 1023 |
supports bandwidth information as well). The "acap" attribute |
| 1024 |
also is not automatically associated with any particular |
| 1025 |
capabilities. See <a href="#section-3.14">Section 3.14</a> for the relationship to <a href="./rfc3407">RFC 3407</a>. |
| 1026 |
|
| 1027 |
Attribute capabilities MUST NOT embed any capability negotiation |
| 1028 |
parameters. This restriction applies to all the capability |
| 1029 |
negotiation parameters defined in this document ("csup", "creq", |
| 1030 |
"acap", "tcap", "pcfg", and "acfg") as well as any capability |
| 1031 |
negotiation extensions defined. The following examples are thus |
| 1032 |
invalid attribute capabilities and MUST NOT be used: |
| 1033 |
|
| 1034 |
a=acap:1 acap:2 foo:a ;Not allowed to embed "acap" |
| 1035 |
|
| 1036 |
a=acap:2 a=pcfg:1 t=1 a=1 ;Not allowed to embed "pcfg" |
| 1037 |
|
| 1038 |
The reason for this restriction is to avoid overly complex processing |
| 1039 |
rules resulting from the expansion of such capabilities into |
| 1040 |
potential configurations (see <a href="#section-3.6.2">Section 3.6.2</a> for further details). |
| 1041 |
|
| 1042 |
<span class="h4"><a class="selflink" id="section-3.4.2" href="#section-3.4.2">3.4.2</a>. Transport Protocol Capability Attribute</span> |
| 1043 |
|
| 1044 |
Transport protocols can be expressed as capabilities by use of a new |
| 1045 |
Transport Protocol Capability attribute ("a=tcap") defined as |
| 1046 |
follows: |
| 1047 |
|
| 1048 |
a=tcap: <trpr-cap-num> <proto-list> |
| 1049 |
|
| 1050 |
where <trpr-cap-num> is an integer between 1 and 2^31-1 (both |
| 1051 |
included) used to number the transport address capability for later |
| 1052 |
reference, and <proto-list> is one or more <proto>, separated by |
| 1053 |
white space, as defined in the SDP "m=" line. The attribute can be |
| 1054 |
provided at the session level and the media level. |
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Andreasen Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
The "tcap" attribute adheres to the <a href="./rfc4566">RFC 4566</a> "attribute" production, |
| 1066 |
with an att-value defined as follows: |
| 1067 |
|
| 1068 |
att-value = trpr-cap-num 1*WSP proto-list |
| 1069 |
trpr-cap-num = 1*10(DIGIT) ;defined in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] |
| 1070 |
proto-list = proto *(1*WSP proto) ;defined in [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] |
| 1071 |
|
| 1072 |
Note that white space is not permitted before the trpr-cap-num. |
| 1073 |
|
| 1074 |
The "tcap" attribute can be provided at the session level and the |
| 1075 |
media level. There MUST NOT be more than one "a=tcap" attribute at |
| 1076 |
the session level and one at the media level (one per media |
| 1077 |
description in the latter case). Each occurrence of the "tcap" |
| 1078 |
attribute in the entire session description MUST use a different |
| 1079 |
value of <trpr-cap-num>. When multiple <proto> values are provided, |
| 1080 |
the first one is associated with the value <trpr-cap-num>, the second |
| 1081 |
one with the value one higher, etc. There MUST NOT be any capability |
| 1082 |
number overlap between different "tcap" attributes in the entire SDP |
| 1083 |
session description. The <trpr-cap-num> values provided are |
| 1084 |
independent of similar <cap-num> values provided for other capability |
| 1085 |
attributes, i.e., they form a separate name-space for transport |
| 1086 |
protocol capabilities. Consecutive numbering of the <trpr-cap-num> |
| 1087 |
values in different "tcap" attributes is not required. |
| 1088 |
|
| 1089 |
Below, we provide examples of the "a=tcap" attribute: |
| 1090 |
|
| 1091 |
a=tcap:1 RTP/AVP |
| 1092 |
|
| 1093 |
a=tcap:2 RTP/AVPF |
| 1094 |
|
| 1095 |
a=tcap:3 RTP/SAVP RTP/SAVPF |
| 1096 |
|
| 1097 |
a=tcap:5 UDP/TLS/RTP/SAVP |
| 1098 |
|
| 1099 |
The first one provides a capability for the "RTP/AVP" profile defined |
| 1100 |
in [<a href="./rfc3551" title=""RTP Profile for Audio and Video Conferences with Minimal Control"">RFC3551</a>] and the second one provides a capability for the RTP |
| 1101 |
with RTCP-based feedback profile defined in [<a href="./rfc4585" title=""Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)"">RFC4585</a>]. The third one |
| 1102 |
provides capabilities for the "RTP/SAVP" (transport capability number |
| 1103 |
3) and "RTP/SAVPF" profiles (transport protocol capability number 4). |
| 1104 |
The last one provides capabilities for "UDP/TLS/RTP/SAVP", i.e., |
| 1105 |
DTLS-SRTP [<a href="./rfc5764" title=""Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)"">RFC5764</a>] (transport capability number 5). |
| 1106 |
|
| 1107 |
The "tcap" attribute by itself can only specify transport protocols |
| 1108 |
as defined by <proto> in [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>]; however, full specification of a |
| 1109 |
media stream requires further qualification of the transport protocol |
| 1110 |
by one or more media format descriptions, which themselves often |
| 1111 |
depend on the transport protocol. As an example, [<a href="./rfc3551" title=""RTP Profile for Audio and Video Conferences with Minimal Control"">RFC3551</a>] defines |
| 1112 |
the "RTP/AVP" transport for use with audio and video codecs (media |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Andreasen Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
formats), whereas [<a href="./rfc4145" title=""TCP-Based Media Transport in the Session Description Protocol (SDP)"">RFC4145</a>] defines the "TCP" transport, which, for |
| 1122 |
example, may be used to negotiate T.38 fax ("image/t38"), etc. In a |
| 1123 |
non-SDP context, some media formats could be viewed as transports |
| 1124 |
themselves (e.g., T.38); however, in the context of SDP and SDP |
| 1125 |
Capability Negotiation, they are not. If capability negotiation is |
| 1126 |
required for such media formats, they MUST all either be valid under |
| 1127 |
the transport protocol indicated in the "m=" line included for the |
| 1128 |
media stream description, or a suitable extension must be used, e.g., |
| 1129 |
SDP Media Capabilities [<a href="#ref-SDPMedCap">SDPMedCap</a>]. |
| 1130 |
|
| 1131 |
The ability to use a particular transport protocol is inherently |
| 1132 |
implied by including it in the "m=" line, regardless of whether or |
| 1133 |
not it is provided in a "tcap" attribute. However, if a potential |
| 1134 |
configuration needs to reference that transport protocol as a |
| 1135 |
capability, the transport protocol MUST be included explicitly in a |
| 1136 |
"tcap" attribute. |
| 1137 |
|
| 1138 |
This may seem redundant (and indeed it is from the offerer's point |
| 1139 |
of view), however it is done to protect against intermediaries |
| 1140 |
(e.g., middleboxes) that may modify "m=" lines while passing |
| 1141 |
unknown attributes through. If an implicit transport capability |
| 1142 |
were used instead (e.g., a reserved transport capability number |
| 1143 |
could be used to refer to the transport protocol in the "m=" |
| 1144 |
line), and an intermediary were to modify the transport protocol |
| 1145 |
in the "m=" line (e.g., to translate between plain RTP and Secure |
| 1146 |
RTP), then the potential configuration referencing that implicit |
| 1147 |
transport capability may no longer be correct. With explicit |
| 1148 |
capabilities, we avoid this pitfall; however, the potential |
| 1149 |
configuration preference (see <a href="#section-3.5.1">Section 3.5.1</a>) may not reflect that |
| 1150 |
of the intermediary (which some may view as a feature). |
| 1151 |
|
| 1152 |
Note that a transport protocol capability may be provided, |
| 1153 |
irrespective of whether or not it is referenced in a potential |
| 1154 |
configuration (just like any other capability). |
| 1155 |
|
| 1156 |
<span class="h4"><a class="selflink" id="section-3.4.3" href="#section-3.4.3">3.4.3</a>. Extension Capability Attributes</span> |
| 1157 |
|
| 1158 |
The SDP Capability Negotiation framework allows for new types of |
| 1159 |
capabilities to be defined as extensions and used with the general |
| 1160 |
capability negotiation framework. The syntax and semantics of such |
| 1161 |
new capability attributes are not defined here; however, in order to |
| 1162 |
be used with potential configurations, they SHOULD allow for a |
| 1163 |
numeric handle to be associated with each capability. This handle |
| 1164 |
can be used as a reference within the potential and actual |
| 1165 |
configuration attributes (see Sections <a href="#section-3.5.1">3.5.1</a> and <a href="#section-3.5.2">3.5.2</a>). The |
| 1166 |
definition of such extension capability attributes MUST also state |
| 1167 |
whether they can be applied at the session level, media level, or |
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Andreasen Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
both. Note that extensions can have option tags defined for them, |
| 1178 |
and option tags MUST be registered with the IANA in accordance with |
| 1179 |
the procedures specified in <a href="#section-6.2">Section 6.2</a>. |
| 1180 |
|
| 1181 |
Extension capabilities SHOULD NOT embed any capability negotiation |
| 1182 |
parameters. This applies to all the capability negotiation |
| 1183 |
parameters defined in this document as well as any extensions |
| 1184 |
defined. The reason for this restriction is to avoid overly complex |
| 1185 |
processing rules resulting from the expansion of such capabilities |
| 1186 |
into potential configurations (see <a href="#section-3.6.2">Section 3.6.2</a> for further |
| 1187 |
details). If an extension does not follow the above "SHOULD NOT" |
| 1188 |
recommendation, the extension MUST provide a careful analysis of why |
| 1189 |
such behavior is both necessary and safe. |
| 1190 |
|
| 1191 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Configuration Attributes</span> |
| 1192 |
|
| 1193 |
<span class="h4"><a class="selflink" id="section-3.5.1" href="#section-3.5.1">3.5.1</a>. Potential Configuration Attribute</span> |
| 1194 |
|
| 1195 |
Potential configurations can be expressed by use of a new Potential |
| 1196 |
Configuration Attribute ("a=pcfg") defined as follows: |
| 1197 |
|
| 1198 |
a=pcfg: <config-number> [<pot-cfg-list>] |
| 1199 |
|
| 1200 |
where <config-number> is an integer between 1 and 2^31-1 (both |
| 1201 |
included). The attribute can be provided only at the media level. |
| 1202 |
|
| 1203 |
The "pcfg" attribute adheres to the <a href="./rfc4566">RFC 4566</a> "attribute" production, |
| 1204 |
with an att-value defined as follows: |
| 1205 |
|
| 1206 |
att-value = config-number [1*WSP pot-cfg-list] |
| 1207 |
config-number = 1*10(DIGIT) ;defined in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] |
| 1208 |
pot-cfg-list = pot-config *(1*WSP pot-config) |
| 1209 |
pot-config = attribute-config-list / |
| 1210 |
transport-protocol-config-list / |
| 1211 |
extension-config-list |
| 1212 |
|
| 1213 |
The missing productions are defined below. Note that white space is |
| 1214 |
not permitted before the config-number. |
| 1215 |
|
| 1216 |
The potential configuration attribute can be provided only at the |
| 1217 |
media level and there can be multiple instances of it within a given |
| 1218 |
media description. The attribute includes a configuration number, |
| 1219 |
which is an integer between 1 and 2^31-1 (both included). The |
| 1220 |
configuration number MUST be unique within the media description |
| 1221 |
(i.e., it has only media-level scope). The configuration number also |
| 1222 |
indicates the relative preference of potential configurations; lower |
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Andreasen Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
numbers are preferred over higher numbers. Consecutive numbering of |
| 1234 |
the configuration numbers in different "pcfg" attributes in a media |
| 1235 |
description is not required. |
| 1236 |
|
| 1237 |
A potential configuration list is normally provided after the |
| 1238 |
configuration number. When the potential configuration list is |
| 1239 |
omitted, the potential configuration equals the actual configuration. |
| 1240 |
The potential configuration list contains one or more of attribute, |
| 1241 |
transport, and extension configuration lists. A potential |
| 1242 |
configuration may for example include attribute capabilities and |
| 1243 |
transport capabilities, transport capabilities only, or some other |
| 1244 |
combination of capabilities. If transport capabilities are not |
| 1245 |
included in a potential configuration, the default transport for that |
| 1246 |
media stream is used. |
| 1247 |
|
| 1248 |
The potential configuration lists generally reference one or more |
| 1249 |
capabilities (extension configuration lists MAY use a different |
| 1250 |
format). Those capabilities are (conceptually) used to construct a |
| 1251 |
new internal version of the SDP session description by use of purely |
| 1252 |
syntactic add and (possibly) delete operations on the original SDP |
| 1253 |
session description (actual configuration). This provides an |
| 1254 |
alternative potential configuration SDP session description that can |
| 1255 |
be used by conventional SDP and offer/answer procedures if selected. |
| 1256 |
|
| 1257 |
This document defines attribute configuration lists and transport |
| 1258 |
protocol configuration lists. Each of these MUST NOT be present more |
| 1259 |
than once in a particular potential configuration attribute. |
| 1260 |
Attribute capabilities referenced by the attribute configuration list |
| 1261 |
(if included) are added to the actual configuration, whereas a |
| 1262 |
transport capability referenced by the transport protocol |
| 1263 |
configuration list (if included) replaces the default transport |
| 1264 |
protocol from the actual configuration. Extension configuration |
| 1265 |
lists can be included as well. There can be more than one extension |
| 1266 |
configuration list; however, each particular extension MUST NOT be |
| 1267 |
present more than once in a given "a=pcfg" attribute. Together, the |
| 1268 |
various configuration lists define a potential configuration. |
| 1269 |
|
| 1270 |
There can be multiple potential configurations in a media |
| 1271 |
description. Each of these indicates not only a willingness, but in |
| 1272 |
fact a desire to use the potential configuration. |
| 1273 |
|
| 1274 |
|
| 1275 |
|
| 1276 |
|
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Andreasen Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
The example SDP session description below contains two potential |
| 1290 |
configurations: |
| 1291 |
|
| 1292 |
v=0 |
| 1293 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 1294 |
s= |
| 1295 |
c=IN IP4 192.0.2.1 |
| 1296 |
t=0 0 |
| 1297 |
m=audio 53456 RTP/AVP 0 18 |
| 1298 |
a=tcap:1 RTP/SAVP RTP/SAVPF |
| 1299 |
a=acap:1 crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 1300 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 1301 |
a=pcfg:1 t=1 a=1 |
| 1302 |
a=pcfg:2 t=2 a=1 |
| 1303 |
|
| 1304 |
Potential configuration 1 contains a transport protocol configuration |
| 1305 |
list that references transport capability 1 ("RTP/SAVP") and an |
| 1306 |
attribute configuration list that references attribute capability 1 |
| 1307 |
("a=crypto:..."). Potential configuration 2 contains a transport |
| 1308 |
protocol configuration list that references transport capability 2 |
| 1309 |
("RTP/SAVPF") and an attribute configuration list that references |
| 1310 |
attribute capability 1 ("a=crypto:..."). |
| 1311 |
|
| 1312 |
Attribute capabilities are used in a potential configuration by use |
| 1313 |
of the attribute-config-list parameter, which is defined by the |
| 1314 |
following ABNF: |
| 1315 |
|
| 1316 |
attribute-config-list = "a=" delete-attributes |
| 1317 |
attribute-config-list =/ "a=" [delete-attributes ":"] |
| 1318 |
mo-att-cap-list *(BAR mo-att-cap-list) |
| 1319 |
|
| 1320 |
delete-attributes = DELETE ( "m" ; media attributes |
| 1321 |
/ "s" ; session attributes |
| 1322 |
/ "ms" ) ; media and session attributes |
| 1323 |
|
| 1324 |
mo-att-cap-list = mandatory-optional-att-cap-list / |
| 1325 |
mandatory-att-cap-list / |
| 1326 |
optional-att-cap-list |
| 1327 |
|
| 1328 |
mandatory-optional-att-cap-list = mandatory-att-cap-list |
| 1329 |
"," optional-att-cap-list |
| 1330 |
mandatory-att-cap-list = att-cap-list |
| 1331 |
optional-att-cap-list = "[" att-cap-list "]" |
| 1332 |
|
| 1333 |
att-cap-list = att-cap-num *("," att-cap-num) |
| 1334 |
att-cap-num = 1*10(DIGIT) ;defined in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] |
| 1335 |
BAR = "|" |
| 1336 |
DELETE = "-" |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Andreasen Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
Note that white space is not permitted within the attribute-config- |
| 1346 |
list rule. |
| 1347 |
|
| 1348 |
Each attribute configuration list can optionally begin with |
| 1349 |
instructions for how to handle attributes that are part of the actual |
| 1350 |
configuration SDP session description (i.e., the "a=" lines present |
| 1351 |
in the original SDP session description). By default, such |
| 1352 |
attributes will remain as part of the potential configuration in |
| 1353 |
question. However, if delete-attributes indicates "-m", then all |
| 1354 |
attribute lines within the media description in question will be |
| 1355 |
deleted in the resulting potential configuration SDP session |
| 1356 |
description (i.e., all "a=" lines under the "m=" line in question). |
| 1357 |
If delete-attributes indicates "-s", then all attribute lines at the |
| 1358 |
session level will be deleted (i.e., all "a=" lines before the first |
| 1359 |
"m=" line). If delete-attributes indicates "-ms", then all attribute |
| 1360 |
lines within this media description ("m=" line) and all attribute |
| 1361 |
lines at the session level will be deleted. |
| 1362 |
|
| 1363 |
The attribute capability list comes next (if included). It contains |
| 1364 |
one or more alternative lists of attribute capabilities. The |
| 1365 |
alternative attribute capability lists are separated by a vertical |
| 1366 |
bar ("|"), and each list contains one or more attribute capabilities |
| 1367 |
separated by commas (","). The attribute capabilities are either |
| 1368 |
mandatory or optional. Mandatory attribute capabilities MUST be |
| 1369 |
supported in order to use the potential configuration, whereas |
| 1370 |
optional attribute capabilities MAY be supported in order to use the |
| 1371 |
potential configuration. |
| 1372 |
|
| 1373 |
Within each attribute capability list, all the mandatory attribute |
| 1374 |
capabilities (if any) are listed first, and all the optional |
| 1375 |
attribute capabilities (if any) are listed last. The optional |
| 1376 |
attribute capabilities are contained within a pair of square brackets |
| 1377 |
("[" and "]"). Each attribute capability is merely an attribute |
| 1378 |
capability number (att-cap-num) that identifies a particular |
| 1379 |
attribute capability by referring to attribute capability numbers |
| 1380 |
defined above and hence MUST be between 1 and 2^31-1 (both included). |
| 1381 |
The following example illustrates the above: |
| 1382 |
|
| 1383 |
a=pcfg:1 a=-m:1,2,[3,4]|1,7,[5] |
| 1384 |
|
| 1385 |
where |
| 1386 |
|
| 1387 |
o "a=-m:1,2,[3,4]|1,7,[5]" is the attribute configuration list |
| 1388 |
|
| 1389 |
o "-m" indicates to delete all attributes from the media description |
| 1390 |
of the actual configuration |
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Andreasen Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
o "1,2,[3,4]" and "1,7,[5]" are both attribute capability lists. |
| 1402 |
The two lists are alternatives, since they are separated by a |
| 1403 |
vertical bar above |
| 1404 |
|
| 1405 |
o "1", "2", and "7" are mandatory attribute capabilities |
| 1406 |
|
| 1407 |
o "3", "4", and "5" are optional attribute capabilities |
| 1408 |
|
| 1409 |
Note that in the example above, we have a single handle ("1") for the |
| 1410 |
potential configuration(s), but there are actually two different |
| 1411 |
potential configurations (separated by a vertical bar). This is done |
| 1412 |
for message size efficiency reasons, which is especially important |
| 1413 |
when we add other types of capabilities to the potential |
| 1414 |
configuration. If there is a need to provide a unique handle for |
| 1415 |
each, then separate "a=pcfg" attributes with different handles MUST |
| 1416 |
be used instead. |
| 1417 |
|
| 1418 |
Each referenced attribute capability in the potential configuration |
| 1419 |
will result in the corresponding attribute name and its associated |
| 1420 |
value (contained inside the attribute capability) being added to the |
| 1421 |
resulting potential configuration SDP session description. |
| 1422 |
|
| 1423 |
Alternative attribute capability lists are separated by a vertical |
| 1424 |
bar ("|"), the scope of which extends to the next alternative (i.e., |
| 1425 |
"," has higher precedence than "|"). The alternatives are ordered by |
| 1426 |
preference with the most preferred listed first. In order for a |
| 1427 |
recipient of the SDP session description (e.g., an answerer receiving |
| 1428 |
this in an offer) to use this potential configuration, exactly one of |
| 1429 |
the alternative lists MUST be selected in its entirety. This |
| 1430 |
requires that all mandatory attribute capabilities referenced by the |
| 1431 |
potential configuration are supported with the attribute values |
| 1432 |
provided. |
| 1433 |
|
| 1434 |
Transport protocol configuration lists are included in a potential |
| 1435 |
configuration by use of the transport-protocol-config-list parameter, |
| 1436 |
which is defined by the following ABNF: |
| 1437 |
|
| 1438 |
transport-protocol-config-list = |
| 1439 |
"t=" trpr-cap-num *(BAR trpr-cap-num) |
| 1440 |
trpr-cap-num = 1*10(DIGIT) ; defined in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] |
| 1441 |
|
| 1442 |
Note that white space is not permitted within this rule. |
| 1443 |
|
| 1444 |
The trpr-cap-num refers to transport protocol capability numbers |
| 1445 |
defined above and hence MUST be between 1 and 2^31-1 (both included). |
| 1446 |
Alternative transport protocol capabilities are separated by a |
| 1447 |
vertical bar ("|"). The alternatives are ordered by preference with |
| 1448 |
the most preferred listed first. If there are no transport protocol |
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Andreasen Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
capabilities included in a potential configuration at the media |
| 1458 |
level, the transport protocol information from the associated "m=" |
| 1459 |
line MUST be used. In order for a recipient of the SDP session |
| 1460 |
description (e.g., an answerer receiving this in an offer) to use |
| 1461 |
this potential configuration, exactly one of the alternatives MUST be |
| 1462 |
selected. This requires that the transport protocol in question is |
| 1463 |
supported. |
| 1464 |
|
| 1465 |
In the presence of intermediaries (the existence of which may not |
| 1466 |
be known), care should be taken with assuming that the transport |
| 1467 |
protocol in the "m=" line will not be modified by an intermediary. |
| 1468 |
Use of an explicit transport protocol capability will guard |
| 1469 |
against capability negotiation implications of that. |
| 1470 |
|
| 1471 |
Extension capabilities can be included in a potential configuration |
| 1472 |
as well by use of extension configuration lists. Extension |
| 1473 |
configuration lists MUST adhere to the following ABNF: |
| 1474 |
|
| 1475 |
extension-config-list = ["+"] ext-cap-name "=" ext-cap-list |
| 1476 |
ext-cap-name = 1*(ALPHA / DIGIT) |
| 1477 |
ext-cap-list = 1*VCHAR ; defined in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] |
| 1478 |
|
| 1479 |
Note that white space is not permitted within this rule. |
| 1480 |
|
| 1481 |
The ext-cap-name refers to the name of the extension capability and |
| 1482 |
the ext-cap-list is here merely defined as a sequence of visible |
| 1483 |
characters. The actual extension supported MUST refine both of these |
| 1484 |
further. For extension capabilities that merely need to be |
| 1485 |
referenced by a capability number, it is RECOMMENDED to follow a |
| 1486 |
structure similar to what has been specified above. Unsupported or |
| 1487 |
unknown potential extension configuration lists in a potential |
| 1488 |
configuration attribute MUST be ignored, unless they are prefixed |
| 1489 |
with the plus ("+") sign, which indicates that the extension is |
| 1490 |
mandatory and MUST be supported in order to use that potential |
| 1491 |
configuration. |
| 1492 |
|
| 1493 |
The "creq" attribute and its associated rules can be used to |
| 1494 |
ensure that required extensions are supported in the first place. |
| 1495 |
|
| 1496 |
Extension configuration lists define new potential configuration |
| 1497 |
parameters and hence they MUST be registered with IANA per the |
| 1498 |
procedures defined in <a href="#section-6.3">Section 6.3</a>. |
| 1499 |
|
| 1500 |
Potential configuration attributes can be provided only at the media |
| 1501 |
level; however, it is possible to reference capabilities provided at |
| 1502 |
either the session or media level. There are certain semantic rules |
| 1503 |
and restrictions associated with this: |
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Andreasen Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
A (media-level) potential configuration attribute in a given media |
| 1514 |
description MUST NOT reference a media-level capability provided in a |
| 1515 |
different media description; doing so invalidates that potential |
| 1516 |
configuration (note that a potential configuration attribute can |
| 1517 |
contain more than one potential configuration by use of |
| 1518 |
alternatives). A potential configuration attribute can however |
| 1519 |
reference a session-level capability. The semantics of doing so |
| 1520 |
depends on the type of capability. In the case of transport protocol |
| 1521 |
capabilities, it has no particular implication. In the case of |
| 1522 |
attribute capabilities, however, it does. More specifically, the |
| 1523 |
attribute name and value (provided within that attribute capability) |
| 1524 |
will be considered part of the resulting SDP for that particular |
| 1525 |
configuration at the *session* level. In other words, it will be |
| 1526 |
as-if that attribute was provided with that value at the session |
| 1527 |
level in the first place. As a result, the base SDP Capability |
| 1528 |
Negotiation framework REQUIRES that potential configurations do not |
| 1529 |
reference any session-level attribute capabilities that contain |
| 1530 |
media-level attributes (since that would place a media-level |
| 1531 |
attribute at the session level). Extensions may modify this |
| 1532 |
behavior, as long as it is fully backwards compatible with the base |
| 1533 |
specification. |
| 1534 |
|
| 1535 |
Individual media streams perform capability negotiation individually, |
| 1536 |
and hence it is possible that one media stream (where the attribute |
| 1537 |
was part of a potential configuration) chose a configuration without |
| 1538 |
a session-level attribute that was chosen by another media stream. |
| 1539 |
The session-level attribute however remains "active" and applies to |
| 1540 |
the entire resulting potential configuration SDP session description. |
| 1541 |
In theory, this is problematic if one or more session-level |
| 1542 |
attributes either conflicts with or potentially interacts with |
| 1543 |
another session-level or media-level attribute in an undefined |
| 1544 |
manner. In practice, such examples seem to be rare (at least with |
| 1545 |
the SDP attributes that had been defined at time of publication of |
| 1546 |
this document). |
| 1547 |
|
| 1548 |
A related set of problems can occur if we need coordination |
| 1549 |
between session-level attributes from multiple media streams in |
| 1550 |
order for a particular functionality to work. The grouping |
| 1551 |
framework [<a href="./rfc5888" title=""The Session Description Protocol (SDP) Grouping Framework"">RFC5888</a>] is an example of this. If we use the SDP |
| 1552 |
Capability Negotiation framework to select a session-level group |
| 1553 |
attribute (provided as an attribute capability), and we require |
| 1554 |
two media descriptions to do this consistently, we could have a |
| 1555 |
problem. The Forward Error Correction (FEC) grouping semantics |
| 1556 |
[<a href="./rfc4756" title=""Forward Error Correction Grouping Semantics in Session Description Protocol"">RFC4756</a>] is one example where this in theory could cause |
| 1557 |
problems, however in practice, it is unclear that there is a |
| 1558 |
significant problem with the grouping semantics that had been |
| 1559 |
defined at time of publication of this document. |
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Andreasen Standards Track [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
Resolving the above issues in general requires inter-media stream |
| 1570 |
constraints and synchronized potential configuration processing; this |
| 1571 |
would add considerable complexity to the overall solution. In |
| 1572 |
practice, with the SDP attributes defined at time of publication of |
| 1573 |
this document, it does not seem to be a significant problem, and |
| 1574 |
hence the base SDP Capability Negotiation solution does not provide a |
| 1575 |
solution to this issue. Instead, it is RECOMMENDED that use of |
| 1576 |
session-level attributes in a potential configuration is avoided when |
| 1577 |
possible, and when not, that such use is examined closely for any |
| 1578 |
potential interaction issues. If interaction is possible, the entity |
| 1579 |
generating the SDP session description SHOULD NOT assume that well- |
| 1580 |
defined operation will occur at the receiving entity. This implies |
| 1581 |
that mechanisms that might have such interactions cannot be used in |
| 1582 |
security critical contexts. |
| 1583 |
|
| 1584 |
The session-level operation of extension capabilities is undefined. |
| 1585 |
Consequently, each new session-level extension capability defined |
| 1586 |
MUST specify the implication of making it part of a configuration at |
| 1587 |
the media level. |
| 1588 |
|
| 1589 |
Below, we provide an example of the "a=pcfg" attribute in a complete |
| 1590 |
media description in order to properly indicate the supporting |
| 1591 |
attributes: |
| 1592 |
|
| 1593 |
v=0 |
| 1594 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 1595 |
s= |
| 1596 |
c=IN IP4 192.0.2.1 |
| 1597 |
t=0 0 |
| 1598 |
m=audio 53456 RTP/AVPF 0 18 |
| 1599 |
a=acap:1 crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 1600 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 1601 |
a=tcap:1 RTP/AVPF RTP/AVP RTP/SAVP RTP/SAVPF |
| 1602 |
a=pcfg:1 t=4|3 a=1 |
| 1603 |
a=pcfg:8 t=1|2 |
| 1604 |
|
| 1605 |
We have two potential configuration attributes listed here. The |
| 1606 |
first one (and most preferred, since its configuration number is "1") |
| 1607 |
indicates that either of the profiles RTP/SAVPF or RTP/SAVP |
| 1608 |
(specified by the transport protocol capability numbers 4 and 3) can |
| 1609 |
be supported with attribute capability 1 (the "crypto" attribute); |
| 1610 |
RTP/SAVPF is preferred over RTP/SAVP since its capability number (4) |
| 1611 |
is listed first in the preferred potential configuration. Note that |
| 1612 |
although we have a single potential configuration attribute and |
| 1613 |
associated handle, we have two potential configurations. |
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Andreasen Standards Track [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
The second potential configuration attribute indicates that the |
| 1626 |
RTP/AVPF or RTP/AVP profiles can be used, with RTP/AVPF being the |
| 1627 |
preferred one. This non-secure RTP alternative is the less preferred |
| 1628 |
one since its configuration number is "8". Again, note that we have |
| 1629 |
two potential configurations here and hence a total of four potential |
| 1630 |
configurations in the SDP session description above. |
| 1631 |
|
| 1632 |
<span class="h4"><a class="selflink" id="section-3.5.2" href="#section-3.5.2">3.5.2</a>. Actual Configuration Attribute</span> |
| 1633 |
|
| 1634 |
The actual configuration attribute identifies which of the potential |
| 1635 |
configurations from an offer SDP session description was selected and |
| 1636 |
used as the actual configuration to generate an answer SDP session |
| 1637 |
description. This is done by including the configuration number and |
| 1638 |
the configuration lists (if any) from the offer that were selected |
| 1639 |
and used by the answerer in his offer/answer procedure as follows: |
| 1640 |
|
| 1641 |
o A selected attribute configuration MUST include the delete- |
| 1642 |
attributes and the known and supported parameters from the |
| 1643 |
selected alternative mo-att-cap-list (i.e., containing all |
| 1644 |
mandatory and all known and supported optional capability numbers |
| 1645 |
from the potential configuration). If delete-attributes were not |
| 1646 |
included in the potential configuration, they will of course not |
| 1647 |
be present here either. |
| 1648 |
|
| 1649 |
o A selected transport protocol configuration MUST include the |
| 1650 |
selected transport protocol capability number. |
| 1651 |
|
| 1652 |
o A selected potential extension configuration MUST include the |
| 1653 |
selected extension configuration parameters as specified for that |
| 1654 |
particular extension. |
| 1655 |
|
| 1656 |
o When a configuration list contains alternatives (separated by |
| 1657 |
"|"), the selected configuration only MUST be provided. |
| 1658 |
|
| 1659 |
Note that the selected configuration number and all selected |
| 1660 |
capability numbers used in the actual configuration attribute refer |
| 1661 |
to those from the offer: not the answer. |
| 1662 |
|
| 1663 |
The answer may for example include capabilities as well to inform |
| 1664 |
the offerer of the answerers capabilities above and beyond the |
| 1665 |
negotiated configuration. The actual configuration attribute does |
| 1666 |
not refer to any of those answer capabilities though. |
| 1667 |
|
| 1668 |
The Actual Configuration Attribute ("a=acfg") is defined as follows: |
| 1669 |
|
| 1670 |
a=acfg: <config-number> [<sel-cfg-list>] |
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Andreasen Standards Track [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
where <config-number> is an integer between 1 and 2^31-1 (both |
| 1682 |
included) that refers to the selected potential configuration. The |
| 1683 |
attribute can be provided only at the media level. |
| 1684 |
|
| 1685 |
The "acfg" attribute adheres to the <a href="./rfc4566">RFC 4566</a> "attribute" production, |
| 1686 |
with an att-value defined as follows: |
| 1687 |
|
| 1688 |
att-value = config-number [1*WSP sel-cfg-list] |
| 1689 |
;config-number defined in <a href="#section-3.5.1">Section 3.5.1</a>. |
| 1690 |
sel-cfg-list = sel-cfg *(1*WSP sel-cfg) |
| 1691 |
sel-cfg = sel-attribute-config / |
| 1692 |
sel-transport-protocol-config / |
| 1693 |
sel-extension-config |
| 1694 |
|
| 1695 |
sel-attribute-config = |
| 1696 |
"a=" [delete-attributes ":"] mo-att-cap-list |
| 1697 |
; defined in <a href="#section-3.5.1">Section 3.5.1</a>. |
| 1698 |
|
| 1699 |
sel-transport-protocol-config = |
| 1700 |
"t=" trpr-cap-num ; defined in <a href="#section-3.5.1">Section 3.5.1</a>. |
| 1701 |
|
| 1702 |
sel-extension-config = |
| 1703 |
ext-cap-name "=" 1*VCHAR ; defined in <a href="#section-3.5.1">Section 3.5.1</a>. |
| 1704 |
|
| 1705 |
Note that white space is not permitted before the config-number. |
| 1706 |
|
| 1707 |
The actual configuration ("a=acfg") attribute can be provided only at |
| 1708 |
the media level. There MUST NOT be more than one occurrence of an |
| 1709 |
actual configuration attribute within a given media description. |
| 1710 |
|
| 1711 |
Below, we provide an example of the "a=acfg" attribute (building on |
| 1712 |
the previous example with the potential configuration attribute): |
| 1713 |
|
| 1714 |
v=0 |
| 1715 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 1716 |
s= |
| 1717 |
c=IN IP4 192.0.2.2 |
| 1718 |
t=0 0 |
| 1719 |
m=audio 54568 RTP/SAVPF 0 |
| 1720 |
a=crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 1721 |
inline:WSJ+PSdFcGdUJShpX1ZjNzB4d1BINUAvLEw6UzF3|2^20|1:32 |
| 1722 |
a=acfg:1 t=4 a=1 |
| 1723 |
|
| 1724 |
It indicates that the answerer used an offer consisting of potential |
| 1725 |
configuration number 1 with transport protocol capability 4 from the |
| 1726 |
offer (RTP/SAVPF) and attribute capability 1 (the "crypto" |
| 1727 |
attribute). The answerer includes his own "crypto" attribute as |
| 1728 |
well. |
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Andreasen Standards Track [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Offer/Answer Model Extensions</span> |
| 1738 |
|
| 1739 |
In this section, we define extensions to the offer/answer model |
| 1740 |
defined in [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>] to allow for potential configurations to be |
| 1741 |
included in an offer, where they constitute alternative offers that |
| 1742 |
may be accepted by the answerer instead of the actual |
| 1743 |
configuration(s) included in the "m=" line(s). |
| 1744 |
|
| 1745 |
The procedures defined in the following subsections apply to both |
| 1746 |
unicast and multicast streams. |
| 1747 |
|
| 1748 |
<span class="h4"><a class="selflink" id="section-3.6.1" href="#section-3.6.1">3.6.1</a>. Generating the Initial Offer</span> |
| 1749 |
|
| 1750 |
An offerer that wants to use the SDP Capability Negotiation defined |
| 1751 |
in this document MUST include the following in the offer: |
| 1752 |
|
| 1753 |
o Zero or more attribute capability attributes. There MUST be an |
| 1754 |
attribute capability attribute ("a=acap") as defined in <a href="#section-3.4.1">Section</a> |
| 1755 |
<a href="#section-3.4.1">3.4.1</a> for each attribute name and associated value (if any) that |
| 1756 |
needs to be indicated as a capability in the offer. Attribute |
| 1757 |
capabilities may be included irrespective of whether or not they |
| 1758 |
are referenced by a potential configuration. |
| 1759 |
|
| 1760 |
Session-level attributes and associated values MUST be provided in |
| 1761 |
attribute capabilities only at the session level, whereas media- |
| 1762 |
level attributes and associated values can be provided in |
| 1763 |
attribute capabilities at either the media level or session level. |
| 1764 |
Attributes that are allowed at either the session or media level |
| 1765 |
can be provided in attribute capabilities at either level. |
| 1766 |
|
| 1767 |
o Zero or more transport protocol capability attributes. There MUST |
| 1768 |
be transport protocol capabilities as defined in <a href="#section-3.4.2">Section 3.4.2</a> |
| 1769 |
with values for each transport protocol that needs to be indicated |
| 1770 |
as a capability in the offer. |
| 1771 |
|
| 1772 |
Transport protocol capabilities may be included irrespective of |
| 1773 |
whether or not they are referenced by a potential configuration. |
| 1774 |
Transport protocols that apply to multiple media descriptions |
| 1775 |
SHOULD be provided as transport protocol capabilities at the |
| 1776 |
session level whereas transport protocols that apply only to a |
| 1777 |
specific media description ("m=" line), SHOULD be provided as |
| 1778 |
transport protocol capabilities within that particular media |
| 1779 |
description. In either case, there MUST NOT be more than a single |
| 1780 |
"a=tcap" attribute at the session level and a single "a=tcap" |
| 1781 |
attribute in each media description. |
| 1782 |
|
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Andreasen Standards Track [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
o Zero or more extension capability attributes. There MUST be one |
| 1794 |
or more extension capability attributes (as outlined in <a href="#section-3.4.3">Section</a> |
| 1795 |
<a href="#section-3.4.3">3.4.3</a>) for each extension capability that is referenced by a |
| 1796 |
potential configuration. Extension capability attributes that are |
| 1797 |
not referenced by a potential configuration can be provided as |
| 1798 |
well. |
| 1799 |
|
| 1800 |
o Zero or more potential configuration attributes. There MUST be |
| 1801 |
one or more potential configuration attributes ("a=pcfg"), as |
| 1802 |
defined in <a href="#section-3.5.1">Section 3.5.1</a>, in each media description where |
| 1803 |
alternative potential configurations are to be negotiated. Each |
| 1804 |
potential configuration attribute MUST adhere to the rules |
| 1805 |
provided in <a href="#section-3.5.1">Section 3.5.1</a> and the additional rules provided below. |
| 1806 |
|
| 1807 |
If the offerer requires support for one or more extensions (besides |
| 1808 |
the base protocol defined here), then the offerer MUST include one or |
| 1809 |
more "a=creq" attributes as follows: |
| 1810 |
|
| 1811 |
o If support for one or more capability negotiation extensions is |
| 1812 |
required for the entire session description, then option tags for |
| 1813 |
those extensions MUST be included in a single session-level "creq" |
| 1814 |
attribute. |
| 1815 |
|
| 1816 |
o For each media description that requires support for one or more |
| 1817 |
capability negotiation extensions not listed at the session level, |
| 1818 |
a single "creq" attribute containing all the required extensions |
| 1819 |
for that media description MUST be included within the media |
| 1820 |
description (in accordance with <a href="#section-3.3.2">Section 3.3.2</a>). |
| 1821 |
|
| 1822 |
Note that extensions that only need to be supported by a particular |
| 1823 |
potential configuration can use the "mandatory" extension prefix |
| 1824 |
("+") within the potential configuration (see <a href="#section-3.5.1">Section 3.5.1</a>). |
| 1825 |
|
| 1826 |
The offerer SHOULD furthermore include the following: |
| 1827 |
|
| 1828 |
o A supported capability negotiation extension attribute ("a=csup") |
| 1829 |
at the session level and/or media level as defined in <a href="#section-3.3.2">Section</a> |
| 1830 |
<a href="#section-3.3.2">3.3.2</a> for each capability negotiation extension supported by the |
| 1831 |
offerer and not included in a corresponding "a=creq" attribute |
| 1832 |
(i.e., at the session level or in the same media description). |
| 1833 |
Option tags provided in a "a=csup" attribute at the session level |
| 1834 |
indicate extensions supported for the entire session description, |
| 1835 |
whereas option tags provided in a "a=csup" attribute in a media |
| 1836 |
description indicate extensions supported for only that particular |
| 1837 |
media description. |
| 1838 |
|
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Andreasen Standards Track [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
Capabilities provided in an offer merely indicate what the offerer is |
| 1850 |
capable of doing. They do not constitute a commitment or even an |
| 1851 |
indication to use them. In contrast, each potential configuration |
| 1852 |
constitutes an alternative offer that the offerer would like to use. |
| 1853 |
The potential configurations MUST be used by the answerer to |
| 1854 |
negotiate and establish the session. |
| 1855 |
|
| 1856 |
The offerer MUST include one or more potential configuration |
| 1857 |
attributes ("a=pcfg") in each media description where the offerer |
| 1858 |
wants to provide alternative offers (in the form of potential |
| 1859 |
configurations). Each potential configuration attribute in a given |
| 1860 |
media description MUST contain a unique configuration number and |
| 1861 |
zero, one or more potential configuration lists, as described in |
| 1862 |
<a href="#section-3.5.1">Section 3.5.1</a>. Each potential configuration list MUST refer to |
| 1863 |
capabilities that are provided at the session level or within that |
| 1864 |
particular media description; otherwise, the potential configuration |
| 1865 |
is considered invalid. The base SDP Capability Negotiation framework |
| 1866 |
REQUIRES that potential configurations not reference any session- |
| 1867 |
level attribute capabilities that contain media-level-only |
| 1868 |
attributes; however, extensions may modify this behavior, as long as |
| 1869 |
it is fully backwards compatible with the base specification. |
| 1870 |
Furthermore, it is RECOMMENDED that potential configurations avoid |
| 1871 |
use of session-level capabilities whenever possible; refer to <a href="#section-3.5.1">Section</a> |
| 1872 |
<a href="#section-3.5.1">3.5.1</a>. |
| 1873 |
|
| 1874 |
The current actual configuration is included in the "m=" line (as |
| 1875 |
defined by [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]) and any associated parameters for the media |
| 1876 |
description (e.g., attribute ("a=") and bandwidth ("b=") lines). |
| 1877 |
Note that the actual configuration is by default the least-preferred |
| 1878 |
configuration, and hence the answerer will seek to negotiate use of |
| 1879 |
one of the potential configurations instead. If the offerer wishes a |
| 1880 |
different preference for the actual configuration, the offerer MUST |
| 1881 |
include a corresponding potential configuration with the relevant |
| 1882 |
configuration number (which indicates the relative preference between |
| 1883 |
potential configurations); this corresponding potential configuration |
| 1884 |
should simply duplicate the actual configuration. |
| 1885 |
|
| 1886 |
This can either be done implicitly (by not referencing any |
| 1887 |
capabilities), or explicitly (by providing and using capabilities |
| 1888 |
for the transport protocol and all the attributes that are part of |
| 1889 |
the actual configuration). The latter may help detect |
| 1890 |
intermediaries that modify the actual configuration but are not |
| 1891 |
SDP Capability Negotiation aware. |
| 1892 |
|
| 1893 |
Per [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>], once the offerer generates the offer, he must be |
| 1894 |
prepared to receive incoming media in accordance with that offer. |
| 1895 |
That rule applies here as well, but only for the actual |
| 1896 |
configurations provided in the offer: Media received by the offerer |
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Andreasen Standards Track [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
according to one of the potential configurations MAY be discarded, |
| 1906 |
until the offerer receives an answer indicating what the actual |
| 1907 |
selected configuration is. Once that answer is received, incoming |
| 1908 |
media MUST be processed in accordance with the actual selected |
| 1909 |
configuration indicated and the answer received (provided the |
| 1910 |
offer/answer exchange completed successfully). |
| 1911 |
|
| 1912 |
The above rule assumes that the offerer can determine whether |
| 1913 |
incoming media adheres to the actual configuration offered or one of |
| 1914 |
the potential configurations instead; this may not always be the |
| 1915 |
case. If the offerer wants to ensure he does not play out any |
| 1916 |
garbage, the offerer SHOULD discard all media received before the |
| 1917 |
answer SDP session description is received. Conversely, if the |
| 1918 |
offerer wants to avoid clipping, he SHOULD attempt to play any |
| 1919 |
incoming media as soon as it is received (at the risk of playing out |
| 1920 |
garbage). In either case, please note that this document does not |
| 1921 |
place any requirements on the offerer to process and play media |
| 1922 |
before answer. For further details, please refer to <a href="#section-3.9">Section 3.9</a>. |
| 1923 |
|
| 1924 |
<span class="h4"><a class="selflink" id="section-3.6.2" href="#section-3.6.2">3.6.2</a>. Generating the Answer</span> |
| 1925 |
|
| 1926 |
When receiving an offer, the answerer MUST check for the presence of |
| 1927 |
a required capability negotiation extension attribute ("a=creq") |
| 1928 |
provided at the session level. If one is found, then capability |
| 1929 |
negotiation MUST be performed. If none is found, then the answerer |
| 1930 |
MUST check each offered media description for the presence of a |
| 1931 |
required capability negotiation extension attribute ("a=creq") and |
| 1932 |
one or more potential configuration attributes ("a=pcfg"). |
| 1933 |
Capability negotiation MUST be performed for each media description |
| 1934 |
where either of those is present in accordance with the procedures |
| 1935 |
described below. |
| 1936 |
|
| 1937 |
The answerer MUST first ensure that it supports any required |
| 1938 |
capability negotiation extensions: |
| 1939 |
|
| 1940 |
o If a session-level "creq" attribute is provided, and it contains |
| 1941 |
an option tag that the answerer does not support, then the |
| 1942 |
answerer MUST NOT use any of the potential configuration |
| 1943 |
attributes provided for any of the media descriptions. Instead, |
| 1944 |
the normal offer/answer procedures MUST continue as per [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]. |
| 1945 |
Furthermore, the answerer MUST include a session-level supported |
| 1946 |
capability negotiation extensions attribute ("a=csup") with option |
| 1947 |
tags for the capability negotiation extensions supported by the |
| 1948 |
answerer. |
| 1949 |
|
| 1950 |
o If a media-level "creq" attribute is provided, and it contains an |
| 1951 |
option tag that the answerer does not support, then the answerer |
| 1952 |
MUST NOT use any of the potential configuration attributes |
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Andreasen Standards Track [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
provided for that particular media description. Instead, the |
| 1962 |
offer/answer procedures for that media description MUST continue |
| 1963 |
as per [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>] (SDP Capability Negotiation is still performed |
| 1964 |
for other media descriptions in the SDP session description). |
| 1965 |
Furthermore, the answerer MUST include a supported capability |
| 1966 |
negotiation extensions attribute ("a=csup") in that media |
| 1967 |
description with option tags for the capability negotiation |
| 1968 |
extensions supported by the answerer for that media description. |
| 1969 |
|
| 1970 |
Assuming all required capability negotiation extensions are |
| 1971 |
supported, the answerer now proceeds as follows. |
| 1972 |
|
| 1973 |
For each media description where capability negotiation is to be |
| 1974 |
performed (i.e., all required capability negotiation extensions are |
| 1975 |
supported and at least one valid potential configuration attribute is |
| 1976 |
present), the answerer MUST perform capability negotiation by using |
| 1977 |
the most preferred potential configuration that is valid to the |
| 1978 |
answerer, subject to any local policies. A potential configuration |
| 1979 |
is valid to the answerer if: |
| 1980 |
|
| 1981 |
1. It is in accordance with the syntax and semantics provided in |
| 1982 |
<a href="#section-3.5.1">Section 3.5.1</a>. |
| 1983 |
|
| 1984 |
2. It contains a configuration number that is unique within that |
| 1985 |
media description. |
| 1986 |
|
| 1987 |
3. All attribute capabilities referenced by the potential |
| 1988 |
configuration are valid themselves (as defined in <a href="#section-3.4.1">Section 3.4.1</a>) |
| 1989 |
and each of them is provided either at the session level or within |
| 1990 |
this particular media description. |
| 1991 |
|
| 1992 |
For session-level attribute capabilities referenced, the |
| 1993 |
attributes contained inside them MUST NOT be media-level-only |
| 1994 |
attributes. Note that the answerer can only determine this for |
| 1995 |
attributes supported by the answerer. If an attribute is not |
| 1996 |
supported, it will simply be ignored by the answerer and hence |
| 1997 |
will not trigger an "invalid" potential configuration. |
| 1998 |
|
| 1999 |
4. All transport protocol capabilities referenced by the potential |
| 2000 |
configuration are valid themselves (as defined in <a href="#section-3.4.2">Section 3.4.2</a>) |
| 2001 |
and each of them is furthermore provided either at the session |
| 2002 |
level or within this particular media description. |
| 2003 |
|
| 2004 |
5. All extension capabilities referenced by the potential |
| 2005 |
configuration and supported by the answerer are valid themselves |
| 2006 |
(as defined by that particular extension) and each of them are |
| 2007 |
furthermore provided either at the session level or within this |
| 2008 |
particular media description. Unknown or unsupported extension |
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Andreasen Standards Track [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
capabilities MUST be ignored, unless they are prefixed with the |
| 2018 |
plus ("+") sign, which indicates that the extension MUST be |
| 2019 |
supported in order to use that potential configuration. If the |
| 2020 |
extension is not supported, that potential configuration is not |
| 2021 |
valid to the answerer. |
| 2022 |
|
| 2023 |
The most preferred valid potential configuration in a media |
| 2024 |
description is the valid potential configuration with the lowest |
| 2025 |
configuration number. The answerer MUST now process the offer for |
| 2026 |
that media stream based on the most preferred valid potential |
| 2027 |
configuration. Conceptually, this entails the answerer constructing |
| 2028 |
an (internal) offer as follows. First, all capability negotiation |
| 2029 |
parameters from the offer SDP session description are removed, |
| 2030 |
thereby yielding an offer SDP session description with the actual |
| 2031 |
configuration as if SDP Capability Negotiation was not done in the |
| 2032 |
first place. Secondly, this actual configuration SDP session |
| 2033 |
description is modified as follows for each media stream offered, |
| 2034 |
based on the capability negotiation parameters included originally: |
| 2035 |
|
| 2036 |
o If a transport protocol capability is included in the potential |
| 2037 |
configuration, then it replaces the transport protocol provided in |
| 2038 |
the "m=" line for that media description. |
| 2039 |
|
| 2040 |
o If attribute capabilities are present with a delete-attributes |
| 2041 |
session indication ("-s") or media and session indication ("-ms"), |
| 2042 |
then all session-level attributes from the actual configuration |
| 2043 |
SDP session description MUST be deleted in the resulting potential |
| 2044 |
configuration SDP session description in accordance with the |
| 2045 |
procedures in <a href="#section-3.5.1">Section 3.5.1</a>. If attribute capabilities are |
| 2046 |
present with a delete-attributes media indication ("-m") or media |
| 2047 |
and session indication ("-ms"), then all attributes from the |
| 2048 |
actual configuration SDP session description inside this media |
| 2049 |
description MUST be deleted. |
| 2050 |
|
| 2051 |
o If a session-level attribute capability is included, the attribute |
| 2052 |
(and its associated value, if any) contained in it MUST be added |
| 2053 |
to the resulting SDP session description. All such added session- |
| 2054 |
level attributes MUST be listed before the session-level |
| 2055 |
attributes that were initially present in the SDP session |
| 2056 |
description. Furthermore, the added session-level attributes MUST |
| 2057 |
be added in the order they were provided in the potential |
| 2058 |
configuration (see also <a href="#section-3.5.1">Section 3.5.1</a>). |
| 2059 |
|
| 2060 |
This allows for attributes with implicit preference ordering to |
| 2061 |
be added in the desired order; the "crypto" attribute [<a href="./rfc4568" title=""Session Description Protocol (SDP) Security Descriptions for Media Streams"">RFC4568</a>] |
| 2062 |
is one such example. |
| 2063 |
|
| 2064 |
|
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Andreasen Standards Track [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
o If a media-level attribute capability is included, then the |
| 2074 |
attribute (and its associated value, if any) MUST be added to the |
| 2075 |
resulting SDP session description within the media description in |
| 2076 |
question. All such added media-level attributes MUST be listed |
| 2077 |
before the media-level attributes that were initially present in |
| 2078 |
the media description in question. Furthermore, the added media- |
| 2079 |
level attributes MUST be added in the order they were provided in |
| 2080 |
the potential configuration (see also <a href="#section-3.5.1">Section 3.5.1</a>). |
| 2081 |
|
| 2082 |
o If a supported extension capability is included, then it MUST be |
| 2083 |
processed in accordance with the rules provided for that |
| 2084 |
particular extension capability. |
| 2085 |
|
| 2086 |
The above steps MUST be performed exactly once per potential |
| 2087 |
configuration, i.e., there MUST NOT be any recursive processing of |
| 2088 |
any additional capability negotiation parameters that may (illegally) |
| 2089 |
have been nested inside capabilities themselves. |
| 2090 |
|
| 2091 |
As an example of this, consider the (illegal) attribute capability |
| 2092 |
|
| 2093 |
a=acap:1 acap:2 foo:a |
| 2094 |
|
| 2095 |
The resulting potential configuration SDP session description will, |
| 2096 |
after the above processing has been done, contain the attribute |
| 2097 |
capability |
| 2098 |
|
| 2099 |
a=acap:2 foo:a |
| 2100 |
|
| 2101 |
However, since we do not perform any recursive processing of |
| 2102 |
capability negotiation parameters, this second attribute capability |
| 2103 |
parameter will not be processed by the offer/answer procedure. |
| 2104 |
Instead, it will simply appear as a (useless) attribute in the SDP |
| 2105 |
session description that will be ignored by further processing. |
| 2106 |
|
| 2107 |
Note that a transport protocol from the potential configuration |
| 2108 |
replaces the transport protocol in the actual configuration, but an |
| 2109 |
attribute capability from the potential configuration is simply added |
| 2110 |
to the actual configuration. In some cases, this can result in |
| 2111 |
having one or more meaningless attributes in the resulting potential |
| 2112 |
configuration SDP session description, or worse, ambiguous or |
| 2113 |
potentially even illegal attributes. Use of delete-attributes for |
| 2114 |
the session- and/or media-level attributes MUST be done to avoid such |
| 2115 |
scenarios. Nevertheless, it is RECOMMENDED that implementations |
| 2116 |
ignore meaningless attributes that may result from potential |
| 2117 |
configurations. |
| 2118 |
|
| 2119 |
|
| 2120 |
|
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Andreasen Standards Track [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
For example, if the actual configuration was using Secure RTP and |
| 2130 |
included an "a=crypto" attribute for the SRTP keying material, |
| 2131 |
then use of a potential configuration that uses plain RTP would |
| 2132 |
make the "crypto" attribute meaningless. The answerer may or may |
| 2133 |
not ignore such a meaningless attribute. The offerer can here |
| 2134 |
ensure correct operation by using delete-attributes to remove the |
| 2135 |
"crypto" attribute (but will then need to provide attribute |
| 2136 |
capabilities to reconstruct the SDP session description with the |
| 2137 |
necessary attributes deleted, e.g., rtpmaps). |
| 2138 |
|
| 2139 |
Also note, that while it is permissible to include media-level |
| 2140 |
attribute capabilities at the session level, the base SDP Capability |
| 2141 |
Negotiation framework defined here does not define any procedures for |
| 2142 |
use of them, i.e., the answerer effectively ignores them. |
| 2143 |
|
| 2144 |
Please refer to <a href="#section-3.6.2.1">Section 3.6.2.1</a> for examples of how the answerer may |
| 2145 |
conceptually "see" the resulting offered alternative potential |
| 2146 |
configurations. |
| 2147 |
|
| 2148 |
The answerer MUST check that he supports all mandatory attribute |
| 2149 |
capabilities from the potential configuration (if any), the transport |
| 2150 |
protocol capability (if any) from the potential configuration, and |
| 2151 |
all mandatory extension capabilities from the potential configuration |
| 2152 |
(if any). If he does not, the answerer MUST proceed to the second |
| 2153 |
most preferred valid potential configuration for the media |
| 2154 |
description, etc. |
| 2155 |
|
| 2156 |
o In the case of attribute capabilities, support implies that the |
| 2157 |
attribute name contained in the capability is supported and it can |
| 2158 |
(and will) be negotiated successfully in the offer/answer exchange |
| 2159 |
with the value provided. This does not necessarily imply that the |
| 2160 |
value provided is supported in its entirety. For example, the |
| 2161 |
"a=fmtp" parameter is often provided with one or more values in a |
| 2162 |
list, where the offerer and answerer negotiate use of some subset |
| 2163 |
of the values provided. Other attributes may include mandatory |
| 2164 |
and optional parts to their values; support for the mandatory part |
| 2165 |
is all that is required here. |
| 2166 |
|
| 2167 |
A side effect of the above rule is that whenever an "fmtp" or |
| 2168 |
"rtpmap" parameter is provided as a mandatory attribute |
| 2169 |
capability, the corresponding media format (codec) must be |
| 2170 |
supported and use of it negotiated successfully. If this is |
| 2171 |
not the offerer's intent, the corresponding attribute |
| 2172 |
capabilities must be listed as optional instead. |
| 2173 |
|
| 2174 |
|
| 2175 |
|
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Andreasen Standards Track [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
o In the case of transport protocol capabilities, support implies |
| 2186 |
that the transport protocol contained in the capability is |
| 2187 |
supported and the transport protocol can (and will) be negotiated |
| 2188 |
successfully in the offer/answer exchange. |
| 2189 |
|
| 2190 |
o In the case of extension capabilities, the extension MUST define |
| 2191 |
the rules for when the extension capability is considered |
| 2192 |
supported and those rules MUST be satisfied. |
| 2193 |
|
| 2194 |
If the answerer has exhausted all potential configurations for the |
| 2195 |
media description, without finding a valid one that is also |
| 2196 |
supported, then the answerer MUST process the offered media stream |
| 2197 |
based on the actual configuration plus any session-level attributes |
| 2198 |
added by a valid and supported potential configuration from another |
| 2199 |
media description in the offered SDP session description. |
| 2200 |
|
| 2201 |
The above process describes potential configuration selection as a |
| 2202 |
per-media-stream process. Inter-media stream coordination of |
| 2203 |
selected potential configurations however is required in some cases. |
| 2204 |
First of all, session-level attributes added by a potential |
| 2205 |
configuration for one media description MUST NOT cause any problems |
| 2206 |
for potential configurations selected by other media descriptions in |
| 2207 |
the offer SDP session description. If the session-level attributes |
| 2208 |
are mandatory, then those session-level attributes MUST furthermore |
| 2209 |
be supported by the session as a whole (i.e., all the media |
| 2210 |
descriptions if relevant). As mentioned earlier, this adds |
| 2211 |
additional complexity to the overall processing and hence it is |
| 2212 |
RECOMMENDED not to use session-level attribute capabilities in |
| 2213 |
potential configurations, unless absolutely necessary. |
| 2214 |
|
| 2215 |
Once the answerer has selected a valid and supported offered |
| 2216 |
potential configuration for all of the media streams (or has fallen |
| 2217 |
back to the actual configuration plus any added session attributes), |
| 2218 |
the answerer MUST generate a valid virtual answer SDP session |
| 2219 |
description based on the selected potential configuration SDP session |
| 2220 |
description, as "seen" by the answerer using normal offer/answer |
| 2221 |
rules (see <a href="#section-3.6.2.1">Section 3.6.2.1</a> for examples). The actual answer SDP |
| 2222 |
session description is formed from the virtual answer SDP session |
| 2223 |
description as follows: if the answerer selected one of the potential |
| 2224 |
configurations in a media description, the answerer MUST include an |
| 2225 |
actual configuration attribute ("a=acfg") within that media |
| 2226 |
description. The "a=acfg" attribute MUST identify the configuration |
| 2227 |
number for the selected potential configuration as well as the actual |
| 2228 |
parameters that were used from that potential configuration; if the |
| 2229 |
potential configuration included alternatives, the selected |
| 2230 |
alternatives only MUST be included. Only the known and supported |
| 2231 |
parameters will be included. Unknown or unsupported parameters MUST |
| 2232 |
NOT be included in the actual configuration attribute. In the case |
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Andreasen Standards Track [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
of attribute capabilities, only the known and supported capabilities |
| 2242 |
are included; unknown or unsupported attribute capabilities MUST NOT |
| 2243 |
be included. |
| 2244 |
|
| 2245 |
If the answerer supports one or more capability negotiation |
| 2246 |
extensions that were not included in a required capability |
| 2247 |
negotiation extensions attribute in the offer, then the answerer |
| 2248 |
SHOULD furthermore include a supported capability negotiation |
| 2249 |
attribute ("a=csup") at the session level with option tags for the |
| 2250 |
extensions supported across media streams. Also, if the answerer |
| 2251 |
supports one or more capability negotiation extensions for only |
| 2252 |
particular media descriptions, then a supported capability |
| 2253 |
negotiation attribute with those option tags SHOULD be included |
| 2254 |
within each relevant media description. The required capability |
| 2255 |
negotiation attribute ("a=creq") MUST NOT be used in an answer. |
| 2256 |
|
| 2257 |
The offerer's originally provided actual configuration is contained |
| 2258 |
in the offer media description's "m=" line (and associated |
| 2259 |
parameters). The answerer MAY send media to the offerer in |
| 2260 |
accordance with that actual configuration as soon as it receives the |
| 2261 |
offer; however, it MUST NOT send media based on that actual |
| 2262 |
configuration if it selects an alternative potential configuration. |
| 2263 |
If the answerer selects one of the potential configurations, then the |
| 2264 |
answerer MAY immediately start to send media to the offerer in |
| 2265 |
accordance with the selected potential configuration; however, the |
| 2266 |
offerer MAY discard such media or play out garbage until the offerer |
| 2267 |
receives the answer. Please refer to <a href="#section-3.9">Section 3.9</a>. for additional |
| 2268 |
considerations and possible alternative solutions outside the base |
| 2269 |
SDP Capability Negotiation framework. |
| 2270 |
|
| 2271 |
If the answerer selected a potential configuration instead of the |
| 2272 |
actual configuration, then it is RECOMMENDED that the answerer send |
| 2273 |
back an answer SDP session description as soon as possible. This |
| 2274 |
minimizes the risk of having media discarded or played out as garbage |
| 2275 |
by the offerer. In the case of SIP [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] without any extensions, |
| 2276 |
this implies that if the offer was received in an INVITE message, |
| 2277 |
then the answer SDP session description should be provided in the |
| 2278 |
first non-100 provisional response sent back (per <a href="./rfc3261">RFC 3261</a>, the |
| 2279 |
answer would need to be repeated in the 200 response as well, unless |
| 2280 |
a relevant extension such as [<a href="./rfc3262" title=""Reliability of Provisional Responses in Session Initiation Protocol (SIP)"">RFC3262</a>] is being used). |
| 2281 |
|
| 2282 |
|
| 2283 |
|
| 2284 |
|
| 2285 |
|
| 2286 |
|
| 2287 |
|
| 2288 |
|
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
<span class="grey">Andreasen Standards Track [Page 41]</span></pre> |
| 2293 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2294 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2295 |
|
| 2296 |
|
| 2297 |
<span class="h5"><a class="selflink" id="section-3.6.2.1" href="#section-3.6.2.1">3.6.2.1</a>. Example Views of Potential Configurations</span> |
| 2298 |
|
| 2299 |
The following examples illustrate how the answerer may conceptually |
| 2300 |
"see" a potential configuration. Consider the following offered SDP |
| 2301 |
session description: |
| 2302 |
|
| 2303 |
v=0 |
| 2304 |
o=alice 2891092738 2891092738 IN IP4 lost.example.com |
| 2305 |
s= |
| 2306 |
t=0 0 |
| 2307 |
c=IN IP4 lost.example.com |
| 2308 |
a=tool:foo |
| 2309 |
a=acap:1 key-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAyO... |
| 2310 |
a=tcap:1 RTP/SAVP RTP/AVP |
| 2311 |
m=audio 59000 RTP/AVP 98 |
| 2312 |
a=rtpmap:98 AMR/8000 |
| 2313 |
a=acap:2 crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 2314 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 2315 |
a=pcfg:1 t=1 a=1|2 |
| 2316 |
m=video 52000 RTP/AVP 31 |
| 2317 |
a=rtpmap:31 H261/90000 |
| 2318 |
a=acap:3 crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 2319 |
inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 |
| 2320 |
a=pcfg:1 t=1 a=1|3 |
| 2321 |
|
| 2322 |
This particular SDP session description offers an audio stream and a |
| 2323 |
video stream, each of which can either use plain RTP (actual |
| 2324 |
configuration) or Secure RTP (potential configuration). Furthermore, |
| 2325 |
two different keying mechanisms are offered, namely session-level Key |
| 2326 |
Management Extensions using MIKEY (attribute capability 1) and media- |
| 2327 |
level SDP security descriptions (attribute capabilities 2 and 3). |
| 2328 |
There are several potential configurations here, however, below we |
| 2329 |
show the one the answerer "sees" when using potential configuration 1 |
| 2330 |
for both audio and video, and furthermore using attribute capability |
| 2331 |
1 (MIKEY) for both (we have removed all the capability negotiation |
| 2332 |
attributes for clarity): |
| 2333 |
|
| 2334 |
v=0 |
| 2335 |
o=alice 2891092738 2891092738 IN IP4 lost.example.com |
| 2336 |
s= |
| 2337 |
t=0 0 |
| 2338 |
c=IN IP4 lost.example.com |
| 2339 |
a=tool:foo |
| 2340 |
a=key-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAyO... |
| 2341 |
m=audio 59000 RTP/SAVP 98 |
| 2342 |
a=rtpmap:98 AMR/8000 |
| 2343 |
m=video 52000 RTP/SAVP 31 |
| 2344 |
a=rtpmap:31 H261/90000 |
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
<span class="grey">Andreasen Standards Track [Page 42]</span></pre> |
| 2349 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2350 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2351 |
|
| 2352 |
|
| 2353 |
Note that the transport protocol in the media descriptions indicate |
| 2354 |
use of Secure RTP. |
| 2355 |
|
| 2356 |
Below, we show the offer the answerer "sees" when using potential |
| 2357 |
configuration 1 for both audio and video and furthermore using |
| 2358 |
attribute capability 2 and 3, respectively, (SDP security |
| 2359 |
descriptions) for the audio and video stream -- note the order in |
| 2360 |
which the resulting attributes are provided: |
| 2361 |
|
| 2362 |
v=0 |
| 2363 |
o=alice 2891092738 2891092738 IN IP4 lost.example.com |
| 2364 |
s= |
| 2365 |
t=0 0 |
| 2366 |
c=IN IP4 lost.example.com |
| 2367 |
a=tool:foo |
| 2368 |
m=audio 59000 RTP/SAVP 98 |
| 2369 |
a=crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 2370 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 2371 |
a=rtpmap:98 AMR/8000 |
| 2372 |
m=video 52000 RTP/SAVP 31 |
| 2373 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 2374 |
inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 |
| 2375 |
a=rtpmap:31 H261/90000 |
| 2376 |
|
| 2377 |
Again, note that the transport protocol in the media descriptions |
| 2378 |
indicate use of Secure RTP. |
| 2379 |
|
| 2380 |
And finally, we show the offer the answerer "sees" when using |
| 2381 |
potential configuration 1 with attribute capability 1 (MIKEY) for the |
| 2382 |
audio stream, and potential configuration 1 with attribute capability |
| 2383 |
3 (SDP security descriptions) for the video stream: |
| 2384 |
|
| 2385 |
v=0 |
| 2386 |
o=alice 2891092738 2891092738 IN IP4 lost.example.com |
| 2387 |
s= |
| 2388 |
t=0 0 |
| 2389 |
c=IN IP4 lost.example.com |
| 2390 |
a=key-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAyO... |
| 2391 |
a=tool:foo |
| 2392 |
m=audio 59000 RTP/SAVP 98 |
| 2393 |
a=rtpmap:98 AMR/8000 |
| 2394 |
m=video 52000 RTP/SAVP 31 |
| 2395 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 2396 |
inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 |
| 2397 |
a=rtpmap:31 H261/90000 |
| 2398 |
|
| 2399 |
|
| 2400 |
|
| 2401 |
|
| 2402 |
|
| 2403 |
|
| 2404 |
<span class="grey">Andreasen Standards Track [Page 43]</span></pre> |
| 2405 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2406 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2407 |
|
| 2408 |
|
| 2409 |
<span class="h4"><a class="selflink" id="section-3.6.3" href="#section-3.6.3">3.6.3</a>. Offerer Processing of the Answer</span> |
| 2410 |
|
| 2411 |
When the offerer attempted to use SDP Capability Negotiation in the |
| 2412 |
offer, the offerer MUST examine the answer for actual use of SDP |
| 2413 |
Capability Negotiation. |
| 2414 |
|
| 2415 |
For each media description where the offerer included a potential |
| 2416 |
configuration attribute ("a=pcfg"), the offerer MUST first examine |
| 2417 |
that media description for the presence of a valid actual |
| 2418 |
configuration attribute ("a=acfg"). An actual configuration |
| 2419 |
attribute is valid if: |
| 2420 |
|
| 2421 |
o it refers to a potential configuration that was present in the |
| 2422 |
corresponding offer, and |
| 2423 |
|
| 2424 |
o it contains the actual parameters that were used from that |
| 2425 |
potential configuration; if the potential configuration included |
| 2426 |
alternatives, the selected alternatives only MUST be included. |
| 2427 |
Note that the answer will include only parameters and attribute |
| 2428 |
capabilities that are known and supported by the answerer, as |
| 2429 |
described in <a href="#section-3.6.2">Section 3.6.2</a>. |
| 2430 |
|
| 2431 |
If a valid actual configuration attribute is not present in a media |
| 2432 |
description, then the offerer MUST process the answer SDP session |
| 2433 |
description for that media stream per the normal offer/answer rules |
| 2434 |
defined in [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]. However, if a valid one is found, the offerer |
| 2435 |
MUST instead process the answer as follows: |
| 2436 |
|
| 2437 |
o The actual configuration attribute specifies which of the |
| 2438 |
potential configurations was used by the answerer to generate the |
| 2439 |
answer for this media stream. This includes all the supported |
| 2440 |
attribute capabilities and the transport capabilities referenced |
| 2441 |
by the potential configuration selected, where the attribute |
| 2442 |
capabilities have any associated delete-attributes included. |
| 2443 |
Extension capabilities supported by the answerer are included as |
| 2444 |
well. |
| 2445 |
|
| 2446 |
o The offerer MUST now process the answer in accordance with the |
| 2447 |
rules in [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>], except that it must be done as if the offer |
| 2448 |
consisted of the selected potential configuration instead of the |
| 2449 |
original actual configuration, including any transport protocol |
| 2450 |
changes in the media ("m=") line(s), attributes added and deleted |
| 2451 |
by the potential configuration at the media and session level, and |
| 2452 |
any extensions used. If this derived answer is not a valid answer |
| 2453 |
to the potential configuration offer selected by the answerer, the |
| 2454 |
offerer MUST instead continue further processing as it would have |
| 2455 |
for a regular offer/answer exchange, where the answer received |
| 2456 |
does not adhere to the rules of [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]. |
| 2457 |
|
| 2458 |
|
| 2459 |
|
| 2460 |
<span class="grey">Andreasen Standards Track [Page 44]</span></pre> |
| 2461 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2462 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2463 |
|
| 2464 |
|
| 2465 |
If the offer/answer exchange was successful, and if the answerer |
| 2466 |
selected one of the potential configurations from the offer as the |
| 2467 |
actual configuration, and the selected potential configuration |
| 2468 |
differs from the actual configuration in the offer (the "m=", "a=", |
| 2469 |
etc., lines), then the offerer SHOULD initiate another offer/answer |
| 2470 |
exchange. This second offer/answer exchange will not modify the |
| 2471 |
session in any way; however, it will help intermediaries (e.g., |
| 2472 |
middleboxes), which look at the SDP session description but do not |
| 2473 |
support the capability negotiation extensions, understand the details |
| 2474 |
of the media stream(s) that were actually negotiated. This new offer |
| 2475 |
MUST contain the selected potential configuration as the actual |
| 2476 |
configuration, i.e., with the actual configuration used in the "m=" |
| 2477 |
line and any other relevant attributes, bandwidth parameters, etc. |
| 2478 |
|
| 2479 |
Note that, per normal offer/answer rules, the second offer/answer |
| 2480 |
exchange still needs to update the version number in the "o=" line |
| 2481 |
(<sess-version> in [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>]). Attribute lines carrying keying |
| 2482 |
material SHOULD repeat the keys from the previous offer, unless |
| 2483 |
re-keying is necessary, e.g., due to a previously forked SIP INVITE |
| 2484 |
request. Please refer to <a href="#section-3.12">Section 3.12</a> for additional considerations |
| 2485 |
related to intermediaries. |
| 2486 |
|
| 2487 |
<span class="h4"><a class="selflink" id="section-3.6.4" href="#section-3.6.4">3.6.4</a>. Modifying the Session</span> |
| 2488 |
|
| 2489 |
Capabilities and potential configurations may be included in |
| 2490 |
subsequent offers as defined in <a href="./rfc3264#section-8">[RFC3264], Section 8</a>. The procedure |
| 2491 |
for doing so is similar to that described above with the answer |
| 2492 |
including an indication of the actual selected configuration used by |
| 2493 |
the answerer. |
| 2494 |
|
| 2495 |
If the answer indicates use of a potential configuration from the |
| 2496 |
offer, then the guidelines provided in <a href="#section-3.6.3">Section 3.6.3</a> for doing a |
| 2497 |
second offer/answer exchange using that potential configuration as |
| 2498 |
the actual configuration apply. |
| 2499 |
|
| 2500 |
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Interactions with ICE</span> |
| 2501 |
|
| 2502 |
Interactive Connectivity Establishment (ICE) [<a href="./rfc5245" title=""Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols"">RFC5245</a>] provides a |
| 2503 |
mechanism for verifying connectivity between two endpoints by sending |
| 2504 |
Session Traversal Utilities for NAT (STUN) messages directly between |
| 2505 |
the media endpoints. The basic ICE specification [<a href="./rfc5245" title=""Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols"">RFC5245</a>] is only |
| 2506 |
defined to support UDP-based connectivity; however, it allows for |
| 2507 |
extensions to support other transport protocols, such as TCP, which |
| 2508 |
is being specified in [<a href="#ref-ICETCP" title=""TCP Candidates with Interactive Connectivity Establishment (ICE)"">ICETCP</a>]. ICE defines a new "a=candidate" |
| 2509 |
attribute, which, among other things, indicates the possible |
| 2510 |
transport protocol(s) to use and then associates a priority with each |
| 2511 |
of them. The most preferred transport protocol that *successfully* |
| 2512 |
verifies connectivity will end up being used. |
| 2513 |
|
| 2514 |
|
| 2515 |
|
| 2516 |
<span class="grey">Andreasen Standards Track [Page 45]</span></pre> |
| 2517 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span> |
| 2518 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2519 |
|
| 2520 |
|
| 2521 |
When using ICE, it is thus possible that the transport protocol that |
| 2522 |
will be used differs from what is specified in the "m=" line. Since |
| 2523 |
both ICE and SDP Capability Negotiation may specify alternative |
| 2524 |
transport protocols, there is a potentially unintended interaction |
| 2525 |
when using these together. |
| 2526 |
|
| 2527 |
We provide the following guidelines for addressing that. |
| 2528 |
|
| 2529 |
There are two basic scenarios to consider: |
| 2530 |
|
| 2531 |
1) A particular media stream can run over different transport |
| 2532 |
protocols (e.g., UDP, TCP, or TCP/TLS), and the intent is simply |
| 2533 |
to use the one that works (in the preference order specified). |
| 2534 |
|
| 2535 |
2) A particular media stream can run over different transport |
| 2536 |
protocols (e.g., UDP, TCP, or TCP/TLS) and the intent is to have |
| 2537 |
the negotiation process decide which one to use (e.g., T.38 over |
| 2538 |
TCP or UDP). |
| 2539 |
|
| 2540 |
In scenario 1, there should be ICE "a=candidate" attributes for UDP, |
| 2541 |
TCP, etc., but otherwise nothing special in the potential |
| 2542 |
configuration attributes to indicate the desire to use different |
| 2543 |
transport protocols (e.g., UDP, or TCP). The ICE procedures |
| 2544 |
essentially cover the capability negotiation required (by having the |
| 2545 |
answerer select something it supports and then use of trial and error |
| 2546 |
connectivity checks). |
| 2547 |
|
| 2548 |
Scenario 2 does not require a need to support or use ICE. Instead, |
| 2549 |
we simply use transport protocol capabilities and potential |
| 2550 |
configuration attributes to indicate the desired outcome. |
| 2551 |
|
| 2552 |
The scenarios may be combined, e.g., by offering potential |
| 2553 |
configuration alternatives where some of them can support only one |
| 2554 |
transport protocol (e.g., UDP), whereas others can support multiple |
| 2555 |
transport protocols (e.g., UDP or TCP). In that case, there is a |
| 2556 |
need for tight control over the ICE candidates that will be used for |
| 2557 |
a particular configuration, yet the actual configuration may want to |
| 2558 |
use all of the ICE candidates. In that case, the ICE candidate |
| 2559 |
attributes can be defined as attribute capabilities and the relevant |
| 2560 |
ones should then be included in the proper potential configurations |
| 2561 |
(for example, candidate attributes for UDP only for potential |
| 2562 |
configurations that are restricted to UDP, whereas there could be |
| 2563 |
candidate attributes for UDP, TCP, and TCP/TLS for potential |
| 2564 |
configurations that can use all three). Furthermore, use of the |
| 2565 |
delete-attributes in a potential configuration can be used to ensure |
| 2566 |
that ICE will not end up using a transport protocol that is not |
| 2567 |
desired for a particular configuration. |
| 2568 |
|
| 2569 |
|
| 2570 |
|
| 2571 |
|
| 2572 |
<span class="grey">Andreasen Standards Track [Page 46]</span></pre> |
| 2573 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span> |
| 2574 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2575 |
|
| 2576 |
|
| 2577 |
SDP Capability Negotiation recommends use of a second offer/answer |
| 2578 |
exchange when the negotiated actual configuration was one of the |
| 2579 |
potential configurations from the offer (see <a href="#section-3.6.3">Section 3.6.3</a>). |
| 2580 |
Similarly, ICE requires use of a second offer/answer exchange if the |
| 2581 |
chosen candidate is not the same as the one in the m/c-line from the |
| 2582 |
offer. When ICE and capability negotiation are used at the same |
| 2583 |
time, the two secondary offer/answer exchanges SHOULD be combined to |
| 2584 |
a single one. |
| 2585 |
|
| 2586 |
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Interactions with SIP Option Tags</span> |
| 2587 |
|
| 2588 |
SIP [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] allows for SIP extensions to define a SIP option tag |
| 2589 |
that identifies the SIP extension. Support for one or more such |
| 2590 |
extensions can be indicated by use of the SIP Supported header, and |
| 2591 |
required support for one or more such extensions can be indicated by |
| 2592 |
use of the SIP Require header. The "a=csup" and "a=creq" attributes |
| 2593 |
defined by the SDP Capability Negotiation framework are similar, |
| 2594 |
except that support for these two attributes by themselves cannot be |
| 2595 |
guaranteed (since they are specified as extensions to the SDP |
| 2596 |
specification [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] itself). |
| 2597 |
|
| 2598 |
SIP extensions with associated option tags can introduce enhancements |
| 2599 |
to not only SIP, but also SDP. This is for example the case for SIP |
| 2600 |
preconditions defined in [<a href="./rfc3312" title=""Integration of Resource Management and Session Initiation Protocol (SIP)"">RFC3312</a>]. When using SDP Capability |
| 2601 |
Negotiation, some potential configurations may include certain SDP |
| 2602 |
extensions, whereas others may not. Since the purpose of the SDP |
| 2603 |
Capability Negotiation is to negotiate a session based on the |
| 2604 |
features supported by both sides, use of the SIP Require header for |
| 2605 |
such extensions may not produce the desired result. For example, if |
| 2606 |
one potential configuration requires SIP preconditions support, |
| 2607 |
another does not, and the answerer does not support preconditions, |
| 2608 |
then use of the SIP Require header for preconditions would result in |
| 2609 |
a session failure, in spite of the fact that a valid and supported |
| 2610 |
potential configuration was included in the offer. |
| 2611 |
|
| 2612 |
In general, this can be alleviated by use of mandatory and optional |
| 2613 |
attribute capabilities in a potential configuration. There are |
| 2614 |
however cases where permissible SDP values are tied to the use of the |
| 2615 |
SIP Require header. SIP preconditions [<a href="./rfc3312" title=""Integration of Resource Management and Session Initiation Protocol (SIP)"">RFC3312</a>] is one such example, |
| 2616 |
where preconditions with a "mandatory" strength-tag can only be used |
| 2617 |
when a SIP Require header with the SIP option tag "precondition" is |
| 2618 |
included. Future SIP extensions that may want to use the SDP |
| 2619 |
Capability Negotiation framework should avoid such coupling. |
| 2620 |
|
| 2621 |
|
| 2622 |
|
| 2623 |
|
| 2624 |
|
| 2625 |
|
| 2626 |
|
| 2627 |
|
| 2628 |
<span class="grey">Andreasen Standards Track [Page 47]</span></pre> |
| 2629 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span> |
| 2630 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2631 |
|
| 2632 |
|
| 2633 |
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. Processing Media before Answer</span> |
| 2634 |
|
| 2635 |
The offer/answer model [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>] requires an offerer to be able to |
| 2636 |
receive media in accordance with the offer prior to receiving the |
| 2637 |
answer. This property is retained with the SDP Capability |
| 2638 |
Negotiation extensions defined here, but only when the actual |
| 2639 |
configuration is selected by the answerer. If a potential |
| 2640 |
configuration is chosen, the offerer may decide not to process any |
| 2641 |
media received before the answer is received. This may lead to |
| 2642 |
clipping. Consequently, the SDP Capability Negotiation framework |
| 2643 |
recommends sending back an answer SDP session description as soon as |
| 2644 |
possible. |
| 2645 |
|
| 2646 |
The issue can be resolved by introducing a three-way handshake. In |
| 2647 |
the case of SIP, this can, for example, be done by defining a |
| 2648 |
precondition [<a href="./rfc3312" title=""Integration of Resource Management and Session Initiation Protocol (SIP)"">RFC3312</a>] for capability negotiation (or by using an |
| 2649 |
existing precondition that is known to generate a second offer/answer |
| 2650 |
exchange before proceeding with the session). However, preconditions |
| 2651 |
are often viewed as complicated to implement and they may add to |
| 2652 |
overall session establishment delay by requiring an extra |
| 2653 |
offer/answer exchange. |
| 2654 |
|
| 2655 |
An alternative three-way handshake can be performed by use of ICE |
| 2656 |
[<a href="./rfc5245" title=""Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols"">RFC5245</a>]. When ICE is being used, and the answerer receives a STUN |
| 2657 |
Binding Request for any one of the accepted media streams from the |
| 2658 |
offerer, the answerer knows the offer has received his answer. At |
| 2659 |
that point, the answerer knows that the offerer will be able to |
| 2660 |
process incoming media according to the negotiated configuration and |
| 2661 |
hence he can start sending media without the risk of the offerer |
| 2662 |
either discarding it or playing garbage. |
| 2663 |
|
| 2664 |
Please note that, the above considerations notwithstanding, this |
| 2665 |
document does not place any requirements on the offerer to process |
| 2666 |
and play media before answer; it merely provides recommendations for |
| 2667 |
how to ensure that media sent by the answerer and received by the |
| 2668 |
offerer prior to receiving the answer can in fact be rendered by the |
| 2669 |
offerer. |
| 2670 |
|
| 2671 |
In some use cases, a three-way handshake is not needed. An example |
| 2672 |
is when the offerer does not need information from the answer, such |
| 2673 |
as keying material in the SDP session description, in order to |
| 2674 |
process incoming media. The SDP Capability Negotiation framework |
| 2675 |
does not define any such solutions; however, extensions may do so. |
| 2676 |
For example, one technique proposed for best-effort SRTP in [<a href="#ref-BESRTP" title=""Session Description Protocol (SDP) Offer/Answer Negotiation For Best-Effort Secure Real-Time Transport Protocol"">BESRTP</a>] |
| 2677 |
is to provide different RTP payload type mappings for different |
| 2678 |
transport protocols used, outside of the actual configuration, while |
| 2679 |
still allowing them to be used by the answerer (exchange of keying |
| 2680 |
|
| 2681 |
|
| 2682 |
|
| 2683 |
|
| 2684 |
<span class="grey">Andreasen Standards Track [Page 48]</span></pre> |
| 2685 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span> |
| 2686 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2687 |
|
| 2688 |
|
| 2689 |
material is still needed, e.g., inband). The basic SDP Capability |
| 2690 |
Negotiation framework defined here does not include the ability to do |
| 2691 |
so; however, extensions that enable that may be defined. |
| 2692 |
|
| 2693 |
<span class="h3"><a class="selflink" id="section-3.10" href="#section-3.10">3.10</a>. Indicating Bandwidth Usage</span> |
| 2694 |
|
| 2695 |
The amount of bandwidth used for a particular media stream depends on |
| 2696 |
the negotiated codecs, transport protocol and other parameters. For |
| 2697 |
example the use of Secure RTP [<a href="./rfc3711" title=""The Secure Real-time Transport Protocol (SRTP)"">RFC3711</a>] with integrity protection |
| 2698 |
requires more bandwidth than plain RTP [<a href="./rfc3551" title=""RTP Profile for Audio and Video Conferences with Minimal Control"">RFC3551</a>]. SDP defines the |
| 2699 |
bandwidth ("b=") parameter to indicate the proposed bandwidth for the |
| 2700 |
session or media stream. |
| 2701 |
|
| 2702 |
In SDP, as defined by [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>], each media description contains one |
| 2703 |
transport protocol and one or more codecs. When specifying the |
| 2704 |
proposed bandwidth, the worst case scenario must be taken into |
| 2705 |
account, i.e., use of the highest bandwidth codec provided, the |
| 2706 |
transport protocol indicated, and the worst case (bandwidth-wise) |
| 2707 |
parameters that can be negotiated (e.g., a 32-bit Hashed Message |
| 2708 |
Authentication Code (HMAC) or an 80-bit HMAC). |
| 2709 |
|
| 2710 |
The base SDP Capability Negotiation framework does not provide a way |
| 2711 |
to negotiate bandwidth parameters. The issue thus remains; however, |
| 2712 |
it is potentially worse than with SDP per [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>], since it is |
| 2713 |
easier to negotiate additional codecs, and furthermore possible to |
| 2714 |
negotiate different transport protocols. The recommended approach |
| 2715 |
for addressing this is the same as for plain SDP; the worst case (now |
| 2716 |
including potential configurations) needs to be taken into account |
| 2717 |
when specifying the bandwidth parameters in the actual configuration. |
| 2718 |
This can make the bandwidth value less accurate than in SDP per |
| 2719 |
[<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] (due to potential greater variability in the potential |
| 2720 |
configuration bandwidth use). Extensions can be defined to address |
| 2721 |
this shortcoming. |
| 2722 |
|
| 2723 |
Note, that when using RTP retransmission [<a href="./rfc4588" title=""RTP Retransmission Payload Format"">RFC4588</a>] with the RTCP- |
| 2724 |
based feedback profile [<a href="./rfc4585" title=""Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)"">RFC4585</a>] (RTP/AVPF), the retransmitted |
| 2725 |
packets are part of the media stream bandwidth when using |
| 2726 |
synchronization source (SSRC) multiplexing. If a feedback-based |
| 2727 |
protocol is offered as the actual configuration transport protocol, a |
| 2728 |
non-feedback-based protocol is offered as a potential configuration |
| 2729 |
transport protocol and ends up being used, the actual bandwidth usage |
| 2730 |
may be lower than the indicated bandwidth value in the offer (and |
| 2731 |
vice versa). |
| 2732 |
|
| 2733 |
|
| 2734 |
|
| 2735 |
|
| 2736 |
|
| 2737 |
|
| 2738 |
|
| 2739 |
|
| 2740 |
<span class="grey">Andreasen Standards Track [Page 49]</span></pre> |
| 2741 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span> |
| 2742 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2743 |
|
| 2744 |
|
| 2745 |
<span class="h3"><a class="selflink" id="section-3.11" href="#section-3.11">3.11</a>. Dealing with Large Number of Potential Configurations</span> |
| 2746 |
|
| 2747 |
When using the SDP Capability Negotiation, it is easy to generate |
| 2748 |
offers that contain a large number of potential configurations. For |
| 2749 |
example, in the offer: |
| 2750 |
|
| 2751 |
v=0 |
| 2752 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 2753 |
s= |
| 2754 |
c=IN IP4 192.0.2.1 |
| 2755 |
t=0 0 |
| 2756 |
m=audio 53456 RTP/AVP 0 18 |
| 2757 |
a=tcap:1 RTP/SAVPF RTP/SAVP RTP/AVPF |
| 2758 |
a=acap:1 crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 2759 |
inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:4 |
| 2760 |
FEC_ORDER=FEC_SRTP |
| 2761 |
a=acap:2 key-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAyO... |
| 2762 |
a=acap:3 rtcp-fb:0 nack |
| 2763 |
a=pcfg:1 t=1 a=1,3|2,3 |
| 2764 |
a=pcfg:2 t=2 a=1|2 |
| 2765 |
a=pcfg:3 t=3 a=3 |
| 2766 |
|
| 2767 |
we have 5 potential configurations on top of the actual configuration |
| 2768 |
for a single media stream. Adding an extension capability with just |
| 2769 |
two alternatives for each would double that number (to 10), and doing |
| 2770 |
the equivalent with two media streams would again double that number |
| 2771 |
(to 20). While it is easy (and inexpensive) for the offerer to |
| 2772 |
generate such offers, processing them at the answering side may not |
| 2773 |
be. Consequently, it is RECOMMENDED that offerers do not create |
| 2774 |
offers with unnecessarily large number of potential configurations in |
| 2775 |
them. |
| 2776 |
|
| 2777 |
On the answering side, implementers MUST take care to avoid excessive |
| 2778 |
memory and CPU consumption. For example, a naive implementation that |
| 2779 |
first generates all the valid potential configuration SDP session |
| 2780 |
descriptions internally, could find itself being memory exhausted, |
| 2781 |
especially if it supports a large number of endpoints. Similarly, a |
| 2782 |
naive implementation that simply performs iterative trial-and-error |
| 2783 |
processing on each possible potential configuration SDP session |
| 2784 |
description (in the preference order specified) could find itself |
| 2785 |
being CPU constrained. An alternative strategy is to prune the |
| 2786 |
search space first by discarding the set of offered potential |
| 2787 |
configurations where the transport protocol indicated (if any) is not |
| 2788 |
supported, and/or one or more mandatory attribute capabilities (if |
| 2789 |
any) are either not supported or not valid. Potential configurations |
| 2790 |
with unsupported mandatory extension configurations in them can be |
| 2791 |
discarded as well. |
| 2792 |
|
| 2793 |
|
| 2794 |
|
| 2795 |
|
| 2796 |
<span class="grey">Andreasen Standards Track [Page 50]</span></pre> |
| 2797 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span> |
| 2798 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2799 |
|
| 2800 |
|
| 2801 |
<span class="h3"><a class="selflink" id="section-3.12" href="#section-3.12">3.12</a>. SDP Capability Negotiation and Intermediaries</span> |
| 2802 |
|
| 2803 |
An intermediary is here defined as an entity between a SIP user agent |
| 2804 |
A and a SIP user agent B, that needs to perform some kind of |
| 2805 |
processing on the SDP session descriptions exchanged between A and B, |
| 2806 |
in order for the session establishment to operate as intended. |
| 2807 |
Examples of such intermediaries include Session Border Controllers |
| 2808 |
(SBCs) that may perform media relaying, Proxy Call Session Control |
| 2809 |
Functions (P-CSCFs) that may authorize use of a certain amount of |
| 2810 |
network resources (bandwidth), etc. The presence and design of such |
| 2811 |
intermediaries may not follow the "Internet" model or the SIP |
| 2812 |
requirements for proxies (which are not supposed to look in message |
| 2813 |
bodies such as SDP session descriptions); however, they are a fact of |
| 2814 |
life in some deployment scenarios and hence deserve consideration. |
| 2815 |
|
| 2816 |
If the intermediary needs to understand the characteristics of the |
| 2817 |
media sessions being negotiated, e.g., the amount of bandwidth used |
| 2818 |
or the transport protocol negotiated, then use of the SDP Capability |
| 2819 |
Negotiation framework may impact them. For example, some |
| 2820 |
intermediaries are known to disallow answers where the transport |
| 2821 |
protocol differs from the one in the offer. Use of the SDP |
| 2822 |
Capability Negotiation framework in the presence of such |
| 2823 |
intermediaries could lead to session failures. Intermediaries that |
| 2824 |
need to authorize use of network resources based on the negotiated |
| 2825 |
media stream parameters are affected as well. If they inspect only |
| 2826 |
the offer, then they may authorize parameters assuming a different |
| 2827 |
transport protocol, codecs, etc., than what is actually being |
| 2828 |
negotiated. For these, and other, reasons it is RECOMMENDED that |
| 2829 |
implementers of intermediaries add support for the SDP Capability |
| 2830 |
Negotiation framework. |
| 2831 |
|
| 2832 |
The SDP Capability Negotiation framework itself attempts to help out |
| 2833 |
these intermediaries as well, by recommending a second offer/answer |
| 2834 |
exchange when use of a potential configuration has been negotiated |
| 2835 |
(see <a href="#section-3.6.3">Section 3.6.3</a>). However, there are several limitations with |
| 2836 |
this approach. First of all, although the second offer/answer |
| 2837 |
exchange is RECOMMENDED, it is not required and hence may not be |
| 2838 |
performed. Secondly, the intermediary may refuse the initial answer, |
| 2839 |
e.g., due to perceived transport protocol mismatch. Thirdly, the |
| 2840 |
strategy is not foolproof since the offer/answer procedures [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>] |
| 2841 |
leave the original offer/answer exchange in effect when a subsequent |
| 2842 |
one fails. Consider the following example: |
| 2843 |
|
| 2844 |
1. Offerer generates an SDP session description offer with the actual |
| 2845 |
configuration specifying a low-bandwidth configuration (e.g., |
| 2846 |
plain RTP) and a potential configuration specifying a high(er) |
| 2847 |
bandwidth configuration (e.g., Secure RTP with integrity). |
| 2848 |
|
| 2849 |
|
| 2850 |
|
| 2851 |
|
| 2852 |
<span class="grey">Andreasen Standards Track [Page 51]</span></pre> |
| 2853 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span> |
| 2854 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2855 |
|
| 2856 |
|
| 2857 |
2. An intermediary (e.g., an SBC or P-CSCF), that does not support |
| 2858 |
SDP Capability Negotiation, authorizes the session based on the |
| 2859 |
actual configuration it sees in the SDP session description. |
| 2860 |
|
| 2861 |
3. The answerer chooses the high(er) bandwidth potential |
| 2862 |
configuration and generates an answer SDP session description |
| 2863 |
based on that. |
| 2864 |
|
| 2865 |
4. The intermediary passes through the answer SDP session |
| 2866 |
description. |
| 2867 |
|
| 2868 |
5. The offerer sees the accepted answer, and generates an updated |
| 2869 |
offer that contains the selected potential configuration as the |
| 2870 |
actual configuration. In other words, the high(er) bandwidth |
| 2871 |
configuration (which has already been negotiated successfully) is |
| 2872 |
now the actual configuration in the offer SDP session description. |
| 2873 |
|
| 2874 |
6. The intermediary sees the new offer; however, it does not |
| 2875 |
authorize the use of the high(er) bandwidth configuration, and |
| 2876 |
consequently generates a rejection message to the offerer. |
| 2877 |
|
| 2878 |
7. The offerer receives the rejected offer. |
| 2879 |
|
| 2880 |
After step 7, per <a href="./rfc3264">RFC 3264</a>, the offer/answer exchange that completed |
| 2881 |
in step 5 remains in effect; however, the intermediary may not have |
| 2882 |
authorized the necessary network resources and hence the media stream |
| 2883 |
may experience quality issues. The solution to this problem is to |
| 2884 |
upgrade the intermediary to support the SDP Capability Negotiation |
| 2885 |
framework. |
| 2886 |
|
| 2887 |
<span class="h3"><a class="selflink" id="section-3.13" href="#section-3.13">3.13</a>. Considerations for Specific Attribute Capabilities</span> |
| 2888 |
|
| 2889 |
<span class="h4"><a class="selflink" id="section-3.13.1" href="#section-3.13.1">3.13.1</a>. The "rtpmap" and "fmtp" Attributes</span> |
| 2890 |
|
| 2891 |
The base SDP Capability Negotiation framework defines transport |
| 2892 |
capabilities and attribute capabilities. Media capabilities, which |
| 2893 |
can be used to describe media formats and their associated |
| 2894 |
parameters, are not defined in this document; however, the "rtpmap" |
| 2895 |
and "fmtp" attributes can nevertheless be used as attribute |
| 2896 |
capabilities. Using such attribute capabilities in a potential |
| 2897 |
configuration requires a bit of care though. |
| 2898 |
|
| 2899 |
The rtpmap parameter binds an RTP payload type to a media format |
| 2900 |
(e.g., codec). While it is possible to provide rtpmaps for payload |
| 2901 |
types not found in the corresponding "m=" line, such rtpmaps provide |
| 2902 |
no value in normal offer/answer exchanges, since only the payload |
| 2903 |
types found in the "m=" line are part of the offer (or answer). This |
| 2904 |
applies to the base SDP Capability Negotiation framework as well. |
| 2905 |
|
| 2906 |
|
| 2907 |
|
| 2908 |
<span class="grey">Andreasen Standards Track [Page 52]</span></pre> |
| 2909 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span> |
| 2910 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2911 |
|
| 2912 |
|
| 2913 |
Only the media formats (e.g., RTP payload types) provided in the "m=" |
| 2914 |
line are actually offered; inclusion of "rtpmap" attributes with |
| 2915 |
other RTP payload types in a potential configuration does not change |
| 2916 |
this fact and hence they do not provide any useful information there. |
| 2917 |
They may still be useful as pure capabilities though (outside a |
| 2918 |
potential configuration) in order to inform a peer of additional |
| 2919 |
codecs supported. |
| 2920 |
|
| 2921 |
It is possible to provide an "rtpmap" attribute capability with a |
| 2922 |
payload type mapping to a different codec than a corresponding actual |
| 2923 |
configuration "rtpmap" attribute for the media description has. Such |
| 2924 |
practice is permissible as a way of indicating a capability. If that |
| 2925 |
capability is included in a potential configuration, then delete- |
| 2926 |
attributes (see <a href="#section-3.5.1">Section 3.5.1</a>) MUST be used to ensure that there is |
| 2927 |
not multiple "rtpmap" attributes for the same payload type in a given |
| 2928 |
media description (which would not be allowed by SDP [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>]). |
| 2929 |
|
| 2930 |
Similar considerations and rules apply to the "fmtp" attribute. An |
| 2931 |
"fmtp" attribute capability for a media format not included in the |
| 2932 |
"m=" line is useless in a potential configuration (but may be useful |
| 2933 |
as a capability by itself). An "fmtp" attribute capability in a |
| 2934 |
potential configuration for a media format that already has an "fmtp" |
| 2935 |
attribute in the actual configuration may lead to multiple fmtp |
| 2936 |
format parameters for that media format and that is not allowed by |
| 2937 |
SDP [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>]. The delete-attributes MUST be used to ensure that |
| 2938 |
there are not multiple "fmtp" attributes for a given media format in |
| 2939 |
a media description. |
| 2940 |
|
| 2941 |
Extensions to the base SDP Capability Negotiation framework may |
| 2942 |
change the above behavior. |
| 2943 |
|
| 2944 |
<span class="h4"><a class="selflink" id="section-3.13.2" href="#section-3.13.2">3.13.2</a>. Direction Attributes</span> |
| 2945 |
|
| 2946 |
SDP defines the "inactive", "sendonly", "recvonly", and "sendrecv" |
| 2947 |
direction attributes. The direction attributes can be applied at |
| 2948 |
either the session level or the media level. In either case, it is |
| 2949 |
possible to define attribute capabilities for these direction |
| 2950 |
capabilities; if used by a potential configuration, the normal |
| 2951 |
offer/answer procedures still apply. For example, if an offered |
| 2952 |
potential configuration includes the "sendonly" direction attribute, |
| 2953 |
and it is selected as the actual configuration, then the answer MUST |
| 2954 |
include a corresponding "recvonly" (or "inactive") attribute. |
| 2955 |
|
| 2956 |
|
| 2957 |
|
| 2958 |
|
| 2959 |
|
| 2960 |
|
| 2961 |
|
| 2962 |
|
| 2963 |
|
| 2964 |
<span class="grey">Andreasen Standards Track [Page 53]</span></pre> |
| 2965 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span> |
| 2966 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 2967 |
|
| 2968 |
|
| 2969 |
<span class="h3"><a class="selflink" id="section-3.14" href="#section-3.14">3.14</a>. Relationship to <a href="./rfc3407">RFC 3407</a></span> |
| 2970 |
|
| 2971 |
<a href="./rfc3407">RFC 3407</a> defines capability descriptions with limited abilities to |
| 2972 |
describe attributes, bandwidth parameters, transport protocols and |
| 2973 |
media formats. <a href="./rfc3407">RFC 3407</a> does not define any negotiation procedures |
| 2974 |
for actually using those capability descriptions. |
| 2975 |
|
| 2976 |
This document defines new attributes for describing attribute |
| 2977 |
capabilities and transport capabilities. It also defines procedures |
| 2978 |
for using those capabilities as part of an offer/answer exchange. In |
| 2979 |
contrast to <a href="./rfc3407">RFC 3407</a>, this document does not define bandwidth |
| 2980 |
parameters, and it also does not define how to express ranges of |
| 2981 |
values. Extensions to this document may be defined in order to fully |
| 2982 |
cover all the capabilities provided by <a href="./rfc3407">RFC 3407</a> (for example, more |
| 2983 |
general media capabilities). |
| 2984 |
|
| 2985 |
It is RECOMMENDED that implementations use the attributes and |
| 2986 |
procedures defined in this document instead of those defined in |
| 2987 |
[<a href="./rfc3407" title=""Session Description Protocol (SDP) Simple Capability Declaration"">RFC3407</a>]. If capability description interoperability with legacy |
| 2988 |
<a href="./rfc3407">RFC 3407</a> implementations is desired, implementations MAY include both |
| 2989 |
<a href="./rfc3407">RFC 3407</a> capability descriptions and capabilities defined by this |
| 2990 |
document. The offer/answer negotiation procedures defined in this |
| 2991 |
document will not use the <a href="./rfc3407">RFC 3407</a> capability descriptions. |
| 2992 |
|
| 2993 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Examples</span> |
| 2994 |
|
| 2995 |
In this section, we provide examples showing how to use the SDP |
| 2996 |
Capability Negotiation. |
| 2997 |
|
| 2998 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Multiple Transport Protocols</span> |
| 2999 |
|
| 3000 |
The following example illustrates how to use the SDP Capability |
| 3001 |
Negotiation extensions to negotiate use of one out of several |
| 3002 |
possible transport protocols. The offerer uses the expected least- |
| 3003 |
common-denominator (plain RTP) as the actual configuration, and the |
| 3004 |
alternative transport protocols as the potential configurations. |
| 3005 |
|
| 3006 |
|
| 3007 |
|
| 3008 |
|
| 3009 |
|
| 3010 |
|
| 3011 |
|
| 3012 |
|
| 3013 |
|
| 3014 |
|
| 3015 |
|
| 3016 |
|
| 3017 |
|
| 3018 |
|
| 3019 |
|
| 3020 |
<span class="grey">Andreasen Standards Track [Page 54]</span></pre> |
| 3021 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span> |
| 3022 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3023 |
|
| 3024 |
|
| 3025 |
The example is illustrated by the offer/answer exchange below, where |
| 3026 |
Alice sends an offer to Bob: |
| 3027 |
|
| 3028 |
Alice Bob |
| 3029 |
|
| 3030 |
| (1) Offer (RTP/[S]AVP[F]) | |
| 3031 |
|--------------------------------->| |
| 3032 |
| | |
| 3033 |
| (2) Answer (RTP/AVPF) | |
| 3034 |
|<---------------------------------| |
| 3035 |
| | |
| 3036 |
| (3) Offer (RTP/AVPF) | |
| 3037 |
|--------------------------------->| |
| 3038 |
| | |
| 3039 |
| (4) Answer (RTP/AVPF) | |
| 3040 |
|<---------------------------------| |
| 3041 |
| | |
| 3042 |
|
| 3043 |
Alice's offer includes plain RTP (RTP/AVP), RTP with RTCP-based |
| 3044 |
feedback (RTP/AVPF), Secure RTP (RTP/SAVP), and Secure RTP with RTCP- |
| 3045 |
based feedback (RTP/SAVPF) as alternatives. RTP is the default, with |
| 3046 |
RTP/SAVPF, RTP/SAVP, and RTP/AVPF as the alternatives and preferred |
| 3047 |
in the order listed: |
| 3048 |
|
| 3049 |
v=0 |
| 3050 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 3051 |
s= |
| 3052 |
c=IN IP4 192.0.2.1 |
| 3053 |
t=0 0 |
| 3054 |
m=audio 53456 RTP/AVP 0 18 |
| 3055 |
a=tcap:1 RTP/SAVPF RTP/SAVP RTP/AVPF |
| 3056 |
a=acap:1 crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 3057 |
inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:4 |
| 3058 |
FEC_ORDER=FEC_SRTP |
| 3059 |
a=acap:2 rtcp-fb:0 nack |
| 3060 |
a=pcfg:1 t=1 a=1,[2] |
| 3061 |
a=pcfg:2 t=2 a=1 |
| 3062 |
a=pcfg:3 t=3 a=[2] |
| 3063 |
|
| 3064 |
The "m=" line indicates that Alice is offering to use plain RTP with |
| 3065 |
PCMU or G.729. The capabilities are provided by the "a=tcap" and |
| 3066 |
"a=acap" attributes. The "tcap" capability indicates that Secure RTP |
| 3067 |
with RTCP-based feedback (RTP/SAVPF), Secure RTP (RTP/SAVP), and RTP |
| 3068 |
with RTCP-based feedback are supported. The first "acap" attribute |
| 3069 |
provides an attribute capability with a handle of 1. The capability |
| 3070 |
is a "crypto" attribute, which provides the keying material for SRTP |
| 3071 |
using SDP security descriptions [<a href="./rfc4568" title=""Session Description Protocol (SDP) Security Descriptions for Media Streams"">RFC4568</a>]. The second "acap" |
| 3072 |
attribute provides an attribute capability with a handle of 2. The |
| 3073 |
|
| 3074 |
|
| 3075 |
|
| 3076 |
<span class="grey">Andreasen Standards Track [Page 55]</span></pre> |
| 3077 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span> |
| 3078 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3079 |
|
| 3080 |
|
| 3081 |
capability is an "rtcp-fb" attribute, which is used by the RTCP-based |
| 3082 |
feedback profiles to indicate that payload type 0 (PCMU) supports |
| 3083 |
feedback type "nack". The "a=pcfg" attributes provide the potential |
| 3084 |
configurations included in the offer by reference to the |
| 3085 |
capabilities. There are three potential configurations: |
| 3086 |
|
| 3087 |
o Potential configuration 1, which is the most preferred potential |
| 3088 |
configuration specifies use of transport protocol capability 1 |
| 3089 |
(RTP/SAVPF) and attribute capabilities 1 (the "crypto" attribute) |
| 3090 |
and 2 (the "rtcp-fb" attribute). Support for the first one is |
| 3091 |
mandatory whereas support for the second one is optional. |
| 3092 |
|
| 3093 |
o Potential configuration 2, which is the second most preferred |
| 3094 |
potential configuration specifies use of transport protocol |
| 3095 |
capability 2 (RTP/SAVP) and mandatory attribute capability 1 (the |
| 3096 |
"crypto" attribute). |
| 3097 |
|
| 3098 |
o Potential configuration 3, which is the least preferred potential |
| 3099 |
configuration (but the second least preferred configuration |
| 3100 |
overall, since the actual configuration provided by the "m=" line |
| 3101 |
is always the least preferred configuration), specifies use of |
| 3102 |
transport protocol capability 3 (RTP/AVPF) and optional attribute |
| 3103 |
capability 2 (the "rtcp-fb" attribute). |
| 3104 |
|
| 3105 |
Bob receives the SDP session description offer from Alice. Bob does |
| 3106 |
not support any Secure RTP profiles; however, he supports plain RTP |
| 3107 |
and RTP with RTCP-based feedback, as well as the SDP Capability |
| 3108 |
Negotiation extensions, and hence he accepts the potential |
| 3109 |
configuration for RTP with RTCP-based feedback provided by Alice: |
| 3110 |
|
| 3111 |
v=0 |
| 3112 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3113 |
s= |
| 3114 |
c=IN IP4 192.0.2.2 |
| 3115 |
t=0 0 |
| 3116 |
m=audio 54568 RTP/AVPF 0 18 |
| 3117 |
a=rtcp-fb:0 nack |
| 3118 |
a=acfg:1 t=3 a=[2] |
| 3119 |
|
| 3120 |
Bob includes the "a=acfg" attribute in the answer to inform Alice |
| 3121 |
that he based his answer on an offer containing the potential |
| 3122 |
configuration with transport protocol capability 3 and optional |
| 3123 |
attribute capability 2 from the offer SDP session description (i.e., |
| 3124 |
the RTP/AVPF profile using the "rtcp-fb" value provided). Bob also |
| 3125 |
includes an "rtcp-fb" attribute with the value "nack" value for RTP |
| 3126 |
payload type 0. |
| 3127 |
|
| 3128 |
|
| 3129 |
|
| 3130 |
|
| 3131 |
|
| 3132 |
<span class="grey">Andreasen Standards Track [Page 56]</span></pre> |
| 3133 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span> |
| 3134 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3135 |
|
| 3136 |
|
| 3137 |
When Alice receives Bob's answer, session negotiation has completed, |
| 3138 |
however Alice nevertheless chooses to generate a new offer using the |
| 3139 |
actual configuration. This is done purely to assist any |
| 3140 |
intermediaries that may reside between Alice and Bob but do not |
| 3141 |
support the SDP Capability Negotiation framework (and hence may not |
| 3142 |
understand the negotiation that just took place): |
| 3143 |
|
| 3144 |
Alice's updated offer includes only RTP/AVPF, and it is not using the |
| 3145 |
SDP Capability Negotiation framework (Alice could have included the |
| 3146 |
capabilities as well if she wanted): |
| 3147 |
|
| 3148 |
v=0 |
| 3149 |
o=- 25678 753850 IN IP4 192.0.2.1 |
| 3150 |
s= |
| 3151 |
c=IN IP4 192.0.2.1 |
| 3152 |
t=0 0 |
| 3153 |
m=audio 53456 RTP/AVPF 0 18 |
| 3154 |
a=rtcp-fb:0 nack |
| 3155 |
|
| 3156 |
The "m=" line now indicates that Alice is offering to use RTP with |
| 3157 |
RTCP-based feedback and using PCMU or G.729. The "rtcp-fb" attribute |
| 3158 |
provides the feedback type "nack" for payload type 0 again (but as |
| 3159 |
part of the actual configuration). |
| 3160 |
|
| 3161 |
Bob receives the SDP session description offer from Alice, which he |
| 3162 |
accepts, and then generates an answer to Alice: |
| 3163 |
|
| 3164 |
v=0 |
| 3165 |
o=- 24351 621815 IN IP4 192.0.2.2 |
| 3166 |
s= |
| 3167 |
c=IN IP4 192.0.2.2 |
| 3168 |
t=0 0 |
| 3169 |
m=audio 54568 RTP/AVPF 0 18 |
| 3170 |
a=rtcp-fb:0 nack |
| 3171 |
|
| 3172 |
Bob includes the same "rtcp-fb" attribute as before, and the session |
| 3173 |
proceeds without change. Although Bob did not include any |
| 3174 |
capabilities in his answer, he could have done so if he wanted. |
| 3175 |
|
| 3176 |
Note that in this particular example, the answerer supported the SDP |
| 3177 |
Capability Negotiation framework and hence the attributes and |
| 3178 |
procedures defined here; however, had he not, the answerer would |
| 3179 |
simply have ignored the new attributes received in step 1 and |
| 3180 |
accepted the offer to use normal RTP. In that case, the following |
| 3181 |
answer would have been generated in step 2 instead: |
| 3182 |
|
| 3183 |
|
| 3184 |
|
| 3185 |
|
| 3186 |
|
| 3187 |
|
| 3188 |
<span class="grey">Andreasen Standards Track [Page 57]</span></pre> |
| 3189 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span> |
| 3190 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3191 |
|
| 3192 |
|
| 3193 |
v=0 |
| 3194 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3195 |
s= |
| 3196 |
c=IN IP4 192.0.2.2 |
| 3197 |
t=0 0 |
| 3198 |
m=audio 54568 RTP/AVP 0 18 |
| 3199 |
|
| 3200 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. DTLS-SRTP or SRTP with Media-Level Security Descriptions</span> |
| 3201 |
|
| 3202 |
The following example illustrates how to use the SDP Capability |
| 3203 |
Negotiation framework to negotiate use of SRTP using either SDP |
| 3204 |
security descriptions or DTLS-SRTP. The offerer (Alice) wants to |
| 3205 |
establish a Secure RTP audio stream but is willing to use plain RTP. |
| 3206 |
Alice prefers to use DTLS-SRTP as the key management protocol, but |
| 3207 |
supports SDP security descriptions as well (note that [<a href="./rfc5763" title=""Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)"">RFC5763</a>] |
| 3208 |
contains additional DTLS-SRTP examples). |
| 3209 |
|
| 3210 |
The example is illustrated by the offer/answer exchange below, where |
| 3211 |
Alice sends an offer to Bob: |
| 3212 |
|
| 3213 |
Alice Bob |
| 3214 |
|
| 3215 |
| (1) Offer (RTP/[S]AVP,SDES | DTLS-SRTP)| |
| 3216 |
|--------------------------------------->| |
| 3217 |
| | |
| 3218 |
|<--------- DTLS-SRTP handshake -------->| |
| 3219 |
| | |
| 3220 |
| (2) Answer (DTLS-SRTP) | |
| 3221 |
|<---------------------------------------| |
| 3222 |
| | |
| 3223 |
| (3) Offer (DTLS-SRTP) | |
| 3224 |
|--------------------------------------->| |
| 3225 |
| | |
| 3226 |
| (4) Answer (DTLS-SRTP) | |
| 3227 |
|<---------------------------------------| |
| 3228 |
| | |
| 3229 |
|
| 3230 |
Alice's offer includes an audio stream that offers use of plain RTP |
| 3231 |
and Secure RTP as alternatives. For the Secure RTP stream, it can be |
| 3232 |
established using either DTLS-SRTP or SDP security descriptions: |
| 3233 |
|
| 3234 |
|
| 3235 |
|
| 3236 |
|
| 3237 |
|
| 3238 |
|
| 3239 |
|
| 3240 |
|
| 3241 |
|
| 3242 |
|
| 3243 |
|
| 3244 |
<span class="grey">Andreasen Standards Track [Page 58]</span></pre> |
| 3245 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span> |
| 3246 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3247 |
|
| 3248 |
|
| 3249 |
v=0 |
| 3250 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 3251 |
s= |
| 3252 |
t=0 0 |
| 3253 |
c=IN IP4 192.0.2.1 |
| 3254 |
a=acap:1 setup:actpass |
| 3255 |
a=acap:2 fingerprint: SHA-1 \ |
| 3256 |
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB |
| 3257 |
a=tcap:1 UDP/TLS/RTP/SAVP RTP/SAVP |
| 3258 |
m=audio 59000 RTP/AVP 98 |
| 3259 |
a=rtpmap:98 AMR/8000 |
| 3260 |
a=acap:3 crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3261 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 3262 |
a=pcfg:1 t=1 a=1,2 |
| 3263 |
a=pcfg:2 t=2 a=3 |
| 3264 |
|
| 3265 |
The first (and preferred) potential configuration for the audio |
| 3266 |
stream specifies use of transport capability 1 (UDP/TLS/RTP/SAVP), |
| 3267 |
i.e., DTLS-SRTP, and attribute capabilities 1 and 2 (active/passive |
| 3268 |
mode and certificate fingerprint), both of which must be supported to |
| 3269 |
choose this potential configuration. The second (and less preferred) |
| 3270 |
potential configuration specifies use of transport capability 2 |
| 3271 |
(RTP/SAVP) and mandatory attribute capability 3, i.e., the SDP |
| 3272 |
security description. |
| 3273 |
|
| 3274 |
Bob receives the SDP session description offer from Alice. Bob |
| 3275 |
supports DTLS-SRTP as preferred by Alice and Bob now initiates the |
| 3276 |
DTLS-SRTP handshake to establish the DTLS-SRTP session (see [<a href="./rfc5764" title=""Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)"">RFC5764</a>] |
| 3277 |
for details). |
| 3278 |
|
| 3279 |
Bob also sends back an answer to Alice as follows: |
| 3280 |
|
| 3281 |
v=0 |
| 3282 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3283 |
s= |
| 3284 |
a=setup:active |
| 3285 |
a=fingerprint: SHA-1 \ |
| 3286 |
FF:FF:FF:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB |
| 3287 |
t=0 0 |
| 3288 |
c=IN IP4 192.0.2.2 |
| 3289 |
m=audio 54568 UDP/TLS/RTP/SAVP 98 |
| 3290 |
a=rtpmap:98 AMR/8000 |
| 3291 |
a=acfg:1 t=1 a=1,2 |
| 3292 |
|
| 3293 |
For the audio stream, Bob accepted the use of DTLS-SRTP, and hence |
| 3294 |
the profile in the "m=" line is "UDP/TLS/RTP/SAVP". Bob also |
| 3295 |
includes a "setup:active" attribute to indicate he is the active |
| 3296 |
|
| 3297 |
|
| 3298 |
|
| 3299 |
|
| 3300 |
<span class="grey">Andreasen Standards Track [Page 59]</span></pre> |
| 3301 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span> |
| 3302 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3303 |
|
| 3304 |
|
| 3305 |
endpoint for the DTLS-SRTP session as well as the fingerprint for |
| 3306 |
Bob's certificate. Bob's "acfg" attribute indicates that he chose |
| 3307 |
potential configuration 1 from Alice's offer. |
| 3308 |
|
| 3309 |
When Alice receives Bob's answer, session negotiation has completed |
| 3310 |
(and Alice can verify the DTLS handshake using Bob's certificate |
| 3311 |
fingerprint in the answer); however, Alice nevertheless chooses to |
| 3312 |
generate a new offer using the actual configuration. This is done |
| 3313 |
purely to assist any intermediaries that may reside between Alice and |
| 3314 |
Bob but do not support the capability negotiation extensions (and |
| 3315 |
hence may not understand the negotiation that just took place). |
| 3316 |
|
| 3317 |
Alice's updated offer includes only DTLS-SRTP for the audio stream, |
| 3318 |
and it is not using the SDP Capability Negotiation framework (Alice |
| 3319 |
could have included the capabilities as well if she wanted): |
| 3320 |
|
| 3321 |
v=0 |
| 3322 |
o=- 25678 753850 IN IP4 192.0.2.1 |
| 3323 |
s= |
| 3324 |
t=0 0 |
| 3325 |
c=IN IP4 192.0.2.1 |
| 3326 |
a=setup:actpass |
| 3327 |
a=fingerprint: SHA-1 \ |
| 3328 |
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB |
| 3329 |
m=audio 59000 UDP/TLS/RTP/AVP 98 |
| 3330 |
a=rtpmap:98 AMR/8000 |
| 3331 |
|
| 3332 |
The "m=" line for the audio stream now indicates that Alice is |
| 3333 |
offering to use DTLS-SRTP in active/passive mode using her |
| 3334 |
certificate fingerprint provided. |
| 3335 |
|
| 3336 |
Bob receives the SDP session description offer from Alice, which he |
| 3337 |
accepts, and then generates an answer to Alice: |
| 3338 |
|
| 3339 |
v=0 |
| 3340 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3341 |
s= |
| 3342 |
a=setup:active |
| 3343 |
a=fingerprint: SHA-1 \ |
| 3344 |
FF:FF:FF:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB |
| 3345 |
t=0 0 |
| 3346 |
c=IN IP4 192.0.2.2 |
| 3347 |
m=audio 54568 UDP/TLS/RTP/SAVP 98 |
| 3348 |
a=rtpmap:98 AMR/8000 |
| 3349 |
a=acfg:1 t=1 a=1,2 |
| 3350 |
|
| 3351 |
|
| 3352 |
|
| 3353 |
|
| 3354 |
|
| 3355 |
|
| 3356 |
<span class="grey">Andreasen Standards Track [Page 60]</span></pre> |
| 3357 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span> |
| 3358 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3359 |
|
| 3360 |
|
| 3361 |
Bob includes the same "setup:active" and fingerprint attributes as |
| 3362 |
before, and the session proceeds without change. Although Bob did |
| 3363 |
not include any capabilities in his answer, he could have done so if |
| 3364 |
he wanted. |
| 3365 |
|
| 3366 |
Note that in this particular example, the answerer supported the |
| 3367 |
capability extensions defined here; however, had he not, the answerer |
| 3368 |
would simply have ignored the new attributes received in step 1 and |
| 3369 |
accepted the offer to use normal RTP. In that case, the following |
| 3370 |
answer would have been generated in step 2 instead: |
| 3371 |
|
| 3372 |
v=0 |
| 3373 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3374 |
s= |
| 3375 |
t=0 0 |
| 3376 |
c=IN IP4 192.0.2.2 |
| 3377 |
m=audio 54568 RTP/AVP 98 |
| 3378 |
a=rtpmap:98 AMR/8000 |
| 3379 |
|
| 3380 |
Finally, if Bob had chosen to use SDP security descriptions instead |
| 3381 |
of DTLS-SRTP, the following answer would have been generated: |
| 3382 |
|
| 3383 |
v=0 |
| 3384 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3385 |
s= |
| 3386 |
t=0 0 |
| 3387 |
c=IN IP4 192.0.2.2 |
| 3388 |
m=audio 54568 RTP/SAVP 98 |
| 3389 |
a=rtpmap:98 AMR/8000 |
| 3390 |
a=crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3391 |
inline:WSJ+PSdFcGdUJShpX1ZjNzB4d1BINUAvLEw6UzF3|2^20|1:32 |
| 3392 |
a=acfg:2 t=2 a=3 |
| 3393 |
|
| 3394 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Best-Effort SRTP with Session-Level MIKEY and Media-Level Security</span> |
| 3395 |
<span class="h3"> Descriptions</span> |
| 3396 |
|
| 3397 |
The following example illustrates how to use the SDP Capability |
| 3398 |
Negotiation extensions to support so-called Best-Effort Secure RTP as |
| 3399 |
well as alternative keying mechanisms, more specifically MIKEY |
| 3400 |
[<a href="./rfc3830" title=""MIKEY: Multimedia Internet KEYing"">RFC3830</a>] and SDP security descriptions. The offerer (Alice) wants |
| 3401 |
to establish an audio and video session. Alice prefers to use |
| 3402 |
session-level MIKEY as the key management protocol, but supports SDP |
| 3403 |
security descriptions as well. |
| 3404 |
|
| 3405 |
The example is illustrated by the offer/answer exchange below, where |
| 3406 |
Alice sends an offer to Bob: |
| 3407 |
|
| 3408 |
|
| 3409 |
|
| 3410 |
|
| 3411 |
|
| 3412 |
<span class="grey">Andreasen Standards Track [Page 61]</span></pre> |
| 3413 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span> |
| 3414 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3415 |
|
| 3416 |
|
| 3417 |
Alice Bob |
| 3418 |
|
| 3419 |
| (1) Offer (RTP/[S]AVP[F], SDES|MIKEY) | |
| 3420 |
|--------------------------------------->| |
| 3421 |
| | |
| 3422 |
| (2) Answer (RTP/SAVP, SDES) | |
| 3423 |
|<---------------------------------------| |
| 3424 |
| | |
| 3425 |
| (3) Offer (RTP/SAVP, SDES) | |
| 3426 |
|--------------------------------------->| |
| 3427 |
| | |
| 3428 |
| (4) Answer (RTP/SAVP, SDES) | |
| 3429 |
|<---------------------------------------| |
| 3430 |
| | |
| 3431 |
|
| 3432 |
Alice's offer includes an audio and a video stream. The audio stream |
| 3433 |
offers use of plain RTP and Secure RTP as alternatives, whereas the |
| 3434 |
video stream offers use of plain RTP, RTP with RTCP-based feedback, |
| 3435 |
Secure RTP, and Secure RTP with RTCP-based feedback as alternatives: |
| 3436 |
|
| 3437 |
v=0 |
| 3438 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 3439 |
s= |
| 3440 |
t=0 0 |
| 3441 |
c=IN IP4 192.0.2.1 |
| 3442 |
a=acap:1 key-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAyO... |
| 3443 |
a=tcap:1 RTP/SAVPF RTP/SAVP RTP/AVPF |
| 3444 |
m=audio 59000 RTP/AVP 98 |
| 3445 |
a=rtpmap:98 AMR/8000 |
| 3446 |
a=acap:2 crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3447 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 3448 |
a=pcfg:1 t=2 a=1|2 |
| 3449 |
m=video 52000 RTP/AVP 31 |
| 3450 |
a=rtpmap:31 H261/90000 |
| 3451 |
a=acap:3 crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 3452 |
inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 |
| 3453 |
a=acap:4 rtcp-fb:* nack |
| 3454 |
a=pcfg:1 t=1 a=1,4|3,4 |
| 3455 |
a=pcfg:2 t=2 a=1|3 |
| 3456 |
a=pcfg:3 t=3 a=4 |
| 3457 |
|
| 3458 |
The potential configuration for the audio stream specifies use of |
| 3459 |
transport capability 2 (RTP/SAVP) and either attribute capability 1 |
| 3460 |
(session-level MIKEY as the keying mechanism) or 2 (SDP security |
| 3461 |
descriptions as the keying mechanism). Support for either of these |
| 3462 |
attribute capabilities is mandatory. There are three potential |
| 3463 |
configurations for the video stream. |
| 3464 |
|
| 3465 |
|
| 3466 |
|
| 3467 |
|
| 3468 |
<span class="grey">Andreasen Standards Track [Page 62]</span></pre> |
| 3469 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span> |
| 3470 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3471 |
|
| 3472 |
|
| 3473 |
o The first configuration with configuration number 1 uses transport |
| 3474 |
capability 1 (RTP/SAVPF) with either attribute capabilities 1 and |
| 3475 |
4 (session-level MIKEY and the "rtcp-fb" attribute) or attribute |
| 3476 |
capabilities 3 and 4 (SDP security descriptions and the "rtcp-fb" |
| 3477 |
attribute). In this example, the offerer insists on not only the |
| 3478 |
keying mechanism being supported, but also that the "rtcp-fb" |
| 3479 |
attribute is supported with the value indicated. Consequently, |
| 3480 |
all the attribute capabilities are marked as mandatory in this |
| 3481 |
potential configuration. |
| 3482 |
|
| 3483 |
o The second configuration with configuration number 2 uses |
| 3484 |
transport capability 2 (RTP/SAVP) and either attribute capability |
| 3485 |
1 (session-level MIKEY) or attribute capability 3 (SDP security |
| 3486 |
descriptions). Both attribute capabilities are mandatory in this |
| 3487 |
configuration. |
| 3488 |
|
| 3489 |
o The third configuration with configuration number 3 uses transport |
| 3490 |
capability 3 (RTP/AVPF) and mandatory attribute capability 4 (the |
| 3491 |
"rtcp-fb" attribute). |
| 3492 |
|
| 3493 |
Bob receives the SDP session description offer from Alice. Bob |
| 3494 |
supports Secure RTP, Secure RTP with RTCP-based feedback and the SDP |
| 3495 |
Capability Negotiation extensions. Bob also supports SDP security |
| 3496 |
descriptions, but not MIKEY, and hence he generates the following |
| 3497 |
answer: |
| 3498 |
|
| 3499 |
v=0 |
| 3500 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3501 |
s= |
| 3502 |
t=0 0 |
| 3503 |
c=IN IP4 192.0.2.2 |
| 3504 |
m=audio 54568 RTP/SAVP 98 |
| 3505 |
a=rtpmap:98 AMR/8000 |
| 3506 |
a=crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3507 |
inline:WSJ+PSdFcGdUJShpX1ZjNzB4d1BINUAvLEw6UzF3|2^20|1:32 |
| 3508 |
a=acfg:1 t=2 a=2 |
| 3509 |
m=video 55468 RTP/SAVPF 31 |
| 3510 |
a=rtpmap:31 H261/90000 |
| 3511 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 3512 |
inline:AwWpVLFJhQX1cfHJSojd0RmdmcmVCspeEc3QGZiN|2^20|1:32 |
| 3513 |
a=rtcp-fb:* nack |
| 3514 |
a=acfg:1 t=1 a=3,4 |
| 3515 |
|
| 3516 |
For the audio stream, Bob accepted the use of Secure RTP, and hence |
| 3517 |
the profile in the "m=" line is "RTP/SAVP". Bob also includes a |
| 3518 |
"crypto" attribute with his own keying material, and an "acfg" |
| 3519 |
attribute identifying actual configuration 1 for the audio media |
| 3520 |
stream from the offer, using transport capability 2 (RTP/SAVP) and |
| 3521 |
|
| 3522 |
|
| 3523 |
|
| 3524 |
<span class="grey">Andreasen Standards Track [Page 63]</span></pre> |
| 3525 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span> |
| 3526 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3527 |
|
| 3528 |
|
| 3529 |
attribute capability 2 (the "crypto" attribute from the offer). For |
| 3530 |
the video stream, Bob accepted the use of Secure RTP with RTCP-based |
| 3531 |
feedback, and hence the profile in the "m=" line is "RTP/SAVPF". Bob |
| 3532 |
also includes a "crypto" attribute with his own keying material, and |
| 3533 |
an "acfg" attribute identifying actual configuration 1 for the video |
| 3534 |
stream from the offer, using transport capability 1 (RTP/SAVPF) and |
| 3535 |
attribute capabilities 3 (the "crypto" attribute from the offer) and |
| 3536 |
4 (the "rtcp-fb" attribute from the offer). |
| 3537 |
|
| 3538 |
When Alice receives Bob's answer, session negotiation has completed; |
| 3539 |
however, Alice nevertheless chooses to generate a new offer using the |
| 3540 |
actual configuration. This is done purely to assist any |
| 3541 |
intermediaries that may reside between Alice and Bob but do not |
| 3542 |
support the capability negotiation extensions (and hence may not |
| 3543 |
understand the negotiation that just took place). |
| 3544 |
|
| 3545 |
Alice's updated offer includes only SRTP for the audio stream SRTP |
| 3546 |
with RTCP-based feedback for the video stream, and it is not using |
| 3547 |
the SDP Capability Negotiation framework (Alice could have included |
| 3548 |
the capabilities as well is she wanted): |
| 3549 |
|
| 3550 |
v=0 |
| 3551 |
o=- 25678 753850 IN IP4 192.0.2.1 |
| 3552 |
s= |
| 3553 |
t=0 0 |
| 3554 |
c=IN IP4 192.0.2.1 |
| 3555 |
m=audio 59000 RTP/SAVP 98 |
| 3556 |
a=rtpmap:98 AMR/8000 |
| 3557 |
a=crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3558 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 3559 |
m=video 52000 RTP/SAVPF 31 |
| 3560 |
a=rtpmap:31 H261/90000 |
| 3561 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 3562 |
inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 |
| 3563 |
a=rtcp-fb:* nack |
| 3564 |
|
| 3565 |
The "m=" line for the audio stream now indicates that Alice is |
| 3566 |
offering to use Secure RTP with PCMU or G.729, whereas the "m=" line |
| 3567 |
for the video stream indicates that Alice is offering to use Secure |
| 3568 |
RTP with RTCP-based feedback and H.261. Each media stream includes a |
| 3569 |
"crypto" attribute, which provides the SRTP keying material, with the |
| 3570 |
same value again. |
| 3571 |
|
| 3572 |
|
| 3573 |
|
| 3574 |
|
| 3575 |
|
| 3576 |
|
| 3577 |
|
| 3578 |
|
| 3579 |
|
| 3580 |
<span class="grey">Andreasen Standards Track [Page 64]</span></pre> |
| 3581 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span> |
| 3582 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3583 |
|
| 3584 |
|
| 3585 |
Bob receives the SDP session description offer from Alice, which he |
| 3586 |
accepts, and then generates an answer to Alice: |
| 3587 |
|
| 3588 |
v=0 |
| 3589 |
o=- 24351 621815 IN IP4 192.0.2.2 |
| 3590 |
s= |
| 3591 |
t=0 0 |
| 3592 |
c=IN IP4 192.0.2.2 |
| 3593 |
m=audio 54568 RTP/SAVP 98 |
| 3594 |
a=rtpmap:98 AMR/8000 |
| 3595 |
a=crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3596 |
inline:WSJ+PSdFcGdUJShpX1ZjNzB4d1BINUAvLEw6UzF3|2^20|1:32 |
| 3597 |
m=video 55468 RTP/SAVPF 31 |
| 3598 |
a=rtpmap:31 H261/90000 |
| 3599 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 3600 |
inline:AwWpVLFJhQX1cfHJSojd0RmdmcmVCspeEc3QGZiN|2^20|1:32 |
| 3601 |
a=rtcp-fb:* nack |
| 3602 |
|
| 3603 |
Bob includes the same "crypto" attribute as before, and the session |
| 3604 |
proceeds without change. Although Bob did not include any |
| 3605 |
capabilities in his answer, he could have done so if he wanted. |
| 3606 |
|
| 3607 |
Note that in this particular example, the answerer supported the |
| 3608 |
capability extensions defined here; however, had he not, the answerer |
| 3609 |
would simply have ignored the new attributes received in step 1 and |
| 3610 |
accepted the offer to use normal RTP. In that case, the following |
| 3611 |
answer would have been generated in step 2 instead: |
| 3612 |
|
| 3613 |
v=0 |
| 3614 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3615 |
s= |
| 3616 |
t=0 0 |
| 3617 |
c=IN IP4 192.0.2.2 |
| 3618 |
m=audio 54568 RTP/AVP 98 |
| 3619 |
a=rtpmap:98 AMR/8000 |
| 3620 |
m=video 55468 RTP/AVP 31 |
| 3621 |
a=rtpmap:31 H261/90000 |
| 3622 |
a=rtcp-fb:* nack |
| 3623 |
|
| 3624 |
Finally, if Bob had chosen to use session-level MIKEY instead of SDP |
| 3625 |
security descriptions, the following answer would have been |
| 3626 |
generated: |
| 3627 |
|
| 3628 |
|
| 3629 |
|
| 3630 |
|
| 3631 |
|
| 3632 |
|
| 3633 |
|
| 3634 |
|
| 3635 |
|
| 3636 |
<span class="grey">Andreasen Standards Track [Page 65]</span></pre> |
| 3637 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span> |
| 3638 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3639 |
|
| 3640 |
|
| 3641 |
v=0 |
| 3642 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3643 |
s= |
| 3644 |
t=0 0 |
| 3645 |
c=IN IP4 192.0.2.2 |
| 3646 |
a=key-mgmt:mikey AQEFgM0XflABAAAAAAAAAAAAAAYAyO... |
| 3647 |
m=audio 54568 RTP/SAVP 98 |
| 3648 |
a=rtpmap:98 AMR/8000 |
| 3649 |
a=acfg:1 t=2 a=1 |
| 3650 |
m=video 55468 RTP/SAVPF 31 |
| 3651 |
a=rtpmap:31 H261/90000 |
| 3652 |
a=rtcp-fb:* nack |
| 3653 |
a=acfg:1 t=1 a=1,4 |
| 3654 |
|
| 3655 |
It should be noted, that although Bob could have chosen session-level |
| 3656 |
MIKEY for one media stream, and SDP security descriptions for another |
| 3657 |
media stream, there are no well-defined offerer processing rules of |
| 3658 |
the resulting answer for this, and hence the offerer may incorrectly |
| 3659 |
assume use of MIKEY for both streams. To avoid this, if the answerer |
| 3660 |
chooses session-level MIKEY, then all Secure RTP-based media streams |
| 3661 |
SHOULD use MIKEY (this applies irrespective of whether or not SDP |
| 3662 |
Capability Negotiation is being used). Use of media-level MIKEY does |
| 3663 |
not have a similar constraint. |
| 3664 |
|
| 3665 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. SRTP with Session-Level MIKEY and Media-Level Security</span> |
| 3666 |
<span class="h3"> Descriptions as Alternatives</span> |
| 3667 |
|
| 3668 |
The following example illustrates how to use the SDP Capability |
| 3669 |
Negotiation framework to negotiate use of either MIKEY or SDP |
| 3670 |
security descriptions, when one of them is included as part of the |
| 3671 |
actual configuration, and the other one is being selected. The |
| 3672 |
offerer (Alice) wants to establish an audio and video session. Alice |
| 3673 |
prefers to use session-level MIKEY as the key management protocol, |
| 3674 |
but supports SDP security descriptions as well. |
| 3675 |
|
| 3676 |
The example is illustrated by the offer/answer exchange below, where |
| 3677 |
Alice sends an offer to Bob: |
| 3678 |
|
| 3679 |
Alice Bob |
| 3680 |
|
| 3681 |
| (1) Offer (RTP/[S]AVP[F], SDES|MIKEY) | |
| 3682 |
|--------------------------------------->| |
| 3683 |
| | |
| 3684 |
| (2) Answer (RTP/SAVP, SDES) | |
| 3685 |
|<---------------------------------------| |
| 3686 |
| | |
| 3687 |
|
| 3688 |
|
| 3689 |
|
| 3690 |
|
| 3691 |
|
| 3692 |
<span class="grey">Andreasen Standards Track [Page 66]</span></pre> |
| 3693 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span> |
| 3694 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3695 |
|
| 3696 |
|
| 3697 |
Alice's offer includes an audio and a video stream. Both the audio |
| 3698 |
and the video stream offer use of Secure RTP: |
| 3699 |
|
| 3700 |
v=0 |
| 3701 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 3702 |
s= |
| 3703 |
t=0 0 |
| 3704 |
c=IN IP4 192.0.2.1 |
| 3705 |
a=key-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAyO... |
| 3706 |
m=audio 59000 RTP/SAVP 98 |
| 3707 |
a=rtpmap:98 AMR/8000 |
| 3708 |
a=acap:1 crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3709 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 3710 |
a=pcfg:1 a=-s:1 |
| 3711 |
m=video 52000 RTP/SAVP 31 |
| 3712 |
a=rtpmap:31 H261/90000 |
| 3713 |
a=acap:2 crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 3714 |
inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 |
| 3715 |
a=pcfg:1 a=-s:2 |
| 3716 |
|
| 3717 |
Alice does not know whether Bob supports MIKEY or SDP security |
| 3718 |
descriptions. She could include attributes for both; however, the |
| 3719 |
resulting procedures and potential interactions are not well- |
| 3720 |
defined. Instead, she places a session-level "key-mgmt" attribute |
| 3721 |
for MIKEY in the actual configuration with SDP security descriptions |
| 3722 |
as an alternative in the potential configuration. The potential |
| 3723 |
configuration for the audio stream specifies that all session-level |
| 3724 |
attributes are to be deleted (i.e., the session-level "a=key-mgmt" |
| 3725 |
attribute) and that mandatory attribute capability 2 is to be used |
| 3726 |
(i.e., the "crypto" attribute). The potential configuration for the |
| 3727 |
video stream is similar, except it uses its own mandatory "crypto" |
| 3728 |
attribute capability (2). Note how the deletion of the session-level |
| 3729 |
attributes does not affect the media-level attributes. |
| 3730 |
|
| 3731 |
Bob receives the SDP session description offer from Alice. Bob |
| 3732 |
supports Secure RTP and the SDP Capability Negotiation framework. |
| 3733 |
Bob also supports both SDP security descriptions and MIKEY. Since |
| 3734 |
the potential configuration is more preferred than the actual |
| 3735 |
configuration, Bob (conceptually) generates an internal potential |
| 3736 |
configuration SDP session description that contains the "crypto" |
| 3737 |
attributes for the audio and video stream, but not the "key-mgmt" |
| 3738 |
attribute for MIKEY, thereby avoiding any ambiguity between the two |
| 3739 |
keying mechanisms. As a result, he generates the following answer: |
| 3740 |
|
| 3741 |
|
| 3742 |
|
| 3743 |
|
| 3744 |
|
| 3745 |
|
| 3746 |
|
| 3747 |
|
| 3748 |
<span class="grey">Andreasen Standards Track [Page 67]</span></pre> |
| 3749 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span> |
| 3750 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3751 |
|
| 3752 |
|
| 3753 |
v=0 |
| 3754 |
o=- 24351 621814 IN IP4 192.0.2.2 |
| 3755 |
s= |
| 3756 |
t=0 0 |
| 3757 |
c=IN IP4 192.0.2.2 |
| 3758 |
m=audio 54568 RTP/SAVP 98 |
| 3759 |
a=rtpmap:98 AMR/8000 |
| 3760 |
a=crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3761 |
inline:WSJ+PSdFcGdUJShpX1ZjNzB4d1BINUAvLEw6UzF3|2^20|1:32 |
| 3762 |
a=acfg:1 a=-s:1 |
| 3763 |
m=video 55468 RTP/SAVP 31 |
| 3764 |
a=rtpmap:31 H261/90000 |
| 3765 |
a=crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 3766 |
inline:AwWpVLFJhQX1cfHJSojd0RmdmcmVCspeEc3QGZiN|2^20|1:32 |
| 3767 |
a=acfg:1 a=-s:2 |
| 3768 |
|
| 3769 |
For the audio stream, Bob accepted the use of Secure RTP using SDP |
| 3770 |
security descriptions. Bob therefore includes a "crypto" attribute |
| 3771 |
with his own keying material, and an "acfg" attribute identifying the |
| 3772 |
actual configuration 1 for the audio media stream from the offer, |
| 3773 |
with the delete-attributes ("-s") and attribute capability 1 (the |
| 3774 |
"crypto" attribute from the offer). For the video stream, Bob also |
| 3775 |
accepted the use of Secure RTP using SDP security descriptions. Bob |
| 3776 |
therefore includes a "crypto" attribute with his own keying material, |
| 3777 |
and an "acfg" attribute identifying actual configuration 1 for the |
| 3778 |
video stream from the offer, with the delete-attributes ("-s") and |
| 3779 |
attribute capability 2. |
| 3780 |
|
| 3781 |
Below, we illustrate the offer SDP session description, when Bob |
| 3782 |
instead offers the "crypto" attribute as the actual configuration |
| 3783 |
keying mechanism and "key-mgmt" as the potential configuration: |
| 3784 |
|
| 3785 |
|
| 3786 |
|
| 3787 |
|
| 3788 |
|
| 3789 |
|
| 3790 |
|
| 3791 |
|
| 3792 |
|
| 3793 |
|
| 3794 |
|
| 3795 |
|
| 3796 |
|
| 3797 |
|
| 3798 |
|
| 3799 |
|
| 3800 |
|
| 3801 |
|
| 3802 |
|
| 3803 |
|
| 3804 |
<span class="grey">Andreasen Standards Track [Page 68]</span></pre> |
| 3805 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span> |
| 3806 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3807 |
|
| 3808 |
|
| 3809 |
v=0 |
| 3810 |
o=- 25678 753849 IN IP4 192.0.2.1 |
| 3811 |
s= |
| 3812 |
t=0 0 |
| 3813 |
c=IN IP4 192.0.2.1 |
| 3814 |
a=acap:1 key-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAyO... |
| 3815 |
m=audio 59000 RTP/SAVP 98 |
| 3816 |
a=rtpmap:98 AMR/8000 |
| 3817 |
a=crypto:1 AES_CM_128_HMAC_SHA1_32 |
| 3818 |
inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 |
| 3819 |
a=acap:2 rtpmap:98 AMR/8000 |
| 3820 |
a=pcfg:1 a=-m:1,2 |
| 3821 |
m=video 52000 RTP/SAVP 31 |
| 3822 |
a=rtpmap:31 H261/90000 |
| 3823 |
a=acap:3 crypto:1 AES_CM_128_HMAC_SHA1_80 |
| 3824 |
inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:32 |
| 3825 |
a=acap:4 rtpmap:31 H261/90000 |
| 3826 |
a=pcfg:1 a=-m:1,4 |
| 3827 |
|
| 3828 |
Note how we this time need to perform delete-attributes at the media |
| 3829 |
level instead of the session level. When doing that, all attributes |
| 3830 |
from the actual configuration SDP session description, including the |
| 3831 |
rtpmaps provided, are removed. Consequently, we had to include these |
| 3832 |
rtpmaps as capabilities as well, and then include them in the |
| 3833 |
potential configuration, thereby effectively recreating the original |
| 3834 |
"rtpmap" attributes in the resulting potential configuration SDP |
| 3835 |
session description. |
| 3836 |
|
| 3837 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 3838 |
|
| 3839 |
The SDP Capability Negotiation framework is defined to be used within |
| 3840 |
the context of the offer/answer model, and hence all the offer/answer |
| 3841 |
security considerations apply here as well [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]. Similarly, the |
| 3842 |
Session Initiation Protocol (SIP) uses SDP and the offer/answer |
| 3843 |
model, and hence, when used in that context, the SIP security |
| 3844 |
considerations apply as well [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>]. |
| 3845 |
|
| 3846 |
However, SDP Capability Negotiation introduces additional security |
| 3847 |
issues. Its use as a mechanism to enable alternative transport |
| 3848 |
protocol negotiation (secure and non-secure) as well as its ability |
| 3849 |
to negotiate use of more or less secure keying methods and material |
| 3850 |
warrant further security considerations. Also, the (continued) |
| 3851 |
support for receiving media before answer combined with negotiation |
| 3852 |
of alternative transport protocols (secure and non-secure) warrants |
| 3853 |
further security considerations. We discuss these issues below. |
| 3854 |
|
| 3855 |
|
| 3856 |
|
| 3857 |
|
| 3858 |
|
| 3859 |
|
| 3860 |
<span class="grey">Andreasen Standards Track [Page 69]</span></pre> |
| 3861 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span> |
| 3862 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3863 |
|
| 3864 |
|
| 3865 |
The SDP Capability Negotiation framework allows for an offered media |
| 3866 |
stream to both indicate and support various levels of security for |
| 3867 |
that media stream. Different levels of security can for example be |
| 3868 |
negotiated by use of alternative attribute capabilities each |
| 3869 |
indicating more or less secure keying methods as well as more or less |
| 3870 |
strong ciphers. Since the offerer indicates support for each of |
| 3871 |
these alternatives, he will presumably accept the answerer seemingly |
| 3872 |
selecting any of the offered alternatives. If an attacker can modify |
| 3873 |
the SDP session description offer, he can thereby force the |
| 3874 |
negotiation of the weakest security mechanism that the offerer is |
| 3875 |
willing to accept. This may enable the attacker to compromise the |
| 3876 |
security of the negotiated media stream. Similarly, if the offerer |
| 3877 |
wishes to negotiate use of a secure media stream (e.g., Secure RTP), |
| 3878 |
but includes a non-secure media stream (e.g., plain RTP) as a valid |
| 3879 |
(but less preferred) alternative, then an attacker that can modify |
| 3880 |
the offered SDP session description will be able to force the |
| 3881 |
establishment of an insecure media stream. The solution to both of |
| 3882 |
these problems involves the use of integrity protection over the SDP |
| 3883 |
session description. Ideally, this integrity protection provides |
| 3884 |
end-to-end integrity protection in order to protect from any man-in- |
| 3885 |
the-middle attack; secure multiparts such as Secure/Multipurpose |
| 3886 |
Internet Mail Extensions (S/MIME) [<a href="./rfc5751" title=""Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification"">RFC5751</a>] provide one such |
| 3887 |
solution; however, S/MIME requires use and availability of a Public |
| 3888 |
Key Infrastructure (PKI). A slightly less secure alternative when |
| 3889 |
using SIP, but generally much easier to deploy in practice, is to use |
| 3890 |
SIP Identity [<a href="./rfc4474" title=""Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)"">RFC4474</a>]; this requires the existence of an |
| 3891 |
authentication service (see [<a href="./rfc4474" title=""Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)"">RFC4474</a>]). Although this mechanism |
| 3892 |
still requires a PKI, it only requires that servers (as opposed to |
| 3893 |
end-users) have third-party validatable certificates, which |
| 3894 |
significantly reduces the barrier to entry by ordinary users. Yet |
| 3895 |
another, and considerably less secure, alternative is to use hop-by- |
| 3896 |
hop security only, e.g., TLS or IPsec thereby ensuring the integrity |
| 3897 |
of the offered SDP session description on a hop-by-hop basis. This |
| 3898 |
is less secure because SIP allows partially trusted intermediaries on |
| 3899 |
the signaling path, and such intermediaries processing the SIP |
| 3900 |
request at each hop would be able to perform a man-in-the-middle |
| 3901 |
attack by modifying the offered SDP session description. In simple |
| 3902 |
architectures where the two UA's proxies communicate directly, the |
| 3903 |
security provided by this method is roughly comparable to that |
| 3904 |
provided by the previously discussed signature-based mechanisms. |
| 3905 |
|
| 3906 |
Per the normal offer/answer procedures, as soon as the offerer has |
| 3907 |
generated an offer, the offerer must be prepared to receive media in |
| 3908 |
accordance with that offer. The SDP Capability Negotiation preserves |
| 3909 |
that behavior for the actual configuration in the offer; however, the |
| 3910 |
offerer has no way of knowing which configuration (actual or |
| 3911 |
potential) was selected by the answerer, until an answer indication |
| 3912 |
is received. This opens up a new security issue where an attacker |
| 3913 |
|
| 3914 |
|
| 3915 |
|
| 3916 |
<span class="grey">Andreasen Standards Track [Page 70]</span></pre> |
| 3917 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span> |
| 3918 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3919 |
|
| 3920 |
|
| 3921 |
may be able to interject media towards the offerer until the answer |
| 3922 |
is received. For example, the offerer may use plain RTP as the |
| 3923 |
actual configuration and Secure RTP as an alternative potential |
| 3924 |
configuration. Even though the answerer selects Secure RTP, the |
| 3925 |
offerer will not know that until he receives the answer, and hence an |
| 3926 |
attacker will be able to send media to the offerer meanwhile. The |
| 3927 |
easiest protection against such an attack is to not offer use of the |
| 3928 |
non-secure media stream in the actual configuration; however, that |
| 3929 |
may in itself have undesirable side effects: If the answerer does not |
| 3930 |
support the secure media stream and also does not support the |
| 3931 |
capability negotiation framework, then negotiation of the media |
| 3932 |
stream will fail. Alternatively, SDP security preconditions |
| 3933 |
[<a href="./rfc5027" title=""Security Preconditions for Session Description Protocol (SDP) Media Streams"">RFC5027</a>] can be used. This will ensure that media is not flowing |
| 3934 |
until session negotiation has completed and hence the selected |
| 3935 |
configuration is known. Use of preconditions however requires both |
| 3936 |
sides to support them. If they don't, and use of them is required, |
| 3937 |
the session will fail. As a (limited) work around to this, it is |
| 3938 |
RECOMMENDED that SIP entities generate an answer SDP session |
| 3939 |
description and send it to the offerer as soon as possible, for |
| 3940 |
example, in a 183 Session Progress message. This will limit the time |
| 3941 |
during which an attacker can send media to the offerer. <a href="#section-3.9">Section 3.9</a> |
| 3942 |
presents other alternatives as well. |
| 3943 |
|
| 3944 |
Additional security considerations apply to the answer SDP session |
| 3945 |
description as well. The actual configuration attribute tells the |
| 3946 |
offerer on which potential configuration the answer was based, and |
| 3947 |
hence an attacker that can either modify or remove the actual |
| 3948 |
configuration attribute in the answer can cause session failure as |
| 3949 |
well as extend the time window during which the offerer will accept |
| 3950 |
incoming media that does not conform to the actual answer. The |
| 3951 |
solutions to this SDP session description answer integrity problem |
| 3952 |
are the same as for the offer, i.e., use of end-to-end integrity |
| 3953 |
protection, SIP identity, or hop-by-hop protection. The mechanism to |
| 3954 |
use depends on the mechanisms supported by the offerer as well as the |
| 3955 |
acceptable security trade offs. |
| 3956 |
|
| 3957 |
As described in Sections <a href="#section-3.1">3.1</a> and <a href="#section-3.11">3.11</a>, SDP Capability Negotiation |
| 3958 |
conceptually allows an offerer to include many different offers in a |
| 3959 |
single SDP session description. This can cause the answerer to |
| 3960 |
process a large number of alternative potential offers, which can |
| 3961 |
consume significant memory and CPU resources. An attacker can use |
| 3962 |
this amplification feature to launch a denial-of-service attack |
| 3963 |
against the answerer. The answerer must protect itself from such |
| 3964 |
attacks. As explained in <a href="#section-3.11">Section 3.11</a>, the answerer can help reduce |
| 3965 |
the effects of such an attack by first discarding all potential |
| 3966 |
configurations that contain unsupported transport protocols, |
| 3967 |
unsupported or invalid mandatory attribute capabilities, or |
| 3968 |
unsupported mandatory extension configurations. The answerer should |
| 3969 |
|
| 3970 |
|
| 3971 |
|
| 3972 |
<span class="grey">Andreasen Standards Track [Page 71]</span></pre> |
| 3973 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span> |
| 3974 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 3975 |
|
| 3976 |
|
| 3977 |
also look out for potential configurations that are designed to pass |
| 3978 |
the above test, but nevertheless produce a large number of potential |
| 3979 |
configuration SDP session descriptions that cannot be supported. |
| 3980 |
|
| 3981 |
A possible way of achieving that is for an attacker to find a |
| 3982 |
valid session-level attribute that causes conflicts or otherwise |
| 3983 |
interferes with individual media description configurations. At |
| 3984 |
the time of publication of this document, we do not know of such |
| 3985 |
an SDP attribute; however, this does not mean it does not exist, |
| 3986 |
or that it will not exist in the future. If such attributes are |
| 3987 |
found to exist, implementers should explicitly protect against |
| 3988 |
them. |
| 3989 |
|
| 3990 |
A significant number of valid and supported potential configurations |
| 3991 |
may remain. However, since all of those contain only valid and |
| 3992 |
supported transport protocols and attributes, it is expected that |
| 3993 |
only a few of them will need to be processed on average. Still, the |
| 3994 |
answerer must ensure that it does not needlessly consume large |
| 3995 |
amounts of memory or CPU resources when processing those as well as |
| 3996 |
be prepared to handle the case where a large number of potential |
| 3997 |
configurations still need to be processed. |
| 3998 |
|
| 3999 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 4000 |
|
| 4001 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. New SDP Attributes</span> |
| 4002 |
|
| 4003 |
The IANA has registered the following new SDP attributes: |
| 4004 |
|
| 4005 |
Attribute name: csup |
| 4006 |
Long form name: Supported capability negotiation extensions |
| 4007 |
Type of attribute: Session-level and media-level |
| 4008 |
Subject to charset: No |
| 4009 |
Purpose: Option tags for supported SDP Capability |
| 4010 |
Negotiation extensions |
| 4011 |
Appropriate values: See <a href="./rfc5939#section-3.3.1">Section 3.3.1 of RFC 5939</a> |
| 4012 |
Contact name: Flemming Andreasen, [email protected] |
| 4013 |
|
| 4014 |
Attribute name: creq |
| 4015 |
Long form name: Required capability negotiation extensions |
| 4016 |
Type of attribute: Session-level and media-level |
| 4017 |
Subject to charset: No |
| 4018 |
Purpose: Option tags for required SDP Capability |
| 4019 |
Negotiation extensions |
| 4020 |
Appropriate values: See <a href="./rfc5939#section-3.3.2">Section 3.3.2 of RFC 5939</a> |
| 4021 |
Contact name: Flemming Andreasen, [email protected] |
| 4022 |
|
| 4023 |
|
| 4024 |
|
| 4025 |
|
| 4026 |
|
| 4027 |
|
| 4028 |
<span class="grey">Andreasen Standards Track [Page 72]</span></pre> |
| 4029 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span> |
| 4030 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 4031 |
|
| 4032 |
|
| 4033 |
Attribute name: acap |
| 4034 |
Long form name: Attribute capability |
| 4035 |
Type of attribute: Session-level and media-level |
| 4036 |
Subject to charset: No |
| 4037 |
Purpose: Attribute capability containing an attribute |
| 4038 |
name and associated value |
| 4039 |
Appropriate values: See <a href="./rfc5939#section-3.4.1">Section 3.4.1 of RFC 5939</a> |
| 4040 |
Contact name: Flemming Andreasen, [email protected] |
| 4041 |
|
| 4042 |
Attribute name: tcap |
| 4043 |
Long form name: Transport Protocol Capability |
| 4044 |
Type of attribute: Session-level and media-level |
| 4045 |
Subject to charset: No |
| 4046 |
Purpose: Transport protocol capability listing one or |
| 4047 |
more transport protocols |
| 4048 |
Appropriate values: See <a href="./rfc5939#section-3.4.2">Section 3.4.2 of RFC 5939</a> |
| 4049 |
Contact name: Flemming Andreasen, [email protected] |
| 4050 |
|
| 4051 |
Attribute name: pcfg |
| 4052 |
Long form name: Potential Configuration |
| 4053 |
Type of attribute: Media-level |
| 4054 |
Subject to charset: No |
| 4055 |
Purpose: Potential configuration for SDP Capability |
| 4056 |
Negotiation |
| 4057 |
Appropriate values: See <a href="./rfc5939#section-3.5.1">Section 3.5.1 of RFC 5939</a> |
| 4058 |
Contact name: Flemming Andreasen, [email protected] |
| 4059 |
|
| 4060 |
Attribute name: acfg |
| 4061 |
Long form name: Actual configuration |
| 4062 |
Type of attribute: Media-level |
| 4063 |
Subject to charset: No |
| 4064 |
Purpose: Actual configuration for SDP Capability |
| 4065 |
Negotiation |
| 4066 |
Appropriate values: See <a href="./rfc5939#section-3.5.2">Section 3.5.2 of RFC 5939</a> |
| 4067 |
Contact name: Flemming Andreasen, [email protected] |
| 4068 |
|
| 4069 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. New SDP Capability Negotiation Option Tag Registry</span> |
| 4070 |
|
| 4071 |
The IANA has created a new SDP Capability Negotiation Option Tag |
| 4072 |
registry. An IANA SDP Capability Negotiation Option Tag registration |
| 4073 |
MUST be documented in an RFC in accordance with the [<a href="./rfc5226" title="">RFC5226</a>] IETF |
| 4074 |
Review policy. The RFC MUST provide the name of the option tag, a |
| 4075 |
syntax, and a semantic specification of any new SDP attributes and |
| 4076 |
any extensions to the potential configuration ("a=pcfg") and actual |
| 4077 |
configuration ("a=acfg") attributes provided in this document. If |
| 4078 |
the extension defines any new SDP attributes that are intended to be |
| 4079 |
capabilities for use by the capability negotiation framework (e.g., |
| 4080 |
similar to "a=acap"), those capabilities MUST adhere to the |
| 4081 |
|
| 4082 |
|
| 4083 |
|
| 4084 |
<span class="grey">Andreasen Standards Track [Page 73]</span></pre> |
| 4085 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span> |
| 4086 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 4087 |
|
| 4088 |
|
| 4089 |
guidelines provided in <a href="#section-3.4.3">Section 3.4.3</a>. Extensions to the potential |
| 4090 |
and actual configuration attributes MUST adhere to the syntax |
| 4091 |
provided in Sections <a href="#section-3.5.1">3.5.1</a> and <a href="#section-3.5.2">3.5.2</a>. |
| 4092 |
|
| 4093 |
The option tag "cap-v0" is defined in this document, and the IANA has |
| 4094 |
registered this option tag. |
| 4095 |
|
| 4096 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. New SDP Capability Negotiation Potential Configuration Parameter</span> |
| 4097 |
<span class="h3"> Registry</span> |
| 4098 |
|
| 4099 |
The IANA has created a new SDP Capability Negotiation Potential |
| 4100 |
Configuration Parameter registry. An IANA SDP Capability Negotiation |
| 4101 |
Potential Configuration registration MUST be documented in an RFC in |
| 4102 |
accordance with the [<a href="./rfc5226" title="">RFC5226</a>] IETF Review policy. The RFC MUST |
| 4103 |
define the syntax and semantics of each new potential configuration |
| 4104 |
parameter. The syntax MUST adhere to the syntax provided for |
| 4105 |
extensions in <a href="#section-3.5.1">Section 3.5.1</a> and the semantics MUST adhere to the |
| 4106 |
semantics provided for extensions in <a href="#section-3.5.1">Section 3.5.1</a> and 3.5.2. |
| 4107 |
Associated with each registration MUST be the encoding name for the |
| 4108 |
parameter as well as a short descriptive name for it. |
| 4109 |
|
| 4110 |
The potential configuration parameters "a" for "attribute" and "t" |
| 4111 |
for "transport protocol" are defined in this document, and the IANA |
| 4112 |
has registered them. |
| 4113 |
|
| 4114 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span> |
| 4115 |
|
| 4116 |
The SDP Capability Negotiation solution defined in this document |
| 4117 |
draws on the overall capability negotiation framework that was |
| 4118 |
defined by [<a href="#ref-SDPng" title=""Session Description and Capability Negotiation"">SDPng</a>]. Also, the SDP Capability Negotiation solution is |
| 4119 |
heavily influenced by the discussions and work done by the SDP |
| 4120 |
Capability Negotiation Design Team. The following people in |
| 4121 |
particular provided useful comments and suggestions to either the |
| 4122 |
document itself or the overall direction of the solution defined |
| 4123 |
here: Francois Audet, John Elwell, Roni Even, Miguel Garcia, Robert |
| 4124 |
Gilman, Cullen Jennings, Jonathan Lennox, Matt Lepinski, Jean- |
| 4125 |
Francois Mule, Joerg Ott, Colin Perkins, Jonathan Rosenberg, Thomas |
| 4126 |
Stach, and Dan Wing. |
| 4127 |
|
| 4128 |
General Area review comments were provided by Christian Vogt, and |
| 4129 |
Stephen Kent provided Security Directorate review comments. Eric |
| 4130 |
Rescorla provided textual input to the Security Considerations. |
| 4131 |
Alexey Melnikov, Robert Sparks, and Magnus Westerlund provided |
| 4132 |
several review comments as well. |
| 4133 |
|
| 4134 |
|
| 4135 |
|
| 4136 |
|
| 4137 |
|
| 4138 |
|
| 4139 |
|
| 4140 |
<span class="grey">Andreasen Standards Track [Page 74]</span></pre> |
| 4141 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span> |
| 4142 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 4143 |
|
| 4144 |
|
| 4145 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 4146 |
|
| 4147 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span> |
| 4148 |
|
| 4149 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 4150 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 4151 |
|
| 4152 |
[<a id="ref-RFC3264">RFC3264</a>] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model |
| 4153 |
with Session Description Protocol (SDP)", <a href="./rfc3264">RFC 3264</a>, June |
| 4154 |
2002. |
| 4155 |
|
| 4156 |
[<a id="ref-RFC4566">RFC4566</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session |
| 4157 |
Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006. |
| 4158 |
|
| 4159 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 4160 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 4161 |
May 2008. |
| 4162 |
|
| 4163 |
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for |
| 4164 |
Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January |
| 4165 |
2008. |
| 4166 |
|
| 4167 |
[<a id="ref-RFC5245">RFC5245</a>] Rosenberg, J., "Interactive Connectivity Establishment |
| 4168 |
(ICE): A Protocol for Network Address Translator (NAT) |
| 4169 |
Traversal for Offer/Answer Protocols", <a href="./rfc5245">RFC 5245</a>, April |
| 4170 |
2010. |
| 4171 |
|
| 4172 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span> |
| 4173 |
|
| 4174 |
[<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, |
| 4175 |
A., Peterson, J., Sparks, R., Handley, M., and E. |
| 4176 |
Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, |
| 4177 |
June 2002. |
| 4178 |
|
| 4179 |
[<a id="ref-RFC3312">RFC3312</a>] Camarillo, G., Ed., Marshall, W., Ed., and J. Rosenberg, |
| 4180 |
"Integration of Resource Management and Session Initiation |
| 4181 |
Protocol (SIP)", <a href="./rfc3312">RFC 3312</a>, October 2002. |
| 4182 |
|
| 4183 |
[<a id="ref-RFC3262">RFC3262</a>] Rosenberg, J. and H. Schulzrinne, "Reliability of |
| 4184 |
Provisional Responses in Session Initiation Protocol |
| 4185 |
(SIP)", <a href="./rfc3262">RFC 3262</a>, June 2002. |
| 4186 |
|
| 4187 |
[<a id="ref-RFC3407">RFC3407</a>] Andreasen, F., "Session Description Protocol (SDP) Simple |
| 4188 |
Capability Declaration", <a href="./rfc3407">RFC 3407</a>, October 2002. |
| 4189 |
|
| 4190 |
[<a id="ref-RFC3551">RFC3551</a>] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and |
| 4191 |
Video Conferences with Minimal Control", STD 65, <a href="./rfc3551">RFC 3551</a>, |
| 4192 |
July 2003. |
| 4193 |
|
| 4194 |
|
| 4195 |
|
| 4196 |
<span class="grey">Andreasen Standards Track [Page 75]</span></pre> |
| 4197 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span> |
| 4198 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 4199 |
|
| 4200 |
|
| 4201 |
[<a id="ref-RFC3711">RFC3711</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. |
| 4202 |
Norrman, "The Secure Real-time Transport Protocol (SRTP)", |
| 4203 |
<a href="./rfc3711">RFC 3711</a>, March 2004. |
| 4204 |
|
| 4205 |
[<a id="ref-RFC3830">RFC3830</a>] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K. |
| 4206 |
Norrman, "MIKEY: Multimedia Internet KEYing", <a href="./rfc3830">RFC 3830</a>, |
| 4207 |
August 2004. |
| 4208 |
|
| 4209 |
[<a id="ref-RFC4145">RFC4145</a>] Yon, D. and G. Camarillo, "TCP-Based Media Transport in |
| 4210 |
the Session Description Protocol (SDP)", <a href="./rfc4145">RFC 4145</a>, |
| 4211 |
September 2005. |
| 4212 |
|
| 4213 |
[<a id="ref-RFC4474">RFC4474</a>] Peterson, J. and C. Jennings, "Enhancements for |
| 4214 |
Authenticated Identity Management in the Session |
| 4215 |
Initiation Protocol (SIP)", <a href="./rfc4474">RFC 4474</a>, August 2006. |
| 4216 |
|
| 4217 |
[<a id="ref-RFC4567">RFC4567</a>] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E. |
| 4218 |
Carrara, "Key Management Extensions for Session |
| 4219 |
Description Protocol (SDP) and Real Time Streaming |
| 4220 |
Protocol (RTSP)", <a href="./rfc4567">RFC 4567</a>, July 2006. |
| 4221 |
|
| 4222 |
[<a id="ref-RFC4568">RFC4568</a>] Andreasen, F., Baugher, M., and D. Wing, "Session |
| 4223 |
Description Protocol (SDP) Security Descriptions for Media |
| 4224 |
Streams", <a href="./rfc4568">RFC 4568</a>, July 2006. |
| 4225 |
|
| 4226 |
[<a id="ref-RFC4585">RFC4585</a>] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, |
| 4227 |
"Extended RTP Profile for Real-time Transport Control |
| 4228 |
Protocol (RTCP)-Based Feedback (RTP/AVPF)", <a href="./rfc4585">RFC 4585</a>, July |
| 4229 |
2006. |
| 4230 |
|
| 4231 |
[<a id="ref-RFC4588">RFC4588</a>] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R. |
| 4232 |
Hakenberg, "RTP Retransmission Payload Format", <a href="./rfc4588">RFC 4588</a>, |
| 4233 |
July 2006. |
| 4234 |
|
| 4235 |
[<a id="ref-RFC4756">RFC4756</a>] Li, A., "Forward Error Correction Grouping Semantics in |
| 4236 |
Session Description Protocol", <a href="./rfc4756">RFC 4756</a>, November 2006. |
| 4237 |
|
| 4238 |
[<a id="ref-RFC5027">RFC5027</a>] Andreasen, F. and D. Wing, "Security Preconditions for |
| 4239 |
Session Description Protocol (SDP) Media Streams", <a href="./rfc5027">RFC</a> |
| 4240 |
<a href="./rfc5027">5027</a>, October 2007. |
| 4241 |
|
| 4242 |
[<a id="ref-RFC5124">RFC5124</a>] Ott, J. and E. Carrara, "Extended Secure RTP Profile for |
| 4243 |
Real-time Transport Control Protocol (RTCP)-Based Feedback |
| 4244 |
(RTP/SAVPF)", <a href="./rfc5124">RFC 5124</a>, February 2008. |
| 4245 |
|
| 4246 |
[<a id="ref-RFC5751">RFC5751</a>] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet |
| 4247 |
Mail Extensions (S/MIME) Version 3.2 Message |
| 4248 |
Specification", <a href="./rfc5751">RFC 5751</a>, January 2010. |
| 4249 |
|
| 4250 |
|
| 4251 |
|
| 4252 |
<span class="grey">Andreasen Standards Track [Page 76]</span></pre> |
| 4253 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span> |
| 4254 |
<span class="grey"><a href="./rfc5939">RFC 5939</a> SDP Capability Negotiation September 2010</span> |
| 4255 |
|
| 4256 |
|
| 4257 |
[<a id="ref-RFC5763">RFC5763</a>] Fischl, J., Tschofenig, H., and E. Rescorla, "Framework |
| 4258 |
for Establishing a Secure Real-time Transport Protocol |
| 4259 |
(SRTP) Security Context Using Datagram Transport Layer |
| 4260 |
Security (DTLS)", <a href="./rfc5763">RFC 5763</a>, May 2010. |
| 4261 |
|
| 4262 |
[<a id="ref-RFC5764">RFC5764</a>] McGrew, D. and E. Rescorla, "Datagram Transport Layer |
| 4263 |
Security (DTLS) Extension to Establish Keys for the Secure |
| 4264 |
Real-time Transport Protocol (SRTP)", <a href="./rfc5764">RFC 5764</a>, May 2010. |
| 4265 |
|
| 4266 |
[<a id="ref-RFC5888">RFC5888</a>] Camarillo, G. and H. Schulzrinne, "The Session Description |
| 4267 |
Protocol (SDP) Grouping Framework", <a href="./rfc5888">RFC 5888</a>, June 2010. |
| 4268 |
|
| 4269 |
[<a id="ref-BESRTP">BESRTP</a>] Kaplan, H. and F. Audet, "Session Description Protocol |
| 4270 |
(SDP) Offer/Answer Negotiation For Best-Effort Secure |
| 4271 |
Real-Time Transport Protocol", Work in Progress, October |
| 4272 |
2006. |
| 4273 |
|
| 4274 |
[<a id="ref-ICETCP">ICETCP</a>] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach, |
| 4275 |
"TCP Candidates with Interactive Connectivity |
| 4276 |
Establishment (ICE)", Work in Progress, September 2010. |
| 4277 |
|
| 4278 |
[<a id="ref-SDPMedCap">SDPMedCap</a>] |
| 4279 |
Gilman, R., Even, R., and F. Andreasen, "SDP media |
| 4280 |
capabilities Negotiation", Work in Progress, July 2010. |
| 4281 |
|
| 4282 |
[<a id="ref-SDPng">SDPng</a>] Kutscher, D., Ott, J., and C. Bormann, "Session |
| 4283 |
Description and Capability Negotiation", Work in Progress, |
| 4284 |
February 2005. |
| 4285 |
|
| 4286 |
Author's Address |
| 4287 |
|
| 4288 |
Flemming Andreasen |
| 4289 |
Cisco Systems |
| 4290 |
Iselin, NJ 08830 |
| 4291 |
USA |
| 4292 |
|
| 4293 |
EMail: [email protected] |
| 4294 |
|
| 4295 |
|
| 4296 |
|
| 4297 |
|
| 4298 |
|
| 4299 |
|
| 4300 |
|
| 4301 |
|
| 4302 |
|
| 4303 |
|
| 4304 |
|
| 4305 |
|
| 4306 |
|
| 4307 |
|
| 4308 |
Andreasen Standards Track [Page 77] |
| 4309 |
</pre> |