RObust Header Compression (ROHC): Support for Reordering and Constant IP-ID
draft-kapoor-rohc-rtp-new-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rohit Kapoor | ||
| Last updated | 2005-03-17 | ||
| 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
RObust Header Compression (ROHC), RFC 3095, defines a framework for header compression, along with a number of compression protocols (profiles). This document seeks to add support for two issues to basic RoHC profiles, (a) the ability to handle reordering and (b) avoid extra header overhead when IP-ID is a constant value. The first issue can be supported by making the value of p (which is part of the RoHC interpretation interval) configurable. The second issue is already supported in the IP Profile of RoHC (RFC 3843). The discussion of this IP-ID issue in the current document merely replicates the discussion in RFC 3843 regarding constant IP-ID.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)