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

Toerless Eckert <tte@cs.fau.de> Wed, 03 March 2021 13:18 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 606FF3A110F; Wed, 3 Mar 2021 05:18:19 -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 fPHmUD8ThFS8; Wed, 3 Mar 2021 05:18:17 -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 E2B423A1100; Wed, 3 Mar 2021 05:18:16 -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 B57B9548045; Wed, 3 Mar 2021 14:18:09 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id ACD11440166; Wed, 3 Mar 2021 14:18:09 +0100 (CET)
Date: Wed, 03 Mar 2021 14:18:09 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Carsten Bormann <cabo@tzi.org>
Cc: "Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com>, "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>
Message-ID: <20210303131809.GB16816@faui48f.informatik.uni-erlangen.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> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <AD8FE644-6290-404F-BB0B-9B01A267B934@tzi.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/WhnYaaVQeTofP0ObBxNlV9N_KkI>
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 13:18:20 -0000

Carsten:

Thank you, fully agree. The first time i saw "backward compatibity" pop up in
these discussions was in questions from ISOCI people in discussions
about future evolution of IP/Internet - of course without any clear
specification or reference as to what they actually meant with it.

Would be good to come up with more precise terminology around
characerizations of relationships between stages of an evolutionary
path in networking though.

Then again, IETF isn't particularily fond of creating
output that can not be hacked into C (oops: these days javascript).

But noting how NMRG is doing a fine jobs on trying to write down
what Intent is (terminology/taxonomy), maybe there is a job
for an IRTF group to do a similar job creating a better terminology
to describe such evolutionary characteristics as they relate to
networking. Otherwise it will continue to be hard to even talk about
such networking evolution without being, as you said just be sidelined.

Cheers
    Toerless

On Wed, Mar 03, 2021 at 08:46:09AM +0100, Carsten Bormann wrote:
> 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.
> 
> 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.
> 
> Grüße, Carsten
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

-- 
---
tte@cs.fau.de