< draft-ietf-mmusic-rfc4566bis-18.txt   draft-ietf-mmusic-rfc4566bis-19.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
Expires: August 8, 2017 C. Perkins Expires: December 19, 2017 C. Perkins
University of Glasgow University of Glasgow
A. Begen A. Begen
Networked Media Networked Media
February 4, 2017 June 17, 2017
SDP: Session Description Protocol SDP: Session Description Protocol
draft-ietf-mmusic-rfc4566bis-18 draft-ietf-mmusic-rfc4566bis-19
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 8, 2017. This Internet-Draft will expire on December 19, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 4, line 11 skipping to change at page 4, line 11
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
format for session description -- it does not incorporate a transport format for session description -- it does not incorporate a transport
protocol, and it is intended to use different transport protocols as protocol, and it is intended to use different transport protocols as
appropriate, including the Session Announcement Protocol (SAP) appropriate, including the Session Announcement Protocol (SAP)
[RFC2974], Session Initiation Protocol (SIP) [RFC3261], Real Time [RFC2974], Session Initiation Protocol (SIP) [RFC3261], Real Time
Streaming Protocol (RTSP) [RFC2326], electronic mail using the MIME Streaming Protocol (RTSP) [RFC7826], electronic mail using the MIME
extensions, and the Hypertext Transport Protocol (HTTP). extensions, and the Hypertext Transport Protocol (HTTP).
SDP is intended to be general purpose so that it can be used in a SDP is intended to be general purpose so that it can be used in a
wide range of network environments and applications. However, it is wide range of network environments and applications. However, it is
not intended to support negotiation of session content or media not intended to support negotiation of session content or media
encodings: this is viewed as outside the scope of session encodings: this is viewed as outside the scope of session
description. description.
This memo obsoletes [RFC4566]. The changes relative to [RFC4566] are This memo obsoletes [RFC4566]. The changes relative to [RFC4566] are
limited to essential corrections, and are outlined in Section 10 of limited to essential corrections, and are outlined in Section 10 of
skipping to change at page 5, line 9 skipping to change at page 5, line 9
sessions such as Internet multimedia conferences, Internet telephone sessions such as Internet multimedia conferences, Internet telephone
calls, and multimedia distribution. The SIP messages used to create calls, and multimedia distribution. The SIP messages used to create
sessions carry session descriptions that allow participants to agree sessions carry session descriptions that allow participants to agree
on a set of compatible media types. These session descriptions are on a set of compatible media types. These session descriptions are
commonly formatted using SDP. When used with SIP, the offer/answer commonly formatted using SDP. When used with SIP, the offer/answer
model [RFC3264] provides a limited framework for negotiation using model [RFC3264] provides a limited framework for negotiation using
SDP. SDP.
3.2. Streaming Media 3.2. Streaming Media
The Real Time Streaming Protocol (RTSP) [RFC2326], is an application- The Real Time Streaming Protocol (RTSP) [RFC7826], is an application-
level protocol for control over the delivery of data with real-time level protocol for control over the delivery of data with real-time
properties. RTSP provides an extensible framework to enable properties. RTSP provides an extensible framework to enable
controlled, on-demand delivery of real-time data, such as audio and controlled, on-demand delivery of real-time data, such as audio and
video. An RTSP client and server negotiate an appropriate set of video. An RTSP client and server negotiate an appropriate set of
parameters for media delivery, partially using SDP syntax to describe parameters for media delivery, partially using SDP syntax to describe
those parameters. those parameters.
3.3. Email and the World Wide Web 3.3. Email and the World Wide Web
Alternative means of conveying session descriptions include Alternative means of conveying session descriptions include
skipping to change at page 9, line 9 skipping to change at page 9, line 9
key. key.
An SDP description consists of a number of lines of text of the form: An SDP description consists of a number of lines of text of the form:
<type>=<value> <type>=<value>
where <type> MUST be exactly one case-significant character and where <type> MUST be exactly one case-significant character and
<value> is structured text whose format depends on <type>. In <value> is structured text whose format depends on <type>. In
general, <value> is either a number of fields delimited by a single general, <value> is either a number of fields delimited by a single
space character or a free format string, and is case-significant space character or a free format string, and is case-significant
unless a specific field defines otherwise. Whitespace MUST NOT be unless a specific field defines otherwise. Whitespace separators
used on either side of the "=" sign. MUST NOT be used on either side of the "=" sign, however, if the
value can contain a leading whitespace as part of its syntax, i.e.,
that whitespace is part of the value.
An SDP description consists of a session-level section followed by An SDP description consists of a session-level section followed by
zero or more media-level sections. The session-level part starts zero or more media-level sections. The session-level part starts
with a "v=" line and continues to the first media-level section (or with a "v=" line and continues to the first media-level section (or
the end of the whole description, whichever comes first). Each the end of the whole description, whichever comes first). Each
media-level section starts with an "m=" line and continues to the media-level section starts with an "m=" line and continues to the
next media-level section or the end of the whole session description next media-level section or the end of the whole session description
- whichever comes first. In general, session-level values are the - whichever comes first. In general, session-level values are the
default for all media unless overridden by an equivalent media-level default for all media unless overridden by an equivalent media-level
value. value.
skipping to change at page 33, line 30 skipping to change at page 33, line 30
portrait = %s"portrait" portrait = %s"portrait"
landscape = %s"landscape" landscape = %s"landscape"
seascape = %s"seascape" seascape = %s"seascape"
; NOTE: These names are case-sensitive. ; NOTE: These names are case-sensitive.
Example: Example:
a=orient:portrait a=orient:portrait
Normally this is only used for a whiteboard or presentation tool. It Normally this is only used for a whiteboard or presentation tool. It
specifies the orientation of a the workspace on the screen. specifies the orientation of the workspace on the screen. Permitted
Permitted values are "portrait", "landscape", and "seascape" (upside- values are "portrait", "landscape", and "seascape" (upside-down
down landscape). landscape).
6.9. type (conference type) 6.9. type (conference type)
Name: type Name: type
Value: type-value Value: type-value
Usage Level: session Usage Level: session
Charset Dependent: no Charset Dependent: no
skipping to change at page 34, line 49 skipping to change at page 34, line 49
Value: charset-value Value: charset-value
Usage Level: session Usage Level: session
Charset Dependent: no Charset Dependent: no
Syntax: Syntax:
charset-value = mime-charset charset-value = mime-charset
(as defined in I-D.iana-charset-reg-procedure) (as defined in [RFC 2978])
This specifies the character set to be used to display the session This specifies the character set to be used to display the session
name and information data. By default, the ISO-10646 character set name and information data. By default, the ISO-10646 character set
in UTF-8 encoding is used. If a more compact representation is in UTF-8 encoding is used. If a more compact representation is
required, other character sets may be used. For example, the ISO required, other character sets may be used. For example, the ISO
8859-1 is specified with the following SDP attribute: 8859-1 is specified with the following SDP attribute:
a=charset:ISO-8859-1 a=charset:ISO-8859-1
The charset specified MUST be one of those registered in the IANA The charset specified MUST be one of those registered in the IANA
skipping to change at page 50, line 11 skipping to change at page 50, line 11
on whether the attribute value is subject to the charset attribute. on whether the attribute value is subject to the charset attribute.
The "Mux Category" column MUST indicate one of the following The "Mux Category" column MUST indicate one of the following
categories: NORMAL, NOT RECOMMENDED, IDENTICAL, SUM, TRANSPORT, categories: NORMAL, NOT RECOMMENDED, IDENTICAL, SUM, TRANSPORT,
INHERIT, IDENTICAL-PER-PT, SPECIAL or TBD as defined by INHERIT, IDENTICAL-PER-PT, SPECIAL or TBD as defined by
[I-D.ietf-mmusic-sdp-mux-attributes]. Finally, the "Reference" [I-D.ietf-mmusic-sdp-mux-attributes]. Finally, the "Reference"
column indicates the specification(s) where the attribute is defined. column indicates the specification(s) where the attribute is defined.
For example, the attribute "setup" which is defined for both session For example, the attribute "setup" which is defined for both session
and media level, will be listed in the new registry as follows: and media level, will be listed in the new registry as follows:
Name | Usage Level | Dependent on Charset? | Mux Category | Reference Name | Usage Level | Dependent on Charset?|Mux Category| Reference |
setup | session,media, | No | IDENTICAL | [RFC4145],[RFC6135], | setup | session,media, | No |IDENTICAL | [RFC4145] |
| dcsa,dcsa(msrp)| | | [I-D.mmusic-msrp-usage-data-channel] | | dcsa,dcsa(msrp)| | | [RFC6135] |
| | | | [I-D.mmusic
| | | |-msrp-usage-
| | | |data-channel
| | | |] |
9. SDP Grammar 9. SDP Grammar
This section provides an Augmented BNF grammar for SDP. ABNF is This section provides an Augmented BNF grammar for SDP. ABNF is
defined in [RFC5234] and [RFC7405]. defined in [RFC5234] and [RFC7405].
; SDP Syntax ; SDP Syntax
session-description = proto-version session-description = proto-version
origin-field origin-field
session-name-field session-name-field
information-field [information-field]
uri-field [uri-field]
email-fields *email-fields
phone-fields *phone-fields
connection-field [connection-field]
bandwidth-fields *bandwidth-fields
time-fields 1*time-fields
key-field [key-field]
attribute-fields *attribute-fields
media-descriptions *media-descriptions
proto-version = %s"v" "=" 1*DIGIT CRLF proto-version = %s"v" "=" 1*DIGIT CRLF
;this memo describes version 0 ;this memo describes version 0
origin-field = %s"o" "=" username SP sess-id SP sess-version SP origin-field = %s"o" "=" username SP sess-id SP sess-version SP
nettype SP addrtype SP unicast-address CRLF nettype SP addrtype SP unicast-address CRLF
session-name-field = %s"s" "=" text CRLF session-name-field = %s"s" "=" text CRLF
information-field = [%s"i" "=" text CRLF] information-field = %s"i" "=" text CRLF
uri-field = [%s"u" "=" uri CRLF]
email-fields = *(%s"e" "=" email-address CRLF) uri-field = %s"u" "=" uri CRLF
phone-fields = *(%s"p" "=" phone-number CRLF) email-fields = %s"e" "=" email-address CRLF
phone-fields = %s"p" "=" phone-number CRLF
connection-field = [%s"c" "=" nettype SP addrtype SP connection-field = %s"c" "=" nettype SP addrtype SP
connection-address CRLF] connection-address CRLF
;a connection field must be present ;a connection field must be present
;in every media description or at the ;in every media description or at the
;session-level ;session-level
bandwidth-fields = *(%s"b" "=" bwtype ":" bandwidth CRLF) bandwidth-fields = %s"b" "=" bwtype ":" bandwidth CRLF
time-fields = 1*( %s"t" "=" start-time SP stop-time time-fields = %s"t" "=" start-time SP stop-time
*(CRLF repeat-fields) CRLF) *(CRLF repeat-fields) CRLF
[zone-adjustments CRLF] [zone-adjustments CRLF]
repeat-fields = %s"r" "=" repeat-interval SP typed-time repeat-fields = %s"r" "=" repeat-interval SP typed-time
1*(SP typed-time) 1*(SP typed-time)
zone-adjustments = %s"z" "=" time SP ["-"] typed-time zone-adjustments = %s"z" "=" time SP ["-"] typed-time
*(SP time SP ["-"] typed-time) *(SP time SP ["-"] typed-time)
key-field = [%s"k" "=" key-type CRLF] key-field = %s"k" "=" key-type CRLF
attribute-fields = *(%s"a" "=" attribute CRLF) attribute-fields = %s"a" "=" attribute CRLF
media-descriptions = *( media-field media-descriptions = media-field
information-field information-field
*connection-field *connection-field
bandwidth-fields bandwidth-fields
key-field key-field
attribute-fields ) attribute-fields
media-field = %s"m" "=" media SP port ["/" integer] media-field = %s"m" "=" media SP port ["/" integer]
SP proto 1*(SP fmt) CRLF SP proto 1*(SP fmt) CRLF
; sub-rules of 'o=' ; sub-rules of 'o='
username = non-ws-string username = non-ws-string
;pretty wide definition, but doesn't ;pretty wide definition, but doesn't
;include space ;include space
sess-id = 1*DIGIT sess-id = 1*DIGIT
skipping to change at page 56, line 15 skipping to change at page 56, line 18
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. contributing to this document.
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.ietf-mmusic-data-channel-sdpneg]
Drage, K., Makaraju, M., Stoetzer-Bradler, J., Ejzak, R.,
and J. Marcon, "SDP-based Data Channel Negotiation",
draft-ietf-mmusic-data-channel-sdpneg-12 (work in
progress), March 2017.
[I-D.ietf-mmusic-sdp-mux-attributes]
Nandakumar, S., "A Framework for SDP Attributes when
Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-16
(work in progress), December 2016.
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987,
<http://www.rfc-editor.org/info/rfc1034>. <http://www.rfc-editor.org/info/rfc1034>.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <http://www.rfc-editor.org/info/rfc1035>. November 1987, <http://www.rfc-editor.org/info/rfc1035>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC2978] Freed, N. and J. Postel, "IANA Charset Registration
Specifications: ABNF", STD 68, RFC 5234, Procedures", BCP 19, RFC 2978, DOI 10.17487/RFC2978,
DOI 10.17487/RFC5234, January 2008, October 2000, <http://www.rfc-editor.org/info/rfc2978>.
<http://www.rfc-editor.org/info/rfc5234>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <http://www.rfc-editor.org/info/rfc3629>. 2003, <http://www.rfc-editor.org/info/rfc3629>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>. <http://www.rfc-editor.org/info/rfc3986>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
IANA Considerations Section in RFCs", BCP 26, RFC 5226, Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
DOI 10.17487/RFC5226, May 2008, July 2006, <http://www.rfc-editor.org/info/rfc4566>.
<http://www.rfc-editor.org/info/rfc5226>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,
September 2009, <http://www.rfc-editor.org/info/rfc5646>.
[RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework",
RFC 5890, DOI 10.17487/RFC5890, August 2010,
<http://www.rfc-editor.org/info/rfc5890>.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,
<http://www.rfc-editor.org/info/rfc4648>. <http://www.rfc-editor.org/info/rfc4648>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Description Protocol", RFC 4566, DOI 10.17487/RFC4566, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
July 2006, <http://www.rfc-editor.org/info/rfc4566>. DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[RFC7656] Lennox, J., Gross, K., Nandakumar, S., Salgueiro, G., and [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
B. Burman, Ed., "A Taxonomy of Semantics and Mechanisms Specifications: ABNF", STD 68, RFC 5234,
for Real-Time Transport Protocol (RTP) Sources", RFC 7656, DOI 10.17487/RFC5234, January 2008,
DOI 10.17487/RFC7656, November 2015, <http://www.rfc-editor.org/info/rfc5234>.
<http://www.rfc-editor.org/info/rfc7656>.
[RFC5576] Lennox, J., Ott, J., and T. Schierl, "Source-Specific [RFC5576] Lennox, J., Ott, J., and T. Schierl, "Source-Specific
Media Attributes in the Session Description Protocol Media Attributes in the Session Description Protocol
(SDP)", RFC 5576, DOI 10.17487/RFC5576, June 2009, (SDP)", RFC 5576, DOI 10.17487/RFC5576, June 2009,
<http://www.rfc-editor.org/info/rfc5576>. <http://www.rfc-editor.org/info/rfc5576>.
[I-D.iana-charset-reg-procedure] [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
McFadden, M. and A. Melnikov, "IANA Charset Registration Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,
Procedures", draft-iana-charset-reg-procedure-01 (work in September 2009, <http://www.rfc-editor.org/info/rfc5646>.
progress), April 2015.
[I-D.ietf-mmusic-sdp-mux-attributes]
Nandakumar, S., "A Framework for SDP Attributes when
Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-16
(work in progress), December 2016.
[I-D.ietf-mmusic-data-channel-sdpneg] [RFC5890] Klensin, J., "Internationalized Domain Names for
Drage, K., Makaraju, M., Stoetzer-Bradler, J., Ejzak, R., Applications (IDNA): Definitions and Document Framework",
and J. Marcon, "SDP-based Data Channel Negotiation", RFC 5890, DOI 10.17487/RFC5890, August 2010,
draft-ietf-mmusic-data-channel-sdpneg-11 (work in <http://www.rfc-editor.org/info/rfc5890>.
progress), January 2017.
12.2. Informative References 12.2. Informative References
[ITU.H332.1998]
International Telecommunication Union, "H.323 extended for
loosely coupled conferences", ITU Recommendation H.332,
September 1998.
[RFC2327] Handley, M. and V. Jacobson, "SDP: Session Description [RFC2327] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", RFC 2327, DOI 10.17487/RFC2327, April 1998, Protocol", RFC 2327, DOI 10.17487/RFC2327, April 1998,
<http://www.rfc-editor.org/info/rfc2327>. <http://www.rfc-editor.org/info/rfc2327>.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<http://www.rfc-editor.org/info/rfc5905>.
[RFC2974] Handley, M., Perkins, C., and E. Whelan, "Session [RFC2974] Handley, M., Perkins, C., and E. Whelan, "Session
Announcement Protocol", RFC 2974, DOI 10.17487/RFC2974, Announcement Protocol", RFC 2974, DOI 10.17487/RFC2974,
October 2000, <http://www.rfc-editor.org/info/rfc2974>. October 2000, <http://www.rfc-editor.org/info/rfc2974>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>. <http://www.rfc-editor.org/info/rfc3261>.
[RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time
Streaming Protocol (RTSP)", RFC 2326,
DOI 10.17487/RFC2326, April 1998,
<http://www.rfc-editor.org/info/rfc2326>.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
DOI 10.17487/RFC3264, June 2002, DOI 10.17487/RFC3264, June 2002,
<http://www.rfc-editor.org/info/rfc3264>. <http://www.rfc-editor.org/info/rfc3264>.
[RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description
Protocol (SDP) Grouping Framework", RFC 5888,
DOI 10.17487/RFC5888, June 2010,
<http://www.rfc-editor.org/info/rfc5888>.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
July 2003, <http://www.rfc-editor.org/info/rfc3550>. July 2003, <http://www.rfc-editor.org/info/rfc3550>.
[RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and
Video Conferences with Minimal Control", STD 65, RFC 3551, Video Conferences with Minimal Control", STD 65, RFC 3551,
DOI 10.17487/RFC3551, July 2003, DOI 10.17487/RFC3551, July 2003,
<http://www.rfc-editor.org/info/rfc3551>. <http://www.rfc-editor.org/info/rfc3551>.
skipping to change at page 59, line 26 skipping to change at page 59, line 10
"Indicating User Agent Capabilities in the Session "Indicating User Agent Capabilities in the Session
Initiation Protocol (SIP)", RFC 3840, Initiation Protocol (SIP)", RFC 3840,
DOI 10.17487/RFC3840, August 2004, DOI 10.17487/RFC3840, August 2004,
<http://www.rfc-editor.org/info/rfc3840>. <http://www.rfc-editor.org/info/rfc3840>.
[RFC3890] Westerlund, M., "A Transport Independent Bandwidth [RFC3890] Westerlund, M., "A Transport Independent Bandwidth
Modifier for the Session Description Protocol (SDP)", Modifier for the Session Description Protocol (SDP)",
RFC 3890, DOI 10.17487/RFC3890, September 2004, RFC 3890, DOI 10.17487/RFC3890, September 2004,
<http://www.rfc-editor.org/info/rfc3890>. <http://www.rfc-editor.org/info/rfc3890>.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245,
DOI 10.17487/RFC5245, April 2010,
<http://www.rfc-editor.org/info/rfc5245>.
[RFC6544] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach,
"TCP Candidates with Interactive Connectivity
Establishment (ICE)", RFC 6544, DOI 10.17487/RFC6544,
March 2012, <http://www.rfc-editor.org/info/rfc6544>.
[RFC7405] Kyzivat, P., "Case-Sensitive String Support in ABNF",
RFC 7405, DOI 10.17487/RFC7405, December 2014,
<http://www.rfc-editor.org/info/rfc7405>.
[ITU.H332.1998]
International Telecommunication Union, "H.323 extended for
loosely coupled conferences", ITU Recommendation H.332,
September 1998.
[RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E. [RFC4567] Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E.
Carrara, "Key Management Extensions for Session Carrara, "Key Management Extensions for Session
Description Protocol (SDP) and Real Time Streaming Description Protocol (SDP) and Real Time Streaming
Protocol (RTSP)", RFC 4567, DOI 10.17487/RFC4567, July Protocol (RTSP)", RFC 4567, DOI 10.17487/RFC4567, July
2006, <http://www.rfc-editor.org/info/rfc4567>. 2006, <http://www.rfc-editor.org/info/rfc4567>.
[RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session
Description Protocol (SDP) Security Descriptions for Media Description Protocol (SDP) Security Descriptions for Media
Streams", RFC 4568, DOI 10.17487/RFC4568, July 2006, Streams", RFC 4568, DOI 10.17487/RFC4568, July 2006,
<http://www.rfc-editor.org/info/rfc4568>. <http://www.rfc-editor.org/info/rfc4568>.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, DOI 10.17487/RFC4855, February 2007,
<http://www.rfc-editor.org/info/rfc4855>.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245,
DOI 10.17487/RFC5245, April 2010,
<http://www.rfc-editor.org/info/rfc5245>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
DOI 10.17487/RFC5322, October 2008, DOI 10.17487/RFC5322, October 2008,
<http://www.rfc-editor.org/info/rfc5322>. <http://www.rfc-editor.org/info/rfc5322>.
[RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description
Protocol (SDP) Grouping Framework", RFC 5888,
DOI 10.17487/RFC5888, June 2010,
<http://www.rfc-editor.org/info/rfc5888>.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<http://www.rfc-editor.org/info/rfc5905>.
[RFC6544] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach,
"TCP Candidates with Interactive Connectivity
Establishment (ICE)", RFC 6544, DOI 10.17487/RFC6544,
March 2012, <http://www.rfc-editor.org/info/rfc6544>.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, Specifications and Registration Procedures", BCP 13,
RFC 6838, DOI 10.17487/RFC6838, January 2013, RFC 6838, DOI 10.17487/RFC6838, January 2013,
<http://www.rfc-editor.org/info/rfc6838>. <http://www.rfc-editor.org/info/rfc6838>.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC7405] Kyzivat, P., "Case-Sensitive String Support in ABNF",
Formats", RFC 4855, DOI 10.17487/RFC4855, February 2007, RFC 7405, DOI 10.17487/RFC7405, December 2014,
<http://www.rfc-editor.org/info/rfc4855>. <http://www.rfc-editor.org/info/rfc7405>.
[RFC7656] Lennox, J., Gross, K., Nandakumar, S., Salgueiro, G., and
B. Burman, Ed., "A Taxonomy of Semantics and Mechanisms
for Real-Time Transport Protocol (RTP) Sources", RFC 7656,
DOI 10.17487/RFC7656, November 2015,
<http://www.rfc-editor.org/info/rfc7656>.
[RFC7826] Schulzrinne, H., Rao, A., Lanphier, R., Westerlund, M.,
and M. Stiemerling, Ed., "Real-Time Streaming Protocol
Version 2.0", RFC 7826, DOI 10.17487/RFC7826, December
2016, <http://www.rfc-editor.org/info/rfc7826>.
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
EMail: M.Handley@cs.ucl.ac.uk EMail: M.Handley@cs.ucl.ac.uk
Van Jacobson Van Jacobson
PARC
3333 Coyote Hill Road
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
 End of changes. 37 change blocks. 
120 lines changed or deleted 121 lines changed or added

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