idnits 2.17.1 draft-ietf-mmusic-sdp-new-23.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2226. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2203. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2210. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2216. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 11 instances of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 -- The draft header indicates that this document obsoletes RFC3266, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC2327, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 10, 2004) is 7067 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '10' is defined on line 2099, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 2152, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2234 (ref. '4') (Obsoleted by RFC 4234) ** Obsolete normative reference: RFC 2279 (ref. '5') (Obsoleted by RFC 3629) ** Obsolete normative reference: RFC 2327 (ref. '6') (Obsoleted by RFC 4566) ** Obsolete normative reference: RFC 2396 (ref. '7') (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 2434 (ref. '8') (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 2732 (ref. '9') (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 3066 (ref. '10') (Obsoleted by RFC 4646, RFC 4647) ** Obsolete normative reference: RFC 3490 (ref. '11') (Obsoleted by RFC 5890, RFC 5891) ** Obsolete normative reference: RFC 3548 (ref. '12') (Obsoleted by RFC 4648) -- Obsolete informational reference (is this intentional?): RFC 1305 (ref. '13') (Obsoleted by RFC 5905) -- Obsolete informational reference (is this intentional?): RFC 2326 (ref. '16') (Obsoleted by RFC 7826) == Outdated reference: A later version (-15) exists of draft-ietf-mmusic-kmgmt-ext-12 == Outdated reference: A later version (-12) exists of draft-ietf-mmusic-sdescriptions-07 Summary: 14 errors (**), 0 flaws (~~), 9 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group M. Handley 2 Internet-Draft UCL 3 Obsoletes: 2327, 3266 (if V. Jacobson 4 approved) Packet Design 5 Expires: June 10, 2005 C. Perkins 6 University of Glasgow 7 December 10, 2004 9 SDP: Session Description Protocol 10 draft-ietf-mmusic-sdp-new-23.txt 12 Status of this Memo 14 This document is an Internet-Draft and is subject to all provisions 15 of section 3 of RFC 3667. By submitting this Internet-Draft, each 16 author represents that any applicable patent or other IPR claims of 17 which he or she is aware have been or will be disclosed, and any of 18 which he or she become aware will be disclosed, in accordance with 19 RFC 3668. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on June 10, 2005. 39 Copyright Notice 41 Copyright (C) The Internet Society (2004). 43 Abstract 45 This memo defines the Session Description Protocol (SDP). SDP is 46 intended for describing multimedia sessions for the purposes of 47 session announcement, session invitation, and other forms of 48 multimedia session initiation. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Glossary of Terms . . . . . . . . . . . . . . . . . . . . . 3 54 3. Examples of SDP Usage . . . . . . . . . . . . . . . . . . . 4 55 3.1 Multicast Session Announcement . . . . . . . . . . . . . . 4 56 3.2 Session Initiation . . . . . . . . . . . . . . . . . . . . 4 57 3.3 Streaming media . . . . . . . . . . . . . . . . . . . . . 4 58 3.4 Email and the World Wide Web . . . . . . . . . . . . . . . 4 59 4. Requirements and Recommendations . . . . . . . . . . . . . . 5 60 4.1 Media and Transport Information . . . . . . . . . . . . . 6 61 4.2 Timing Information . . . . . . . . . . . . . . . . . . . . 6 62 4.3 Private Sessions . . . . . . . . . . . . . . . . . . . . . 7 63 4.4 Obtaining Further Information about a Session . . . . . . 7 64 4.5 Categorisation . . . . . . . . . . . . . . . . . . . . . . 7 65 4.6 Internationalisation . . . . . . . . . . . . . . . . . . . 7 66 5. SDP Specification . . . . . . . . . . . . . . . . . . . . . 7 67 5.1 Protocol Version ("v=") . . . . . . . . . . . . . . . . . 10 68 5.2 Origin ("o=") . . . . . . . . . . . . . . . . . . . . . . 11 69 5.3 Session Name ("s=") . . . . . . . . . . . . . . . . . . . 12 70 5.4 Session Information ("i=") . . . . . . . . . . . . . . . . 12 71 5.5 URI ("u=") . . . . . . . . . . . . . . . . . . . . . . . . 12 72 5.6 Email Address and Phone Number ("e=" and "p=") . . . . . . 13 73 5.7 Connection Data ("c=") . . . . . . . . . . . . . . . . . . 14 74 5.8 Bandwidth ("b=") . . . . . . . . . . . . . . . . . . . . . 16 75 5.9 Timing ("t=") . . . . . . . . . . . . . . . . . . . . . . 17 76 5.10 Repeat Times ("r=") . . . . . . . . . . . . . . . . . . 18 77 5.11 Time Zones ("z=") . . . . . . . . . . . . . . . . . . . 18 78 5.12 Encryption Keys ("k=") . . . . . . . . . . . . . . . . . 19 79 5.13 Attributes ("a=") . . . . . . . . . . . . . . . . . . . 21 80 5.14 Media Descriptions ("m=") . . . . . . . . . . . . . . . 22 81 6. SDP Attributes . . . . . . . . . . . . . . . . . . . . . . . 24 82 7. Security Considerations . . . . . . . . . . . . . . . . . . 31 83 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 32 84 8.1 The "application/sdp" media type . . . . . . . . . . . . . 32 85 8.2 Registration of Parameters . . . . . . . . . . . . . . . . 33 86 8.3 Encryption Key Access Methods . . . . . . . . . . . . . . 38 87 9. SDP Grammar . . . . . . . . . . . . . . . . . . . . . . . . 38 88 10. Summary of Changes from RFC 2327 . . . . . . . . . . . . . . 43 89 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 44 90 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 44 91 12.1 Normative References . . . . . . . . . . . . . . . . . . . 44 92 12.2 Informative References . . . . . . . . . . . . . . . . . . 45 93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 46 94 Intellectual Property and Copyright Statements . . . . . . . 48 96 1. Introduction 98 When initiating multimedia teleconferences, voice-over-IP calls, 99 streaming video, or other sessions, there is a requirement to convey 100 media details, transport addresses, and other session description 101 metadata to the participants. 103 SDP provides a standard representation for such information, 104 irrespective of how that information is transported. SDP is purely a 105 format for session description - it does not incorporate a transport 106 protocol, and is intended to use different transport protocols as 107 appropriate, including the Session Announcement Protocol [14], 108 Session Initiation Protocol [15], Real-Time Streaming Protocol [16], 109 electronic mail using the MIME extensions, and the Hypertext 110 Transport Protocol. 112 SDP is intended to be general purpose so that it can be used in a 113 wide range of network environments and applications. However, it is 114 not intended to support negotiation of session content or media 115 encodings: this is viewed as outside the scope of session 116 description. 118 This memo updates RFC 2327 [6] in the light of implementation 119 experience, and adds a small number of new features. Section 10 120 outlines the changes introduced in this memo. 122 2. Glossary of Terms 124 The following terms are used in this document, and have specific 125 meaning within the context of this document. 127 Conference: A multimedia conference is a set of two or more 128 communicating users along with the software they are using to 129 communicate. 131 Session: A multimedia session is a set of multimedia senders and 132 receivers and the data streams flowing from senders to receivers. 133 A multimedia conference is an example of a multimedia session. 135 Session Description: A well defined format for conveying sufficient 136 information to discover and participate in a multimedia session. 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 140 document are to be interpreted as described in RFC 2119 [3]. 142 3. Examples of SDP Usage 144 3.1 Multicast Session Announcement 146 In order to assist the advertisement of multicast multimedia 147 conferences and other multicast sessions, and to communicate the 148 relevant session setup information to prospective participants, a 149 distributed session directory may be used. An instance of such a 150 session directory periodically sends packets containing a description 151 of the session to a well known multicast group. These advertisements 152 are received by other session directories such that potential remote 153 participants can use the session description to start the tools 154 required to participate in the session. 156 One protocol commonly used to implement such a distributed directory 157 is the Session Announcement Protocol, SAP [14]. SDP provides the 158 recommended session description format for such session 159 announcements. 161 3.2 Session Initiation 163 The Session Initiation Protocol, SIP [15] is an application layer 164 control protocol for creating, modifying and terminating sessions 165 such as Internet multimedia conferences, Internet telephone calls and 166 multimedia distribution. The SIP messages used to create sessions 167 carry session descriptions which allow participants to agree on a set 168 of compatible media types. These session descriptions are commonly 169 formatted using SDP. When used with SIP, the offer/answer model [17] 170 provides a limited framework for negotiation using SDP. 172 3.3 Streaming media 174 The Real Time Streaming Protocol, RTSP [16], is an application-level 175 protocol for control over the delivery of data with real-time 176 properties. RTSP provides an extensible framework to enable 177 controlled, on-demand delivery of real-time data, such as audio and 178 video. An RTSP client and server negotiate an appropriate set of 179 parameters for media delivery, partially using SDP syntax to describe 180 those parameters. 182 3.4 Email and the World Wide Web 184 Alternative means of conveying session descriptions include 185 electronic mail and the World Wide Web. For both email and WWW 186 distribution, the MIME content type "application/sdp" is used. This 187 enables the automatic launching of applications for participation in 188 the session from the WWW client or mail reader in a standard manner. 190 Note that announcements of multicast sessions made only via email or 191 the World Wide Web (WWW) do not have the property that the receiver 192 of a session announcement can necessarily receive the session because 193 the multicast sessions may be restricted in scope, and access to the 194 WWW server or reception of email is possible outside this scope. 195 Session announcements made using SAP do not suffer this mismatch. 197 4. Requirements and Recommendations 199 The purpose of SDP is to convey information about media streams in 200 multimedia sessions to allow the recipients of a session description 201 to participate in the session. SDP is primarily intended for use in 202 an internetwork, although it is sufficiently general that it can 203 describe conferences in other network environments. Media streams 204 can be many-to-many. The times during which the session is active 205 need not be continuous. 207 Thus far, multicast based sessions on the Internet have differed from 208 many other forms of conferencing in that anyone receiving the traffic 209 can join the session (unless the session traffic is encrypted). In 210 such an environment, SDP serves two primary purposes. It is a means 211 to communicate the existence of a session, and is a means to convey 212 sufficient information to enable joining and participating in the 213 session. In a unicast environment, only the latter purpose is likely 214 to be relevant. 216 An SDP session description includes: 218 o Session name and purpose 220 o Time(s) the session is active 222 o The media comprising the session 224 o Information needed to receive those media (addresses, ports, 225 formats and so on) 227 As resources necessary to participate in a session may be limited, 228 some additional information may also be desirable: 230 o Information about the bandwidth to be used by the session 232 o Contact information for the person responsible for the session 234 In general, SDP must convey sufficient information to enable 235 applications to join a session (with the possible exception of 236 encryption keys), and to announce the resources to be used to any 237 non-participants that may need to know (this latter feature is 238 primarily useful when SDP is used with a multicast session 239 announcement protocol). 241 4.1 Media and Transport Information 243 An SDP session description includes the following media information: 245 o The type of media (video, audio, etc.) 247 o The transport protocol (RTP/UDP/IP, H.320, etc.) 249 o The format of the media (H.261 video, MPEG video, etc.) 251 In addition to media format and transport protocol, SDP conveys 252 address and port details. For an IP multicast session, these 253 comprise: 255 o The multicast group address for media 257 o The transport port for media 259 This address and port are the destination address and destination 260 port of the multicast stream, whether being sent, received, or both. 262 For unicast IP sessions, the following are conveyed: 264 o The remote address for media 266 o The remote transport port for media 268 The semantics of this address and port depend on the media and 269 transport protocol defined. By default, this SHOULD be the remote 270 address and remote port to which data is sent. Some media types MAY 271 redefine this behaviour, but this is NOT RECOMMENDED. 273 4.2 Timing Information 275 Sessions may either be bounded or unbounded in time. Whether or not 276 they are bounded, they may be only active at specific times. SDP can 277 convey: 279 o An arbitrary list of start and stop times bounding the session 281 o For each bound, repeat times such as "every Wednesday at 10am for 282 one hour" 284 This timing information is globally consistent, irrespective of local 285 time zone or daylight saving time. 287 4.3 Private Sessions 289 It is possible to create both public sessions and private sessions. 290 SDP itself does not distinguish between these: private sessions are 291 typically conveyed by encrypting the session description during 292 distribution. The details of how encryption is performed are 293 dependent on the mechanism used to convey SDP: mechanisms are 294 currently defined for SDP transported using SAP [14] and SIP [15], 295 others may be defined in future. 297 If a session announcement is private it is possible to use that 298 private announcement to convey encryption keys necessary to decode 299 each of the media in a conference, including enough information to 300 know which encryption scheme is used for each media. 302 4.4 Obtaining Further Information about a Session 304 A session description should convey enough information to decide 305 whether or not to participate in a session. SDP may include 306 additional pointers in the form of Universal Resources Identifiers 307 (URIs) for more information about the session. 309 4.5 Categorisation 311 When many session descriptions are being distributed by SAP, or any 312 other advertisement mechanism, it may be desirable to filter session 313 announcements that are of interest from those that are not. SDP 314 supports a categorisation mechanism for sessions that is capable of 315 being automated. 317 4.6 Internationalisation 319 The SDP specification recommends the use of the ISO 10646 character 320 sets in the UTF-8 encoding [5] to allow many different languages to 321 be represented. However, to assist in compact representations, SDP 322 also allows other character sets such as ISO 8859-1 to be used when 323 desired. Internationalisation only applies to free-text fields 324 (session name and background information), and not to SDP as a whole. 326 5. SDP Specification 328 An SDP session description is denoted by the MIME content type 329 "application/sdp" (See Section 8). 331 An SDP session description is entirely textual using the ISO 10646 332 character set in UTF-8 encoding. SDP field names and attribute names 333 use only the US-ASCII subset of UTF-8, but textual fields and 334 attribute values MAY use the full ISO 10646 character set. Field and 335 attribute values which use the full UTF-8 character set are never 336 directly compared, hence there is no requirement for UTF-8 337 normalisation. The textual form, as opposed to a binary encoding 338 such as ASN.1 or XDR, was chosen to enhance portability, to enable a 339 variety of transports to be used, and to allow flexible, text-based 340 toolkits to be used to generate and process session descriptions. 341 However, since SDP may be used in environments where the maximum 342 permissible size of a session description is limited, the encoding is 343 deliberately compact. Also, since announcements may be transported 344 via very unreliable means or damaged by an intermediate caching 345 server, the encoding was designed with strict order and formatting 346 rules so that most errors would result in malformed session 347 announcements which could be detected easily and discarded. This 348 also allows rapid discarding of encrypted session announcements for 349 which a receiver does not have the correct key. 351 An SDP session description consists of a number of lines of text of 352 the form: 354 = 356 where MUST be exactly one case-significant character and 357 is structured text whose format depends on . In 358 general is either a number of fields delimited by a single 359 space character, or a free format string. Whitespace MUST NOT be 360 used either side of the "=" sign. 362 An SDP session description consists of a session-level section 363 followed by zero or more media-level sections. The session-level 364 part starts with a "v=" line and continues to the first media-level 365 section. The media description starts with an "m=" line and 366 continues to the next media description or end of the whole session 367 description. In general, session-level values are the default for 368 all media unless overridden by an equivalent media-level value. 370 Some lines in each description are REQUIRED and some are OPTIONAL but 371 all MUST appear in exactly the order given here (the fixed order 372 greatly enhances error detection and allows for a simple parser). 373 OPTIONAL items are marked with a "*". 375 Session description 376 v= (protocol version) 377 o= (owner/creator and session identifier) 378 s= (session name) 379 i=* (session information) 380 u=* (URI of description) 381 e=* (email address) 382 p=* (phone number) 383 c=* (connection information - not required if included in 384 all media) 385 b=* (zero or more bandwidth information lines) 386 One or more time descriptions ("t=" and "r=" lines, see below) 387 z=* (time zone adjustments) 388 k=* (encryption key) 389 a=* (zero or more session attribute lines) 390 Zero or more media descriptions 392 Time description 393 t= (time the session is active) 394 r=* (zero or more repeat times) 396 Media description, if present 397 m= (media name and transport address) 398 i=* (media title) 399 c=* (connection information - optional if included at 400 session-level) 401 b=* (zero or more bandwidth information lines) 402 k=* (encryption key) 403 a=* (zero or more media attribute lines) 405 The set of type letters is deliberately small and not intended to be 406 extensible -- an SDP parser MUST completely ignore any session 407 description that contains a type letter that it does not understand. 408 The attribute mechanism ("a=" described below) is the primary means 409 for extending SDP and tailoring it to particular applications or 410 media. Some attributes (the ones listed in Section 6 of this memo) 411 have a defined meaning, but others may be added on an application-, 412 media- or session-specific basis. An SDP parser MUST ignore any 413 attribute it doesn't understand. 415 An SDP session description may contain URIs which reference external 416 content in the "u=", "k=" and "a=" lines. These URIs may be 417 dereferenced in some cases, making the session description non-self 418 contained. 420 The connection ("c=") and attribute ("a=") information in the 421 session-level section applies to all the media of that session unless 422 overridden by connection information or an attribute of the same name 423 in the media description. For instance, in the example below, each 424 media behaves as if it were given a "recvonly" attribute. 426 An example SDP description is: 428 v=0 429 o=jdoe 2890844526 2890842807 IN IP4 10.47.16.5 430 s=SDP Seminar 431 i=A Seminar on the session description protocol 432 u=http://www.example.com/seminars/sdp.pdf 433 e=j.doe@example.com (Jane Doe) 434 c=IN IP4 224.2.17.12/127 435 t=2873397496 2873404696 436 a=recvonly 437 m=audio 49170 RTP/AVP 0 438 m=video 51372 RTP/AVP 99 439 a=rtpmap:99 h263-1998/90000 441 Text fields such as the session name and information are octet 442 strings which may contain any octet with the exceptions of 0x00 443 (Nul), 0x0a (ASCII newline) and 0x0d (ASCII carriage return). The 444 sequence CRLF (0x0d0a) is used to end a record, although parsers 445 SHOULD be tolerant and also accept records terminated with a single 446 newline character. If the "a=charset" attribute is not present, 447 these octet strings MUST be interpreted as containing ISO-10646 448 characters in UTF-8 encoding (the presence of the "a=charset" 449 attribute MAY force some fields to be interpreted differently). 451 A session description can contain domain names in the "o=", "u=", 452 "e=", "c=" and "a=" lines. Any domain name used in SDP MUST comply 453 with [1], [2]. Internationalised domain names (IDNs) MUST be 454 represented using the ASCII Compatible Encoding (ACE) form defined in 455 [11] and MUST NOT be directly represented in UTF-8 or any other 456 encoding (this requirement is for compatibility with RFC 2327 and 457 other SDP-related standards, which predate the development of 458 internationalized domain names). 460 5.1 Protocol Version ("v=") 462 v=0 464 The "v=" field gives the version of the Session Description Protocol. 465 This memo defines version 0. There is no minor version number. 467 5.2 Origin ("o=") 469 o= 470 472 The "o=" field gives the originator of the session (her username and 473 the address of the user's host) plus a session identifier and version 474 number: 476 is the user's login on the originating host, or it is "-" 477 if the originating host does not support the concept of user ids. 478 The MUST NOT contain spaces. 480 is a numeric string such that the tuple of , 481 , , and form a 482 globally unique identifier for the session. The method of 483 allocation is up to the creating tool, but it has been 484 suggested that a Network Time Protocol (NTP) format timestamp be 485 used to ensure uniqueness [13]. 487 is a version number for this session description. Its 488 usage is up to the creating tool, so long as is 489 increased when a modification is made to the session data. Again, 490 it is RECOMMENDED that an NTP format timestamp is used. 492 is a text string giving the type of network. Initially 493 "IN" is defined to have the meaning "Internet", but other values 494 MAY be registered in future (see Section 8). 496 is a text string giving the type of the address that 497 follows. Initially "IP4" and "IP6" are defined, but other values 498 MAY be registered in future (see Section 8). 500 is the address of the machine from which the 501 session was created. For an address type of IP4, this is either 502 the fully-qualified domain name of the machine, or the 503 dotted-decimal representation of the IP version 4 address of the 504 machine. For an address type of IP6, this is either the 505 fully-qualified domain name of the machine, or the compressed 506 textual representation of the IP version 6 address of the machine. 507 For both IP4 and IP6, the fully-qualified domain name is the form 508 that SHOULD be given unless this is unavailable, in which case the 509 globally unique address MAY be substituted. A local IP address 510 MUST NOT be used in any context where the SDP description might 511 leave the scope in which the address is meaningful. 513 In general, the "o=" field serves as a globally unique identifier for 514 this version of this session description, and the subfields excepting 515 the version taken together identify the session irrespective of any 516 modifications. 518 For privacy reasons, it is sometimes desirable to obfuscate the 519 username and IP address of the session originator. If this is a 520 concern, an arbitrary and private MAY be 521 chosen to populate the "o=" field, provided these are selected in a 522 manner that does not affect the global uniqueness of the field. 524 5.3 Session Name ("s=") 526 s= 528 The "s=" field is the textual session name. There MUST be one and 529 only one "s=" field per session description. The "s=" field MUST NOT 530 be empty and SHOULD contain ISO 10646 characters (but see also the 531 "a=charset" attribute). If a session has no meaningful name, the 532 value "s= " SHOULD be used (i.e. a single space as the session 533 name). 535 5.4 Session Information ("i=") 537 i= 539 The "i=" field provides textual information about the session. There 540 MUST be at most one session-level "i=" field per session description, 541 and at most one "i=" field per media. If the "a=charset" attribute 542 is present, it specifies the character set used in the "i=" field. 543 If the "a=charset" attribute is not present, the "i=" field MUST 544 contain ISO 10646 characters in UTF-8 encoding. 546 A single "i=" field MAY also be used for each media definition. In 547 media definitions, "i=" fields are primarily intended for labelling 548 media streams. As such, they are most likely to be useful when a 549 single session has more than one distinct media stream of the same 550 media type. An example would be two different whiteboards, one for 551 slides and one for feedback and questions. 553 The "i=" field is intended to provide a free-form human readable 554 description of the session or the purpose of a media stream. It is 555 not suitable for parsing by automata. 557 5.5 URI ("u=") 559 u= 561 A URI is a Universal Resource Identifier as used by WWW clients [7], 562 [9]. The URI should be a pointer to additional information about the 563 session. This field is OPTIONAL, but if it is present it MUST be 564 specified before the first media field. No more than one URI field 565 is allowed per session description. 567 5.6 Email Address and Phone Number ("e=" and "p=") 569 e= 570 p= 572 The "e=" and "p=" lines specify contact information for the person 573 responsible for the conference. This is not necessarily the same 574 person that created the conference announcement. 576 Inclusion of an email address or phone number is OPTIONAL. Note that 577 the previous version of SDP specified that either an email field or a 578 phone field MUST be specified, but this was widely ignored. The 579 change brings the specification into line with common usage. 581 If the email address or phone number are present, they MUST be 582 specified before the first media field. More than one email or phone 583 field can be given for a session description. 585 Phone numbers SHOULD be given in the form of an international public 586 telecommunication number (see ITU-T Recommendation E.164) preceded by 587 a "+". Spaces and hyphens may be used to split up a phone field to 588 aid readability if desired. For example: 590 p=+1 617 555-6011 592 Both email addresses and phone numbers can have an OPTIONAL free text 593 string associated with them, normally giving the name of the person 594 who may be contacted. This MUST be enclosed in parenthesis if it is 595 present. For example: 597 e=j.doe@example.com (Jane Doe) 599 The alternative RFC 2822 name quoting convention is also allowed for 600 both email addresses and phone numbers. For example: 602 e=Jane Doe 604 The free text string SHOULD be in the ISO-10646 character set with 605 UTF-8 encoding, or alternatively in ISO-8859-1 or other encodings if 606 the appropriate session-level "a=charset" attribute is set. 608 5.7 Connection Data ("c=") 610 c= 612 The "c=" field contains connection data. 614 A session description MUST contain either at least one "c=" field in 615 each media description or a single "c=" field at the session level. 616 It MAY contain a single session-level "c=" field and additional "c=" 617 field(s) per media description, in which case the per-media values 618 override the session-level settings for the respective media. 620 The first sub-field ("") is the network type, which is a 621 text string giving the type of network. Initially "IN" is defined to 622 have the meaning "Internet", but other values MAY be registered in 623 the future (see Section 8). 625 The second sub-field ("") is the address type. This allows 626 SDP to be used for sessions that are not IP based. This memo only 627 defines IP4 and IP6, but other values MAY be registered in the future 628 (see Section 8). 630 The third sub-field ("") is the connection 631 address. OPTIONAL sub-fields MAY be added after the connection 632 address depending on the value of the field. 634 When the is IP4 and IP6, the connection address is defined 635 as follows: 637 o If the session is multicast, the connection address will be an IP 638 multicast group address. If the session is not multicast, then 639 the connection address contains the unicast IP address of the 640 expected data source or data relay or data sink as determined by 641 additional attribute fields. It is not expected that unicast 642 addresses will be given in a session description that is 643 communicated by a multicast announcement, though this is not 644 prohibited. 646 o Sessions using an IPv4 multicast connection address MUST also have 647 a time to live (TTL) value present in addition to the multicast 648 address. The TTL and the address together define the scope with 649 which multicast packets sent in this conference will be sent. TTL 650 values MUST be in the range 0-255. While the TTL MUST be 651 specified, its use to scope multicast traffic is deprecated; 652 applications SHOULD use an administratively scoped address 653 instead. 655 The TTL for the session is appended to the address using a slash as a 656 separator. An example is: 658 c=IN IP4 224.2.36.42/127 660 IPv6 multicast does not use TTL scoping, and hence the TTL value MUST 661 NOT be present for IPv6 multicast. It is expected that IPv6 scoped 662 addresses will be used to limit the scope of conferences. 664 Hierarchical or layered encoding schemes are data streams where the 665 encoding from a single media source is split into a number of layers. 666 The receiver can choose the desired quality (and hence bandwidth) by 667 only subscribing to a subset of these layers. Such layered encodings 668 are normally transmitted in multiple multicast groups to allow 669 multicast pruning. This technique keeps unwanted traffic from sites 670 only requiring certain levels of the hierarchy. For applications 671 requiring multiple multicast groups, we allow the following notation 672 to be used for the connection address: 674 [/]/ 676 If the number of addresses is not given it is assumed to be one. 677 Multicast addresses so assigned are contiguously allocated above the 678 base address, so that, for example: 680 c=IN IP4 224.2.1.1/127/3 682 would state that addresses 224.2.1.1, 224.2.1.2 and 224.2.1.3 are to 683 be used at a TTL of 127. This is semantically identical to including 684 multiple "c=" lines in a media description: 686 c=IN IP4 224.2.1.1/127 687 c=IN IP4 224.2.1.2/127 688 c=IN IP4 224.2.1.3/127 690 Similarly, an IPv6 example would be: 692 c=IN IP6 FF15::101/3 694 which is semantically equivalent to: 696 c=IN IP6 FF15::101 697 c=IN IP6 FF15::102 698 c=IN IP6 FF15::103 700 (remembering that the TTL field is not present in IPv6 multicast). 702 Multiple addresses or "c=" lines MAY be specified on a per-media 703 basis only if they provide multicast addresses for different layers 704 in a hierarchical or layered encoding scheme. They MUST NOT be 705 specified for a session-level "c=" field. 707 The slash notation for multiple addresses described above MUST NOT be 708 used for IP unicast addresses. 710 5.8 Bandwidth ("b=") 712 b=: 714 This OPTIONAL field denotes the proposed bandwidth to be used by the 715 session or media. The is an alphanumeric modifier giving 716 the meaning of the figure. Two values are defined in 717 this specification, but other values MAY be registered in future (see 718 Section 8 and [20], [24]): 720 CT If the bandwidth of a session or media in a session is different 721 from the bandwidth implicit from the scope, a "b=CT:..." line 722 SHOULD be supplied for the session giving the proposed upper limit 723 to the bandwidth used (the "conference total" bandwidth). The 724 primary purpose of this is to give an approximate idea as to 725 whether two or more sessions can co-exist simultaneously. When 726 using the CT modifier with RTP, if several RTP sessions are part 727 of the conference, the conference total refers to total bandwidth 728 of all RTP sessions. 730 AS The bandwidth is interpreted to be application-specific (it will 731 be the application's concept of maximum bandwidth). Normally this 732 will coincide with what is set on the application's "maximum 733 bandwidth" control if applicable. For RTP based applications, AS 734 gives the RTP "session bandwidth" as defined in Section 6.2 of 735 [18]. 737 Note that CT gives a total bandwidth figure for all the media at all 738 sites. AS gives a bandwidth figure for a single media at a single 739 site, although there may be many sites sending simultaneously. 741 A prefix "X-" is defined for names. This is intended for 742 experimental purposes only. For example: 744 b=X-YZ:128 746 Use of the "X-" prefix is NOT RECOMMENDED: instead new modifiers 747 SHOULD be registered with IANA in the standard namespace. SDP 748 parsers MUST ignore bandwidth fields with unknown modifiers. 749 Modifiers MUST be alpha-numeric and, although no length limit is 750 given, they are recommended to be short. 752 The is interpreted as kilobits per second by default. 753 The definition of a new modifier MAY specify that the 754 bandwidth is to be interpreted in some alternative unit (the "CT" and 755 "AS" modifiers defined in this memo use the default units). 757 5.9 Timing ("t=") 759 t= 761 The "t=" lines specify the start and stop times for a session. 762 Multiple "t=" lines MAY be used if a session is active at multiple 763 irregularly spaced times; each additional "t=" lines specifies an 764 additional period of time for which the session will be active. If 765 the session is active at regular times, an "r=" line (see below) 766 should be used in addition to, and following, a "t=" line - in which 767 case the "t=" line specifies the start and stop times of the repeat 768 sequence. 770 The first and second sub-fields give the start and stop times for the 771 session respectively. These values are the decimal representation of 772 Network Time Protocol (NTP) time values in seconds since 1900 [13]. 773 To convert these values to UNIX time, subtract decimal 2208988800. 775 NTP timestamps are elsewhere represented by 64 bit values which wrap 776 sometime in the year 2036. Since SDP uses an arbitrary length 777 decimal representation, this should not cause an issue (SDP 778 timestamps MUST continue counting seconds since 1900, NTP will use 779 the value modulo the 64 bit limit). 781 If the is set to zero, then the session is not bounded, 782 though it will not become active until after the . If 783 the is also zero, the session is regarded as permanent. 785 User interfaces SHOULD strongly discourage the creation of unbounded 786 and permanent sessions as they give no information about when the 787 session is actually going to terminate, and so make scheduling 788 difficult. 790 The general assumption may be made, when displaying unbounded 791 sessions that have not timed out to the user, that an unbounded 792 session will only be active until half an hour from the current time 793 or the session start time, whichever is the later. If behaviour 794 other than this is required, an end-time SHOULD be given and modified 795 as appropriate when new information becomes available about when the 796 session should really end. 798 Permanent sessions may be shown to the user as never being active 799 unless there are associated repeat times which state precisely when 800 the session will be active. In general, permanent sessions SHOULD 801 NOT be created for any session expected to have a duration of less 802 than 2 months, and should be discouraged for sessions expected to 803 have a duration of less than 6 months. 805 5.10 Repeat Times ("r=") 807 r= 809 "r=" fields specify repeat times for a session. For example, if a 810 session is active at 10am on Monday and 11am on Tuesday for one hour 811 each week for three months, then the in the 812 corresponding "t=" field would be the NTP representation of 10am on 813 the first Monday, the would be 1 week, the would be 1 hour, and the offsets would be zero and 25 815 hours. The corresponding "t=" field stop time would be the NTP 816 representation of the end of the last session three months later. By 817 default all fields are in seconds, so the "r=" and "t=" fields might 818 be: 820 t=3034423619 3042462419 821 r=604800 3600 0 90000 823 To make description more compact, times may also be given in units of 824 days, hours or minutes. The syntax for these is a number immediately 825 followed by a single case-sensitive character. Fractional units are 826 not allowed - a smaller unit should be used instead. The following 827 unit specification characters are allowed: 829 d - days (86400 seconds) 830 h - hours (3600 seconds) 831 m - minutes (60 seconds) 832 s - seconds (allowed for completeness but NOT RECOMMENDED) 834 Thus, the above session announcement could also have been written: 836 r=7d 1h 0 25h 838 Monthly and yearly repeats cannot be directly specified with a single 839 SDP repeat time - instead separate "t=" fields should be used to 840 explicitly list the session times. 842 5.11 Time Zones ("z=") 844 z= .... 846 To schedule a repeated session which spans a change from daylight 847 saving time to standard time or vice-versa, it is necessary to 848 specify offsets from the base time. This is required because 849 different time zones change time at different times of day, different 850 countries change to or from daylight time on different dates, and 851 some countries do not have daylight saving time at all. 853 Thus in order to schedule a session that is at the same time winter 854 and summer, it must be possible to specify unambiguously by whose 855 time zone a session is scheduled. To simplify this task for 856 receivers, we allow the sender to specify the NTP time that a time 857 zone adjustment happens and the offset from the time when the session 858 was first scheduled. The "z=" field allows the sender to specify a 859 list of these adjustment times and offsets from the base time. 861 An example might be: 863 z=2882844526 -1h 2898848070 0 865 This specifies that at time 2882844526 the time base by which the 866 session's repeat times are calculated is shifted back by 1 hour, and 867 that at time 2898848070 the session's original time base is restored. 868 Adjustments are always relative to the specified start time - they 869 are not cumulative. Adjustments apply to all "t=" and "r=" lines in 870 a session description. 872 If a session is likely to last several years, it is expected that the 873 session announcement will be modified periodically rather than 874 transmit several years worth of adjustments in one session 875 announcement. 877 5.12 Encryption Keys ("k=") 879 k= 880 k=: 882 If transported over a secure and trusted channel, the session 883 description protocol MAY be used to convey encryption keys. A simple 884 mechanism for key exchange is provided by the key field ("k=") 885 although this is primarily supported for compatibility with older 886 implementations and its use is NOT RECOMMENDED. Work is in progress 887 to define new key exchange mechanisms for use with SDP [26][27] and 888 it is expected that new applications will use those mechanisms. 890 A key field is permitted before the first media entry (in which case 891 it applies to all media in the session), or for each media entry as 892 required. The format of keys and their usage is outside the scope of 893 this document, and the key field provides no way to indicate the 894 encryption algorithm to be used, key type, or other information about 895 the key: this is assumed to be provided by the higher-level protocol 896 using SDP. If there is a need to convey this information within SDP, 897 the extensions mentioned previously SHOULD be used. Many security 898 protocols require two keys: one for confidentiality, another for 899 integrity. This specification does not support transfer of two keys. 901 The method indicates the mechanism to be used to obtain a usable key 902 by external means, or from the encoded encryption key given. The 903 following methods are defined: 905 k=clear: 907 The encryption key is included untransformed in this key field. 908 This method MUST NOT be used unless it can be guaranteed that 909 the SDP is conveyed over a secure channel. The encryption key 910 is interpreted as text according to the charset attribute, use 911 the "k=base64:" method to convey characters that are otherwise 912 prohibited in SDP. 914 k=base64: 916 The encryption key is included in this key field but has been 917 base64 encoded [12] because it includes characters that are 918 prohibited in SDP. This method MUST NOT be used unless it can 919 be guaranteed that the SDP is conveyed over a secure channel. 921 k=uri: 923 A Universal Resource Identifier is included in the key field. 924 The URI refers to the data containing the key, and may require 925 additional authentication before the key can be returned. When 926 a request is made to the given URI, the reply should specify 927 the encoding for the key. The URI is often a secure HTTP URI, 928 although this is not required. 930 k=prompt 932 No key is included in this SDP description, but the session or 933 media stream referred to by this key field is encrypted. The 934 user should be prompted for the key when attempting to join the 935 session, and this user-supplied key should then be used to 936 decrypt the media streams. The use of user-specified keys is 937 NOT RECOMMENDED, since such keys tend to have weak security 938 properties. 940 The key field MUST NOT be used unless it can be guaranteed that the 941 SDP is conveyed over a secure and trusted channel. An example of 942 such a channel might be SDP embedded inside an S/MIME message or a 943 TLS-protected HTTP session. It is important to ensure that the 944 secure channel is with the party that is authorised to join the 945 session, not an intermediary: if a caching proxy server is used, it 946 is important to ensure that the proxy is either trusted or unable to 947 access the SDP. Definition of appropriate security measures is 948 beyond the scope of this specification, and should be defined by the 949 users of SDP. 951 5.13 Attributes ("a=") 953 a= 954 a=: 956 Attributes are the primary means for extending SDP. Attributes may 957 be defined to be used as "session-level" attributes, "media-level" 958 attributes, or both. 960 A media description may have any number of attributes ("a=" fields) 961 which are media specific. These are referred to as "media-level" 962 attributes and add information about the media stream. Attribute 963 fields can also be added before the first media field; these 964 "session-level" attributes convey additional information that applies 965 to the conference as a whole rather than to individual media. 967 Attribute fields may be of two forms: 969 o A property attribute is simply of the form "a=". These are 970 binary attributes, and the presence of the attribute conveys that 971 the attribute is a property of the session. An example might be 972 "a=recvonly". 974 o A value attribute is of the form "a=:". For 975 example, a whiteboard could have the value attribute 976 "a=orient:landscape" 978 Attribute interpretation depends on the media tool being invoked. 979 Thus receivers of session descriptions should be configurable in 980 their interpretation of session descriptions in general and of 981 attributes in particular. 983 Attribute names MUST use the US-ASCII subset of ISO-10646/UTF-8. 985 Attribute values are octet strings, and MAY use any octet value 986 except 0x00 (Nul), 0x0A (LF), and 0x0D (CR). By default, attribute 987 values are to be interpreted as in ISO-10646 character set with UTF-8 988 encoding. Unlike other text fields, attribute values are NOT 989 normally affected by the "charset" attribute as this would make 990 comparisons against known values problematic. However, when an 991 attribute is defined, it can be defined to be charset-dependent, in 992 which case its value should be interpreted in the session charset 993 rather than in ISO-10646. 995 Attributes MUST be registered with IANA (see Section 8). If an 996 attribute is received that is not understood, it MUST be ignored by 997 the receiver. 999 5.14 Media Descriptions ("m=") 1001 m= ... 1003 A session description may contain a number of media descriptions. 1004 Each media description starts with an "m=" field, and is terminated 1005 by either the next "m=" field or by the end of the session 1006 description. A media field has several sub-fields: 1008 is the media type. Currently defined media are "audio", 1009 "video", "text", "application" and "message", although this list 1010 may be extended in future (see Section 8). 1012 is the transport port to which the media stream is sent. The 1013 meaning of the transport port depends on the network being used as 1014 specified in the relevant "c=" field, and on the transport 1015 protocol defined in the sub-field of the media field. 1016 Other ports used by the media application (such as the RTCP port 1017 [18]) MAY be derived algorithmically from the base media port or 1018 MAY be specified in a separate attribute (for example "a=rtcp:" as 1019 defined in [21]). 1021 For applications where hierarchically encoded streams are being 1022 sent to a unicast address, it may be necessary to specify multiple 1023 transport ports. This is done using a similar notation to that 1024 used for IP multicast addresses in the "c=" field: 1026 m= / ... 1028 In such a case, the ports used depend on the transport protocol. 1029 For RTP, the default is that only the even numbered ports are used 1030 for data with the corresponding one-higher odd ports used for the 1031 RTCP belonging to the RTP session, and the 1032 denoting the number of RTP sessions. For example: 1034 m=video 49170/2 RTP/AVP 31 1036 would specify that ports 49170 and 49171 form one RTP/RTCP pair 1037 and 49172 and 49173 form the second RTP/RTCP pair. RTP/AVP is the 1038 transport protocol and 31 is the format (see below). If 1039 non-contiguous ports are required, they must be signalled using a 1040 separate attribute (for example "a=rtcp:" as defined in [21]). 1042 If multiple addresses are specified in the "c=" field and multiple 1043 ports are specified in the "m=" field, a one-to-one mapping from 1044 port to the corresponding address is implied. For example: 1046 c=IN IP4 224.2.1.1/127/2 1047 m=video 49170/2 RTP/AVP 31 1049 would imply that address 224.2.1.1 is used with ports 49170 and 1050 49171, and address 224.2.1.2 is used with ports 49172 and 49173. 1052 The combination of ports specified in "m=" lines and IP addresses 1053 specified in "c=" lines MUST comply with the following rules for 1054 RTP-based media streams (other protocols SHOULD define similar 1055 rules): 1057 1. If two media sessions have the same transport address (i.e. 1058 identical IP address and port numbers), the associated payload 1059 types (e.g. given in the "a=rtpmap:" attribute) MUST NOT be 1060 in conflict, i.e. the same payload type MUST NOT be mapped to 1061 different media types. 1063 2. If two media sessions have the same transport address, they 1064 MUST use compatible media (e.g. both audio or both video). 1066 3. If two media sessions have the same transport address, they 1067 SHOULD operate under the same RTP profile. The sessions MAY 1068 use two different RTP profiles only if those profiles are 1069 specifically designed to be compatible. 1071 4. If two media sessions have the same RTP transport address, 1072 they MUST also use the same RTCP address and vice versa. 1074 Two media sessions with the same transport address indicate 1075 alternatives for the same media stream, i.e. all profiles, media 1076 types, and payload types provided in any of the "m=" lines are 1077 valid. 1079 is the transport protocol. The meaning of the transport 1080 protocol is dependent on the address type field in the relevant 1081 "c=" field. Thus a "c=" field of IP4 indicates that the transport 1082 protocol runs over IP4. The following transport protocols are 1083 defined, but may be extended through registration of new protocols 1084 with IANA (see Section 8): 1086 * udp: denotes an unspecified protocol running over UDP. 1088 * RTP/AVP: denotes RTP [18] used under the RTP Profile for Audio 1089 and Video Conferences with Minimal Control [19] running over 1090 UDP. 1092 * RTP/SAVP: denotes the Secure Real-time Transport Protocol [22] 1093 running over UDP. 1095 The main reason to specify the transport-protocol in addition to 1096 the media format is that the same standard media formats may be 1097 carried over different transport protocols even when the network 1098 protocol is the same - a historical example is vat PCM audio and 1099 RTP PCM audio, another might be TCP/RTP PCM audio. In addition, 1100 relays and monitoring tools that are transport-protocol-specific 1101 but format-independent are possible. 1103 is a media format description. The fourth and any subsequent 1104 sub-fields describe the format of the media. The interpretation 1105 of the media format depends on the value of the sub-field. 1107 If the sub-field is "RTP/AVP" or "RTP/SAVP" the 1108 sub-fields contain RTP payload type numbers. When a list of 1109 payload type numbers is given, this implies that all of these 1110 payload formats MAY be used in the session, but the first of these 1111 formats SHOULD be used as the default format for the session. For 1112 dynamic payload type assignments the "a=rtpmap:" attribute (see 1113 Section 6) SHOULD be used to map from an RTP payload type number 1114 to a media encoding name that identifies the payload format. The 1115 "a=fmtp:" attribute MAY be used to specify format parameters (see 1116 Section 6). 1118 If the sub-field is "udp" the sub-fields MUST 1119 reference a media type describing the format under the "audio", 1120 "video", "text", "application" or "message" top-level MIME types. 1121 The media type registration SHOULD define the packet format for 1122 use with UDP transport. 1124 For media using other transport protocols, the field is 1125 protocol specific. Rules for interpretation of the 1126 sub-field MUST be defined when registering new protocols (see 1127 section 8.2.2). 1129 6. SDP Attributes 1131 The following attributes are defined. Since application writers may 1132 add new attributes as they are required, this list is not exhaustive. 1134 Registration procedures for new attributes are defined in Section 1135 8.2.4. 1137 a=cat: 1139 This attribute gives the dot-separated hierarchical category 1140 of the session. This is to enable a receiver to filter 1141 unwanted sessions by category. It is a session-level 1142 attribute, and is not dependent on charset. 1144 a=keywds: 1146 Like the cat attribute, this is to assist identifying wanted 1147 sessions at the receiver. This allows a receiver to select 1148 interesting session based on keywords describing the purpose 1149 of the session. It is a session-level attribute. It is a 1150 charset dependent attribute, meaning that its value should be 1151 interpreted in the charset specified for the session 1152 description if one is specified, or by default in ISO 1153 10646/UTF-8. 1155 a=tool: 1157 This gives the name and version number of the tool used to 1158 create the session description. It is a session-level 1159 attribute, and is not dependent on charset. 1161 a=ptime: 1163 This gives the length of time in milliseconds represented by 1164 the media in a packet. This is probably only meaningful for 1165 audio data, but may be used with other media types if it makes 1166 sense. It should not be necessary to know ptime to decode RTP 1167 or vat audio, and it is intended as a recommendation for the 1168 encoding/packetisation of audio. It is a media attribute, and 1169 is not dependent on charset. 1171 a=maxptime: 1173 The maximum amount of media which can be encapsulated in each 1174 packet, expressed as time in milliseconds. The time SHALL be 1175 calculated as the sum of the time the media present in the 1176 packet represents. For frame based codecs, the time SHOULD 1177 be an integer multiple of the frame size. This attribute is 1178 probably only meaningful for audio data, but may be used with 1179 other media types if it makes sense. It is a media attribute, 1180 and is not dependent on charset. Note that this attribute was 1181 introduced after RFC 2327, and non updated implementations will 1182 ignore this attribute. 1184 a=rtpmap: / 1185 [/] 1187 This attribute maps from an RTP payload type number (as used in 1188 an "m=" line) to an encoding name denoting the payload format 1189 to be used. It also provides information on the clock rate and 1190 encoding parameters. It is a media level attribute that is not 1191 dependent on charset. 1193 While an RTP profile may make static assignments of payload 1194 type numbers to payload formats, it is more common for that 1195 assignment to be done dynamically using "a=rtpmap:" attributes. 1196 As an example of a static payload type, consider u-law PCM 1197 coded single channel audio sampled at 8kHz. This is completely 1198 defined in the RTP Audio/Video profile as payload type 0, so 1199 there is no need for an "a=rtpmap: attribute, and the media for 1200 such a stream sent to UDP port 49232 can be specified as: 1202 m=audio 49232 RTP/AVP 0 1204 An example of a dynamic payload type is 16 bit linear encoded 1205 stereo audio sampled at 16 kHz. If we wish to use the dynamic 1206 RTP/AVP payload type 98 for this stream, additional information 1207 is required to decode it: 1209 m=audio 49232 RTP/AVP 98 1210 a=rtpmap:98 L16/16000/2 1212 Up to one rtpmap attribute can be defined for each media format 1213 specified. Thus we might have: 1215 m=audio 49230 RTP/AVP 96 97 98 1216 a=rtpmap:96 L8/8000 1217 a=rtpmap:97 L16/8000 1218 a=rtpmap:98 L16/11025/2 1220 RTP profiles that specify the use of dynamic payload types MUST 1221 define the set of valid encoding names and/or a means to 1222 register encoding names if that profile is to be used with SDP. 1223 The "RTP/AVP" and "RTP/SAVP" profiles use MIME sub-types for 1224 encoding names, under the top-level media type denoted in the 1225 "m=" line. In the example above, the media types are "audio/l8" 1226 and "audio/l16". 1228 For audio streams, indicates the 1229 number of audio channels. This parameter is OPTIONAL and 1230 may be omitted if the number of channels is one, provided 1231 no additional parameters are needed. 1233 For video streams, no encoding parameters are currently 1234 specified. 1236 Additional encoding parameters MAY be defined in the future, 1237 but codec specific parameters SHOULD NOT be added. Parameters 1238 added to an "a=rtpmap:" attribute SHOULD only be those required 1239 for a session directory to make the choice of appropriate media 1240 to participate in a session. Codec-specific parameters should 1241 be added in other attributes (for example, "a=fmtp:"). 1243 Note: RTP audio formats typically do not include information 1244 about the number of samples per packet. If a non-default (as 1245 defined in the RTP Audio/Video Profile) packetisation is 1246 required, the "ptime" attribute is used as given below. 1248 a=recvonly 1250 This specifies that the tools should be started in receive 1251 only mode where applicable. It can be either a session or 1252 media attribute, and is not dependent on charset. Note that 1253 recvonly applies to the media only, not to any associated 1254 control protocol (e.g. an RTP based system in recvonly mode 1255 SHOULD still send RTCP packets). 1257 a=sendrecv 1259 This specifies that the tools should be started in send and 1260 receive mode. This is necessary for interactive conferences 1261 with tools that default to receive only mode. It can be either 1262 a session or media attribute, and is not dependent on charset. 1264 If none of the attributes "sendonly", "recvonly", "inactive", 1265 and "sendrecv" is present, "sendrecv" SHOULD be assumed as the 1266 default for sessions which are not of the conference type 1267 "broadcast" or "H332" (see below). 1269 a=sendonly 1271 This specifies that the tools should be started in send-only 1272 mode. An example may be where a different unicast address is 1273 to be used for a traffic destination than for a traffic 1274 source. In such a case, two media descriptions may be used, 1275 one sendonly and one recvonly. It can be either a session or 1276 media attribute, but would normally only be used as a media 1277 attribute. It is not dependent on charset. Note that sendonly 1278 applies only to the media, and any associated control protocol 1279 (e.g. RTCP) SHOULD still be received and processed as normal. 1281 a=inactive 1283 This specifies that the tools should be started in inactive 1284 mode. This is necessary for interactive conferences where 1285 users can put other users on hold. No media is sent over an 1286 inactive media stream. Note that an RTP based system SHOULD 1287 still send RTCP, even if started inactive. It can be either a 1288 session or media attribute, and is not dependent on charset. 1290 a=orient: 1292 Normally this is only used for a whiteboard or presentation 1293 tool. It specifies the orientation of a the workspace on 1294 the screen. It is a media attribute. Permitted values are 1295 "portrait", "landscape" and "seascape" (upside down landscape). 1296 It is not dependent on charset. 1298 a=type: 1300 This specifies the type of the conference. Suggested values 1301 are "broadcast", "meeting", "moderated", "test" and "H332". 1302 "recvonly" should be the default for "type:broadcast" 1303 sessions, "type:meeting" should imply "sendrecv" and 1304 "type:moderated" should indicate the use of a floor control 1305 tool and that the media tools are started so as to mute new 1306 sites joining the conference. 1308 Specifying the attribute "type:H332" indicates that this 1309 loosely coupled session is part of a H.332 session as defined 1310 in the ITU H.332 specification [15]. Media tools should be 1311 started "recvonly". 1313 Specifying the attribute "type:test" is suggested as a hint 1314 that, unless explicitly requested otherwise, receivers can 1315 safely avoid displaying this session description to users. 1317 The type attribute is a session-level attribute, and is not 1318 dependent on charset. 1320 a=charset: 1322 This specifies the character set to be used to display the 1323 session name and information data. By default, the ISO-10646 1324 character set in UTF-8 encoding is used. If a more compact 1325 representation is required, other character sets may be used. 1327 For example, the ISO 8859-1 is specified with the following 1328 SDP attribute: 1330 a=charset:ISO-8859-1 1332 This is a session-level attribute and is not dependent on 1333 charset. The charset specified MUST be one of those registered 1334 with IANA, such as ISO-8859-1. The character set identifier is 1335 a US-ASCII string and MUST be compared against the IANA 1336 identifiers using a case insensitive comparison. If the 1337 identifier is not recognised or not supported, all strings that 1338 are affected by it SHOULD be regarded as octet strings. 1340 Note that a character set specified MUST still prohibit the 1341 use of bytes 0x00 (Nul), 0x0A (LF) and 0x0d (CR). Character 1342 sets requiring the use of these characters MUST define a 1343 quoting mechanism that prevents these bytes appearing within 1344 text fields. 1346 a=sdplang: 1348 This can be a session level attribute or a media level 1349 attribute. As a session level attribute, it specifies the 1350 language for the session description. As a media level 1351 attribute, it specifies the language for any media-level SDP 1352 information field associated with that media. Multiple 1353 sdplang attributes can be provided either at session or media 1354 level if multiple languages in the session description or 1355 media use multiple languages, in which case the order of the 1356 attributes indicates the order of importance of the various 1357 languages in the session or media from most important to least 1358 important. 1360 In general, sending session descriptions consisting of 1361 multiple languages is discouraged. Instead, multiple 1362 descriptions SHOULD be sent describing the session, one in 1363 each language. However this is not possible with all 1364 transport mechanisms, and so multiple sdplang attributes are 1365 allowed although NOT RECOMMENDED. 1367 The "sdplang" attribute value must be a single RFC 3066 1368 language tag in US-ASCII [6]. It is not dependent on 1369 the charset attribute. An "sdplang" attribute SHOULD be 1370 specified when a session is of sufficient scope to cross 1371 geographic boundaries where the language of recipients cannot 1372 be assumed, or where the session is in a different language 1373 from the locally assumed norm. 1375 a=lang: 1377 This can be a session level attribute or a media level 1378 attribute. As a session level attribute, it specifies the 1379 default language for the session being described. As a media 1380 level attribute, it specifies the language for that media, 1381 overriding any session-level language specified. Multiple 1382 lang attributes can be provided either at session or media 1383 level if the session description or media use multiple 1384 languages, in which case the order of the attributes indicates 1385 the order of importance of the various languages in the 1386 session or media from most important to least important. 1388 The "lang" attribute value must be a single RFC 3066 language 1389 tag in US-ASCII [6]. It is not dependent on the charset 1390 attribute. A "lang" attribute SHOULD be specified when a 1391 session is of sufficient scope to cross geographic boundaries 1392 where the language of recipients cannot be assumed, or where 1393 the session is in a different language from the locally 1394 assumed norm. 1396 a=framerate: 1398 This gives the maximum video frame rate in frames/sec. It is 1399 intended as a recommendation for the encoding of video data. 1400 Decimal representations of fractional values using the 1401 notation "." are allowed. It is a 1402 media attribute, defined only for video media, and is not 1403 dependent on charset. 1405 a=quality: 1407 This gives a suggestion for the quality of the encoding as an 1408 integer value. The intention of the quality attribute for 1409 video is to specify a non-default trade-off between frame-rate 1410 and still-image quality. For video, the value in the range 0 1411 to 10, with the following suggested meaning: 1413 10 - the best still-image quality the compression scheme 1414 can give. 1415 5 - the default behaviour given no quality suggestion. 1416 0 - the worst still-image quality the codec designer 1417 thinks is still usable. 1419 It is a media attribute, and is not dependent on charset. 1421 a=fmtp: 1422 This attribute allows parameters that are specific to a 1423 particular format to be conveyed in a way that SDP doesn't 1424 have to understand them. The format must be one of the 1425 formats specified for the media. Format-specific parameters 1426 may be any set of parameters required to be conveyed by SDP 1427 and given unchanged to the media tool that will use this 1428 format. At most one instance of this attribute is allowed 1429 for each format. 1431 It is a media attribute, and is not dependent on charset. 1433 7. Security Considerations 1435 SDP is frequently used with the Session Initiation Protocol [15] 1436 using the offer/answer model [17] to agree parameters for unicast 1437 sessions. When used in this manner, the security considerations of 1438 those protocols apply. 1440 SDP is a session description format that describes multimedia 1441 sessions. A session description SHOULD NOT be trusted unless it has 1442 been obtained by an authenticated transport protocol from a trusted 1443 source. Many different transport protocols may be used to distribute 1444 session description, and the nature of the authentication will differ 1445 from transport to transport. 1447 One transport that will frequently be used to distribute session 1448 descriptions is the Session Announcement Protocol (SAP). SAP 1449 provides both encryption and authentication mechanisms but due to the 1450 nature of session announcements it is likely that there are many 1451 occasions where the originator of a session announcement cannot be 1452 authenticated because they are previously unknown to the receiver of 1453 the announcement and because no common public key infrastructure is 1454 available. 1456 On receiving a session description over an unauthenticated transport 1457 mechanism or from an untrusted party, software parsing the session 1458 should take a few precautions. Session descriptions contain 1459 information required to start software on the receivers system. 1460 Software that parses a session description MUST NOT be able to start 1461 other software except that which is specifically configured as 1462 appropriate software to participate in multimedia sessions. It is 1463 normally considered inappropriate for software parsing a session 1464 description to start, on a user's system, software that is 1465 appropriate to participate in multimedia sessions, without the user 1466 first being informed that such software will be started and giving 1467 their consent. Thus a session description arriving by session 1468 announcement, email, session invitation, or WWW page MUST NOT deliver 1469 the user into an interactive multimedia session unless the user has 1470 explicitly pre-authorized such action. As it is not always simple to 1471 tell whether a session is interactive or not, applications that are 1472 unsure should assume sessions are interactive. 1474 In this specification, there are no attributes which would allow the 1475 recipient of a session description to be informed to start multimedia 1476 tools in a mode where they default to transmitting. Under some 1477 circumstances it might be appropriate to define such attributes. If 1478 this is done an application parsing a session description containing 1479 such attributes SHOULD either ignore them, or inform the user that 1480 joining this session will result in the automatic transmission of 1481 multimedia data. The default behaviour for an unknown attribute is 1482 to ignore it. 1484 Session descriptions may be parsed at intermediate systems such as 1485 firewalls for the purposes of opening a hole in the firewall to allow 1486 participation in multimedia sessions. This SHOULD NOT be done unless 1487 the SDP is conveyed in a manner that allows proper authentication and 1488 authorization checks to ensure that firewall holes are only opened in 1489 accordance with applicable security policy. SDP by itself does not 1490 include sufficient information to enable these checks: they depend on 1491 the encapsulating protocol (e.g. SIP or RTSP). 1493 Use of the "k=" field poses a significant security risk, since it 1494 conveys session encryption keys in the clear. SDP MUST NOT be used 1495 to convey key material, unless it can be guaranteed that the channel 1496 over which the SDP is delivered is both private and authenticated. 1498 8. IANA Considerations 1500 8.1 The "application/sdp" media type 1502 One MIME type is to be registered, as defined below. This updates 1503 the previous definition from RFC 2327. 1505 To: ietf-types@iana.org 1506 Subject: Registration of media type "application/sdp" 1508 MIME media type name: application 1510 MIME subtype name: sdp 1512 Required parameters: None. 1514 Optional parameters: None. 1516 Encoding considerations: 1518 SDP files are primarily 7-bit ASCII text. The "a=charset:" 1519 attribute may be used to signal the presence of other, 1520 possibly 8-bit, text in certain parts of an SDP file (see 1521 section 6 of RFC XXXX). Arbitrary binary content cannot 1522 be directly represented in SDP. 1524 Security considerations: 1525 See section 7 of RFC XXXX 1527 Interoperability considerations: 1528 See RFC XXXX 1530 Published specification: 1531 See RFC XXXX 1533 Applications which use this media type: 1534 Voice over IP, video teleconferencing, streaming media, instant 1535 messaging, etc. See also section 3 of RFC XXXX. 1537 Additional information: 1539 Magic number(s): None. 1540 File extension(s): The extension ".sdp" is commonly used. 1541 Macintosh File Type Code(s): "sdp " 1543 Person & email address to contact for further information: 1544 Mark Handley 1545 Colin Perkins 1546 IETF MMUSIC working group 1548 Intended usage: COMMON 1550 Author/Change controller: 1551 Authors of RFC XXXX 1552 IETF MMUSIC working group delegated from the IESG 1554 8.2 Registration of Parameters 1556 There are seven field names that may be registered with IANA. Using 1557 the terminology in the SDP specification BNF, they are "media", 1558 "proto", "fmt", "att-field", "bwtype", "nettype" and "addrtype". 1560 8.2.1 Media types ("media") 1562 The set of media types is intended to be small and SHOULD NOT be 1563 extended except under rare circumstances. The same rules should 1564 apply for media names as for top-level MIME content types, and where 1565 possible the same name should be registered for SDP as for MIME. For 1566 media other than existing MIME top-level content types, a 1567 standards-track RFC MUST be produced for a new top-level content type 1568 to be registered, and the registration MUST provide good 1569 justification why no existing media name is appropriate (the 1570 "Standards Action" policy of RFC 2434 [8]. 1572 This memo registers the media types "audio", "video", "text", 1573 "application" and "message". 1575 Note: The media types "control" and "data" were listed as valid in 1576 the previous version of this specification [6], however their 1577 semantics were never fully specified and they are not widely used. 1578 These media types have been removed in this specification, although 1579 they still remain valid media type capabilities for a SIP user agent 1580 as defined in RFC 3840 [23]. If these media types are considered 1581 useful in future, a Standards Track RFC MUST be produced to document 1582 their use. Until that is done, applications SHOULD NOT use these 1583 types and SHOULD NOT declare support for them in SIP capabilities 1584 declarations (even though they exist in the registry created by RFC 1585 3840). 1587 8.2.2 Transport protocols ("proto") 1589 The "proto" field describes the transport protocol used. This SHOULD 1590 reference a standards-track protocol RFC. This memo registers three 1591 values: "RTP/AVP" is a reference to RTP [18] used under the RTP 1592 Profile for Audio and Video Conferences with Minimal Control [19] 1593 running over UDP/IP, "RTP/SAVP" is a reference to the Secure 1594 Real-time Transport Protocol [22], and "udp" indicates an unspecified 1595 protocol over UDP. 1597 If other RTP profiles are defined in the future, their "proto" name 1598 SHOULD be specified in the same manner. For example, an RTP profile 1599 whose short name is "XYZ" would be denoted by a "proto" field of 1600 "RTP/XYZ". 1602 New transport protocols SHOULD be registered with IANA. 1603 Registrations MUST reference an RFC describing the protocol. Such an 1604 RFC MAY be Experimental or Informational, although it is preferable 1605 if it is Standards-Track. Registrations MUST also define the rules 1606 by which their "fmt" namespace is managed (see below). 1608 8.2.3 Media formats ("fmt") 1610 Each transport protocol, defined by the "proto" field, has an 1611 associated "fmt" namespace that describes the media formats which may 1612 conveyed by that protocol. Formats cover all the possible encodings 1613 that might want to be transported in a multimedia session. 1615 RTP payload formats under the "RTP/AVP" and "RTP/SAVP" profiles MUST 1616 use the payload type number as their "fmt" value. If the payload 1617 type number is dynamically assigned by this session description, an 1618 additional "rtpmap" attribute MUST be included to specify the format 1619 name and parameters as defined by the MIME type registration for the 1620 payload format. It is RECOMMENDED that other RTP profiles which are 1621 registered (in combination with RTP) as SDP transport protocols 1622 specify the same rules for the "fmt" namespace. 1624 For the "udp" protocol, new formats SHOULD be registered. Use of an 1625 existing MIME subtype for the format is encouraged. If no MIME 1626 subtype exists, it is RECOMMENDED that a suitable one is registered 1627 through the IETF process (RFC 2048) by production of, or reference 1628 to, a standards-track RFC that defines the transport protocol for the 1629 format. 1631 For other protocols, formats MAY be registered according to the rules 1632 of the associated "proto" specification. 1634 Registrations of new formats MUST specify which transport protocols 1635 they apply to. 1637 8.2.4 Attribute names ("att-field") 1639 Attribute field names ("att-field") MUST be registered with IANA and 1640 documented, because of noticeable issues due to conflicting 1641 attributes under the same name. Unknown attributes in SDP are simply 1642 ignored, but conflicting ones that fragment the protocol are a 1643 serious problem. 1645 New attribute registrations are accepted according to the 1646 "Specification Required" policy of RFC 2434, provided that the 1647 specification includes the following information: 1649 o contact name, email address and telephone number 1651 o attribute-name (as it will appear in SDP) 1653 o long-form attribute name in English 1655 o type of attribute (session level, media level, or both) 1657 o whether the attribute value is subject to the charset attribute. 1659 o a one paragraph explanation of the purpose of the attribute. 1661 o a specification of appropriate attribute values for this 1662 attribute. 1664 The above is the minimum that IANA will accept. Attributes that are 1665 expected to see widespread use and interoperability, SHOULD be 1666 documented with a standards-track RFC that specifies the attribute 1667 more precisely. 1669 Submitters of registrations should ensure that the specification is 1670 in the spirit of SDP attributes, most notably that the attribute is 1671 platform independent in the sense that it makes no implicit 1672 assumptions about operating systems and does not name specific pieces 1673 of software in a manner that might inhibit interoperability. 1675 IANA is requested to register the following initial set of attribute 1676 names ("att-field" values), with definitions as in Section 6 of this 1677 memo (these definitions update those in RFC 2327): 1679 Name | Session or Media level? | Dependent on charset? 1680 ----------+-------------------------+---------------------- 1681 cat | Session | No 1682 keywds | Session | Yes 1683 tool | Session | No 1684 ptime | Media | No 1685 maxptime | Media | No 1686 rtpmap | Media | No 1687 recvonly | Either | No 1688 sendrecv | Either | No 1689 sendonly | Either | No 1690 inactive | Either | No 1691 orient | Media | No 1692 type | Session | No 1693 charset | Session | No 1694 sdplang | Either | No 1695 lang | Either | No 1696 framerate | Media | No 1697 quality | Media | No 1698 fmtp | Media | No 1700 8.2.5 Bandwidth specifiers ("bwtype") 1702 A proliferation of bandwidth specifiers is strongly discouraged. 1704 New bandwidth specifiers ("bwtype" fields) MUST be registered with 1705 IANA. The submission MUST reference a standards-track RFC specifying 1706 the semantics of the bandwidth specifier precisely, and indicating 1707 when it should be used, and why the existing registered bandwidth 1708 specifiers do not suffice. 1710 IANA is requested to register the bandwith specifiers "CT" and "AS" 1711 with definitions as in Section 5.8 of this memo (these definitions 1712 update those in RFC 2327). 1714 8.2.6 Network types ("nettype") 1716 New network types (the "nettype" field) may be registered with IANA 1717 if SDP needs to be used in the context of non-Internet environments. 1718 Whilst these are not normally the preserve of IANA, there may be 1719 circumstances when an Internet application needs to interoperate with 1720 a non- Internet application, such as when gatewaying an Internet 1721 telephony call into the PSTN. The number of network types should be 1722 small and should be rarely extended. A new network type cannot be 1723 registered without registering at least one address type to be used 1724 with that network type. A new network type registration MUST 1725 reference an RFC which gives details of the network type and address 1726 type and specifies how and when they would be used. 1728 IANA is requested to register the network type "IN" to represent the 1729 Internet, with definition as in Sections 5.2 and 5.7 of this memo 1730 (these definitions update those in RFC 2327). 1732 8.2.7 Address types ("addrtype") 1734 New address types ("addrtype") may be registered with IANA. An 1735 address type is only meaningful in the context of a network type, and 1736 any registration of an address type MUST specify a registered network 1737 type, or be submitted along with a network type registration. A new 1738 address type registration MUST reference an RFC giving details of the 1739 syntax of the address type. Address types are not expected to be 1740 registered frequently. 1742 IANA is requested to register the address types "IP4" and "IP6" with 1743 definitions as in Sections 5.2 and 5.7 of this memo (these 1744 definitions update those in RFC 2327). 1746 8.2.8 Registration Procedure 1748 In the RFC documentation that registers SDP "media", "proto", "fmt", 1749 "bwtype", "nettype" and "addrtype" fields, the authors MUST include 1750 the following information for IANA to place in the appropriate 1751 registry: 1753 o contact name, email address and telephone number 1755 o name being registered (as it will appear in SDP) 1756 o long-form name in English 1758 o type of name ("media", "proto", "fmt", "bwtype", "nettype", or 1759 "addrtype") 1761 o a one paragraph explanation of the purpose of the registered name. 1763 o a reference to the specification for the registered name (this 1764 will typically be an RFC number). 1766 IANA may refer any registration to the IESG Transport Area Directors 1767 for review, and may request revisions to be made before a 1768 registration will be made. 1770 8.3 Encryption Key Access Methods 1772 The IANA currently maintains a table of SDP encryption key access 1773 method ("enckey") names. This table is obsolete and SHOULD be 1774 removed, since the "k=" line is not extensible. New registrations 1775 MUST NOT be accepted. 1777 9. SDP Grammar 1779 This section provides an Augmented BNF grammar for SDP. ABNF is 1780 defined in [4]. 1782 ; SDP Syntax 1783 session-description = proto-version 1784 origin-field 1785 session-name-field 1786 information-field 1787 uri-field 1788 email-fields 1789 phone-fields 1790 connection-field 1791 bandwidth-fields 1792 time-fields 1793 key-field 1794 attribute-fields 1795 media-descriptions 1797 proto-version = "v=" 1*DIGIT CRLF 1798 ;this memo describes version 0 1800 origin-field = "o=" username SP sess-id SP sess-version SP 1801 nettype SP addrtype SP unicast-address CRLF 1803 session-name-field = "s=" text CRLF 1804 information-field = ["i=" text CRLF] 1806 uri-field = ["u=" uri CRLF] 1808 email-fields = *("e=" email-address CRLF) 1810 phone-fields = *("p=" phone-number CRLF) 1812 connection-field = ["c=" nettype SP addrtype SP 1813 connection-address CRLF] 1814 ;a connection field must be present 1815 ;in every media description or at the 1816 ;session-level 1818 bandwidth-fields = *("b=" bwtype ":" bandwidth CRLF) 1820 time-fields = 1*( "t=" start-time SP stop-time 1821 *(CRLF repeat-fields) CRLF) 1822 [zone-adjustments CRLF] 1824 repeat-fields = "r=" repeat-interval SP typed-time 1825 1*(SP typed-time) 1827 zone-adjustments = "z=" time SP ["-"] typed-time 1828 *(SP time SP ["-"] typed-time) 1830 key-field = ["k=" key-type CRLF] 1832 attribute-fields = *("a=" attribute CRLF) 1834 media-descriptions = *( media-field 1835 information-field 1836 *connection-field 1837 bandwidth-fields 1838 key-field 1839 attribute-fields ) 1841 media-field = "m=" media SP port ["/" integer] 1842 SP proto 1*(SP fmt) CRLF 1844 ; sub-rules of 'o=' 1845 username = non-ws-string 1846 ;pretty wide definition, but doesn't 1847 ;include space 1849 sess-id = 1*DIGIT 1850 ;should be unique for this username/host 1852 sess-version = 1*DIGIT 1854 nettype = token 1855 ;typically "IN" 1857 addrtype = token 1858 ;typically "IP4" or "IP6" 1860 ; sub-rules of 'u=' 1861 uri = URI-reference 1862 ; see RFC2396 and RFC2732 1864 ; sub-rules of 'e=' 1865 email-address = email *SP "(" 1*email-safe ")" / 1866 1*email-safe "<" email ">" / 1867 email 1869 email = addr-spec ; defined in RFC2822 1870 ; modified to remove CFWS 1872 ; sub-rules of 'p=' 1873 phone-number = phone *SP "(" 1*email-safe ")" / 1874 1*email-safe "<" phone ">" / 1875 phone 1877 phone = ["+"] DIGIT 1*(SP / "-" / DIGIT) 1879 ; sub-rules of 'c=' 1880 connection-address = multicast-address / unicast-address 1882 ; sub-rules of 'b=' 1883 bwtype = token 1885 bandwidth = 1*DIGIT 1887 ; sub-rules of 't=' 1888 start-time = time / "0" 1890 stop-time = time / "0" 1892 time = POS-DIGIT 9*DIGIT 1893 ; Decimal representation of NTP time in 1894 ; seconds since 1900. The representation 1895 ; of NTP time is an unbounded length field 1896 ; containing at least 10 digits. Unlike the 1897 ; 64-bit representation used elsewhere, time 1898 ; in SDP does not wrap in the year 2036. 1900 ; sub-rules of 'r=' and 'z=' 1901 repeat-interval = POS-DIGIT *DIGIT [fixed-len-time-unit] 1903 typed-time = 1*DIGIT [fixed-len-time-unit] 1905 fixed-len-time-unit = "d" / "h" / "m" / "s" 1907 ; sub-rules of 'k=' 1908 key-type = "prompt" / 1909 "clear:" text / 1910 "base64:" base64 / 1911 "uri:" uri 1913 base64 = *base64-unit [base64-pad] 1914 base64-unit = 4base64-char 1915 base64-pad = 2base64-char "==" / 3base64-char "=" 1916 base64-char = ALPHA / DIGIT / "+" / "/" 1918 ; sub-rules of 'a=' 1919 attribute = (att-field ":" att-value) / att-field 1921 att-field = token 1923 att-value = byte-string 1925 ; sub-rules of 'm=' 1926 media = token 1927 ;typically "audio", "video", "text" or 1928 ;"application" 1930 fmt = token 1931 ;typically an RTP payload type for audio 1932 ;and video media 1934 proto = token *("/" token) 1935 ;typically "RTP/AVP" or "udp" 1937 port = 1*DIGIT 1939 ; generic sub-rules: addressing 1940 unicast-address = IP4-address / IP6-address / FQDN / extn-addr 1942 multicast-address = IP4-multicast / IP6-multicast / FQDN 1943 / extn-addr 1945 IP4-multicast = m1 3( "." decimal-uchar ) 1946 "/" ttl [ "/" integer ] 1947 ; IPv4 multicast addresses may be in the 1948 ; range 224.0.0.0 to 239.255.255.255 1950 m1 = ("22" ("4"/"5"/"6"/"7"/"8"/"9")) / 1951 ("23" DIGIT ) 1953 IP6-multicast = hexpart [ "/" integer ] 1954 ; IPv6 address starting with FF 1956 ttl = (POS-DIGIT *2DIGIT) / "0" 1958 FQDN = 4*(alpha-numeric / "-" / ".") 1959 ; fully qualified domain name as specified 1960 ; in RFC1035 (and updates) 1962 IP4-address = b1 3("." decimal-uchar) 1964 b1 = decimal-uchar 1965 ; less than "224" 1967 ; The following is from RFC2373 Appendix B. It is a direct copy. 1968 IP6-address = hexpart [ ":" IP4-address ] 1970 hexpart = hexseq / hexseq "::" [ hexseq ] / 1971 "::" [ hexseq ] 1973 hexseq = hex4 *( ":" hex4) 1975 hex4 = 1*4HEXDIG 1977 ; Generic for other address families 1978 extn-addr = non-ws-string 1980 ; generic sub-rules: datatypes 1981 text = byte-string 1982 ;default is to interpret this as UTF8 text. 1983 ;ISO 8859-1 requires "a=charset:ISO-8859-1" 1984 ;session-level attribute to be used 1986 byte-string = 1*(%x01-09/%x0B-0C/%x0E-FF) 1987 ;any byte except NUL, CR or LF 1989 non-ws-string = 1*(VCHAR/%x80-FF) 1990 ;string of visible characters 1992 token-char = %x21 / %x23-27 / %x2A-2B / %x2D-2E / %x30-39 1993 / %x41-5A / %x5E-7E 1995 token = 1*(token-char) 1996 email-safe = %x01-09/%x0B-0C/%x0E-27/%x2A-3B/%x3D/%x3F-FF 1997 ;any byte except NUL, CR, LF, or the quoting 1998 ;characters ()<> 2000 integer = POS-DIGIT *DIGIT 2002 ; generic sub-rules: primitives 2003 alpha-numeric = ALPHA / DIGIT 2005 POS-DIGIT = %x31-39 ; 1 - 9 2007 decimal-uchar = DIGIT 2008 / POS-DIGIT DIGIT 2009 / ("1" 2*(DIGIT)) 2010 / ("2" ("0"/"1"/"2"/"3"/"4") DIGIT) 2011 / ("2" "5" ("0"/"1"/"2"/"3"/"4"/"5")) 2013 ; external references: 2014 ; ALPHA, DIGIT, CRLF, SP, VCHAR: from RFC 2234 2015 ; URI-reference: from RFC2396 and RFC2732 2016 ; addr-spec: from RFC 2822 2018 10. Summary of Changes from RFC 2327 2020 The memo has been significantly restructured, incorporating a large 2021 number of clarifications to the specification in light of use. With 2022 the exception of those items noted below, the changes to the memo are 2023 intended to be backwards compatible clarifications. However, due to 2024 inconsistencies and unclear definitions in RFC 2327 it is likely that 2025 some implementations interpreted that memo in ways that differ from 2026 this version of SDP. 2028 The ABNF grammar in Section 9 has been extensively revised and 2029 updated, correcting a number of mistakes and incorporating the RFC 2030 3266 IPv6 extensions. Known inconsistencies between the grammar and 2031 the specification text have been resolved. 2033 A media type registration for SDP is included. Requirements for the 2034 registration of attributes and other parameters with IANA have been 2035 clarified and tightened (Section 8). It is noted that "text" and 2036 "message" are valid media types for use with SDP, but that "control" 2037 and "data" are under-specified and deprecated. 2039 RFC 2119 terms are now used throughout to specify requirements 2040 levels. Certain of those requirements, in particular in relation to 2041 parameter registration, are stricter than those in RFC 2327. 2043 The "RTP/SAVP" RTP profile and its "fmt" namespace are registered. 2045 The attributes "a=inactive" and "a=maxptime" have been added. 2047 RFC 2327 mandated that either "e=" or "p=" was required. Both are 2048 now optional, to reflect actual usage. 2050 The significant limitations of the "k=" field are noted, and its use 2051 is deprecated. 2053 Most uses of the "x-" prefix notation for experimental parameters are 2054 disallowed and the other uses are deprecated. 2056 11. Acknowledgements 2058 Many people in the IETF Multiparty Multimedia Session Control 2059 (MMUSIC) working group have made comments and suggestions 2060 contributing to this document. In particular, we would like to thank 2061 Eve Schooler, Steve Casner, Bill Fenner, Allison Mankin, Ross 2062 Finlayson, Peter Parnes, Joerg Ott, Carsten Bormann, Steve Hanna, 2063 Jonathan Lennox, Keith Drage, Sean Olson, Bernie Hoeneisen and 2064 Jonathan Rosenberg. 2066 12. References 2068 12.1 Normative References 2070 [1] Mockapetris, P., "Domain names - concepts and facilities", STD 2071 13, RFC 1034, November 1987. 2073 [2] Mockapetris, P., "Domain names - implementation and 2074 specification", STD 13, RFC 1035, November 1987. 2076 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2077 Levels", BCP 14, RFC 2119, March 1997. 2079 [4] Crocker, D. and P. Overell, "Augmented BNF for Syntax 2080 Specifications: ABNF", RFC 2234, November 1997. 2082 [5] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2083 2279, January 1998. 2085 [6] Handley, M. and V. Jacobson, "SDP: Session Description 2086 Protocol", RFC 2327, April 1998. 2088 [7] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 2089 Resource Identifiers (URI): Generic Syntax", RFC 2396, August 2090 1998. 2092 [8] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA 2093 Considerations Section in RFCs", BCP 26, RFC 2434, October 2094 1998. 2096 [9] Hinden, R., Carpenter, B. and L. Masinter, "Format for Literal 2097 IPv6 Addresses in URL's", RFC 2732, December 1999. 2099 [10] Alvestrand, H., "Tags for the Identification of Languages", BCP 2100 47, RFC 3066, January 2001. 2102 [11] Faltstrom, P., Hoffman, P. and A. Costello, "Internationalizing 2103 Domain Names in Applications (IDNA)", RFC 3490, March 2003. 2105 [12] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", 2106 RFC 3548, July 2003. 2108 12.2 Informative References 2110 [13] Mills, D., "Network Time Protocol (Version 3) Specification, 2111 Implementation", RFC 1305, March 1992. 2113 [14] Handley, M., Perkins, C. and E. Whelan, "Session Announcement 2114 Protocol", RFC 2974, October 2000. 2116 [15] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., 2117 Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: 2118 Session Initiation Protocol", RFC 3261, June 2002. 2120 [16] Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming 2121 Protocol (RTSP)", RFC 2326, April 1998. 2123 [17] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with 2124 Session Description Protocol (SDP)", RFC 3264, June 2002. 2126 [18] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, 2127 "RTP: A Transport Protocol for Real-Time Applications", STD 64, 2128 RFC 3550, July 2003. 2130 [19] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video 2131 Conferences with Minimal Control", STD 65, RFC 3551, July 2003. 2133 [20] Casner, S., "Session Description Protocol (SDP) Bandwidth 2134 Modifiers for RTP Control Protocol (RTCP) Bandwidth", RFC 3556, 2135 July 2003. 2137 [21] Huitema, C., "Real Time Control Protocol (RTCP) attribute in 2138 Session Description Protocol (SDP)", RFC 3605, October 2003. 2140 [22] Baugher, M., McGrew, D., Naslund, M., Carrara, E. and K. 2141 Norrman, "The Secure Real-time Transport Protocol (SRTP)", RFC 2142 3711, March 2004. 2144 [23] Rosenberg, J., Schulzrinne, H. and P. Kyzivat, "Indicating User 2145 Agent Capabilities in the Session Initiation Protocol (SIP)", 2146 RFC 3840, August 2004. 2148 [24] Westerlund, M., "A Transport Independent Bandwidth Modifier for 2149 the Session Description Protocol (SDP)", RFC 3890, September 2150 2004. 2152 [25] International Telecommunications Union, "H.323 extended for 2153 loosely coupled conferences", ITU Recommendation H.332, 2154 September 1998. 2156 [26] Arkko, J., Carrara, E., Lindholm, F., Naslund, M. and K. 2157 Norrman, "Key Management Extensions for Session Description 2158 Protocol (SDP) and Real Time Streaming Protocol (RTSP)", 2159 draft-ietf-mmusic-kmgmt-ext-12 (work in progress), November 2160 2004. 2162 [27] Andreasen, F., Baugher, M. and D. Wing, "Session Description 2163 Protocol Security Descriptions for Media Streams", 2164 draft-ietf-mmusic-sdescriptions-07 (work in progress), July 2165 2004. 2167 Authors' Addresses 2169 Mark Handley 2170 University College London 2171 Department of Computer Science 2172 Gower Street 2173 London WC1E 6BT 2174 UK 2176 EMail: M.Handley@cs.ucl.ac.uk 2178 Van Jacobson 2179 Packet Design 2180 2465 Latham Street 2181 Mountain View, CA 94040 2182 USA 2184 EMail: van@packetdesign.com 2185 Colin Perkins 2186 University of Glasgow 2187 Department of Computing Science 2188 17 Lilybank Gardens 2189 Glasgow G12 8QQ 2190 UK 2192 EMail: csp@csperkins.org 2194 Intellectual Property Statement 2196 The IETF takes no position regarding the validity or scope of any 2197 Intellectual Property Rights or other rights that might be claimed to 2198 pertain to the implementation or use of the technology described in 2199 this document or the extent to which any license under such rights 2200 might or might not be available; nor does it represent that it has 2201 made any independent effort to identify any such rights. Information 2202 on the procedures with respect to rights in RFC documents can be 2203 found in BCP 78 and BCP 79. 2205 Copies of IPR disclosures made to the IETF Secretariat and any 2206 assurances of licenses to be made available, or the result of an 2207 attempt made to obtain a general license or permission for the use of 2208 such proprietary rights by implementers or users of this 2209 specification can be obtained from the IETF on-line IPR repository at 2210 http://www.ietf.org/ipr. 2212 The IETF invites any interested party to bring to its attention any 2213 copyrights, patents or patent applications, or other proprietary 2214 rights that may cover technology that may be required to implement 2215 this standard. Please address the information to the IETF at 2216 ietf-ipr@ietf.org. 2218 Disclaimer of Validity 2220 This document and the information contained herein are provided on an 2221 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2222 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2223 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2224 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2225 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2226 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2228 Copyright Statement 2230 Copyright (C) The Internet Society (2004). This document is subject 2231 to the rights, licenses and restrictions contained in BCP 78, and 2232 except as set forth therein, the authors retain all their rights. 2234 Acknowledgment 2236 Funding for the RFC Editor function is currently provided by the 2237 Internet Society.