rfc9667v2.txt   rfc9667.txt 
skipping to change at line 273 skipping to change at line 273
termed the Area Leader, or in a distributed manner on all nodes that termed the Area Leader, or in a distributed manner on all nodes that
are supporting dynamic flooding. If the flooding topology is are supporting dynamic flooding. If the flooding topology is
computed centrally, it is encoded into and distributed as part of the computed centrally, it is encoded into and distributed as part of the
normal LSDB. This is the centralized mode of operation. If the normal LSDB. This is the centralized mode of operation. If the
flooding topology is computed in a distributed fashion, this is the flooding topology is computed in a distributed fashion, this is the
distributed mode of operation. Nodes within such an IGP area would distributed mode of operation. Nodes within such an IGP area would
only flood on the flooding topology. On links outside of the only flood on the flooding topology. On links outside of the
flooding topology, normal database synchronization mechanisms, i.e., flooding topology, normal database synchronization mechanisms, i.e.,
OSPF database exchange and IS-IS Complete Sequence Number PDUs OSPF database exchange and IS-IS Complete Sequence Number PDUs
(CSNPs), would apply, but flooding may not. The detailed behavior of (CSNPs), would apply, but flooding may not. The detailed behavior of
the notes participating in IGP is described in Section 6. New link- the nodes participating in IGP is described in Section 6. New link-
state information that arrives from outside of the flooding topology state information that arrives from outside of the flooding topology
suggests that the sender has no flooding topology information or that suggests that the sender has no flooding topology information or that
it is operating on old information about the flooding topology. In it is operating on old information about the flooding topology. In
these cases, the new link-state information should be flooded on the these cases, the new link-state information should be flooded on the
flooding topology as well. flooding topology as well.
The flooding topology covers the full set of nodes within the area, The flooding topology covers the full set of nodes within the area,
but excludes some of the links that standard flooding would employ. but excludes some of the links that standard flooding would employ.
Since the flooding topology is computed before topology changes, the Since the flooding topology is computed before topology changes, the
skipping to change at line 840 skipping to change at line 840
the specified Circuit Types and flooding scopes received in the in the specified Circuit Types and flooding scopes received in the in
the IS-IS Flooding Request TLV. Flooding MUST be enabled until the the IS-IS Flooding Request TLV. Flooding MUST be enabled until the
Circuit Type or Flooding Scope is no longer advertised in the IS-IS Circuit Type or Flooding Scope is no longer advertised in the IS-IS
Flooding Request TLV or the TLV no longer appears in IIH PDUs Flooding Request TLV or the TLV no longer appears in IIH PDUs
received on the link. received on the link.
When flooding is temporarily enabled on the link for any Circuit Type When flooding is temporarily enabled on the link for any Circuit Type
or Flooding Scope due to receiving the IS-IS Flooding Request TLV, or Flooding Scope due to receiving the IS-IS Flooding Request TLV,
the receiver MUST perform standard database synchronization for the the receiver MUST perform standard database synchronization for the
corresponding Circuit Types and flooding scopes on the link. In the corresponding Circuit Types and flooding scopes on the link. In the
case of IS-IS, this results in setting the Send Routing Message (SRM) case of IS-IS, this results in setting the Send Routeing Message
flag for all related LSPs on the link and sending CSNPs. (SRM) flag for all related LSPs on the link and sending CSNPs.
So long as the IS-IS Flooding Request TLV is being received, flooding So long as the IS-IS Flooding Request TLV is being received, flooding
MUST NOT be disabled for any of the Circuit Types or flooding scopes MUST NOT be disabled for any of the Circuit Types or flooding scopes
present in the IS-IS Flooding Request TLV, even if the connection present in the IS-IS Flooding Request TLV, even if the connection
between the neighbors is removed from the flooding topology. between the neighbors is removed from the flooding topology.
Flooding for such Circuit Types or flooding scopes MUST continue on Flooding for such Circuit Types or flooding scopes MUST continue on
the link and be considered temporarily enabled. the link and be considered temporarily enabled.
5.1.6. IS-IS LEEF Advertisement 5.1.6. IS-IS LEEF Advertisement
In support of advertising which edges are currently enabled in the In support of advertising which edges are currently enabled in the
flooding topology, an implementation MAY indicate that a link is part flooding topology, an implementation MAY indicate that a link is part
of the flooding topology by advertising a bit value in the Link of the flooding topology by advertising a bit value in the Link
Attributes sub-TLV defined by [RFC5029]. Attributes sub-TLV defined by [RFC5029].
The following bit-value is defined by this document: The following bit-value is defined by this document:
Local Edge Enabled for Flooding (LEEF): 0 Local Edge Enabled for Flooding (LEEF): 0x4
5.2. OSPF LSAs and TLVs 5.2. OSPF LSAs and TLVs
This section defines new Link State Advertisements (LSAs) and TLVs This section defines new Link State Advertisements (LSAs) and TLVs
for both OSPFv2 and OSPFv3. for both OSPFv2 and OSPFv3.
The following LSAs and TLVs/sub-TLVs are added to OSPFv2/OSPFv3: The following LSAs and TLVs/sub-TLVs are added to OSPFv2/OSPFv3:
1. A TLV that is used to advertise the preference for becoming the 1. A TLV that is used to advertise the preference for becoming the
Area Leader. Area Leader.
 End of changes. 3 change blocks. 
4 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.48.