Security considerations for the Babel routing protocol
draft-chroboczek-babel-security-considerations-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Juliusz Chroboczek | ||
Last updated | 2015-10-09 (Latest revision 2015-04-07) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
Where we stress that the Babel routing protocol is completely insecure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)