Dynamic Virtual Network Engine (DVNE) Protocol
draft-mrw-dvne-prot-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Margaret Cullen , Padmanabha Nallur | ||
| Last updated | 2010-10-18 | ||
| 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 the Dynamic Virtual Network Engine (DVNE) protocol. The DVNE protocol is a signaling protocol between a virtual network node (the DVNE Client) and a configuration server (the DVNE Mediator). The DVNE protocol is used to authenticate the nodes in a Virtual Network and assist them to setup and release VPN connections directly among themselves. A DVNE clients can be located anywhere in a private or public network, directly connected or behind one or more levels of NAT. The DVNE protocol performs client authentication, peer discovery, virtual network address management, and provides all parameters necessary to enable the clients setup a secure VPN connection. The protocol does not explicitly setup the VPN connection itself. It only enables the clients to be able to directly setup the VPN connection themselves.
Authors
Margaret Cullen
Padmanabha Nallur
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)