Re: [Coin] Charter discussion
Adrian Farrel <adrian@olddog.co.uk> Fri, 12 November 2021 16:18 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB053A0BCC for <coin@ietfa.amsl.com>; Fri, 12 Nov 2021 08:18:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 vIAE4EUAueg2 for <coin@ietfa.amsl.com>; Fri, 12 Nov 2021 08:18:36 -0800 (PST)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (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 1F20E3A0BC9 for <coin@irtf.org>; Fri, 12 Nov 2021 08:18:35 -0800 (PST)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 1ACGIPAq009296; Fri, 12 Nov 2021 16:18:25 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id EDAE74604B; Fri, 12 Nov 2021 16:18:24 +0000 (GMT)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E0E754604A; Fri, 12 Nov 2021 16:18:24 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS; Fri, 12 Nov 2021 16:18:24 +0000 (GMT)
Received: from LAPTOPK7AS653V ([84.93.2.7]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 1ACGINfr028711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Nov 2021 16:18:24 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Lixia Zhang' <lixia@cs.ucla.edu>, 'Marie-Jose Montpetit' <marie@mjmontpetit.com>
Cc: coin@irtf.org
References: <018001d7d705$67e4b890$37ae29b0$@olddog.co.uk> <CAPjWiCSzvC5-zy0tm_OPRR+X6=S8V3ELEkLK59ix0t=MZkaP2w@mail.gmail.com> <E3AC2E9F-5BD5-4EC3-AE46-77887215224D@dkutscher.net> <331B6109-DBE9-4F74-B7F3-7F57CF85F10F@orandom.net> <CAPjWiCR-pXcC7UsTT7d1bT6WkOqS-jyyi7MZQYHBUsGWbbScJQ@mail.gmail.com> <5ED03D87-05DF-4A98-8CB1-8B47A8611152@cs.ucla.edu>
In-Reply-To: <5ED03D87-05DF-4A98-8CB1-8B47A8611152@cs.ucla.edu>
Date: Fri, 12 Nov 2021 16:18:23 -0000
Organization: Old Dog Consulting
Message-ID: <041701d7d7e0$eaf50010$c0df0030$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKYns4kYxTyFFe/7wcMLWBZRVci7QImlJJ4ASElpiMCMgnOZAJ57Le8ANBhXNWqOGHeoA==
Content-Language: en-gb
X-Originating-IP: 84.93.2.7
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2034-8.6.0.1018-26526.000
X-TM-AS-Result: No--12.847-10.0-31-10
X-imss-scan-details: No--12.847-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2034-8.6.1018-26526.000
X-TMASE-Result: 10--12.846500-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFrxIbpQ8BhdbLzgL/eLACDEOhJ9m53n4aAG2HMvWEJenhgU wEEz5FCmt6ev2BaRTqo7FdeJ58l/x1Lj6g9IGWlslTsGW3DmpUsP6OWzRxLAk1Yl7G4TK5CUdVd Df+p3DnJXvg4jWgsrJ3f1e2LieD10wxrh0396D3Ii8B1njP2CEvMMVfCUdzaoteXjSBMYnmlbqm KSA8DdPnXeI/fDOAs9jgJtTfwwy7b+JnnT2Ts2BY61Z+HJnvsOPJb7oABYhT8+Jpc06rUTNlNNT Kw5Eie+BwBWBuX2DYT4t7nX2oD1r/bQb0xGIlFtmOFnGEL0JOML8TGleseLPFymazekyFPRFA7u NHNvzLcYsB65CzUe4G+iqAHXmtzlxXR7Fsw9DdPE4i/j+gqDIDZtT0BD+ZNHHSjftcn3H6MQSz6 0vL+6B0HI0i5PrgSdbJL4ernHsayv6XrOv9OTH/niqx8KBlfTQf/cbp253zEXXa3f7P/Dv1WXI5 56BNbpghYhuaPVNFQflvVCPV3y7IgLXzz7b4Uvyq0aou1D6WzABZQAi1LTAakUwB3MABAn4N3C7 pSZ7XvAFplsMye+YBpP73E4lTwGmmOznkVAUcDBFOikWBnGHUjCi9tfhPjQ3RhWEOGgfZaw0FFG deCd9nNSFQYOn23UvFHe2GnEhBhl+hxxqfcpPs/XkDDEkV4el93RwgngsFpQJFvZj8C0JrHobIz JEXjb3VntjC+iJjXUlUXqI6dEdR1getEocBZFA03RH6J3AaMCgrdjroXmnAqju8Vew4gSQQ/s9v EJJncdKAxsNfeGEYmq3EBRK23aDYTDmdGrg82eAiCmPx4NwBaLWfA4qcOBi2QFaYS1v20qtq5d3 cxkNfAxRSAc0OEN9v+NNOVSdf9ptOg0kshUWMC3MegAbkO5DWCQmT7PbnQlvG2AUV1RLHx7rRXV QWcC
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/9lDmzb5EdKl8V-W745CnPRp-eU8>
Subject: Re: [Coin] Charter discussion
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2021 16:18:41 -0000
Hi Lixia, Picking on one point. Please look at draft-farrel-irtf-introduction-to-semantic-routing for our latest thoughts on what we mean by semantic routing. Making changes to the semantics of IP addresses is *one* possible approach to placing semantics in packets to enable routing. But it is not our objective. I know there are a number of proposals to do this (including WGs that work on it extensively), but we are not supporting or promoting these approaches. Our objective is to look at the consequences for packet routing systems if they use the different approaches to semantic routing. How does backward compatibility work? What happens to scalability and stability? What about security and privacy? Thanks, Adrian PS "Routing" is, of course, a concept used widely at multiple layers. Sometimes it means slightly different things, but the general concept is the same. We, however, are considering "packet routing" at layer 3. -----Original Message----- From: Coin <coin-bounces@irtf.org> On Behalf Of Lixia Zhang Sent: 12 November 2021 16:04 To: Marie-Jose Montpetit <marie@mjmontpetit.com> Cc: coin@irtf.org Subject: Re: [Coin] Charter discussion > On Nov 12, 2021, at 6:30 AM, Marie-Jose Montpetit <marie@mjmontpetit.com> wrote: > > P4 is another language. > > Programming dataplanes (and control planes and distributed systems) is the goal. > > So now we will have tel-heads -> net-heads -> prog-heads? > > And all in our lifetime! Agree. Progress is accelerating :-) But it seems to me that the word "net" in "net-heads" could benefit from a bit further classification 1/ communications need networking. 2/ so telecom also built networks, and "tel-heads" in the old days referred to as "bell-shaped heads", the view that communication is about building a network that sets up circuits. 3/ really dont mean to put word in your mouth: I assume the "net" in net-heads means IP networking (as opposed to telecom networks) that we have today? If I dare to say this in public (please do not shoot me! close friends have heard it from me for years:) -- by paraphrasing the old saying, and clarifying what kind net one is talking about: the "net-heads" in the above should be called "IP-shaped heads", thinking in terms of shooting packets to destination addresses. 4/ the "N" in ICN is also about networking, information-centric networking. Now back to where this exchange started: yes all kinds of networks need routing (telecom had routing too, they just did in different ways), so COIN needs routing support, whether that is in/out the charter is a separable question. I would just like to remind ourselves that that routing works on some identifier space, so we need to first clarify what that identifier space identifiers. IP address identifies locations (more precisely: network attachment points). ICN names identifies information--a name can name anything, so the information can be about anything (sensor data, compute function, Netflix movie, or a node's MIB or its attachment points...). As I read from draft-king-irtf-semantic-routing-survey, "semantic routing" aims to change the semantics of IP addresses. But I am afraid that the definition of IP addresses cannot be *feasibly* redefined in fundamental ways --- just look at "IP multicast address" as an example: that's no longer the address as defined by RFC791, and that redefinition implied profound changes to the deployed IP base, hence its 30 years of (losing?) battle in deployment. "The farther back you can look, the farther forward you are likely to see."--Winston Churchill just my 2 cents, Lixia -- Coin mailing list Coin@irtf.org https://www.irtf.org/mailman/listinfo/coin
- [Coin] Charter discussion Adrian Farrel
- Re: [Coin] Charter discussion Marie-Jose Montpetit
- Re: [Coin] Charter discussion Dirk Kutscher
- Re: [Coin] Charter discussion David R. Oran
- Re: [Coin] Charter discussion Marie-Jose Montpetit
- Re: [Coin] Charter discussion Lixia Zhang
- Re: [Coin] Charter discussion Adrian Farrel
- Re: [Coin] Charter discussion Dino Farinacci
- Re: [Coin] Charter discussion Cedric Westphal
- Re: [Coin] Charter discussion David R. Oran
- Re: [Coin] Charter discussion christian.tschudin
- Re: [Coin] Charter discussion Marie-Jose Montpetit
- Re: [Coin] Charter discussion David R. Oran
- Re: [Coin] Charter discussion Marie-Jose Montpetit
- Re: [Coin] Charter discussion Jon Crowcroft
- Re: [Coin] Charter discussion Marie-Jose Montpetit
- Re: [Coin] Charter discussion Hesham ElBakoury
- Re: [Coin] Charter discussion Jeff Tantsura
- Re: [Coin] Charter discussion Bernier, Daniel
- Re: [Coin] Charter discussion Milheiro Mendes, Paulo Jorge
- Re: [Coin] Charter discussion Hesham ElBakoury
- Re: [Coin] Charter discussion Dino Farinacci
- Re: [Coin] Charter discussion Marie-Jose Montpetit
- Re: [Coin] Charter discussion Sharon Barkai
- Re: [Coin] Charter discussion Hesham ElBakoury
- Re: [Coin] Charter discussion Dino Farinacci
- Re: [Coin] Charter discussion Colin Perkins
- Re: [Coin] Charter discussion Adrian Farrel