Re: Revision of the SLAAC/renum I-D (Fwd: New Version Notification for draft-gont-6man-slaac-renum-01.txt)

On 19/02/2019 02:18, JORDI PALET MARTINEZ wrote:
> As just said in another list in Spanish, the reference to GERMAN-DP
> is wrong, in the sense that is not a law or anything similar. German
> folks can confirm. At least that has been said a few weeks ago by
> Germans in another list ...

Hi,

Interesting. Can any German speaking person on this list confirm?

I also heard something like this, but can't confirm.

Cheers, Jan

> 
> Regards, Jordi
> 
> 
> 
> -----Mensaje original----- De: ipv6 <ipv6-bounces@ietf.org> en
> nombre de Fernando Gont <fgont@si6networks.com> Fecha: martes, 19 de
> febrero de 2019, 8:49 Para: "6man@ietf.org" <6man@ietf.org> CC: IPv6
> Operations <v6ops@ietf.org> Asunto: Revision of the SLAAC/renum I-D
> (Fwd: New Version Notification for
> draft-gont-6man-slaac-renum-01.txt)
> 
> Folks,
> 
> We have posted a revision of our I-D, which expands a lot on the
> problem and possible solutions, based on the email discussion we had
> on this list.
> 
> The revised I-D is available at: 
> https://www.ietf.org/internet-drafts/draft-gont-6man-slaac-renum-01.txt
>
>  Comments will be very welcome.
> 
> Thanks! Fernando & Jan
> 
> 
> 
> 
> -------- Forwarded Message -------- Subject: New Version Notification
> for draft-gont-6man-slaac-renum-01.txt Date: Mon, 18 Feb 2019
> 15:45:21 -0800 From: internet-drafts@ietf.org To: Fernando Gont
> <fgont@si6networks.com>, Jan Zorz <jan@go6.si>
> 
> 
> A new version of I-D, draft-gont-6man-slaac-renum-01.txt has been
> successfully submitted by Fernando Gont and posted to the IETF
> repository.
> 
> Name:		draft-gont-6man-slaac-renum Revision:	01 Title:		Reaction of
> Stateless Address Autoconfiguration (SLAAC) to Renumbering Events 
> Document date:	2019-02-18 Group:		Individual Submission Pages:		22 
> URL: 
> https://www.ietf.org/internet-drafts/draft-gont-6man-slaac-renum-01.txt
>
> 
Status:
> https://datatracker.ietf.org/doc/draft-gont-6man-slaac-renum/ 
> Htmlized:
> https://tools.ietf.org/html/draft-gont-6man-slaac-renum-01 Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-gont-6man-slaac-renum 
> Diff: 
> https://www.ietf.org/rfcdiff?url2=draft-gont-6man-slaac-renum-01
> 
> Abstract: 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 analyzes these problem scenarios, and proposes workarounds
> to improve network robustness.  This document updates RFC4861 and
> RFC4862 to allow for a more robust reaction to network configuration
> changes.
> 
> 
> 
> 
> 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
> 
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
> 
> 
> 
> 
> ********************************************** IPv4 is over Are you
> ready for the new Internet ? http://www.theipv6company.com The IPv6
> Company
> 
> This electronic message contains information which may be privileged
> or confidential. The information is intended to be for the exclusive
> use of the individual(s) named above and further non-explicilty
> authorized disclosure, copying, distribution or use of the contents
> of this information, even if partially, including attached files, is
> strictly prohibited and will be considered a criminal offense. If you
> are not the intended recipient be aware that any disclosure, copying,
> distribution or use of the contents of this information, even if
> partially, including attached files, is strictly prohibited, will be
> considered a criminal offense, so you must reply to the original
> sender to inform about this communication and delete it.
> 
> 
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
> 