Issues in IPSec Context Transfer
draft-gopal-seamoby-ipsecctxt-issues-01
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ram Gopal | ||
| Last updated | 2002-02-28 | ||
| 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
The reasons and the motivation for transferring context have been described in [1]. The requirements for a context transfer protocol can be found in [2]. In this document, we describe issues that need to be considered for transferring security (specifically IPsec) related context between access routers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)