Context Transfer Considerations for ROHC
draft-kenward-seamoby-ct-rohc-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Gary W. Kenward | ||
| Last updated | 2001-07-12 | ||
| 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
There is an interest in enhancing the performance of handover between access routers through the transfer of forwarding context [2]. To clearly understand the requirements for this transfer, it is useful to examine the requirements of specific feature contexts. This document reviews the requirements for transferring the context associated with RObust Header Compressions (ROHC [3]) in preparation for a handoff of the IP traffic being compressed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)