Skip to main content

Minutes interim-2022-ietfieee-02: Tue 07:00

Meeting Minutes IETF-IEEE (ietfieee) IAB ASG
Date and time 2022-06-21 14:00
Title Minutes interim-2022-ietfieee-02: Tue 07:00
State Active
Other versions plain text
Last updated 2022-06-21

IETF/IEEE 802 Coordination Meeting, 2022-06-21

1. Welcome, roll call, agenda bashing


Andrew Alston
Amelia Andersdotter
Paul Congdon
Roman Danyliw
Donald Eastlake
Lars Eggert
János Farkas
Russ Housley
Erik Kline
Warren Kumari
Cindy Morgan
Michael Richardson
John Scudder
Dorothy Stanley
Eric Vyncke
Rob Wilton
Ziyang Xing
Juan Carlos Zuniga


Francesca Palombini
Zahed Sarker
Russ White

2. Action item updates


    - Rob Wilton to send a liaison from the NETCONF WG to 802.1 about
      security coordination for draft-ietf-netconf-keystore.

  In Progress:

    - None

3. IETF New Work summary

  • Media Over QUIC (MOQ)
    Applications and Real-Time Area

    Media over QUIC (MOQ) will work on a solution for a low-latency
    media delivery protocol for ingest and distribution. This work may
    address use cases including live streaming, gaming, and media
    conferencing and allows efficient scaling. The solution supports
    both web browsers and simple devices that don’t contain embedded

    Russ Housley noted that there are 5 documents under consideration.

  • Supply Chain Integrity, Transparency, and Trust (SCITT)
    Security Area

    The scope of this BOF is focused on solutions that fulfill a set of
    fundamental guiding technical objectives: IoT-applicable, crypto-
    agile, and identity-agile. The intent is to create a globally
    uniform/interoperable (counter-)signing format for "Statements made
    about supply chain elements", to enable offline/air-gap validation,
    and to reduce emerging issues with respect to claim-lifetime &

  • Multicast Source Routing over IPv6 (MSR6)
    Routing Area

    MSR6 focuses on source routing multicast based on native IPv6 (IPv6
    and IPv6 extension headers), including Best Effort and Traffic
    Engineering solutions, to decouple multicast forwarding from per-
    flow state at intermediate nodes.

    Russ Housley noted that this is probably not currently of interest
    to 802, but as the work progresses, there may be some multicast
    technology that becomes relevant at Layer 2.

  • Secure Asset Transfer Protocol (SATP)
    Security Area

    The goal of Secure Asset Transfer (SAT) is to develop a standard
    protocol which operates between two gateways for the purpose of
    transferring digital assets between networks or systems. Each
    gateway represents one network or system, and the SAT protocol
    performs a unidirectional transfer of a digital asset from the
    origin network to a destination network.

  • Transfer dIGital cREdentialS Securely (TIGRESS)
    Applications and Real-Time Area
    More info:

    This is a follow-up to the Secure Credential Transfer BOF at IETF
    113. There are many situations in which it is desirable to transfer
    a copy of a digital credential to another person. Today, no such
    standardized method exists in a cross-platform, credential type-
    agnostic capacity. TIGRESS will define and standardize a protocol
    that will facilitate such credential transfers from one person's
    device to another person's device. The protocol will leverage a
    "relay server" to transfer data from sender to recipient. The scope
    of the transfer is limited to a single origin device and a single
    destination device.

  • Stub Network Auto Configuration for IPv6 (SNAC)
    Internet Area

    SNAC will work on the problem of connecting stub networks to
    existing infrastructure in the absence of an expert operator. In a
    managed network, constrained networks can be provisioned into the
    routing infrastructure. However, the vast majority of IPv6 links on
    the Internet are not managed, and so this approach leaves out most
    networks, specifically home and small office networks. This problem
    is described in detail in draft-lemon-stub-networks-ps, and a
    solution based on IPv6 routing and unicast DNS-SD is described in

    Russ Housley noted that this is work is likely of interest to 802.

    Éric Vyncke added that the goal is more to develop new guidelines,
    rather than create new protocols. It is not clear at this stage
    whether the work will remain in the Internet Area or move over to
    the Operations and Management Area.

  • JSON Web Proofs (JWP)
    Security Area

    This BOF proposes to re-form the JSON Object Signing and Encryption
    (JOSE) working group to develop a set of companion specifications to
    the existing JOSE specs that are designed to support the privacy-
    enhancing primitives of selective disclosure and unlinkability.
    These specifications will utilize defined cryptographic schemes,
    standardizing their use in a JSON-based serializable container
    format; creation or standardization of new cryptographic algorithms
    would not be in scope.

4. 802 New Work summary

  • 60802 - Standard - Time-Sensitive Networking Profile for Industrial
    Automation, PAR, CSD, and PAR Extension

    This document defines time-sensitive networking profiles for
    industrial automation. The profiles select features, options,
    configurations, defaults, protocols, and procedures of bridges, end
    stations, and LANs to build industrial automation networks. This
    document also specifies YANG modules defining read-only information
    available online and offline as a digital data sheet.

  • 802.1Qdv - Amendment: Enhancements to Cyclic Queuing and Forwarding,
    PAR and CSD

    This amendment specifies procedures, protocols and managed objects
    to enhance Cyclic Queuing and Forwarding, comprising: a transmission
    selection procedure that organizes frames in a traffic class output
    queue into logical bins that are output in strict rotation at a
    constant frequency; a procedure for storing received frames into
    bins based on the time of reception of the frame; a procedure for
    storing received frames into bins based on per-flow octet counters;
    a protocol for determining the phase relationship between a
    transmitter's and a receiver's bin boundaries in time; managed
    objects, Management Information Base (MIB), and YANG modules for
    controlling these procedures; and an informative annex to provide
    guidance for applying these procedures. This amendment also
    addresses errors and omissions in the description of existing IEEE
    Std 802.1Q functionality.

  • 802.1Qdw - Amendment: Source Flow Control, PAR and CSD

    This amendment specifies procedures, managed objects, and a YANG
    data model for the signaling and remote invocation of flow control
    at the source of transmission in a data center network. This
    amendment specifies enhancements to the Data Center Bridging
    Capability (DCBX) protocol to advertise the new capability. This
    amendment specifies the optional use of existing stream filters to
    allow bridges at the edge of the network to intercept and convert
    signaling messages to existing Priority- based Flow Control (PFC)
    frames. This amendment also addresses errors of existing IEEE Std
    802.1Q functionality.

  • 802.1CQ - Standard - Multicast and Local Address Assignment, PAR

    This extends the 802.1CQ PAR until 2022-12-31.

  • 802.1DC - Standard - Quality of Service Provision by Network
    Systems, PAR Extension

    This extends the 802.1DC PAR until 2022-12-31.

  • 802.1Qcz - Amendment: Congestion Isolation, PAR Extension

    This amendment specifies protocols, procedures and managed objects
    that support the isolation of congested data flows within data
    center environments. This is achieved by enabling systems to
    individually identify flows creating congestion, adjust transmission
    selection for packets of those flows, and signal to neighbors. This
    mechanism reduces head-of-line blocking for uncongested flows
    sharing a traffic class in lossless networks. Congestion Isolation
    is intended to be used with higher layer protocols that utilize end-
    to-end congestion control in order to reduce packet loss and
    latency. This amendment also addresses errors and omissions in the
    description of existing functionality.

  • 802.1Qdd - Amendment: Resource Allocation Protocol, PAR Extension

    This amendment specifies protocols, procedures, and managed objects
    for a Resource Allocation Protocol (RAP) that uses the Link-local
    Registration Protocol (LRP) and supports and provides backwards
    compatibility with the stream reservation and quality of service
    capabilities, controls and protocols specified in IEEE Std 802.1Q.
    RAP provides support for accurate latency calculation and reporting,
    can use redundant paths established by other protocols, and is not
    limited to bridged networks.

  • 802.3 Industry Connections - New Ethernet Applications, Endorsement
    Letter & ICAID

    Dorothy Stanley reported that this is an ongoing project under the
    ICAID process. It is a pre-standards development forum for a New
    Ethernet Applications project.

  • 802.15.4 - Standard for Low Rate Wireless Networks, Revision PAR

    This standard defines the physical layer (PHY) and medium access
    control (MAC) sublayer specifications for low-data-rate wireless
    connectivity with fixed, portable, and moving devices with no
    battery or very limited battery consumption requirements. In
    addition, the standard provides modes that allow for precision
    ranging. PHYs are defined for devices operating in a variety of
    geographic regions.

5. Review current coordination items

  • Item 5. Enabling use of Local Addresses for virtualization and IoT

    Donald Eastlake reported that work on an update to RFC 7042 has

  • Item 25. Layer 2/Layer 3 Interaction for Time-Sensitive Traffic

    János Farkas reported that the DETNET charter is being updated to
    include flow identification and packet treatment.

  • Item 27. Development of YANG models in the IEEE 802

    Rob Wilton reported that there is still a desire for a YANG model
    for 802.1AX, but there is not currently a PAR to work on that.

    Michael Richardson reported that the CORE Working Group has started
    work on YANG-SID and MegaAllocations.

    János Farkas said that P802f is ready to be shared with NETMOD.

    Rob Wilton has an action to send a liaison from the NETCONF WG to
    802.1 about security coordination for draft-ietf-netconf-keystore.

  • Item 33. Capability Discovery

    Alvaro Retana reported via email that the drafts have not
    progressed. The WG has started the discussion of an updated charter
    to explicitly include work on L3DL.

    Paul Congdon noted that the LLDPv2 standard (802.1ABdh) has been

  • Item 34. Reliable and Available Wireless (RAW)

    Dorothy Stanley reported that they asked 802.11 to review the RAW
    documents, but did not get a response. She will ask again.

    Russ Housley suggested that this coordination item can be closed if
    there is no further interaction on it by the next meeting. John
    Scudder will follow up with the RAW chairs.

  • Item 35. MAC Address Device Identification for Network and
    Application Services (MADINAS)

    Juan Carlos Zuniga reported that MADINAS recently adopted draft-
    henry-madinas-framework, and they have had positive interactions
    with WBA that are being captured in the MADINAS documents.

  • Possible New Items

    Dorothy Stanley note that the SNAC BOF references 802.15, so there
    may be coordination needed if SNAC is chartered as a Working Group.

6. Future meeting plans

  The next IEEE 802 and IETF meetings will both be hybrid meetings, so
  the coordination group will not meet in person.

7. Adjourn