Jeff Tantsura writes:
> Looking at the fix, Donald has only removed IPV4_CLASS_DE(a)
> uint32_t)(a)) & 0xe000) == 0xe000)
> validation but kept INADDR_ANY.
> I’ll bring up RFC6286 to him
I believe it is implementing the RFC6286 requirements. INADDR_ANY is
((in_addr_t) 0x),
Looking at the fix, Donald has only removed IPV4_CLASS_DE(a) uint32_t)(a))
& 0xe000) == 0xe000)
validation but kept INADDR_ANY.
I’ll bring up RFC6286 to him
Cheers,
Jeff
> On Sep 12, 2022, at 13:41, Bjørn Mork wrote:
> Jeff Tantsura writes:
>
>> Indeed, someone was recently comp
Jeff Tantsura writes:
> Indeed, someone was recently complaining that FRR is unhappy with a
> peer with router-id from class E range…
This made me curious enough to dig up the fix. If anyone else is interested:
https://github.com/FRRouting/frr/commit/b5c2113e47f846d0c48fb4ef63e29bf96bd2fbe2
B
Indeed, someone was recently complaining that FRR is unhappy with a peer with
router-id from class E range…
Cheers,
Jeff
> On Sep 9, 2022, at 09:30, Saku Ytti wrote:
>
> On Fri, 9 Sept 2022 at 09:31, Crist Clark wrote:
>
>> As I said in the original email, I realize router IDs just need to
I assume you would still have a Loopback0 address. While I'm not completely
sure it's a hard guaranty of uniqueness as I don't know your numbering scheme,
if it is, why not use the last 32bits of the IPv6 Loopback0 address. This
should closely approximate previous modes of operation and not requ
On Fri, 9 Sept 2022 at 09:31, Crist Clark wrote:
> As I said in the original email, I realize router IDs just need to be
> unique in
> an AS. We could have done random ones with IPv4, but using a well chosen
In some far future this will be true. We meet eBGP speakers across the
world, and not ev
As I said in the original email, I realize router IDs just need to be
unique in
an AS. We could have done random ones with IPv4, but using a well chosen
address assigned to the router guarantees uniqueness as well as some
other useful
properties. I was wondering if people had some ways to do som
On Wed, 7 Sep 2022, Crist Clark wrote:
During some IPv6 numbering discussions at work today, someone had a question
that I hadn't really considered before. How to choose 32-bit router IDs for
IPv6-only routers.
Quick background. We have a requirement to convert a significant portion of our
net
enke and jenny yuan cleaned this up in 6286
randy
Thu, Sep 08, 2022 at 10:18:13AM -0700, Randy Bush:
> > A question Dorian and I discussed but never answered is, how are open
> > collisions handled if two speakers, presumably an external AS, happen
> > to have the RID?
>
> the uniqueness is supposed to be on the tuple {AS,RID}
I thought that was
> A question Dorian and I discussed but never answered is, how are open
> collisions handled if two speakers, presumably an external AS, happen
> to have the RID?
the uniqueness is supposed to be on the tuple {AS,RID}
so an RID 'collision' with a foreign AS should not be possible
randy
Thu, Sep 08, 2022 at 08:13:33AM -0700, Randy Bush:
> > During some IPv6 numbering discussions at work today, someone had a
> > question that I hadn't really considered before. How to choose 32-bit
> > router IDs for IPv6-only routers.
>
> arbitrary 32 bit number unique in the autonomous system. e
>
> Is there really such as thing as pure IPV6 only?
>
Yup.
On Thu, Sep 8, 2022 at 11:32 AM Paul Amaral via NANOG
wrote:
> Is there really such as thing as pure IPV6 only? I don’t think you will be
> able to run IPV6 for transport without the router locally knowing how to
> handle IPV4, at leas
Is there really such as thing as pure IPV6 only? I don’t think you will be able
to run IPV6 for transport without the router locally knowing how to handle
IPV4, at least not right now as there’s a lot of legacy code. Usually IPV6 is
enabled longer after IPV4 has been running. With that said, can
Right!
Personally it just needs to be unique. Relying on a Id to be unique when
ascociated to an IP address that may be used on a failover system seems really
poor to me.
Assign a random ID and plug it into your IPAM!. If at anything assign a router
ID to a rack location and associate every bi
> During some IPv6 numbering discussions at work today, someone had a
> question that I hadn't really considered before. How to choose 32-bit
> router IDs for IPv6-only routers.
arbitrary 32 bit number unique in the autonomous system. even in an
ipv4 world it does not need to match any configured
On Thu, 8 Sept 2022 at 10:22, Bjørn Mork wrote:
> I'm not used to punching anything, so I probably have too simple a view
> of the world.
>
> But I still don't understand how this changes the ID allocation scheme,
> which is how I understood the question. I assume the punched value was
> based o
Saku Ytti writes:
> On Thu, 8 Sept 2022 at 10:01, Bjørn Mork wrote:
>
>> Why would you do it differently than for dual-stack routers, except that
>> you skip the step where you configure the ID as a loopback address?
>
> Because you may not have an option, if you're IPv6 only, vendors (e.g.
> ju
On Thu, 8 Sept 2022 at 10:01, Bjørn Mork wrote:
> Why would you do it differently than for dual-stack routers, except that
> you skip the step where you configure the ID as a loopback address?
Because you may not have an option, if you're IPv6 only, vendors (e.g.
junos) may expect you to punch i
Crist Clark writes:
> During some IPv6 numbering discussions at work today, someone had a
> question that I hadn't really considered before. How to choose 32-bit
> router IDs for IPv6-only routers.
Why would you do it differently than for dual-stack routers, except that
you skip the step where y
Hey,
> Well, now there is no IPv4. But BGP, OSPFv3, and other routing protocols
> still use 32-bit router IDs for IPv6. On the one hand, there are plenty of
> 32-bit numbers to use. Generally speaking, router IDs just need to be unique
> inside of an AS to do their job, but (a) for humans or au
21 matches
Mail list logo
