Re: p2p interfaces (Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?)

[Jen Linkova <[e-mail]>]

On Wed, Nov 25, 2020 at 1:25 AM Eric Vyncke (evyncke)
<evyncke=[e-mail]> wrote:
> The looped interface issue was one of the use case for rfc7527 (using the SeND nonce option to detect whether the source of NS is myself)

+1. Actually I think Enhanced DAD shall be enabled by default (I was
surprised to see that it's not so widely supported as it should be).
Another nasty scenario is 'a short-lived loop in the switching
infrastructure disabling IPv6 on the router interface' (did I mention
that some routers are happily sending VRRP packets from an address
which is marked as 'duplicated'? ;-\

> -----Original Message-----
> From: Mikael Abrahamsson <swmike=[e-mail]>
> Organization: People's Front Against WWW
> Date: Tuesday, 24 November 2020 at 15:19
> To: Jared Mauch <[e-mail]>
> Cc: Eric Vyncke <[e-mail]>, 6man WG <[e-mail]>
> Subject: Re: p2p interfaces (Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?)
>
>     On Tue, 24 Nov 2020, Jared Mauch wrote:
>
>     >   If a link is point-to-point are there operations that should be
>     > turned off, and should we define that list?  (perhaps DAD is one of them)
>
>     I've seen DAD failures disabling interface on IOS XR when POS link was
>     looped...
>
>     :P
>
>     --
>     Mikael Abrahamsson    email: [e-mail]
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



-- 
SY, Jen Linkova aka Furry