Re: [Int-area] Using ISO8473 as a network layer to carry flexible addresses

Stewart Bryant <stewart.bryant@gmail.com> Wed, 03 March 2021 10:14 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52CC3A0BB1; Wed, 3 Mar 2021 02:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level:
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qt5GKdghuEmT; Wed, 3 Mar 2021 02:14:52 -0800 (PST)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AC313A0BAB; Wed, 3 Mar 2021 02:14:52 -0800 (PST)
Received: by mail-wm1-x330.google.com with SMTP id n4so5727030wmq.3; Wed, 03 Mar 2021 02:14:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gcuJJPgy/4m1+81sebafOj8r+qKxnCTvrag38qUpd6w=; b=rggx7Mao+u+tjhEU+XM7HwGNMVaoQZ9k/2yv/Qj760TXfCm/UVKdh3M1adoD3AbJFR 1ixw6CODnbiduSvD+MiPDSaSNmpegipMsnJguo1pRB6ckUARK73Y5vjfuWxFgz3W4f+9 QKBObGAEwLpwKCChCGP7DJY+uV7gN6ZAKqJ+gPpJ2KNA8RdLAIK+CUEo3lWKRy0OJ/Bg +hAdAY8GdDefLBjE5uPB5TQlAiybzdU7IdksV79vRG/2Bz+88TAxC5BAlJ9O6ntvuB6r jn70BTYmVm7BcnpZIMZxPOamckn4y3RwRNa+l+NxX0nXM4wQLL8I1BbE6aB2nIZBQuZ/ 6mJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gcuJJPgy/4m1+81sebafOj8r+qKxnCTvrag38qUpd6w=; b=iMoX6QNmFM+Fnwheal6dtp+s5E6OTFFGtsWohB9pDW62YDGrmTkYcSToQ2lj3/nbsE KTVKQ6aMcwOoXxBu2NwlVBiUV2sAOl1RRd6/1yNbiVhKw+anFM8NUVuo0z5kVnjGPnPi rNWQnF+PyRZUcEnrPlJ5j/BSRBZayh77GMJEdjSPFEwO21ZlTJ8i5Fu5xPR+Ai0QU0c1 9a/DNG7tGWPFQTXhUJSJmJH3myi7DzZ9+r/C7m1VpNBa5PcYWWDvCyCTl/p/0lTIAe9P uauk65r6k7xs++OvhYv5Y7DgvFQbXrB38z4H4Gr4r6VV9AXVjH7ybw9bKUu7p2K7wJ0Q oYiQ==
X-Gm-Message-State: AOAM530UJmkxStXexL/r49SnXnl1Y7vuFrJjaJs4kSwCf1kpcwT/1o2+ NZF3jMa4rJgZc5NeuXGWJG4=
X-Google-Smtp-Source: ABdhPJzESOkcqbFe5giUnVMBgMCWWW+8Kxm/mFor4Uvwg8LTGomjOLoD/lMwUdjXYL1pTaNwERK5mQ==
X-Received: by 2002:a1c:cc14:: with SMTP id h20mr8367807wmb.14.1614766489614; Wed, 03 Mar 2021 02:14:49 -0800 (PST)
Received: from broadband.bt.com ([2a00:23c5:3395:c901:509c:c49d:e999:d998]) by smtp.gmail.com with ESMTPSA id r7sm31819752wre.25.2021.03.03.02.14.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Mar 2021 02:14:49 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <e9fa4b47-7020-29cf-ff49-0dbb98573bab@gmail.com>
Date: Wed, 03 Mar 2021 10:14:48 +0000
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Toerless Eckert <tte@cs.fau.de>, "draft-jia-flex-ip-address-structure@ietf.org" <draft-jia-flex-ip-address-structure@ietf.org>, "draft-jia-scenarios-flexible-address-structure@ietf.org" <draft-jia-scenarios-flexible-address-structure@ietf.org>, int-area <int-area@ietf.org>, Jiayihao <jiayihao@huawei.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <93BF016D-47C0-4D05-BA70-B326CBFBD999@gmail.com>
References: <CDB32FF0-5CE0-4C0F-B1D1-B6BFEA42E817@gmail.com> <3dd5a712bd2b4fdbb882d860ab2ece82@huawei.com> <7A6DB0D7-A2A3-4995-A6D9-ABDFF4F7879B@gmail.com> <20210301153259.GB11539@faui48f.informatik.uni-erlangen.de> <3ee2a63b-45db-b296-d6da-c1b4263b8fd6@gmail.com> <2233700F-9AFF-472B-B3BF-33226339DB6E@gmail.com> <e9fa4b47-7020-29cf-ff49-0dbb98573bab@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/0z41BZm7Nj5LRXnFrgqKHpwGZGs>
Subject: Re: [Int-area] Using ISO8473 as a network layer to carry flexible addresses
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2021 10:14:54 -0000


> On 2 Mar 2021, at 20:15, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 03-Mar-21 01:32, Stewart Bryant wrote:
>> 
>> 
>>> On 1 Mar 2021, at 20:08, Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>>> 
>>> 
>>> It would take but a minute to design a longer-address mechanism for IPv6, although I don't have space to include it in the margin of this email**. But it would take many years for it to be widely implemented and deployed, during which time the Internet would be opaque to such addresses.
>>> 
>>> 
>>> ** Basically, use a prefix such as fb00::/8 to indicate an extended address.
>> 
>> Hi Brian
>> 
>> Basically I think that this fails the backwards compatibility text.
> 
> Short answer: that's why the Internet would be opaque to it for many years.
> 
> Longer answer: change every router in the universe (exactly what we did to achieve the universal deployment of IPv6). At that point, changing the ethertype/IP version is really not that different than demultiplexing packets by looking at the first byte of the source address.
> 
> But I am not seriously advocating any of this. If I'd believed this was a viable approach, I would have advocated one of the IPng proposals that extended IPv4 addressing in that way.
> 

Fundamental to moving this discussion forward is an understanding of what the future structure of the Internet will be.

Will it be the classical model of client-edge-aggregation-core-agregarion-edge-server with large quantities of traffic going through the core, or will it be client-edge-server for the majority of traffic with server-server to build the application running in a private network and only a minority of traffic still running using the classical model?

If the Internet evolves to the client-edge-server model there is an opportunity to migrate away from the worst effort model that currently constrains us, to a model that provides the service that the customers are prepared to pay for.

If there is a viable commercial case for higher quality services provided at the edge, then than will happen, regardless of any decisions we took 20 years ago which currently limit our ability to evolve the network layer, and regardless of any position that the IETF takes to block it. At the end of the day it all comes down to economics, and it is currently unclear whether the classical model will prevail or a new model will develop, or indeed if there is a change, when and how fast it will transition.

- Stewart