Functional requirements for the deployment of an IP VPN service offering
draft-jacquenet-ip-vpn-needs-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Christian Jacquenet | ||
Last updated | 2000-07-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
This document aims at identifying the requirements which should be taken into consideration by a service provider, when considering the deployment of an IP VPN service offering. From this perspective, this document does not specify any technical means which could be used to deploy an IP VPN service offering, unlike the [VPN-FRAME] document. This document tries to express a service provider perspective, according to its own experience of IP-based service offerings, and to its own perception of the (constantly) evolving needs of the customers of such services. To some extent, this document can be viewed as a complementary taxonomy effort of the [TAXONOMY] draft.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)