Functional requirements for the deployment of an IP VPN service offering
draft-jacquenet-ip-vpn-needs-00

Document Type Expired Internet-Draft (individual)
Author Christian Jacquenet 
Last updated 2000-07-20
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-jacquenet-ip-vpn-needs-00.txt

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

Christian Jacquenet (christian.jacquenet@cnet.francetelecom.fr)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)