Re: [v6ops] New Version Notification for draft-olopade-6man-slaac-signaling-00.txt

["Olopade, Olorunloba" <[e-mail]>]

Hello all,

I'm proposing an alternate way to address the SLAAC flash renumbering issue, and I've been advised to put this in a draft. This is the initial draft, and definitely need more work, but will like to know if people think this approach is worth considering.

Regards.

Loba Olopade

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] 
Sent: 19 October 2020 19:43
To: Olopade, Olorunloba <[e-mail]>
Subject: New Version Notification for draft-olopade-6man-slaac-signaling-00.txt


A new version of I-D, draft-olopade-6man-slaac-signaling-00.txt
has been successfully submitted by Loba Olopade and posted to the IETF repository.

Name:		draft-olopade-6man-slaac-signaling
Revision:	00
Title:		Explicit signaling of Stateless Address Autoconfiguration (SLAAC) to Renumbering Events
Document date:	2020-10-19
Group:		Individual Submission
Pages:		7
URL:            https://www.ietf.org/archive/id/draft-olopade-6man-slaac-signaling-00.txt
Status:         https://datatracker.ietf.org/doc/draft-olopade-6man-slaac-signaling/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-olopade-6man-slaac-signaling
Htmlized:       https://tools.ietf.org/html/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.

                                                                                  


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


--------------------------------------------------------------------
Save Paper - Do you really need to print this e-mail?

Visit www.virginmedia.com for more information, and more fun.

This email and any attachments are or may be confidential and legally privileged
and are sent solely for the attention of the addressee(s).

Virgin Media will never ask for account or financial information via email. If you are in receipt of a suspicious email, please report to www.virginmedia.com/netreport

If you have received this email in error, please delete it from your system: its use, disclosure or copying is unauthorised. Statements and opinions expressed in this email may not represent those of Virgin Media. Any representations or commitments in this email are subject to contract.

Registered office: 500 Brook Drive, Reading, RG2 6UU

Registered in England and Wales with number 2591237