draft-ietf-grow-bgp-gshut-05.txt		draft-ietf-grow-bgp-gshut-06.txt
	Network Working Group Pierre Francois		Network Working Group Pierre Francois
	Internet-Draft Institute IMDEA Networks		Internet-Draft Institute IMDEA Networks
	Intended status: Informational Bruno Decraene		Intended status: Informational Bruno Decraene
	Expires: August 1, 2014 Orange		Expires: February 15, 2015 Orange
	Cristel Pelsser		Cristel Pelsser
	Internet Initiative Japan		Internet Initiative Japan
	Keyur Patel		Keyur Patel
	Clarence Filsfils		Clarence Filsfils
	Cisco Systems		Cisco Systems
	January 28, 2014		August 14, 2014
	Graceful BGP session shutdown		Graceful BGP session shutdown
	draft-ietf-grow-bgp-gshut-05		draft-ietf-grow-bgp-gshut-06
	Abstract		Abstract
	This draft describes operational procedures aimed at reducing the		This draft describes operational procedures aimed at reducing the
	amount of traffic lost during planned maintenances of routers or		amount of traffic lost during planned maintenances of routers or
	links, involving the shutdown of BGP peering sessions.		links, involving the shutdown of BGP peering sessions.
	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
	skipping to change at page 1, line 38		skipping to change at page 1, line 38
	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 August 1, 2014.		This Internet-Draft will expire on February 15, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 3, line 25		skipping to change at page 3, line 25
	4.2.3. Router g-shut . . . . . . . . . . . . . . . . . . . . 7		4.2.3. Router g-shut . . . . . . . . . . . . . . . . . . . . 7
	5. Forwarding modes and transient forwarding loops during		5. Forwarding modes and transient forwarding loops during
	convergence . . . . . . . . . . . . . . . . . . . . . . . . . 8		convergence . . . . . . . . . . . . . . . . . . . . . . . . . 8
	6. Link Up cases . . . . . . . . . . . . . . . . . . . . . . . . 8		6. Link Up cases . . . . . . . . . . . . . . . . . . . . . . . . 8
	6.1. Unreachability local to the ASBR . . . . . . . . . . . . . 8		6.1. Unreachability local to the ASBR . . . . . . . . . . . . . 8
	6.2. iBGP convergence . . . . . . . . . . . . . . . . . . . . . 9		6.2. iBGP convergence . . . . . . . . . . . . . . . . . . . . . 9
	7. IANA assigned g-shut BGP community . . . . . . . . . . . . . . 9		7. IANA assigned g-shut BGP community . . . . . . . . . . . . . . 9
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 10		8. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10		9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10		10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
			10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
			10.2. Informative References . . . . . . . . . . . . . . . . . . 11
	Appendix A. Alternative techniques with limited applicability . . 11		Appendix A. Alternative techniques with limited applicability . . 11
	A.1. Multi Exit Discriminator tweaking . . . . . . . . . . . . 11		A.1. Multi Exit Discriminator tweaking . . . . . . . . . . . . 11
	A.2. IGP distance Poisoning . . . . . . . . . . . . . . . . . . 11		A.2. IGP distance Poisoning . . . . . . . . . . . . . . . . . . 11
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
	1. Introduction		1. Introduction
	Routing changes in BGP can be caused by planned, maintenance		Routing changes in BGP can be caused by planned, maintenance
	operations. This document discusses operational procedures to be		operations. This document discusses operational procedures to be
	applied in order to reduce or eliminate losses of packets during the		applied in order to reduce or eliminate losses of packets during the
	maintenance. These losses come from the transient lack of		maintenance. These losses come from the transient lack of
	reachability during the BGP convergence following the shutdown of an		reachability during the BGP convergence following the shutdown of an
	eBGP peering session between two Autonomous System Border Routers		eBGP peering session between two Autonomous System Border Routers
	(ASBR).		(ASBR).
	skipping to change at page 10, line 36		skipping to change at page 10, line 36
	transitive extended community do not need to do this as the community		transitive extended community do not need to do this as the community
	is non transitive and hence cannot be used by remote ASes.		is non transitive and hence cannot be used by remote ASes.
	9. Acknowledgments		9. Acknowledgments
	The authors wish to thank Olivier Bonaventure and Pradosh Mohapatra		The authors wish to thank Olivier Bonaventure and Pradosh Mohapatra
	for their useful comments on this work.		for their useful comments on this work.
	10. References		10. References
	[AddPath] D. Walton, E. Chen, A. Retana, and J. Scudder,		10.1. Normative References
	"Advertisement of Multiple Paths in BGP",
	draft-ietf-idr-add-paths-09.txt (work in progress).
	[BestExternal]
	Marques, P., Fernando, R., Chen, E., Mohapatra, P., and H.
	Gredler, "Advertisement of the best-external route to
	IBGP", draft-ietf-idr-best-external-05.txt.
	[REQS] Decraene, B., Francois, P., Pelsser, C., Ahmad, Z.,		[REQS] Decraene, B., Francois, P., Pelsser, C., Ahmad, Z.,
	Armengol, A., and T. Takeda, "Requirements for the		Armengol, A., and T. Takeda, "Requirements for the
	graceful shutdown of BGP sessions", RFC 6198.		graceful shutdown of BGP sessions", RFC 6198.
	[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
	Communities Attribute", RFC 4360, February 2006.
	[EXT_POOL]		[EXT_POOL]
	Decraene, B. and P. Francois, "Assigned BGP extended		Decraene, B. and P. Francois, "Assigned BGP extended
	communities",		communities",
	draft-ietf-idr-reserved-extended-communities-06.		draft-ietf-idr-reserved-extended-communities-06.
			[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
			Communities Attribute", RFC 4360, February 2006.
	[BGPWKC] "http://www.iana.org/assignments/		[BGPWKC] "http://www.iana.org/assignments/
	bgp-well-known-communities".		bgp-well-known-communities".
	[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, March 1997.
			10.2. Informative References
			[AddPath] D. Walton, E. Chen, A. Retana, and J. Scudder,
			"Advertisement of Multiple Paths in BGP",
			draft-ietf-idr-add-paths-09.txt (work in progress).
			[BestExternal]
			Marques, P., Fernando, R., Chen, E., Mohapatra, P., and H.
			Gredler, "Advertisement of the best-external route to
			IBGP", draft-ietf-idr-best-external-05.txt.
	Appendix A. Alternative techniques with limited applicability		Appendix A. Alternative techniques with limited applicability
	A few alternative techniques have been considered to provide g-shut		A few alternative techniques have been considered to provide g-shut
	capabilities but have been rejected due to their limited		capabilities but have been rejected due to their limited
	applicability. This section describe them for possible reference.		applicability. This section describe them for possible reference.
	A.1. Multi Exit Discriminator tweaking		A.1. Multi Exit Discriminator tweaking
	The MED attribute of the paths to be avoided can be increased so as		The MED attribute of the paths to be avoided can be increased so as
	to force the routers in the neighboring AS to select other paths.		to force the routers in the neighboring AS to select other paths.
End of changes. 10 change blocks.
	16 lines changed or deleted		22 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/