rfc9764v2.txt		rfc9764.txt
	skipping to change at line 196 ¶		skipping to change at line 196 ¶
	The accepted MTU for an interface is impacted by packet encapsulation		The accepted MTU for an interface is impacted by packet encapsulation
	considerations at a given layer, e.g., Layer 2, Layer 3, tunnel, etc.		considerations at a given layer, e.g., Layer 2, Layer 3, tunnel, etc.
	A common misconfiguration of interface parameters is inconsistent		A common misconfiguration of interface parameters is inconsistent
	MTU. In the presence of inconsistent MTU, it is possible for		MTU. In the presence of inconsistent MTU, it is possible for
	applications to have unidirectional connectivity.		applications to have unidirectional connectivity.
	When it is necessary for an application using BFD with Large Packets		When it is necessary for an application using BFD with Large Packets
	to test the bidirectional Path MTU, it is necessary to configure the		to test the bidirectional Path MTU, it is necessary to configure the
	bfd.PaddedPduSize parameter on each side of the BFD session. For		bfd.PaddedPduSize parameter on each side of the BFD session. For
	example, if the desire is to verify a 1500-byte MTU in both		example, if the desire is to verify a 1512-byte MTU in both
	directions on an Ethernet or point-to-point link, each side of the		directions on an Ethernet or point-to-point link, each side of the
	BFD session must have bfd.PaddedPduSize set to 1500. In the absence		BFD session must have bfd.PaddedPduSize set to 1512. In the absence
	of such consistent configuration, BFD with Large Packets may		of such consistent configuration, BFD with Large Packets may
	correctly determine unidirectional connectivity at the tested MTU,		correctly determine unidirectional connectivity at the tested MTU,
	but bidirectional MTU may not be properly validated.		but bidirectional MTU may not be properly validated.
	It should be noted that some interfaces may intentionally have		It should be noted that some interfaces may intentionally have
	different MTUs. Setting the bfd.PaddedPduSize appropriately for each		different MTUs. Setting the bfd.PaddedPduSize appropriately for each
	side of the BFD session supports such scenarios.		side of the BFD session supports such scenarios.
	4.4. Detecting MTU Changes		4.4. Detecting MTU Changes
	skipping to change at line 255 ¶		skipping to change at line 255 ¶
	such a way to better test the ECMP members and to tie the BFD session		such a way to better test the ECMP members and to tie the BFD session
	state to the health of that ECMP. Due to implementation-specific		state to the health of that ECMP. Due to implementation-specific
	load balancing, it is not possible to standardize such additional		load balancing, it is not possible to standardize such additional
	mechanisms for BFD.		mechanisms for BFD.
	Misconfiguration of some member MTUs may lead to load balancing that		Misconfiguration of some member MTUs may lead to load balancing that
	may have an inconsistent Path MTU depending on how the traffic is		may have an inconsistent Path MTU depending on how the traffic is
	balanced. While the intent of BFD with large packets is to verify		balanced. While the intent of BFD with large packets is to verify
	Path MTU, it is subject to the same considerations above.		Path MTU, it is subject to the same considerations above.
	The above text also applies to most, if not all, BFD techniques.		This section applies to most, if not all, BFD techniques.
	4.6. S-BFD		4.6. S-BFD
	This mechanism also can be applied to other forms of BFD, including		This mechanism also can be applied to other forms of BFD, including
	Seamless BFD (S-BFD) [RFC7880].		Seamless BFD (S-BFD) [RFC7880].
	5. BFD Encapsulated in Large Packets YANG Module		5. BFD Encapsulated in Large Packets YANG Module
	5.1. Data Model Overview		5.1. Data Model Overview
	skipping to change at line 534 ¶		skipping to change at line 534 ¶
	perhaps intentionally, if the session cannot accommodate such BFD		perhaps intentionally, if the session cannot accommodate such BFD
	control packets. Operators should be mindful that multiple BFD		control packets. Operators should be mindful that multiple BFD
	clients may rely on the status of a given BFD session when		clients may rely on the status of a given BFD session when
	changing this value.		changing this value.
	There are no particularly sensitive readable data nodes.		There are no particularly sensitive readable data nodes.
	There are no particularly sensitive RPC or action operations.		There are no particularly sensitive RPC or action operations.
	Modules that use the groupings that are defined in this document		Modules that use the groupings that are defined in this document
	should identify the corresponding security considerations. This		should identify the corresponding security considerations. For
	module defines one such grouping, "bfd-large-common", which contains		example, reusing some of these groupings will expose privacy-related
	the "pdu-size" data node whose security considerations are documented		information (e.g., 'node-example'). This module defines one such
	above.		grouping, "bfd-large-common", which contains the "pdu-size" data node
			whose security considerations are documented above.
	7. IANA Considerations		7. IANA Considerations
	7.1. The "IETF XML" Registry		7.1. The "IETF XML" Registry
	IANA has registered the following URI in the "ns" subregistry of the		IANA has registered the following URI in the "ns" subregistry of the
	"IETF XML Registry" [RFC3688].		"IETF XML Registry" [RFC3688].
	URI: urn:ietf:params:xml:ns:yang:ietf-bfd-large		URI: urn:ietf:params:xml:ns:yang:ietf-bfd-large
	Registrant Contact: The IESG		Registrant Contact: The IESG
End of changes. 4 change blocks.
	7 lines changed or deleted		8 lines changed or added
This html diff was produced by rfcdiff 1.48.