PPVPN draft-rosen-rfc2547bis-03.txt

[Eric Rosen <erosen@cisco.com>]

NAME OF I-D:

http://www.ietf.org/internet-drafts/draft-rosen-rfc2547bis-03.txt

SUMMARY

This document specifies  the "RFC2547" style of VPN that is  called out as a
work  item  in the  charter  of  the PPVPN  WG.   The  primary  goal of  VPN
methodology is  to support the  case in which  a client obtains  IP backbone
services  from  a  Service  Provider  or Service  Providers  with  which  it
maintains  contractual relationships.  The  client may  be an  enterprise, a
group of enterprises  which need an extranet, an  Internet Service Provider,
an  application service provider,  another VPN  Service Provider  which uses
this  same method  to offer  VPNs  to clients  of its  own, etc.   

In this VPN methodology, the interface which the service provider offers its
customer is a  layer 3 interface.  Different customers  may have overlapping
address spaces.  Each customer's address  space is disambiguated, and BGP is
used to distribute the customer's routes across the backbone. 

RELATED DOCUMENTS

http://www.ietf.org/internet-drafts/draft-ietf-ppvpn-requirements-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-ppvpn-framework-00.txt
http://www.ietf.org/internet-drafts/draft-rosen-vpns-ospf-bgp-mpls-01.txt
http://www.ietf.org/internet-drafts/draft-rosen-vpn-mcast-00.txt
http://www.ietf.org/internet-drafts/draft-declercq-bgp-ipsec-vpn-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

It addresses the following work item from the PPVPN WG charter:

        The working group is  expected to consider at least three
        specific approaches, including BGP-VPNs (e.g. RFC 2547)

as it is the base spec for the RFC2547 VPNs. 

JUSTIFICATION

The WG should consider this document as it specifically addresses one of the
work items called out in the charter.