< draft-mcglashan-mscp-02.txt		draft-mcglashan-mscp-03.txt >
	Network Working Group S. McGlashan		Network Working Group S. McGlashan
	Internet-Draft Hewlett-Packard		Internet-Draft Hewlett-Packard
	Intended status: Standards Track R. Auburn		Intended status: Standards Track R. Auburn
	Expires: February 1, 2007 Voxeo		Expires: September 3, 2007 Voxeo
	D. Burke		D. Burke
	Voxpilot		Voxpilot
	E. Candell		E. Candell
	Comverse		Comverse
	R. Surapaneni		R. Surapaneni
	Tellme Networks		Tellme Networks
	July 31, 2006		March 2, 2007
	Media Server Control Protocol (MSCP)		Media Server Control Protocol (MSCP)
	draft-mcglashan-mscp-02.txt		draft-mcglashan-mscp-03.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		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 becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	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 February 1, 2007.		This Internet-Draft will expire on September 3, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This document specifies MSCP (Media Server Control Protocol), a		This document specifies MSCP (Media Server Control Protocol), a
	protocol to control interactive dialog and conferencing functions on		protocol to control interactive dialog and conferencing functions on
	a media server. The protocol messages - requests, responses and		a media server. The protocol messages - requests, responses and
	notifications - are modeled on dialog and conferencing elements		notifications - are modeled on dialog and conferencing elements
	defined in CCXML (Voice Browser Call Control), and interactive		defined in CCXML (Voice Browser Call Control), and interactive
	dialogs can be specified in VoiceXML (Voice Extensible Markup		dialogs can be specified in VoiceXML (Voice Extensible Markup
	Language). MSCP messages have self-contained XML representation and		Language). MSCP messages have self-contained XML representation and
	skipping to change at page 8, line 16 ¶		skipping to change at page 8, line 16 ¶
	and executes services such as interactive media and conferencing		and executes services such as interactive media and conferencing
	in an operator's network. An AS influences and impacts the SIP		in an operator's network. An AS influences and impacts the SIP
	session, in particular by terminating SIP sessions on a media		session, in particular by terminating SIP sessions on a media
	server, which is under its control.		server, which is under its control.
	Media Server: A media server (MS) processes media streams on behalf		Media Server: A media server (MS) processes media streams on behalf
	of an AS by offering functionality such as interactive media,		of an AS by offering functionality such as interactive media,
	conferencing, and transcoding to the end user. Interactive media		conferencing, and transcoding to the end user. Interactive media
	functionality is realized by way of dialogs, which are identified		functionality is realized by way of dialogs, which are identified
	by a URI and initiated by the application server. Conferencing		by a URI and initiated by the application server. Conferencing
	mixing [SIPCONF] functionality is controlled directly by the AS.		mixing [RFC4353] functionality is controlled directly by the AS.
	2.3. Architecture		2.3. Architecture
	Even though the MSCP protocol is modeled on a subset of CCXML		Even though the MSCP protocol is modeled on a subset of CCXML
	elements, the protocol is agnostic to the implementation of the AS		elements, the protocol is agnostic to the implementation of the AS
	and MS. These may be implemented using CCXML and VoiceXML		and MS. These may be implemented using CCXML and VoiceXML
	interpreters, due to ease of authoring applications in XML. For		interpreters, due to ease of authoring applications in XML. For
	example, the AS is implemented as a CCXML interpreter and the MS is		example, the AS is implemented as a CCXML interpreter and the MS is
	implemented using a VoiceXML interpreter for dialog functions and a		implemented using a VoiceXML interpreter for dialog functions and a
	conferencing interpreter for conferencing functions.		conferencing interpreter for conferencing functions.
	The MSCP protocol can be used between an AS and MS in a variety of		The MSCP protocol can be used between an AS and MS in a variety of
	architectures; for example, in SIP architectures including IPCC and		architectures; for example, in SIP architectures including IPCC and
	3GPP IMS. In the IMS architecture, an incoming call arriving at the		3GPP IMS. In the IMS architecture, an incoming call arriving at the
	CSCF is handled by a SIP AS. When media processing is required, the		CSCF is handled by a SIP AS. When media processing is required, the
	AS interacts with a MRF MS to obtain media services.		AS interacts with a MRF MS to obtain media services.
	For conferencing applications, the AS includes the conference focus,		For conferencing applications, the AS includes the conference focus,
	conference policy server, and conference notification server		conference policy server, and conference notification server
	[SIPCONF]. The AS MAY support the SIP Event Package for Conference		[RFC4353]. The AS MAY support the SIP Event Package for Conference
	State [SIPEVENTS]. The MS exposes mixer functionality under control		State [RFC4575]. The MS exposes mixer functionality under control of
	of the AS via the MSCP protocol.		the AS via the MSCP protocol.
	For a CCXML AS, the conference policy is defined by the executing		For a CCXML AS, the conference policy is defined by the executing
	CCXML application. A conference policy server may be implemented via		CCXML application. A conference policy server may be implemented via
	the CCXML Basic Event I/O Processor. The conference URI, which		the CCXML Basic Event I/O Processor. The conference URI, which
	uniquely identifies the focus of the conference, can be mapped by the		uniquely identifies the focus of the conference, can be mapped by the
	AS to a specific CCXML conferencing application. For example,		AS to a specific CCXML conferencing application. For example,
	1234@as1.example.com might be mapped to		1234@as1.example.com might be mapped to
	http://www.example.com/confapp01.ccxml.		http://www.example.com/confapp01.ccxml.
	2.3.1. Connections, Dialogs and Conferences		2.3.1. Connections, Dialogs and Conferences
	skipping to change at page 57, line 15 ¶		skipping to change at page 57, line 15 ¶
	A simple transaction model is employed. The AS can send requests to		A simple transaction model is employed. The AS can send requests to
	the MS. A response message must be sent from the MS to the AS in		the MS. A response message must be sent from the MS to the AS in
	reply to each request message. Notification messages may be sent at		reply to each request message. Notification messages may be sent at
	any time from the AS to the MS or from the MS to the AS.		any time from the AS to the MS or from the MS to the AS.
	7.2.1. Establishing the Transport Channel		7.2.1. Establishing the Transport Channel
	The AS can locate the MS in the SIP network using standard SIP		The AS can locate the MS in the SIP network using standard SIP
	mechanisms [RFC3263]. The transport channel is established via the		mechanisms [RFC3263]. The transport channel is established via the
	SDP offer/answer model [RFC3264] and the mechanism described in		SDP offer/answer model [RFC3264] and the mechanism described in
	[TCPSDP]. The transport channel is identified in the SDP offer and		[RFC4145]. The transport channel is identified in the SDP offer and
	answer with an m-line of type "application". The port number in the		answer with an m-line of type "application". The port number in the
	offer is fixed at 9. The corresponding m-line in the answer		offer is fixed at 9. The corresponding m-line in the answer
	specifies the MS port number for which the AS must connect to. The		specifies the MS port number for which the AS must connect to. The
	a=setup attribute MUST be "active" for the offer from the AS and MUST		a=setup attribute MUST be "active" for the offer from the AS and MUST
	be "passive" for the answer from the MS.		be "passive" for the answer from the MS.
	The transport channel persists for the duration of the associated SIP		The transport channel persists for the duration of the associated SIP
	dialog. If an endpoint determines that the TCP connection has been		dialog. If an endpoint determines that the TCP connection has been
	closed and it should be reestablished, it SHOULD perform a new offer/		closed and it should be reestablished, it SHOULD perform a new offer/
	answer exchange using a connection value of 'new' for this m-line.		answer exchange using a connection value of 'new' for this m-line.
	skipping to change at page 78, line 18 ¶		skipping to change at page 78, line 18 ¶
	[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.
	13.2. Informative References		13.2. Informative References
	[BASIC_CONFERENCE_PACKAGE]		[BASIC_CONFERENCE_PACKAGE]
	Boulton, C., Melanchuk, T., McGlashan, S., and A.		Boulton, C., Melanchuk, T., McGlashan, S., and A.
	Shiratzky, "A Conference Control Package for the Session		Shiratzky, "A Conference Control Package for the Session
	Initiation Protocol (SIP)",		Initiation Protocol (SIP)",
	draft-boulton-conference-control-package-00 (work in		draft-boulton-conference-control-package-01 (work in
	progress), March 2006.		progress), November 2006.
	[BASIC_IVR_PACKAGE]		[BASIC_IVR_PACKAGE]
	Boulton, C., Melanchuk, T., McGlashan, S., and A.		Boulton, C., Melanchuk, T., McGlashan, S., and A.
	Shiratzky, "A Basic Interactive Voice Response (IVR)		Shiratzky, "A Basic Interactive Voice Response (IVR)
	Control Package for the Session Initiation Protocol		Control Package for the Session Initiation Protocol
	(SIP)", draft-boulton-ivr-control-package-01 (work in		(SIP)", draft-boulton-ivr-control-package-03 (work in
	progress), March 2006.		progress), March 2007.
	[CCXML10] Auburn, R J., "Voice Browser Call Control: CCXML Version		[CCXML10] Auburn, R J., "Voice Browser Call Control: CCXML Version
	1.0", W3C Working Draft (work in progress), June 2005.		1.0", W3C Working Draft (work in progress), January 2007.
	[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,		[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
	Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext		Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
	Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.		Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
	[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,
	June 2002.		June 2002.
	skipping to change at page 79, line 5 ¶		skipping to change at page 79, line 5 ¶
	[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.
	[RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G.		[RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G.
	Camarillo, "Best Current Practices for Third Party Call		Camarillo, "Best Current Practices for Third Party Call
	Control (3pcc) in the Session Initiation Protocol (SIP)",		Control (3pcc) in the Session Initiation Protocol (SIP)",
	BCP 85, RFC 3725, April 2004.		BCP 85, RFC 3725, April 2004.
	[SIPCONF] Rosenberg, J., "A Framework for Conferencing with the		[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
	Session Initiation Protocol",		the Session Description Protocol (SDP)", RFC 4145,
	draft-ietf-sipping-conferencing-framework-05 (work in		September 2005.
	progress), May 2005.
	[SIPCONTROLFRAMEWORK]		[RFC4353] Rosenberg, J., "A Framework for Conferencing with the
	Boulton, C., Melanchuk, T., McGlashan, S., and A.		Session Initiation Protocol (SIP)", RFC 4353,
	Shiratzky, "A Control Framework for the Session Initiation		February 2006.
	Protocol (SIP)", draft-boulton-sip-control-framework-03
	(work in progress), June 2006.
	[SIPEVENTS]		[RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
	Rosenberg, J., Schulzrinne, H., and O. Levin, "Session
	Initiation Protocol (SIP) Event Package for Conference		Initiation Protocol (SIP) Event Package for Conference
	State", draft-ietf-sipping-conferencing-package-11 (work		State", RFC 4575, August 2006.
	in progress), June 2005.
	[TCPSDP] Yon, D. and G. Camarillo, "TCP-Based Media Transport in		[SIPCONTROLFRAMEWORK]
	the Session Description Protocol (SDP)",		Boulton, C., Melanchuk, T., McGlashan, S., and A.
	draft-ietf-mmusic-sdp-comedia-10 (work in progress),		Shiratzky, "A Control Framework for the Session Initiation
	November 2004.		Protocol (SIP)", draft-boulton-sip-control-framework-05
			(work in progress), February 2007.
	[VXML20] McGlashan, S., Burnett, D., Carter, J., Danielsen, P.,		[VXML20] McGlashan, S., Burnett, D., Carter, J., Danielsen, P.,
	Ferrans, J., Hunt, A., Lucas, B., Porter, B., Rehor, K.,		Ferrans, J., Hunt, A., Lucas, B., Porter, B., Rehor, K.,
	and S. Tryphonas, "Voice Extensible Markup Language		and S. Tryphonas, "Voice Extensible Markup Language
	(VoiceXML) Version 2.0", W3C Recommendation, March 2004.		(VoiceXML) Version 2.0", W3C Recommendation, March 2004.
	[VXML_IVR_PACKAGE]		[VXML_IVR_PACKAGE]
	Boulton, C., Melanchuk, T., McGlashan, S., and A.		Boulton, C., Melanchuk, T., McGlashan, S., and A.
	Shiratzky, "A VoiceXML Interactive Voice Response (IVR)		Shiratzky, "A VoiceXML Interactive Voice Response (IVR)
	Control Package for the Session Initiation Protocol		Control Package for the Session Initiation Protocol
	(SIP)", draft-boulton-ivr-vxml-control-package-00 (work in		(SIP)", draft-boulton-ivr-vxml-control-package-02 (work in
	progress), March 2006.		progress), March 2007.
	[XML] Bray, T., Paoli, J., Sperberg-McQueen, C M., Maler, E.,		[XML] Bray, T., Paoli, J., Sperberg-McQueen, C M., Maler, E.,
	and F. Yergeau, "Extensible Markup Language (XML) 1.0		and F. Yergeau, "Extensible Markup Language (XML) 1.0
	(Third Edition)", W3C Recommendation, February 2004.		(Third Edition)", W3C Recommendation, February 2004.
	Authors' Addresses		Authors' Addresses
	Scott McGlashan		Scott McGlashan
	Hewlett-Packard		Hewlett-Packard
	Gustav III:s boulevard 36		Gustav III:s boulevard 36
	skipping to change at page 81, line 7 ¶		skipping to change at page 81, line 7 ¶
	Rao Surapaneni		Rao Surapaneni
	Tellme Networks		Tellme Networks
	1310 Villa Street		1310 Villa Street
	Mountain View, CA 94041		Mountain View, CA 94041
	USA		USA
	Email: rao@tellme.com		Email: rao@tellme.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (2006).		Copyright (C) The IETF Trust (2007).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Intellectual Property		Intellectual Property
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
End of changes. 19 change blocks.
	39 lines changed or deleted		35 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/