Flooding Reduction Algorithm Interoperability Considerations
draft-lsr-prz-interop-flood-reduction-architecture-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tony Przygienda , Shraddha Hegde | ||
| Last updated | 2024-10-19 | ||
| Replaced by | draft-lsr-interop-flood-reduction-architecture, draft-ietf-lsr-isis-flood-reduction-arch | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-lsr-interop-flood-reduction-architecture, draft-ietf-lsr-isis-flood-reduction-arch | |
| 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:
Abstract
In case multiple distributed (including a possible centralized one) flood reduction algorithms are deployed at the same time in an IGP domain the correctness of the overall solution preconditions certain co-operative behavior of involved algorithms. Under such conditions the correctness of the overall solution can be derived from resulting graph theoretical concepts easily. This document presents the necessary requirements on the deployed algorithms and the resulting framework. The situation of multiple algorithms in the network in steady state is per se not necessarily operationally desirable but must be, if minimal network disruption during such procedure is required, solved for possible migration scenarios caused by e.g. discovered defects or algorithm improvements.
Authors
Tony Przygienda
Shraddha Hegde
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)