draft-ietf-idr-link-bandwidth-06.txt		draft-ietf-idr-link-bandwidth-07.txt
	Network Working Group P. Mohapatra		Network Working Group P. Mohapatra
	Internet-Draft R. Fernando		Internet-Draft Sproute Networks
	Intended status: Standards Track Cisco Systems		Intended status: Standards Track R. Fernando
	Expires: July 26, 2013 January 22, 2013		Expires: September 6, 2018 Cisco Systems
			March 5, 2018
	BGP Link Bandwidth Extended Community		BGP Link Bandwidth Extended Community
	draft-ietf-idr-link-bandwidth-06.txt		draft-ietf-idr-link-bandwidth-07.txt
	Abstract		Abstract
	This document describes an application of BGP extended communities		This document describes an application of BGP extended communities
	that allows a router to perform unequal cost load balancing.		that allows a router to perform unequal cost load balancing.
	Status of this Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on July 26, 2013.		This Internet-Draft will expire on September 6, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2018 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	This document may contain material from IETF Documents or IETF		This document may contain material from IETF Documents or IETF
	Contributions published or made publicly available before November		Contributions published or made publicly available before November
	10, 2008. The person(s) controlling the copyright in some of this		10, 2008. The person(s) controlling the copyright in some of this
	skipping to change at page 2, line 16 ¶		skipping to change at page 2, line 19 ¶
	modifications of such material outside the IETF Standards Process.		modifications of such material outside the IETF Standards Process.
	Without obtaining an adequate license from the person(s) controlling		Without obtaining an adequate license from the person(s) controlling
	the copyright in such materials, this document may not be modified		the copyright in such materials, this document may not be modified
	outside the IETF Standards Process, and derivative works of it may		outside the IETF Standards Process, and derivative works of it may
	not be created outside the IETF Standards Process, except to format		not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other		it for publication as an RFC or to translate it into languages other
	than English.		than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
	2. Link Bandwidth Extended Community . . . . . . . . . . . . . . . 3		2. Link Bandwidth Extended Community . . . . . . . . . . . . . . 2
	3. Deployment Considerations . . . . . . . . . . . . . . . . . . . 3		3. Deployment Considerations . . . . . . . . . . . . . . . . . . 3
	4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4		4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
	6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5		6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	7. Normative References . . . . . . . . . . . . . . . . . . . . . 5		7. Normative References . . . . . . . . . . . . . . . . . . . . 4
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
	1. Introduction		1. Introduction
	When a BGP speaker receives multiple paths from its internal peers,		When a BGP speaker receives multiple paths from its internal peers,
	it could select more than one path to send traffic to. In doing so,		it could select more than one path to send traffic to. In doing so,
	it might be useful to provide the speaker with information that would		it might be useful to provide the speaker with information that would
	help it distribute the traffic based on the bandwidth of the external		help it distribute the traffic based on the bandwidth of the external
	(DMZ) link. This document suggests that the external link bandwidth		(DMZ) link. This document suggests that the external link bandwidth
	be carried in the network using a new extended community [RFC4360] -		be carried in the network using a new extended community [RFC4360] -
	the link bandwidth extended community.		the link bandwidth extended community.
	1.1. Requirements Language		1.1. Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	2. Link Bandwidth Extended Community		2. Link Bandwidth Extended Community
	skipping to change at page 5, line 22 ¶		skipping to change at page 4, line 41 ¶
	---- -----		---- -----
	non-transitive Link Bandwidth Ext. Community 0x4004		non-transitive Link Bandwidth Ext. Community 0x4004
	6. Security Considerations		6. Security Considerations
	There are no additional security risks introduced by this design.		There are no additional security risks introduced by this design.
	7. Normative References		7. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119,
			DOI 10.17487/RFC2119, March 1997,
			<https://www.rfc-editor.org/info/rfc2119>.
	[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended		[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
	Communities Attribute", RFC 4360, February 2006.		Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
			February 2006, <https://www.rfc-editor.org/info/rfc4360>.
	[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private		[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
	Networks (VPNs)", RFC 4364, February 2006.		Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
			2006, <https://www.rfc-editor.org/info/rfc4364>.
	[RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet		[RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet
	Autonomous System (AS) Number Space", RFC 6793,		Autonomous System (AS) Number Space", RFC 6793,
	December 2012.		DOI 10.17487/RFC6793, December 2012,
			<https://www.rfc-editor.org/info/rfc6793>.
	Authors' Addresses		Authors' Addresses
	Pradosh Mohapatra		Pradosh Mohapatra
	Cisco Systems		Sproute Networks
	170 W. Tasman Drive
	San Jose, CA 95134		Email: pradosh@sproute.com
	USA
	Phone:
	Email: pmohapat@cisco.com
	Rex Fernando		Rex Fernando
	Cisco Systems		Cisco Systems
	170 W. Tasman Drive		170 W. Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	USA		USA
	Phone:
	Email: rex@cisco.com		Email: rex@cisco.com
End of changes. 16 change blocks.
	30 lines changed or deleted		32 lines changed or added
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/