IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 14 February 2019 19:13 UTC

Return-Path: <brian.e.carpenter@gmail.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 B8390130E69 for <ipv6@ietfa.amsl.com>; Thu, 14 Feb 2019 11:13:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6W7pST-5ZbPU for <ipv6@ietfa.amsl.com>; Thu, 14 Feb 2019 11:13:11 -0800 (PST)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 D7AF1130DFA for <ipv6@ietf.org>; Thu, 14 Feb 2019 11:13:10 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id 101so3637800pld.6 for <ipv6@ietf.org>; Thu, 14 Feb 2019 11:13:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=bZjn6rL2eDLbFzg+5Uq06jKAwgrkagM5ugeYS+tN4og=; b=fHf7Zxp4z3LgXCnze0RETWak6a4AQPOQ/NgeisQhBGHV9TaoEEUf9NmQ61cf8HrSFI v0Wgo2cyrzOckUIYhEgj+MIUNg9zkUGVdFI373Sitv3umq+GCLIQqJ3jOC6vqWJ18LhZ L4FD6MlVqiTdto2zt/C+uj3Z5ObPmS3R7vUaJ7o199/IVR1BPs/zZ573YpsLKUvh6jkF IokcJWiRZZ8mIsjZ1P5eU0MNiUD09/kRAUnIrKKHC9ESgcBi182bBSGq+RQqrLrkw1md aHweSHvVZykZL+KMfn9L8sMgwEDHAAHQrlGmDiFWCmSheeGbn4lIodP9RYnxZtBxS8bS KzYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bZjn6rL2eDLbFzg+5Uq06jKAwgrkagM5ugeYS+tN4og=; b=Kq4JB59StqoPuQZ2yLXu0LKtqkrNvSwpKE57mQeGru2IOycdLNRqzFE/geDOfc8enx jj3QPqYcQIix0McR4ncCgIveO9ySDq84AliuBRiEjahY2Pymaw37mmqcRbDtSIZf9ARD jw6zQ/Jrpmb8TXAX900yzDEfdl7lp7Vp0VVzhsRp5Zz/npSFEQni5LvU6Ts+5CT5J/L+ pp6n9Zk7p4qEif3Uro5IR5Xgdn4az6jSqKB4IDO4QFDJTF2FMwyiJHzEA8jpCZeo3hXX BGWuNQVoRRDRs87uQX7oftVTZnOfuurST1hOTnP+XJRFR1cO45XT2NRHDXxBQklL6coy iDYA==
X-Gm-Message-State: AHQUAuaGvcKYxUA3Bg0QyvygVHgfLL9hsuCDjs4G6BLzITUIloEnL54t jeoXybmeX8Vo85CUdbkYhyph66xN
X-Google-Smtp-Source: AHgI3IZw0MqOW5p1WLH6CnS0DvFUHauhsFyGibw7yznY5FXYEqMxrBu/Gkz9CSKUSTVtED7gGBn5MQ==
X-Received: by 2002:a17:902:29c9:: with SMTP id h67mr5843619plb.111.1550171589397; Thu, 14 Feb 2019 11:13:09 -0800 (PST)
Received: from [192.168.88.44] ([103.29.31.113]) by smtp.gmail.com with ESMTPSA id e9sm12848588pfh.42.2019.02.14.11.13.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Feb 2019 11:13:08 -0800 (PST)
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Lee Howard <lee@asgard.org>, 6man WG <ipv6@ietf.org>
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <m1gptWx-0000G3C@stereo.hq.phicoh.net> <69609C58-7205-4519-B17A-4FBC8AE2EA16@employees.org> <d40b41c3-ff1b-cab4-a8de-16692a78e8fd@go6.si> <D1E45CAD-08D0-43D4-90F7-C4DD44CB32C0@employees.org> <alpine.DEB.2.20.1902041330531.23912@uplift.swm.pp.se> <46B8DB92-DC81-4242-9780-0D00FB6BDB7A@employees.org> <1c7ebabb-d6f6-d877-d4aa-d6c0fc7d5c60@go6.si> <6278.1549471453@dooku.sandelman.ca> <CAO42Z2xdKtLJV11KXELBKca6CWn=B6Avz6bO_94kFFXaKiZ-pQ@mail.gmail.com> <4602.1549908472@localhost> <CAO42Z2w1swQNuwnrOyTCEMXt0NSyrBx7Ww3kUN-7dfEV=fvk3A@mail.gmail.com> <c16e0e1f-1ed2-ad88-80f1-070bdd8bccca@go6.si> <1F2C2AEE-1C7D-481C-BBA7-7E507312C53A@employees.org> <e56a6e5b-648d-200e-c35d-97f15a31fb2a@asgard.org> <CAO42Z2zh7fKAgQJq9aLCTiFoSSsTeGM=pK3gXitg+gcxH=9fhQ@mail.gmail.com> <d38857c2-6e92-91d6-bb5d-d3eeeb61276a@gmail.com> <CAO42Z2yb47OyXk__Sz-kO00pfcBJgLAhff5DF=mpAddR0iCnAA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <49d76746-66c4-e509-82e5-ef1243db61be@gmail.com>
Date: Fri, 15 Feb 2019 08:13:02 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2yb47OyXk__Sz-kO00pfcBJgLAhff5DF=mpAddR0iCnAA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FCcq2vS2tAcOg_em3VRMNY_uwT8>
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: Thu, 14 Feb 2019 19:13:13 -0000

Mark,

> If this problem was a solved within each application (i.e. the problem
> of unexpectedly failing transport layer connections caused by
> unexpected IP address changes), it doesn't need to be solved at any of
> the lower layers.

Logically that's true of course. But I'm not suggesting that every app
should watch out for this specific cause. I am suggesting that every app
should be written to recover from failing transport layer connections.
As far as I can see, that's already the case in most cases. (Coming
to you via Thunderbird, which seems highly resistant to transport
failures.)

Regards
   Brian

v2.23.0 | Report a Bug | By Email