< draft-ietf-lsr-dynamic-flooding-05.txt		draft-ietf-lsr-dynamic-flooding-06.txt >
	Internet Engineering Task Force T. Li, Ed.		Internet Engineering Task Force T. Li, Ed.
	Internet-Draft Arista Networks		Internet-Draft Arista Networks
	Intended status: Standards Track P. Psenak, Ed.		Intended status: Standards Track P. Psenak, Ed.
	Expires: November 18, 2020 L. Ginsberg		Expires: November 28, 2020 L. Ginsberg
	Cisco Systems, Inc.		Cisco Systems, Inc.
	H. Chen		H. Chen
	Futurewei		Futurewei
	T. Przygienda		T. Przygienda
	Juniper Networks, Inc.		Juniper Networks, Inc.
	D. Cooper		D. Cooper
	CenturyLink		CenturyLink
	L. Jalil		L. Jalil
	Verizon		Verizon
	S. Dontula		S. Dontula
	ATT		ATT
	May 17, 2020		May 27, 2020
	Dynamic Flooding on Dense Graphs		Dynamic Flooding on Dense Graphs
	draft-ietf-lsr-dynamic-flooding-05		draft-ietf-lsr-dynamic-flooding-06
	Abstract		Abstract
	Routing with link state protocols in dense network topologies can		Routing with link state protocols in dense network topologies can
	result in sub-optimal convergence times due to the overhead		result in sub-optimal convergence times due to the overhead
	associated with flooding. This can be addressed by decreasing the		associated with flooding. This can be addressed by decreasing the
	flooding topology so that it is less dense.		flooding topology so that it is less dense.
	This document discusses the problem in some depth and an		This document discusses the problem in some depth and an
	architectural solution. Specific protocol changes for IS-IS, OSPFv2,		architectural solution. Specific protocol changes for IS-IS, OSPFv2,
	skipping to change at page 1, line 49 ¶		skipping to change at page 1, line 49 ¶
	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 https://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 November 18, 2020.		This Internet-Draft will expire on November 28, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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
	(https://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
	skipping to change at page 42, line 28 ¶		skipping to change at page 42, line 28 ¶
	IANA is requested to set up a registry called "IGP Algorithm Type For		IANA is requested to set up a registry called "IGP Algorithm Type For
	Computing Flooding Topology" under an existing "Interior Gateway		Computing Flooding Topology" under an existing "Interior Gateway
	Protocol (IGP) Parameters" IANA registries.		Protocol (IGP) Parameters" IANA registries.
	Values in this registry come from the range 0-255.		Values in this registry come from the range 0-255.
	The initial values in the IGP Algorithm Type For Computing Flooding		The initial values in the IGP Algorithm Type For Computing Flooding
	Topology registry are:		Topology registry are:
	0: Reserved for centralized mode. Individual values are are to be		0: Reserved for centralized mode.
	assigned according to the "Specification Required" policy defined
	in [RFC8126]
	1-127: Available for standards action.Individual values are are to		1-127: Available for standards action. Individual values are to
	be assigned according to the "Private Use" policy defined in		be assigned according to the "Specification Required" policy
	[RFC8126]		defined in [RFC8126].
	128-254: Reserved for private use.		128-254: Reserved for private use.
	255: Reserved.		255: Reserved.
	8. Security Considerations		8. Security Considerations
	This document introduces no new security issues. Security of routing		This document introduces no new security issues. Security of routing
	within a domain is already addressed as part of the routing protocols		within a domain is already addressed as part of the routing protocols
	themselves. This document proposes no changes to those security		themselves. This document proposes no changes to those security
End of changes. 6 change blocks.
	10 lines changed or deleted		8 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/