[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PPVPN draft-ouldbrahim-bgpvpn-auto-01.txt
- To: idsummary <idsummary@subip.ietf.org>
- Subject: PPVPN draft-ouldbrahim-bgpvpn-auto-01.txt
- From: "Hamid Ould-Brahim" <hbrahim@nortelnetworks.com>
- Date: Thu, 10 May 2001 09:54:06 -0400
- Delivery-date: Thu, 10 May 2001 06:55:47 -0700
- Envelope-to: idsummary-data@psg.com
NAME OF I-D:
http://www.ietf.org/internet-drafts/draft-ouldbrahim-bgpvpn-auto-01.txt
SUMMARY
In any Network-Based VPN (NBVPN) scheme, the Provider Edge (PE)
routers attached to a common VPN must exchange certain information
as a prerequisite to establish VPN-specific connectivity. In
[RFC2547-bis], VPN-specific routes are exchanged, along with the
information needed to enable a PE to determine which routes belong
to which VPNs. In [VPN-VR], VR addresses must be exchanged, along
with the information needed to enable the PEs to determine which VRs
are in the same VPN ("membership"), and which of those VRs are to
have VPN connectivity ("topology"). Once the VRs are reachable
through the tunnels, routes ("reachability") are then exchanged by
running existing routing protocol per VPN basis. The purpose of this
draft is to define a common BGP based auto-discovery mechanism used
for both the virtual router [VPN-VR] and [RFC2547-bis]
architectures. Each scheme uses the mechanism to automatically
discover the information needed by that particular scheme.
Interworking scenarios between [RFC2547-bis] and the virtual router
models are also discussed.
RELATED DOCUMENTS
http://www.ietf.org/internet-drafts/draft-rosen-rfc2547bis-03.txt
http://www.ietf.org/internet-drafts/draft-ouldbrahim-vpn-vr-03.txt
WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK
Applications +-------+ +-------+ (new) Hour glass
that use CCAMP: \ | TE-WG | | PPVPN | ... /
\ +-------+ +-------+ /
\ +----------------------+ /
\ | CCAMP | /
\ |-----------+----------| /
/ | C | M --|------ IGP LSA ext
/ | control | measure | \
/ +----------------------+ \
Technologies to / +----+ +----+ +----+ +----+ +----+ \
measure/control:/ |MPLS| |OPT | |RPR | |ATM | | FR |...\
+----+ +----+ +----+ +----+ +----+
It fits in the PPVPN box.
WHY IS IT TARGETED AT THIS WG
This ID describes an auto-discovery mechanism for both RFC2547 and
virtual router schemes which are considered by the PPVPN working group.
As stated in their charter:
"The working group is expected to consider at least three specific
approaches
including BGP-VPNs (e.g. RFC 2547), virtual routers and port-based VPNs
(i.e., where the SP provides a Layer 2 interface, such as Frame Relay or
ATM,
to the VPN customer, while using IP-based mechanisms in the provider
infrastructure to improve scalability and configurability over traditional
L2
networks). Multiple approaches are being developed as each approach has
particular characteristics and differing scope of applicability."
JUSTIFICATION
This work properly highlight the auto-discovery mechanism. Which need
to be explicit for those who are implementing the PPVPN
layer-3 solutions. More than that this work alos addresses interworking
scenarios between RFC2547 and virtual router.
------- End of Forwarded Message