RE: Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

2022-08-31 Thread Vasilenko Eduard via NANOG
itself. Eduard -Original Message- From: Fernando Gont [mailto:fg...@si6networks.com] Sent: Wednesday, August 31, 2022 4:12 PM To: Vasilenko Eduard ; nanog@nanog.org Subject: Re: Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum) Hi, On 31/8/22 09:43, Vasilenko

Re: Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

2022-08-31 Thread Fernando Gont
Hi, On 31/8/22 09:43, Vasilenko Eduard wrote: Hi all, The router could split information between RAs (and send it at different intervals). It may be difficult to guess what is stale and what is just "not in this RA". You ask the router, and the router responds. If you want to consider the ca

RE: Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

2022-08-31 Thread Vasilenko Eduard via NANOG
ust 31, 2022 1:35 PM To: nanog@nanog.org Subject: Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum) Folks, We have been discussing the potential problems associated with SLAAC renumbering events for a while now -- one of the most common cases being ISPs rotating home pre

Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

2022-08-31 Thread Fernando Gont
Folks, We have been discussing the potential problems associated with SLAAC renumbering events for a while now -- one of the most common cases being ISPs rotating home prefixes, and your devices ending up with stale/invalid addresses. We have done quite a bit of work already: * Problem st