[secdir] [new-work] WG Review: IOT Operations (iotops)

[The IESG <[e-mail]>]

The IOT Operations (iotops) WG in the Operations and Management Area of the
IETF is undergoing rechartering. The IESG has not made any determination yet.
The following draft charter was submitted, and is provided for informational
purposes only. Please send your comments to the IESG mailing list
([e-mail]) by 2025-04-14.

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

Chairs:
  Alexey Melnikov <[e-mail]>
  Henk Birkholz <[e-mail]>

Assigned Area Director:
  Mohamed Boucadair <[e-mail]>

Operations and Management Area Directors:
  Mahesh Jethanandani <[e-mail]>
  Mohamed Boucadair <[e-mail]>

Mailing list:
  Address: [e-mail]
  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.

The IOTOPS working group focuses 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, and * are deployed in sufficiently large numbers that they cannot easily
be managed or maintained manually.

The IETF defines a number of standards related to IoT. This includes, but is
not limited to, work done in ACE, ANIMA, CBOR, CORE, DRIP, LAKE, ROLL, SCHC,
SUIT, TEEP, 6LO, and other working groups. IOTOPS is intended to be a venue
to discuss how various IoT-related technologies fit together. Specifically,
IOTOPS provides a venue for IoT experts and other interested parties to
engage in discussions of operational IoT requirements, as well as approaches
for new uses of IP technology related to IoT devices and network operations.

Likewise, the IOTOPS working group welcomes presentations from operators
sharing issues and experience, and other work within scope for the working
group.

Revision, updates, and extensions to work from existing WGs will be done in
those WGs.

Where other new work may be needed, IOTOPS will help identify candidate
venues within the IETF for their development.

IOTOPS is chartered with the following scope:

* Standard track/BCP specifications that cover:

     - Manufacturer Usage Description (MUD) solutions
     - Configuration backup and recovery solutions
     - Software/firmware upgrade solutions, focusing on discovery and
     distribution

* Informational/BCP documents are restricted to:

    - Documenting requirements and terminology.
    - 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

    - Taking input and discussing issues related to IoT operational security.
    - Publishing operational practices and guidance.

Milestones:

  Jun 2025 - Submit "Comparison of CoAP Security Protocols" to the IESG

  Sep 2025 - Submit "Authorized Update to MUD URLs" to the IESG

  Nov 2025 - Submit "A summary of security-enabling technologies for IoT
  devices" to the IESG

  Dec 2025 - Submit "Terminology for Constrained-Node Networks" to the IESG



_______________________________________________
new-work mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]