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

Thorsten Dahm <thorstendlux@google.com> Thu, 12 July 2018 11:56 UTC

Return-Path: <thorstendlux@google.com>
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 E59691310ED for <din@ietfa.amsl.com>; Thu, 12 Jul 2018 04:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level:
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 YL-meDskFFhh for <din@ietfa.amsl.com>; Thu, 12 Jul 2018 04:56:02 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2B0A1292F1 for <din@irtf.org>; Thu, 12 Jul 2018 04:56:01 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id l15-v6so1653096lji.6 for <din@irtf.org>; Thu, 12 Jul 2018 04:56:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3SPNoSTidmcAv+3lbRHN0MuK6o2jf5TpJShNH777aXc=; b=mUVWyxyb1h7GWi2u9UvxuSjnaIjXrsN8sC0q/j33iT2wMOgoywmMxbYRZzK3uhGc/B 1LI9ML//f15ILsaduJJCIdGaeQxXptJyOC7Noj38qRpCJgbHYXOjIkHA94+Y+I4+wQ1+ v3Ri9qOm+fgve2NnCft1Wk7+8S6pCtc1Lfc10EZgMIggFmIlZYWoXiPgRmmOG+Lg8Yub WFf6G6MecVqmhpLc+bUQ0lLII3tZCXpk1ifdR9bfmU3+a/9gOkPa95Uq4MdUCSZlca8b QbwM7Dm/VO565fRp1vsKIiMWHy/agiAY9NuMqxxW1LXncVHWui3jVcRhdN0XMaBNkSPK V+gQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3SPNoSTidmcAv+3lbRHN0MuK6o2jf5TpJShNH777aXc=; b=FkV/f2CZVn9X8UND+NuICPtCz4wczM40eGkYAoVug9toMq7+AsoXp9uh/bdlGV+uP5 nCoI3uvTr/tntHCuZWUSZ5kJT8vpPCehY7SxakpzSPJtnLSUzrdTItRNGMFDgNbwuUpz 1uaxd2hnzDlfUrgStRhxMchqu4portGARK1wldab6L18HXBFcXXbExo23fpIwmxerDpI Ql0kDK8PDsWr3OFXVgWFHZTWvI6ZJ18oehQ8yWQizOsMmpyrDsGP3S76d4MwT6FLR8E7 coR62L4CPlOyAsjz7kGkaCkflzfJ1US82rax1R+SiwHb4R7O9nTYd30KrTYKtCuJO0Ou j6jA==
X-Gm-Message-State: AOUpUlEc+LKMDvv4ZsUiPM4W0B/Jd3aKkfNazNIsF017HpVWIwjbDQlc d2sWpd+jTUEB+Se4HLLKphSEmHVeZeG5a7rZp47VpQ==
X-Google-Smtp-Source: AAOMgpf4b6haZ/Eb43ENPoCa4uAtaper+kLjCQ+U42IRGVAAP5BTdeHYYQ+wFN8Uz60tZXHOX1MfDoP6vJ76ajwttIY=
X-Received: by 2002:a2e:259:: with SMTP id 86-v6mr409869ljc.107.1531396559709; Thu, 12 Jul 2018 04:55:59 -0700 (PDT)
MIME-Version: 1.0
References: <28186522.28665.1531320642798.JavaMail.root@webmail08.bt.ext.cpcloud.co.uk> <32528273.30719.1531322433684.JavaMail.defaultUser@defaultHost>
In-Reply-To: <32528273.30719.1531322433684.JavaMail.defaultUser@defaultHost>
From: Thorsten Dahm <thorstendlux@google.com>
Date: Thu, 12 Jul 2018 12:55:31 +0100
Message-ID: <CAB4uO_y6XTuMvAnyn+46WpPScwSgUS-M8MPA-T3jVByH90+PQA@mail.gmail.com>
To: wjgo_10009@btinternet.com
Cc: din@irtf.org, "t2trg@irtf.org" <t2trg@irtf.org>, jhong@etri.re.kr, joosang.youn@gmail.com, yghong@etri.re.kr
Content-Type: multipart/alternative; boundary="000000000000f42e210570cc0b3c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/oqOTPzuGe2MvHbmGTg5Jt38lSGs>
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: Thu, 12 Jul 2018 11:56:06 -0000

Hi William,

Am Mi., 11. Juli 2018 um 16:20 Uhr schrieb William_J_G Overington
<wjgo_10009=40btinternet.com@dmarc.ietf.org>:

> Something that I have been wondering about is this: How will devices
> communicate? For example, will it be by email technology or what?


I'm sure no IoT device will use email as primary communication method. :-)
If you wonder what protocols are used by IoT, please have a look at COAP,
MQTT, BACnet, and things like CoRE.


> For example, could an IoT device have a mobile telephone built into it so
> that it could send an email by a mobile telephone connection?
>
>
too expensive, hard to manage (user would have to buy SIM cards / sign
mobile phone contracts for every device etc.). Most devices will use
Ethernet, Wifi or Bluetooth / BLE. Some will also use technologies like
ZigBee or Thread.

Maybe it would be more suitable to evaluate how well the protocols above
work with edge computing setups and if / how the protocols could be
improved?

Regards,
Thorsten


-- 
Thorsten Dahm

Network Engineer
Google Ireland Ltd.
The Gasworks, Barrow Street
Dublin 4,  Ireland

Registered in Dublin, Ireland
Registration Number: 368047