Re: [Iotops] IOTOPS Draft Charter

Qin Wu <bill.wu@huawei.com> Tue, 03 November 2020 13:53 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7B93A0AC1 for <iotops@ietfa.amsl.com>; Tue, 3 Nov 2020 05:53:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 loNQFGHKJMLL for <iotops@ietfa.amsl.com>; Tue, 3 Nov 2020 05:53:32 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 553C03A00C9 for <iotops@ietf.org>; Tue, 3 Nov 2020 05:53:32 -0800 (PST)
Received: from lhreml712-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id D3B7AFEB9D0211E942E4 for <iotops@ietf.org>; Tue, 3 Nov 2020 13:53:30 +0000 (GMT)
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 3 Nov 2020 13:53:30 +0000
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Tue, 3 Nov 2020 13:53:30 +0000
Received: from DGGEML511-MBS.china.huawei.com ([169.254.4.33]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0487.000; Tue, 3 Nov 2020 21:53:26 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>, "iotops@ietf.org" <iotops@ietf.org>
Thread-Topic: IOTOPS Draft Charter
Thread-Index: Adax5sJDqtFl3VHrQtux5YlG1X1z5w==
Date: Tue, 03 Nov 2020 13:53:25 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADB1F914@dggeml511-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.101.103]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/73GhHUPbNMld019HmL1iHSDSBGk>
Subject: Re: [Iotops] IOTOPS Draft Charter
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2020 13:53:34 -0000

-----邮件原件-----
发件人: Iotops [mailto:iotops-bounces@ietf.org] 代表 Rob Wilton (rwilton)
发送时间: 2020年11月3日 21:10
收件人: iotops@ietf.org
主题: [Iotops] IOTOPS Draft Charter

Hi,

An updated draft charter for IOTOPS (also inline) has been posted to https://datatracker.ietf.org/doc/charter-ietf-iotops/

This charter has received a couple of rounds of informal review from other IESG members.  Warren and I believe that it is close to the state where we could ask the IESG to ballot on the draft version before it goes out for public review.

Hence, I think that this would be an appropriate time for discussion of the proposed charter on the @iotops alias.

---

The IOTOPS Working Group is for the discussion of operational issues related to Internet of Things (IoT) devices, in particular related to device onboarding and lifecycle management.

IoT has a rather nebulous definition with different meanings for different people.

For the purposes of this WG, its focus is on devices that are:
  - networked - either to the Internet or isolated domain(s),

[Qin]: It is not clear what isolated domains means? Home network, enterprise network, campus network, Content delivery network, IoT network,
I would suggest to replace isolated domain(s) with limited domain defined in RFC8799.

  - have a very limited end user interface or no end-user interface at all,
  - are deployed in sufficiently large numbers that they cannot easily be
  managed or maintained manually.

The IETF is or has worked on a number of technologies related to IoT. These include work done in ANIMA, CBOR, CORE, DRIP, LAKE, LPWAN, LWIG, ROLL, SUIT, and 6TISCH.  IOTOPS is intended to be a discussion venue where people can discuss how the various technologies developed in these WGs fit together, what gaps remain, what has been learnt from deploying these, etc.

IOTOPS will solicit input on IoT-device-related operational issues and practices, and existing and proposed technologies related to the deployment, operational management, and lifecycle management of IoT devices.  IOTOPS provides a venue for IoT experts and other interested parties to engage in discussions of IoT requirements of networking standards, as well as proposals for new uses of IP technology in IoT specific scenarios.

Revision, updates, and extensions related to existing WGs will be done in those WGs.  Where new protocols may be needed, IOTOPS will help identify candidate venues within IETF for their development. In this context, IOTOPS will operate with a "dispatch" model as described in RFC 7957.

IOTOPS WG charter is restricted to:

1) Taking input and discussing issues related to the operational management of IoT devices. This includes (but is not limited to):
  - factory provisioning of devices
  - onboarding of devices
  - access control of devices to network resources
  - administrative control of devices
  - software/firmware upgrades
  - isolation/quarantine of devices
  - remediation of broken devices
  - end of life management of devices

[Qin]: Why limit to talking input and discussing issues, I think IoTOPS could be a better place if there is no good home for some IoT on boarding work, I am not suggest to put all work in this WG,
But at least some network based solution should be documented here.

2) Discussing issues related to IoT operational security.

[Qin]: How about also covering privacy issues in IoT scenarios?

3) Publish operational practice and document requirements.

---

Regards,
Rob

--
Iotops mailing list
Iotops@ietf.org
https://www.ietf.org/mailman/listinfo/iotops