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

I-D ACTION:draft-ietf-sipping-sigcomp-sip-dictionary-01.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		: The Session Initiation Protocol (SIP) and Session 
                          Description Protocol (SDP) static dictionary for 
                          Signaling Compression (SigComp)
	Author(s)	: M. Garcia et al.
	Filename	: draft-ietf-sipping-sigcomp-sip-dictionary-01.txt
	Pages		: 23
	Date		: 22-May-02
The Session Initiation Protocol (SIP) [2] is a text-based protocol for
initiating and managing communication sessions. The protocol can be
compressed by using Signaling Compression (SigComp) [1]. Similarly,
the Session Description Protocol (SDP) [24] is a text-based protocol
intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of
multimedia session initiation. This memo defines a SIP/SDP-specific
static dictionary that SigComp can use in order to achieve higher
efficiency. The dictionary is compression algorithm independent.

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-sigcomp-sip-dictionary-01.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-sigcomp-sip-dictionary-01.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