Subject: Re: [rohc] Protocol Convergence Layer for header compression negotiation

From: "Kavitha KR" <[email-masked]>
Date: Mon, 5 Apr 2004 13:12:04 +0530

Hi Anirudh,

Your proposal of a standard Protocol Convergence Layer (PCL) for ROHC is
interesting.
I have a few comments.

General protocol convergence layer  requirements:
Further extending your ideas, let me try to list down, what are the
requirements of such a layer.
Basically this layer should take care of all the configuration &
negotiation parameters for the compression protocol
and adapt the frames to the link layer below.

Control Plane
(1) Header Compression negotiation with peer ROHC.
(2) Configuring the various (MIB) ROHC protocol parameters. (as in  PDCP
specs)

User Plane
(3) Framing
(4) Segmentation (if not available in link layer)
(5) Buffering to handle packet reordering
(6) Context relocation to handle mobility (PDCP specs)
(7) Detection of packet losses (PDCP seq numbering)

Existing Scenario
As you had also noted, this functionalities are covered somehow in the
existing networks through
proprietary solutions. To consolidate a few,

(1) ROHC o PPP for PPP links.
(2) PDCP protocol supports ROHC in case of UMTS networks,
(3) In case of 3GPP2 CDMA HRU-HRL concepts are applied, where HRL is
      an adaptation layer almost equivalent, to what you have suggested,.
But there
      HRL takes care of user plane requirements, PPP itself takes care of
signalling
      plane requirements.
(4) 802.16 & Bluetooth have their own header compression schemes.
(5) 802.11 is a potential candidate. There was a proposal for ROHC o WEM
      (Wireless Ethernet Medium) suggested & expired.
(6) MANET is yet another potential candidate, and the draft for ROHC o
MANET has
      been recently released.

Questions
(1) Is it really possible to standardize it at this stage?

(2) Has any work been done to compare the efficienies of ROHC protocol and
the
      header compressions followed in 802.16 or bluetooth?
(If ROHC gets to be proved as a better one, on these networks, it could
pave a
way for standardization)

Regards
Kavitha.

This email may contain confidential or privileged information for the
intended recipient(s). If you are not the intended recipient, please do not
use or disseminate the information, notify the sender and delete it from
your system. Thanks

_______________________________________________
Rohc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/rohc