This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] IPv6-renew
- Previous message (by thread): [atlas] IPv6-renew
- Next message (by thread): [atlas] Resolves AAAA Correctly, Doesn't Resolve A - best way to resolve this?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard (INEX)
nick at inex.ie
Mon Jun 21 13:11:08 CEST 2021
Ole Troan wrote on 21/06/2021 11:11: > To be correct; it's an operational issue. SLAAC works as designed with IPv6 renumbering. slaac - being stateless 'n all - was not designed with flash renumbering in mind because flash renumbering needs some degree of state synchronisation on all devices on the path between the provisioning system issuing the prefix and the end device. So in this sense it is a protocol issue, albeit an issue that was outside the design scope of the protocol. > Imagine if the mobile operator swapped your mobile phone number midstream. mobile phone numbers are stateful. You don't need to change phone number every time you're handed off to a different cell. Nick
- Previous message (by thread): [atlas] IPv6-renew
- Next message (by thread): [atlas] Resolves AAAA Correctly, Doesn't Resolve A - best way to resolve this?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]