< draft-rosenberg-sip-tote-01.txt		draft-rosenberg-sip-tote-02.txt >
	SIP J. Rosenberg		SIP J. Rosenberg
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track July 14, 2008		Intended status: Standards Track November 3, 2008
	Expires: January 15, 2009		Expires: May 7, 2009
	Session Based Trivial Object Transfer and Exchange (TOTE)		Session Based Trivial Object Transfer and Exchange (TOTE)
	draft-rosenberg-sip-tote-01		draft-rosenberg-sip-tote-02
	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 34 ¶		skipping to change at page 1, line 34 ¶
	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 January 15, 2009.		This Internet-Draft will expire on May 7, 2009.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2008).		Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	This document defines a simple protocol - Trivial Object Transfer and		This document defines a simple protocol - Trivial Object Transfer and
	Exchange (TOTE) - that provides bidirectional exchange of MIME		Exchange (TOTE) - that provides bidirectional exchange of MIME
	objects over a TCP connection. It is used in conjunction with		objects over a TCP connection. It is used in conjunction with
	skipping to change at page 2, line 37 ¶		skipping to change at page 2, line 37 ¶
	11.1. TOTE Purpose Registry . . . . . . . . . . . . . . . . . . 13		11.1. TOTE Purpose Registry . . . . . . . . . . . . . . . . . . 13
	11.2. SDP Transport Protocol . . . . . . . . . . . . . . . . . . 14		11.2. SDP Transport Protocol . . . . . . . . . . . . . . . . . . 14
	11.3. SDP Attribute Names . . . . . . . . . . . . . . . . . . . 14		11.3. SDP Attribute Names . . . . . . . . . . . . . . . . . . . 14
	11.3.1. Send Purposes . . . . . . . . . . . . . . . . . . . . 14		11.3.1. Send Purposes . . . . . . . . . . . . . . . . . . . . 14
	11.3.2. Receive Purposes . . . . . . . . . . . . . . . . . . 14		11.3.2. Receive Purposes . . . . . . . . . . . . . . . . . . 14
	12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15		12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15		13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
	13.1. Normative References . . . . . . . . . . . . . . . . . . . 15		13.1. Normative References . . . . . . . . . . . . . . . . . . . 15
	13.2. Informative References . . . . . . . . . . . . . . . . . . 16		13.2. Informative References . . . . . . . . . . . . . . . . . . 16
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16
	Intellectual Property and Copyright Statements . . . . . . . . . . 17		Intellectual Property and Copyright Statements . . . . . . . . . . 18
	1. Introduction		1. Introduction
	The Session Initiation Protocol (SIP) [RFC3261] allows for the		The Session Initiation Protocol (SIP) [RFC3261] allows for the
	establishment, management, and termination of interactive sessions		establishment, management, and termination of interactive sessions
	between user agents. These sessions are often used for the exchange		between user agents. These sessions are often used for the exchange
	of real time media, such as voice, video or text, using protocols		of real time media, such as voice, video or text, using protocols
	such as the Real Time Transport Protocol (RTP).		such as the Real Time Transport Protocol (RTP).
	Oftentimes, there is a need for agents to exchange non-real time		Oftentimes, there is a need for agents to exchange non-real time
	skipping to change at page 3, line 45 ¶		skipping to change at page 3, line 45 ¶
	that is desired. This subscription is ideally done as part of a		that is desired. This subscription is ideally done as part of a
	separate dialog. This technique is recommended for application		separate dialog. This technique is recommended for application
	interaction, and is described in		interaction, and is described in
	[I-D.ietf-sipping-app-interaction-framework].		[I-D.ietf-sipping-app-interaction-framework].
	Media: A user agent can use SIP to set up another media session		Media: A user agent can use SIP to set up another media session
	whose purpose is to carry the application specific data.		whose purpose is to carry the application specific data.
	INFO: A user agent can send the data in a SIP INFO message along the		INFO: A user agent can send the data in a SIP INFO message along the
	existing SIP dialog. This technique is described in		existing SIP dialog. This technique is described in
	[I-D.kaplan-sip-info-events].		[I-D.ietf-sip-info-events].
	Currently, there is no general purpose protocol that allows agents to		Currently, there is no general purpose protocol that allows agents to
	set up a media session for the exchange of application data. This		set up a media session for the exchange of application data. This
	specification fills that need. It defines a protocol called Trivial		specification fills that need. It defines a protocol called Trivial
	Object Transfer and Exchange (TOTE). TOTE is a TCP-based protocol		Object Transfer and Exchange (TOTE). TOTE is a TCP-based protocol
	that provides framing and content-typing. This specification also		that provides framing and content-typing. This specification also
	defines parameters for the Session Description Protocol (SDP)		defines parameters for the Session Description Protocol (SDP)
	[RFC4566] so that TOTE sessions can be established using protocols		[RFC4566] so that TOTE sessions can be established using protocols
	based on the offer/answer model [RFC3264], such as SIP. These SDP		based on the offer/answer model [RFC3264], such as SIP. These SDP
	extensions allow agents to negotiate the "purpose" of TOTE session,		extensions allow agents to negotiate the "purpose" of TOTE session,
	along with supported MIME types. The "purpose" is a parameter that		along with supported MIME types. The "purpose" is a parameter that
	operates similarly to the INFO events defined in		operates similarly to the INFO events defined in
	[I-D.kaplan-sip-info-events].		[I-D.ietf-sip-info-events].
	2. Overview of Operation		2. Overview of Operation
	An agent wishing to establish a TOTE session includes a "message"		An agent wishing to establish a TOTE session includes a "message"
	media line in an SDP offer. This m-line indicates that the messaging		media line in an SDP offer. This m-line indicates that the messaging
	session uses TOTE over TCP or TLS over TCP (TOTE is defined only for		session uses TOTE over TCP or TLS over TCP (TOTE is defined only for
	TCP or TLS/TCP). The m-line also includes a list of "purpose"		TCP or TLS/TCP). The m-line also includes a list of "purpose"
	parameters that the agent wishes to receive or wishes to send. TOTE		parameters that the agent wishes to receive or wishes to send. TOTE
	sessions can be established before there is a need to actually send		sessions can be established before there is a need to actually send
	or receive data, or on-demand at the time the exchange is desired.		or receive data, or on-demand at the time the exchange is desired.
	skipping to change at page 15, line 45 ¶		skipping to change at page 15, line 45 ¶
	[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.
	[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.
	[I-D.ietf-mmusic-ice-tcp]		[I-D.ietf-mmusic-ice-tcp]
	Rosenberg, J., "TCP Candidates with Interactive		Rosenberg, J., "TCP Candidates with Interactive
	Connectivity Establishment (ICE)",		Connectivity Establishment (ICE)",
	draft-ietf-mmusic-ice-tcp-06 (work in progress),		draft-ietf-mmusic-ice-tcp-07 (work in progress),
	February 2008.		July 2008.
	[RFC4572] Lennox, J., "Connection-Oriented Media Transport over the		[RFC4572] Lennox, J., "Connection-Oriented Media Transport over the
	Transport Layer Security (TLS) Protocol in the Session		Transport Layer Security (TLS) Protocol in the Session
	Description Protocol (SDP)", RFC 4572, July 2006.		Description Protocol (SDP)", RFC 4572, July 2006.
	[RFC4571] Lazzaro, J., "Framing Real-time Transport Protocol (RTP)		[RFC4571] Lazzaro, J., "Framing Real-time Transport Protocol (RTP)
	and RTP Control Protocol (RTCP) Packets over Connection-		and RTP Control Protocol (RTCP) Packets over Connection-
	Oriented Transport", RFC 4571, July 2006.		Oriented Transport", RFC 4571, July 2006.
	13.2. Informative References		13.2. Informative References
	[I-D.ietf-sipping-app-interaction-framework]		[I-D.ietf-sipping-app-interaction-framework]
	Rosenberg, J., "A Framework for Application Interaction in		Rosenberg, J., "A Framework for Application Interaction in
	the Session Initiation Protocol (SIP)",		the Session Initiation Protocol (SIP)",
	draft-ietf-sipping-app-interaction-framework-05 (work in		draft-ietf-sipping-app-interaction-framework-05 (work in
	progress), July 2005.		progress), July 2005.
	[I-D.kaplan-sip-info-events]		[I-D.ietf-sip-info-events]
	Kaplan, H. and C. Holmberg, "The SIP INFO Method and Info		Burger, E., Kaplan, H., and C. Holmberg, "Session
	Package Framework", draft-kaplan-sip-info-events-01 (work		Initiation Protocol (SIP) INFO Method and Package
	in progress), February 2008.		Framework", draft-ietf-sip-info-events-00 (work in
			progress), October 2008.
	[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 2434,		IANA Considerations Section in RFCs", BCP 26, RFC 2434,
	October 1998.		October 1998.
	[RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message		[RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message
	Session Relay Protocol (MSRP)", RFC 4975, September 2007.		Session Relay Protocol (MSRP)", RFC 4975, September 2007.
	[RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session		[RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
	Initiation Protocol (SIP) Event Package for Conference		Initiation Protocol (SIP) Event Package for Conference
	State", RFC 4575, August 2006.		State", RFC 4575, August 2006.
	[I-D.ietf-xcon-common-data-model]		[I-D.ietf-xcon-common-data-model]
	Novo, O., Camarillo, G., Morgan, D., and R. Even,		Novo, O., Camarillo, G., Morgan, D., Even, R., and J.
	"Conference Information Data Model for Centralized		Urpalainen, "Conference Information Data Model for
	Conferencing (XCON)", draft-ietf-xcon-common-data-model-11		Centralized Conferencing (XCON)",
	(work in progress), June 2008.		draft-ietf-xcon-common-data-model-12 (work in progress),
			October 2008.
	Author's Address		Author's Address
	Jonathan Rosenberg		Jonathan Rosenberg
	Cisco		Cisco
	Edison, NJ		Iselin, NJ
	US		US
	Phone: +1 973 952-5000
	Email: jdrosen@cisco.com		Email: jdrosen@cisco.com
	URI: http://www.jdrosen.net		URI: http://www.jdrosen.net
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2008).		Copyright (C) The IETF Trust (2008).
	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.
End of changes. 11 change blocks.
	19 lines changed or deleted		20 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/