Re: [T2TRG] Comments on draft-hong-iot-edge-computing-02

홍용근 <yghong@etri.re.kr> Sun, 24 March 2019 08:54 UTC

Return-Path: <yghong@etri.re.kr>
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 DB7DE127971 for <t2trg@ietfa.amsl.com>; Sun, 24 Mar 2019 01:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.921
X-Spam-Level:
X-Spam-Status: No, score=-0.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 LtHMNbV3sHes for <t2trg@ietfa.amsl.com>; Sun, 24 Mar 2019 01:54:30 -0700 (PDT)
Received: from mscreen.etri.re.kr (mscreen.etri.re.kr [129.254.9.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2759E127984 for <T2TRG@irtf.org>; Sun, 24 Mar 2019 01:54:29 -0700 (PDT)
Received: from unknown (HELO smtpeg.etri.re.kr) (129.254.27.142) by 129.254.9.16 with ESMTP; 24 Mar 2019 17:54:22 +0900
X-Original-SENDERIP: 129.254.27.142
X-Original-MAILFROM: yghong@etri.re.kr
X-Original-RCPTTO: draft-hong-iot-edge-computing@ietf.org, T2TRG@irtf.org, matthias.kovatsch@huawei.com
Received: from SMTP5.etri.info (129.254.28.75) by SMTPEG2.etri.info (129.254.27.142) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 24 Mar 2019 17:54:28 +0900
Received: from SMTP1.etri.info ([169.254.1.52]) by SMTP5.etri.info ([129.254.28.75]) with mapi id 14.03.0319.002; Sun, 24 Mar 2019 17:54:26 +0900
From: 홍용근 <yghong@etri.re.kr>
To: Frank MATTHIAS KOVATSCH <matthias.kovatsch@huawei.com>, "T2TRG@irtf.org" <T2TRG@irtf.org>, "draft-hong-iot-edge-computing@ietf.org" <draft-hong-iot-edge-computing@ietf.org>
Thread-Topic: Comments on draft-hong-iot-edge-computing-02
Thread-Index: AdThgm++l77M7UB7SWKPXCYtIqDFowAmXMsw
Date: Sun, 24 Mar 2019 08:54:26 +0000
Message-ID: <F4BDF78D6E708E489DF2D720B16F87B7B8EA6B52@SMTP1.etri.info>
References: <F800760CC25E5345BDBCD9213249A3E3DDB56F@lhreml505-mbb.china.huawei.com>
In-Reply-To: <F800760CC25E5345BDBCD9213249A3E3DDB56F@lhreml505-mbb.china.huawei.com>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [129.254.26.37]
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/YX-87dHWbk8R1BIFNcp-9YaLCvA>
Subject: Re: [T2TRG] Comments on draft-hong-iot-edge-computing-02
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: Sun, 24 Mar 2019 08:54:33 -0000

Dear Matthias.

Thanks for your valuable comments.
On t2trg IETF 104 pre-meeting, we had a good time to discuss Edge and IoT.

See my response inline below. 

Best regards.

Yong-Geun.

-----Original Message-----
From: Frank MATTHIAS KOVATSCH [mailto:matthias.kovatsch@huawei.com] 
Sent: Sunday, March 24, 2019 12:04 AM
To: T2TRG@irtf.org; draft-hong-iot-edge-computing@ietf.org
Subject: Comments on draft-hong-iot-edge-computing-02

Dear group and authors

Here are some comments on the document:

> draft-hong-iot-edge-computing

We should rename to draft-hong-t2trg-iot-edge-computing to associate the draft with T2TRG

[Yong-Geun] When we submitted this draft at first, we were not sure that what is the best place to discuss. But, during IETF 103 and IETF 104 meeting, we believe that t2trg cloud be proper place to discuss. When we submit updated version, we would rename the draft name as you suggested.

> 3.2. IoT with Cloud computing

Under Background, maybe rather focus on Cloud Computing alone first (--> "3.2. Cloud Computing")

It would also be good to introduce Edge Computing stand-alone as well before integrating with IoT.

[Yong-Geun] The reason why we integrated IoT with Cloud computing and Edge computing is that we wanted to focus on IoT services with Cloud computing and Edge computing. But, it is also suitable to discuss Cloud computing and Edge computing before integrating with IoT. We will reflect this change in a next revision.

> 3.3. IoT Environmental changes

Instead of already talking about "era of post-Clouds", maybe the background should first simply list the changes IoT brings. However, that would be a duplication of 4. New challenges of IoT.

> 45% of the data created in IoT will be stored, processed, analyzed and acted close to, or at the edge of the network

This is already a prediction of IoT Edge Computing, but it is unclear what led to this prediction. The only argument appears to be users "producing data with their mobile devices".

Overall, I would remove this section from Background and focus on giving well-structures reasons for IoT Edge Computing under 4. New challenges of IoT

[Yong-Geun] Yes, it looks like that Section 3.3 and Section 4 has a duplication. We would focus on Section.4 New challenge of IoT and remove Section 3.3 in a revision.