IoT-DIR Chairs: Samita Chakrabarti, Ines Robles, Ari Keranen
Date: 8 March
Time: 3pm UTC
Schedule Duration: 1:30 minutes
Material:
https://datatracker.ietf.org/meeting/interim-2024-iotdir-01/session/iotdir
[TOC]
This meeting is aligned with the IETF Note Well:
https://www.ietf.org/about/note-well/
Notice that we aim to record the meeting.
Recording this here since the chat didn't work...
AK: Sometimes we get answer to review requests from directorate members
that they "are not experts on the topic". You don't need to be expert,
or often even particularly well informed, of the topic of the draft, but
provide general review with focus on IoT-related topics. Chairs usually
try to assign reviews based on who we think would know the area best,
but sometimes such persons are already authors / active participants or
we don't find a good match and will do best-effort assignments.
6TiSCH is closed
6lo will meet in the next IETF
4 WG documents:
Submitted to IESG for publication (received reviews from genart
and tsvart):
Other WG documents:
Path-Aware Semantic Addressing (PASA) for Low power and
Lossy Networks
(draft-ietf-6lo-path-aware-semantic-addressing-04)
Transmission of SCHC-compressed packets over IEEE 802.15.4
networks (draft-ietf-6lo-schc-15dot4-05)
IPv6 Neighbor Discovery Prefix Registration
(draft-ietf-6lo-prefix-registration-02)
2 individual documents that will be presented:
ANIMA will meet in Brisbane for a 1 hour slot, Monday 17:30 - 18:80
ANIMA has continued to work through weekly side meetings and githut
issue tracking (github.com/anima-wg) on most of its active WG drafts and
closed significant number of issues. Due to logical and author
dependencies, these have ended up becoming a cluster.
Adopted since IETF118 (not yet posted)
Passed WGLC sent to AD (some delay due to AD Change at IETF119 (from Rob
Wilton)
TBD waiting for discuss with authors @ IETF119:
Limited local attendance in Brisbane, hence chairs will ask WG if a
formal interim e.g.: end of April wouldmake sense (if remote attendance
due to TZ is also not going to work well.
Example core open issue is whether to keep YANG as data modelling for
the voucher (RFC8366) because there is still no tooling to automatically
convert YANG into the required JSON or CBOR code. BUt going away from
YANG would require to rewrite entire rfc836bis to be spec'ed into CDDL
(which supports JSON and CBOR).
Will not meet in Brisbane (except on the hallways)
ASDF is in the process of shipping draft-ietf-asdf-sdf-18 to the
IESG.
Rechartering upcoming, with an interim focused on that scheduled
for April.
CBOR will meet at IETF 119, in a 90-minute session
First 30 minutes: Tutorials on how to use CBOR in I-Ds, drop by!
(And if you're into YANG, the next 30 minutes may also be of
interest)
Interim meetings after IETF 119
Documents:
In RFC editor queue (EDIT): draft-ietf-cbor-time-tag-12
In IESG: those ↓ by IETF119, likely
nth WGLC active until IETF119 for
EDN: draft-ietf-cbor-edn-literals-08,
CCDL: draft-ietf-cbor-update-8610-grammar-04 and
CDDL: draft-ietf-cbor-cddl-more-control-03
(note: UNIX style documents, do one thing in a small tool)
The cluster formerly known as CDDL 2.0 (includes docs in WGLC)
CBOR core: Packed cluster:
CBOR core: Serialization
How to use CBOR (cf. tutorial part)
EDN extension point usage: draft-bormann-cbor-e-ref-00
Procedural (EDN/CDDL in drafts):
draft-bormann-cbor-draft-numbers-03
CDDL ancillary
CBOR applications
inside WG
Outside CBOR WG
2 documents approved for publication and in the RFC Editor's Queue
1 document in IESG processing (Proposed Standard)
Among the WG documents:
Selected ongoing activities
Major work on the CORECONF documents
"Constrained Resource identifiers" (HREF)
New WG documents
Discussion on using mDNS for node discovery
Since IETF 118
CoRE will meet at IETF 119, in a 2-hour session
Interim meetings after IETF 119
(no comments)
Continuing work of RAW that concluded.
(no comments)
(no comments)
Concluded 2024-01-23.
CB: There is one more 7228bis (terminology for constrined nodes) that
has new draft, looking to put it to IoTops.
Currently not in data tracker due to DT hick-up.
EL: ADs can override publication, so if stuck, talk to your AD.
CB: yes, ADs very busy at the moment. Queued up for review according to
DT.
EL: worth rising the issue. Want this done as early as possible.
EL: Currently an independent submission for ARM's architecture as a RATS
extension. Not too late for reviews. Contact ISE to review, would love
reviews.
draft-tschofenig-rats-psa-token
Concluded 2023-10-20 --> DETNET
Carles Gomez: Biweekly interims planned. Architecture draft has been
discussed ("SCHC session", "SCHC header" being discussed). Also:
protocol number, SCHC for ICMP
EL: System for Cross Identity Management, draft-ietf-scim-devices,
extends cloud based provisioning from users to devices. Heading for
WGLC.
(with an audible "c")
(no comments)
RH: DT has retired. DW single-chairing. Almost everything in
WGLC-or-later.
All of the SUIT WG documents are nearing completion.
draft-ietf-suit-manifest-25: with the IESG
draft-ietf-suit-mud-08: with the IESG
draft-ietf-suit-mti-05: passed WGLC; working to shepherd writeup
draft-ietf-suit-update-management-06: passed WGLC; waiting on companion
document
draft-ietf-suit-trust-domains-06: passed WGLC; waiting on companion
document
draft-ietf-suit-firmware-encryption-19: In WGLC now
draft-ietf-suit-report-08: almost ready for WGLC
(no comments, but notes were provided below:)
Will not meet at IETF 119
The protocol spec is in AD review read for IESG publication.
Informational draft
https://datatracker.ietf.org/doc/draft-ietf-teep-usecase-for-cc-in-network/
should have a WGLC to see if it is ready as well.
(no comments)
Not physically meeting at IETF 119. Will meet at IETF 121, possibly at
120.
Interim meeting on IoT security in Paris on May 21/22, co-located
with the hackathon on lightweight IoT security hosted by Inria.
Registration is open!
Documents:
"IoT Edge Challenges and Functions" draft in RFC editor queue (state
RFC-EDITOR).
Three RG drafts with recent minor updates:
AK: BoFs? side meetings?
TE: Thursday side meeting on "Enterprise Network" -- all active
enterprises (?) looking for common design criteria for operations (?).
From low end to active devices in enteprises and campuses. Comparing
their operations challenges to IoT usage. Link?
CA: not SDO but research thing on next gen networks and security.
Bringing IETF experience to avoid re-inventing things. So far not much
online, best we have right now is COST website