[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rohc] SigComp assembler and interpreter ?
- To: Simran Suri <ssuri at ipnetfusion.com>
- Subject: Re: [rohc] SigComp assembler and interpreter ?
- From: Carsten Bormann <cabo at tzi.org>
- Date: Wed, 25 Feb 2004 11:05:43 +0100
- Cc: "Price, Richard" <richard.price at roke.co.uk>, Robert.Sugar at nokia.com, lars-erik.jonsson at ericsson.com, "'zhigang.c.liu at nokia.com'" <zhigang.c.liu at nokia.com>, Pekka.Pessi at nokia.com, Carsten Bormann <cabo at tzi.org>, "West, Mark" <mark.a.west at roke.co.uk>, jan.christoffersson at ericsson.com, rohc at ietf.org, "Surtees, Abigail" <abigail.surtees at roke.co.uk>
- In-reply-to: <403C0F9B.6000109@ipnetfusion.com>
- List-help: <mailto:rohc-request@ietf.org?subject=help>
- List-id: Robust Header Compression <rohc.ietf.org>
- List-post: <mailto:rohc@ietf.org>
- List-subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,<mailto:rohc-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,<mailto:rohc-request@ietf.org?subject=unsubscribe>
- References: <EA943CD30BCB104E9D38F5B5DC2D9A7014615A@rsys004a.roke.co.uk> <403C0F9B.6000109@ipnetfusion.com>
- Sender: rohc-admin at ietf.org
Hi Simran,
2. Has there been any addition to the UDVM assembler/interpreter since
March 2002? Specifically, has the implementation expanded to work with
all the instructions in the UDVM instruction set? Also does anyone
have any programming experience with the UDVM instruction set that can
be shared?
Does "the UDVM assembler/interpreter" refer to my half-baked
implementation of the -05 draft?
I haven't got around to work on this implementation to upgrade it with
respect to the changes we made on the way to RFC3320 and the revised
assembler syntax we agreed on for the implementers guide.
3. I tried out the examples posted by Carsten and these worked
perfectly. However, can anyone tell me how we got the compressed
message in the first place?
A UDVM implementation is not a complete SigComp implementation. In
addition you need:
-- an interface to the higher layer protocol (e.g., SIP)
-- a state manager
-- a portfolio (>= 1) of compression algorithm implementations, and
-- UDVM code to send to the decompressor for each of these.
Clearly, these are significant pieces of work, some of which also have
interesting IPR complications.
Gruesse, Carsten
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc