Layer-3 VPN Import/Export Verification
draft-ietf-l3vpn-vpn-verification-00
| Document | Type |
Expired Internet-Draft
(l3vpn WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Michael H. Behringer | ||
| Last updated | 2005-03-25 (Latest revision 2005-03-24) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
Configuration errors on Provider Edge (PE) routers in Layer-3 VPN networks based on [RFC2547] can lead to security breaches of the connected VPNs. For example, the PE router could be mistakenly configured such that a connected Customer Edge (CE) router belongs to an incorrect VPN. Here we propose a scheme that verifies local and remote routing information received by the PE router before it installs new VPN routes into the Virtual Routing & Forwarding Instance (VRF). The proposed changes affect only the PE routers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)