Network Working Group

Internet Engineering Task Force (IETF)                         W. Kumari
Internet-Draft
Request for Comments: 9672                                   Google, LLC
Updates: 8110 (if approved)                                                 D. Harkins
Intended status:
Category: Informational                       Hewlett-Packard Enterprise
Expires: 8 February 2025                                   7 August
ISSN: 2070-1721                                             October 2024

   Transferring Opportunistic Wireless Encryption to the IEEE 802.11
                             Working Group
                    draft-wkumari-rfc8110-to-ieee-02

Abstract

   RFC8110

   RFC 8110 describes Opportunistic Wireless Encryption (OWE), a mode
   that allows unauthenticated clients to connect to a network using
   encrypted traffic.  This document transfers the ongoing maintenance
   and further development of the protocol to the IEEE 802.11 Working
   Group.

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

About

Status of This Document Memo

   This note document is to be removed before publishing as not an RFC.

   The latest revision of this draft can be found at
   https://wkumari.github.io/draft-wkumari-rfc8110-to-ieee/draft-
   wkumari-rfc8110-to-ieee.html.  Status information for this document
   may be found at https://datatracker.ietf.org/doc/draft-wkumari-
   rfc8110-to-ieee/.

   Source Internet Standards Track specification; it is
   published for this draft and an issue tracker can be found at
   https://github.com/wkumari/draft-wkumari-rfc8110-to-ieee.

Status of This Memo informational purposes.

   This Internet-Draft document is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents a product of the Internet Engineering Task Force
   (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list  It represents the consensus of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents valid
   approved by the IESG are candidates for a maximum any level of six months Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 8 February 2025.
   https://www.rfc-editor.org/info/rfc9672.

Copyright Notice

   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)
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to 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 are provided without warranty as described
   in the Revised BSD License.

Table of Contents

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

1.  Introduction

   [RFC8110] describes

   Opportunistic Wireless Encryption (OWE), (OWE) [RFC8110] is a mode of
   opportunistic security [RFC7435] for IEEE Std 802.11 that provides
   encryption of the wireless medium without authentication.

   Since publication, [RFC8110] (also known as "[Wi-Fi_Enhanced_Open]")
   has been widely implemented and deployed.

   [IEEE_802.11] has requested [IEEE_LS] that in order to allow for
   ongoing maintenance and further development of the protocol, and to
   ensure that the protocol remains in sync with the IEEE protocols,
   future work on the protocol described in RFC8110 will now occur in
   [IEEE_802.11].  This document is a concurrence.

2.  Transfer of Maintenance

   At the request of [IEEE_802.11], in order to allow for ongoing
   maintenance and further development of the protocol, and to ensure
   that the protocol remains in sync with the IEEE protocols, this
   document specifies that future work on the protocol described in
   RFC8110 will now occur in [IEEE_802.11].

   The protocol defined in RFC8110 will be duplicated in [IEEE_802.11]
   such that that document alone will be enough to implement it and any
   further maintenance or modification of the protocol will be performed
   in IEEE under its policies and procedures.

3.  Security Considerations

   This document simply notes that future work on the protocol described
   in RFC8110 [RFC8110] will now occur in the IEEE.  As such, it does not
   introduce any new security considerations.

4.  IANA Considerations

   This document has no IANA actions.

5.  References

5.1.  Normative References

   [RFC8110]  Harkins, D., Ed. and W. Kumari, Ed., "Opportunistic
              Wireless Encryption", RFC 8110, DOI 10.17487/RFC8110,
              March 2017, <https://www.rfc-editor.org/rfc/rfc8110>. <https://www.rfc-editor.org/info/rfc8110>.

5.2.  Informative References

   [IEEE_802.11]
              "IEEE
              IEEE, IEEE 802.11 Working Group", n.d., Group,
              <https://www.ieee802.org/11/>.

   [IEEE_LS]  "Liaison Statement from IEEE 802.11 to the IETF - statement: OWE (RFC8110) now in 802.11", n.d., IETF
              Liaison Statement, May 2024,
              <https://datatracker.ietf.org/liaison/1929/>.

   [RFC7435]  Dukhovni, V., "Opportunistic Security: Some Protection
              Most of the Time", RFC 7435, DOI 10.17487/RFC7435,
              December 2014, <https://www.rfc-editor.org/rfc/rfc7435>. <https://www.rfc-editor.org/info/rfc7435>.

   [Wi-Fi_Enhanced_Open]
              Harkins, D., "Wi-Fi CERTIFIED Enhanced Open™: Open: Transparent Wi-Fi®
              Wi-Fi protections without complexity", n.d., <https://www.wi-
              fi.org/beacon/dan-harkins/wi-fi-certified-enhanced-open-
              transparent-wi-fi-protections-without-complexity>. Wi-Fi Alliance, The
              Beacon Blog, <https://www.wi-fi.org/beacon/dan-harkins/wi-
              fi-certified-enhanced-open-transparent-wi-fi-protections-
              without-complexity>.

Acknowledgments

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

   In addition, we would like to thank Stephen Farrell, who the AD that
   sponsored the original work, as well as Clemens Schimpe, Dorothy
   Stanley, Paul Wouters, Eric Vyncke, Mike Montemurro, and Peter Yee.

   Apologies to anyone we forgot to acknowledge; RFC8110 RFC 8110 was written 7+
   years ago and we have had many conversations with many people since
   then...

Change Log

   *  From -00 to -01:

      -  Fixed a nit ("This documents updates" -> "This document
         updates")

      -  We have the liaison from the IEEE 802.11 WG; update to point at
         the liaison statement.

      -  For some reason, pushing the -01 version to GitHub didn't
         trigger the build.  Trying to post manually.

Authors' Addresses

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

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