IMHO, I believe that the examples should consider v4 and v6. But there is something more important than that! The examples should be made so that the routing policies apply simultaneously to both Address-Families.
I honestly feel disgusted when I have to operate a routing engine that does not allow me to use the same route-maps (or equivalent) for both address-families. P.S.: Hey Huawei, how are you doing? I think that using the same routing-policies, regardless of address-families, should be BCOP. It is because of the lack of this as a standard that aberrations such as: "In IPv4 the path is BabaNet->ThatNet, and in IPv6 it is BabaNet->TutuNet->FifiNet>ThatNet." In the day-to-day work of network operators, they end up having to take emergency actions to deal with a specific need, and IPv4 routing policies being separated from IPv6 routing policies, they end up only putting out the fire in IPv4 and IPv6 ends up forgotten. Em qui., 5 de jun. de 2025 às 19:13, babydr DBA James W. Laferriere < bab...@baby-dragons.com> escreveu: > Hello Alexander , > > On Wed, 4 Jun 2025, Alexander Zubkov via Bird-users wrote: > > 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 > > While the rest of the world maybe in a V^ world , My little > network > still uses V4 & the Documents should continue to also have V4 examples . > Maybe seperated examples V4 & V6 . > > Tia , JimL > > -- > +---------------------------------------------------------------------+ > | James W. Laferriere | System Techniques | Give me VMS | > | Network & System Engineer | 3237 Holden Road | Give me Linux | > | j...@system-techniques.com | Fairbanks, AK. 99709 | only on AXP | > +---------------------------------------------------------------------+ > -- Douglas Fernando Fischer Engº de Controle e Automação
