[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PPVPN draft-rosen-vpn-mcast-01.txt
- To: idsummary@subip.ietf.org
- Subject: PPVPN draft-rosen-vpn-mcast-01.txt
- From: Eric Rosen <erosen@cisco.com>
- Date: Wed, 11 Jul 2001 12:39:28 -0400
- Reply-to: erosen@cisco.com
- User-Agent: EMH/1.10.0 WEMI/1.13.2 (Mochimune) FLIM/1.12.1(Nishinokyō) Emacs/20.6 (sparc-sun-solaris2.5.1)MULE/4.0 (HANANOEN)
NAME OF I-D:
http://www.ietf.org/internet-drafts/draft-rosen-vpn-mcast-01.txt
SUMMARY
The base specification for RFC2547 VPNs, i.e., draft-rosen-rfc2547bis-
03.txt, does not specify the procedures necessary for a service provider to
support multicast within the VPNs that it provides to its customers. That
specification is contained in this document, along with discussion of some
alternative procedures.
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-02.txt
http://www.ietf.org/internet-drafts/draft-rosen-ppvpn-ipsec-2547-00.txt
http://www.ietf.org/internet-drafts/draft-farinacci-mpls-multicast-03.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).
It extends the base specification for RFC2547 VPNs by adding procedures
to enable multicasts used within the VPN to traverse the backbone.
JUSTIFICATION
The WG should consider this document as it specifically addresses one of the
work items called out in the charter.