< draft-ietf-mmusic-sdp-miscellaneous-caps-00.txt		draft-ietf-mmusic-sdp-miscellaneous-caps-02.txt >
	MMUSIC WG M. Garcia-Martin		MMUSIC WG M. Garcia-Martin
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Standards Track S. Veikkolainen		Intended status: Standards Track S. Veikkolainen
	Expires: September 27, 2012 Nokia		Expires: April 17, 2013 Nokia
	R. Gilman		R. Gilman
	March 26, 2012		October 14, 2012
	Miscellanoues Capabilities Negotiation in the Session Description		Miscellanoues Capabilities Negotiation in the Session Description
	Protocol (SDP)		Protocol (SDP)
	draft-ietf-mmusic-sdp-miscellaneous-caps-00		draft-ietf-mmusic-sdp-miscellaneous-caps-02
	Abstract		Abstract
	SDP has been extended with a capability negotiation mechanism		SDP has been extended with a capability negotiation mechanism
	framework that allows the endpoints to negotiate transport protocols		framework that allows the endpoints to negotiate transport protocols
	and attributes. This framework has been extended with a media		and attributes. This framework has been extended with a media
	capabilities negotiation mechanism that allows endpoints to negotiate		capabilities negotiation mechanism that allows endpoints to negotiate
	additional media-related capabilities. This negotiation is embedded		additional media-related capabilities. This negotiation is embedded
	into the widely-used SDP offer/answer procedures.		into the widely-used SDP offer/answer procedures.
	skipping to change at page 1, line 44		skipping to change at page 1, line 44
	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 September 27, 2012.		This Internet-Draft will expire on April 17, 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 15		skipping to change at page 3, line 15
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Conventions Used in This Document . . . . . . . . . . . . . . 4		2. Conventions Used in This Document . . . . . . . . . . . . . . 4
	3. Protocol Description . . . . . . . . . . . . . . . . . . . . . 4		3. Protocol Description . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Extensions to SDP . . . . . . . . . . . . . . . . . . . . 4		3.1. Extensions to SDP . . . . . . . . . . . . . . . . . . . . 4
	3.1.1. Bandwidth Capability . . . . . . . . . . . . . . . . . 7		3.1.1. Bandwidth Capability . . . . . . . . . . . . . . . . . 7
	3.1.2. Connection Data Capability . . . . . . . . . . . . . . 9		3.1.2. Connection Data Capability . . . . . . . . . . . . . . 9
	3.1.3. Title Capability . . . . . . . . . . . . . . . . . . . 11		3.1.3. Title Capability . . . . . . . . . . . . . . . . . . . 11
	3.2. Session Level versus Media Level . . . . . . . . . . . . . 14		3.2. Session Level versus Media Level . . . . . . . . . . . . . 14
	3.3. Offer/Answer model extensions . . . . . . . . . . . . . . 14		3.3. Offer/Answer model extensions . . . . . . . . . . . . . . 15
	3.3.1. Generating the Initial Offer . . . . . . . . . . . . . 15		3.3.1. Generating the Initial Offer . . . . . . . . . . . . . 15
	3.3.2. Generating the Answer . . . . . . . . . . . . . . . . 15		3.3.2. Generating the Answer . . . . . . . . . . . . . . . . 15
	3.3.3. Offerer Processing of the Answer . . . . . . . . . . . 15		3.3.3. Offerer Processing of the Answer . . . . . . . . . . . 15
	3.3.4. Modifying the Session . . . . . . . . . . . . . . . . 15		3.3.4. Modifying the Session . . . . . . . . . . . . . . . . 15
	4. Field Replacement Rules . . . . . . . . . . . . . . . . . . . 15		4. Field Replacement Rules . . . . . . . . . . . . . . . . . . . 16
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
	5.1. New SDP Attributes . . . . . . . . . . . . . . . . . . . . 16		5.1. New SDP Attributes . . . . . . . . . . . . . . . . . . . . 16
	5.2. New Option Tags . . . . . . . . . . . . . . . . . . . . . 17		5.2. New Option Tags . . . . . . . . . . . . . . . . . . . . . 17
	5.3. New SDP Capability Negotiation Configuration Parameters . 17		5.3. New SDP Capability Negotiation Configuration Parameters . 17
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 17		6. Security Considerations . . . . . . . . . . . . . . . . . . . 17
	7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18		7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
	8.1. Normative References . . . . . . . . . . . . . . . . . . . 18		8.1. Normative References . . . . . . . . . . . . . . . . . . . 18
	8.2. Informative References . . . . . . . . . . . . . . . . . . 18		8.2. Informative References . . . . . . . . . . . . . . . . . . 18
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
	skipping to change at page 10, line 35		skipping to change at page 10, line 35
	<extension-config-list>, with		<extension-config-list>, with
	ext-cap-name = "c"		ext-cap-name = "c"
	ext-cap-list = conn-cap-list		ext-cap-list = conn-cap-list
	where, according to the following Augmented Backus-Naur Form (ABNF)		where, according to the following Augmented Backus-Naur Form (ABNF)
	[RFC5234] syntax:		[RFC5234] syntax:
	extension-config-list =/ conn-config-list		extension-config-list =/ conn-config-list
	conn-config-list = "c=" conn-cap-list		conn-config-list = ["+"] "c=" conn-cap-list
	conn-cap-list = conn-cap-num *(BAR conn-cap-num)		conn-cap-list = conn-cap-num *(BAR conn-cap-num)
	conn-cap-num = 1*DIGIT ; 1 to 2^32-1 inclusive		conn-cap-num = 1*DIGIT ; 1 to 2^32-1 inclusive
	Figure 6: Syntax of the connection data parameter in 'lcfg' and		Figure 6: Syntax of the connection data parameter in 'lcfg' and
	'pcfg' attributes		'pcfg' attributes
	Each capability configuration alternative contains a single		Each capability configuration alternative contains a single
	connection data capability attribute number and refers to the conn-		connection data capability attribute number and refers to the conn-
	cap-num capability number defined explicitly earlier in this		cap-num capability number defined explicitly earlier in this
	document, and hence must be between 1 and 2^31-1 (both included).		document, and hence must be between 1 and 2^31-1 (both included).
	The connection data capability allows the expression of only a single		The connection data capability allows the expression of only a single
	capability in each alternative, rather than a list of capabilities,		capability in each alternative, rather than a list of capabilities,
	since no more than a single connection data field is permitted per		since no more than a single connection data field is permitted per
	media block. Nevertheless, it is still allowed to express		media block. Nevertheless, it is still allowed to express
	alternative potential connection configurations separated by a		alternative potential connection configurations separated by a
	vertical bar ("|").		vertical bar ("|").
			An endpoint includes a plus sign ("+") in this configuration
			attribute to mandate support for this extension. An endpoint that
			receives this attribute prefixed with a plus sign and does not
			support this extension MUST treat that potential configuration as not
			valid.
	The connection data parameter to the actual configuration attribute		The connection data parameter to the actual configuration attribute
	('a=acfg') is formulated as a <sel-extension-config> with		('a=acfg') is formulated as a <sel-extension-config> with
	ext-cap-name = "c"		ext-cap-name = "c"
	hence		hence
	sel-extension-config =/ sel-connection-config		sel-extension-config =/ sel-connection-config
	sel-connection-config = "c=" conn-cap-num ; as defined above.		sel-connection-config = "c=" conn-cap-num ; as defined above.
	skipping to change at page 18, line 17		skipping to change at page 18, line 17
	Thanks to Christer Holmberg, Alf Heidermark, and Ingemar Johansson		Thanks to Christer Holmberg, Alf Heidermark, and Ingemar Johansson
	for arguing for the existence of this document and early reviewing		for arguing for the existence of this document and early reviewing
	it. Thanks to Flemming Andreasen, Andrew Allen, and Jonathan Lennox		it. Thanks to Flemming Andreasen, Andrew Allen, and Jonathan Lennox
	for a detailed review and many improvement suggestions.		for a detailed review and many improvement suggestions.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[I-D.ietf-mmusic-sdp-media-capabilities]		[I-D.ietf-mmusic-sdp-media-capabilities]
	Gilman, R., Even, R., and F. Andreasen, "SDP Media		Gilman, R., Even, R., and F. Andreasen, "Session
	Capabilities Negotiation",		Description Protocol (SDP) Media Capabilities
	draft-ietf-mmusic-sdp-media-capabilities-13 (work in		Negotiation", draft-ietf-mmusic-sdp-media-capabilities-15
	progress), March 2012.		(work in progress), October 2012.
	[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, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[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,
	June 2002.		June 2002.
	[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session		[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
	Description Protocol", RFC 4566, July 2006.		Description Protocol", RFC 4566, July 2006.
	skipping to change at page 18, line 45		skipping to change at page 18, line 45
	[RFC5939] Andreasen, F., "Session Description Protocol (SDP)		[RFC5939] Andreasen, F., "Session Description Protocol (SDP)
	Capability Negotiation", RFC 5939, September 2010.		Capability Negotiation", RFC 5939, September 2010.
	8.2. Informative References		8.2. Informative References
	[I-D.ietf-mmusic-sdp-cs]		[I-D.ietf-mmusic-sdp-cs]
	Garcia, M. and S. Veikkolainen, "Session Description		Garcia, M. and S. Veikkolainen, "Session Description
	Protocol (SDP) Extension For Setting Up Audio and Video		Protocol (SDP) Extension For Setting Up Audio and Video
	Media Streams Over Circuit-Switched Bearers In The Public		Media Streams Over Circuit-Switched Bearers In The Public
	Switched Telephone Network (PSTN)",		Switched Telephone Network (PSTN)",
	draft-ietf-mmusic-sdp-cs-10 (work in progress),		draft-ietf-mmusic-sdp-cs-12 (work in progress),
	March 2012.		October 2012.
	[RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the		[RFC3108] Kumar, R. and M. Mostafa, "Conventions for the use of the
	Session Description Protocol (SDP) for ATM Bearer		Session Description Protocol (SDP) for ATM Bearer
	Connections", RFC 3108, May 2001.		Connections", RFC 3108, May 2001.
	[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, July 2003.		Applications", STD 64, RFC 3550, July 2003.
	[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.		[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
End of changes. 10 change blocks.
	13 lines changed or deleted		19 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/