Mobile IP NAT/NAPT/Firewall Traversal
draft-vaarala-mobileip-nat-traversal-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sami Vaarala | ||
| 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
Mobile IP and Network Address Translation (NAT) are incompatible. This draft presents a mechanism of establishing a Mobile IP NAT traversal binding in a backwards compatible manner. The NAT traversal is based on using the Mobile IP Home Agent UDP port for encapsulation of data traffic, thus requiring only a single NAT address mapping. The presented method optimizes round trips required to set up the NAT address mapping, which is a critical measure for handover performance.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)