From - Tue Jun 25 09:22:05 2002 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) by magnum.cs.columbia.edu (8.11.6/8.9.3) with ESMTP id g5OMNJp23514; Mon, 24 Jun 2002 18:23:19 -0400 Received: from loki.ietf.org (loki.ietf.org [132.151.1.177]) by cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g5OMMixc001511; Mon, 24 Jun 2002 18:22:44 -0400 (EDT) Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id RAA27528 for ietf-123-outbound.06@ietf.org; Mon, 24 Jun 2002 17:45:01 -0400 (EDT) Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id RAA27505 for ; Mon, 24 Jun 2002 17:44:13 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03054; Mon, 24 Jun 2002 17:43:31 -0400 (EDT) Message-Id: <200206242143.RAA03054@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board , rohc@ietf.org From: The IESG Subject: Protocol Action: Signaling Compression to Proposed Standard Date: Mon, 24 Jun 2002 17:43:31 -0400 Sender: scoya@cnri.reston.va.us The IESG has approved the Internet-Draft 'Signaling Compression' as a Proposed Standard. In the same action, the following Internet-Drafts were approved for publication as Informational RFCs: o SigComp - Extended Operations o Signaling Compression Requirements & Assumptions These documents are the product of the Robust Header Compression Working Group. The IESG contact persons are Allison Mankin and Scott Bradner. Technical Summary Many application protocols used for multimedia communications are text-based and have not been optimized in terms of size. For example, typical SIP messages range from a few hundred bytes up to two thousand bytes or more. With the planned usage of these protocols in wireless handsets as part of 2.5G and 3G cellular networks, the large message size is problematic, especially because of transmisssion delay concerns. Taking into account retransmissions, and the multiplicity of messages that are required in some flows, call setup and feature invocation are adversely affected. SigComp provides a means to eliminate this problem by offering robust, lossless compression of application messages. The Sigcomp document presents the architecture and pre-requisites of the SigComp solution, the format of the SigComp message and the Universal Decompressor Virtual Machine (UDVM) that provides decompression functionality. Arbitary applications ar supported by transferring a well-formed UDVM for the use of a flow or flows from the sender to the receiver. SigComp is offered to applications as a layer between the application and an underlying transport. The service provides is that of the underlying transport plus compression. SigComp supports a wide range of transports including TCP, UDP and SCTP [RFC-2960]. The two informational drafts provide background to the design (requirements) and a set of optimization techniques for UDVM construction (extended operations) that may either be adopted by implementations or used as a model for optimizations to be added in future. Working Group Summary The working group had strong agreement to advance these drafts. Protocol Quality No problems were found during IETF Last Call. There have been two independent prototyping developments of sigcomp, with resuls of both the protocol and interoperation tests being fed into the working group effort before last call. Allison Mankin reviewed the documents for the IESG.