PPVPN draft-rosen-vpn-mcast-00.txt

[Eric Rosen <erosen@cisco.com>]

NAME OF I-D:

http://www.ietf.org/internet-drafts/draft-rosen-vpn-mcast-00.txt

SUMMARY

An  enterprise which  uses IP  multicast may  also be  a VPN  customer  of a
service provider, using  an RFC2547 style of VPN.   This draft specifies the
procedures used within  the service provider network in  order to enable the
VPN customers to use IP multicast  in a transparent manner across an RFC2547
VPN 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-rfc2547bis-03.txt
http://www.ietf.org/internet-drafts/draft-rosen-vpns-ospf-bgp-mpls-01.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).

The base specification  (draft-rosen-rfc2547bis-03.txt) does not contain the
procedures needed  for supporting multicast.  Those procedures  are added by
this document.

JUSTIFICATION

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