Re: [T2TRG] Comments on draft-hong-iot-edge-computing-02
Alessandro Bassi <alessandro@bassiconsulting.eu> Tue, 02 April 2019 11:08 UTC
Return-Path: <alessandro@bassiconsulting.eu>
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 1D4F41200EA for <t2trg@ietfa.amsl.com>; Tue, 2 Apr 2019 04:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 NuKc5z85ZaNE for <t2trg@ietfa.amsl.com>; Tue, 2 Apr 2019 04:08:30 -0700 (PDT)
Received: from m-r1.th.seeweb.it (m-ra.th.seeweb.it [5.144.164.173]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90EF21200DE for <t2trg@irtf.org>; Tue, 2 Apr 2019 04:08:30 -0700 (PDT)
Received: from [192.168.1.166] (unknown [37.143.118.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by m-r1.th.seeweb.it (Postfix) with ESMTPSA id A09A5211DA; Tue, 2 Apr 2019 13:08:26 +0200 (CEST)
To: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
Cc: yghong@etri.re.kr, t2trg@irtf.org
References: <06b11fde-2ec6-2c31-8a1a-390ebd158a2d@bassiconsulting.eu> <4a181edf13e14f825d90823be4d0b491.squirrel@webmail.entel.upc.edu>
From: Alessandro Bassi <alessandro@bassiconsulting.eu>
Message-ID: <0264cc1a-9f98-643d-9d14-9baf163b644b@bassiconsulting.eu>
Date: Tue, 02 Apr 2019 13:08:26 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <4a181edf13e14f825d90823be4d0b491.squirrel@webmail.entel.upc.edu>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/odJ9Ngsru860a6NNovw0dDSWgJY>
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:08:32 -0000
Dear Carles, indeed, you are right: in my comment I should have specified the Device class I was referring to. thanks! best, --alex On 02. 04. 19 13:00, Carles Gomez Montenegro wrote: > 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 >
- [T2TRG] Comments on draft-hong-iot-edge-computing… Alessandro Bassi
- Re: [T2TRG] Comments on draft-hong-iot-edge-compu… Carles Gomez Montenegro
- Re: [T2TRG] Comments on draft-hong-iot-edge-compu… Alessandro Bassi
- Re: [T2TRG] Comments on draft-hong-iot-edge-compu… 홍용근
- Re: [T2TRG] Comments on draft-hong-iot-edge-compu… Alessandro Bassi
- Re: [T2TRG] Comments on draft-hong-iot-edge-compu… Yong-Geun Hong