[Sip] Re: [rohc] Requirements for signaling compression

"Hans Hannu" <Hans.Hannu@epl.ericsson.se> Fri, 03 August 2001 09:17 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 FAA10488 for <sip-archive@odin.ietf.org>; Fri, 3 Aug 2001 05:17:09 -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 FAA16163; Fri, 3 Aug 2001 05:00:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA16124 for <sip@ns.ietf.org>; Fri, 3 Aug 2001 04:59:55 -0400 (EDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA09789 for <sip@ietf.org>; Fri, 3 Aug 2001 04:58:51 -0400 (EDT)
Received: from mailserver1.ericsson.se (mailserver1.ericsson.se [136.225.152.91]) by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id f738xrN07236; Fri, 3 Aug 2001 10:59:53 +0200 (MEST)
Received: from e0000865d41e2 (eplpc6014.epl.ericsson.se [150.132.176.14]) by mailserver1.ericsson.se (8.9.3/8.9.3/eri-1.0) with SMTP id KAA06321; Fri, 3 Aug 2001 10:59:51 +0200 (MET DST)
Message-ID: <00b001c11bfa$a7a11410$0eb08496@e0000865d41e2.epl.ericsson.se>
From: Hans Hannu <Hans.Hannu@epl.ericsson.se>
To: "Price, Richard" <richard.price@roke.co.uk>
Cc: rohc@cdt.luth.se, sip@ietf.org
Date: Fri, 03 Aug 2001 10:59:50 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Content-Transfer-Encoding: 7bit
Subject: [Sip] Re: [rohc] Requirements for signaling compression
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
Content-Transfer-Encoding: 7bit

Hi,
Comments inline.

>These requirements seem fine to me - assuming of course that SIP
>compression is performed on a per-hop basis.


The requirements are not only considering SIP compression. The intention is
to provide requirements for a generic solution applicable for compression of
ASCII based signaling protocols, such as SIP/SDP, RTSP etc..

>What about compression between a mobile and a SIP proxy?
I believe that the requirements apply also to this case.

BR
/Hans H

>Is this beyond
>the scope of the ROHC WG?
>
>Regards,
>
>Richard P
>
>-----Original Message-----
>From: Hans Hannu [mailto:Hans.Hannu@epl.ericsson.se]
>Sent: Thursday, August 02, 2001 2:31 PM
>To: rohc
>Subject: [rohc] Requirements for signaling compression
>
>
>Hi,
>
>>From the discussions I see that compression of SIP is the major concern
all
>have, but maybe we should also look at the current version of the
>requirements document as we will discuss requirements in London, not only
>solutions.
>Chapter 3 of,
>http://www.ietf.org/internet-drafts/draft-ietf-rohc-signaling-req-assump-01
 .
>txt states the current requirements. There are most likely requirements
>missing and maybe not all are wanted...
>
>BR
>/Hans H
>
>---
>Mailing list for Robust Header Compression WG
>Archive: http://www.cdt.luth.se/rohc/
>


_______________________________________________
Sip mailing list  http://www.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