IS-IS Flood Reflection
draft-przygienda-lsr-flood-reflection-01

Document Type Replaced Internet-Draft (lsr WG)
Authors Tony Przygienda  , Chris Bowers  , Yiu Lee  , Alankar Sharma  , Russ White 
Last updated 2020-06-29 (latest revision 2020-01-07)
Replaces draft-przygienda-flood-reflector
Replaced by draft-lsr-isis-flood-reflection
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Adopted by a WG
Document shepherd Acee Lindem
IESG IESG state Replaced by draft-lsr-isis-flood-reflection
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Acee Lindem <acee@cisco.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-przygienda-lsr-flood-reflection-01.txt

Abstract

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.

Authors

Tony Przygienda (prz@juniper.net)
Chris Bowers (cbowers@juniper.net)
Yiu Lee (yiu_lee@comcast.com)
Alankar Sharma (alankar_sharma@comcast.com)
Russ White (russw@juniper.net)

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