Experiences implementing the Babel routing protocol
draft-hoeiland-joergensen-babel-implementation-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Toke Høiland-Jørgensen | ||
| Last updated | 2016-10-07 (Latest revision 2016-04-05) | ||
| 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
This document describes the experiences creating independent implementations of the Babel routing protocol [RFC6126], based on the two independent implementations currently available. The Babel routing protocol is easy to implement, and it is quite feasible for someone with no prior experience with routing protocols to create a working implementation. The few issues that needed clarification during the independent implementation work are documented, with the hope of aiding others seeking to implement Babel.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)