Re: [saag] Transferring OWE to the IEEE 802.11 group…

Mike,

                IEEE 802.11 is planning to issue a liaison statement to IETF  that indicates their understanding and support of this action. I expect that the IEEE 802.11 WG will approve transmittal of the liaison statement during the upcoming interim meeting in a couple of weeks’ time. Once the IEEE 802 LMSC Executive Committee approves sending this external liaison, it can then be transmitted to the IETF.

                I can’t speak to whether the copyright transfers. IEEE charges for access to IEEE 802 standards for the first six months after they are published. Thereafter, they are freely available under the IEEE GET Program™. (https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68)

                                -Peter

On 4/29/24, 8:42 AM, "saag on behalf of StJohns, Michael" <saag-bounces@ietf.org on behalf of msj@nthpermutation.com> wrote:

Since we’ve never done this in reverse before, maybe get IEEE to co publish the update/change control RFC in their series at the same time? Or as some sort of record?

What do you intend for the status of the RFC to be?  Historic?   Cancelled?  Transferred? Informational?

Does the copyright transfer?  E.g. does community lose the right to make derivative works except within the IEEE system?  Does IEEE get to charge people for the OWE standard?

Mike

Ps - transfer makes sense.  But let’s make sure we don’t lose current rights.  

On Mon, Apr 29, 2024 at 11:27 Warren Kumari <warren@kumari.net> wrote:

Hi all,

In 2017 we published RFC8110 - "Opportunistic Wireless Encryption"[0], an "extension to IEEE Std 802.11 to provide for opportunistic (unauthenticated) encryption to the wireless media."

This is an extension to IEEE802.11, but we published it through the IETF process for reasons which are a: no longer important and b: best left to history. OWE is now widely deployed, both in vendor code as well as in the real world, and the IEEE would like to take over the future care and feeding of the protocol, make some much needed updates, etc. 

Seeing as this is an extension to IEEE work, this makes sense to the authors, and so we'd like to "transfer[s] the ongoing maintenance and further development of the protocol to the IEEE 802.11 Working Group."

So, what does it even mean to transfer a protocol to someone else? Well, basically we publish an RFC noting that the IETF is not planning any future updates to this protocol, and advising readers to follow the work over there instead. 

Here is our (really short) draft noting this: https://datatracker.ietf.org/doc/draft-wkumari-rfc8110-to-ieee/

The primary purpose of the draft is to both inform future readers that the IETF is not working on this (which is why we are "Update"ing RFC8110), and to make it clear that the IETF and IEEE are cooperating (and that the IEEE didn't steal the work, or anything like that…)

W

[0]: Also known as "Wi-Fi CERTIFIED Enhanced Open(TM)" by the WiFi Alliance

P.S: Yes, there has already been a fair bit of discussion though the liaisons, the IETF-IEEE coordination group, etc.

_______________________________________________
saag mailing list
saag@ietf.org
https://www.ietf.org/mailman/listinfo/saag

_______________________________________________ saag mailing list saag@ietf.org https://www.ietf.org/mailman/listinfo/saag 