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

Ted Lemon <mellon@fugue.com> Mon, 15 March 2021 22:17 UTC

Return-Path: <mellon@fugue.com>
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 1CF053A10F6 for <iot-directorate@ietfa.amsl.com>; Mon, 15 Mar 2021 15:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 s89fWkl1OSqC for <iot-directorate@ietfa.amsl.com>; Mon, 15 Mar 2021 15:17:26 -0700 (PDT)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 E3C983A10FA for <iot-directorate@ietf.org>; Mon, 15 Mar 2021 15:17:25 -0700 (PDT)
Received: by mail-qk1-x730.google.com with SMTP id n24so3197550qkh.9 for <iot-directorate@ietf.org>; Mon, 15 Mar 2021 15:17:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=Qej47Y5ncnsZs6fJEWfxZ0dFCed1GPszzPrNu0dzj+U=; b=tgqEYLMvh7pu8B9edLC02gkJo/jlbnFbauyaKUZNvCDI+zF01/bPQi8J3BfI1nzlAe ElatvnsndsU2P/mauzPE0l4AwRL3M6q/w2xHKDfpJHtqHwKeqm4CR8cUUjNTAV8JKZXv H9Exe0K4bnc6QZAerur0CktkIm3dKzcAOFSQap1ye4PVTQCT7vWROwMaTTPjVp7ZXrD7 RNeWr2Rz5qtrUMgrsc2EPDd+moZuFeautEDwtF/26RZWSU5PGl557N2Rr9viznHTCFHM 2BV5CMnJB1MzMUUbX15pCjarbQP5A6t3vK+WI0VWxlwxt3ZoUBAcXzNxA3/i+fSZgdDl 4PHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=Qej47Y5ncnsZs6fJEWfxZ0dFCed1GPszzPrNu0dzj+U=; b=oeTZVxk37KVD1O6rY4oyiwbcwU94ESXnFYKeQ3oYYouelmF66e41mR4Nn3zvgH/VkA t7FgpMpZ9PBBetTuhjbDSRWB0ol1/2i20A2HZXc8c+IX16nhr41u+guy3ELObTAxMgTe LvqJwMfS6za7BCeapjoK/iWTmiIDX/FoGBGrQ16cc3BpaF8tlHl/fQoaLbvZrSsLkWi5 I+5djml1V2zn8x022+rzbprLr5zg+uRHVCfvzfhGE3ap1g3p6ju54O1QYby6eNjWP4Or lNfk1qNghNbwmrrTNfMa6jn9wDinmMahN8o/b1ylWwPf8NgZK9GnF4zHEYaO8C+B63aY 1XnQ==
X-Gm-Message-State: AOAM532XVl57vTDN4PFDGkyKqa8kFxKuoPkRFY6B1EcHrg2K8myfXWZJ fHV1FuCYy5XB8VyLTc5Tp9Yq3A==
X-Google-Smtp-Source: ABdhPJwas/pc5i3pWzi/J/9y7hhUlypECSLSWe6iOM0vYU7GdfD0AVBgv+BdcJRzRzDKiw32CYV3QQ==
X-Received: by 2002:a37:9f89:: with SMTP id i131mr27968969qke.160.1615846644417; Mon, 15 Mar 2021 15:17:24 -0700 (PDT)
Received: from smtpclient.apple (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id a14sm12004475qtw.80.2021.03.15.15.17.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 15 Mar 2021 15:17:23 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-1B2924C3-7C9C-4C14-B494-7754813A4A33"
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 15 Mar 2021 18:17:22 -0400
Message-Id: <752E0725-0987-442E-8900-616E09C190A1@fugue.com>
References: <SN6PR11MB31508699466A4C8E48B16FF9D76C9@SN6PR11MB3150.namprd11.prod.outlook.com>
Cc: "Chakrabarti, Samita" <samita.chakrabarti=40verizon.com@dmarc.ietf.org>, IETF IoT Directorate <iot-directorate@ietf.org>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Ari Keränen <ari.keranen@ericsson.com>, Ines Robles <mariainesrobles@googlemail.com>, Erik Kline <ek.ietf@gmail.com>, raw-chairs@ietf.org, coinrg-chairs@irtf.org
In-Reply-To: <SN6PR11MB31508699466A4C8E48B16FF9D76C9@SN6PR11MB3150.namprd11.prod.outlook.com>
To: "Schooler, Eve M" <eve.m.schooler@intel.com>
X-Mailer: iPhone Mail (18E173)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/JPQAhL7lhrF0jxAGgRt-8vXYUm0>
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: Mon, 15 Mar 2021 22:17:30 -0000

Samita, fwiw, Thread is an 802.15.4 6lowpan mesh using technology developed in the IETF, quite a bit of it in “IoT” working groups. I don’t think there’s really any question as to whether this work is IoT-relevant. We’d certainly appreciate review from the IoT directorate when the time is right. 

> On Mar 15, 2021, at 18:10, Schooler, Eve M <eve.m.schooler@intel.com> wrote:
> 
> 
> For some time, I have been wanting the IETF’s definition of IoT to mean more than constrained devices (Carsten is probably tired of me raising this point in T2T!). While constrained devices are certainly an interesting class of IoT, so are (i) low-latency IoT domains and (ii) Edge IoT contexts that generate lots of data and disrupt where the compute, control, and data management need to reside.
> My 2c’s,
> Eve
>  
> From: Iot-directorate <iot-directorate-bounces@ietf.org> On Behalf Of Chakrabarti, Samita
> Sent: Monday, March 15, 2021 2:56 PM
> To: IETF IoT Directorate <iot-directorate@ietf.org>; Eric Vyncke (evyncke) <evyncke@cisco.com>; Ari Keränen <ari.keranen@ericsson.com>; Ines Robles <mariainesrobles@googlemail.com>; Erik Kline <ek.ietf@gmail.com>
> Subject: [Iot-directorate] Question on IETF IOT-devices scope
>  
> Hello All:
>  
> In pre-IETF IOT-DIRECTORATE meeting, Ted Lemon has pointed to two documents regarding connecting the Thread Mesh networks to the traditional IP Infrastructure:
> 1) (https://datatracker.ietf.org/doc/draft-lemon-stub-networks-ps/)  - Problem Statement
> 2) https://datatracker.ietf.org/doc/draft-lemon-stub-networks/         - A possible solution
>  
> IoT-Directorate co-chairs and the responsible ADs would like to discuss if it makes sense to extend the IOT-Directorate charter
>  towards less constrained devices such as some of the home devices considered as 'things'.
> 
> The charter of the directorate says : (https://datatracker.ietf.org/group/iotdir/about/)
> 
> "The Internet of Things (IoT) refers to devices, that are often constrained in communication and computation capabilities, now becoming more commonly
>  connected to the Internet, and various services that are built on top of the capabilities these devices jointly provide. It is expected that this development will usher in more machine-to-machine communication using the Internet with no human user actively
>  involved."
> 
> Should IoT-Directorate members consider Thread Mesh stub networks as one of topics under IOT-DIR scope of discussion or part of
>  IoT work?
> 
> Thanks,
> 
> -Samita
> 
>  
> 
>  
> 
> -- 
> Iot-directorate mailing list
> Iot-directorate@ietf.org
> https://www.ietf.org/mailman/listinfo/iot-directorate