PPVPN draft-rosen-ppvpn-ipsec-2547-00.txt

[Eric Rosen <erosen@cisco.com>]

NAME OF I-D

http://www.ietf.org/internet-drafts/draft-rosen-ppvpn-ipsec-2547-00.txt

SUMMARY

The  base  specification  for  RFC2547 VPNs,  i.e.,  draft-rosen-rfc2547bis-
03.txt, specifies  the procedures for  providing a particular style  of VPN,
using MPLS  label switched  paths between Provider  Edge (PE)  routers.  The
base  specification does  not  discuss  other types  of  tunnels between  PE
routers. 

This draft extends  the base specification by specifying  the procedures for
providing the  RFC2547 style  of VPN using  IPsec tunnels (rather  than MPLS
LSPs) between PE routers. 

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-rfc2547bis-03.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

The WG is  chartered with considering the RFC2547 style  of VPN.  This draft
specifies procedures to allow that style  of VPN to run on networks which do
not implement  MPLS in  the core switches,  and/or in environments  in which
increased security is needed.

Thus  the  draft  allows  the  RFC2547  style  of  VPN  to  meet  additional
requirements that are not met by the base specification.

JUSTIFICATION

The WG should consider this document as it extends a style of VPN explicitly
called out in  the charter so that (a)  additional security requirements can
be met,  (b) it  becomes applicable  to a wider  range of  IP-based backbone
environments.