IPsec Context Transfer
draft-gopal-seamoby-ipsec-relocate-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ram Gopal | ||
| Last updated | 2001-11-19 | ||
| 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
Seamless offering of security to a Mobile Node (MN) during handovers is crucial for enabling a variety of application services in the Mobile Internet. Handovers also imply that a terminal such as a MN may perform network access authentication in order to obtain connectivity and access to network features such as QoS, header compression etc. Security context associated with several Security Associations (SA) may need to be transferred in order to achieve this. This enables the MN to regain authenticated connectivity and establish new SAs without having to reinitiate time-consuming operations.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)