IETF Logo Mail Archive

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

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

Return-Path: <prvs=1954f3d980=jordi.palet@consulintel.es>
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 4E15312D826; Wed, 20 Feb 2019 03:26:24 -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 XOkttRBz8_ue; Wed, 20 Feb 2019 03:26:22 -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 AD18B128CF2; Wed, 20 Feb 2019 03:26:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1550661979; x=1551266779; 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=t/fJ7d3wv+7zFkAPRU3vxeoNnTYeOFitHBc5TZJIiIM=; b=TKyxY/tbRsLq7 g7thy2oqGnPldyCSuEZ3DEBOpR2KbiPCe+Q1/92thsLktPAL1HPi4+8quLlFgr0m Az7S8Uqw/ue0lbaCIcqBDb6idT5JBVrY4URsBRaLo1taypdW4L2VjbvuBC6b0hOE ZOm5ojVaZ5mNgoLi5VZa2m1HOhCSG4=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 20 Feb 2019 12:26:19 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 20 Feb 2019 12:26:17 +0100
Received: from [10.10.10.160] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50006161532.msg; Wed, 20 Feb 2019 12:26:17 +0100
X-MDRemoteIP: 10.8.10.10
X-MDHelo: [10.10.10.160]
X-MDArrival-Date: Wed, 20 Feb 2019 12:26:17 +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:26:08 +0900
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
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: <6D78F4B2-A30D-4562-AC21-E4D3DE019D90@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/ipv6/7Ter4T1pHbBn4Jm7Wj07gA4joq0>
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 11:26:24 -0000

Ok, so let's go for IPv6 PI for every household, business, etc. ...

Regards,
Jordi
 
 

-----Mensaje original-----
De: ipv6 <ipv6-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
    
    --------------------------------------------------------------------
    IETF IPv6 working group mailing list
    ipv6@ietf.org
    Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    --------------------------------------------------------------------
    



**********************************************
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.

v2.23.0 | Report a Bug | By Email