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

Gert Doering <gert@space.net> Thu, 21 February 2019 21:53 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 6114B13125D for <v6ops@ietfa.amsl.com>; Thu, 21 Feb 2019 13:53:08 -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 XOlfUB875PGB for <v6ops@ietfa.amsl.com>; Thu, 21 Feb 2019 13:53:05 -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 7E0C6131238 for <v6ops@ietf.org>; Thu, 21 Feb 2019 13:53:05 -0800 (PST)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 258B540AD6 for <v6ops@ietf.org>; Thu, 21 Feb 2019 22:53:03 +0100 (CET)
X-SpaceNet-Relay: true
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 040FF40084; Thu, 21 Feb 2019 22:53:03 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id DDE14B85B4; Thu, 21 Feb 2019 22:53:02 +0100 (CET)
Date: Thu, 21 Feb 2019 22:53:02 +0100
From: Gert Doering <gert@space.net>
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Gert Doering <gert@space.net>, Lorenzo Colitti <lorenzo@google.com>, "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Message-ID: <20190221215302.GU71606@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> <20190221073530.GT71606@Space.Net> <CAO42Z2wmB2W52b4MZ2h9sW5E9cQKm-HRjyf--q8C26jezS7LXQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="vOedOGAU6TSXepIO"
Content-Disposition: inline
In-Reply-To: <CAO42Z2wmB2W52b4MZ2h9sW5E9cQKm-HRjyf--q8C26jezS7LXQ@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/YgHtmsy33i-i5LuW4ifa8aE18Fg>
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 21:53:14 -0000

Hi,

On Fri, Feb 22, 2019 at 08:40:24AM +1100, Mark Smith wrote:
> > 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 -
> 
> Getting it back in IPv6 is one of the things I hope we can get.
> 
> That's because applications that would be best performing, most robust and
> more secure with a peer-to-peer communications model are forced to adopt an
> absolute client-server model (where the server is a much more likely
> performance bottleneck, the server becomes a SPOF for all clients using it
> at the time, and the server is a natural interception point for a malicious
> server operator).

Have you looked out there recently?  None of the big actors in the market
seem to have any particular interest in moving away from a "we are the cloud 
content players, you are just visiting clients" model.

(The gaming industry has, to some extent, but that doesn't seem to be
a really strong driver)

[..]
> Another analogy to show the significance is that with NAT in the telephone
> network, it wouldn't be possible for me to give you this phone's number to
> call me. Would any of us accept that constraint on the usability of our
> phones?

When did you do the last phone call on your mobile tablet-like computer 
thingie?

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