Customer Managed Gateway Selection for RFC2547 VPN(s)
draft-uttaro-mult-gws-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Jim Uttaro | ||
| Last updated | 2002-09-18 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-uttaro-mult-gws-00.txt
Abstract
This document presents an application of the BGP community attribute in simplifying the implementation and configuration of routing policies between two or more VPN service providers. It is assumed that RFC2547 has been implemented to provide the VPN service although this is not a requirement of this application It shows how use of the community attribute along with the setting of a BGP metric can be used by customers to select the best gateway between one or more VPN service providers. This technique simplifies configuration and management at the provider level, and gives the customer the ability to control its own routing policy with respect to the selection of gateways between service providers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)