draft-ietf-mmusic-sdp-new-22.txt   draft-ietf-mmusic-sdp-new-23.txt 
Network Working Group M. Handley Network Working Group M. Handley
Internet-Draft UCL Internet-Draft UCL
Obsoletes: 2327, 3266 (if V. Jacobson Obsoletes: 2327, 3266 (if V. Jacobson
approved) Packet Design approved) Packet Design
Expires: May 28, 2005 C. Perkins Expires: June 10, 2005 C. Perkins
University of Glasgow University of Glasgow
November 27, 2004 December 10, 2004
SDP: Session Description Protocol SDP: Session Description Protocol
draft-ietf-mmusic-sdp-new-22.txt draft-ietf-mmusic-sdp-new-23.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of 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 is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 38 skipping to change at page 1, line 39
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 28, 2005. This Internet-Draft will expire on June 10, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2004).
Abstract Abstract
This memo defines the Session Description Protocol (SDP). SDP is This memo defines the Session Description Protocol (SDP). SDP is
intended for describing multimedia sessions for the purposes of intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of session announcement, session invitation, and other forms of
skipping to change at page 2, line 28 skipping to change at page 2, line 28
4.4 Obtaining Further Information about a Session . . . . . . 7 4.4 Obtaining Further Information about a Session . . . . . . 7
4.5 Categorisation . . . . . . . . . . . . . . . . . . . . . . 7 4.5 Categorisation . . . . . . . . . . . . . . . . . . . . . . 7
4.6 Internationalisation . . . . . . . . . . . . . . . . . . . 7 4.6 Internationalisation . . . . . . . . . . . . . . . . . . . 7
5. SDP Specification . . . . . . . . . . . . . . . . . . . . . 7 5. SDP Specification . . . . . . . . . . . . . . . . . . . . . 7
5.1 Protocol Version ("v=") . . . . . . . . . . . . . . . . . 10 5.1 Protocol Version ("v=") . . . . . . . . . . . . . . . . . 10
5.2 Origin ("o=") . . . . . . . . . . . . . . . . . . . . . . 11 5.2 Origin ("o=") . . . . . . . . . . . . . . . . . . . . . . 11
5.3 Session Name ("s=") . . . . . . . . . . . . . . . . . . . 12 5.3 Session Name ("s=") . . . . . . . . . . . . . . . . . . . 12
5.4 Session Information ("i=") . . . . . . . . . . . . . . . . 12 5.4 Session Information ("i=") . . . . . . . . . . . . . . . . 12
5.5 URI ("u=") . . . . . . . . . . . . . . . . . . . . . . . . 12 5.5 URI ("u=") . . . . . . . . . . . . . . . . . . . . . . . . 12
5.6 Email Address and Phone Number ("e=" and "p=") . . . . . . 13 5.6 Email Address and Phone Number ("e=" and "p=") . . . . . . 13
5.7 Connection Data ("c=") . . . . . . . . . . . . . . . . . . 13 5.7 Connection Data ("c=") . . . . . . . . . . . . . . . . . . 14
5.8 Bandwidth ("b=") . . . . . . . . . . . . . . . . . . . . . 16 5.8 Bandwidth ("b=") . . . . . . . . . . . . . . . . . . . . . 16
5.9 Timing ("t=") . . . . . . . . . . . . . . . . . . . . . . 17 5.9 Timing ("t=") . . . . . . . . . . . . . . . . . . . . . . 17
5.10 Repeat Times ("r=") . . . . . . . . . . . . . . . . . . 18 5.10 Repeat Times ("r=") . . . . . . . . . . . . . . . . . . 18
5.11 Time Zones ("z=") . . . . . . . . . . . . . . . . . . . 18 5.11 Time Zones ("z=") . . . . . . . . . . . . . . . . . . . 18
5.12 Encryption Keys ("k=") . . . . . . . . . . . . . . . . . 19 5.12 Encryption Keys ("k=") . . . . . . . . . . . . . . . . . 19
5.13 Attributes ("a=") . . . . . . . . . . . . . . . . . . . 21 5.13 Attributes ("a=") . . . . . . . . . . . . . . . . . . . 21
5.14 Media Descriptions ("m=") . . . . . . . . . . . . . . . 22 5.14 Media Descriptions ("m=") . . . . . . . . . . . . . . . 22
6. SDP Attributes . . . . . . . . . . . . . . . . . . . . . . . 24 6. SDP Attributes . . . . . . . . . . . . . . . . . . . . . . . 24
7. Security Considerations . . . . . . . . . . . . . . . . . . 31 7. Security Considerations . . . . . . . . . . . . . . . . . . 31
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 32 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 32
8.1 The "application/sdp" media type . . . . . . . . . . . . . 32 8.1 The "application/sdp" media type . . . . . . . . . . . . . 32
8.2 Registration of Parameters . . . . . . . . . . . . . . . . 33 8.2 Registration of Parameters . . . . . . . . . . . . . . . . 33
8.3 Encryption Key Access Methods . . . . . . . . . . . . . . 38 8.3 Encryption Key Access Methods . . . . . . . . . . . . . . 38
9. SDP Grammar . . . . . . . . . . . . . . . . . . . . . . . . 38 9. SDP Grammar . . . . . . . . . . . . . . . . . . . . . . . . 38
10. Summary of Changes from RFC 2327 . . . . . . . . . . . . . . 43 10. Summary of Changes from RFC 2327 . . . . . . . . . . . . . . 43
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 44 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 44
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 44 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 44
12.1 Normative References . . . . . . . . . . . . . . . . . . . 44 12.1 Normative References . . . . . . . . . . . . . . . . . . . 44
12.2 Informative References . . . . . . . . . . . . . . . . . . 45 12.2 Informative References . . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 46 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 46
Intellectual Property and Copyright Statements . . . . . . . 47 Intellectual Property and Copyright Statements . . . . . . . 48
1. Introduction 1. Introduction
When initiating multimedia teleconferences, voice-over-IP calls, When initiating multimedia teleconferences, voice-over-IP calls,
streaming video, or other sessions, there is a requirement to convey streaming video, or other sessions, there is a requirement to convey
media details, transport addresses, and other session description media details, transport addresses, and other session description
metadata to the participants. metadata to the participants.
SDP provides a standard representation for such information, SDP provides a standard representation for such information,
irrespective of how that information is transported. SDP is purely a irrespective of how that information is transported. SDP is purely a
skipping to change at page 12, line 7 skipping to change at page 12, line 7
that SHOULD be given unless this is unavailable, in which case the that SHOULD be given unless this is unavailable, in which case the
globally unique address MAY be substituted. A local IP address globally unique address MAY be substituted. A local IP address
MUST NOT be used in any context where the SDP description might MUST NOT be used in any context where the SDP description might
leave the scope in which the address is meaningful. leave the scope in which the address is meaningful.
In general, the "o=" field serves as a globally unique identifier for In general, the "o=" field serves as a globally unique identifier for
this version of this session description, and the subfields excepting this version of this session description, and the subfields excepting
the version taken together identify the session irrespective of any the version taken together identify the session irrespective of any
modifications. modifications.
For privacy reasons, it is sometimes desirable to obfuscate the
username and IP address of the session originator. If this is a
concern, an arbitrary <username> and private <unicast-address> MAY be
chosen to populate the "o=" field, provided these are selected in a
manner that does not affect the global uniqueness of the field.
5.3 Session Name ("s=") 5.3 Session Name ("s=")
s=<session name> s=<session name>
The "s=" field is the textual session name. There MUST be one and The "s=" field is the textual session name. There MUST be one and
only one "s=" field per session description. The "s=" field MUST NOT only one "s=" field per session description. The "s=" field MUST NOT
be empty and SHOULD contain ISO 10646 characters (but see also the be empty and SHOULD contain ISO 10646 characters (but see also the
"a=charset" attribute). If a session has no meaningful name, the "a=charset" attribute). If a session has no meaningful name, the
value "s= " SHOULD be used (i.e. a single space as the session value "s= " SHOULD be used (i.e. a single space as the session
name). name).
skipping to change at page 32, line 46 skipping to change at page 33, line 4
MIME media type name: application MIME media type name: application
MIME subtype name: sdp MIME subtype name: sdp
Required parameters: None. Required parameters: None.
Optional parameters: None. Optional parameters: None.
Encoding considerations: Encoding considerations:
See section 5 of RFC XXXX
SDP files are primarily 7-bit ASCII text. The "a=charset:"
attribute may be used to signal the presence of other,
possibly 8-bit, text in certain parts of an SDP file (see
section 6 of RFC XXXX). Arbitrary binary content cannot
be directly represented in SDP.
Security considerations: Security considerations:
See section 8 of RFC XXXX See section 7 of RFC XXXX
Interoperability considerations: Interoperability considerations:
See RFC XXXX See RFC XXXX
Published specification: Published specification:
See RFC XXXX See RFC XXXX
Applications which use this media type: Applications which use this media type:
Voice over IP, video teleconferencing, streaming media, instant Voice over IP, video teleconferencing, streaming media, instant
messaging, etc. See also section 3 of RFC XXXX. messaging, etc. See also section 3 of RFC XXXX.
Additional information: Additional information:
skipping to change at page 33, line 21 skipping to change at page 33, line 31
Voice over IP, video teleconferencing, streaming media, instant Voice over IP, video teleconferencing, streaming media, instant
messaging, etc. See also section 3 of RFC XXXX. messaging, etc. See also section 3 of RFC XXXX.
Additional information: Additional information:
Magic number(s): None. Magic number(s): None.
File extension(s): The extension ".sdp" is commonly used. File extension(s): The extension ".sdp" is commonly used.
Macintosh File Type Code(s): "sdp " Macintosh File Type Code(s): "sdp "
Person & email address to contact for further information: Person & email address to contact for further information:
Mark Handley <M.Handley@cs.ucl.ac.uk>
Colin Perkins <csp@csperkins.org> Colin Perkins <csp@csperkins.org>
IETF MMUSIC working group IETF MMUSIC working group <mmusic@ietf.org>
Intended usage: COMMON Intended usage: COMMON
Author/Change controller: Author/Change controller:
Authors of RFC XXXX Authors of RFC XXXX
IETF MMUSIC working group delegated from the IESG IETF MMUSIC working group delegated from the IESG
8.2 Registration of Parameters 8.2 Registration of Parameters
There are seven field names that may be registered with IANA. Using There are seven field names that may be registered with IANA. Using
skipping to change at page 44, line 15 skipping to change at page 44, line 25
Most uses of the "x-" prefix notation for experimental parameters are Most uses of the "x-" prefix notation for experimental parameters are
disallowed and the other uses are deprecated. disallowed and the other uses are deprecated.
11. Acknowledgements 11. Acknowledgements
Many people in the IETF Multiparty Multimedia Session Control Many people in the IETF Multiparty Multimedia Session Control
(MMUSIC) working group have made comments and suggestions (MMUSIC) working group have made comments and suggestions
contributing to this document. In particular, we would like to thank contributing to this document. In particular, we would like to thank
Eve Schooler, Steve Casner, Bill Fenner, Allison Mankin, Ross Eve Schooler, Steve Casner, Bill Fenner, Allison Mankin, Ross
Finlayson, Peter Parnes, Joerg Ott, Carsten Bormann, Steve Hanna, Finlayson, Peter Parnes, Joerg Ott, Carsten Bormann, Steve Hanna,
Jonathan Lennox, Keith Drage, Sean Olson, Bernie Hoenelsen and Jonathan Lennox, Keith Drage, Sean Olson, Bernie Hoeneisen and
Jonathan Rosenberg. Jonathan Rosenberg.
12. References 12. References
12.1 Normative References 12.1 Normative References
[1] Mockapetris, P., "Domain names - concepts and facilities", STD [1] Mockapetris, P., "Domain names - concepts and facilities", STD
13, RFC 1034, November 1987. 13, RFC 1034, November 1987.
[2] Mockapetris, P., "Domain names - implementation and [2] Mockapetris, P., "Domain names - implementation and
 End of changes. 14 change blocks. 
11 lines changed or deleted 23 lines changed or added

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