Using BGP as an Auto-Discovery Mechanism for VR-based Layer-3 VPNs
draft-ietf-l3vpn-bgpvpn-auto-09

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    l3vpn mailing list <l3vpn@ietf.org>, 
    l3vpn chair <l3vpn-chairs@tools.ietf.org>
Subject: Document Action: 'Network based IP VPN Architecture 
         Using Virtual Routers' to Informational RFC 

The IESG has approved the following documents:

- 'Using BGP as an Auto-Discovery Mechanism for VR-based Layer-3 VPNs '
   <draft-ietf-l3vpn-bgpvpn-auto-10.txt> as an Informational RFC
- 'Network based IP VPN Architecture Using Virtual Routers '
   <draft-ietf-l3vpn-vpn-vr-04.txt> as an Informational RFC
- 'Applicability Statement for Virtual Router-based Layer 3 PPVPN 
   Approaches '
   <draft-ietf-l3vpn-as-vr-03.txt> as an Informational RFC

These documents are products of the Layer 3 Virtual Private Networks 
Working Group. 

The IESG contact persons are Mark Townsley and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-vpn-vr-04.txt

.	Technical Summary

This document describes a network-based Virtual Private Network (VPN)
architecture using the virtual router (VR) concept. Multiple VRs can exist
in a single physical device. A VR emulates all the functionality of a
physical router, and therefore inherits all existing mechanisms and tools
for configuration, operation, accounting, and maintenance. Any routing
protocol can be used to distribute VPN reachability information among VRs,
and no VPN-related modifications or extensions are needed to the routing
protocol for achieving VPN reachability. Direct VR-to-VR connectivity may
be configured through layer-2 links or through IP- or MPLS-based tunnels.
Traffic from VRs belonging to different VPNs may be aggregated over a
"backbone VR" network, which greatly simplifies VPN provisioning. This
architecture accommodates various backbone deployment scenarios, both
where the VPN service provider owns the backbone, and where the VPN
service provider obtains backbone service from one or more other service
providers.

    *    Working Group Summary

Active participation in the L3VPN WG on Virtual Routers has not existed
for some time. There is little energy to modify these documents further,
though there is consensus to publish what has been accomplished as
Informational in order to capture the work. 

    *    Protocol Quality

Rather than a specific protocol, these documents describe how one should
implement and use a "Virtual Router" in order to provide a VPN service.
These documents were reviewed by Mark Townsley for the IESG, and Ross
Callon, Ron Bonica and Rick Wilder for the L3VPN WG.

Note to RFC Editor
 
 (Insert note to RFC Editor here)

IESG Note

 (Insert IESG Note here)

IANA Note

 (Insert IANA Note here)