BGP/MPLS IP Virtual Private Networks (VPNs)
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Internet Architecture Board <email@example.com>, RFC Editor <firstname.lastname@example.org>, l3vpn mailing list <email@example.com>, l3vpn chair <firstname.lastname@example.org> Subject: Protocol Action: 'BGP/MPLS IP VPNs' to Proposed Standard The IESG has approved the following documents: - 'BGP/MPLS IP VPNs ' <draft-ietf-l3vpn-rfc2547bis-04.txt> as a Proposed Standard - 'Applicability Statement for BGP/MPLS IP VPNs ' <draft-ietf-l3vpn-as2547-08.txt> as an Informational RFC These documents are products of the Layer 3 Virtual Private Networks Working Group. The IESG contact persons are Thomas Narten and Ross Callon. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-rfc2547bis-04.txt
Technical Summary This document describes a method by which a Service Provider may use an IP backbone to provide IP VPNs (Virtual Private Networks) for its customers. This method uses a "peer model", in which the customers' edge routers ("CE routers") send their routes to the Service Provider's edge routers ("PE routers"). BGP is then used by the Service Provider to exchange the routes of a particular VPN among the PE routers that are attached to that VPN. This bis done in a way which ensures that routes from different VPNs remain distinct and separate, even if two VPNs have an overlapping address space. The PE routers distribute, to the CE routers in a particular VPN, the routes from other the CE routers in that VPN. The CE routers do not peer with each other, hence there is no "overlay" visible to the VPN's routing algorithm. The term "IP" in "IP VPN" is used to indicate that the PE receives IP datagrams from the CE, examines their IP headers, and routes them accordingly. Working Group Summary There has long been consent in the WG to move this document forward. Indeed, the original charter called from revising RFC 2547 (informational) to reflect experience with it, and put it on the standards track. Protocol Quality This document has been reviewed for the IESG by Thomas Narten. There are numerous implementations in use.