RFC 3486 on Compressing the Session Initiation Protocol (SIP)

rfc-editor@RFC-EDITOR.ORG, sipping@ietf.org, sip@ietf.org Wed, 05 March 2003 18:13 UTC

Message-Id: <200303042353.h24Nr4Z14535@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3486 on Compressing the Session Initiation Protocol (SIP)
Cc: rfc-editor@RFC-EDITOR.ORG
From: rfc-editor@RFC-EDITOR.ORG, sipping@ietf.org, sip@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 04 Mar 2003 15:53:04 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

A new Request for Comments is now available in online RFC libraries.


        RFC 3486

        Title:      Compressing the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo
        Status:     Standards Track
        Date:       February 2003
        Mailbox:    Gonzalo.Camarillo@ericsson.com
        Pages:      12
        Characters: 24181
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-compression-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3486.txt


This document describes a mechanism to signal that compression is
desired for one or more Session Initiation Protocol
(SIP) messages.  It also states when it is appropriate to send
compressed SIP messages to a SIP entity.

This document is a product of the Session Initiation Proposal
Investigation Working Group and the Session Initiation Protocol
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3486.txt"><ftp://ftp.isi.edu/in-notes/rfc3486.txt>

RFC 3486 on Compressing the Session Initiation Pr… rfc-editor
RFC 3486 on Compressing the Session Initiation Pr… rfc-editor