idnits 2.17.1 draft-greevenbosch-mmusic-hitchhikersguide-sdp-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 5, 2012) is 4306 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'ICE' is mentioned on line 205, but not defined ** Obsolete normative reference: RFC 2327 (Obsoleted by RFC 4566) ** Obsolete normative reference: RFC 3266 (Obsoleted by RFC 4566) ** Obsolete normative reference: RFC 3388 (Obsoleted by RFC 5888) ** Obsolete normative reference: RFC 4091 (Obsoleted by RFC 5245) ** Obsolete normative reference: RFC 4474 (Obsoleted by RFC 8224) ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) ** Obsolete normative reference: RFC 4572 (Obsoleted by RFC 8122) ** Obsolete normative reference: RFC 4583 (Obsoleted by RFC 8856) Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 mmusic B. Greevenbosch 3 Internet-Draft Huawei Technologies 4 Intended status: Informational July 5, 2012 5 Expires: January 6, 2013 7 Hitchhiker's guide to the Session Description Protocol (SDP) 8 draft-greevenbosch-mmusic-hitchhikersguide-sdp-01 10 Abstract 12 The Session Initiation Protocol (SDP) is the subject of numerous 13 specifications that have been produced by the IETF. It can be 14 difficult to locate the right document, or even to determine the set 15 of Request for Comments (RFC) about SDP. This specification serves 16 as a guide to the SDP RFC series. It lists a current snapshot of the 17 specifications under the SDP umbrella, briefly summarises each, and 18 groups them into categories. 20 Note 22 Discussion and suggestions for improvement are requested, and should 23 be sent to mmusic@ietf.org. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on January 6, 2013. 42 Copyright Notice 44 Copyright (c) 2012 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 4 60 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 3. SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 3.1. Core SDP specifications . . . . . . . . . . . . . . . . . 7 63 3.2. General purpose infrastructure extensions . . . . . . . . 7 64 3.3. NAT Traversal . . . . . . . . . . . . . . . . . . . . . . 8 65 3.4. Minor extensions . . . . . . . . . . . . . . . . . . . . . 8 66 3.5. Security mechanisms . . . . . . . . . . . . . . . . . . . 8 67 3.6. Conferencing . . . . . . . . . . . . . . . . . . . . . . . 9 68 4. SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 69 4.1. Security mechanisms . . . . . . . . . . . . . . . . . . . 10 70 5. Documents left to handle . . . . . . . . . . . . . . . . . . . 11 71 5.1. SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 72 5.1.1. RFCs . . . . . . . . . . . . . . . . . . . . . . . . . 11 73 5.1.2. Working group drafts . . . . . . . . . . . . . . . . . 11 74 5.1.3. Individual drafts . . . . . . . . . . . . . . . . . . 11 75 5.2. SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 76 5.2.1. RFCs . . . . . . . . . . . . . . . . . . . . . . . . . 11 77 5.2.2. Working group drafts . . . . . . . . . . . . . . . . . 11 78 5.2.3. Individual drafts . . . . . . . . . . . . . . . . . . 12 79 5.3. H.248/Megaco . . . . . . . . . . . . . . . . . . . . . . . 12 80 5.3.1. RFCs . . . . . . . . . . . . . . . . . . . . . . . . . 12 81 5.3.2. Working group drafts . . . . . . . . . . . . . . . . . 12 82 5.3.3. Individual drafts . . . . . . . . . . . . . . . . . . 12 83 5.4. RTCP . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 84 5.4.1. RFCs . . . . . . . . . . . . . . . . . . . . . . . . . 12 85 5.4.2. Working group drafts . . . . . . . . . . . . . . . . . 12 86 5.4.3. Individual drafts . . . . . . . . . . . . . . . . . . 12 87 5.5. Yet unclassified . . . . . . . . . . . . . . . . . . . . . 12 88 5.5.1. RFCs . . . . . . . . . . . . . . . . . . . . . . . . . 12 89 5.5.2. Working group drafts . . . . . . . . . . . . . . . . . 13 90 5.5.3. Individual drafts . . . . . . . . . . . . . . . . . . 13 91 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 92 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 93 8. Normative References . . . . . . . . . . . . . . . . . . . . . 16 94 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19 96 1. Requirements notation 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [RFC2119]. 102 2. Introduction 104 The Session Description Protocol (SDP) [RFC4566] is the subject of 105 numerous specifications that have been produced by the IETF. It can 106 be difficult to locate the right document, or even to determine the 107 set of Request for Comments (RFC) about SDP. 109 This specification serves as a guide to the SDP RFC series. It is a 110 current snapshot of the specifications under the SDP umbrella at the 111 time of publication. It is anticipated that this document itself 112 will be regularly updated as SDP specifications mature. Furthermore, 113 it references many specifications, which, at the time of publication 114 of this document, were not yet finalised, and may eventually be 115 completed or abandoned. Therefore, the enumeration of specifications 116 here is a work-in-progress and subject to change. 118 For each specification, a paragraph or so description is included 119 that summarises the purpose of the specification. Each specification 120 also includes a letter that designates its category in the Standards 121 Track [RFC2026]. These values are: 123 S: Standards Track (Proposed Standard, Draft Standard, or 124 Standard) 126 E: Experimental 128 B: Best Current Practice 130 I: Informational 132 The specifications are grouped together by topic. The topics are: 134 Core: The SDP specifications that are expected to be utilised for 135 each session or registration an endpoint participates in. 137 General Purpose Infrastructure: General purpose extensions to SDP, 138 but the ones that are not expected to always be used. 140 NAT Traversal: Specifications to deal with firewall and NAT 141 traversal. 143 Quality of Service: Specifications related to multimedia quality of 144 service (QoS). 146 Operations and Management: Specifications related to configuration 147 and monitoring of SDP deployments. 149 Minor Extensions: Specifications that solve a narrow problem space 150 or provide an optimisation. 152 Security Mechanisms: Specifications providing security functionality 153 for SDP. 155 Conferencing: Specifications for multimedia conferencing. 157 Typically, SDP extensions fit naturally into topic areas, and 158 implementors interested in a particular topic often implement many or 159 all of the specifications in that area. There are some 160 specifications that fall into multiple topic areas, but generally 161 they will be listed only once. 163 This document itself is not an update to [RFC4566] or an extension to 164 SDP. It is an informational document, meant to guide newcomers, 165 implementers, and deployers to the many specifications associated 166 with SDP. 168 3. SDP 170 3.1. Core SDP specifications 172 RFC 2327, Session Description Protocol (S): [RFC2327] defines the 173 original SDP protocol. The RFC has been obsoleted by its 174 successor [RFC4566]. 176 RFC 3264, An Offer/Answer Model with the Session Description 177 Protocol (S): [RFC3264] defines how SDP is used with SIP [RFC3261] 178 to negotiate the parameters of a media session. It is in 179 widespread usage and an integral part of the behaviour of SIP. 181 RFC 4566, Session Description Protocol (S): [RFC4566] defines a 182 format for representing multimedia sessions. SDP objects are 183 carried in the body of SIP messages and, based on the offer/answer 184 model, are used to negotiate the media characteristics of a 185 session between users. 187 3.2. General purpose infrastructure extensions 189 RFC 3266, Support for IPv6 in Session Description Protocol (SDP) 190 (S): [RFC3266] describes the use of Internet Protocol Version 6 191 (IPv6) addresses in conjunction with the Session Description 192 Protocol (SDP). The document clarifies existing text in SDP in 193 regard to the syntax of IPv6 addresses. 195 RFC 3388, Grouping of Media Lines in the Session Description 196 Protocol (S): [RFC3388] defines a framework for grouping together 197 media streams in an SDP message. Such a grouping allows 198 relationships between these streams, such as which stream is the 199 audio for a particular video feed, to be expressed. 201 RFC 4091, The Alternative Network Address Types (ANAT) Semantics for 202 the Session Description Protocol (SDP) Grouping Framework (S): 203 [RFC4091] defines a mechanism for including both IPv4 and IPv6 204 addresses to establish a media stream. This mechanism has been 205 deprecated in favor of ICE [ICE]. 207 RFC 4145, TCP-Based Media Transport in the Session Description 208 Protocol (SDP) (S): [RFC4145] defines an extension to SDP for 209 setting up TCP-based sessions between user agents. It defines who 210 sets up the connection and how its lifecycle is managed. It has 211 seen relatively little usage due to the small number of media 212 types to date that use TCP. 214 RFC 5583, Signaling Media Decoding Dependency in the Session 215 Description Protocol (SDP) (S): [RFC5583] defines an extension to 216 the grouping framework from [RFC3388]. A "DDP" grouping semantics 217 identifier and a "depend" attribute are defined to express 218 decoding dependencies between different media streams. The "mid" 219 labeling mechanism from [RFC3388] is reused. 221 3.3. NAT Traversal 223 RFC3605, Real Time Control Protocol (RTCP) Attribute in the Session 224 Description Protocol (SDP) (S): [RFC3605] defines a way to 225 explicitly signal, within an SDP message, the IP address and port 226 for RTCP, rather than using the port+1 rule in the Real Time 227 Transport Protocol (RTP) [RFC3550]. It is needed for devices 228 behind NAT, and the specification is required by ICE. 230 3.4. Minor extensions 232 RFC3890, A Transport Independent Bandwidth Modifier for the Session 233 Description Protocol (SDP) (S): [RFC3890] specifies an SDP 234 extension that allows for the description of the bandwidth for a 235 media session that is independent of the underlying transport 236 mechanism. 238 RFC 4796, The SDP (Session Description Protocol) Content Attribute 239 (S): [RFC4796] defines an SDP attribute for describing the purpose 240 of a media stream. Examples include a slide view, the speaker, a 241 sign language feed, and so on. 243 3.5. Security mechanisms 245 RFC4567, Key Management Extensions for Session Description Protocol 246 (SDP) and Real Time Streaming Protocol (RTSP) (S): [RFC4567] 247 defines extensions to SDP that allow tunneling of a key management 248 protocol, namely MIKEY [RFC3830], through offer/answer exchanges. 249 This mechanism is one of three Secure Realtime Transport Protocol 250 (SRTP) keying techniques specified for SIP, with Datagram 251 Transport Layer Security (DTLS)-SRTP [RFC5683] having been 252 selected as the final solution. 254 RFC4568, Session Description Protocol (SDP) Security Descriptions 255 for Media Streams (S): [RFC4568] defines extensions to SDP that 256 allow for the negotiation of keying material directly through 257 offer/answer, without a separate key management protocol. This 258 mechanism, sometimes called sdescriptions, has the drawback that 259 the media keys are available to any entity that has visibility to 260 the SDP. It is one of three SRTP keying techniques specified for 261 SIP, with DTLS-SRTP [RFC5683] having been selected as the final 262 solution. 264 RFC4572, Connection-Oriented Media Transport over the Transport 265 Layer Security (TLS) Protocol in the Session Description Protocol 266 (SDP) (S): [RFC4572] specifies a mechanism for signaling TLS- 267 based media streams between endpoints. It expands the TCP-based 268 media signaling parameters defined in [RFC4145] to include 269 fingerprint information for TLS streams so that TLS can operate 270 between end hosts using self-signed certificates. 272 RFC5027, Security Preconditions for Session Description Protocol 273 Media Streams (S): [RFC5027] defines a precondition for use with 274 the preconditions framework [RFC3312]. The security precondition 275 prevents a session from being established until a security media 276 stream is set up. 278 3.6. Conferencing 280 RFC4574, The SDP (Session Description Protocol) Label Attribute (S): 281 [RFC4574] defines an SDP attribute for providing an opaque label 282 for media streams. These labels can be referred to by external 283 documents, and in particular, by conference policy documents. 284 This allows a UA to tie together documents it may obtain through 285 conferencing mechanisms to media streams to which they refer. 287 RFC4583, Session Description Protocol (SDP) Format for Binary Floor 288 Control Protocol (BFCP) Streams (S): [RFC4583] defines a mechanism 289 in SDP to signal floor control streams that use BFCP. It is used 290 for push-to-talk and conference floor control. 292 4. SIP 294 4.1. Security mechanisms 296 RFC3893, Session Initiation Protocol (SIP) Authenticated Identity 297 Body (AIB) Format (S): [RFC3893] defines a SIP message fragment 298 that can be signed in order to provide an authenticated identity 299 over a request. It was an early predecessor to [RFC4474], and 300 consequently AIB has seen no deployment. 302 RFC4474, Enhancements for Authenticated Identity Management in SIP 303 (S): [RFC4474] defines a mechanism for providing a 304 cryptographically verifiable identity of the calling party in a 305 SIP request. Known as "SIP Identity", this mechanism provides an 306 alternative to [RFC3325]. It has seen little deployment so far, 307 but its importance as a key construct for anti-spam techniques and 308 new security mechanisms makes it a core part of the SIP 309 specifications. 311 RFC 4916, Connected Identity in the Session Initiation Protocol 312 (SIP) (S): [RFC4916] formally updates [RFC3261]. It defines an 313 extension to SIP that allows a calling user to determine the 314 identity of the final called user (connected party). Due to 315 forwarding and retargeting services, this may not be the same as 316 the user that the caller was originally trying to reach. The 317 mechanism works in tandem with the SIP identity specification 318 [RFC4474] to provide signatures over the connected party identity. 319 It can also be used if a party identity changes mid call due to 320 third party call control actions or PSTN behavior. 322 5. Documents left to handle 324 5.1. SDP 326 5.1.1. RFCs 328 3108, 3890, 4317, 4570, 4583, 4585, 5104, 5245, 5432, 5547, 5576, 329 5669, 5763, 5888, 5898, 5939, 6188, 6236. 331 5.1.2. Working group drafts 333 draft-ietf-mmusic-media-loopback-16, 334 draft-ietf-mmusic-parallax-attribute-00, 335 draft-ietf-mmusic-rfc4566bis-04, draft-ietf-mmusic-sdp-cs-09, 336 draft-ietf-mmusic-sdp-media-capabilities-12, 337 draft-ietf-mmusic-traffic-class-for-sdp-00, 338 draft-ietf-mmusic-signal-3d-format-00, draft-ietf-payload-rtp-mvc. 340 5.1.3. Individual drafts 342 draft-boucadair-mmusic-altc-04, 343 draft-boucadair-mmusic-ipv6-use-cases-00, 344 draft-boulton-mmusic-sdp-control-package-attribute-07, 345 draft-holmberg-mmusic-sdp-bundle-negotiation-00, 346 draft-lennox-mmusic-sdp-source-selection-03, 347 draft-petithuguenin-mmusic-ice-attributes-level-02, 348 draft-westerlund-mmusic-sdp-bw-attribute-00. 350 5.2. SIP 352 5.2.1. RFCs 354 2976, 3087, 3204, 3261, 3263, 3265, 3311, 3312, 3313, 3323, 3325, 355 3326, 3329, 3372, 3398, 3420, 3427, 3428, 3486, 3524, 3578, 3581, 356 3608, 3665, 3666, 3680, 3840, 3841, 3842, 3856, 3857, 3891, 3892, 357 3903, 3910, 3911, 3959, 3960, 3969, 4411, 4412, 4117, 4235, 4240, 358 4320, 4458, 4483, 4488, 4497, 4508, 4538, 4575, 4579, 4662, 4730, 359 5049, 5079, 5360, 5361, 5362, 5363, 5365, 5366, 5367, 5368, 5373, 360 5393, 5621, 5626, 5627, 5628, 5630, 5658, 5727, 5767, 5839, 5922, 361 5923, 6011, 6035, 6050, 6072, 6086, 6157, 6442. 363 5.2.2. Working group drafts 365 draft-ietf-sip-saml-08, draft-ietf-sip-session-policy-framework-10. 367 5.2.3. Individual drafts 369 5.3. H.248/Megaco 371 5.3.1. RFCs 373 5125, 5615 375 5.3.2. Working group drafts 377 5.3.3. Individual drafts 379 5.4. RTCP 381 5.4.1. RFCs 383 3611, 6725, 6332 385 5.4.2. Working group drafts 387 5.4.3. Individual drafts 389 5.5. Yet unclassified 391 5.5.1. RFCs 393 2848; 394 3262; 395 3310; 396 3327; 397 3407: att-field definition for sqn, cdsc, cpar, cparmin, cparmax; 398 3515; 399 3556: bwtype definition for RS, RR; 400 3711: proto definition for RTP/AVPF; 401 3725; 402 3853; 403 3926: proto definition for FLUTE/UDP, att-field definition for flute- 404 tsi, flute-ch, FEC-declaration, FEC-OTI-extension, content-desc, 405 group attribute definition for CS; 406 4028; 407 4168; 408 4169; 409 4244; 410 4571: proto definition for TCP/RTP/AVP; 411 4975: proto definition for TCP/MSRP; att-field definition for accept- 412 types, accept-wrapped-types, max-size, path; 413 5124: proto definition for RTP/SAVPF; 414 5159: att-field definition for bcastversion, stkmstream, 415 SRTPAuthentication, SRTPROCTxRate; 416 5245: att-field definition for candidate, remote-candidates; 417 5285: att-field definition for extmap; 418 5432: att-field definition for qos-mech-send, qos-mech-recv; 419 5506: att-field definition for rtcp-rsize; 420 5760: att-field definition for rtcp-unicast; 421 5761: att-field definition for rtcp-mux; 422 5762: proto definition for DCCP, DCCP/RTP/AVP, DCCP/RTP/SAVP, DCCP/ 423 RTP/AVPF, DCCP/RTP/SAVPF, att-field definition for dccp-service code; 424 5764: proto definition for DCCP/TLS/RTP/SAVP, UDP/TLS/RTP/SAVP, UDP/ 425 TLS/RTP/SAVPF, DCCP/TLS/RTP/SAVPF; 426 5956: group attribute definition for FEC, FEC-FR; ssrc-group SDP 427 attribute definition for FEC-FR; 428 6064: proto definition for UDP/MBMS-FEC/RTP/AVP, UDP/MBMS-FEC/RTP/ 429 SAVP, UDP/MBMS-REPAIR, att-field definition for 3GPP-Integrity-Key, 430 3GPP-SDP-Auth, alt-group, att-field definition for 3GPP-QoE-Metrics, 431 3GP-Asset-Information, mbms-mode, mbms-repair, X-predecbufsize, 432 X-initpredecbufperiod, X-initpostdecbufperiod, X-decbyterate, 3gpp- 433 videopostdecbufsize, framesize, 3GPP-SRTP-Config, alt, 434 alt-default-id, 3GPP-Adaptation-Support, mbms-flowid; 435 6128: att-field definition for multicast-rtcp; 436 6189: att-field definition for zrtp-hash; 437 6193: att-field definition for ike-setup, psk-fingerprint; 438 6230: att-field definition for cfw-id; 439 6284: att-field definition for portmapping-req; 440 6285: att-field definition for rams-updates; "ack" and "nack" 441 attribute definition for rai; 442 6364: proto definition for FEC/UDP, UDP/FEC, att-field definition for 443 fec-source-flow, fec-repair-flow, repair-window. 445 5.5.2. Working group drafts 447 draft-ietf-mmusic-rfc2326bis-28 449 5.5.3. Individual drafts 450 6. Security Considerations 452 This specification is an overview of existing specifications and does 453 not introduce any security considerations on its own. 455 7. Acknowledgements 457 The author would like to thank Jonathan Rosenberg, the author of "A 458 Hitchhiker's guide to the Session Initiation Protocol (SIP)" 459 [RFC5411], which served as basis for this document, and from which 460 much text was copied. 462 The title of this document was inspired by the "The Hitchhiker's 463 Guide to the Galaxy" [HGTTG]. 465 Thanks to Gonzalo Salguiero and Yue Peiyu for their help identifying 466 related RFCs and providing feedback. 468 8. Normative References 470 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 471 3", BCP 9, RFC 2026, October 1996. 473 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 474 Requirement Levels", BCP 14, RFC 2119, March 1997. 476 [RFC2327] Handley, M. and V. Jacobson, "SDP: Session Description 477 Protocol", RFC 2327, April 1998. 479 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 480 A., Peterson, J., Sparks, R., Handley, M., and E. 481 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 482 June 2002. 484 [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model 485 with Session Description Protocol (SDP)", RFC 3264, 486 June 2002. 488 [RFC3266] Olson, S., Camarillo, G., and A. Roach, "Support for IPv6 489 in Session Description Protocol (SDP)", RFC 3266, 490 June 2002. 492 [RFC3312] Camarillo, G., Marshall, W., and J. Rosenberg, 493 "Integration of Resource Management and Session Initiation 494 Protocol (SIP)", RFC 3312, October 2002. 496 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 497 Extensions to the Session Initiation Protocol (SIP) for 498 Asserted Identity within Trusted Networks", RFC 3325, 499 November 2002. 501 [RFC3388] Camarillo, G., Eriksson, G., Holler, J., and H. 502 Schulzrinne, "Grouping of Media Lines in the Session 503 Description Protocol (SDP)", RFC 3388, December 2002. 505 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 506 Jacobson, "RTP: A Transport Protocol for Real-Time 507 Applications", STD 64, RFC 3550, July 2003. 509 [RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute 510 in Session Description Protocol (SDP)", RFC 3605, 511 October 2003. 513 [RFC3830] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K. 514 Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830, 515 August 2004. 517 [RFC3890] Westerlund, M., "A Transport Independent Bandwidth 518 Modifier for the Session Description Protocol (SDP)", 519 RFC 3890, September 2004. 521 [RFC3893] Peterson, J., "Session Initiation Protocol (SIP) 522 Authenticated Identity Body (AIB) Format", RFC 3893, 523 September 2004. 525 [RFC4091] Camarillo, G. and J. Rosenberg, "The Alternative Network 526 Address Types (ANAT) Semantics for the Session Description 527 Protocol (SDP) Grouping Framework", RFC 4091, June 2005. 529 [RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in 530 the Session Description Protocol (SDP)", RFC 4145, 531 September 2005. 533 [RFC4474] Peterson, J. and C. Jennings, "Enhancements for 534 Authenticated Identity Management in the Session 535 Initiation Protocol (SIP)", RFC 4474, August 2006. 537 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 538 Description Protocol", RFC 4566, July 2006. 540 [RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E. 541 Carrara, "Key Management Extensions for Session 542 Description Protocol (SDP) and Real Time Streaming 543 Protocol (RTSP)", RFC 4567, July 2006. 545 [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session 546 Description Protocol (SDP) Security Descriptions for Media 547 Streams", RFC 4568, July 2006. 549 [RFC4572] Lennox, J., "Connection-Oriented Media Transport over the 550 Transport Layer Security (TLS) Protocol in the Session 551 Description Protocol (SDP)", RFC 4572, July 2006. 553 [RFC4574] Levin, O. and G. Camarillo, "The Session Description 554 Protocol (SDP) Label Attribute", RFC 4574, August 2006. 556 [RFC4583] Camarillo, G., "Session Description Protocol (SDP) Format 557 for Binary Floor Control Protocol (BFCP) Streams", 558 RFC 4583, November 2006. 560 [RFC4796] Hautakorpi, J. and G. Camarillo, "The Session Description 561 Protocol (SDP) Content Attribute", RFC 4796, 562 February 2007. 564 [RFC4916] Elwell, J., "Connected Identity in the Session Initiation 565 Protocol (SIP)", RFC 4916, June 2007. 567 [RFC5027] Andreasen, F. and D. Wing, "Security Preconditions for 568 Session Description Protocol (SDP) Media Streams", 569 RFC 5027, October 2007. 571 [RFC5411] Rosenberg, J., "A Hitchhiker's Guide to the Session 572 Initiation Protocol (SIP)", RFC 5411, February 2009. 574 [RFC5583] Schierl, T. and S. Wenger, "Signaling Media Decoding 575 Dependency in the Session Description Protocol (SDP)", 576 RFC 5583, July 2009. 578 [RFC5683] Brusilovsky, A., Faynberg, I., Zeltsan, Z., and S. Patel, 579 "Password-Authenticated Key (PAK) Diffie-Hellman 580 Exchange", RFC 5683, February 2010. 582 [HGTTG] Adams, D., "The Hitchhiker's Guide to the Galaxy", 583 TS 26.234 v5.3.0, September 1979. 585 Author's Address 587 Bert Greevenbosch 588 Huawei Technologies Co., Ltd. 589 Huawei Industrial Base 590 Bantian, Longgang District 591 Shenzhen 518129 592 P.R. China 594 Phone: +86-755-28978088 595 Email: bert.greevenbosch@huawei.com