Criteria for Evaluating VPN Implementation Mechanisms
draft-yu-vpn-criteria-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jessica Yu , Lianghwa Jou , Dr. Vijay Srinivasan | ||
| Last updated | 2000-07-13 | ||
| 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
A variety of mechanisms for implementing Virtual Private Network (VPN) utilizing public IP network infrastructure have been proposed in [1,2,3,4] and more may be emerging. This document attempts to identify a set of criteria for evaluating such mechanisms. The criteria could be used by IETF for evaluating a VPN proposal before advancing it to standard track or by VPN Service Providers or enterprise network administrators for choosing which mechanism to use in order to implement their desired VPN networks. The mechanisms this criteria addresses are exclusively for implementing IP based VPNs, as oppose to non-IP based ones, such as Frame Relay based VPNs, etc.
Authors
Jessica Yu
Lianghwa Jou
Dr. Vijay Srinivasan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)