Re: A common problem with SLAAC in "renumbering" scenarios

Lorenzo Colitti <lorenzo@google.com> Wed, 20 February 2019 07:36 UTC

Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82724130EF3 for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 23:36:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.501
X-Spam-Level:
X-Spam-Status: No, score=-17.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id luZkG78MD0e3 for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 23:36:02 -0800 (PST)
Received: from mail-it1-x134.google.com (mail-it1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F63D130DCB for <ipv6@ietf.org>; Tue, 19 Feb 2019 23:36:02 -0800 (PST)
Received: by mail-it1-x134.google.com with SMTP id x131so13070267itc.3 for <ipv6@ietf.org>; Tue, 19 Feb 2019 23:36:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sJRNdQwtyxOlcizTE9JV65LOB9nb2unQw4K719+K720=; b=SLf/t8zBQgcuGBTNBe3ZR0JE89CEHt73AzAUvQ3Pq2LhnHfzaun79ybrajqZ+QghOi mqWgbBYAt8gTYmMnf4VOK4ujFxCD+OE5u/W8FzhfmmcjiG1VcwIgtiOkc99Lztxc5MLy tujVKsd1YvYJFf5MbSYvGp0772zV2bbvjI5rnx/YMMHDWc6EeGcw1pubNLUMjCUVCRlw 8fefQAm9sd3vUcDGn1TtL1Yi3Cb5kelMcUhw3YOJ1q76CZSXsmeFarElv5UgizYc4Nqp N/HzFb/npKE3NvHYKi5AaP8w4zeR9qQ/eUh5YqugJM1by22BGJmWKEOCd+cP8odWec0g DYfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sJRNdQwtyxOlcizTE9JV65LOB9nb2unQw4K719+K720=; b=X3APa1vFjqMx/s+WG0ylQlocmMA9Cg6WcedQ5yw+d6xjWyyohPNDH5QfsltHyIf5dp z0UCTPwsL9spYG0ZyH97jl47uTf+CeRhYhsXu11CqsMOvJRZbiQsdVg2eQ/QNrwJy90O w6r/2R9SKhPUXPQyMoFd1Q/zZXLCywVshN/xOQzDhW3nMadX9Iq5xNmbFrNueCUG0l9X OzupyhXA3JOtGQ+O3LcRUyEqrOSgoqhJwMW5fnFRCpCN56scbIRSXgRnk0CIirkfmVDp zTPP3bZKpplaRHz9IeCau8C1ht11LNJV+++63NUH8XmoimwxCgm6BUfvP1AhiyHqaaI3 E3Gw==
X-Gm-Message-State: AHQUAubH1bnBoS4X2JPfiQugk3I2aImQs8TKBzmw48x9HQiVPs0rmqbB vKnlzDeEczXc27yyShlZvre0hQupySy3Xi13uPWIZ4qz
X-Google-Smtp-Source: AHgI3IZttMEzbndr+lmmwQ+Sh2pAOb1EM1TyLnK2GvUZ3hXJEIBym1eUR+ocPVWGnui/CWefW/jqmPSAr6mWom+R0QM=
X-Received: by 2002:a05:660c:3cd:: with SMTP id c13mr5289748itl.134.1550648161024; Tue, 19 Feb 2019 23:36:01 -0800 (PST)
MIME-Version: 1.0
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <CAHL_VyCMpCcGkEQu+RV1GRf2QLB-HD0+AOOBV0YhfQ5sbydVzQ@mail.gmail.com> <8CE7A0CD-97D9-46A0-814D-CAF8788F9964@consulintel.es> <e3e0bf2273e04f15b792665d0f66dfe5@boeing.com> <4c5fab33-2bff-e5b5-fc1d-8f60a01a146d@go6.si> <b4525832-9151-20bf-7136-31d87ba6c88d@huitema.net> <463f15cf-2754-e2e8-609d-dc0f33448c6c@go6.si> <ff649810-7242-7bc2-d36f-3f998f7bdd71@asgard.org> <9CDF41CA-83B4-4FC4-B995-EF79727C5458@steffann.nl> <CAO42Z2wA+vLmU7+sU6xLK7TO6pWfNQA5shs9zp=PqANCihLmBQ@mail.gmail.com> <BAB3061A-1808-4C0E-AA1B-2D7DD5BA63FC@employees.org> <bbd8b761-403a-5b3f-3f04-dc3bfdea116e@foobar.org> <6F3036C6-50A1-43C6-B554-31293B69E59D@employees.org> <433607c1-dbc6-a42e-cb17-dc209e33bdaa@si6networks.com> <12EA4FAE-BE3D-4CFE-9837-DF052F79A998@employees.org> <5bc3eaf0-3ef0-d954-b228-00a7faac7f4c@si6networks.com> <CAO42Z2wa9gWoB_bWrYt79urHF8ihmMAbjDSZCBoZa8dn8SCNFw@mail.gmail.com> <alpine.DEB.2.20.1902200735480.24327@uplift.swm.pp.se> <CAO42Z2xwyes97LAy1duXpJMeknJhmkA6yV-tWCPLmw6QvOuKbQ@mail.gmail.com>
In-Reply-To: <CAO42Z2xwyes97LAy1duXpJMeknJhmkA6yV-tWCPLmw6QvOuKbQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 20 Feb 2019 16:35:49 +0900
Message-ID: <CAKD1Yr0t8MEg-SRukTKM9VjLSaJB4tc-uhxJkX2U-3gQX2PvWQ@mail.gmail.com>
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cfb07705824e6815"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/PXhoX_7JW9nplqZS30zGhuswoes>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2019 07:36:08 -0000

On Wed, Feb 20, 2019 at 4:19 PM Mark Smith <markzzzsmith@gmail.com> wrote:

> So while the addresses were removed from the interface, the TCP
> connection entirely survived that, and treated the link down/up event
> as a period of packet loss.
>

That doesn't really make sense on a mobile platform. When you switch from
wifi to cell data, you probably don't want to keep that connection alive
until that specific wifi network comes back. Instead you want to give the
app an error as soon as possible so it can retry the failed connection on
the new network. On Android, TCP connections are closed the instant their
IP address goes away. I don't know what iOS does.