< draft-ouldbrahim-bgpvpn-auto-00.txt		draft-ouldbrahim-bgpvpn-auto-01.txt >
	Network Working Group Hamid Ould-Brahim		Provider Provisioned VPN WG Hamid Ould-Brahim
	Internet Draft Bryan Gleeson		Internet Draft Bryan Gleeson
	draft-ouldbrahim-bgpvpn-auto-00.txt Peter Ashwood-Smith		draft-ouldbrahim-bgpvpn-auto-01.txt Peter Ashwood-Smith
	Expiration Date: May 2001 Nortel Networks		Expiration Date: September 2001 Nortel Networks
	Eric C. Rosen		Eric C. Rosen
	Yakov Rekhter
	Cisco Systems		Cisco Systems
	November 2000		Yakov Rekhter
			Juniper Networks
			Luyuan Fang
			AT&T
			Jeremy De Clercq
			Alcatel
			March 2001
	Using BGP as an Auto-Discovery		Using BGP as an Auto-Discovery
	Mechanism for Network-based VPNs		Mechanism for Network-based VPNs
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026 [RFC-2026].		all provisions of Section 10 of RFC2026 [RFC-2026].
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	skipping to change at page 4, line 40 ¶		skipping to change at page 4, line 44 ¶
	For the virtual router model, the VPN-ID is carried within the route		For the virtual router model, the VPN-ID is carried within the route
	distinguisher (RD) field. In order to hold the 7-bytes VPN-ID, the		distinguisher (RD) field. In order to hold the 7-bytes VPN-ID, the
	first byte of RD type field is used to indicate the existence of the		first byte of RD type field is used to indicate the existence of the
	VPN-ID format. A value of 0x80 in the first byte of RD's type field		VPN-ID format. A value of 0x80 in the first byte of RD's type field
	indicates that the RD field is carrying the VPN-ID format. In this		indicates that the RD field is carrying the VPN-ID format. In this
	case, the type field range 0x8000-0x80ff will be reserved for the		case, the type field range 0x8000-0x80ff will be reserved for the
	virtual router case.		virtual router case.
	5.1.2 VPN-ID Extended Community		5.1.2 VPN-ID Extended Community
	A new extended community attribute is used to carry the VPN-ID. The		A new extended community is used to carry the VPN-ID. The first byte
	first byte of the extended community attribute will be used to		of the VPN-ID extended community will be used to indicate the
	indicate the presence of the VPN-ID format. A value of 0x20		presence of the VPN-ID format. A value of 0x20 indicates that the
	indicates that the remaining 7 bytes following the first byte of the		remaining 7 bytes following the first byte of the type field holds a
	type field holds a VPN-ID value. In this case an extended community		VPN-ID value. In this case an extended community with type field in
	with type field in the range of 0x2000-0x20ff will be used		the range of 0x2000-0x20ff will be used exclusively for the virtual
	exclusively for the virtual router case. The BGP UPDATE message will		router case. The BGP UPDATE message will carry information for a
	carry information for a single VPN (when used with a VPN-ID extended		single VPN (when used with a VPN-ID extended community). The use of
	community). The use of VPN-ID extended community allows a PE to		VPN-ID extended community allows a PE to perform route filtering per
	perform route filtering per VPN basis.		VPN basis.
	5.2 VPN Topology Information		5.2 VPN Topology Information
	A new extended community attribute is used to indicate different VPN		A new extended community is used to indicate different VPN topology
	topology values. A type 0x0020 represents the VPN topology field.		values. A type 0x0020 represents the VPN topology field. The first
	The first two bytes (of the remaining 6 bytes) are reserved. The		two bytes (of the remaining 6 bytes) are reserved. The actual
	actual topology values are carried within the remaining four bytes.		topology values are carried within the remaining four bytes. The
	The following topology values are defined:		following topology values are defined:
	Value Topology Type		Value Topology Type
	1 "Hub"		1 "Hub"
	2 "Spoke"		2 "Spoke"
	3 "Mesh"		3 "Mesh"
	Arbitrary values can also be used to allow specific topologies to be		Arbitrary values can also be used to allow specific topologies to be
	constructed. VPN connectivity between two VRs within the same VPN is		constructed. VPN connectivity between two VRs within the same VPN is
	achieved if and only if at least one of them is a hub (the other is		achieved if and only if at least one of them is a hub (the other is
	skipping to change at page 6, line 32 ¶		skipping to change at page 6, line 34 ¶
	A PE implementing only [RFC2547-bis] will not import routes from a		A PE implementing only [RFC2547-bis] will not import routes from a
	BGP UPDATE message containing the VPN-ID extended community. On the		BGP UPDATE message containing the VPN-ID extended community. On the
	other hand, a PE implementing the virtual router architecture will		other hand, a PE implementing the virtual router architecture will
	not import routes from a BGP UPDATE message containing the route		not import routes from a BGP UPDATE message containing the route
	target extended community attribute.		target extended community attribute.
	The granularity at which the information is either [RFC2547-bis]		The granularity at which the information is either [RFC2547-bis]
	related or VR-related is per BGP UPDATE message. Different SAFI		related or VR-related is per BGP UPDATE message. Different SAFI
	numbers are used to indicate that the message carried in BGP		numbers are used to indicate that the message carried in BGP
	multiprotocol extension attributes is to be handled by the VR or		multiprotocol extension attributes is to be handled by the VR or
	[RFC2547-bis] architectures. SAFI number of 128 is used for		[RFC2547-bis] architectures. SAFI number of 128 is used for [RFC2547-
	[RFC2547-bis] related format. A value of 129 for the SAFI number is		bis] related format. A value of 129 for the SAFI number is for the
	for the virtual router (where the NLRI are carrying a labeled		virtual router (where the NLRI are carrying a labeled prefixes), and
	prefixes), and a SAFI value of 140 is for non labeled addresses.		a SAFI value of 140 is for non labeled addresses.
	7. Use of BGP Capability Advertisement		7. Use of BGP Capability Advertisement
	A BGP speaker that uses VPN information as described in this		A BGP speaker that uses VPN information as described in this
	document with multiprotocol extensions should use the Capability		document with multiprotocol extensions should use the Capability
	Advertisement procedures to determine whether the speaker could use		Advertisement procedures to determine whether the speaker could use
	Multiprotocol Extensions with a particular peer. The Capability Code		Multiprotocol Extensions with a particular peer. The Capability Code
	field is set to 1 (which indicates Multiprotocol Extensions		field is set to 1 (which indicates Multiprotocol Extensions
	capabilities).		capabilities).
	skipping to change at page 8, line 36 ¶		skipping to change at page 8, line 39 ¶
	Phone: +1 613 763 4534		Phone: +1 613 763 4534
	Email: petera@nortelnetworks.com		Email: petera@nortelnetworks.com
	Eric C. Rosen		Eric C. Rosen
	Cisco Systems, Inc.		Cisco Systems, Inc.
	250 Apollo drive		250 Apollo drive
	Chelmsford, MA, 01824		Chelmsford, MA, 01824
	E-mail: erosen@cisco.com		E-mail: erosen@cisco.com
	Yakov Rekhter		Yakov Rekhter
	Cisco Systems		Juniper Networks
	170 Tasman Drive		1194 N. Mathilda Avenue
	San Jose, CA, 95134		Sunnyvale, CA 94089
	Email: yakov@cisco.com		Email: yakov@juniper.net
			Luyuan Fang
			AT&T
			200 Laurel Avenue
			Middletown, NJ 07748
			Email: Luyuanfang@att.com
			draft-ouldbrahim-bgpvpn-auto-01.txt September 2001
			Phone: +1 (732) 420 1920
			Jeremy De Clercq
			Alcatel
			Francis Wellesplein 1
			B-2018 Antwerpen, Belgium
			Phone: +32 3 240 47 52
			Email: jeremy.de_clercq@alcatel.be
			draft-ouldbrahim-bgpvpn-auto-01.txt September 2001
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (date). All Rights Reserved. This		Copyright (C) The Internet Society (date). All Rights Reserved. This
	document and translations of it may be copied and furnished to		document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph		kind, provided that the above copyright notice and this paragraph
	are included on all such copies and derivative works. However, this		are included on all such copies and derivative works. However, this
End of changes. 8 change blocks.
	28 lines changed or deleted		56 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/