IS-IS LSP lifetime corruption - Problem Statement
draft-decraene-isis-lsp-lifetime-problem-statement-02

Document Type Expired Internet-Draft (individual)
Authors Bruno Decraene  , Christof Schmitz 
Last updated 2017-01-05 (latest revision 2016-07-04)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

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-decraene-isis-lsp-lifetime-problem-statement-02.txt

Abstract

The IS-IS protocol exchanges Link State Packet (LSP) to exchange routing information. The lifetime of this LSP is located in the LSP header and is neither protected from corruption by the Fletcher checksum nor by cryptographic authentication. So the LSP lifetime may be altered, either accidentally or maliciously any time. The lifetime field of the LSP is an important field for the correct operation of IS-IS. Corruption of this LSP lifetime may cause flooding storm with severe impact in the network. This draft documents the problem statement and calls for a solution.

Authors

Bruno Decraene (bruno.decraene@orange.com)
Christof Schmitz (christof.schmitz@orange.com)

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