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

"Olopade, Olorunloba" <> Tue, 20 October 2020 23:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9D7083A07BD; Tue, 20 Oct 2020 16:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 x4CPXA_1v8z7; Tue, 20 Oct 2020 16:19:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8853B3A07B7; Tue, 20 Oct 2020 16:19:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=mailrelays; t=1603235951; x=1634771951; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version:content-transfer-encoding; bh=Y3qQAZYTvc705ES29nYDzYMotVkTFfYJk62FYcxH/4k=; b=QE2XFhoBP2ZVHp/iXXSvIznhFb5fO4tE2tuDrkOtH4NJ+DU8gixo1aDK /nLbWgt+g5OtbYdpMGxgE3E1R2QeMbmRCpo9bSGBnaQoijpBPJmaemojC aWThJXl/PThOmYGfTQimI2Pwyts1Bo/YqI4X37qdZyC6aPvCc/qtcqoAs 8=;
IronPort-SDR: Vr+IlthqSI/7WlnwXoa90XXtxNGROnoCkwFPNCkEsG0OO5Vh5vx1sfxV139maCeGtMdOVNv6Ii x72bkx98GGYg==
X-AddDisclaimer: Media
X-NonCorpAttach-CLI: false
From: "Olopade, Olorunloba" <>
To: Philip Homburg <>, "" <>
CC: 6man <>
Thread-Topic: [v6ops] New Version Notification for draft-olopade-6man-slaac-signaling-00.txt
Thread-Index: AQHWpu3EqPfc7oeAUkOb/UoGeTcid6mhIDaA
Date: Tue, 20 Oct 2020 23:18:54 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [v6ops] New Version Notification for draft-olopade-6man-slaac-signaling-00.txt
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: Tue, 20 Oct 2020 23:19:14 -0000

Hello Philip,

Not sure which mature solutions you are referring to. Are these standardised?

In my opinion, to comprehensively deal with robustness issue with SLAAC, we need to make changes to both hosts and routers. 

-----Original Message-----
From: [] On Behalf Of Philip Homburg
Sent: 20 October 2020 15:31
Cc: Olopade, Olorunloba <>uk>; 6man <>
Subject: Re: [v6ops] New Version Notification for draft-olopade-6man-slaac-signaling-00.txt 

In your letter dated Mon, 19 Oct 2020 18:53:56 +0000 you wrote:
>I'm proposing an alternate way to address the SLAAC flash renumbering 
>issue, a nd I've been advised to put this in a draft. This is the 
>initial draft, and de finitely need more work, but will like to know if 
>people think this approach i s worth considering.

The mechanism proposed in this draft could work if carefully specified to deal with edge cases (for example "poor man's multihoming").

However, for this to work changes are required to both routers and hosts.
If the router is a CPE, then we already have quite mature solutions that don't require changes to hosts.

This would do nothing for hosts behind old CPEs. 

This draft could provide a solution of hosts that get moved to a different VLAN. However, the need to update both hosts and router makes it more attractive to find a solution that only requires hosts to be changed.
Save Paper - Do you really need to print this e-mail?

Visit 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

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