PPVPN draft-luciani-ppvpn-VPN-discovery-00.txt

["Jim Luciani" <jluciani@CrescentNetworks.com>]

NAME OF I-D:

http://www.ietf.org/internet-drafts/draft-luciani-ppvpn-VPN-discovery-00.txt

SUMMARY

Virtual private networks are becoming a common service offered by
service providers.  There are many technologies over which to implement
a VPN service from IPSec to GRE to MPLS.  One common requirement
of VPN methodologies is the need to discover all of the sites, or at least
all the provider equipment associated with the sites, that are in the VPN.
DNS provides a simple and commonly available means for site discovery
that is independent of any signaling protocol.


RELATED DOCUMENTS

http://www.ietf.org/internet-drafts/draft-ietf-ppvpn-requirements-02.txt
http://www.ietf.org/internet-drafts/draft-ietf-ppvpn-framework-01.txt
http://www.ietf.org/internet-drafts/draft-martini-l2circuit-trans-mpls-07.tx
t
http://www.ietf.org/internet-drafts/draft-lasserre-tls-mpls-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-requirements-01.txt

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

This work fits squarely in the PPVPN box.


WHY IS IT TARGETED AT THIS WG

The following is a quote from the PPVPN WG charter:

"The effort will produce a small number of approaches that are based on
collections of individual technologies that already exist (see below for
specifics). The goal is to foster interoperability among implementations of
a specific approach. Standardization of specific approaches will be gauged
on (I)SP support. Note that it is not a goal of this WG to develop new
protocols or extend existing ones. Rather, the purpose is to document and
identify gaps and shortcomings in individual approaches with regards to the
requirements."

One such gap is auto discovery of VPN information as mentioned in the
requirements and framework drafts.  This is a particularly interesting topic
for medium to large scale VPN deployments.


JUSTIFICATION

This document specifically addresses one of the areas of specific concern to
the WG as mentioned in both the requirements and framework documents.