NAT traversal for LISP
draft-ermagan-lisp-nat-traversal-19
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vina Ermagan , Dino Farinacci , Darrel Lewis , Fabio Maino , Marc Portoles-Comeras , Jesper Skriver , Chris White , Albert López Brescó , Albert Cabellos-Aparicio | ||
| Last updated | 2021-11-08 (Latest revision 2021-05-07) | ||
| 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 describes a mechanism for IPv4 NAT traversal for LISP tunnel routers (xTR) and LISP Mobile Nodes (LISP-MN) behind a NAT device. A LISP device both detects the NAT and initializes its state. Forwarding to the LISP device through a NAT is enabled by the LISP Re-encapsulating Tunnel Router (RTR) network element, which acts as an anchor point in the data plane, forwarding traffic from unmodified LISP devices through the NAT.
Authors
Vina Ermagan
Dino Farinacci
Darrel Lewis
Fabio Maino
Marc Portoles-Comeras
Jesper Skriver
Chris White
Albert López Brescó
Albert Cabellos-Aparicio
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)