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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 03 March 2021 09:48 UTC

Return-Path: <alexandre.petrescu@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 282923A0964 for <int-area@ietfa.amsl.com>; Wed, 3 Mar 2021 01:48:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.648
X-Spam-Level:
X-Spam-Status: No, score=0.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 jzxxXPGcqvZc for <int-area@ietfa.amsl.com>; Wed, 3 Mar 2021 01:48:42 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 54BA33A0962 for <int-area@ietf.org>; Wed, 3 Mar 2021 01:48:42 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 1239mdOR036215 for <int-area@ietf.org>; Wed, 3 Mar 2021 10:48:39 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C0BBC203415 for <int-area@ietf.org>; Wed, 3 Mar 2021 10:48:39 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B5C89203407 for <int-area@ietf.org>; Wed, 3 Mar 2021 10:48:39 +0100 (CET)
Received: from [10.14.0.50] ([10.14.0.50]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 1239mdEY005465 for <int-area@ietf.org>; Wed, 3 Mar 2021 10:48:39 +0100
To: int-area@ietf.org
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> <554E7FC1-0146-4AEF-B84C-805B51013180@gmail.com> <6F4E6B0C717D4641A2B79BC1740D8CF4A902DD90@dggemm513-mbs.china.huawei.com> <D8A2DB51-FEEC-48E6-99AC-0F50D771C91A@gmail.com> <6F4E6B0C717D4641A2B79BC1740D8CF4A9030885@dggemm513-mbs.china.huawei.com> <AD8FE644-6290-404F-BB0B-9B01A267B934@tzi.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d3c7ada2-9a9c-cd3a-d0f5-89d89a00abc0@gmail.com>
Date: Wed, 03 Mar 2021 10:48:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <AD8FE644-6290-404F-BB0B-9B01A267B934@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/8scR4LlZhnnTo38X7WP_tQ5UQfk>
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 09:48:45 -0000


Le 03/03/2021 à 08:46, Carsten Bormann a écrit :
> On 2021-03-03, at 03:42, Liguangpeng (Roc, Network Technology 
> Laboratory) <liguangpeng@huawei.com> wrote:
>> 
>> backwards compatible
> 
> I would suggest not to center the discussion on terms that are so 
> overloaded that they are essentially meaningless.
> 
> Some believe “backwards compatible” means “does not break existing 
> applications”. That is a low bar (but not trivial either).  It does 
> not imply any form of deployability in the sense of actually making 
> the scheme work.

I agree.

The 'backwards compatibility' concept has many facets.

I could say that using an ISO network layer is backwards compatible in
that it does not break existing IP network layers.  The EtherType in the
layer below makes sure there is a right distinction.

But, has this been tried in practice against many systems?  Have people
sent ISO network layer packets to computers that only implement IP and
that might not have an EtherType value for ISO in their link layer of
their stacks?  What happens them?  Maybe it is just an error reported,
or maybe the system segfaults outright.

This can be looked up closer.

> Some believe “backwards compatible” means “seamlessly integrates 
> existing infrastructure” (maybe with the exception that certain 
> benefits do not accrue until that is upgraded).  That has
> essentially been the basis for all major innovation that has happened
> in the Internet, with the exception of IPv6 (and you know how long
> that took and still is taking in some parts of the world).
> 
> Terms like “backwards compatible” are, however, useful for derailing 
> the discussion if that is one’s intention, because quickly the 
> discussion will be about the terms and no longer about the subject.

If one is to derail discussion, one would also point to 'future proof'
aspects of newly designed protocols.  Designing something today that
might not work in the future is not advantageous.

Putting an IPv6 implementation in a computer that only does IPv4 makes
sure that computer is future proof for when IPv6 arrives.

But can one say that putting an ISO network layer in a computer that
only does IPv4 and IPv6 is future proof for when ISO arrives?  Is there
a plan for deployment of ISO network layer?  Like IPv6 had a plan with
the 6bone, 3ffe prefixed addresses, and the 'island' concept?

Alex

> 
> Grüße, Carsten
> 
> _______________________________________________ Int-area mailing list
> Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
>