Guidelines for Mobile IP and IPSec VPN Usage
draft-tessier-mobileip-ipsec-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Serge Tessier | ||
| Last updated | 2002-12-02 | ||
| 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 highlights some of the issues that should be considered when IPSec [2] and Mobile IP [3] inter-work with each other. This work finds some applications in the following fields: VPN traversal requirement [4], IPSec Remote access client co-located with a Mobile Node, IPSec security Gateway running in parallel with a Home Agent or a MIP Proxy [5]. The purpose of this document is informational. Rather that strictly indicating how both protocol should take advantages of each other (IPSec running on top of Mobile IP or the other way around), which is a subjective task left to the user and implementation developers of both protocol, it rather proposes some usage guidelines and general considerations regarding the preference of one solution over the other one.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)