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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Wed, 20 February 2019 11:25 UTC

Return-Path: <prvs=1954f3d980=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF7812D826; Wed, 20 Feb 2019 03:25:07 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 ADAm7cs00o0y; Wed, 20 Feb 2019 03:25:05 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1302C128CF2; Wed, 20 Feb 2019 03:25:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1550661903; x=1551266703; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=ZXH3m08NXx5GNZyWOqafKkF8zwxiO+fnAp2pZ6BmtOw=; b=K+e47Ud5VG1bK nZkKtxMAjRCxpV4O0lH2Yl3gDNb1zNA/ZJc0lgAsS1hLmnfm18UwWdLAZjdWk9/q uyDzMxsFV8K57Fgaby12Bb60yiMHxNyzEtH7yzeQ4c41Po9NF2Cnisn2qOs30ixA WIMcWmq1XJf/MCHmmI7x95QGkfJzsA=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 20 Feb 2019 12:25:03 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 20 Feb 2019 12:25:02 +0100
Received: from [10.10.10.160] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50006161528.msg; Wed, 20 Feb 2019 12:25:02 +0100
X-MDRemoteIP: 10.8.10.10
X-MDHelo: [10.10.10.160]
X-MDArrival-Date: Wed, 20 Feb 2019 12:25:02 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1954f3d980=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/10.10.7.190210
Date: Wed, 20 Feb 2019 20:24:51 +0900
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Gert Doering <gert@space.net>, Nick Hilliard <nick@foobar.org>
CC: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Message-ID: <B6E2EC33-EEAF-40D0-AFCC-BDAFA9134ACD@consulintel.es>
Thread-Topic: [v6ops] A common problem with SLAAC in "renumbering" scenarios
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <alpine.DEB.2.20.1901311236320.5601@uplift.swm.pp.se> <35adea8e-704a-76f2-857f-a83a9ad689ef@si6networks.com> <CAFU7BAS1_veTu-ZXAF0MF4niJwz149nGipx3ep_6fh1bewOzgg@mail.gmail.com> <d9503983-6524-a13a-2cb0-cdcb95f76ea6@si6networks.com> <CAFU7BAQfg712UfgW9wi9pd3eVeZP9cqJEXd6=FDmchuSdauv+g@mail.gmail.com> <82c00442-bbc4-581b-2054-2d02d50d20ad@si6networks.com> <CAFU7BASDgmSwY=SLiabSqyiTOphxU0COtFLQvT8drm0iTxM+-Q@mail.gmail.com> <CAHL_VyDf5Dnh+2uE1=V3DL2P4vABSZ4dR8oOOveBzf2Fmj0xXA@mail.gmail.com> <27cc7a26-1ce1-38cf-4fc8-35032cf757dc@foobar.org> <20190220112256.GI71606@Space.Net>
In-Reply-To: <20190220112256.GI71606@Space.Net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/KaubP1sxFdCRWMDtuwyMO9ILh0c>
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2019 11:25:08 -0000

What a sacrilege!

Regards,
Jordi
 
 

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Gert Doering <gert@space.net>
Fecha: miércoles, 20 de febrero de 2019, 20:23
Para: Nick Hilliard <nick@foobar.org>
CC: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Asunto: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios

    Hi,
    
    On Wed, Feb 20, 2019 at 11:08:50AM +0000, Nick Hilliard wrote:
    > Add some NAT on the CPE and this entire problem goes away!
    
    NATs are good!
    
    (Seriously, given what a train wreck IPv6 seems to become, NPT and
    ULAs or IPv6 PI inside is increasingly looking more attractive...)
    
    Gert Doering
            -- NetMaster
    -- 
    have you enabled IPv6 on something today...?
    
    SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
    Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
    D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
    Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.