IETF/IEEE 802 Coordination Meeting, 2024-10-23

1. Welcome, roll call, agenda bashing

Present:

Cindy Morgan
Deb Cooley
Donald Eastlake
Dorothy Stanley
Éric Vyncke
Glenn Parsons
John Scudder
Juan Carlos Zuniga
Orie Steele
Paul Wouters
Peter Yee
Russ Housley
Suresh Krishnan

Regrets:

Mirja Kühlewind
Tommy Pauly
Warren Kumari

2. Action item updates

Overcome By Events (OBE):

• 2024-02-16: Warren Kumari to reach out to the RAC about new Ethertypes for Safer Limited Domains.

New:

• 2024-10-23: Dorothy Stanley to find a representative from 802.15 to participate on the ieee-ietf-coord mailing list and coordination meetings.

3. IETF New Work summary

https://datatracker.ietf.org/wg/bofs/

ALLDISPATCH - IETF-Wide "Dispatch" Session (General Area)

ALLDISPATCH is a continuation of an experiment at IETF 119 and IETF 120 at combining the various Area Dispatch sessions into one meeting to discuss where to take new work. The IESG is expected to report back on this experiment after IETF 121.

DEEPSPACE - Deepspace (Internet Area)

Deep space communications involve long delays (e.g., Earth to Mars is 4-20 minutes) and intermittent communications, because of orbital dynamics. The combination of long delays and intermittent communications makes the round-trip time very large and very variable. Space agencies and private sector are planning to deploy IP networks on celestial bodies, such as Moon or Mars, ground, orbits and vicinity. By having the deep space links also IP, it makes a complete end to end IP network. However, given the delays and disruptions, the upper layers such as transport and application protocols have to be profiled to support this environment. While deep space is defined by ITU as 2M km away from Earth, therefore excluding Moon, this work does include Moon deployment.

There were discussions at IETF 120 about whether to incorporate this work into the Delay/Disruption Tolerant Networking (DTN) Working Group, but they decided that it would be better to have a separate group for this.

DIEM - Digital Emblems (Internet Area)

The DIEM BoF at IETF 121 will be a venue for discussing the chartering of perspective work on the topic of digital emblems and what useful scopes can be taken on by existing WGs or will require a new WG.

Éric Vyncke noted that this may require some coordination about Layer 2 down the line.

Juan Carlos Zuniga noted that there are similar discussions happening in the WiFi Alliance.

HPWAN - High Performance Wide Area Network (Web and Internet Transport Area)

The HPWAN BoF will be to bring together interested parties, including those operating R&E infrastructures, to discuss existing practices, what works, what does not work. The output of the BoF would be to document requirements for such infrastructures, and then identify potential avenues for IETF work to improve transport protocols to make large-scale data transfers more effective over wide-area, high RTT, potentially lossy paths, where the physical (inter-continental) infrastructure may be shared between multiple research and science communities.

RPP - RESTful Provisioning Protocol (Applications and Real-Time Area)

The Extensible Provisioning Protocol (EPP) was standardized (STD 69) over 20 years ago to address the needs of domain name management between domain name registries and registrars. EPP has served the domain name industry well, but despite its extensibility features it is not compatible with modern software development and infrastructure services that have been developed in the intervening years.

On the side of ccTLDs, there is a desire to create a new domain name provisioning protocol based on state-of-the-art RESTful principles and corresponding data representations using JSON instead of XML. This new protocol will specifically target current software development methodologies as well as scalable infrastructure as is commonly found in cloud and on-premises stateless, serverless, containerized and virtual application clustering technologies.

After careful consideration by the REGEXT working group, there is a rough consensus that this new approach would not fulfill all the requirements described in RFC5730 for extensions of the EPP protocol and that a new group would better fulfill the purpose of this work. The new work shall however consider the best possible compatibility with EPP and define a clear path for efficiently operating EPP alongside the new RESTful protocol and migration to the new protocol.

4. 802 New Work summary

https://ieee802.org/PARs.shtml

P802.1CB - Standard - Frame Replication and Elimination for Reliability - Revision to IEEE Standard 802.1CB-2017

This is a Revision to IEEE Standard 802.1CB-2017 that will roll in all of the amendments over the last ten years. This standard specifies procedures, managed objects, and protocols for bridges and end systems that provide identification and replication of packets for redundant transmission, identification of duplicate packets, and elimination of duplicate packets. It is not concerned with the creation of the multiple paths over which the duplicates are transmitted.

This revision project is needed to incorporate approved amendments and corrigenda, to incorporate technical and editorial corrections to existing functionality, and to maintain consistency in the consolidated text.

P802.1CBec - Amendment - Guidance for Sequence Recovery Function Parameter Configuration

This is an Amendment to IEEE Standard 802.1CB-2017. This amendment adds an informative annex describing recommended values for the existing sequence recovery function parameters and provides guidance regarding frame buffering in relay and end systems to assist in the usage of Frame Replication and Elimination for Reliability. This amendment also includes technical and editorial corrections in the description of existing IEEE Std 802.1CB functionality.

The sequence recovery function specified in the base standard eliminates duplicate frames and forwards non-duplicate frames. Inappropriate setting of parameter values and buffer dimensioning could lead to duplicates being passed and unintentional frame elimination. This informative annex provides guidance to avoid this unwanted behavior.

P802.11bq - Amendment - Enhancements for Integrated mmWave (IMMW) WLAN

This is an Amendment to IEEE Standard 802.11-2020. This amendment defines standardized modifications to both the IEEE Std 802.11 physical layer (PHY) and the IEEE Std 802.11 Medium Access Control (MAC) that allows Wireless Local Area Network (WLAN) non-standalone operation in unlicensed bands between 42 GHz and 71 GHz using single-user (SU) OFDM based transmissions. The amendment requires that an 802.11 device supporting this amendment also supports at least one of the 2.4 GHz to 7.25 GHz (sub-7 GHz) unlicensed bands. The amendment expands the multi-link operation defined in the sub-7 GHz band specifications to support non-standalone operation in the unlicensed bands between 42 GHz and 71 GHz.

This amendment on PHY and MAC operation in unlicensed bands between 42 GHz and 71 GHz leverages or reuses existing PHY and MAC specifications defined for the operation in sub-7 GHz bands, e.g. SU transmission PPDU format and MAC frames, and defines bandwidth modes operating in non-overlapping channels.

This amendment provides coexistence mechanisms with legacy IEEE 802.11 devices operating in the unlicensed bands between 42 GHz and 71 GHz.

Use of WLANs based on IEEE 802.11 technology continues to grow and diversify over many market segments including residential, enterprise, industrial. More stringent requirements are emerging to meet the demands of new applications (e.g. augmented and virtual reality, proximity ranging and sensing) both in terms of throughput, latency bounds and accuracy. The very large bandwidth available in the unlicensed bands between 42 GHz and 71 GHz, combined with the widely used 2.4, 5 and 6 GHz bands, is a great opportunity to help meet these requirements even in the densest environments. Enabling non-standalone operation in the unlicensed bands between 42 GHz and 71 GHz in a cost-effective manner is required so that as many devices can benefit from it.

P802.16 - Standard for Air Interface for Broadband Wireless Access Systems - Revision to IEEE Standard 802.16-2017

This is a Revision to IEEE Standard 802.16-2017. This standard specifies the air interface, including the medium access control layer (MAC) and physical layer (PHY), of combined fixed and mobile point-to-multipoint broadband wireless access (BWA) systems providing multiple services. The MAC is structured to support the WirelessMAN-SC, WirelessMANOFDM, and WirelessMAN-OFDMA PHY specifications, each suited to a particular operational environment.

Revision of the standard is required to incorporate one amendment (P802.16t-2024).

5. Review current coordination items

Potential Areas for IETF/IEEE802 Coordination, v45

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

John Scudder noted that during the IETF Last Call for draft-ietf-detnet-raw-technologies, someone asked whether a formal liaison had been sent to 802 about this work. John said that he did not believe this was necessary because the work was being tracked as one of the coordination items in the IETF-IEEE Coordination Group, but if anyone thinks that a formal liaison is necessary to please let him know.

Russ Housley noted that the only reason a formal liaison might be needed is the there has not been a representative of 802.15 at those coordination meetings since the passing of Bob Heile; Dorothy Stanley took an action item to find someone from 802.15 to participate.

Éric Vyncke suggested that https://datatracker.ietf.org/doc/draft-ietf-6lo-owc/ be added to the list of relevant documents.

Dorothy Stanley suggested that 802.11bb Light Communications be added to the list of relevant documents.

Item 27. Development of YANG models in the IEEE 802

Éric Vyncke noted that Mahesh Jethanandani should be added as one of the owners for this item, as he is now the Area Director responsible for YANG.

Item 29. Opportunistic Wireless Encryption (OWE)

Éric Vyncke reported that draft-wkumari-rfc8110-to-ieee is currently in AUTH48 and will be published as RFC 9672 shortly. This coordination item will be closed.

Item 33. Capability Discovery

John Scudder reported that a recharter of LSVR is still planned, but will not happen until early 2025 because the group wants to finish their currently-chartered work on the base specification first.

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

Éric Vyncke reported that draft-ietf-madinas-mac-address-randomization is currently in the RFC Editor Queue, and that draft-ietf-madinas-use-cases just entered AD Evaluation.

Juan Carlos Zuniga noted that there are some followup discussions happening in the RADIUS EXTensions (RADEXT) WG around draft-ietf-radext-deprecating-radius, considering changes for better identifier privacy.

6. Future meeting plans

There were no pressing topics that would require meeting during IETF 121. The next meeting will be a teleconference sometime around February 2025. Additionally, the group will meet in person during the weekend between the IETF and IEEE 802 meetings in Madrid in July 2025.

7. Adjourn