draft-ietf-mmusic-rfc4566bis-05.txt   draft-ietf-mmusic-rfc4566bis-06.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 PARC Intended status: Standards Track PARC
Expires: August 30, 2012 C. Perkins Expires: February 26, 2013 C. Perkins
University of Glasgow University of Glasgow
A. Begen A. Begen
Cisco Cisco
February 27, 2012 August 25, 2012
SDP: Session Description Protocol SDP: Session Description Protocol
draft-ietf-mmusic-rfc4566bis-05 draft-ietf-mmusic-rfc4566bis-06
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. This document obsoletes RFC 4566. multimedia session initiation. This document obsoletes RFC 4566.
Status of This Memo Status of This Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 August 30, 2012. This Internet-Draft will expire on February 26, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
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 . . . . . . . . . . . . . . . . . . 47 12.2. Informative References . . . . . . . . . . . . . . . . . . 46
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 42 skipping to change at page 12, line 42
<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. Unless an SDP extension for NAT traversal is used substituted. Unless an SDP extension for NAT traversal is used
(e.g., ICE [RFC5245], ICE TCP [I-D.ietf-mmusic-ice-tcp]), a local (e.g., ICE [RFC5245], ICE TCP [RFC6544]), a local IP address MUST
IP address MUST NOT be used in any context where the SDP NOT be used in any context where the SDP description might leave
description might leave the scope in which the address is the scope in which the address is meaningful (for example, a local
meaningful (for example, a local address MUST NOT be included in address MUST NOT be included in an application-level referral that
an application-level referral that might leave the scope). 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 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 [RFC1034] Mockapetris, P., "Domain names - concepts and
and facilities", STD 13, RFC 1034, facilities", STD 13, RFC 1034, November 1987.
November 1987.
[RFC1035] Mockapetris, P., "Domain names - [RFC1035] Mockapetris, P., "Domain names - implementation and
implementation and specification", STD 13, specification", STD 13, RFC 1035, November 1987.
RFC 1035, November 1987.
[RFC2119] Bradner, S., "Key words for use in RFCs to [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Indicate Requirement Levels", BCP 14, Requirement Levels", BCP 14, RFC 2119, March 1997.
RFC 2119, March 1997.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for
for Syntax Specifications: ABNF", STD 68, Syntax Specifications: ABNF", STD 68, RFC 5234,
RFC 5234, January 2008. January 2008.
[RFC3629] Yergeau, F., "UTF-8, a transformation [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
format of ISO 10646", STD 63, RFC 3629, 10646", STD 63, RFC 3629, November 2003.
November 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,
Masinter, "Uniform Resource Identifier "Uniform Resource Identifier (URI): Generic Syntax",
(URI): Generic Syntax", STD 66, RFC 3986, STD 66, RFC 3986, January 2005.
January 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for
for Writing an IANA Considerations Section Writing an IANA Considerations Section in RFCs",
in RFCs", BCP 26, RFC 5226, May 2008. BCP 26, RFC 5226, May 2008.
[RFC5646] Phillips, A. and M. Davis, "Tags for [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Identifying Languages", BCP 47, RFC 5646, Languages", BCP 47, RFC 5646, September 2009.
September 2009.
[RFC5890] Klensin, J., "Internationalized Domain [RFC5890] Klensin, J., "Internationalized Domain Names for
Names for Applications (IDNA): Definitions Applications (IDNA): Definitions and Document
and Document Framework", RFC 5890, Framework", RFC 5890, August 2010.
August 2010.
[RFC4648] Josefsson, S., "The Base16, Base32, and [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Base64 Data Encodings", RFC 4648, Encodings", RFC 4648, October 2006.
October 2006.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP:
"SDP: Session Description Protocol", Session Description Protocol", RFC 4566, July 2006.
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, Description Protocol", RFC 2327, April 1998.
April 1998.
[RFC5905] Mills, D., Martin, J., Burbank, J., and W. [RFC5905] Mills, D., Martin, J., Burbank, J., and W. Kasch,
Kasch, "Network Time Protocol Version 4: "Network Time Protocol Version 4: Protocol and
Protocol and Algorithms Specification", Algorithms Specification", RFC 5905, June 2010.
RFC 5905, June 2010.
[RFC2974] Handley, M., Perkins, C., and E. Whelan, [RFC2974] Handley, M., Perkins, C., and E. Whelan, "Session
"Session Announcement Protocol", RFC 2974, Announcement Protocol", RFC 2974, October 2000.
October 2000.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G.,
G., Johnston, A., Peterson, J., Sparks, Johnston, A., Peterson, J., Sparks, R., Handley, M.,
R., Handley, M., and E. Schooler, "SIP: and E. Schooler, "SIP: Session Initiation Protocol",
Session Initiation Protocol", RFC 3261, RFC 3261, June 2002.
June 2002.
[RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, [RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, "Real
"Real Time Streaming Protocol (RTSP)", Time Streaming Protocol (RTSP)", RFC 2326,
RFC 2326, April 1998. April 1998.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer
Offer/Answer Model with Session Model with Session Description Protocol (SDP)",
Description Protocol (SDP)", RFC 3264, RFC 3264, June 2002.
June 2002.
[RFC5888] Camarillo, G. and H. Schulzrinne, "The [RFC5888] Camarillo, G. and H. Schulzrinne, "The Session
Session Description Protocol (SDP) Description Protocol (SDP) Grouping Framework",
Grouping Framework", RFC 5888, June 2010. RFC 5888, June 2010.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
R., and V. Jacobson, "RTP: A Transport Jacobson, "RTP: A Transport Protocol for Real-Time
Protocol for Real-Time Applications", Applications", STD 64, RFC 3550, July 2003.
STD 64, RFC 3550, July 2003.
[RFC3551] Schulzrinne, H. and S. Casner, "RTP [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for
Profile for Audio and Video Conferences Audio and Video Conferences with Minimal Control",
with Minimal Control", STD 65, RFC 3551, STD 65, RFC 3551, July 2003.
July 2003.
[RFC3556] Casner, S., "Session Description Protocol [RFC3556] Casner, S., "Session Description Protocol (SDP)
(SDP) Bandwidth Modifiers for RTP Control Bandwidth Modifiers for RTP Control Protocol (RTCP)
Protocol (RTCP) Bandwidth", RFC 3556, Bandwidth", RFC 3556, July 2003.
July 2003.
[RFC3605] Huitema, C., "Real Time Control Protocol [RFC3605] Huitema, C., "Real Time Control Protocol (RTCP)
(RTCP) attribute in Session Description attribute in Session Description Protocol (SDP)",
Protocol (SDP)", RFC 3605, October 2003. RFC 3605, October 2003.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E.,
Carrara, E., and K. Norrman, "The Secure and K. Norrman, "The Secure Real-time Transport
Real-time Transport Protocol (SRTP)", Protocol (SRTP)", RFC 3711, March 2004.
RFC 3711, March 2004.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
Kyzivat, "Indicating User Agent "Indicating User Agent Capabilities in the Session
Capabilities in the Session Initiation Initiation Protocol (SIP)", RFC 3840, August 2004.
Protocol (SIP)", RFC 3840, August 2004.
[RFC3890] Westerlund, M., "A Transport Independent [RFC3890] Westerlund, M., "A Transport Independent Bandwidth
Bandwidth Modifier for the Session Modifier for the Session Description Protocol
Description Protocol (SDP)", RFC 3890, (SDP)", RFC 3890, September 2004.
September 2004.
[RFC5245] Rosenberg, J., "Interactive Connectivity [RFC5245] Rosenberg, J., "Interactive Connectivity
Establishment (ICE): A Protocol for Establishment (ICE): A Protocol for Network Address
Network Address Translator (NAT) Traversal Translator (NAT) Traversal for Offer/Answer
for Offer/Answer Protocols", RFC 5245, Protocols", RFC 5245, April 2010.
April 2010.
[I-D.ietf-mmusic-ice-tcp] Rosenberg, J., Keranen, A., Lowekamp, B., [RFC6544] Rosenberg, J., Keranen, A., Lowekamp, B., and A.
and A. Roach, "TCP Candidates with Roach, "TCP Candidates with Interactive Connectivity
Interactive Connectivity Establishment Establishment (ICE)", RFC 6544, March 2012.
(ICE)", draft-ietf-mmusic-ice-tcp-16 (work
in progress), November 2011.
[ITU.H332.1998] International Telecommunication Union, [ITU.H332.1998] International Telecommunication Union, "H.323
"H.323 extended for loosely coupled extended for loosely coupled conferences",
conferences", ITU Recommendation H.332, ITU Recommendation H.332, September 1998.
September 1998.
[RFC4567] Arkko, J., Lindholm, F., Naslund, M., [RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K.,
Norrman, K., and E. Carrara, "Key and E. Carrara, "Key Management Extensions for
Management Extensions for Session Session Description Protocol (SDP) and Real Time
Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)", RFC 4567, July 2006.
Streaming Protocol (RTSP)", RFC 4567,
July 2006.
[RFC4568] Andreasen, F., Baugher, M., and D. Wing, [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session
"Session Description Protocol (SDP) Description Protocol (SDP) Security Descriptions for
Security Descriptions for Media Streams", Media Streams", RFC 4568, July 2006.
RFC 4568, July 2006.
[RFC5322] Resnick, P., Ed., "Internet Message [RFC5322] Resnick, P., Ed., "Internet Message Format",
Format", RFC 5322, October 2008. RFC 5322, October 2008.
[RFC4288] Freed, N. and J. Klensin, "Media Type [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications
Specifications and Registration and Registration Procedures", BCP 13, RFC 4288,
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
London WC1E 6BT London WC1E 6BT
UK UK
 End of changes. 38 change blocks. 
124 lines changed or deleted 96 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/