prefer ipv6 examples in the documentation

[Alexander Zubkov]

Hi all,

Sorry, it looks like I forgot to attach the patch itself in my first
message.

Regards,
Alexander

On Thu, Jun 5, 2025 at 4:48 AM Nico Schottelius <
nico.schottelius at ungleich.ch> wrote:

>
> Good morning,
>
> I've to say I love this. I think this is the really the right place &
> right time, I am often frustrated with educational material still
> referencing IPv4 primarily.
>
> I personally would really welcome this to be accepted.
>
> Related topic:
>
> There is actually one more item to look for and maybe it's literally
> just one item: what are the real world requirements for IPv4 in bird / a
> router?
>
> What I know for sure and probably everyone knows is that the router ID
> is a 32 bit integer, in practice the (public-ish) IPv4 address of the
> router. While technically it can be anything (let's say 1 or 2 or 42),
> it is being sent to the BGP peer:
>
> k8s_p5_1_6 BGP        ---        up     2025-06-01    Established
>   BGP state:          Established
>     Neighbor address: 2a0a:e5c0::62be:b4ff:fe08:49e1
>     Neighbor AS:      65533
>     Local AS:         199553
>     Neighbor ID:      15.108.225.116
>     ...
>
> I know this is out of scope for a change just in bird, but it might be
> worth discussing on how to treat the router ID, because with the notion
> of "it's unique / official address", every router out there still
> requires at least one IPv4 address, which is at minimum very cumbersome.
>
> </related topic>
>
> Hope the patch makes it into the documentation, as bird is one of the
> best pieces of routing software and having an IPv6 first documentation
> would certainly benefit it.
>
> Greetings from Seoul,
>
> Nico
>
>
> Alexander Zubkov via Bird-users <bird-users at network.cz> writes:
>
> > Hi everybody!
> >
> > In spite or recent Maria's activity, I decided to checked the BIRD
> documentation and found many examples where legacy :) IPv4 addresses are
> used.
> > My proposal is to preferably use IPv6 examples in the documentation. I
> tried to spot the places where IPv4 examples can be replaced or complemented
> > by IPv6 examples, and prepared a patch with possible changes.
> >
> > Regards,
> > Alexander Zubkov
>
> --
> Sustainable and modern Infrastructures by ungleich.ch
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20250605/18dbeb30/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: doc-ipv6.patch
Type: text/x-patch
Size: 12992 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20250605/18dbeb30/attachment.bin>