<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-v6ops-cpe-slaac-renum" target="https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-cpe-slaac-renum-06">
   <front>
      <title>Improving the Reaction of Customer Edge Routers to 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>6connect</organization>
      </author>
      <author initials="R." surname="Patterson" fullname="Richard Patterson">
         <organization>Sky UK</organization>
      </author>
      <author initials="B." surname="Volz" fullname="Bernie Volz">
         <organization>Cisco</organization>
      </author>
      <date month="December" day="11" year="2020" />
      <abstract>
	 <t>   In scenarios where network configuration information becomes invalid
   without any explicit signaling of that condition (such as when a
   Customer Edge Router crashes and reboots without knowledge of the
   previously-employed configuration information), hosts on the local
   network will continue using stale network configuration information
   for an unacceptably long period of time, thus resulting in
   connectivity problems.  This document specifies improvements to
   Customer Edge Routers that help mitigate the aforementioned problem
   for typical residential and small office scenarios.  This document
   updates RFC7084.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-cpe-slaac-renum-06" />
   
</reference>
