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

Luigi Iannone <ggx@gigix.net> Thu, 04 March 2021 06:03 UTC

Return-Path: <ggx@gigix.net>
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 405253A133E for <int-area@ietfa.amsl.com>; Wed, 3 Mar 2021 22:03:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.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 KGKFsS0oL0Xs for <int-area@ietfa.amsl.com>; Wed, 3 Mar 2021 22:03:08 -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 9A0163A133F for <int-area@ietf.org>; Wed, 3 Mar 2021 22:03:08 -0800 (PST)
Received: by mail-wr1-x430.google.com with SMTP id v15so26283359wrx.4 for <int-area@ietf.org>; Wed, 03 Mar 2021 22:03:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CcDrEECWWwnV4j/IS0aVCsVoQLIblKSByGCVLoQS550=; b=RQQ0P4SXTBfsWDmcjao7s/6YxkM0VirkQ5cOl2nKeMUrJDkEGRie4xCAmWWFLdAZMd SeRUhsKhsb1TluAdmDuQPvb7l7BWRnoATGS0N0md4g+5ybBsTvUEMnKgfx0tEvg6f87r Qp/tzEG9xnewp+iM3MHXPLFgrFzBwYC6NI3ZIcF195TQZTWcyoHC4AQjgU7JD7BCQZuR R/zq9/2JXoLs9v2ZBdZlki0yVBiPrR4sPBPiViOahpfhrKQcfxYJTS0c7AL8KXtMB+oZ A+OqmAEbDBf2Y+y46fOIP+zMKH7Sq7lKWulEARnJyT21WeSv2F17X2x4FyLjehQT4DYb eKAA==
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=CcDrEECWWwnV4j/IS0aVCsVoQLIblKSByGCVLoQS550=; b=X0sovOjP6Rro68KOBvOmo16WSQIKKaqMEuDzcFzbXSM62P2NE1E5BB4OI5cL/1IOZS Ea/S0++s8ipMKIRVBi4RjcvvX9pTJfLK6EZ6hNr1Ttrl/zMYUkYCkTLS/fN8UEecKkSo Qq4cVU4hJTCdmkzBLTV+kyWk8FviJCo7IwYnX1nmXEe9SLE+dW7+ydCtnpH6rVSxykMp PFe8YlGQPnyAWYQpBTRU1/qafZ44Ylz4xIznawOpqIYB3i5ROrfs2Cz6T5yzkq5nzrqD uZL+wHUSZ1jgf4OCF9bPiYvL4dRYLJqn+HDF4jLOIDqyG6WI05HmS3lZAQqX4ViHI4dg vO5Q==
X-Gm-Message-State: AOAM531N/hh00dCHW2SgZ+EJjHaiNQpi1Rjv04avwHbO2tmaqeUtv2+a uAEd5mtUX7LI8ATugm8+kpp7Gg==
X-Google-Smtp-Source: ABdhPJwd3bEgNpfdFfiQrR3nV4Cu84x91QVysK2rkYSEQMSA32TirB2Q+BFM/OFTezieGXRhO4bZ7Q==
X-Received: by 2002:a05:6000:18f:: with SMTP id p15mr2101819wrx.23.1614837785899; Wed, 03 Mar 2021 22:03:05 -0800 (PST)
Received: from ?IPv6:2a01:e0a:1ec:470:78ce:fa6f:e5bc:a5b0? ([2a01:e0a:1ec:470:78ce:fa6f:e5bc:a5b0]) by smtp.gmail.com with ESMTPSA id l15sm7920526wme.43.2021.03.03.22.03.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Mar 2021 22:03:05 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <20210303131809.GB16816@faui48f.informatik.uni-erlangen.de>
Date: Thu, 04 Mar 2021 07:03:04 +0100
Cc: Carsten Bormann <cabo@tzi.org>, "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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DDA951F-AE6A-4C88-B455-CF587843A062@gigix.net>
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> <20210303131809.GB16816@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/siKFwaeE767e5TkqRTGelGHbOKw>
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: Thu, 04 Mar 2021 06:03:11 -0000


> On 3 Mar 2021, at 14:18, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> 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.

+1

I think is a good idea. Would be nice to have something like that.
To be complete it should not look only at the “backward” part but also to the “forward” part, covering things like incremental deployability.

Ciao

L.
 



> 
> 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
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area