Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draft for draft-hong-iot-edge-computing-00.txt
홍용근 <yghong@etri.re.kr> Tue, 17 July 2018 09:57 UTC
Return-Path: <yghong@etri.re.kr>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0B78130F33 for <din@ietfa.amsl.com>; Tue, 17 Jul 2018 02:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.922
X-Spam-Level:
X-Spam-Status: No, score=-0.922 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] 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 aZ1GK5JDnlbB for <din@ietfa.amsl.com>; Tue, 17 Jul 2018 02:57:19 -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 BED0E130DC1 for <din@irtf.org>; Tue, 17 Jul 2018 02:57:18 -0700 (PDT)
Received: from unknown (HELO smtpeg.etri.re.kr) (129.254.27.141) by 129.254.9.16 with ESMTP; 17 Jul 2018 18:57:08 +0900
X-Original-SENDERIP: 129.254.27.141
X-Original-MAILFROM: yghong@etri.re.kr
X-Original-RCPTTO: din@irtf.org, joosang.youn@gmail.com, laura.marie.feeney@it.uu.se, t2trg@irtf.org
Received: from SMTP3.etri.info (129.254.28.73) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 17 Jul 2018 18:57:12 +0900
Received: from SMTP1.etri.info ([169.254.1.174]) by SMTP3.etri.info ([10.2.6.32]) with mapi id 14.03.0319.002; Tue, 17 Jul 2018 18:57:13 +0900
From: 홍용근 <yghong@etri.re.kr>
To: L M Feeney <laura.marie.feeney@it.uu.se>, 홍정하 <jhong@etri.re.kr>, "t2trg@irtf.org" <t2trg@irtf.org>, "din@irtf.org" <din@irtf.org>
CC: "joosang.youn@gmail.com" <joosang.youn@gmail.com>
Thread-Topic: [T2TRG] [T2TRG/Din] Discussion New draft for draft-hong-iot-edge-computing-00.txt
Thread-Index: AQHUF/e/n5iJTSi4eE21AFX5KjiNp6SRvs4AgAF0dFA=
Date: Tue, 17 Jul 2018 09:57:13 +0000
Message-ID: <F4BDF78D6E708E489DF2D720B16F87B7B81C05C7@SMTP1.etri.info>
References: <F8EFC212DF9A004DA18AA8FB011E4233B79BCC1C@SMTP1.etri.info> <82dc8fd0-3ea0-c72f-2fff-cf42c1867769@it.uu.se>
In-Reply-To: <82dc8fd0-3ea0-c72f-2fff-cf42c1867769@it.uu.se>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.0.96]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/bmyBRZUp8RBmo0tQJNyEStGMYw0>
Subject: Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draft for draft-hong-iot-edge-computing-00.txt
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.27
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: Tue, 17 Jul 2018 09:57:33 -0000
Dear Laura Marie Feeney. Thanks for your valuable comments. For regarding of architectural issue, the current draft does not include an architectural context and I agree your point. If we consider a requirement such as latency, this requirement is very related to a network architecture and its capabilities. I agree that it would be more better to consider a network architecture when we talk about requirements. For implementing IoT Edge computing, we can utilize many open sources and existing commercial products. Even though we can describe an architecture of IoT Edge computing based on some typical open sources and existing commercial products, we hope to find common architecture of IoT Edge computing and describe common parts of them. I appreciate your comments and we would try to describe architecture contexts in a next revision. Best regards. Yong-Geun. -----Original Message----- From: L M Feeney [mailto:laura.marie.feeney@it.uu.se] Sent: Tuesday, July 17, 2018 5:23 AM To: 홍정하; t2trg@irtf.org; din@irtf.org Cc: 홍용근; joosang.youn@gmail.com Subject: Re: [T2TRG] [T2TRG/Din] Discussion New draft for draft-hong-iot-edge-computing-00.txt Dear Jungha and team and all, I think the document addresses important and interesting issues. I agree with Thorsten Dahm that it lists problems (generally in the form of requirements) and misses solutions. But for me, it also misses an architectural context for the challenges that are highlighted by the document. For example, the discussion of latency is really about a requirement. It would be helpful to understand more about the challenge: Where does the important delay and jitter come from? Is it in the wireless access or is due to potentially high traffic loads in the network infrastructure at the edge? Or is the bottleneck in coordinating resources needed for edge processing? Perhaps working through these sorts of questions would highlight where the most useful directions are? Of course, the answers might be different for different architecture models of the network and the edge functionality: A RPL-based network operating in unlicensed spectrum and connecting via home WiFi to edge services being provided to users spread over a large geographic area might be quite different from a network that uses a mobile operator's radio access network to connect to edge services for a factory environment. Perhaps the use cases in section 5 would be helpful in focusing on a small number of representative architectures? Thanks and best regards, Laura ---- Laura Marie Feeney Uppsala University, Sweden On 2018-07-10 04:43, Jungha Hong wrote: > Dear all, > > We submitted a draft tiled "Problem Statement of IoT integrated with > Edge Computing". > > https://www.ietf.org/internet-drafts/draft-hong-iot-edge-computing-00.txt > > This is the first edition and its purpose is to discuss the followings: > > * New challenges of IoT by the environment changes > * Edge computing as an emerging technology in IoT > * Use cases of Edge computing in IoT > * IETF/IRTF directions for Edge computing in IoT > > We would like to start a discussion first on the mailing list before the > Montreal meeting. > > Please take a look and give us any comments. > > We hope to get an enough comments for a side meeting in Montreal. > > I am copying it to DINRG as well in case they might be interested in > this topic. > > Thanks, > > Jungha Hong > > > ------------------------------------------------------------------------ > *보낸 사람 : *"internet-drafts@ietf.org" <internet-drafts@ietf.org> > *보낸 날짜 : *2018-07-02 21:22:08 ( +09:00 ) > *받는 사람 : *홍정하 <jhong@etri.re.kr>, 홍용근 <yghong@etri.re.kr>, 홍 > 정하 <jhong@etri.re.kr>, Joo-Sang Youn <joosang.youn@gmail.com>, 홍용근 > <yghong@etri.re.kr> > *참조 : * > *제목 : *New Version Notification for draft-hong-iot-edge-computing-00.txt > > > A new version of I-D, draft-hong-iot-edge-computing-00.txt > has been successfully submitted by Jungha Hong and posted to the > IETF repository. > > Name: draft-hong-iot-edge-computing > Revision: 00 > Title: Problem Statement of IoT integrated with Edge Computing > Document date: 2018-07-02 > Group: Individual Submission > Pages: 12 > URL: > https://www.ietf.org/internet-drafts/draft-hong-iot-edge-computing-00.txt > Status: https://datatracker.ietf.org/doc/draft-hong-iot-edge-computing/ > Htmlized: https://tools.ietf.org/html/draft-hong-iot-edge-computing-00 > Htmlized: > https://datatracker.ietf.org/doc/html/draft-hong-iot-edge-computing > > > Abstract: > This document describes new challenges for IoT services issued by the > changes of the IoT environment. In order to address those new > challenges, the integration of Edge computing and IoT has been > emerged as a promising solution. This document provides the concept > of IoT integrated with Edge computing as well as its use cases to > discuss the benefits and challenges of Edge computing mainly focused > on IoT data. The direction of Edge computing for IoT should be > discussed in 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 > > > > _______________________________________________ > T2TRG mailing list > T2TRG@irtf.org > https://www.irtf.org/mailman/listinfo/t2trg > När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/ E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: http://www.uu.se/om-uu/dataskydd-personuppgifter/
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… William_J_G Overington
- [Din] [T2TRG/Din] Discussion New draft for draft-… Jungha Hong
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… Thorsten Dahm
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… William_J_G Overington
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… Mats Wichmann
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… Jungha Hong
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… Jungha Hong
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… Jungha Hong
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… Jungha Hong
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… William_J_G Overington
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… Thorsten Dahm
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… William_J_G Overington
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… William_J_G Overington
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… 홍용근
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… Jungha Hong
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… William_J_G Overington
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… L M Feeney
- Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draf… 홍용근