ROHC (Robust Header Compression) in NEMO network
draft-minaburo-rohc-nemo-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ana Minaburo | ||
| Last updated | 2005-07-07 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines the use of ROHC header compression mechanisms for the NEMO Basic Support protocol [7]. The idea is to use both NEMO and ROHC as they have been defined. In the NEMO Basic Support protocol, the tunneling between the Mobile Router (MR) and the Home Agent (HA) of the MR is done over different access technologies. Some of these technologies are wireless (e.g. Wireless LAN, 3G or PPP) and have scarce resources by nature, the use of ROHC compression can be useful to reduce the bandwidth consumption.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)