< draft-ietf-rtgwg-backoff-algo-01.txt		draft-ietf-rtgwg-backoff-algo-02.txt >
	Network Working Group B. Decraene		Network Working Group B. Decraene
	Internet-Draft Orange		Internet-Draft Orange
	Intended status: Standards Track S. Litkowski		Intended status: Standards Track S. Litkowski
	Expires: December 21, 2015 Orange Business Service		Expires: June 19, 2016 Orange Business Service
	H. Gredler		H. Gredler
	Juniper Networks, Inc.		Private Contributor
	A. Lindem		A. Lindem
	Cisco Systems
	P. Francois		P. Francois
	IMDEA Networks Institute		Cisco Systems
	June 19, 2015		December 17, 2015
	SPF Back-off algorithm for link state IGPs		SPF Back-off algorithm for link state IGPs
	draft-ietf-rtgwg-backoff-algo-01		draft-ietf-rtgwg-backoff-algo-02
	Abstract		Abstract
	This document defines a standard algorithm to back-off link-state IGP		This document defines a standard algorithm to back-off link-state IGP
	SPF computations.		SPF computations.
	Having one standard algorithm improves interoperability by reducing		Having one standard algorithm improves interoperability by reducing
	the probability and/or duration of transient forwarding loops during		the probability and/or duration of transient forwarding loops during
	the IGP convergence when the IGP reacts to multiple proximate IGP		the IGP convergence when the IGP reacts to multiple proximate IGP
	events.		events.
	skipping to change at page 1, line 49 ¶		skipping to change at page 1, line 48 ¶
	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 December 21, 2015.		This Internet-Draft will expire on June 19, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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 7, line 26 ¶		skipping to change at page 7, line 26 ¶
	10. Acknowledgements		10. Acknowledgements
	We would like to acknowledge Les Ginsberg, Uma Chunduri, and Mike		We would like to acknowledge Les Ginsberg, Uma Chunduri, and Mike
	Shand for the discussions and comments related to this document.		Shand for the discussions and comments related to this document.
	11. References		11. References
	11.1. Normative References		11.1. 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,
			<http://www.rfc-editor.org/info/rfc2119>.
	11.2. Informative References		11.2. Informative References
	[I-D.ietf-rtgwg-spf-uloop-pb-statement]		[I-D.ietf-rtgwg-spf-uloop-pb-statement]
	Litkowski, S., "Link State protocols SPF trigger and delay		Litkowski, S., Decraene, B., and M. Horneffer, "Link State
	algorithm impact on IGP microloops", draft-ietf-rtgwg-spf-		protocols SPF trigger and delay algorithm impact on IGP
	uloop-pb-statement-00 (work in progress), May 2015.		micro-loops", draft-ietf-rtgwg-spf-uloop-pb-statement-02
			(work in progress), December 2015.
	[ISO10589-Second-Edition]		[ISO10589-Second-Edition]
	International Organization for Standardization,		International Organization for Standardization,
	"Intermediate system to Intermediate system intra-domain		"Intermediate system to Intermediate system intra-domain
	routeing information exchange protocol for use in		routeing information exchange protocol for use in
	conjunction with the protocol for providing the		conjunction with the protocol for providing the
	connectionless-mode Network Service (ISO 8473)", ISO/IEC		connectionless-mode Network Service (ISO 8473)", ISO/
	10589:2002, Second Edition, Nov 2002.		IEC 10589:2002, Second Edition, Nov 2002.
	[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.		[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
			DOI 10.17487/RFC2328, April 1998,
			<http://www.rfc-editor.org/info/rfc2328>.
	[RFC5715] Shand, M. and S. Bryant, "A Framework for Loop-Free		[RFC5715] Shand, M. and S. Bryant, "A Framework for Loop-Free
	Convergence", RFC 5715, January 2010.		Convergence", RFC 5715, DOI 10.17487/RFC5715, January
			2010, <http://www.rfc-editor.org/info/rfc5715>.
	[RFC6976] Shand, M., Bryant, S., Previdi, S., Filsfils, C.,		[RFC6976] Shand, M., Bryant, S., Previdi, S., Filsfils, C.,
	Francois, P., and O. Bonaventure, "Framework for Loop-Free		Francois, P., and O. Bonaventure, "Framework for Loop-Free
	Convergence Using the Ordered Forwarding Information Base		Convergence Using the Ordered Forwarding Information Base
	(oFIB) Approach", RFC 6976, July 2013.		(oFIB) Approach", RFC 6976, DOI 10.17487/RFC6976, July
			2013, <http://www.rfc-editor.org/info/rfc6976>.
	Authors' Addresses		Authors' Addresses
	Bruno Decraene		Bruno Decraene
	Orange		Orange
	38 rue du General Leclerc		38 rue du General Leclerc
	Issy Moulineaux cedex 9 92794		Issy Moulineaux cedex 9 92794
	France		France
	Email: bruno.decraene@orange.com		Email: bruno.decraene@orange.com
	Stephane Litkowski		Stephane Litkowski
	Orange Business Service		Orange Business Service
	Email: stephane.litkowski@orange.com		Email: stephane.litkowski@orange.com
	Hannes Gredler		Hannes Gredler
	Juniper Networks, Inc.		Private Contributor
	1194 N. Mathilda Ave.
	Sunnyvale, CA 94089
	US
	Email: hannes@juniper.net		Email: hannes@gredler.at
	Acee Lindem		Acee Lindem
	Cisco Systems		Cisco Systems
	301 Midenhall Way		301 Midenhall Way
	Cary, NC 27513		Cary, NC 27513
	USA		USA
	Email: acee@cisco.com		Email: acee@cisco.com
	Pierre Francois		Pierre Francois
	IMDEA Networks Institute		Cisco Systems
	1194 N. Mathilda Ave.
	Leganes
	ES
	Email: pierre.francois@imdea.org		Email: pifranco@cisco.com
End of changes. 16 change blocks.
	25 lines changed or deleted		25 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/