Re: [T2TRG] Review of draft-hong-t2trg-iot-edge-computing-03

Xavier de Foy <x.defoy.ietf@gmail.com> Mon, 20 April 2020 19:10 UTC

Return-Path: <x.defoy.ietf@gmail.com>
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 6DC9E3A0C89 for <t2trg@ietfa.amsl.com>; Mon, 20 Apr 2020 12:10:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dmrm29Ze4sJA for <t2trg@ietfa.amsl.com>; Mon, 20 Apr 2020 12:10:36 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 108DF3A0C86 for <t2trg@irtf.org>; Mon, 20 Apr 2020 12:10:36 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id w20so5020513ljj.0 for <t2trg@irtf.org>; Mon, 20 Apr 2020 12:10:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BJdI9QBje7LvYJNKMHa+zp7yoBq9QAU6KBD8jUZySug=; b=RAysXoZ9f+AYugpAI6kj1ovz+XZfqcaZ9mQJpEJng2g0Iwev38WKVindNKtpXXkLOt bwjK/wE1XqYwglzXgU/uOSEGJCUQG7Dn1s97bqg5FE3eD9TONnhbgObBQq/hK40uHD2t j2ZL1m7tllucihTskT2rSkXJZS37+f/tkUGZvW9y4vM+twjhK2HtZ9EkywFrYjMHbBoK 6eI9pngusNUea+8KwfYkhp5CWEIVgzqO7DJ62fws4PpjDpymrEVgY1MnlN7a+I9AA59L MyP0sDXvU+cEHz0seyfGpD3j9F38qmMZcL31hE2zfIMUG09ESMoBmhq34SmdbmiEwTcC e4Mg==
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=BJdI9QBje7LvYJNKMHa+zp7yoBq9QAU6KBD8jUZySug=; b=KiMUiQGeEc7ulNZ3aUwjYLJptTof0eG/3bbU0jwYiqxAvfhPbO1MMLkciihADvhVI5 tuEwRYtsWHEbRDdMrfrytpAG89Q5Oq80HaxdQYSLz20DKpQRg0XProsAjyopv/QPdjMg FmBYJEpcoIJkC/dRKh4pQcnauUUDLKGIneFoPGmAeSQ6kIFakGG9oydqubgeypSos3mt V2jxwUDST7x8ky5khfWBco+A8kgy0sBvBOz8lSr/h4Al5zRk8nSCDuaEBUwH5xUqK/tC GWtE2bCGhBkgIWjzOhcp9b+LeuWUeFD28598LLNX82ARJWLfnnoDt4Rs1+g35fZvoPrH QPfg==
X-Gm-Message-State: AGi0PuaWNPm4D6Q9eKPeLtzGNaOleaQTEMHgUypmR4m9K3mJR7mWFiyV YqVnIctjS5Mt1Xtc6nOyRLTmGZet5XApqrLbRfE=
X-Google-Smtp-Source: APiQypLDzxK+sOrWlT0hFrHNRJ2kQzXBX2O+4RcNpNhrOe2xW3OipXR/7q/viUX8G5RKju6uik9sua6VWFqstkHaNUw=
X-Received: by 2002:a2e:9496:: with SMTP id c22mr9683180ljh.165.1587409834263; Mon, 20 Apr 2020 12:10:34 -0700 (PDT)
MIME-Version: 1.0
References: <662112FF-A470-4443-AD8C-3408CCC9C9CA@arm.com>
In-Reply-To: <662112FF-A470-4443-AD8C-3408CCC9C9CA@arm.com>
From: Xavier de Foy <x.defoy.ietf@gmail.com>
Date: Mon, 20 Apr 2020 15:10:21 -0400
Message-ID: <CAHYjOTYTcjQOYCE9LNHfK39J9BNPktoVs98YW2gO7rWSg14zAg@mail.gmail.com>
To: Thomas Fossati <Thomas.Fossati@arm.com>
Cc: "t2trg@irtf.org" <t2trg@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000048d04a05a3bda7c6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/RWH-rmnhrK96uTIHjgVOXo3iELk>
Subject: Re: [T2TRG] Review of draft-hong-t2trg-iot-edge-computing-03
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: Mon, 20 Apr 2020 19:10:39 -0000

Hi Thomas, thanks for taking the time to review and for the constructive
comments.

We (co-authors) basically agree with your points and will take them into
account in our next update (we will leave more time for other reviews to
come in, if any), please find additional details below.

On Fri, Apr 17, 2020 at 9:26 AM Thomas Fossati <Thomas.Fossati@arm.com>
wrote:

> Hi Xavier and co-authors,
>
> I've read your draft and found it to be a good document.  To me it looks
> like a very useful addition to the corpus produced by this RG, so I'd
> recommend adoption.
>
> Below I've left a few annotations in case you find them useful.
>
> High level:
> - Nicely structured document;
> - Some sections are fully developed, other less so, which is totally
>   normal at this stage.  In particular, I'm having a bit of trouble
>   with Section 3.5 content-/scope-wise.  I also found forward reference
>   to Appendix A slightly confusing.  It probably needs a bit of reorg
>   to disentangle the various threads into a clearer picture.
>
>
[xavier] Yes, it seems best to cut section 3.5 from appendix A, frame it
better as a current "state of the art" overview and maybe place it later in
the document (e.g. after the challenges on IoT, and before describing the
functions).


> Low level:
>
- Section 3.2.  "It is predicted that by 2019" needs refreshing :-)
> - Please remove section 2 altogether, 2119 language is not needed here;
> - Section 4.1.  Not just the BE nature of the Internet, it may also be
>   simple and pure speed-of-light limitations at work there;
>
- Section 4.3.  The dual is also true, a cloud back-end might want to
>   have a reading of the device even if it's currently asleep.  In this
>   case the edge GW caches the last reading and makes it available to the
>   cloud;
>
- Section 4.4.  There's also a threat from passive observers on the
>   device-to-cloud path that can do traffic analysis even when the
>   communication is encrypted end-to-end.  So hiding the natural traffic
>   patterns associated with the sensor network can be a further
>   requirement?
>

[xavier] Agreed on your low level comments above. This last comment seems
to be a good additional argument to use EC for IoT.

- Appendix A.  It's a good snapshot but it has an intrinsic "aging"
>   problem.  Maybe better keeping its content in a living document and
>   referencing it from here?
>

[xavier] Agreed, keeping the appendix may not be a good long term solution.
I assume by living document you mean another individual draft?


> Nits:
> - "Cloud computing has been a predominant" =>
>        "Cloud computing has become a predominant" maybe?
> - Not clear what "post-clouds" means in "we will reach the era of
>   post-clouds"; Is this an established term? I'd never heard it before.
>
> cheers!
>
>
Best Regards,
Xavier.