> The only corner of the babel RFC that still scares me are "sources" :)
Then let me lecture a bit :-)
Babel is partly based on the ideas in DSDV, which was a pure mesh
protocol. In DSDV, there is no distinction between prefix, neighbour and
source: the IP address of a router is used as the
Hi Daniel __
> I'd be interested in helping out.
That’s fantastic! Please feel free to have a look at my code and start hacking
right away. I try to keep my local changes synced as close to the master.
So you can see my progress right away. I am currently, still working on the
protocol parsing
Hi Steffen,
On Thu, May 18, 2023 at 09:41:30AM +0200, Steffen Vogel wrote:
> My hope is to find a few collaborators for my endeavor who can support me
> with the tricky parts of the protocol.
Sounds fun. I'd be interested in helping out. Been meaning to get more into
go anyway.
I've been
Hi Juliusz,
> That's way into the future, but I encourage you to keep source-specific
> routing in mind.
Noted __ I am already parsing sub-TLVs for it. I think there is also a valid
use-case for SADR
within overlay networks as every node has its own external gateway and
connected networks
> A couple of days ago, I started to work on implementation of the Babel
> protocol in Go driven by the following objectives:
Excellent news. Babel is a protocol, and I'm trying to encourage
independent implementations of the protocol. In fact, I consider that the
implementation in BIRD is
Hello, Steffen.
It's a very cool and interesting project.
Being a network admin, I would be very interested in such a use-case,
when it will be at least beta-status ready.
So, I will be able to assist with some testing of routing. (Playing
with some overlay things too, multihop and RTT based.)
Hi babel-users,
This is my first post to this list and as such also my first contact with the
Babel community.
A couple of days ago, I started to work on implementation of the Babel protocol
in Go driven by the following objectives:
- Embeddable Go-package / library
- Possibly also a
