Moving draft-gont-slaac-renum forward (fwd: New Version Notification for draft-gont-6man-slaac-renum-06.txt)

[Fernando Gont <[e-mail]>]

Folks,

I've just posted a revision of draft-gont-6man-slaac-renum 
(<https://www.ietf.org/internet-drafts/draft-gont-6man-slaac-renum-06.txt>), 
which incorporates these changes:

* It updates the section on the default PIO lifetimes (Section 4.1.1) 
according to the discussion we had both at the 6man interim meeting and 
on the mailing-list.

* Added an "Implementation status" section


At this point, we would like 6man to be polled for adoption of this 
document as a wg item.

The topic and variants of this document have been discussed for over a 
year now, with the problem statement document becoming a wg item of 
v6ops (draft-ietf-v6ops-slaac-renum).

We believe that both the topic and the document have received a fair 
share of interest and discussion, and that it is time for the wg to make 
a decision on the document, for the wg to continue to work on it as a 
working group document.

Thanks!

Cheers,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for draft-gont-6man-slaac-renum-06.txt
Date: Mon, 06 Apr 2020 12:37:26 -0700
From: [e-mail]
To: Fernando Gont <[e-mail]>, Jan Zorz <[e-mail]>, 
Richard Patterson <[e-mail]>


A new version of I-D, draft-gont-6man-slaac-renum-06.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-gont-6man-slaac-renum
Revision:	06
Title:		Improving the Robustness of Stateless Address Autoconfiguration 
(SLAAC) to Flash Renumbering Events
Document date:	2020-04-06
Group:		Individual Submission
Pages:		29
URL: 
https://www.ietf.org/internet-drafts/draft-gont-6man-slaac-renum-06.txt
Status: 
https://datatracker.ietf.org/doc/draft-gont-6man-slaac-renum/
Htmlized:       https://tools.ietf.org/html/draft-gont-6man-slaac-renum-06
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-gont-6man-slaac-renum
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-gont-6man-slaac-renum-06

Abstract:
    In renumbering scenarios where an IPv6 prefix suddenly becomes
    invalid, hosts on the local network will continue using stale
    prefixes for an unacceptably long period of time, thus resulting in
    connectivity problems.  This document improves the reaction of IPv6
    Stateless Address Autoconfiguration to such renumbering scenarios.

 


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