IETF Logo Mail Archive

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

Stewart Bryant <stewart.bryant@gmail.com> Tue, 02 March 2021 13:53 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 853033A1867; Tue, 2 Mar 2021 05:53:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, URIBL_BLOCKED=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 3dXKyRE09cdf; Tue, 2 Mar 2021 05:53:16 -0800 (PST)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 786D83A1865; Tue, 2 Mar 2021 05:53:16 -0800 (PST)
Received: by mail-wr1-x430.google.com with SMTP id b18so13470672wrn.6; Tue, 02 Mar 2021 05:53:16 -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=/duXFIsi11FzzGddbkdrKeFw8HOer3OKb6vlX3zbD7w=; b=qMHho64o8iMeulOYWHR1gGHwj284d15XD+n0uTtvRe+bsLJ8I/lZHzE6CPhjQL/Ajg xXaMTfdjB6QVB2wkif6KgImfU+xZ/0Xf/qnZ6qOgyaBYT/vPF5KT3RJWOS6kajxPfGrB rXn58/8h51lV2fJF7uHd9X4QWQyt9b0dOsXjCbDKAHcgslhVUGEopskdTrY4u0bLzh7U f5sT/jglyPZ8pHF2/c7KYIzG7fwAX0PJJr8J8O+0Z8ctMU8rbAy6rB0xQ6NFfrqAbbsG raNXKfoxsnsEwZN0WUx6643iiPtEohptQ5jXJbL16m1/P7dWOYsrsROHZ0Lr+a8kyUE5 KzhA==
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=/duXFIsi11FzzGddbkdrKeFw8HOer3OKb6vlX3zbD7w=; b=aD+PiWTjiWWBIxaw8grXOlsLBH/WAkfGj3ws8ilYOvQqxMo1qdGzMDT67WARA+eZc5 qLTurzpRuHDt+cOzqsc1Iss4Z/ZWgnnYQJpOAXSPcJKcQ14SayXFPhT1vCqwJ14dokYP 5sO/tEznbUgXd9NEeVrtaTR88uxfxbluRniiYDpKfo7eJQXXzkHbuzhLApFGp/7dll3Z /XDeV9vUzOXWIY1v5PaWUYFIv/XDiheGYVzTJcJVLpxOf1hYaIE8xvUsWAhCzxJTiVst Zw7kd8beQjWpFMesUawhi/YJ4Vv/F7kx3yzpWj8WVNq/64Dt62tXmwrkXuD1E1LStgDD W5eQ==
X-Gm-Message-State: AOAM532B6sdr4kji2hQNHwVcU05tocNtVYN7wUqWV4GbaeU4Dvh8MnTW JorNAY1hhMPitEBf8V6PNlQ=
X-Google-Smtp-Source: ABdhPJwyLrvfg+HvcBxYvCsHLjm7JGRijEmwWhBDzc5UOljmY8hbEhBftbDkNSDOt6mkZSihClB62w==
X-Received: by 2002:a5d:5043:: with SMTP id h3mr21856570wrt.120.1614693193721; Tue, 02 Mar 2021 05:53:13 -0800 (PST)
Received: from [192.168.8.125] ([212.183.132.45]) by smtp.gmail.com with ESMTPSA id j125sm2642924wmb.44.2021.03.02.05.53.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Mar 2021 05:53:13 -0800 (PST)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <554E7FC1-0146-4AEF-B84C-805B51013180@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8CC4133B-8868-430A-BCCE-471AE4704906"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 02 Mar 2021 13:53:12 +0000
In-Reply-To: <20210301153259.GB11539@faui48f.informatik.uni-erlangen.de>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Jiayihao <jiayihao@huawei.com>, "draft-jia-scenarios-flexible-address-structure@ietf.org" <draft-jia-scenarios-flexible-address-structure@ietf.org>, int-area <int-area@ietf.org>, "draft-jia-flex-ip-address-structure@ietf.org" <draft-jia-flex-ip-address-structure@ietf.org>
To: Toerless Eckert <tte@cs.fau.de>
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>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/MVofbSncj3BeAJvl_cmwpyZuyLk>
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 13:53:19 -0000


> On 1 Mar 2021, at 15:33, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> I really don't understand why the IPv6 world has not understood how the most easy way
> to allow for the applicability of IPv6 to grow (especially beyond "just more addresses thn IPv4")
> would be to come up with a backward compatible encap on the wire that would support additional
> address lengths.

Toerless

I don’t think there is a simple backwards compatible approach, but we can probably do more than we do today.

Backwards compatible means that you could put your new packet into a IPv6 parser and it would correctly forward the packet as if nothing had changed.

You could I suppose put a well known IPv6 address in the IPv6 header and put the real address in an extension header, perhaps including the pointer to the address in the suffix of the IPv6 address to make finding the EH much faster, but I am not sure that is backwards compatible.

I suppose it might be able to do a bit better if the address in the IPv6 DA was the DA of the egress router and old routers did best effort to the egress and newer routers knew to take a look at the extension header for more detail.

I think that it is worth thinking about how we could do better than we do today, but I think we need to be careful with the term backwards compatible.

- Stewart

v2.23.0 | Report a Bug | By Email