Re: [arch-d] ipv4 and ipv6 Coexistence.

Toerless Eckert <tte@cs.fau.de> Tue, 25 February 2020 20:24 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7ACD3A1532 for <architecture-discuss@ietfa.amsl.com>; Tue, 25 Feb 2020 12:24:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 y0EmWfCjDQHp for <architecture-discuss@ietfa.amsl.com>; Tue, 25 Feb 2020 12:24:09 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 052043A1533 for <architecture-discuss@ietf.org>; Tue, 25 Feb 2020 12:24:08 -0800 (PST)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id D2424548005; Tue, 25 Feb 2020 21:24:03 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id C6B34440040; Tue, 25 Feb 2020 21:24:03 +0100 (CET)
Date: Tue, 25 Feb 2020 21:24:03 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Fred Baker <fredbakersba@gmail.com>
Cc: Mark Andrews <marka@isc.org>, architecture-discuss@ietf.org
Message-ID: <20200225202403.GG39574@faui48f.informatik.uni-erlangen.de>
References: <PR3P194MB0843ACAE01F33CEC57266A1AAE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <EDAE6375-EE0B-4864-9834-C1FBC209D581@sobco.com> <PR3P194MB08431E138262F2A43C1D0621AE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <8ADEA0E1-291A-4400-9925-F65A26116372@consulintel.es> <PR3P194MB0843939F3B38426960A66E70AE130@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <D8063303-7DDA-41F8-A63A-C0244E3E9E25@isc.org> <20200224222715.GA49892@faui48f.informatik.uni-erlangen.de> <28C4725E-E4C5-4937-835F-C6DEA9B710CF@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <28C4725E-E4C5-4937-835F-C6DEA9B710CF@gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/obW84oFazWM66_HP1PwwXxhyYtU>
Subject: Re: [arch-d] ipv4 and ipv6 Coexistence.
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2020 20:24:11 -0000

Thanks, Fred, inline

On Tue, Feb 25, 2020 at 10:16:24AM -0800, Fred Baker wrote:
> On Feb 24, 2020, at 2:27 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > In private / controlled networks, the choices are not only IPv4 vs.
> > IPv6 or their interop, but also (SR-)MPLS and even more so L2 ethernet
> > switching.
> 
> You make some important points, but...

> We have had several countries discuss pulling off the Internet or doing something pretty disruptive, such as unilaterally changing from DNS to something else or imposing government-controlled firewalls. My point to them - and I have spoken with more than one - is that disrupting Internet communications affects the flow of international commerce, and therefore money, into their countries.

Let me answer this further below.

> The same point applies in this case. If a company wants to internally only use <something> as a link layer protocol, that's their choice, but if they step very far away from IPv4 and IPv6, it means that they can't do business with their vendors and their customers - they have to in some way translate or overlay at that boundary. What has been beneficial with Internet technologies since they were invented was that one no longer had to think about global deployments of BBN 1822, X.25, Ethernet, or any of a long list of other things; they became carriers for a common architecture enabling global communications.

I think its dismissive to call private or controlled networks
"link layers".  They include global enterprise, service provider, defense,
federal and other federated networks, manufacturing and the like. 

The Internet already is an overlay of sorts and the heavy lifting is
done below it by those private/controlled network re-using IETF TCP/IP
technologies, and a lot more than "The Internet".  Including the likes
of MPLS, SRv6, DiffServ, heck even IntServ or *yikes* IP multicast. And
parts of the IETF are still treating innovation to improve those type of
networks as tangential or subordinated to comply with policies really only
built just with "The Internet" use-case in mind.

Making future IETF technologies better support where the heavy lifting
is done is what i think would serve the IETF well.

[rant]
About your first point: I think that additional entities like
governments "breaking" the Internet is a completely separate point,
from the one i made and argued above.

The vision of the transparent global Internet was a great vision to
me until 1995 when the Internet population exploded and IMHO the 
model started to fail. Since then, the mayority of TCP/IP hosts
connects to the internet through some type of policy filtering,
and the IETF has architecturally not really acknowledged
that reality or the need for it. How are countries policing the
Internet for their constituencies now any different from enterprises
having done the same for decades for their constituencies ? What
else but closing its eyes to the issue did the IETF do in the last 25
years ?

And now its easy to see how a limited number of regulated
"WWW service conglomerates" will happily claim to solve all policy
requirements at their application/gateway level. Because IETF
networking architecture has failed to evolve the "Internet" model to
something a little more based on reality of human society than the
original Internet garden of Eden model that is still canon.
[/rant]

Cheers
    Toerless