A Core MPLS IP VPN Link Broadcast And Virtual Router Discovery
draft-ietf-ppvpn-corevpn-disc-00
| Document | Type |
Expired Internet-Draft
(ppvpn WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Chandrasekar Kathirvelu , Fred Ammann , Karthik Muthukrishnan | ||
| Last updated | 2015-10-14 (Latest revision 2001-07-27) | ||
| 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 (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Scott O. Bradner | ||
| IESG note | |||
| Send notices to | <rick@rhwilder.net> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
An IPVPN consists of many routers, some physically discrete and some virtual, housed in a Provider Edge router. The problem that presents itself is that these virtual routers need to find each other over a virtual topology and they need to send broadcast datagrams as mandated in routing protocols [such as the neighbor discovery datagram and routing updates in OSPF, the routing updates in RIPV2 etc] and user data over this virtual topology. This memo presents an approach for solving these problems.
Authors
Chandrasekar Kathirvelu
Fred Ammann
Karthik Muthukrishnan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)