[Iotops] WG Action: Formed IOT Operations (iotops)

The IESG <iesg-secretary@ietf.org> Fri, 05 February 2021 18:11 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: iotops@ietf.org
Delivered-To: iotops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 69EA23A0E00; Fri, 5 Feb 2021 10:11:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, iotops-chairs@ietf.org, iotops@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <161254868941.18465.1677940885094079436@ietfa.amsl.com>
Date: Fri, 05 Feb 2021 10:11:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/aRyc1P1DpnPh9iF6Q-lc7LNABr8>
Subject: [Iotops] WG Action: Formed IOT Operations (iotops)
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 05 Feb 2021 18:11:29 -0000

A new IETF WG has been formed in the Operations and Management Area. For
additional information, please contact the Area Directors or the WG Chairs.

IOT Operations (iotops)
-----------------------------------------------------------------------
Current status: Proposed WG

Chairs:
  Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
  Alexey Melnikov <alexey.melnikov@isode.com>

Assigned Area Director:
  Warren Kumari <warren@kumari.net>

Operations and Management Area Directors:
  Warren Kumari <warren@kumari.net>
  Robert Wilton <rwilton@cisco.com>

Mailing list:
  Address: iotops@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/iotops
  Archive: https://mailarchive.ietf.org/arch/browse/iotops/

Group page: https://datatracker.ietf.org/group/iotops/

Charter: https://datatracker.ietf.org/doc/charter-ietf-iotops/

The IOTOPS Working Group is chartered 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 within limited administrative
  domains

  - 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 works on a number of technologies related to IoT. This includes, but
is not limited to work done in ACE, ANIMA, CBOR, CORE, DRIP, LAKE, LPWAN,
LWIG, ROLL, SUIT, TEEP, 6LO, 6TISCH, and other working groups. IOTOPS is
intended to be a discussion venue where people can discuss how various
IoT-related technologies fit together.

IOTOPS provides a venue for IoT experts and other interested parties to
engage in discussions of operational IoT requirements, as well as proposals
for new uses of IP technology related to IoT devices and network operations.

Revision, updates, and extensions to work from existing WGs will be done in
those WGs.  Where new work may be needed, IOTOPS will help identify candidate
venues within IETF for their development.

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

2) Taking input and discussing issues related to IoT operational security.

3) Publishing operational practices.

4) Documenting requirements.

Approximately one year after chartering, the WG chairs will prepare a report
for the IESG summarizing what the group has accomplished; this is both as a
checkpoint for this working group and as a demonstration to the IESG that
this style of working groups such as this have value and should be considered
more often.