Skip to main content

IS-IS Flood Reflection

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Tony Przygienda , Chris Bowers , Yiu Lee , Alankar Sharma , Russ White
Last updated 2020-07-01
Replaces draft-przygienda-lsr-flood-reflection
Replaced by RFC 9377
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-lsr-isis-flood-reflection
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document describes an optional ISIS extension that allows the creation of IS-IS flood reflection topologies. Flood reflection allows the creation of topologies where L1 areas provide transit forwarding for L2 destinations within an L2 topology. It accomplishes this by creating L2 flood reflection adjacencies within each L1 area. The L2 flood reflection adjacencies are used to flood L2 LSPDUs, and they are used in the L2 SPF computation. However, they are not used for forwarding. This arrangement gives the L2 topology better scaling properties. In addition, only those routers directly participating in flood reflection have to support the feature. This allows for the incremental deployment of scalable L1 transit areas in an existing network, without the necessity of upgrading other routers in the network.


Tony Przygienda
Chris Bowers
Yiu Lee
Alankar Sharma
Russ White

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)