RFC 9672

Transferring Opportunistic Wireless Encryption to the IEEE 802.11 Working Group

📅 published December 2024, from ietf

🎀 RFC 9672: Transferring Opportunistic Wireless Encryption to the IEEE 802.11 Working Group 🎀

Bestie, this one is a handover doc!! 💖 It's about moving the ongoing care of OWE (Opportunistic Wireless Encryption) from the IETF over to the IEEE 802.11 Working Group. Here is the title-block tea ☕:

  • Series: Internet Engineering Task Force (IETF)
  • Number: RFC 9672
  • Authors: W. Kumari (Google, LLC) and D. Harkins (Hewlett-Packard Enterprise)
  • Category: Informational 🦋
  • ISSN: 2070-1721
  • Date: December 2024
  • Updates: RFC 8110 ✨

So this doc updates RFC 8110, and it does not obsolete anything. 💅

Abstract ✨

Okay so, RFC 8110 describes OWE, a mode that lets unauthenticated clients connect to a network using encrypted traffic. 🔐 This doc transfers the ongoing maintenance and further development of that protocol to the IEEE 802.11 Working Group. 🌸

This document updates RFC 8110 by noting that future work on the protocol described therein will occur in the IEEE 802.11 Working Group. 🫶

Status of This Memo 🌈

Lowkey, this is not an Internet Standards Track spec. It's published for informational purposes only. 🧚

This is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community, and it got public review and was approved for publication by the Internet Engineering Steering Group (IESG). 💜 Not every IESG-approved doc is a candidate for any level of Internet Standard, so see Section 2 of RFC 7841 for that. 🙈

For the current status, any errata, and how to give feedback, check https://www.rfc-editor.org/info/rfc9672. ✨

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. 🎀

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication. Please review these carefully, because they describe your rights and restrictions for this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions, and they are provided without warranty as described in the Revised BSD License. 📜

Table of Contents 🦋

  • 1. Introduction
  • 2. Transfer of Maintenance
  • 3. Security Considerations
  • 4. IANA Considerations
  • 5. References
    • 5.1. Normative References
    • 5.2. Informative References
  • Acknowledgments
  • Authors' Addresses

1. Introduction 🌸

Okay bestie, so OWE [RFC8110] is a mode of opportunistic security [RFC7435] for IEEE Std 802.11 that encrypts the wireless medium without authentication. 🔐✨

Since it was published, [RFC8110] (also known as "[Wi-Fi_Enhanced_Open]") has been widely implemented and deployed. It's giving success story 👑💅

The IEEE 802.11 Working Group [IEEE_802.11] asked to maintain and develop OWE (see [IEEE_LS]) so the protocol stays in sync with the IEEE protocols. 🧚 This document is the concurrence that future work on OWE [RFC8110] will now happen in the IEEE 802.11 Working Group. 🫶

2. Transfer of Maintenance 🎀

So this doc is the concurrence that future work on OWE [RFC8110] will now occur in the IEEE 802.11 Working Group [IEEE_802.11], so the protocol stays in sync with the IEEE protocols. 💜

The OWE protocol [RFC8110] will be duplicated by the IEEE 802.11 Working Group [IEEE_802.11], so the document alone is enough to implement, maintain, and modify the protocol within the IEEE under its policies and procedures. 🌈 Main character handoff, periodt! 💅

3. Security Considerations 🔐

Bestie, this doc only notes that future work on the protocol described in [RFC8110] will now happen in the IEEE. ✨ That's it! So it does not introduce any new security considerations. 🙈💖

4. IANA Considerations 🧚

This document has no IANA actions. 🌸

5. References 📚

5.1. Normative References

5.2. Informative References

Acknowledgments 🫶

The authors would like to thank the IEEE 802.11 Working Group for their work, and for taking on the responsibility for future work on the protocol described in RFC 8110. 👑

They'd also like to thank Stephen Farrell, the AD who sponsored the original work, plus Clemens Schimpe, Dorothy Stanley, Paul Wouters, Eric Vyncke, Mike Montemurro, and Peter Yee. 💖

Apologies to anyone we forgot to acknowledge! RFC 8110 was written 7+ years ago, and they've had many conversations with many people since then... 🙈💀

Authors' Addresses 🦋

Warren Kumari Google, LLC Email: warren@kumari.net

Dan Harkins Hewlett-Packard Enterprise Email: daniel.harkins@hpe.com

📦 where this page comes from