Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

Owen DeLong <> Thu, 31 October 2019 23:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D28C2120824 for <>; Thu, 31 Oct 2019 16:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qNsZMUEy68Vz for <>; Thu, 31 Oct 2019 16:17:57 -0700 (PDT)
Received: from ( [IPv6:2620:0:930::200:2]) by (Postfix) with ESMTP id E4415120026 for <>; Thu, 31 Oct 2019 16:17:50 -0700 (PDT)
Received: from [] ([]) (authenticated bits=0) by (8.15.2/8.15.2) with ESMTPSA id x9VJc4ig024527 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 31 Oct 2019 12:38:05 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 x9VJc4ig024527
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=mail; t=1572550686; bh=WfEgN3vpy6lYv+gn9ike8sv8srQDubeyBLmf3+JSRnU=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=1xqrCXcbzyL4mVULu6ZA19QuHVkplJh0TGWOhDbhMTeMPpO1eDFZ2mHYVFcglc07t F/VGZVTvTZC9aJmYaC5uoTS1I+dZXesFRNmil07HXQ3f4Zo54ueEdagvOYShz1eUgS iKvj+x/fJRiHBZjfcDZyZoGj65fY3g25aX4hb68M=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Owen DeLong <>
In-Reply-To: <>
Date: Thu, 31 Oct 2019 12:38:04 -0700
Cc: Ted Lemon <>, v6ops list <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Fernando Gont <>
X-Mailer: Apple Mail (2.3445.104.8)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 ( []); Thu, 31 Oct 2019 12:38:06 -0700 (PDT)
Archived-At: <>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Oct 2019 23:17:59 -0000

> On Oct 31, 2019, at 12:21 PM, Fernando Gont <> wrote:
> Hello, Ted,
> On 27/10/19 09:02, Ted Lemon wrote:
>> Indeed, this would also not actually solve the problem.   At present,
>> the ISPs are doing something that is out of spec and causes problems.
>> If we “fix” this by accommodating what they do, does that help, or
>> does it just encourage them to continue doing it?
> Did happy eyeballs encourage broken IPv6 connectivity, or did it
> actually help IPv6 deployment?

Considering these mutually exclusive is a false dichotomy.

It did both.

>> What should be happening on the host with a prefix that’s deprecated
>> is that TCP connections should be timing out.   This doesn’t take
>> very long.  
> ~9 minutes, IIRC.

Somewhat variable, but yes, can be as long as ~15 minutes in some cases.

>> First of all, fix CPEs so that they definitely support clean
>> deprecation of prefixes using PD.
> But robustness cannot rely on any of these specific bits.

Perhaps not, but this is the lowest hanging fruit and the cleanest set of changes.

Certainly you have to admit that the proposed CPE changes would yield the greatest improvement
in robustness at the lowest cost of any of the proposed solutions in the I-D in question.

>> When another RA arrives, see if it was signed with the same key.   If
>> so, it came from the same router, and can be trusted to update
>> whatever information that router sent, including flash-deprecating a
>> prefix.   If not, ignore it.
> In the non-SEND trust model, you do trust the local router. Why did you
> trust the local router to configure your network, but not for
> deprecating the prefix?

Trusting the local router to configure the network to add a previously non-operational host to the network has a somewhat different set of consequence for failure than trusting whatever on-link host wishes to tell you to effectively shut down your currently operating network connection.

Especially when you consider that such an announcement can be sent to the all nodes on link multicast address, effectively dropping them all at once.

I agree it’s not a huge difference, but, it is a difference and certainly the scope of the resulting problem can be much larger than the case of individual host configuration.