draft-ietf-mmusic-rfc4566bis-04.txt   draft-ietf-mmusic-rfc4566bis-05.txt 
Network Working Group M. Handley Network Working Group M. Handley
Internet-Draft UCL Internet-Draft UCL
Obsoletes: 4566 (if approved) V. Jacobson Obsoletes: 4566 (if approved) V. Jacobson
Intended status: Standards Track Packet Design Intended status: Standards Track PARC
Expires: April 26, 2012 C. Perkins Expires: August 30, 2012 C. Perkins
University of Glasgow University of Glasgow
A. Begen A. Begen
Cisco Cisco
October 24, 2011 February 27, 2012
SDP: Session Description Protocol SDP: Session Description Protocol
draft-ietf-mmusic-rfc4566bis-04 draft-ietf-mmusic-rfc4566bis-05
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
multimedia session initiation. multimedia session initiation. This document obsoletes RFC 4566.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 26, 2012. This Internet-Draft will expire on August 30, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 23 skipping to change at page 3, line 23
8.2.5. Bandwidth Specifiers ("bwtype") . . . . . . . . . . . 38 8.2.5. Bandwidth Specifiers ("bwtype") . . . . . . . . . . . 38
8.2.6. Network Types ("nettype") . . . . . . . . . . . . . . 38 8.2.6. Network Types ("nettype") . . . . . . . . . . . . . . 38
8.2.7. Address Types ("addrtype") . . . . . . . . . . . . . . 38 8.2.7. Address Types ("addrtype") . . . . . . . . . . . . . . 38
8.2.8. Registration Procedure . . . . . . . . . . . . . . . . 39 8.2.8. Registration Procedure . . . . . . . . . . . . . . . . 39
8.3. Encryption Key Access Methods . . . . . . . . . . . . . . 39 8.3. Encryption Key Access Methods . . . . . . . . . . . . . . 39
9. SDP Grammar . . . . . . . . . . . . . . . . . . . . . . . . . 39 9. SDP Grammar . . . . . . . . . . . . . . . . . . . . . . . . . 39
10. Summary of Changes from RFC 4566 . . . . . . . . . . . . . . . 44 10. Summary of Changes from RFC 4566 . . . . . . . . . . . . . . . 44
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 45 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 45
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.1. Normative References . . . . . . . . . . . . . . . . . . . 46 12.1. Normative References . . . . . . . . . . . . . . . . . . . 46
12.2. Informative References . . . . . . . . . . . . . . . . . . 46 12.2. Informative References . . . . . . . . . . . . . . . . . . 47
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 41 skipping to change at page 12, line 41
<unicast-address> is an address of the machine from which the <unicast-address> is an address of the machine from which the
session was created. For an address type of IP4, this is either a session was created. For an address type of IP4, this is either a
fully qualified domain name of the machine or the dotted-decimal fully qualified domain name of the machine or the dotted-decimal
representation of an IP version 4 address of the machine. For an representation of an IP version 4 address of the machine. For an
address type of IP6, this is either a fully qualified domain name address type of IP6, this is either a fully qualified domain name
of the machine or the compressed textual representation of an IP of the machine or the compressed textual representation of an IP
version 6 address of the machine. For both IP4 and IP6, the fully version 6 address of the machine. For both IP4 and IP6, the fully
qualified domain name is the form that SHOULD be given unless this qualified domain name is the form that SHOULD be given unless this
is unavailable, in which case a globally unique address MAY be is unavailable, in which case a globally unique address MAY be
substituted. A local IP address MUST NOT be used in any context substituted. Unless an SDP extension for NAT traversal is used
where the SDP description might leave the scope in which the (e.g., ICE [RFC5245], ICE TCP [I-D.ietf-mmusic-ice-tcp]), a local
address is meaningful (for example, a local address MUST NOT be IP address MUST NOT be used in any context where the SDP
included in an application-level referral that might leave the description might leave the scope in which the address is
scope). meaningful (for example, a local address MUST NOT be included in
an application-level referral that might leave the scope).
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 For privacy reasons, it is sometimes desirable to obfuscate the
username and IP address of the session originator. If this is a username and IP address of the session originator. If this is a
concern, an arbitrary <username> and private <unicast-address> MAY be concern, an arbitrary <username> and private <unicast-address> MAY be
chosen to populate the "o=" field, provided that these are selected chosen to populate the "o=" field, provided that these are selected
skipping to change at page 35, line 16 skipping to change at page 35, line 16
There are seven field names that may be registered with IANA. Using There are seven field names that may be registered with IANA. Using
the terminology in the SDP specification Backus-Naur Form (BNF), they the terminology in the SDP specification Backus-Naur Form (BNF), they
are "media", "proto", "fmt", "att-field", "bwtype", "nettype", and are "media", "proto", "fmt", "att-field", "bwtype", "nettype", and
"addrtype". "addrtype".
8.2.1. Media Types ("media") 8.2.1. Media Types ("media")
The set of media types is intended to be small and SHOULD NOT be The set of media types is intended to be small and SHOULD NOT be
extended except under rare circumstances. The same rules should extended except under rare circumstances. The same rules should
apply for media names as for top-level media content types, and where apply for media names as for top-level media types, and where
possible the same name should be registered for SDP as for MIME. For possible the same name should be registered for SDP as for MIME. For
media other than existing top-level media content types, a Standards media other than existing top-level media types, a Standards Track
Track RFC MUST be produced for a new top-level content type to be RFC MUST be produced for a new top-level media type to be registered,
registered, and the registration MUST provide good justification why and the registration MUST provide good justification why no existing
no existing media name is appropriate (the "Standards Action" policy media name is appropriate (the "Standards Action" policy of
of [RFC5226]. [RFC5226].
This memo registers the media types "audio", "video", "text", This memo registers the media types "audio", "video", "text",
"application", and "message". "application", and "message".
Note: The media types "control" and "data" were listed as valid in an Note: The media types "control" and "data" were listed as valid in an
early version of this specification (RFC 2327); however, their early version of this specification (RFC 2327); however, their
semantics were never fully specified and they are not widely used. semantics were never fully specified and they are not widely used.
These media types have been removed in this specification, although These media types have been removed in this specification, although
they still remain valid media type capabilities for a SIP user agent they still remain valid media type capabilities for a SIP user agent
as defined in [RFC3840]. If these media types are considered useful as defined in [RFC3840]. If these media types are considered useful
skipping to change at page 44, line 48 skipping to change at page 44, line 48
10. Summary of Changes from RFC 4566 10. Summary of Changes from RFC 4566
The ABNF rule for IP6-address has been corrected. As a result, the The ABNF rule for IP6-address has been corrected. As a result, the
ABNF rule for IP6-multicast has changed, and the (now unused) rules ABNF rule for IP6-multicast has changed, and the (now unused) rules
for hexpart, hexseq, and hex4 have been removed. for hexpart, hexseq, and hex4 have been removed.
IPv4 unicast and multicast addresses in the example SDP descriptions IPv4 unicast and multicast addresses in the example SDP descriptions
have been revised per RFCs 5735 and 5771. have been revised per RFCs 5735 and 5771.
Text in Section 5.2 has been revised to clarify the use of local
addresses in case of ICE-like SDP extensions.
Normative and informative references have been updated. Normative and informative references have been updated.
The following purely editorial changes have been made: The following purely editorial changes have been made:
o Section 4.6: fix typo in first sentence: "sets" -> "set" o Section 4.6: fix typo in first sentence: "sets" -> "set"
o Section 5: clarify second paragraph (SDP field and attribute names o Section 5: clarify second paragraph (SDP field and attribute names
use the US-ASCII subset of UTF-8). use the US-ASCII subset of UTF-8).
o Section 5: clarify that an SDP session description can contain o Section 5: clarify that an SDP session description can contain
skipping to change at page 46, line 7 skipping to change at page 46, line 7
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 Hoeneisen, Jonathan Jonathan Lennox, Keith Drage, Sean Olson, Bernie Hoeneisen, Jonathan
Rosenberg, John Elwell, Flemming Andreasen, Jon Peterson, Spencer Rosenberg, John Elwell, Flemming Andreasen, Jon Peterson, Spencer
Dawkins, and Alfred Hoenes. Dawkins, and Alfred Hoenes.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC1034] Mockapetris, P., "Domain names - concepts and [RFC1034] Mockapetris, P., "Domain names - concepts
facilities", STD 13, RFC 1034, November 1987. and facilities", STD 13, RFC 1034,
November 1987.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names -
specification", STD 13, RFC 1035, November 1987. implementation and specification", STD 13,
RFC 1035, November 1987.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to
Requirement Levels", BCP 14, RFC 2119, March 1997. Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for [RFC5234] Crocker, D. and P. Overell, "Augmented BNF
Syntax Specifications: ABNF", STD 68, RFC 5234, for Syntax Specifications: ABNF", STD 68,
January 2008. RFC 5234, January 2008.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation
10646", STD 63, RFC 3629, November 2003. format of ISO 10646", STD 63, RFC 3629,
November 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, [RFC3986] Berners-Lee, T., Fielding, R., and L.
"Uniform Resource Identifier (URI): Generic Syntax", Masinter, "Uniform Resource Identifier
STD 66, RFC 3986, January 2005. (URI): Generic Syntax", STD 66, RFC 3986,
January 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for [RFC5226] Narten, T. and H. Alvestrand, "Guidelines
Writing an IANA Considerations Section in RFCs", for Writing an IANA Considerations Section
BCP 26, RFC 5226, May 2008. in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for
Languages", BCP 47, RFC 5646, September 2009. Identifying Languages", BCP 47, RFC 5646,
September 2009.
[RFC5890] Klensin, J., "Internationalized Domain Names for [RFC5890] Klensin, J., "Internationalized Domain
Applications (IDNA): Definitions and Document Names for Applications (IDNA): Definitions
Framework", RFC 5890, August 2010. and Document Framework", RFC 5890,
August 2010.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data [RFC4648] Josefsson, S., "The Base16, Base32, and
Encodings", RFC 4648, October 2006. Base64 Data Encodings", RFC 4648,
October 2006.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: [RFC4566] Handley, M., Jacobson, V., and C. Perkins,
Session Description Protocol", RFC 4566, July 2006. "SDP: Session Description Protocol",
RFC 4566, July 2006.
12.2. Informative References 12.2. Informative References
[RFC2327] Handley, M. and V. Jacobson, "SDP: Session [RFC2327] Handley, M. and V. Jacobson, "SDP: Session
Description Protocol", RFC 2327, April 1998. Description Protocol", RFC 2327,
April 1998.
[RFC5905] Mills, D., Martin, J., Burbank, J., and W. Kasch, [RFC5905] Mills, D., Martin, J., Burbank, J., and W.
"Network Time Protocol Version 4: Protocol and Kasch, "Network Time Protocol Version 4:
Algorithms Specification", RFC 5905, June 2010. Protocol and Algorithms Specification",
RFC 5905, June 2010.
[RFC2974] Handley, M., Perkins, C., and E. Whelan, "Session [RFC2974] Handley, M., Perkins, C., and E. Whelan,
Announcement Protocol", RFC 2974, October 2000. "Session Announcement Protocol", RFC 2974,
October 2000.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo,
Johnston, A., Peterson, J., Sparks, R., Handley, M., G., Johnston, A., Peterson, J., Sparks,
and E. Schooler, "SIP: Session Initiation Protocol", R., Handley, M., and E. Schooler, "SIP:
RFC 3261, June 2002. Session Initiation Protocol", RFC 3261,
June 2002.
[RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, "Real [RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier,
Time Streaming Protocol (RTSP)", RFC 2326, "Real Time Streaming Protocol (RTSP)",
April 1998. RFC 2326, April 1998.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer [RFC3264] Rosenberg, J. and H. Schulzrinne, "An
Model with Session Description Protocol (SDP)", Offer/Answer Model with Session
RFC 3264, June 2002. Description Protocol (SDP)", RFC 3264,
June 2002.
[RFC5888] Camarillo, G. and H. Schulzrinne, "The Session [RFC5888] Camarillo, G. and H. Schulzrinne, "The
Description Protocol (SDP) Grouping Framework", Session Description Protocol (SDP)
RFC 5888, June 2010. Grouping Framework", RFC 5888, June 2010.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick,
Jacobson, "RTP: A Transport Protocol for Real-Time R., and V. Jacobson, "RTP: A Transport
Applications", STD 64, RFC 3550, July 2003. Protocol for Real-Time Applications",
STD 64, RFC 3550, July 2003.
[RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for [RFC3551] Schulzrinne, H. and S. Casner, "RTP
Audio and Video Conferences with Minimal Control", Profile for Audio and Video Conferences
STD 65, RFC 3551, July 2003. with Minimal Control", STD 65, RFC 3551,
July 2003.
[RFC3556] Casner, S., "Session Description Protocol (SDP) [RFC3556] Casner, S., "Session Description Protocol
Bandwidth Modifiers for RTP Control Protocol (RTCP) (SDP) Bandwidth Modifiers for RTP Control
Bandwidth", RFC 3556, July 2003. Protocol (RTCP) Bandwidth", RFC 3556,
July 2003.
[RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) [RFC3605] Huitema, C., "Real Time Control Protocol
attribute in Session Description Protocol (SDP)", (RTCP) attribute in Session Description
RFC 3605, October 2003. Protocol (SDP)", RFC 3605, October 2003.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., [RFC3711] Baugher, M., McGrew, D., Naslund, M.,
and K. Norrman, "The Secure Real-time Transport Carrara, E., and K. Norrman, "The Secure
Protocol (SRTP)", RFC 3711, March 2004. Real-time Transport Protocol (SRTP)",
RFC 3711, March 2004.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, [RFC3840] Rosenberg, J., Schulzrinne, H., and P.
"Indicating User Agent Capabilities in the Session Kyzivat, "Indicating User Agent
Initiation Protocol (SIP)", RFC 3840, August 2004. Capabilities in the Session Initiation
Protocol (SIP)", RFC 3840, August 2004.
[RFC3890] Westerlund, M., "A Transport Independent Bandwidth [RFC3890] Westerlund, M., "A Transport Independent
Modifier for the Session Description Protocol Bandwidth Modifier for the Session
(SDP)", RFC 3890, September 2004. Description Protocol (SDP)", RFC 3890,
September 2004.
[ITU.H332.1998] International Telecommunication Union, "H.323 [RFC5245] Rosenberg, J., "Interactive Connectivity
extended for loosely coupled conferences", Establishment (ICE): A Protocol for
ITU Recommendation H.332, September 1998. Network Address Translator (NAT) Traversal
for Offer/Answer Protocols", RFC 5245,
April 2010.
[RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., [I-D.ietf-mmusic-ice-tcp] Rosenberg, J., Keranen, A., Lowekamp, B.,
and E. Carrara, "Key Management Extensions for and A. Roach, "TCP Candidates with
Session Description Protocol (SDP) and Real Time Interactive Connectivity Establishment
Streaming Protocol (RTSP)", RFC 4567, July 2006. (ICE)", draft-ietf-mmusic-ice-tcp-16 (work
in progress), November 2011.
[RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session [ITU.H332.1998] International Telecommunication Union,
Description Protocol (SDP) Security Descriptions for "H.323 extended for loosely coupled
Media Streams", RFC 4568, July 2006. conferences", ITU Recommendation H.332,
September 1998.
[RFC5322] Resnick, P., Ed., "Internet Message Format", [RFC4567] Arkko, J., Lindholm, F., Naslund, M.,
RFC 5322, October 2008. Norrman, K., and E. Carrara, "Key
Management Extensions for Session
Description Protocol (SDP) and Real Time
Streaming Protocol (RTSP)", RFC 4567,
July 2006.
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications [RFC4568] Andreasen, F., Baugher, M., and D. Wing,
and Registration Procedures", BCP 13, RFC 4288, "Session Description Protocol (SDP)
Security Descriptions for Media Streams",
RFC 4568, July 2006.
[RFC5322] Resnick, P., Ed., "Internet Message
Format", RFC 5322, October 2008.
[RFC4288] Freed, N. and J. Klensin, "Media Type
Specifications and Registration
Procedures", BCP 13, RFC 4288,
December 2005. December 2005.
Authors' Addresses Authors' Addresses
Mark Handley Mark Handley
University College London University College London
Department of Computer Science Department of Computer Science
Gower Street
London WC1E 6BT London WC1E 6BT
UK UK
EMail: M.Handley@cs.ucl.ac.uk EMail: M.Handley@cs.ucl.ac.uk
Van Jacobson Van Jacobson
Packet Design PARC
2465 Latham Street 3333 Coyote Hill Road
Mountain View, CA 94040 Palo Alto, CA 94304
USA USA
EMail: van@parc.com EMail: van@parc.com
Colin Perkins Colin Perkins
University of Glasgow University of Glasgow
School of Computing Science School of Computing Science
University of Glasgow University of Glasgow
Glasgow G12 8QQ Glasgow G12 8QQ
UK UK
EMail: csp@csperkins.org EMail: csp@csperkins.org
Ali Begen Ali Begen
 End of changes. 44 change blocks. 
103 lines changed or deleted 144 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/