Re: [Din] [T2TRG] [T2TRG/Din] Discussion New draft for draft-hong-iot-edge-computing-00.txt

Jungha Hong <jhong@etri.re.kr> Fri, 13 July 2018 01:16 UTC

Return-Path: <jhong@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 3ABFA130EAF for <din@ietfa.amsl.com>; Thu, 12 Jul 2018 18:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 na95FyC_rupc for <din@ietfa.amsl.com>; Thu, 12 Jul 2018 18:16:04 -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 ECBEF127333 for <din@irtf.org>; Thu, 12 Jul 2018 18:16:03 -0700 (PDT)
Received: from unknown (HELO smtpeg.etri.re.kr) (129.254.27.141) by 129.254.9.16 with ESMTP; 13 Jul 2018 10:16:00 +0900
X-Original-SENDERIP: 129.254.27.141
X-Original-MAILFROM: jhong@etri.re.kr
X-Original-RCPTTO: din@irtf.org, joosang.youn@gmail.com, wjgo_10009@btinternet.com, t2trg@irtf.org
Received: from SMTP4.etri.info (129.254.28.74) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 13 Jul 2018 10:16:02 +0900
Received: from SMTP1.etri.info ([169.254.1.174]) by SMTP4.etri.info ([10.2.6.33]) with mapi id 14.03.0319.002; Fri, 13 Jul 2018 10:15:58 +0900
From: Jungha Hong <jhong@etri.re.kr>
To: "wjgo_10009@btinternet.com" <wjgo_10009@btinternet.com>, "t2trg@irtf.org" <t2trg@irtf.org>, "din@irtf.org" <din@irtf.org>
CC: =?utf-8?B?7ZmN7Jqp6re8?= <yghong@etri.re.kr>, "joosang.youn@gmail.com" <joosang.youn@gmail.com>
Thread-Topic: RE: [T2TRG] [T2TRG/Din] Discussion New draft for draft-hong-iot-edge-computing-00.txt
Thread-Index: AQHUGdw8yfbAFr0KfE+MCgkQ5R26YqSMWPKx
Date: Fri, 13 Jul 2018 01:15:56 +0000
Message-ID: <F8EFC212DF9A004DA18AA8FB011E4233B79BD3A4@SMTP1.etri.info>
References: <8735791.11744.1531387735646.JavaMail.root@webmail22.bt.ext.cpcloud.co.uk>, <18064017.22162.1531398660824.JavaMail.defaultUser@defaultHost>
In-Reply-To: <18064017.22162.1531398660824.JavaMail.defaultUser@defaultHost>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-new-displayname: SnVuZ2hhIEhvbmc=
x-originating-ip: [129.254.28.44]
Content-Type: multipart/alternative; boundary="_000_F8EFC212DF9A004DA18AA8FB011E4233B79BD3A4SMTP1etriinfo_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/9N400cEV6yKU-gPMRif-cT9m6n8>
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: Fri, 13 Jul 2018 01:16:07 -0000

Dear William Overington.

Thanks for clarifying your two suggestions.
Although those are not exactly addressed in our draft, it seems to be meaningful concerns.
We hope to find a  good approach on how to consider your two suggestions.

Due to lack of time for discussion on our draft before Montreal meeting, we would like to ask you to contribute on those concerns
in the next revision of this draft if you are not planning to make your own draft.

Thanks,
Jungha Hong







________________________________
보낸 사람 : "William_J_G Overington" <wjgo_10009@btinternet.com>
보낸 날짜 : 2018-07-12 21:31:19 ( +09:00 )
받는 사람 : 홍정하 <jhong@etri.re.kr>kr>, t2trg@irtf.org <t2trg@irtf.org>rg>, din@irtf.org <din@irtf.org>
참조 : 홍용근 <yghong@etri.re.kr>kr>, joosang.youn@gmail.com <joosang.youn@gmail.com>
제목 : Re: RE: [T2TRG] [T2TRG/Din] Discussion New draft for draft-hong-iot-edge-computing-00.txt



Hi





> I wonder how your two suggestions are related to our draft.





> Could you please clarify your suggestions more related to the draft?





In section 5.3 is the following.





> In spite of such benifits of Edge computing in IoT services, it has challenges such as programmability, naming, data abstraction, service management, privacy and security and optimization metrics.





My first suggestion relates to naming, data abstraction and service management.





My second suggestion relates to programmability.





Consider please a thought experiment.





Suppose that there is a type of thing that can measure air temperature, air pressure, location in latitude and longitude. Let us call it a type 8001 device.





Suppose that the type 8001 device has built into it a mobile telephone that can receive and send emails.





When asked, by email, a type 8001 device can make a measurement and send a reply, listing any one or more of air temperature, air pressure, location in latitude and longitude. Each particular type 8001 device has its own unique telephone number.





As a first stage of this thought experiment, let us suppose that one of the type 8001 devices is located in Italy, one is located in Greece and one is located in Latvia.





Suppose that there is a type of thing than can ask a type 8001 device for measurement data of one or more of air temperature, air pressure, location in latitude and longitude. Each has a display screen that may sometimes be being viewed by a human being who knows the local language and may, but need not, know any other language. Let us call it a type 8002 device.





Let us suppose that one of the type 8002 devices is located in Portugal and one is located in Japan.





My first suggestion allows questions from a preset list of questions to be asked by a type 8002 device independently of any human language and a reply to be sent from a type 8001 device independently of any human language, yet also displayable in any human language that can be displayed using the Universal Character Set simply by having a sentence.dat file for the particular human language loaded into the type 8002 device.





In this context, the Universal Character Set may be thought of as the same as the Unicode character set.





As regards my second suggestion, suppose please that after some time it is decided that the format of the email sent in response to an enquiry should always begin by specifying the location at which the measurements of air temperature and air pressure have been made, even if not explicitly requested.





If the type 8001 devices all have to be altered by a service technician this could take a while and be expensive. Also, if a type 8001 device can be made by several manufacturers and some use one microprocessor and some use another and so on with either direct machine code programs, or an app running on one of a number of different operating system platforms the task could be enormous.





Yet suppose that each type 8001 device runs a program that is written in a portable interpretable object code, the same code on each type 8001 device. Certainly the interpreter software for a particular type 8001 device may well be different from the interpreter software for a type 8001 device made by another manufacturer; that is not a problem provided that each interpreter software program complies to the specification for how to interpret the portable interpretable object code by running it in a software construct known as a virtual machine.





Given that scenario, the desired software update can be achieved by sending each type 8001 device an email, with appropriate security of provenance, to update the application program on the type 8001 device.





Comments are welcome. Discussion of this thought experiment is welcome





William Overington





Thursday 12 July 2018







----Original message----





From : jhong@etri.re.kr



Date : 2018/07/12 - 02:17 (GMTDT)



To : wjgo_10009@btinternet.com, t2trg@irtf.org, din@irtf.org



Cc : yghong@etri.re.kr, joosang.youn@gmail.com



Subject : RE: [T2TRG] [T2TRG/Din] Discussion New draft for draft-hong-iot-edge-computing-00.txt





Dear William Overington,





Thanks for your email.





I wonder how your two suggestions are related to our draft.





Could you please clarify your suggestions more related to the draft?





Thanks,





Jungha Hong