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

Gert Doering <gert@space.net> Thu, 21 February 2019 07:35 UTC

Return-Path: <gert@space.net>
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 90149126C15 for <v6ops@ietfa.amsl.com>; Wed, 20 Feb 2019 23:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 tYn1XnL_cB4Y for <v6ops@ietfa.amsl.com>; Wed, 20 Feb 2019 23:35:33 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27790126C01 for <v6ops@ietf.org>; Wed, 20 Feb 2019 23:35:32 -0800 (PST)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 145BD41CDB for <v6ops@ietf.org>; Thu, 21 Feb 2019 08:35:31 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id F3F3E41B57; Thu, 21 Feb 2019 08:35:30 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id E610EB740D; Thu, 21 Feb 2019 08:35:30 +0100 (CET)
Date: Thu, 21 Feb 2019 08:35:30 +0100
From: Gert Doering <gert@space.net>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Message-ID: <20190221073530.GT71606@Space.Net>
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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="Q3LtICoXRyWKz3HA"
Content-Disposition: inline
In-Reply-To: <CAKD1Yr0HBG+rhyFWg9zh0t3mW486Mjx9umjn+CRqAZg4z9r0dg@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.11.2 (2019-01-07)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6E-ZqLjmK63IwLPu898EA6Okop4>
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: Thu, 21 Feb 2019 07:35:36 -0000

Hi,

On Thu, Feb 21, 2019 at 08:43:21AM +0900, Lorenzo Colitti wrote:
> Because the advantages are for network operators have corresponding
> disadvantages for application developers and thus for users. Application
> complexity and brittleness due to NAT traversal. Battery impact of NAT
> keepalives. Higher-latency due to relaying and rendezvous. And so on.

NPTv6 does not need state, so no keepalives and battery impact.

Applications today seem to be all "HTTP(S)" or "QUIC", and they all had to
learn how to deal with NAPT.  New protocols that embed IP addresses are 
killed by IPv4 NAPT anyway, so that ship has sailed - and everything that
doesn't care about embedded IP addresses will nicely work throug NPTv6.

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