[rfc-dist] RFC 5049 on Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Dec 12 15:04:26 PST 2007


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

        
        RFC 5049

        Title:      Applying Signaling Compression (SigComp) to 
                    the Session Initiation Protocol (SIP) 
        Author:     C. Bormann, Z. Liu,
                    R. Price, G. Camarillo, Ed.
        Status:     Standards Track
        Date:       December 2007
        Mailbox:    cabo at tzi.org, 
                    zhigang.c.liu at nokia.com, 
                    richard.price at eads.com,  
                    Gonzalo.Camarillo at ericsson.com
        Pages:      21
        Characters: 47891
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rohc-sigcomp-sip-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5049.txt

This document describes some specifics that apply when Signaling
Compression (SigComp) is applied to the Session Initiation Protocol
(SIP), such as default minimum values of SigComp parameters,
compartment and state management, and a few issues on SigComp over
TCP.  Any implementation of SigComp for use with SIP must conform to
this document and SigComp, and in addition, support the SIP and
Session Description Protocol (SDP) static dictionary.  [STANDARDS TRACK]

This document is a product of the Robust Header Compression
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list