IETF Logo Mail Archive

Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios

Lorenzo Colitti <lorenzo@google.com> Thu, 21 February 2019 23:55 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 BC16A1312B9 for <ipv6@ietfa.amsl.com>; Thu, 21 Feb 2019 15:55:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level:
X-Spam-Status: No, score=-17.5 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, URIBL_BLOCKED=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 wyyzoQil2QKt for <ipv6@ietfa.amsl.com>; Thu, 21 Feb 2019 15:55:05 -0800 (PST)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 C5A73130E0A for <6man@ietf.org>; Thu, 21 Feb 2019 15:55:04 -0800 (PST)
Received: by mail-io1-xd30.google.com with SMTP id r136so377220iod.3 for <6man@ietf.org>; Thu, 21 Feb 2019 15:55:04 -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=A3TmlL5ornOSugvsKCuzDNK+EZ9Sis/zk1UESWHFfGQ=; b=EUwnq0RHbXcLSOMuBeFKeQ7v2a9gIcGsWW2NBmLYCiwe7QL3F5hnzm/pVL9oSR/Kpv xwXDDFN6yx1mJFLWHpbdWw7KnVmjsi7Zx7X9BXOeU37FhkWFsiNP0NJbcG3vjqqRykgc U4ho02lLwONxTDnaL2dM18kwmCfn2TW6lfS+qJeaGFMICcsmECxugUr8Ppqwnetk1FJI C35TjJ+T9jLlAuPy58YkHl3tKQA7aL7JyPibu7BC2Ty+bnkN6pksEIs2a9vJd2tvR0ml 3yOwy4Nj+b/E2sMgJxlo44aRiN3Y/WHSRkZ5uafCuzHvvQ7AMqmv+IB0Cpy8jSECKprN huyw==
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=A3TmlL5ornOSugvsKCuzDNK+EZ9Sis/zk1UESWHFfGQ=; b=uPai+eHcQexk5Lo0/bx3D6ZjGUCFEAL4zsTdbw3fZ0YRIbt4ZvygR+yOLd5BuybQEi L6k3kKaV0ZFIAtDEAnt6fLnle3oRhgEeCw8qrjiyjzN/zU+k6k5coUdt1pk3ppic9yCY VO/qWWEG+PBZqoYXeSRTSzD2yhwmXngtyFepNVutRzma1Q6RJ/jvqRyWzVk6RbWt81p7 07xFo48Mbsv+o2MGf6h2xmZRzd6KVcE/V4W1ccmOwZugYOeir2IVfCFYWMwpw9embDKt 1eqRzloV0lGxGVvL2JhyoEqi3g1ErrMjxx1UeQfpTN4i8m6bisiqIjIWG6qWnFYVSP5s 54jA==
X-Gm-Message-State: AHQUAuaVqk5Gz8NXskszRitT/NNB032E06e9IvxymorUyqTgjnFxWBie MFVOfgjez/6Njz56Ym8yeieNP7hGpOdwPWX0TtMa4A==
X-Google-Smtp-Source: AHgI3Ibsk4aLBvK1WsSm8CGYygZTH+VvOiDfFY+Gma0RFyggwaYJ381ukFn+jPlpajXLQkrxbW6779fQUM/Dsr1WXOc=
X-Received: by 2002:a5e:9912:: with SMTP id t18mr768064ioj.14.1550793303672; Thu, 21 Feb 2019 15:55:03 -0800 (PST)
MIME-Version: 1.0
References: <6D78F4B2-A30D-4562-AC21-E4D3DE019D90@consulintel.es> <B6E2EC33-EEAF-40D0-AFCC-BDAFA9134ACD@consulintel.es> <20190220113603.GK71606@Space.Net> <28fbc2c305c640c9afb3704050f6e8d7@boeing.com> <20190220213107.GS71606@Space.Net> <019c552eb1624d348641d6930829fd1f@boeing.com> <CAKD1Yr0HBG+rhyFWg9zh0t3mW486Mjx9umjn+CRqAZg4z9r0dg@mail.gmail.com> <c86c9322-743c-477b-ad8a-373ce47ace6e@si6networks.com>
In-Reply-To: <c86c9322-743c-477b-ad8a-373ce47ace6e@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 22 Feb 2019 08:54:49 +0900
Message-ID: <CAKD1Yr1g3nMVJt-dTuV+bGu+4GthNDj7tJiA5OdbFf2fd0-zrA@mail.gmail.com>
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
To: Fernando Gont <fgont@si6networks.com>
Cc: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fcbcc505827033aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Wi3r0AHbXZ96NSDpqM2-S47YkI8>
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, 21 Feb 2019 23:55:07 -0000

On Thu, Feb 21, 2019 at 10:35 AM Fernando Gont <fgont@si6networks.com>
wrote:

> Given that RFC6092 recommends "only allow outgoing connections",


RFC 6092 recommends no such thing.

v2.23.0 | Report a Bug | By Email