Flexible Dynamic Mesh VPN
draft-detienne-dmvpn-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Frederic Detienne , Manish Kumar, Mike Sullenberger | ||
Last updated | 2014-06-23 (Latest revision 2013-12-20) | ||
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 purpose of a Dynamic Mesh VPN (DMVPN) is to allow IPsec/IKE Security Gateways administrators to configure the devices in a partial mesh (often a simple star topology called Hub-Spokes) and let the Security Gateways establish direct protected tunnels called Shortcut Tunnels. These Shortcut Tunnels are dynamically created when traffic flows and are protected by IPsec. To achieve this goal, this document extends NHRP ([RFC2332]) into a routing policy feed and integrates GRE tunneling with IKEv2 and IPsec to provide the necessary cryptographic security.
Authors
Frederic Detienne
Manish Kumar
Mike Sullenberger
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)