[Sip] New I-Ds
"Price, Richard" <richard.price@roke.co.uk> Fri, 20 July 2001 20:43 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA14169 for <sip-archive@odin.ietf.org>; Fri, 20 Jul 2001 16:43:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16388; Fri, 20 Jul 2001 16:19:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16357 for <sip@ns.ietf.org>; Fri, 20 Jul 2001 16:19:02 -0400 (EDT)
Received: from rsys000a.roke.co.uk ([193.118.201.102]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA03110 for <sip@ietf.org>; Fri, 20 Jul 2001 16:18:04 -0400 (EDT)
Received: by RSYS002A with Internet Mail Service (5.5.2653.19) id <P29DQRBN>; Fri, 20 Jul 2001 21:17:42 +0100
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9DEB@RSYS002A>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'sip@ietf.org'" <sip@ietf.org>, "'rohc@cdt.luth.se'" <rohc@cdt.luth.se>
Date: Fri, 20 Jul 2001 21:17:42 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed; boundary="------------InterScan_NT_MIME_Boundary"
Subject: [Sip] New I-Ds
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Hi, New versions of the EPIC drafts have now been submitted to the Internet Drafts editor. In the meantime, the drafts are available from the following URLS: http://www.epic.roke.co.uk/epic/draft-ietf-rohc-tcp-epic-01.txt This draft describes the basic EPIC programmable compression scheme and uses it to generate a ROHC profile for TCP/IP compression. http://www.epic.roke.co.uk/epic/draft-price-rohc-signaling-epic-00.txt This draft describes a "learning" version of EPIC that does not require programming, and uses it to generate a ROHC profile for SIP compression. http://www.epic.roke.co.uk/epic/draft-price-rohc-epic-02.txt This draft describes an optional enhancement to EPIC which boosts the compression efficiency. We hope you have as much fun reading these drafts as we had writing them(!) Best regards, Richard Price ------------------------------------------------------------------------- Richard Price Internet Applications & Mobility Roke Manor Research Ltd. Old Salisbury Lane Romsey, Hants SO51 0ZN, UK. Telephone: +44 1794 833681 E-mail: richard.price@roke.co.uk ------------------------------------------------------------------------- -----Original Message----- From: Price, Richard Sent: Friday, July 20, 2001 2:56 PM To: 'Romeo Zwart' Cc: 'sip@ietf.org'; 'rohc@cdt.luth.se' Subject: RE: [Sip] RE: [rohc] New I-D on compression of SIP Hi, Apologies to members of the SIP mailing list who haven't received my previous emails on the subject. The scheme in question is EPIC (Efficient Protocol-Independent Compression) which is a programmable compression scheme with a very high level of efficiency. There is also a "learning" version of EPIC that does not need to be programmed - we used this to obtain the results for SIP compression. The new EPIC draft is being published today - we will post a copy on our website and provide the link shortly. Regards, Richard P -----Original Message----- From: Romeo Zwart [mailto:Romeo.Zwart@icoe.att.com] Sent: Friday, July 20, 2001 2:11 PM To: Price, Richard Subject: RE: [Sip] RE: [rohc] New I-D on compression of SIP Hi Richard, Thanks for this info, results look impressive. I am a bit confused when you say "our own SIP compression scheme". So that's not SCRIBE or ROGER, is it? Has that scheme been documented anywhere? Romeo At 02:21 PM 7/20/2001, you wrote: >Hi, > >We chose the "Successful Simple SIP to SIP" call flow from >Section 3.1.1 of <draft-ietf-sip-call-flows-05.txt> to >benchmark our own SIP compression scheme. > >Initially the "dictionary" of previously received messages >is empty, but new messages can be compressed relative to all >previously received messages. This illustrates nicely how the >compression ratio goes up with a more comprehensive dictionary. > >The results for our scheme are as follows: > >Message Size Compressed Size Compression Ratio > > 423 152 2.78 > 189 6 31.50 > 205 16 12.81 > 420 28 15.00 > 195 4 48.75 > 214 8 26.75 > 198 2 99.00 > >If anyone has an alternative set of SIP messages, we could provide >compression ratios for these also. > >Regards, > >Richard P
- [Sip] New I-Ds Price, Richard