[Sip] SigComp with EPIC compression for SIP messages
"Lepine, Jean-Pierre" <jeanpierre.lepine@smisrd.com> Sun, 20 February 2005 09:54 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17833 for <sip-web-archive@ietf.org>; Sun, 20 Feb 2005 04:54:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2o8y-00008I-8m for sip-web-archive@ietf.org; Sun, 20 Feb 2005 05:16:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2mSr-0006F3-5m; Sun, 20 Feb 2005 03:29:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2Chz-0007UQ-Da; Fri, 18 Feb 2005 13:18:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16648; Fri, 18 Feb 2005 13:18:27 -0500 (EST)
Received: from [207.236.152.71] (helo=mtlexch02.mtl.slr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2D3f-0004GC-3Q; Fri, 18 Feb 2005 13:40:56 -0500
Received: by MTLEXCH02 with Internet Mail Service (5.5.2657.72) id <D55ZYR01>; Fri, 18 Feb 2005 13:19:46 -0500
Message-ID: <1CCF22B8BDBD254DA84EC0B05D3DAEEC0268C4CD@mtlexch01.mtl.cmac.com>
From: "Lepine, Jean-Pierre" <jeanpierre.lepine@smisrd.com>
To: rohc@ietf.org, sip@ietf.org, sipping@ietf.org
Date: Fri, 18 Feb 2005 13:17:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
X-Mailman-Approved-At: Sun, 20 Feb 2005 03:29:14 -0500
Subject: [Sip] SigComp with EPIC compression for SIP messages
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0490239705=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> Hi all, I am currently looking at using SigComp with EPIC compression for SIP messages. After reading relevant RFCs and Internet drafts, a few things are not clear to me. First, I understand that EPIC relies on a profile to compress and decompress data. The EPIC reference implementation from Roke Manor Research Ltd provides a profile for RTP. However, I can't find a profile for SIP. Is there one out there? I think I can write one but this would likely be a problem for interoperability since the decompressor MUST use the same profile. One solution would be to download the profile to the other endpoint but this does not look too good to me, partly because I have a concern about the profile size. Furthermore, I don't see how I could instruct the other endpoint to use a downloaded profile (file name and location ?). Any other option? Also, in the SigComp User Guide (draft-ietf-rohc-sigcomp-user-guide-00.txt), section 4.6 is talking about EPIC and SIP but never mentions the need or existence of a profile. Without a profile, how can EPIC be used ? The mentioned section also shows compression results for three algorithms, including EPIC. All algorithms employed a static dictionary and shared compression. Exactly how the EPIC results were obtained is not clear to me, in particular how EPIC was used ? Only the Hierarchical Huffman algorithm ? EPIC used in conjunction with DEFLATE ? Did all three algorithms used the static dictionary described in RFC3485 ? Any help would be really appreciated, Thanks.
_______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] SigComp with EPIC compression for SIP messa… Lepine, Jean-Pierre
- [Sip] RE: [rohc] SigComp with EPIC compression fo… Lars-Erik Jonsson (LU/EAB)
- [Sip] Re: [rohc] SigComp with EPIC compression fo… Pekka Pessi
- [Sip] RE: [rohc] SigComp with EPIC compression fo… Lars-Erik Jonsson (LU/EAB)
- [Sip] Re: [rohc] SigComp with EPIC compression fo… Carsten Bormann
- [Sip] Re: [rohc] SigComp with EPIC compression fo… Carsten Bormann