VPN Discovery Discussions and Options
draft-squire-ppvpn-vpn-discovery-reqts-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Matt Squire | ||
| Last updated | 2001-11-16 | ||
| 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
VPNs are a common service being offered by providers. The PPVPN WG is tasked with defining a limited number of solutions to support the interoperable deployment of VPN services. As part of this effort, a design team was tasked with defining the requirements of PPVPN discovery proposals, to analyze if additional discovery schemes are needed, and to characterize potential solutions to the problem. This draft is the output of that design work. Consensus was not reached on the solution characteristics. However, this draft attempts to capture the discussions and positions of the design team exchanges.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)