idnits 2.17.1 draft-ietf-rohc-sigcomp-07.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3320 5 Title: Signaling Compression (SigComp) 6 Author(s): R. Price, C. Bormann, J. Christoffersson, 7 H. Hannu, Z. Liu, J. Rosenberg 8 Status: Standards Track 9 Date: January 2003 10 Mailbox: richard.price@roke.co.uk, cabo@tzi.org, 11 jan.christoffersson@epl.ericsson.se, 12 hans.hannu@epl.ericsson.se 13 zhigang.c.liu@nokia.com, jdrosen@dynamicsoft.com 14 Pages: 62 15 Characters: 137035 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-rohc-sigcomp-07.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3320.txt 22 This document defines Signaling Compression (SigComp), a solution for 23 compressing messages generated by application protocols such as the 24 Session Initiation Protocol (SIP) (RFC 3261) and the Real Time 25 Streaming Protocol (RTSP) (RFC 2326). The architecture and 26 prerequisites of SigComp are outlined, along with the format of the 27 SigComp message. 29 Decompression functionality for SigComp is provided by a Universal 30 Decompressor Virtual Machine (UDVM) optimized for the task of running 31 decompression algorithms. The UDVM can be configured to understand 32 the output of many well-known compressors such as DEFLATE (RFC-1951). 34 This document is a product of Robust Header Compression Working Group 35 of the IETF. 37 This is now a Proposed Standard Protocol. 39 This document specifies an Internet standards track protocol for 40 the Internet community, and requests discussion and suggestions 41 for improvements. Please refer to the current edition of the 42 "Internet Official Protocol Standards" (STD 1) for the 43 standardization state and status of this protocol. Distribution 44 of this memo is unlimited. 46 This announcement is sent to the IETF list and the RFC-DIST list. 47 Requests to be added to or deleted from the IETF distribution list 48 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 49 added to or deleted from the RFC-DIST distribution list should 50 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 52 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 53 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 54 help: ways_to_get_rfcs. For example: 56 To: rfc-info@RFC-EDITOR.ORG 57 Subject: getting rfcs 59 help: ways_to_get_rfcs 61 Requests for special distribution should be addressed to either the 62 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 63 specifically noted otherwise on the RFC itself, all RFCs are for 64 unlimited distribution.echo 65 Submissions for Requests for Comments should be sent to 66 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 67 Authors, for further information.