Security considerations for the Babel routing protocol
draft-chroboczek-babel-security-considerations-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2015-10-09 (latest revision 2015-04-07) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
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-chroboczek-babel-security-considerations-00.txt
https://www.ietf.org/archive/id/draft-chroboczek-babel-security-considerations-00.txt
Abstract
Where we stress that the Babel routing protocol is completely insecure.
Authors
Juliusz Chroboczek (jch@pps.univ-paris-diderot.fr)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)