idnits 2.17.1 draft-ietf-rohc-sigcomp-extended-04.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 3321 5 Title: Signaling Compression (SigComp) - Extended 6 Operations 7 Author(s): H. Hannu, J. Christoffersson, S. Forsgren, 8 K. Leung, Z. Liu, R. Price 9 Status: Informational 10 Date: January 2003 11 Mailbox: hans.hannu@epl.ericsson.se, 12 jan.christoffersson@epl.ericsson.se, 13 StefanForsgren@alvishagglunds.se, 14 kcleung@eee.hku.hk, zhigang.c.liu@nokia.com, 15 richard.price@roke.co.uk 16 Pages: 19 17 Characters: 39433 18 Updates/Obsoletes/SeeAlso: None 20 I-D Tag: draft-ietf-rohc-sigcomp-extended-04.txt 22 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3321.txt 24 This document describes how to implement certain mechanisms in 25 Signaling Compression (SigComp), RFC 3320, which can significantly 26 improve the compression efficiency compared to using simple 27 per-message compression. 29 SigComp uses a Universal Decompressor Virtual Machine (UDVM) for 30 decompression, and the mechanisms described in this document are 31 possible to implement using the UDVM instructions defined in RFC 3320. 33 This document is a product of the Robust Header Compression Working 34 Group of the IETF. 36 This memo provides information for the Internet community. It does 37 not specify an Internet standard of any kind. Distribution of this 38 memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.