<?xml version='1.0'encoding='utf-8'?>encoding='UTF-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.18 (Ruby 3.3.3) --><rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-wkumari-rfc8110-to-ieee-02" number="9672" category="info" consensus="true" submissionType="IETF" obsoletes="" updates="8110" tocInclude="true" sortRefs="true" symRefs="true"version="3"> <!-- xml2rfc v2v3 conversion 3.22.0 -->version="3" xml:lang="en" > <front> <titleabbrev="RFC8110-to-IEEE">Transferringabbrev="RFC 8110 to IEEE">Transferring Opportunistic Wireless Encryption to the IEEE 802.11 Working Group</title> <seriesInfoname="Internet-Draft" value="draft-wkumari-rfc8110-to-ieee-02"/>name="RFC" value="9672"/> <author initials="W." surname="Kumari" fullname="Warren Kumari"> <organization>Google, LLC</organization> <address> <email>warren@kumari.net</email> </address> </author> <author initials="D." surname="Harkins" fullname="Dan Harkins"> <organization>Hewlett-Packard Enterprise</organization> <address> <email>daniel.harkins@hpe.com</email> </address> </author> <date year="2024"month="August" day="07"/>month="October"/> <keyword>IEEE</keyword> <keyword>OWE</keyword> <keyword>Opportunistic Wireless Encryption</keyword> <keyword>RFC8110</keyword> <abstract> <?line 56?><t>RFC8110<t>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.</t> <t>This document updatesRFC8110RFC 8110 by noting that future work on the protocol describedin RFC8110therein will occur in the IEEE 802.11 Working Group.</t> </abstract><note removeInRFC="true"> <name>About This Document</name> <t> The latest revision of this draft can be found at <eref target="https://wkumari.github.io/draft-wkumari-rfc8110-to-ieee/draft-wkumari-rfc8110-to-ieee.html"/>. Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-wkumari-rfc8110-to-ieee/"/>. </t> <t>Source for this draft and an issue tracker can be found at <eref target="https://github.com/wkumari/draft-wkumari-rfc8110-to-ieee"/>.</t> </note></front> <middle> <?line 64?> <section anchor="introduction"> <name>Introduction</name><t><xref target="RFC8110"/> describes Opportunistic<t>Opportunistic Wireless Encryption(OWE),(OWE) <xref target="RFC8110"/> is a mode of opportunistic security <xref target="RFC7435"/> for IEEE Std 802.11 that provides encryption of the wireless medium without authentication.</t> <t>Since publication, <xref target="RFC8110"/> (also known as "<xref target="Wi-Fi_Enhanced_Open"/>") has been widely implemented and deployed.</t> <!-- [rfced] Section 1: We are having trouble parsing this text. Please consider whether the suggested text correctly conveys the intended meaning. Original: [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. Perhaps: The IEEE 802.11 Working Group [IEEE_802.11] has requested the ability to maintain and develop OWE (see [IEEE_LS]). This document represents concurrence that future work on OWE [RFC8110] will now occur in the IEEE 802.11 Working Group to ensure that the protocol remains in sync with the IEEE protocols. --> <t><xref target="IEEE_802.11"/> has requested <xref target="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 <xref target="IEEE_802.11"/>. This document is a concurrence.</t> </section> <section anchor="transfer-of-maintenance"> <name>Transfer of Maintenance</name> <!-- [rfced] Section 2: If the update above is accepted, may we make a similar change here? Original: 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. Perhaps: This document represents concurrence that future work on OWE [RFC8110] will now occur in the IEEE 802.11 Working Group [IEEE_802.11] to ensure that the protocol remains in sync with the IEEE protocols. The OWE protocol [RFC8110] will be duplicated by the IEEE 802.11 Working Group [IEEE_802.11] such that the document alone will be enough to implement, maintain, and modify the protocol within the IEEE under its policies and procedures. --> <t>At the request of <xref target="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 <xref target="IEEE_802.11"/>.</t> <t>The protocol defined in RFC8110 will be duplicated in <xref target="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.</t> </section> <section anchor="security-considerations"> <name>Security Considerations</name> <t>This document simply notes that future work on the protocol described inRFC8110<xref target="RFC8110"/> will now occur in the IEEE. As such, it does not introduce any new security considerations.</t> </section> <section anchor="iana-considerations"> <name>IANA Considerations</name> <t>This document has no IANA actions.</t> </section> </middle> <back> <references anchor="sec-combined-references"> <name>References</name> <references anchor="sec-normative-references"> <name>Normative References</name><reference anchor="RFC8110"> <front> <title>Opportunistic Wireless Encryption</title> <author fullname="D. Harkins" initials="D." role="editor" surname="Harkins"/> <author fullname="W. Kumari" initials="W." role="editor" surname="Kumari"/> <date month="March" year="2017"/> <abstract> <t>This memo specifies an extension to IEEE Std 802.11 to provide for opportunistic (unauthenticated) encryption to the wireless media.</t> </abstract> </front> <seriesInfo name="RFC" value="8110"/> <seriesInfo name="DOI" value="10.17487/RFC8110"/> </reference><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8110.xml"/> </references> <references anchor="sec-informative-references"> <name>Informative References</name><reference anchor="RFC7435"> <front> <title>Opportunistic Security: Some Protection Most of the Time</title> <author fullname="V. Dukhovni" initials="V." surname="Dukhovni"/> <date month="December" year="2014"/> <abstract> <t>This document defines the concept "Opportunistic Security" in the context of communications protocols. Protocol designs based on Opportunistic Security use encryption even when authentication is not available, and use authentication when possible, thereby removing barriers to the widespread use of encryption on the Internet.</t> </abstract> </front> <seriesInfo name="RFC" value="7435"/> <seriesInfo name="DOI" value="10.17487/RFC7435"/> </reference><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7435.xml"/> <reference anchor="Wi-Fi_Enhanced_Open" target="https://www.wi-fi.org/beacon/dan-harkins/wi-fi-certified-enhanced-open-transparent-wi-fi-protections-without-complexity"> <front> <title>Wi-Fi CERTIFIED EnhancedOpen™:Open: TransparentWi-Fi®Wi-Fi protections without complexity</title><author><author fullname="Dan Harkins"> <organization/> </author><date>n.d.</date></front> <refcontent>Wi-Fi Alliance, The Beacon Blog</refcontent> </reference> <reference anchor="IEEE_802.11" quote-title="false" target="https://www.ieee802.org/11/"> <front><title>IEEE<title >IEEE 802.11 Working Group</title> <author><organization/><organization>IEEE</organization> </author><date>n.d.</date></front> </reference> <reference anchor="IEEE_LS" target="https://datatracker.ietf.org/liaison/1929/"> <front> <title>LiaisonStatement from IEEE 802.11 to the IETF -statement: OWE (RFC8110) now in 802.11</title> <author> <organization/> </author><date>n.d.</date><date month="May" year="2024"/> </front> <refcontent>IETF Liaison Statement</refcontent> </reference> </references> </references><?line 101?><section numbered="false" anchor="acknowledgments"> <name>Acknowledgments</name> <t>The authors would like to thank the IEEE 802.11working groupWorking Group for their work, and for taking on the responsibility for future work on the protocol described inRFC8110.</t>RFC 8110.</t> <t>In addition, we would like to thankStephen Farrell, who<contact fullname="Stephen Farrell"/>, the AD that sponsored the original work, as well asClemens Schimpe, Dorothy Stanley, Paul Wouters, Eric Vyncke, Mike Montemurro, and Peter Yee.</t><contact fullname="Clemens Schimpe"/>, <contact fullname="Dorothy Stanley"/>, <contact fullname="Paul Wouters"/>, <contact fullname="Eric Vyncke"/>, <contact fullname="Mike Montemurro"/>, and <contact fullname="Peter Yee"/>.</t> <t>Apologies to anyone we forgot to acknowledge;RFC8110RFC 8110 was written 7+ years ago and we have had many conversations with many people since then...</t> </section><section numbered="false" anchor="change-log"> <name>Change Log</name> <ul spacing="normal"> <li> <t>From -00 to -01: </t> <ul spacing="normal"> <li> <t>Fixed a nit ("This documents updates" -> "This document updates")</t> </li> <li> <t>We have the liaison from the IEEE 802.11 WG; update to point at the liaison statement.</t> </li> <li> <t>For some reason, pushing the -01 version to GitHub didn't trigger the build. Trying to post manually.</t> </li> </ul> </li> </ul> </section></back><!-- ##markdown-source: H4sIAAAAAAAAA61YXXLbyBF+n1N0YR9iJwQleTe1u9xKyoxMyaqVY5eliipP riHQJKYEzmBnBqIZld5ykhwgh8hRcpJ8PQApQlYkVzYP4g+mp3++7v66qTzP VTSx5glll17bsGDvjV3S+6ZxPrbWhGgKujKeaw6BZrbwmyYaZyk6ihXT2Ww2 ox8OX42PjujK+Wu5fOpd22RKz+eeb6D548nxD0dHh3l0uYhnqtCRl85vJmTs wilVusLqFZwovV7EfH3drrQ3uV8U23uGmfPDVyq085UJAQ7ETYMLZ7PLE6Jv SNfBwZKxJTeMFxuzEWVcmui80bV8OZv+CW/O49PHy5NM2XY1Zz9RJZyZqMLZ wDa0YULRt6zg97eqbeQQj8QNBSue9YSmH2dTfFkj2qVEOqGr02Hs6po3OC4n ivKEkLy/v+renkNWhHrE1A3bFs59Q7SzJF+62Icm8XilTS0ir/mzXjU1jwu3 kufaF9WEqhibMDk42Ds8gDqoNrFq50Cvx/3gySxkuFELKhE3tjp72XGnamzc 0zqePh1XcVVnSuk2Vg4JIsrxR9SVSHalvWdLP6e7WToxNsjBePDQ+aW25m9a MMXpqXPLmkd0fn7cnXMHV7ZO+l73EViO2UOLb7Slt1rADvv23oyHTx8YfMvr mmPMP+jiWvsSGY7sG28CD+yXuMP1uOo0va6aLm3KOr+CqhsWAPp6mCglDTM8 +P67b38vH69MfmI+zWylbcHlp/fog0kyFLVf8iBb6/V4bfKFGcPlgzlrFP8B /Mh7Jw7SYV6wj2ZhuMy5V5o7KM2jEEWDXrBIYZJsvItcSNwBT5C1NuYIAlX2 2cRNF+6WZpKbdDz7eHl2cjZ7Q1uHSRz+99//MaHLe/1dUP/6J+1ZoN4CDS1I m33qiGgY9n7UUl4iI3EfHR0MHHuCyXrt5xePawZJaIBSXLOHhbhI6mujTQCu Rz+++nFo6Lw7oQvc4pVEufBuNWDSHbmC3RJz0Iu+BF6SdWsUYC+JNlF5npOe B/EgKtXLUcmh8GbO4Su4/AUsvByRppUrGZZ1BKHWbh1Ua6UL4aMRzi6pqA2+ BHEQRWOREvmoCW0jfEhtENi4Uw15OLVYmGJMl5UJwvNtCjj2syakMJ1dOrmG hkCPWCkH0rakRetx7BHKDdeuSTfdIl2RenCFq58dQ2OlxDTtTPecvm0pmm+A aBT5FPeija3nRO4kU27f1hbSUvDf3l+buiZXFK2Xp8/5IrlambKsWYGZz2z0 rmxTXSt1e9vrvLv7FdlzC+UGVwLDNzQJJf3CFtAPEun8vIjlrugkfgR7Y2B9 m0PxrMd8vbW9wlxtV7s+3KsQSCPICyMZbNp53T8b0X5sL2RY0zXq2JIOlN3e dpwwYIK7u+wlVTieM8h+DZfqDRlpeMkihKRAMOxrt+ESNoHeHgPAitz1/EuL QQXp/vT8AicpTuQKAxrFJeUrtZ4g+RWVOEqC0CZbhO+7aFA+Xhgf/AXTYWOL hN99wWzFwuh/rEHhhV0dPkCj67/7JsBnLQ0MadBswWOpxu0CKJG9uwdAqWkX SI+mHD9QP/p6ONUzcH49nuqr8YyD2EPDhYy1sN/w6v8JtlDOQMvC2Ed0zJnK tql7Zv1SD5bdotrGjZddBLp2lnc62Lp2WQlSu/YgExN62m7UFuv9kkZqwBUA oWvPL0h1q7phL9sGl1g7OlRbK0k2mACNg+eCohjCTTQucAypki62lHOMeY3W 9clMeEjFQRxO9DtMxvOVr/57MrYFMKZpIEFwJGiUDiZgCBId5UpfwzSv1Y4f i4Gzwilg6Omfp89EIURjXSepi91dYfo5dgLRMi2E7Woul3IjqNtJ9+ODyz9k C7AhZ3ddzXQrL1Yc19Yl1eaauwGn7fUXo2Xdj5b0yyC1GySMT89HXZvJM52E ejCRoEaCmZtaIhaBJyBXj9U/YjsDb5f4aZWYfc2PensRucFUoBPZrmt087py NH1Dyb7zshpUrPDjbGmsrjunZRqsISzvx6mSA10UFaoEe/sbB6+qjWxNtubN iD7otsZ8bbFVo8dnHqPuL6CBax6pd+LKO/xG5BUIznVU8oEhSX9lIbspqtct Ewc4KYTUTyx4LF230ewyxj/dd634h1JBG9H3v6MNa6RKL10CG9crfSMvJXrN pnK6gWv6fmntnjfs0KYofulEmZzjcWqaY+C2ZDp3y8fr47d0ImtifngoDuaH ac3FQ/NZpiFZVPmLbFCaYbvsZJT/kbJH96DsZdJy1Xsv6e83124r/WKhOf2p vypeNKB3UE3cv5d23bDdbcedkyi04FZSgDpI1TRtqLqdiyUUEqT6/yqcmvi2 nVNpSvsb2RTNcsmptpPieWvqEuPMb9J1cQEjCcC2GDsbAPkfPxrSBNMQAAA= --></rfc>