Re: [Iot-directorate] Question on IETF IOT-devices scope

Toerless Eckert <tte@cs.fau.de> Tue, 16 March 2021 18:26 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: iot-directorate@ietfa.amsl.com
Delivered-To: iot-directorate@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AC293A0CB2 for <iot-directorate@ietfa.amsl.com>; Tue, 16 Mar 2021 11:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level:
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no 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 M7ANV6Fko-cA for <iot-directorate@ietfa.amsl.com>; Tue, 16 Mar 2021 11:26:10 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B2B73A0C06 for <iot-directorate@ietf.org>; Tue, 16 Mar 2021 11:26:10 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2DBA754802F; Tue, 16 Mar 2021 19:26:05 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 28BA4440166; Tue, 16 Mar 2021 19:26:05 +0100 (CET)
Date: Tue, 16 Mar 2021 19:26:05 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Carsten Bormann <cabo@tzi.org>
Cc: "Chakrabarti, Samita" <samita.chakrabarti=40verizon.com@dmarc.ietf.org>, Ari Ker?nen <ari.keranen@ericsson.com>, IETF IoT Directorate <iot-directorate@ietf.org>, Ines Robles <mariainesrobles@googlemail.com>, Erik Kline <ek.ietf@gmail.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Message-ID: <20210316182605.GK8957@faui48f.informatik.uni-erlangen.de>
References: <CAHYRG6Nhh4YZrs_0jLTyFJu5XTLLVy_SWT0+rN8EZ2JanY8UxQ@mail.gmail.com> <C7620420-A4A4-45D7-8FDD-922C0B90C796@tzi.org> <20210316171644.GH8957@faui48f.informatik.uni-erlangen.de> <D6CF885A-2280-4D29-9F9D-6C56B5BCB488@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D6CF885A-2280-4D29-9F9D-6C56B5BCB488@tzi.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/ZH9M8v9RwhYmng6Bzv3AAkIEzqU>
Subject: Re: [Iot-directorate] Question on IETF IOT-devices scope
X-BeenThere: iot-directorate@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for the IoT Directorate Members <iot-directorate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-directorate/>
List-Post: <mailto:iot-directorate@ietf.org>
List-Help: <mailto:iot-directorate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2021 18:26:14 -0000

Thanks. And of course i did not mean that there was anything wrong with
rfc7228, i just think we had a lot more focus on rfc7228 type constrained
devices than other IoT devices, purely because of the work that was brought
to the IETF.

On Tue, Mar 16, 2021 at 06:52:43PM +0100, Carsten Bormann wrote:
> On 2021-03-16, at 18:16, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > Imho, no good deed goes unpunished: Maybe because of rfc7228 there is a
> > little bit of the mis-perception in the IETF that Io(T)hings are primarily things
> > with such memory/bandwidth/power constraints. Of course, a lot of
> > low-power networking work the IETF will have overall contributed to this
> > biased thinking we may have.
> 
> There is nothing wrong with RFC 7228 (except maybe that we haven???t obsoleted it yet with https://datatracker.ietf.org/doc/html/draft-bormann-lwig-7228bis-06):
> It argues that scaling up to the number of Things(*) we actually need requires reducing both the cost of the device itself and the power consumption added by it.  That will maintain a long-term drive to Things that are on the less powerful side (think milliwatt), even if today, still at the bottom of the S-curve, there are lots of wasteful (think watt or more) devices.
> 
> Grüße, Carsten
> 
> 
> (*) A definition of Thing is in https://www.ietf.org/archive/id/draft-ietf-asdf-sdf-05.html#name-terminology-and-conventions ??? there is some discussion about the word ???device??? here (which may be too narrow), but there is no discussion of constrainedness in that definition.

-- 
---
tte@cs.fau.de