< draft-ietf-lsr-isis-flood-reflection-04.txt		draft-ietf-lsr-isis-flood-reflection-05.txt >
	Network Working Group A. Przygienda		Network Working Group A. Przygienda, Ed.
	Internet-Draft C. Bowers		Internet-Draft C. Bowers
	Intended status: Standards Track Juniper		Intended status: Experimental Juniper
	Expires: 24 April 2022 Y. Lee		Expires: 26 May 2022 Y. Lee
	A. Sharma		A. Sharma
	Comcast		Comcast
	R. White		R. White
	Juniper		Juniper
	21 October 2021		22 November 2021
	IS-IS Flood Reflection		IS-IS Flood Reflection
	draft-ietf-lsr-isis-flood-reflection-04		draft-ietf-lsr-isis-flood-reflection-05
	Abstract		Abstract
	This document describes a backwards compatible, optional ISIS		This document describes a backwards compatible, optional ISIS
	extension that allows the creation of IS-IS flood reflection		extension that allows the creation of IS-IS flood reflection
	topologies. Flood reflection allows topologies in which L1 areas		topologies. Flood reflection allows topologies in which L1 areas
	provide transit forwarding for L2 using all available L1 nodes		provide transit forwarding for L2 using all available L1 nodes
	internally. It accomplishes this by creating L2 flood reflection		internally. It accomplishes this by creating L2 flood reflection
	adjacencies within each L1 area. Those adjacencies are used to flood		adjacencies within each L1 area. Those adjacencies are used to flood
	L2 LSPDUs, and they are used in the L2 SPF computation. However,		L2 LSPDUs, and they are used in the L2 SPF computation. However,
	skipping to change at page 2, line 10 ¶		skipping to change at page 2, line 10 ¶
	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 24 April 2022.		This Internet-Draft will expire on 26 May 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD License text		extracted from this document must include Revised BSD License text as
	as described in Section 4.e of the Trust Legal Provisions and are		described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Further Details . . . . . . . . . . . . . . . . . . . . . . . 8		3. Further Details . . . . . . . . . . . . . . . . . . . . . . . 8
	4. Flood Reflection TLV . . . . . . . . . . . . . . . . . . . . 9		4. Flood Reflection TLV . . . . . . . . . . . . . . . . . . . . 9
	5. Flood Reflection Discovery Sub-TLV . . . . . . . . . . . . . 10		5. Flood Reflection Discovery Sub-TLV . . . . . . . . . . . . . 10
	6. Flood Reflection Discovery Tunnel Type Sub-Sub-TLV . . . . . 11		6. Flood Reflection Discovery Tunnel Type Sub-Sub-TLV . . . . . 11
	7. Flood Reflection Adjacency Sub-TLV . . . . . . . . . . . . . 12		7. Flood Reflection Adjacency Sub-TLV . . . . . . . . . . . . . 12
	skipping to change at page 3, line 24 ¶		skipping to change at page 3, line 24 ¶
	Flood Reflector Client:		Flood Reflector Client:
	Node configured to build flood reflector adjacencies and normal L2		Node configured to build flood reflector adjacencies and normal L2
	nodes.		nodes.
	Flood Reflector Adjacency:		Flood Reflector Adjacency:
	ISIS L2 adjacency limited by one end being client and the other		ISIS L2 adjacency limited by one end being client and the other
	reflector and agreeing on the same Flood Reflector Cluster ID.		reflector and agreeing on the same Flood Reflector Cluster ID.
	Flood Reflector Cluster:		Flood Reflector Cluster:
	Collection of clients and flood reflectors configured with the		Collection of clients and flood reflectors configured with the
	same cluster identifier.		same cluster identifier. Cluster ID value of 0 SHOULD NOT be used
			since it may be used in the future for special purposes.
	Tunnel Deployment:		Tunnel Deployment:
	Deployment where flood reflector clients build a full mesh of		Deployment where flood reflector clients build a full mesh of
	tunnels in L1 to "shortcut" forwarding of L2 traffic through the		tunnels in L1 to "shortcut" forwarding of L2 traffic through the
	cluster.		cluster.
	No Tunnel Deployment:		No Tunnel Deployment:
	Deployment where flood reflector clients redistribute L2		Deployment where flood reflector clients redistribute L2
	reachability into L1 to allow forwarding through the cluster		reachability into L1 to allow forwarding through the cluster
	without underlying tunnels.		without underlying tunnels.
	skipping to change at page 10, line 6 ¶		skipping to change at page 10, line 6 ¶
	RESERVED: This field is reserved for future use. It MUST be set to		RESERVED: This field is reserved for future use. It MUST be set to
	0 when sent and MUST be ignored when received.		0 when sent and MUST be ignored when received.
	Flood Reflection Cluster ID: Flood Reflection Cluster Identifier.		Flood Reflection Cluster ID: Flood Reflection Cluster Identifier.
	These same 32-bit value MUST be assigned to all of the flood		These same 32-bit value MUST be assigned to all of the flood
	reflectors and flood reflector clients in the same L1 area. The		reflectors and flood reflector clients in the same L1 area. The
	value MUST be unique across different L1 areas within the IGP		value MUST be unique across different L1 areas within the IGP
	domain. On a given router, the same value of the Flood Reflection		domain. On a given router, the same value of the Flood Reflection
	Cluster ID MUST be advertised across all interfaces advertising		Cluster ID MUST be advertised across all interfaces advertising
	the Flood Reflection TLV in IIHs. This implies that a flood		the Flood Reflection TLV in IIHs. This implies that a flood
	reflector can participate in a single L1 area only.		reflector can participate in a single L1 area only. In case of
			Cluster ID value of 0, the TLV MUST be ignored.
	Sub-TLVs: Optional sub-TLVs. For future extensibility, the format		Sub-TLVs: Optional sub-TLVs. For future extensibility, the format
	of the Flood Reflection TLV allows for the possibility of		of the Flood Reflection TLV allows for the possibility of
	including optional sub-TLVs. No sub-TLVs of the Flood Reflection		including optional sub-TLVs. No sub-TLVs of the Flood Reflection
	TLV are defined in this document.		TLV are defined in this document.
	The Flood Reflection TLV SHOULD NOT appear more than once in an IIH.		The Flood Reflection TLV SHOULD NOT appear more than once in an IIH.
	A router receiving multiple Flood Reflection TLVs in the same IIH		A router receiving multiple Flood Reflection TLVs in the same IIH
	MUST use the values in the first TLV and it SHOULD adequately log		MUST use the values in the first TLV and it SHOULD adequately log
	such violations subject to rate limiting.		such violations subject to rate limiting.
	skipping to change at page 10, line 47 ¶		skipping to change at page 10, line 48 ¶
	Length: The length, in octets, of the following fields.		Length: The length, in octets, of the following fields.
	C (Client): This bit is set to indicate that the router acts as a		C (Client): This bit is set to indicate that the router acts as a
	flood reflector client. When this bit is NOT set, the router acts		flood reflector client. When this bit is NOT set, the router acts
	as a flood reflector.		as a flood reflector.
	RESERVED: This field is reserved for future use. It MUST be set to		RESERVED: This field is reserved for future use. It MUST be set to
	0 when sent and MUST be ignored when received.		0 when sent and MUST be ignored when received.
	Flood Reflection Cluster ID: The Flood Reflection Cluster Identifier		Flood Reflection Cluster ID: The Flood Reflection Cluster Identifier
	is the same as that defined in the Flood Reflection TLV.		is the same as that defined in the Flood Reflection TLV and obeys
			the same rules.
	The Flood Reflection Discovery sub-TLV SHOULD NOT appear more than		The Flood Reflection Discovery sub-TLV SHOULD NOT appear more than
	once in TLV 242. A router receiving multiple Flood Reflection		once in TLV 242. A router receiving multiple Flood Reflection
	Discovery sub-TLVs in TLV 242 MUST use the values in the first sub-		Discovery sub-TLVs in TLV 242 MUST use the values in the first sub-
	TLV and it SHOULD adequately log such violations subject to rate		TLV and it SHOULD adequately log such violations subject to rate
	limiting.		limiting.
	6. Flood Reflection Discovery Tunnel Type Sub-Sub-TLV		6. Flood Reflection Discovery Tunnel Type Sub-Sub-TLV
	Flood Reflection Discovery Tunnel Type sub-sub-TLV is advertised		Flood Reflection Discovery Tunnel Type sub-sub-TLV is advertised
	skipping to change at page 12, line 42 ¶		skipping to change at page 12, line 42 ¶
	Length: The length, in octets, of the following fields.		Length: The length, in octets, of the following fields.
	C (Client): This bit is set to indicate that the router advertising		C (Client): This bit is set to indicate that the router advertising
	this adjacency is a flood reflector client. When this bit is NOT		this adjacency is a flood reflector client. When this bit is NOT
	set, the router advertising this adjacency is a flood reflector.		set, the router advertising this adjacency is a flood reflector.
	RESERVED: This field is reserved for future use. It MUST be set to		RESERVED: This field is reserved for future use. It MUST be set to
	0 when sent and MUST be ignored when received.		0 when sent and MUST be ignored when received.
	Flood Reflection Cluster ID: The Flood Reflection Cluster Identifier		Flood Reflection Cluster ID: The Flood Reflection Cluster Identifier
	is the same as that defined in the Flood Reflection TLV.		is the same as that defined in the Flood Reflection TLV and obeys
			the same rules.
	The Flood Reflection Adjacency sub-TLV SHOULD NOT appear more than		The Flood Reflection Adjacency sub-TLV SHOULD NOT appear more than
	once in a given TLV. A router receiving multiple Flood Reflection		once in a given TLV. A router receiving multiple Flood Reflection
	Adjacency sub-TLVs in a TLV MUST use the values in the first sub-TLV		Adjacency sub-TLVs in a TLV MUST use the values in the first sub-TLV
	and it SHOULD adequately log such violations subject to rate		and it SHOULD adequately log such violations subject to rate
	limiting.		limiting.
	8. Flood Reflection Discovery		8. Flood Reflection Discovery
	A router participating in flood reflection MUST be configured as an		A router participating in flood reflection MUST be configured as an
	skipping to change at page 19, line 12 ¶		skipping to change at page 19, line 12 ¶
	DOI 10.17487/RFC7981, October 2016,		DOI 10.17487/RFC7981, October 2016,
	<https://www.rfc-editor.org/info/rfc7981>.		<https://www.rfc-editor.org/info/rfc7981>.
	[RFC9012] Patel, K., Van de Velde, G., Sangli, S., and J. Scudder,		[RFC9012] Patel, K., Van de Velde, G., Sangli, S., and J. Scudder,
	"The BGP Tunnel Encapsulation Attribute", RFC 9012,		"The BGP Tunnel Encapsulation Attribute", RFC 9012,
	DOI 10.17487/RFC9012, April 2021,		DOI 10.17487/RFC9012, April 2021,
	<https://www.rfc-editor.org/info/rfc9012>.		<https://www.rfc-editor.org/info/rfc9012>.
	Authors' Addresses		Authors' Addresses
	Tony Przygienda		Tony Przygienda (editor)
	Juniper		Juniper
	1137 Innovation Way		1137 Innovation Way
	Sunnyvale, CA		Sunnyvale, CA
	United States of America		United States of America
	Email: prz@juniper.net		Email: prz@juniper.net
	Chris Bowers		Chris Bowers
	Juniper		Juniper
	1137 Innovation Way		1137 Innovation Way
End of changes. 11 change blocks.
	14 lines changed or deleted		18 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/