PPVPN draft-tsenevir-vpn-discovery-00.txt

[Tissa Senevirathne <tissa@force10networks.com>]

NAME of I-D

http://search.ietf.org/internet-drafts/draft-tsenevir-vpn-discovery-00.txt


SUMMARY:

 This document identifies the scope of VPN discovery and defines the
requirements that need to be satisfied by VPN auto discovery solutions. A
possible 3-Layered VPN auto discovery architecture is presented. 


RELATED DOCUMENTS:

http://search.ietf.org/internet-drafts/draft-tsenevir-8021qospf-00.txt
http://search.ietf.org/internet-drafts/draft-senevirathne-vmi-frame-00.txt
http://search.ietf.org/internet-drafts/draft-tsenevir-l2-req-00.txt
http://search.ietf.org/internet-drafts/draft-rosen-ppvpn-l2vpn-00.txt
http://search.ietf.org/internet-drafts/draft-tsenevir-bgp-l2vpn-01.txt

WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK

PPVPN

WHY IS IT TARGETED AT THIS WG

 PPVPN WG charter specify provisioning of VPN services. Auto discovery of
VPN is a key aspect for large scale VPN deployments and hence within the
broader scope of PPVPN WG charter

JUSTIFICATION

VPN services are gaining popularity in services infrastructure. Without the
auto discovery VPN providers are required to configure VPN service points
manually. In large-scale deployments such manual configurations are
administratively prohibitive. Methods presented here helps Larger scale VPN
deployments that span multiple AS boundaries.