RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio n algorithms)
"Price, Richard" <richard.price@roke.co.uk> Wed, 27 February 2002 14:56 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 ESMTP id JAA25626
for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 09:56:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24103;
Wed, 27 Feb 2002 09:53:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24074
for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 09:53:47 -0500 (EST)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA25362
for <rohc@ietf.org>; Wed, 27 Feb 2002 09:53:29 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
id <1S9WN4H0>; Wed, 27 Feb 2002 14:50:14 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FD9@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Miguel A. Garcia'" <Miguel.A.Garcia@ericsson.com>,
"Dr. Carsten Bormann" <cabo@tzi.org>
Cc: zhigang.c.liu@nokia.com, "'Lars-Erik Jonsson (EPL)'"
<Lars-Erik.Jonsson@epl.ericsson.se>, rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
n algorithms)
Date: Wed, 27 Feb 2002 14:50:13 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
boundary="------------InterScan_NT_MIME_Boundary"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Hi Miguel and Carsten, Just got back from holiday - mind if I join in this interesting discussion? I'd be grateful for an answer to the following two questions: Miguel: Is it important from a technical perspective for 3GPP to have an algorithm negotiation mechanism? Section 6.5.6 of the 3GPP requirements draft seems to specify a solution rather than a requirement, in the sense that entities external to SigComp don't know (or care) whether a negotiation mechanism is being employed. Surely what is more important is the technical performance of the solution, measured using some or all of the following: * Call setup time * Processing requirements * Memory requirements * Standardisation effort * Implementation effort * IPR concerns * Future-proofing * Any others I've forgotten? If the ROHC WG can beat the algorithm negotiation approach in terms of all of the above, is it still necessary to provide an algorithm negotiation mechanism within SigComp? Carsten: Do you have any objections to including an algorithm negotiation mechanism, other than the additional standardisation effort? The reason I ask is that SigComp already has the ability to negotiate algorithms - it comes for free as part of the "state claim" mechanism that we provided to support explicit acks. So no additional effort is needed to include algorithm negotiation. Is it OK to provide both the UDVM approach and the algorithm negotiation approach, and leave it to implementers to choose which to adopt? Regards, Richard > -----Original Message----- > From: Miguel A. Garcia [mailto:Miguel.A.Garcia@ericsson.com] > Sent: Wednesday, February 27, 2002 1:53 PM > To: Dr. Carsten Bormann > Cc: zhigang.c.liu@nokia.com; rohc@ietf.org > Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default > decompression algorithms) > > > Hi: > > No, these requirements were discussed prior to the UDVM approach. > > As I said, a new version of this draft will be shortly submitted. > I need to discuss with the rest of the co-authors some better wording > that reflects the latest assumptions in Rohc and 3GPP. > > I will announce the draft in this mailing list as well. > > /Miguel > > "Dr. Carsten Bormann" wrote: > > > > Miguel, > > > > does this list of requirements take into account the UDVM approach? > > It does seem to predate its adoption. > > > > Gruesse, Carsten > > -- > Miguel-Angel Garcia Oy LM Ericsson AB > Jorvas, Finland > mailto:Miguel.A.Garcia@ericsson.com Phone: +358 9 299 3553 > mailto:Miguel.A.Garcia@piuha.net Mobile: +358 40 5140002 > > _______________________________________________ > Rohc mailing list > Rohc@ietf.org > https://www1.ietf.org/mailman/listinfo/rohc >
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Kevan Hobbis
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Lars-Erik Jonsson (EPL)
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Price, Richard
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Lars-Erik Jonsson (EPL)
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Price, Richard
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Dr. Carsten Bormann
- Re: SigComp Requirements (was Re: [rohc] RE: Defa… Miguel A. Garcia
- Re: SigComp Requirements (was Re: [rohc] RE: Defa… Miguel A. Garcia
- Re: SigComp Requirements (was Re: [rohc] RE: Defa… Miguel A. Garcia
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Lars-Erik Jonsson (EPL)
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Price, Richard
- Re: SigComp Requirements (was Re: [rohc] RE: Defa… Miguel A. Garcia
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Dr. Carsten Bormann
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Price, Richard
- RE: SigComp Requirements (was Re: [rohc] RE: Defa… Dr. Carsten Bormann