Auto Discovery VPN Problem Statement and Requirements
draft-ietf-ipsecme-p2p-vpn-problem-02
| Document | Type | Replaced Internet-Draft (ipsecme WG) | |
|---|---|---|---|
| Last updated | 2012-10-15 (latest revision 2012-07-09) | ||
| Replaces | draft-nir-ipsecme-p2p | ||
| Replaced by | RFC 7018 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-ipsecme-ad-vpn-problem | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-ipsecme-p2p-vpn-problem-02.txt
Abstract
This document describes the problem of enabling a large number of systems to communicate directly using IPsec to protect the traffic between them. It them expands on the requirements, for such a solution. Manual configuration of all possible tunnels is too cumbersome in many such cases. In other cases the IP address of end points change or the end points may be behind NAT gateways, making static configuration impossible. The Auto Discovery VPN solution is chartered to address these requirements.
Authors
Steve Hanna
(shanna@juniper.net)
Vishwas Manral
(vishwas.manral@hp.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)