IS-IS Flooding over TCP
draft-hsmit-lsr-isis-flooding-over-tcp-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-04-15 (latest revision 2018-10-12) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
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) | ||
https://www.ietf.org/archive/id/draft-hsmit-lsr-isis-flooding-over-tcp-00.txt
Abstract
This document proposes a solution to use TCP for IS-IS flooding. The proposed solution is a relative simple extension to implement. IS-IS flooding over TCP brings BGP's property of scalable transport via TCP to Link-State protocols. This proposal defines a new TLV in point-to-point IIHs to signal the intent of a router to do flooding over TCP, and it defines a small header to encapsulate IS-IS PDUs in the TCP byte-stream.
Authors
Henk Smit
(hhw.smit@xs4all.nl)
Gunter Van de Velde
(gunter.van_de_velde@nokia.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)