Diff: rfc9672.original

	rfc9672.original	rfc9672.txt


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

	Transferring Opportunistic Wireless Encryption to the IEEE 802.11	Transferring Opportunistic Wireless Encryption to the IEEE 802.11
	Working Group	Working Group

	draft-wkumari-rfc8110-to-ieee-02

	Abstract	Abstract


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


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


	About This Document

	This note is to be removed before publishing as 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 for this draft and an issue tracker can be found at
	https://github.com/wkumari/draft-wkumari-rfc8110-to-ieee.

	Status of This Memo	Status of This Memo


	This Internet-Draft is submitted in full conformance with the	This document is not an Internet Standards Track specification; it is
	provisions of BCP 78 and BCP 79.	published for informational purposes.

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


	Internet-Drafts are draft documents valid for a maximum of six months	This document is a product of the Internet Engineering Task Force
	and may be updated, replaced, or obsoleted by other documents at any	(IETF). It represents the consensus of the IETF community. It has
	time. It is inappropriate to use Internet-Drafts as reference	received public review and has been approved for publication by the
	material or to cite them other than as "work in progress."	Internet Engineering Steering Group (IESG). Not all documents
		approved by the IESG are candidates for any level of Internet
		Standard; see Section 2 of RFC 7841.


	This Internet-Draft will expire on 8 February 2025.	Information about the current status of this document, any errata,
		and how to provide feedback on it may be obtained at
		https://www.rfc-editor.org/info/rfc9672.

	Copyright Notice	Copyright Notice

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

	This document is subject to BCP 78 and the IETF Trust's Legal	This document is subject to BCP 78 and the IETF Trust's Legal

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

	Table of Contents	Table of Contents


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

	1. Introduction	1. Introduction


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

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

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

	skipping to change at page 3, line 21 ¶	skipping to change at line 97 ¶
	RFC8110 will now occur in [IEEE_802.11].	RFC8110 will now occur in [IEEE_802.11].

	The protocol defined in RFC8110 will be duplicated 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	such that that document alone will be enough to implement it and any
	further maintenance or modification of the protocol will be performed	further maintenance or modification of the protocol will be performed
	in IEEE under its policies and procedures.	in IEEE under its policies and procedures.

	3. Security Considerations	3. Security Considerations

	This document simply notes that future work on the protocol described	This document simply notes that future work on the protocol described

	in RFC8110 will now occur in the IEEE. As such, it does not	in [RFC8110] will now occur in the IEEE. As such, it does not
	introduce any new security considerations.	introduce any new security considerations.

	4. IANA Considerations	4. IANA Considerations

	This document has no IANA actions.	This document has no IANA actions.

	5. References	5. References

	5.1. Normative References	5.1. Normative References

	[RFC8110] Harkins, D., Ed. and W. Kumari, Ed., "Opportunistic	[RFC8110] Harkins, D., Ed. and W. Kumari, Ed., "Opportunistic
	Wireless Encryption", RFC 8110, DOI 10.17487/RFC8110,	Wireless Encryption", RFC 8110, DOI 10.17487/RFC8110,

	March 2017, <https://www.rfc-editor.org/rfc/rfc8110>.	March 2017, <https://www.rfc-editor.org/info/rfc8110>.

	5.2. Informative References	5.2. Informative References

	[IEEE_802.11]	[IEEE_802.11]

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


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

	[RFC7435] Dukhovni, V., "Opportunistic Security: Some Protection	[RFC7435] Dukhovni, V., "Opportunistic Security: Some Protection
	Most of the Time", RFC 7435, DOI 10.17487/RFC7435,	Most of the Time", RFC 7435, DOI 10.17487/RFC7435,

	December 2014, <https://www.rfc-editor.org/rfc/rfc7435>.	December 2014, <https://www.rfc-editor.org/info/rfc7435>.

	[Wi-Fi_Enhanced_Open]	[Wi-Fi_Enhanced_Open]

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

	Acknowledgments	Acknowledgments


	The authors would like to thank the IEEE 802.11 working group for	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	their work, and for taking on the responsibility for future work on

	the protocol described in RFC8110.	the protocol described in RFC 8110.


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


	Apologies to anyone we forgot to acknowledge; RFC8110 was written 7+	Apologies to anyone we forgot to acknowledge; RFC 8110 was written 7+
	years ago and we have had many conversations with many people since	years ago and we have had many conversations with many people since
	then...	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	Authors' Addresses

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

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

End of changes. 22 change blocks.
	82 lines changed or deleted	55 lines changed or added
This html diff was produced by rfcdiff 1.48.