Re: [T2TRG] New Version Notification for draft-hong-t2trg-iot-edge-computing-01.txt

Rute Sofia <sofia@fortiss.org> Fri, 08 November 2019 08:48 UTC

Return-Path: <sofia@fortiss.org>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 272C2120233 for <t2trg@ietfa.amsl.com>; Fri, 8 Nov 2019 00:48:36 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ewYkxUyRKbJl for <t2trg@ietfa.amsl.com>; Fri, 8 Nov 2019 00:48:33 -0800 (PST)
Received: from mail.fortiss.org (mail.fortiss.org [178.15.138.114]) (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 7412C120111 for <t2trg@irtf.org>; Fri, 8 Nov 2019 00:48:32 -0800 (PST)
Received: from [192.168.16.27] (port=12973 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 1iSzwI-0002o7-2b; Fri, 08 Nov 2019 09:48:19 +0100
Received: from ms01.fortiss.fortiss.org (192.168.16.27) by ms01.fortiss.fortiss.org (192.168.16.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 8 Nov 2019 09:48:18 +0100
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.1713.008; Fri, 8 Nov 2019 09:48:18 +0100
X-CTCH-RefID: str=0001.0A0C0214.5DC52BD3.0006, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
From: Rute Sofia <sofia@fortiss.org>
To: Jungha Hong <jhong@etri.re.kr>, "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: New Version Notification for draft-hong-t2trg-iot-edge-computing-01.txt
Thread-Index: AQHVkuxCsvHk+n8gZkSfuIqsRq3OlaeA9t0pgAABNhA=
Date: Fri, 08 Nov 2019 08:48:18 +0000
Message-ID: <1c07cdd5efc54dc89f6b11c8a2a873d8@fortiss.org>
References: <157285712544.16483.3305572835875869516.idtracker@ietfa.amsl.com> <F8EFC212DF9A004DA18AA8FB011E4233BB942BB6@SMTP1.etri.info>
In-Reply-To: <F8EFC212DF9A004DA18AA8FB011E4233BB942BB6@SMTP1.etri.info>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.0.7.116]
Content-Type: multipart/alternative; boundary="_000_1c07cdd5efc54dc89f6b11c8a2a873d8fortissorg_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/TkRQ-Zk_-kgQRcY8Vqu4wh56bdg>
Subject: Re: [T2TRG] New Version Notification for draft-hong-t2trg-iot-edge-computing-01.txt
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2019 08:48:36 -0000

Hello Jungha

I will not be in Singapore and given the time gap, remote participation is hard. Here are a few comments and if needed, I can assist in contributing:


-          3.3, Edge Computing, the title should go for Edge/Fog computing (which anyway is referenced in the text)

-          4. Additional challenges not mentioned:

o   Energy consumption

o   Handling both event-driven and time-driven traffic (you mention latency and jitter, but speak mostly about deterministic aspects)

-          5.

o   The definition of what the edge is/can be is missing. The edge can be a complex device co-located to a BS, on a shop-floor. But it can also be a smartphone. There is the need to define this in the context being provided.

-           The document provides (Figure 1) a centralized version of the edge computing manager.  It would be good to consider a second figure, with a de-centralized version.

-          5.3, the edge computing functions should also include the relevant abstraction functions, e.g., semantic interoperability; data aggregation, etc.

-          5.4, stating that the edge computing domain should directly or indirectly control the network functions (of the data exchange) is reducing the possibility of having an autonomous, self-organizing behaviour between edge computing nodes.

-          6.1, the computing aspects and protocols mentioned should consider or cite work that are relevant both from a consumer and an industrial perspective. OPC-UA must be mentioned; and other relevant protocols are DDS.

-          6.1, this section is not really also clear…this seems to describe a set of services which are today common to any edge platform, but seems to be quite incomplete…

-          6.2 Likewise for this section. Perhaps it should be split into consumer and Industrial IoT, and for each category, then address specific and relevant use-cases, as well as provide pointers to prior work on this





BR

Rute Sofia
From: T2TRG <t2trg-bounces@irtf.org> On Behalf Of Jungha Hong
Sent: 08 November 2019 09:29
To: t2trg@irtf.org
Subject: [T2TRG] FW: New Version Notification for draft-hong-t2trg-iot-edge-computing-01.txt


Dear all,



IoT Edge computing draft was updated and submitted as below. We also put it into a T2TRG repo on github.



Section 5 has been mainly updated and it is discussing IoT Edge computing model.

The figure of Gateway-based IoT Edge computing architecture was also replaced with IoT Edge computing model to focus on common functions of IoT Edge computing.



We would like to discuss adopting it as RG document in Singapore.

Please review the draft and give us comments (in advance if possible).



Thanks,

Jungha







________________________________
보낸 사람 : "internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>" <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
보낸 날짜 : 2019-11-04 17:45:50 ( +09:00 )
받는 사람 : 홍용근 <yghong@etri.re.kr<mailto:yghong@etri.re.kr>>, 홍정하 <jhong@etri.re.kr<mailto:jhong@etri.re.kr>>, Dirk Kutscher <ietf@dkutscher.net<mailto:ietf@dkutscher.net>>, 홍용근 <yghong@etri.re.kr<mailto:yghong@etri.re.kr>>, Eve Schooler <eve.m.schooler@intel.com<mailto:eve.m.schooler@intel.com>>, Xavier de Foy <xavier.defoy@interdigital.com<mailto:xavier.defoy@interdigital.com>>, Matthias Kovatsch <ietf@kovatsch.net<mailto:ietf@kovatsch.net>>
참조 :
제목 : New Version Notification for draft-hong-t2trg-iot-edge-computing-01.txt




A new version of I-D, draft-hong-t2trg-iot-edge-computing-01.txt


has been successfully submitted by Yong-Geun Hong and posted to the


IETF repository.




Name: draft-hong-t2trg-iot-edge-computing


Revision: 01


Title: IoT Edge Computing Challenges and Functions


Document date: 2019-11-04


Group: Individual Submission


Pages: 25


URL: https://www.ietf.org/internet-drafts/draft-hong-t2trg-iot-edge-computing-01.txt


Status: https://datatracker.ietf.org/doc/draft-hong-t2trg-iot-edge-computing/


Htmlized: https://tools.ietf.org/html/draft-hong-t2trg-iot-edge-computing-01


Htmlized: https://datatracker.ietf.org/doc/html/draft-hong-t2trg-iot-edge-computing


Diff: https://www.ietf.org/rfcdiff?url2=draft-hong-t2trg-iot-edge-computing-01




Abstract:


This document describes new challenges such as strict latency, uplink


cost, uninterrupted services, privacy and security, for IoT services


originated from the IoT environmental changes. In order to address


those new challenges, the integration of Edge computing and IoT has


emerged as a promising solution. This document describes the concept


of IoT integrated with Edge computing as well as the state-of-the-art


of IoT Edge computing. It also proposes a general model for IoT Edge


computing. The direction of Edge computing for IoT should be


discussed in the IETF/IRTF.










Please note that it may take a couple of minutes from the time of submission


until the htmlized version and diff are available at tools.ietf.org.




The IETF Secretariat