Provider Provisioned GMPLS-based Virtual Private Cross-Connect Service
draft-ouldbrahim-ppvpn-vpoxc-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hamid H. Ould-Brahim | ||
| Last updated | 2002-12-18 | ||
| 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 describes an Optical Virtual Private Network service (OVPN) called Virtual Private Optical Cross-Connect (VPOXC). A VPOXC is a provider provisioned VPN service part of the customer private network but administered and under the control of the service provider. A VPOXC operates similarly to a physical optical cross-connect except that it allows a wide spectrum of port topology such as hub and spoke, full mesh, and arbitrary topologies. To the VPOXC customer, the service provider network appears as a virtual private optical cross- connect where customer sites are attached to. The VPOXC port topology is defined by the customer, and enforced by the service provider. Customers can signal any optical connectivity according to the port topology implemented by the VPOXC. Client devices operate within the VPOXC space independently from the service provider network operations.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)