IETF Logo Mail Archive

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

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Tue, 02 April 2019 11:00 UTC

Return-Path: <carlesgo@entel.upc.edu>
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 D29591200E5 for <t2trg@ietfa.amsl.com>; Tue, 2 Apr 2019 04:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 jtEgo-E6BUK5 for <t2trg@ietfa.amsl.com>; Tue, 2 Apr 2019 04:00:54 -0700 (PDT)
Received: from violet.upc.es (violet.upc.es [147.83.2.51]) (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 585E11200DB for <t2trg@irtf.org>; Tue, 2 Apr 2019 04:00:54 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by violet.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id x32B0hnU042706; Tue, 2 Apr 2019 13:00:43 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 80E501D53C1; Tue, 2 Apr 2019 13:00:42 +0200 (CEST)
Received: from 131.111.5.141 by webmail.entel.upc.edu with HTTP; Tue, 2 Apr 2019 13:00:43 +0200
Message-ID: <4a181edf13e14f825d90823be4d0b491.squirrel@webmail.entel.upc.edu>
In-Reply-To: <06b11fde-2ec6-2c31-8a1a-390ebd158a2d@bassiconsulting.eu>
References: <06b11fde-2ec6-2c31-8a1a-390ebd158a2d@bassiconsulting.eu>
Date: Tue, 02 Apr 2019 13:00:43 +0200
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: Alessandro Bassi <alessandro@bassiconsulting.eu>
Cc: yghong@etri.re.kr, t2trg@irtf.org
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.100.2 at violet
X-Virus-Status: Clean
X-Greylist: ACL matched, not delayed by milter-greylist-4.3.9 (violet.upc.es [147.83.2.51]); Tue, 02 Apr 2019 13:00:43 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/Hy45orQfMspJilBQObop6n3twMI>
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: Tue, 02 Apr 2019 11:00:57 -0000

Dear Alessandro,

Please find a couple of inline comments below:

> "[...] are connected to the Internet, IoT data volume from these things
> are expected to increase explosively."
>
> why? Besides, usually a Device is not directly connected to the
> Internet. A temperature sensor is just connected to a proxi. A smart
> shoe is just connected to a smart phone via BLE. Usually, constrained
> devices do not have enough "power" to hold a complete Internet stack,
> and they are connected to a gateway.

Well, there are different classes of constrained devices [RFC 7228,
draft-bormann-lwig-7228bis-04].

>From RFC 7228, regarding Class 1 devices:

   "... are capable enough to use a
   protocol stack specifically designed for constrained nodes (such as
   the Constrained Application Protocol (CoAP) over UDP [COAP]) and
   participate in meaningful conversations without the help of a gateway
   node."

You are right that there are devices which are more constrained than Class
1 ones (i.e. Class 0 devices). These match the category you just
described.

On another topic, please note that there is support for IPv6 over BLE.
This comprises the star network topology [RFC 7668] and extended (e.g.
mesh) topologies [draft-ietf-6lo-blemesh].

Thanks,

Carles

v2.23.0 | Report a Bug | By Email