[Din] revisit arguments for edge

Aaron Ding <Aaron.Ding@tudelft.nl> Sat, 03 July 2021 07:07 UTC

Return-Path: <Aaron.Ding@tudelft.nl>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 89C6A3A1D13; Sat, 3 Jul 2021 00:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.795
X-Spam-Status: No, score=-1.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id jf19xsXaxdy9; Sat, 3 Jul 2021 00:07:51 -0700 (PDT)
Received: from mailservice.tudelft.nl (mailservice.tudelft.nl []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42C913A1D12; Sat, 3 Jul 2021 00:07:50 -0700 (PDT)
Received: from localhost (localhost []) by amavis (Postfix) with ESMTP id 572D2400BD; Sat, 3 Jul 2021 09:07:48 +0200 (CEST)
X-Virus-Scanned: amavisd-new at tudelft.nl
Received: from mailservice.tudelft.nl ([]) by localhost (tudelft.nl []) (amavisd-new, port 10026) with ESMTP id Gi5l72TJibW7; Sat, 3 Jul 2021 09:07:46 +0200 (CEST)
Received: from SRV126.tudelft.net (srv126.tudelft.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.tudelft.nl (Postfix) with ESMTPS id 9B29540097; Sat, 3 Jul 2021 09:07:45 +0200 (CEST)
Received: from SRV223.tudelft.net ( by SRV126.tudelft.net ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2242.10; Sat, 3 Jul 2021 09:07:45 +0200
Received: from SRV223.tudelft.net ([fe80::89f8:a8a8:176c:252c]) by SRV223.tudelft.net ([fe80::89f8:a8a8:176c:252c%2]) with mapi id 15.01.2242.010; Sat, 3 Jul 2021 09:07:45 +0200
From: Aaron Ding <Aaron.Ding@tudelft.nl>
To: "coin@irtf.org" <coin@irtf.org>, "din@irtf.org" <din@irtf.org>
Thread-Topic: revisit arguments for edge
Thread-Index: AQHXb9ofe/d8UEbEcUSG+fmRg8IC/Q==
Date: Sat, 3 Jul 2021 07:07:45 +0000
Message-ID: <eca3377d1d88457a9e92aa1e5f71d319@tudelft.nl>
References: <9447b829d6d74ea3a4b1397996d0a44e@tudelft.nl> <a2cbde43125b4d6eb0cf4377d0509039@tudelft.nl> <b0464912669d417485df7d55cc0f5de3@tudelft.nl> <f2985213f1824470b4f5de9e28be8e26@tudelft.nl> <ba266c32b2794219aa3752a60fe9717d@tudelft.nl> <68c671814326403a9e3867d4970276d1@tudelft.nl> <5bab07a54efb416a9094fe59cb2995f9@tudelft.nl> <9de631a4f6a04e23956074a54935c8fc@tudelft.nl> <1468883c4d6d4f4f9e91af8519327cb9@tudelft.nl> <d6bb7b7e4c17431595184ce56f5e51a0@tudelft.nl> <91129f51c5b54a30b59a690cc168e175@tudelft.nl> <5e90908e08a242aaaa2a6d7069d2f6a4@tudelft.nl> <057dacdebc39402cab0647182489d07e@tudelft.nl> <f4a94ea1e59943c3865b83907f05dd08@tudelft.nl> <de089ea658a746f494f4522fab53e81a@tudelft.nl> <dc32e8e5dcda49019a6d389664675732@tudelft.nl> <1466227adc3f4673a7d322e76a4a4415@tudelft.nl> <68891d560ca040e18a46de4e96e3432b@tudelft.nl> <264b767130194722a64513b55bbe871f@tudelft.nl> <CAFvDQ9qpbb14C=VOL_+a3tkN8E-uqHL-f1hC=P3AibLxHn2UYQ@mail.gmail.com> <11DD39D8-5384-40AA-8922-B550F60D694F@getnexar.com> <41ed4405744e4f489b214c3a25fb8469@tudelft.nl>, <CAFvDQ9rrms7gxVcGhvXtfPjJKbAGWz3EDBeEWsKU3UiEc2EoqQ@mail.gmail.com>
In-Reply-To: <CAFvDQ9rrms7gxVcGhvXtfPjJKbAGWz3EDBeEWsKU3UiEc2EoqQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_eca3377d1d88457a9e92aa1e5f71d319tudelftnl_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/LPyjL6lnSH8nuaIN2VgOoNKmohw>
Subject: [Din] revisit arguments for edge
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jul 2021 07:07:57 -0000

for colleagues on lists, this 'Revisit Edge' is now published on IEEE Internet Computing:



From: Sharon Barkai <sharon.barkai@getnexar.com<mailto:sharon.barkai@getnexar.com>>
Sent: Sunday, June 27, 2021 13:22
To: Hesham ElBakoury
Cc: Aaron Ding; coin@irtf.org<mailto:coin@irtf.org>
Subject: Re: [Coin] revisit arguments for edge

"The Automotive Edge Computing Consortium (AECC) estimates that more than 30% of video data produced on the vehicle will need to be offloaded. This is to increase safety thresholds by processing offloaded data with external data for augmenting awareness of the moving vehicle. The volume of data that will need to be offloaded is expected to be between 400 GB to 5 TB per hour. If all the data is sent to the cloud, the QoS objectives cannot not be met due to the limited bandwidth. Therefore, exploiting the edge that efficiently processes the data near the source is required for such applications.”

This “physics” argument is one of the most compelling for a programmable edge:
- not satisfied by CDN/rCDN edge caches with generic traffic management
- crowd-source collection of transient street conditions must be edge curated
- transient conditions such as blockages, free-parking, double-parking, hazards
- curation includes multiple source verification, localization of what is “seen”
- plus tracking for how long transient conditions persist and who needs to know
- all of which have policy based, changing and constantly evolving, enterprise logic
- attainable today on existing cellular with existing metro DCs peering to carriers

This programmable edge use-case is also very high-function-network COIN oriented:
- requires continues p2p p2mp service while modems switch carriers for reception
- requires addressable in-network instance steering to avoid resolution over mobile
- addressable vehicle IDs and addressable geolocation services while driving
- in-network instance selection, avoids massive client updates upon cluster shifts

On Jun 27, 2021, at 13:45, Hesham ElBakoury <helbakoury@gmail.com<mailto:helbakoury@gmail.com>> wrote:

The article answers this question in its conclusion which says: "This article argues that the motivation for edge computing research has not diminished since it was first formulated."


On Sun, Jun 27, 2021, 1:55 AM Aaron Ding <Aaron.Ding@tudelft.nl<mailto:Aaron.Ding@tudelft.nl>> wrote:

COINRG colleagues,

Is the motive for Edge diminishing since its first concepts were formulated more than a decade ago?

A recent work to share on "Revisiting the Arguments for Edge Computing Research"

CPI Lab, TU Delft