[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I-D ACTION:draft-ietf-sipping-cc-framework-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: A Call Control and Multi-party usage framework 
			  for the Session Initiation Protocol (SIP)
	Author(s)	: R. Mahy et. al.
	Filename	: draft-ietf-sipping-cc-framework-02.txt
	Pages		: 43
	Date		: 2003-3-7
This document defines a framework and requirements for multi-party
usage of SIP.  To enable discussion of multi-party features and
applications we define an abstract call model for describing the
media relationships required by many of these.  The model and actions
described here are specifically chosen to be independent of the SIP
signaling and/or mixing approach chosen to actually setup the media
relationships.  In addition to its dialog manipulation aspect, this
framework includes requirements for communicating related information
and events such as conference and session state, and session history.
This framework also describes other goals which embody the spirit of
SIP applications as used on the Internet.

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-cc-framework-02.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-cc-framework-02.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the