Minutes interim-2026-ietfieee-02: Wed 18:00
minutes-interim-2026-ietfieee-02-202606171800-00
| Meeting Minutes | IETF-IEEE (ietfieee) IAB ASG | |
|---|---|---|
| Date and time | 2026-06-17 18:00 | |
| Title | Minutes interim-2026-ietfieee-02: Wed 18:00 | |
| State | Active | |
| Other versions | markdown | |
| Last updated | 2026-06-17 |
IETF/IEEE 802 Coordination Meeting, 2026-06-17
1. Welcome, roll call, agenda bashing
Ann Krieger
Cindy Morgan
Deb Cooley
Donald Eastlake
Éric Vyncke
James Gilb
János Farkas
Mike StJohns
Peter Yee
Robert Stacey
Russ Housley
Suresh Krishnan
Tommy Jensen
Warren Kumari
2. Action item updates
NONE
3. IETF New Work summary
Agent Communication Protocols (agentproto) - ART Area
The AGENTPROTO BoF will look at chartering a Working Group to work on
defining protocol building blocks for enabling interoperability for AI
Agent applications across the Internet. An AI agent is an autonomous,
adaptive intelligent software system that uses AI models to complete a
specific task. AI Agents often interact with users via chat or voice,
performing tasks based on the flow of the conversation. To complete
tasks on behalf of a human user or another AI agent, they can
independently make decisions, execute actions, and interact with other
AI agents and tools.
Dynamic Multi-agent Secured Collaboration (dmsc) - ART Area
DMSC is a non-WG forming BoF that will explore whether there is interest
in the IETF to work on interoperable protocols and mechanisms for AI
Agent Gateway-mediated collaboration, including agent capability
exposure, request forwarding, coordination, synchronization, policy
control, observability, and secure communication.
Discovery of Agents, Workloads, and Named entities (dawn) - INT Area
The DAWN BoF will look at chartering a Working Group to develop
requirements, information models, and protocol solutions for entity
discovery.
Robert Stacey noted that this might be relevant to some of the work
coming up in 802.11.
Continuous Updating and Ratcheting for Rekeying Encrypted Network Transport (current) - SEC Area
The CURRENT BoF will look at chartering a Working Group to define a
two-party protocol that uses Messaging Layer Security (MLS) as specified
in RFC 9420 for the key management.
Protocol for Transposed Transactions over HTTP (ptth) - WIT Area
The PTTH BoF will look at chartering a Working Group to define a
standardized mechanism for reversing the roles of HTTP clients and HTTP
servers in a secure and interoperable way. This enables a system that
would traditionally act as a server to initiate HTTP requests towards a
system that traditionally acts as a client.
4. 802 New Work summary
IEEE 802 PARs & ICAIDs under consideration
P802.1EH - Standard - Telemetry Tagging of Data Frames PAR and CSD
This standard specifies protocols, procedures, and managed objects to
support forward signaling of telemetry in dedicated tags added to data
frames. This standard supports Medium Access Control (MAC), Customer
Virtual Local Area Network (C-VLAN) and Service Virtual Local Area
Network (S-VLAN) bridges and end stations. Telemetry in conjunction with
IEEE Std 802.1AE MAC Security is also supported. This standard specifies
a service interface to enable higher layer protocols to initiate and
retrieve telemetry from the data link layer. This standard supports
managed objects and a YANG data model for initiating and recording
telemetry.
P802.1EJ - Standard - Backward Notification PAR and CSD
This standard specifies procedures, protocols, and managed objects for
backward notification to signal data center network conditions toward
the source end station. This standard supports Medium Access Control
(MAC), Customer Virtual Local Area Network (C-VLAN) and Service Virtual
Local Area Network (S-VLAN) bridges and end stations in data center
networks. The notification mechanism conveys information for congestion
management, path rebalancing, and failure recovery. This standard
specifies how notifications are triggered and constructed, and a service
interface for exposing the information to entities above the data link
layer. This standard supports managed objects and a YANG data model for
backward notification.
Éric Vyncke noted that this appears to be similar to the work in the
proposed Fast Network Notifications (fann) WG, but at Layer 2.
P802.1DGei - Amendment - Time Synchronization PAR and CSD
This amendment selects IEEE 802.1AS time synchronization options,
defaults, and parameter values, and provides configuration guidelines
and constraints for automotive in- vehicle bridged IEEE 802.3 Ethernet
networks.
P802.3dv - Amendment - 400 Gb/s/lane Signaling for for 400 Gb/s, 800 Gb/s, and 1.6 Tb/s Ethernet PAR and CSD
This project is to specify additions to, and appropriate modifications
of, IEEE Std 802.3 to add Physical Layer specifications and Management
Parameters for 400 Gb/s, 800 Gb/s and 1.6 Tb/s using 400 Gb/s/lane
signaling for electrical interconnects and single-mode fiber optical
interconnects with reaches up to 500 meters
P802.19.3a - Amendment - Recommended Practice Amendment: Enhanced sub-1GHz Coexistence PAR Modification CSD
This minor PAR modification amends the PAR scope to remove the date on
IEEE Std 802.11.
5. Review current coordination items
Potential Areas for IETF/IEEE802 Coordination, v50
Item 25. Layer 2/Layer 3 Interaction for Time-Sensitive Traffic
IETF DetNet:
recently published:
- RFC 9913 Reliable and Available Wireless (RAW) Technologies
- RFC 9912 Reliable and Available Wireless (RAW) Architecture
- RFC 9938 Deterministic Networking (DetNet) Controller Plane
Framework
ongoing work:
- Requirements for Scaling Deterministic Networks
- Dataplane Enhancement Taxonomy
-
data plane enhancement solution proposals:
- On-time Forwarding with Non-work Conserving Stateless Core Fair
Queuing - Deadline Based Deterministic Forwarding
- Timeslot Queueing and Forwarding Mechanism
- Deterministic Networking (DetNet) Data Plane - Tagged Cyclic
Queuing and Forwarding (TCQF) for bounded latency with low
jitter in large scale DetNets - Deterministic Networking (DetNet) Data Plane - guaranteed
Latency Based Forwarding (gLBF) for bounded latency with low
jitter and asynchronous forwarding in Deterministic
Networks - On-time Forwarding with Push-In First-Out (PIFO) queue
- On-time Forwarding with Non-work Conserving Stateless Core Fair
Queuing
- On-time Forwarding with Non-work Conserving Stateless Core Fair
-
recently adopted drafts:
IEEE 802.1 TSN:
recently published:
- IEEE 802.1ASed – Timing and Synchronization for Time-Sensitive
Applications - Amendment: Fault-Tolerant Timing with Time
Integrity - IEEE 802.1ASds – Timing and Synchronization for Time-Sensitive
Applications - Amendment: Support for the IEEE Std 802.3 Clause 4
Media Access Control (MAC) operating in half-duplex
recently approved (by both IEC and IEEE SASB):
at SA ballot:
at Task Group ballot:
- P802.1DD – Resource Allocation Protocol
- P802.1DU – Cut-Through Forwarding Bridges and Bridged Networks
- P802.1CBec – Guidance for Sequence Recovery Function Parameter
Configuration (https://1.ieee802.org/tsn/802-1cbec/)
with the Editor:
- P802.1EH – Telemetry Tagging of Data Frames
- P802.1EJ – Backward Notification
- P802.1DGei – Amendment: Time Synchronization
recent blog posts:
Item 27. Development of YANG models in the IEEE 802
There was no update on the call. Russ will follow up with Mahesh
Jethanandani and Scott Mansfield.
Item 33. Capability Discovery
Russ Housley noted that there has been no progress in over a year and
asked if this item should be closed. János Farkas said that it wouldb be
good to understand what the plans are in the LSVR WG before closing
this. Russ will send email to the authors for a status update.
Item 36. Post Quantum Cryptography (PQC)
Russ Housley will update the coordination list to add:
- the RFC numbers for recenly-published documents
- a pointer to the liaison statement from 802.11 to the TLS WG
regarding draft-ietf-tls-mlkem - a pointer to new relevant documents in the TLS and EMU WGs
Robert Stacey said that P802.11bt expects to go to initial WG ballot in
July.
Item 37. Jumbo Ethernet Frames
Éric Vyncke said that they were not able to garner interest on working
on this in the INT Area, so this item can be closed.
Item 38. L4S and Wi-Fi
There was no update on the call. Robert Stacey will follow up with Juan
Carlos Zuniga.
It was noted that the reference to RFC 9814 in the coordination document
is wrong; that should RFC 9930, RFC 9931, and RFC 9932.