BGP based Auto-Discovery mechanism for Optical VPNs
draft-fedyk-bgpvpon-auto-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Don Fedyk | ||
| Last updated | 2001-02-27 | ||
| 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
Consider a service provider network that offers Optical Virtual Private Network (OVPN) service. An important goal in the OVPN service is the ability to support what is known as _single end provisioning_, where addition of a new port to a given OVPN would involve configuration/provisioning changes only on the devices connected to that port. Another important goal in the OVPN service is the ability to establish/terminate an optical connection between a pair of (existing) ports within an OVPN without involving configuration/provisioning changes in any of the provider devices. In this document we describe a set of mechanisms that accomplishes these goals.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)