<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.gont-v6ops-slaac-renum" target="https://datatracker.ietf.org/doc/html/draft-gont-v6ops-slaac-renum-02">
   <front>
      <title>Reaction of Stateless Address Autoconfiguration (SLAAC) to Flash- Renumbering Events</title>
      <author initials="F." surname="Gont" fullname="Fernando Gont">
         <organization>SI6 Networks</organization>
      </author>
      <author initials="J." surname="Zorz" fullname="Jan Zorz">
         <organization>Go6 Institute</organization>
      </author>
      <author initials="R." surname="Patterson" fullname="Richard Patterson">
         <organization>Sky UK</organization>
      </author>
      <date month="February" day="20" year="2020" />
      <abstract>
	 <t>   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
   documents this problem, and discusses operational workarounds that
   may help to improve network robustness.  Additionally, it highlights
   areas where further work may be needed.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-gont-v6ops-slaac-renum-02" />
   
</reference>
