Folks, To make the story short: Based on the recent discussion we had on our IETF I-D draft-gont-6man-slaac-renum, we have posted this new I-D which focuses on discussing the problem, and describing operational mitigations.
The document is available at: https://www.ietf.org/internet-drafts/draft-gont-v6ops-slaac-renum-00.txt Comments are welcome. It is being discussed on the IETF v6ops wg mailing-list: https://mailarchive.ietf.org/arch/msg/v6ops/5D2hdpB6QHRm9u-MUj6erQaLZY0 If possible, post your comments on the v6ops wg list. But comments are welcome, whether there, here, or even unicast to us (co-authors) ;-) Thanks! Cheers, Fernando -------- Forwarded Message -------- Subject: New Version Notification for draft-gont-v6ops-slaac-renum-00.txt Date: Sat, 06 Jul 2019 08:59:12 -0700 From: [email protected] To: Fernando Gont <[email protected]>, Jan Zorz <[email protected]>, Richard Patterson <[email protected]> A new version of I-D, draft-gont-v6ops-slaac-renum-00.txt has been successfully submitted by Fernando Gont and posted to the IETF repository. Name: draft-gont-v6ops-slaac-renum Revision: 00 Title: Reaction of Stateless Address Autoconfiguration (SLAAC) to Renumbering Events Document date: 2019-07-06 Group: Individual Submission Pages: 14 URL: https://www.ietf.org/internet-drafts/draft-gont-v6ops-slaac-renum-00.txt Status: https://datatracker.ietf.org/doc/draft-gont-v6ops-slaac-renum/ Htmlized: https://tools.ietf.org/html/draft-gont-v6ops-slaac-renum-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-gont-v6ops-slaac-renum Abstract: In scenarios where network configuration information related to IPv6 prefixes becomes invalid without any explicit signaling of that condition (such as when a CPE crashes and reboots without knowledge of the previously-employed prefixes), nodes on the local network will continue using stale prefixes for an unacceptably long period of time, thus resulting in connectivity problems. This document analyzes these problem scenarios, and discusses operational workarounds to improve network robustness. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
