Explicit signaling of Stateless Address Autoconfiguration (SLAAC) to Renumbering Events
draft-olopade-6man-slaac-signaling-00

Document Type Active Internet-Draft (individual)
Author Loba Olopade 
Last updated 2020-10-19
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IPv6 Maintenance (6man) Working Group                       Loba Olopade
Internet-Draft                                              Virgin Media
Updates: 4862 (if approved)                             October 19, 2020
Intended status: Standards Track                                        
Expires: April 22, 2021                                                 

  Explicit signaling of Stateless Address Autoconfiguration (SLAAC)
                      to Renumbering Events
                 draft-olopade-6man-slaac-signaling-00

Abstract

   After a renumbering event in an IPv6 network utilizing SLAAC, hosts
   might continue to use stale addresses, as they are unaware of the
   changes. Likewise, routers, who may deprecate the use of these
   prefixes, are unaware of their use on the hosts. This scenario could
   have an adverse effect on communication with the host. This document
   proposes changes to the SLAAC algorithm that will explicitly allow
   routers to learn of these stale prefixes that are still assigned on
   the network.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 19, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
 

Olopade                  Expires April 22, 2021                 [Page 1]
Internet-Draft        Explicit Signaling for SLAAC      October 19, 2020

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  SLAAC reaction to new PIOs . . . . . . . . . . . . . . . . . .  3
     3.1.  Proposed Change  . . . . . . . . . . . . . . . . . . . . .  4
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  4
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
   6.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  4
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  4
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  6
   Appendix A.  Suggested Garbage collection of stale prefix 
            information . . . . . . . . . . . . . . . . . . . . . . .  6
     A.1  Prefix Validation . . . . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

 

Olopade                  Expires April 22, 2021                 [Page 2]
Internet-Draft        Explicit Signaling for SLAAC      October 19, 2020

1.  Introduction

   After a renumbering event in an IPv6 network utilizing SLAAC, hosts
   might continue to use stale addresses, as they are unaware of the
   changes. Likewise, routers, who may deprecate the use of these
   prefixes, are unaware of their use on the hosts. This scenario, with
   its causes and impacts are well documented in [I-D.ietf-v6ops-slaac-
   renum] and [I-D.linkova-6man-default-addr-selection-update]. A key
   factor with this issue is the lack of explicit signaling. For various
   reasons, routers might not explicitly signal the network that there
   is a renumbering event. Once the renumbering event has occurred,
   there are no means to learn of the stale prefixes that might still be
   present on the network. Without a means to do a garbage collection,
   the network is limited to the aging out process of stale
   information.

   Rather than aging out, it would be better for routers to learn of
   this information, in a proactive manner. Using Neighbor Discovery
   messages, the router could learn of the stale prefixes.
Show full document text