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

Stewart Bryant <stewart.bryant@gmail.com> Tue, 02 March 2021 12:32 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 3C19F3A171C; Tue, 2 Mar 2021 04:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 YlYb-53RYAny; Tue, 2 Mar 2021 04:32:56 -0800 (PST)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 99CC63A171B; Tue, 2 Mar 2021 04:32:56 -0800 (PST)
Received: by mail-wm1-x331.google.com with SMTP id w7so2060155wmb.5; Tue, 02 Mar 2021 04:32:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Bd/7PUHSVj5FSLNXwfwGDpjkTP1tvjpxQIv9SqgE72E=; b=txT+1x/7HnegHRpjXsk2EG4DeiBcasrCuLAWaYkkRM/bp1x3iGl46Jt412x8vrHxsX fAArKtS6Hc3CxWtiBM/gPnDiSn5tPa8JNFuPOpM5Ayl/tUqPYl0Fs9HIsyw9U86XGPq2 NW/bWyTz7J+UEau87O6tdL02d1C103b0/WFq5bDtIspI9mGIJ5iJsyb3/pudL0uWvlaK ZQGECXE2a8A/g01+vpappy/jedFd28mx4VC7d+GsaNkRc9LkcX7cdNcVhxejDZMW8V2N CX3tPcX7f1EnlYVS0bQPzXRsXuRwSFkAwzoICcctOdHv/xB3AAsaCPZZkC//e5zekkIn MY7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Bd/7PUHSVj5FSLNXwfwGDpjkTP1tvjpxQIv9SqgE72E=; b=ucl8zOKpvbfXSBtWGLSvCQPKJAxRz1uPLVBSASyRYZU8B+za1VB3iDA5hNqbnjPrFS NylBCTWyufOwxT3iPOq0YEYx76TBzhv1EBVutowbL7/diDb/D3UuRy1Z8OBBxcB3YgpK Ok2hj4Y26/judvCsu5hNbt3wu39kgnEYQyUOvnSSEAfUdkfTJ8aLhHFhGISEYeooUync 2qXxGJAX7YEIvfOwvTAar8nFC63gpxalG1rHNBZzOmxbrCHflui+HXNmrSrTkwM3P1/z GdbKUrlgS//U9Ph9R0unFp5Eo3WkX4dGCUDy2LWjfFK58D8DunUnueBqZaMT3C4rHuZn 7ASw==
X-Gm-Message-State: AOAM531dyCcAKkY6OAPyy9tlqeHvCUEarEqXLm0tB4pS+8uSzAW7Wefy Dv39eRcs8RCJKMWdWTgZ6J0=
X-Google-Smtp-Source: ABdhPJwZ7RtnsFJZf60a0H9fZZVHA4ca1Pa2UMHbAEz5K1CWIw8DqmjiTfHZAFSFtj5pavhJH1v0QQ==
X-Received: by 2002:a1c:2c05:: with SMTP id s5mr3818040wms.70.1614688371676; Tue, 02 Mar 2021 04:32:51 -0800 (PST)
Received: from [192.168.8.125] ([212.183.132.45]) by smtp.gmail.com with ESMTPSA id h20sm2321866wmp.38.2021.03.02.04.32.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Mar 2021 04:32:50 -0800 (PST)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <2233700F-9AFF-472B-B3BF-33226339DB6E@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D64EB784-A299-4EF6-9C87-290C7FE3BC61"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 02 Mar 2021 12:32:48 +0000
In-Reply-To: <3ee2a63b-45db-b296-d6da-c1b4263b8fd6@gmail.com>
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>
To: Brian E Carpenter <brian.e.carpenter@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>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/nZSju1FUqbD4KUgMYKqp_xZgOlM>
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: Tue, 02 Mar 2021 12:32:58 -0000


> On 1 Mar 2021, at 20:08, Brian E Carpenter <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.

It is perfectly legitimate to write an IPv6 forwarder as follows:

If MACaddress == me and MACtype == IPv6 pass packet to IPv6 forwarder

In IPv6 forwarder:

If version == IPv6 and Hop Limit not exceeded send bytes 24 to 39 to address lookup engine

Wait for address result and forward packet accordingly

Except that this forwarder would have sent a bunch of random junk to the ALE consisting of some of the SA and maybe some of the DA depending on their sizes.

So to stop an old and legitimately designed parser being fooled you really have to use a new MAC type and a new version and as soon as you do that you might as well design the packet optimally for the job at hand.

If the IPv6 designers had followed the strategy of both the Ethernet designers and the ISO8473 designers and put DA before SA then the elegant approach that you and others have  proposed at various times would have worked nicely.

Best regards

Stewart