rfc9672.original.xml   rfc9672.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.18 (Ruby 3.3. <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
3) --> -wkumari-rfc8110-to-ieee-02" number="9672" category="info" consensus="true" subm
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft issionType="IETF" obsoletes="" updates="8110" tocInclude="true" sortRefs="true"
-wkumari-rfc8110-to-ieee-02" category="info" consensus="true" submissionType="IE symRefs="true" version="3" xml:lang="en" >
TF" updates="8110" tocInclude="true" sortRefs="true" symRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 3.22.0 -->
<front> <front>
<title abbrev="RFC8110-to-IEEE">Transferring Opportunistic Wireless Encrypti <title abbrev="RFC 8110 to IEEE">Transferring Opportunistic Wireless Encrypt
on to the IEEE 802.11 Working Group</title> ion to the IEEE 802.11 Working Group</title>
<seriesInfo name="Internet-Draft" value="draft-wkumari-rfc8110-to-ieee-02"/> <seriesInfo name="RFC" value="9672"/>
<author initials="W." surname="Kumari" fullname="Warren Kumari"> <author initials="W." surname="Kumari" fullname="Warren Kumari">
<organization>Google, LLC</organization> <organization>Google, LLC</organization>
<address> <address>
<email>warren@kumari.net</email> <email>warren@kumari.net</email>
</address> </address>
</author> </author>
<author initials="D." surname="Harkins" fullname="Dan Harkins"> <author initials="D." surname="Harkins" fullname="Dan Harkins">
<organization>Hewlett-Packard Enterprise</organization> <organization>Hewlett-Packard Enterprise</organization>
<address> <address>
<email>daniel.harkins@hpe.com</email> <email>daniel.harkins@hpe.com</email>
</address> </address>
</author> </author>
<date year="2024" month="August" day="07"/> <date year="2024" month="December"/>
<keyword>IEEE</keyword> <keyword>IEEE</keyword>
<keyword>OWE</keyword> <keyword>OWE</keyword>
<keyword>Opportunistic Wireless Encryption</keyword> <keyword>Opportunistic Wireless Encryption</keyword>
<keyword>RFC8110</keyword> <keyword>RFC8110</keyword>
<abstract> <abstract>
<?line 56?> <?line 56?>
<t>RFC8110 describes Opportunistic Wireless Encryption (OWE), a mode that allows <t>RFC 8110 describes Opportunistic Wireless Encryption (OWE), a mode that allow s
unauthenticated clients to connect to a network using encrypted traffic. This unauthenticated clients to connect to a network using encrypted traffic. This
document transfers the ongoing maintenance and further development of the protoc ol to the IEEE 802.11 Working Group.</t> document transfers the ongoing maintenance and further development of the protoc ol to the IEEE 802.11 Working Group.</t>
<t>This document updates RFC8110 by noting that future work on the protoco
l described in RFC8110 will occur in the IEEE 802.11 Working Group.</t> <t>This document updates RFC 8110 by noting that future work on the protoc
ol described therein will occur in the IEEE 802.11 Working Group.</t>
</abstract> </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.ht
ml"/>.
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> </front>
<middle> <middle>
<?line 64?> <?line 64?>
<section anchor="introduction"> <section anchor="introduction">
<name>Introduction</name> <name>Introduction</name>
<t><xref target="RFC8110"/> describes Opportunistic Wireless Encryption (O
WE), a mode of <t>Opportunistic Wireless Encryption (OWE) <xref target="RFC8110"/> is a m
ode of
opportunistic security <xref target="RFC7435"/> for IEEE Std 802.11 that provide s encryption opportunistic security <xref target="RFC7435"/> for IEEE Std 802.11 that provide s encryption
of the wireless medium without authentication.</t> of the wireless medium without authentication.</t>
<t>Since publication, <xref target="RFC8110"/> (also known as "<xref targe t="Wi-Fi_Enhanced_Open"/>") has been widely implemented and deployed.</t> <t>Since publication, <xref target="RFC8110"/> (also known as "<xref targe t="Wi-Fi_Enhanced_Open"/>") has been widely implemented and deployed.</t>
<t><xref target="IEEE_802.11"/> has requested <xref target="IEEE_LS"/> tha
t in order to allow for ongoing maintenance and further development of the proto <t>The IEEE 802.11 Working Group <xref target="IEEE_802.11"/> has requested the
col, and to ensure that the protocol remains in sync with the IEEE protocols, fu ability to maintain and develop OWE (see <xref target="IEEE_LS"/>) to ensure tha
ture work on the protocol described in RFC8110 will now occur in <xref target="I t the protocol remains in sync with the IEEE protocols. This document represent
EEE_802.11"/>. This document is a concurrence.</t> s concurrence that future work on OWE <xref target="RFC8110"/> will now occur in
the IEEE 802.11 Working Group.
</t>
</section> </section>
<section anchor="transfer-of-maintenance"> <section anchor="transfer-of-maintenance">
<name>Transfer of Maintenance</name> <name>Transfer of Maintenance</name>
<t>At the request of <xref target="IEEE_802.11"/>, in order to allow for o
ngoing maintenance <t>
and further development of the protocol, and to ensure that the protocol This document represents concurrence that future work on OWE <xref target="RF
remains in sync with the IEEE protocols, this document specifies that future C8110"/> will now occur in the IEEE 802.11 Working Group <xref target="IEEE_802.
work on the protocol described in RFC8110 will now occur in <xref target="IEEE_8 11"/> to ensure that the protocol remains in sync with the IEEE protocols. </t>
02.11"/>.</t> <t>
<t>The protocol defined in RFC8110 will be duplicated in <xref target="IEE The OWE protocol <xref target="RFC8110"/> will be duplicated by the IEEE 802.
E_802.11"/> 11 Working
such that that document alone will be enough to implement it and any Group <xref target="IEEE_802.11"/> such that the document alone will be enoug
further maintenance or modification of the protocol will be performed h to implement,
in IEEE under its policies and procedures.</t> maintain, and modify the protocol within the IEEE under its policies and
procedures.
</t>
</section> </section>
<section anchor="security-considerations"> <section anchor="security-considerations">
<name>Security Considerations</name> <name>Security Considerations</name>
<t>This document simply notes that future work on the protocol described i n <t>This document simply notes that future work on the protocol described i n
RFC8110 will now occur in the IEEE. As such, it does not introduce any new <xref target="RFC8110"/> will now occur in the IEEE. As such, it does not introd uce any new
security considerations.</t> security considerations.</t>
</section> </section>
<section anchor="iana-considerations"> <section anchor="iana-considerations">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t>This document has no IANA actions.</t> <t>This document has no IANA actions.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references anchor="sec-combined-references"> <references anchor="sec-combined-references">
<name>References</name> <name>References</name>
<references anchor="sec-normative-references"> <references anchor="sec-normative-references">
<name>Normative References</name> <name>Normative References</name>
<reference anchor="RFC8110">
<front> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.81
<title>Opportunistic Wireless Encryption</title> 10.xml"/>
<author fullname="D. Harkins" initials="D." role="editor" surname="H
arkins"/>
<author fullname="W. Kumari" initials="W." role="editor" surname="Ku
mari"/>
<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>
</references> </references>
<references anchor="sec-informative-references"> <references anchor="sec-informative-references">
<name>Informative References</name> <name>Informative References</name>
<reference anchor="RFC7435">
<front> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.74
<title>Opportunistic Security: Some Protection Most of the Time</tit 35.xml"/>
le>
<author fullname="V. Dukhovni" initials="V." surname="Dukhovni"/>
<date month="December" year="2014"/>
<abstract>
<t>This document defines the concept "Opportunistic Security" in t
he context of communications protocols. Protocol designs based on Opportunistic
Security use encryption even when authentication is not available, and use authe
ntication when possible, thereby removing barriers to the widespread use of encr
yption on the Internet.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="7435"/>
<seriesInfo name="DOI" value="10.17487/RFC7435"/>
</reference>
<reference anchor="Wi-Fi_Enhanced_Open" target="https://www.wi-fi.org/be acon/dan-harkins/wi-fi-certified-enhanced-open-transparent-wi-fi-protections-wit hout-complexity"> <reference anchor="Wi-Fi_Enhanced_Open" target="https://www.wi-fi.org/be acon/dan-harkins/wi-fi-certified-enhanced-open-transparent-wi-fi-protections-wit hout-complexity">
<front> <front>
<title>Wi-Fi CERTIFIED Enhanced Open™: Transparent Wi-Fi® protection <title>Wi-Fi CERTIFIED Enhanced Open: Transparent Wi-Fi protections
s without complexity</title> without complexity</title>
<author> <author fullname="Dan Harkins">
<organization/> <organization/>
</author> </author>
<date>n.d.</date>
</front> </front>
<refcontent>Wi-Fi Alliance, The Beacon Blog</refcontent>
</reference> </reference>
<reference anchor="IEEE_802.11" target="https://www.ieee802.org/11/">
<reference anchor="IEEE_802.11" quote-title="false" target="https://www.
ieee802.org/11/">
<front> <front>
<title>IEEE 802.11 Working Group</title> <title >IEEE 802.11 Working Group</title>
<author> <author>
<organization/> <organization>IEEE</organization>
</author> </author>
<date>n.d.</date>
</front> </front>
</reference> </reference>
<reference anchor="IEEE_LS" target="https://datatracker.ietf.org/liaison /1929/"> <reference anchor="IEEE_LS" target="https://datatracker.ietf.org/liaison /1929/">
<front> <front>
<title>Liaison Statement from IEEE 802.11 to the IETF - OWE (RFC8110 ) now in 802.11</title> <title>Liaison statement: OWE (RFC8110) now in 802.11</title>
<author> <author>
<organization/> <organization/>
</author> </author>
<date>n.d.</date> <date month="May" year="2024"/>
</front> </front>
<refcontent>IETF Liaison Statement</refcontent>
</reference> </reference>
</references> </references>
</references> </references>
<?line 101?>
<section numbered="false" anchor="acknowledgments"> <section numbered="false" anchor="acknowledgments">
<name>Acknowledgments</name> <name>Acknowledgments</name>
<t>The authors would like to thank the IEEE 802.11 working group for their work, <t>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 and for taking on the responsibility for future work on the protocol
described in RFC8110.</t> described in RFC 8110.</t>
<t>In addition, we would like to thank Stephen Farrell, who AD sponsored t <t>In addition, we would like to thank <contact fullname="Stephen Farrell"
he />, the AD that sponsored the
original work, as well as Clemens Schimpe, Dorothy Stanley, Paul Wouters, Eric V original work, as well as <contact fullname="Clemens Schimpe"/>, <contact fullna
yncke, me="Dorothy Stanley"/>, <contact fullname="Paul Wouters"/>, <contact fullname="E
Mike Montemurro, and Peter Yee.</t> ric Vyncke"/>,
<t>Apologies to anyone we forgot to acknowledge; RFC8110 was written 7+ ye <contact fullname="Mike Montemurro"/>, and <contact fullname="Peter Yee"/>.</t>
ars ago <t>Apologies to anyone we forgot to acknowledge; RFC 8110 was written 7+ y
ears ago
and we have had many conversations with many people since then...</t> and we have had many conversations with many people since then...</t>
</section> </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" -&gt; "This document upda
tes")</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 trigg
er 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=
</back>
</rfc> </rfc>
 End of changes. 31 change blocks. 
167 lines changed or deleted 75 lines changed or added

This html diff was produced by rfcdiff 1.48.