[Idr] Link Local Next Hop Handling for BGP

[Donatas Abraitis <[e-mail]>]

Hi, folks!

we want to continue with a long-standing draft
https://datatracker.ietf.org/doc/html/draft-white-linklocalnh to take some
further actions to move forward.

More and more issues come dealing with inter-operability handling IPv6
link-local next-hops. Especially it's tricky how to handle 32-bytes length
next-hops and every implementation handles this independently which makes
things even worse.

Some open-source daemons set NH length to 32-bytes, but the global address
(GA) is set to `::`. How this should be handled correctly? In such a case,
a DUT device can be in trouble while setting next-hop at receiving side (if
global is preferred).

If IPv6 GA does not exist, sending LL(LL) with 32-bytes is the correct way
or not again?

Controversially, is it OKay sending GA(::) (I didn't see and even expect
this to happen, but...).

Waiting for comments!

-- 
Donatas