Requirements for Multi Autonomous System VPN Services
draft-halstead-guichard-mavs-requirements-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Halstead | ||
| Last updated | 2006-05-08 | ||
| 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 complements [RFC-4031] and defines requirements that are specific to the delivery of BGP/MPLS-based [RFC-4364] VPN services across multiple administrative domains. These requirements are independent of underlying technologies or the number of Autonomous Systems such VPNs may span. It lists the requirements of the different parties that are involved in the administration of these Autonomous Systems and may therefore be involved in the delivery of the VPN service offerings.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)