draft-ietf-grow-large-communities-usage-04.txt		draft-ietf-grow-large-communities-usage-05.txt
	Global Routing Operations J. Snijders		Global Routing Operations J. Snijders
	Internet-Draft J. Heasley		Internet-Draft J. Heasley
	Intended status: Informational NTT		Intended status: Informational NTT
	Expires: September 14, 2017 M. Schmidt		Expires: September 28, 2017 M. Schmidt
	i3D.net		i3D.net
	March 13, 2017		March 27, 2017
	Use of BGP Large Communities		Use of BGP Large Communities
	draft-ietf-grow-large-communities-usage-04		draft-ietf-grow-large-communities-usage-05
	Abstract		Abstract
	Examples and inspiration for operators to use BGP Large Communities.		Examples and inspiration for operators to use BGP Large Communities.
	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 http://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 September 14, 2017.		This Internet-Draft will expire on September 28, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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		(http://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
	skipping to change at page 2, line 14 ¶		skipping to change at page 2, line 14 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. The Design Overview . . . . . . . . . . . . . . . . . . . . . 2		2. The Design Overview . . . . . . . . . . . . . . . . . . . . . 2
	2.1. Informational Communities . . . . . . . . . . . . . . . . 4		2.1. Informational Communities . . . . . . . . . . . . . . . . 4
	2.2. Action Communities . . . . . . . . . . . . . . . . . . . 4		2.2. Action Communities . . . . . . . . . . . . . . . . . . . 4
	3. Examples of Informational Communities . . . . . . . . . . . . 5		3. Examples of Informational Communities . . . . . . . . . . . . 5
	3.1. Location . . . . . . . . . . . . . . . . . . . . . . . . 5		3.1. Location . . . . . . . . . . . . . . . . . . . . . . . . 5
	3.1.1. An ISO 3166-1 Numeric Function . . . . . . . . . . . 5		3.1.1. An ISO 3166-1 Numeric Function . . . . . . . . . . . 5
	3.1.2. A UN M.49 Region Function . . . . . . . . . . . . . . 5		3.1.2. An UN M.49 Region Function . . . . . . . . . . . . . 5
	3.2. Relation Function . . . . . . . . . . . . . . . . . . . . 6		3.2. Relation Function . . . . . . . . . . . . . . . . . . . . 6
	3.3. Combining Informational Communities . . . . . . . . . . . 6		3.3. Combining Informational Communities . . . . . . . . . . . 6
	4. Examples of Action Communities . . . . . . . . . . . . . . . 7		4. Examples of Action Communities . . . . . . . . . . . . . . . 7
	4.1. Selective NO_EXPORT . . . . . . . . . . . . . . . . . . . 7		4.1. Selective NO_EXPORT . . . . . . . . . . . . . . . . . . . 7
	4.1.1. ASN Based Selective NO_EXPORT . . . . . . . . . . . . 7		4.1.1. ASN Based Selective NO_EXPORT . . . . . . . . . . . . 7
	4.1.2. Location Based Selective NO_EXPORT . . . . . . . . . 7		4.1.2. Location Based Selective NO_EXPORT . . . . . . . . . 7
	4.2. Selective AS_PATH Prepending . . . . . . . . . . . . . . 8		4.2. Selective AS_PATH Prepending . . . . . . . . . . . . . . 8
	4.2.1. ASN Based Selective AS_PATH Prepending . . . . . . . 8		4.2.1. ASN Based Selective AS_PATH Prepending . . . . . . . 8
	4.2.2. Location Based Selective AS_PATH Prepending . . . . . 9		4.2.2. Location Based Selective AS_PATH Prepending . . . . . 9
	4.3. Manipulation of the LOCAL_PREF Attribute . . . . . . . . 9		4.3. Manipulation of the LOCAL_PREF Attribute . . . . . . . . 9
	4.3.1. Global Manipulation of LOCAL_PREF . . . . . . . . . . 10		4.3.1. Global Manipulation of LOCAL_PREF . . . . . . . . . . 10
	4.3.2. Location Based Manipulation of LOCAL_PREF . . . . . . 10		4.3.2. Region Based Manipulation of LOCAL_PREF . . . . . . . 10
	4.3.3. Note of Caution for LOCAL_PREF Functions . . . . . . 11		4.3.3. Note of Caution for LOCAL_PREF Functions . . . . . . 11
	4.4. Route Server Prefix Distribution Control . . . . . . . . 11		4.4. Route Server Prefix Distribution Control . . . . . . . . 11
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 12		5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12		7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
	8.1. Normative References . . . . . . . . . . . . . . . . . . 13		8.1. Normative References . . . . . . . . . . . . . . . . . . 13
	8.2. Informative References . . . . . . . . . . . . . . . . . 13		8.2. Informative References . . . . . . . . . . . . . . . . . 13
	8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 13		8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
	skipping to change at page 5, line 39 ¶		skipping to change at page 5, line 39 ¶
	| 64497:1:840 | Route learned in the United States of |		| 64497:1:840 | Route learned in the United States of |
	| | America |		| | America |
	+---------------------+---------------------------------------------+		+---------------------+---------------------------------------------+
	Example documentation for Informational Communities deployed by AS		Example documentation for Informational Communities deployed by AS
	64497 to describe the location where a route was imported using ISO		64497 to describe the location where a route was imported using ISO
	3166-1 numeric identifiers.		3166-1 numeric identifiers.
	Table 2: Information: ISO 3166-1		Table 2: Information: ISO 3166-1
	3.1.2. A UN M.49 Region Function		3.1.2. An UN M.49 Region Function
	AS 64497 could assign a value of 2 to the Function field to designate		AS 64497 could assign a value of 2 to the Function field to designate
	the content of the Parameter field as the M.49 numeric code published		the content of the Parameter field as the M.49 numeric code published
	by the United Nations Statistics Division (UNSD) [4] for macro		by the United Nations Statistics Division (UNSD) [4] for macro
	geographical (continental) regions, geographical sub-regions, or		geographical (continental) regions, geographical sub-regions, or
	selected economic and other groupings.		selected economic and other groupings.
	+---------------------+-------------------------------+		+---------------------+-------------------------------+
	| BGP Large Community | Description |		| BGP Large Community | Description |
	+---------------------+-------------------------------+		+---------------------+-------------------------------+
	skipping to change at page 10, line 42 ¶		skipping to change at page 10, line 42 ¶
	| 64497:12:0 | Assign LOCAL_PREF for a fallback route |		| 64497:12:0 | Assign LOCAL_PREF for a fallback route |
	+---------------------+---------------------------------------------+		+---------------------+---------------------------------------------+
	Example documentation for Action Communities deployed by AS 64497 to		Example documentation for Action Communities deployed by AS 64497 to
	expose a BGP traffic engineering function which allows a BGP neighbor		expose a BGP traffic engineering function which allows a BGP neighbor
	to globally manipulate the LOCAL_PREF attribute for the route within		to globally manipulate the LOCAL_PREF attribute for the route within
	AS 64497.		AS 64497.
	Table 10: Action: Global LOCAL_PREF Manipulation		Table 10: Action: Global LOCAL_PREF Manipulation
	4.3.2. Location Based Manipulation of LOCAL_PREF		4.3.2. Region Based Manipulation of LOCAL_PREF
	AS 64497 could place one of the previously defined Preference		AS 64497 could place one of the previously defined Preference
	Function Identifiers in the Function field and use an ISO 3166-1		Function Identifiers in the Function field and use an UN M.49 numeric
	numeric country identifier in the Parameter field to designate the		region identifier in the Parameter field to designate the
	geographical region within which the non-default LOCAL_PREF		geographical region within which the non-default LOCAL_PREF
	associated with that function identifier should be applied to the		associated with that function identifier should be applied to the
	route. The value of the LOCAL_PREF attribute should not deviate from		route. The value of the LOCAL_PREF attribute should not deviate from
	the default for that route class in any region not specified by one		the default for that route class in any region not specified by one
	or more of these Action Communities.		or more of these Action Communities.
	+--------------+----------------------------------------------------+		+--------------+----------------------------------------------------+
	| BGP Large | Description |		| BGP Large | Description |
	| Community | |		| Community | |
	+--------------+----------------------------------------------------+		+--------------+----------------------------------------------------+
	| 64497:9:528 | Assign LOCAL_PREF for a customer backup route on |		| 64497:9:3 | Assign the LOCAL_PREF value equivalent to a |
	| | BGP speakers in the Netherlands |		| | customer backup class route on BGP routers in the |
	| 64497:10:392 | Assign LOCAL_PREF for a peering route on BGP |		| | North America region |
	| | speakers in Japan |		| 64497:10:5 | Assign the LOCAL_PREF value equivalent to a |
	| 64497:12:840 | Assign LOCAL_PREF for a fallback route on BGP |		| | peering class route on BGP routers in the South |
	| | speakers in United States of America |		| | America region |
			| 64497:12:142 | Assign the LOCAL_PREF value equivalent to a |
			| | fallback class route on BGP routers in the Asia |
			| | region |
	+--------------+----------------------------------------------------+		+--------------+----------------------------------------------------+
	Example documentation for Action Communities deployed by AS 64497 to		Example documentation for Action Communities deployed by AS 64497 to
	expose a BGP traffic engineering function which allows a BGP neighbor		expose a BGP traffic engineering function which allows a BGP neighbor
	to selectively manipulate the LOCAL_PREF attribute within AS 64497 in		to selectively manipulate the LOCAL_PREF attribute within AS 64497 in
	the geographical region specified in the Parameter field.		the geographical region specified in the Parameter field.
	Table 11: Action: Regional LOCAL_PREF Manipulation		Table 11: Action: Regional LOCAL_PREF Manipulation
	4.3.3. Note of Caution for LOCAL_PREF Functions		4.3.3. Note of Caution for LOCAL_PREF Functions
	skipping to change at page 12, line 46 ¶		skipping to change at page 12, line 46 ¶
	Operations and Security [RFC7454].		Operations and Security [RFC7454].
	6. IANA Considerations		6. IANA Considerations
	None.		None.
	7. Acknowledgments		7. Acknowledgments
	The authors would like to gratefully acknowledge the insightful		The authors would like to gratefully acknowledge the insightful
	comments, contributions, critique and support from Adam Chappell,		comments, contributions, critique and support from Adam Chappell,
	Jonathan Stewart, Greg Hankins, Nick Hilliard, Will Hargrave, and		Jonathan Stewart, Greg Hankins, Nick Hilliard, Will Hargrave, Randy
	Randy Bush.		Bush and Shawn Morris.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities		[RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
	Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996,		Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996,
	<http://www.rfc-editor.org/info/rfc1997>.		<http://www.rfc-editor.org/info/rfc1997>.
	[RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations		[RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations
End of changes. 11 change blocks.
	18 lines changed or deleted		21 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/