[atlas] IPv6-renew

>> Is this a flaw, or is it by design?
> 
> this is a known protocol issue with slaac.  There's some discussion about it in rfc8978 and draft-ietf-6man-slaac-renum.

To be correct; it's an operational issue. SLAAC works as designed with IPv6 renumbering.
Imagine if the mobile operator swapped your mobile phone number midstream.

Support for ephemeral addressing (aka flash renumbering) is quite involved.
The mobile phone stacks have largely managed to do that, but for all else it involves transitioning away from TCP, updating all apps etc...

Not surprising that the probe takes a few minutes to detect and adjust.

Best regards,
Ole
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20210621/250d0897/attachment.sig>