[icnrg] review of draft-choi-icnrg-aiot-02

Rute Sofia <sofia@fortiss.org> Tue, 05 May 2020 08:40 UTC

Return-Path: <sofia@fortiss.org>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8E08A3A15D9 for <icnrg@ietfa.amsl.com>; Tue, 5 May 2020 01:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id B61pJEHH_pOm for <icnrg@ietfa.amsl.com>; Tue, 5 May 2020 01:40:55 -0700 (PDT)
Received: from mail.fortiss.org (mail.fortiss.org []) (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 317133A15D7 for <icnrg@irtf.org>; Tue, 5 May 2020 01:40:54 -0700 (PDT)
Received: from [] (port=44047 helo=ms01.fortiss.fortiss.org) by mail.fortiss.org with esmtps (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <sofia@fortiss.org>) id 1jVt8E-0004bA-1W for icnrg@irtf.org; Tue, 05 May 2020 10:40:50 +0200
Received: from ms01.fortiss.fortiss.org ( by ms01.fortiss.fortiss.org ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Tue, 5 May 2020 10:40:50 +0200
Received: from ms01.fortiss.fortiss.org ([fe80::3928:e952:611b:9286]) by ms01.fortiss.fortiss.org ([fe80::3928:e952:611b:9286%12]) with mapi id 15.01.1913.010; Tue, 5 May 2020 10:40:50 +0200
X-CTCH-RefID: str=0001.0A782F15.5EB1264F.003C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
From: Rute Sofia <sofia@fortiss.org>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: review of draft-choi-icnrg-aiot-02
Thread-Index: AdYisfNcKCHh63pKRG2MrXIXgIq8Cg==
Date: Tue, 5 May 2020 08:40:49 +0000
Message-ID: <092ce0e7cf8441a2a2fa185b8781f014@fortiss.org>
Accept-Language: en-US, de-DE
x-originating-ip: []
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha-256"; boundary="----9BE58C0140D972E5D6A314FF085730EF"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/4cm5LDuo1bcL3V7dpyas509NU4Q>
Subject: [icnrg] review of draft-choi-icnrg-aiot-02
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2020 08:40:58 -0000

Dear All,

a review of draft-choi-icnrg-aiot-02 (https://datatracker.ietf.org/doc/draft-choi-icnrg-aiot/).

The draft is relevant as it handles the need of applying AI to IoT environments. However, the connection to ICNRG is not clear IMO. Also, the draft is still in a very early stage of development, which requires a lot more thought; a good look into available related work on the field. Some sections should IMO be re-written and merged.

Overall comments follow.

Best Regards,
Rute Sofia

Global comments:
There is something wrong with the formatting, please check it as several words are cut, aspect which difficults the reading.

The motivation (intro) should be re-written to explain better the problem. The application in the context of ICNRG is not completely clear.

The wide use of "IoT service" is tricky. Perhaps IoT end-to-end system is better. An IoT service environment simply refers to what we usually use on the Cloud/Edge. I believe the authors are also considering the IoT devices, i.e.: all of the IoT ecosystem.
There is the need for a terminology section where all of the different terms are described.
It is also relevant not to focus the topic of IoT on consumer IoT only, as it is now drafted. In fact, AI is highly important in Industrial IoT environments.

Concerning the IoT challenges, there are 2 main aspects which are not addressed and should be: the need for mobility support; intermittent and asynchronous communication.

Comments per section:

intends to present a right direction to empower AI - a "right direction" should be replaced by other terms, for instance, a potential direction.

1.  Introduction

The way the motivation has been described is quite confusing, again with some confusion on the terms. Also, the description of how data sources work require more explanation. For instance data sources do send small packets,but the volume can be high. Then, it is explicitely stated that the data sources communicate with a server (client/server) thus eliminating the possibility of direct communication (Thing to Thing) and Pub/Sub communication.

2.      Challenges
There are 2 main challenges missing: mobility, and intermittent connectivity. In terms of security and concerning both hw and sw: accountability.

2.1   Untrusted and incorrect devices
What is meant with "incorrect device"
Also, this section is focused on hw and PHY aspects.

In shop-floors and industrial environments, devices are certified. It is not usual to deploy uncertified sensors. However, a problem that can arise is the fact that other sensing devices, such as rugged tablets, may be used for maintenance. While the hw has been certified, software/app and user accountability is required.

2.2   traffic burstiness

The claims stated should be backed up with specific references. There are specific guidelines being provided, for instance, by IIC or by the IEEE concerning different IoT environments and traffic profiles. Also, the assumptions stated, that for "normal IoT traffic" (what is this) the "normal bandwidth" (what is this) is very small is not accurate. In IIoT, these devices are connected via Ethernet and soon with WiFi 6. In consumer IIoT, we are connected via the internet, with often a wireless or LTE "bottleneck" at the last hop to the end-user.

2.3   management overhead of IoT devices
Is this about configuration or onboarding? Or both? Also, please notice that smartphones and rugged devices are actually sensing devices which have also to be accounted for in IoT environments.

3.      AI/ML based IoT services should be named as examples of AI application per domain sectors.
The idea of describing the potential application of AI in different domains is relevant. However, its current status is confusing. There is a quick description of different sectors. Perhaps organizing this in a similar fashion, with specific aspects such as: description; problem solved with AI; main techniques applied; expected impact.

4.      Requirements

This section should have a list of requirements based on section 3. At this stage, it is still confusing. It is also too little, so either it is removed (a subsection of 3 could be added instead).

Context-awareness is suddenly addressed in this section without actually describing it anywhere else. On which layers, which indicators are being considered, etc.? This needs to be addressed up front in the draft.

Section 4 and 5 do not add much in comparison to related literature. What is the purpose of these 2 sections? Could they be merged? Also, the introduction on different ML methods can be done by recurring to relevant related work in the field.

The application of neuromorphic computing should also be cited (SNN and IoT).

Section 6 and 3 are somewhat repeating. The content of 3 could be placed in 6, use-cases.

Rute Sofia

fortiss · Landesforschungsinstitut des Freistaats Bayern
An-Institut Technische Universität München
Guerickestraße 25
80805 München
Tel.: +49 (89) 3603522 170
Fax: +49 (89) 3603522 50
E-Mail: sofia@fortiss.org<mailto:sofia@fortiss.org>

Amtsgericht München: HRB: 176633
USt-IdNr.: DE263907002, Steuer-Nr.: 143/237/25900
Rechtsform: gemeinnützige GmbH
Sitz der Gesellschaft: München
Geschäftsführer: Dr. Harald Rueß, Thomas Vallon
Vorsitzender des Aufsichtsrats: Dr. Manfred Wolter