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

Toerless Eckert <tte@cs.fau.de> Tue, 16 March 2021 17:46 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 9ABA43A1546 for <iot-directorate@ietfa.amsl.com>; Tue, 16 Mar 2021 10:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 4wGxvfojAMkf for <iot-directorate@ietfa.amsl.com>; Tue, 16 Mar 2021 10:46:12 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.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 D82F73A1543 for <iot-directorate@ietf.org>; Tue, 16 Mar 2021 10:46:11 -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 7AD9054802F; Tue, 16 Mar 2021 18:46:06 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 7220F440166; Tue, 16 Mar 2021 18:46:06 +0100 (CET)
Date: Tue, 16 Mar 2021 18:46:06 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Bruce Nordman <bnordman@lbl.gov>
Cc: Carsten Bormann <cabo@tzi.org>, "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: <20210316174606.GJ8957@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> <CAK+eDP8hCCER22jt0H-3JsZUr48u=L7Vyg-XoSaKji=UNxz+Yg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAK+eDP8hCCER22jt0H-3JsZUr48u=L7Vyg-XoSaKji=UNxz+Yg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/lRJNk2wN6ZOWNpK1acDpbCcwRKk>
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 17:46:14 -0000

Nice. Have you checked work around https://tools.ietf.org/html/rfc7460 ?
Maybe thats of interest as well to you. If its missing what you need,
maybe it would still be a good basis to link off any additional information
you think is missing.

On Tue, Mar 16, 2021 at 10:38:13AM -0700, Bruce Nordman wrote:
> All--
>   As someone who works on energy use of devices in buildings, we categorize
> devices by their Primary Function - e.g. space conditioning, water heat,
> light, etc.  I have long proposed a category of Electronics as devices
> whose primary function is Information.  I have NOT studied various IoT
> definitions.  To me, IoT are devices whose primary function is other than
> Information - really everything not in Electronics - devices whose
> primary function is to be interactive with the physical world.  This is
> probably most useful as a possible supplement to another definition, not a
> replacement.
>   I do have an interest in device classification, e.g. from my web page:
> 
>    - *Device Classification*. Report on Simple Universal Device
>    Classification
>    <https://drive.google.com/open?id=0B8B9XW6B7prlc0pfWDNnUlU5dmc>
> (2014), Internet
>    Draft <http://tools.ietf.org/html/draft-nordman-classification-00> and
>    Presentation <http://tools.ietf.org/agenda/82/slides/appsawg-8.pdf> from
>    IETF 82. *Taxonomy*
>    <https://drive.google.com/open?id=0B8B9XW6B7prlU0tWdVhENDE3ODg> of
>    electronic and miscellaneous products (2006)
> 
> Thanks.
> --Bruce
> 
> On Tue, Mar 16, 2021 at 10:17 AM Toerless Eckert <tte@cs.fau.de> wrote:
> 
> > Carsten, *:
> >
> > 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.
> >
> > I for once think that (T)hings like cars as a device itself constituted
> > from maybe multiple networks with sub(T)hings will evolve to be a very
> > nice counter-example: As an electric car its not really power constrained
> > (definition: if you can waste highly toxic battery stored energy to warm
> > some passenger buttock, you are not a power constrained device ? ;-). With
> > maybe even in excess of Gigabits worth of streaming telemetry/video being
> > rocessed when autonomous, its also not bandwidth constrained. Arguably not
> >  in the sense of rfc7228 compute constrained (definition: more compute
> > power
> > than a current cell-phone is not compute constrained ? ;-).
> >
> > But such examples and fun with them aside: I think one important
> > "constraint"
> >  that we have not formalized, but which might be a better/broader
> > classifier for
> > 'non-IT' (T)hings is the absence of a personal caretaker/user for the
> > device and/or typical user-interface elements through which such a
> > caretaker
> > can normally or at last in key ops scenarios manage the device: keyboard,
> > mouse,
> > screen, or even rs232/usb console. Maybe there is some nice new
> > terminology/classification to be written to amend rfc7228. "Interfacing
> > constrained
> > devices".
> >
> > Cheers
> >     Toerless
> >
> > On Mon, Mar 15, 2021 at 11:09:44PM +0100, Carsten Bormann wrote:
> > > On 2021-03-15, at 22:55, Chakrabarti, Samita <samita.chakrabarti=
> > 40verizon.com@dmarc.ietf.org> wrote:
> > > >
> > > > Should IoT-Directorate members consider Thread Mesh stub networks as
> > one of topics under IOT-DIR scope of discussion or part of IoT work?
> > >
> > > The intention of the IETF IoT work was always to enable networks that
> > *include* constrained devices, not to limit the work to just the
> > constrained devices.
> > > So I see no contradiction to discuss less-constrained devices as well.
> > >
> > > Grüße, Carsten
> > >
> > >
> > >
> > > --
> > > Iot-directorate mailing list
> > > Iot-directorate@ietf.org
> > > https://www.ietf.org/mailman/listinfo/iot-directorate
> >
> > --
> > ---
> > tte@cs.fau.de
> >
> > --
> > Iot-directorate mailing list
> > Iot-directorate@ietf.org
> > https://www.ietf.org/mailman/listinfo/iot-directorate
> >
> 
> 
> -- 
> *Bruce Nordman*
> Lawrence Berkeley National Laboratory
> *nordman.lbl.gov <http://nordman.lbl.gov>*
> BNordman@LBL.gov
> 510-486-7089; m: 510-501-7943

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