I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These
comments were written primarily for the benefit of the security area
directors. Document editors and WG chairs should treat these comments just
like any other last call comments.

The summary of the review is Ready with Nits.

Security
--------

Section 1 says that Security is out of scope for this draft. The Security
Considerations section, in its entirety, is as follows:
"Most RAW technologies integrate some authentication or encryption
mechanisms that were defined outside the IETF."

Perhaps that is adequate for this document; however, I would recommend that
some material from the last paragraph of Section 1 be added to the above.
Perhaps something like the following sentence:
"The IETF specifications referenced herein each provide their own Security
Considerations, and the lower layer technologies used provide their own
security at Layer-2."

Adding this would more than double the size of the Security Considerations.
:-)


Big Nits
--------

Section 4: This section states that IEEE Std 802.11-2012 and IEEE Std
802.11-2016 "introduce" support for various features. This is wrong. These
are merely 802.11 standard complete roll-ups, each derived from the
previous roll-up by incorporating the 802.11 standard amendments adopted
since that previous roll-up. Significant features were "introduced" by such
amendments to 802.11.

Section 4.3.1/4.3.2.2: References to 802.11be as being in the future, or
being "expected" to include or introduce features, are out of date. I
believe 802.11be received final approval as a standard in September 2024.
See https://grouper.ieee.org/groups/802/11/Reports/802.11_Timelines.htm


Smaller Nits
------------

Title: Should add "(RAW)" after "Reliable and Available Wireless".

Abstract: The word "browses" in the first line sounds strange. I suggest
replacing it with "surveys".

Section 1: Same problem with "browses".

Section 3:

"which enables to use the" -> "which enables using the"

"listener enables to always maintain them" -> "listener enables always
maintaining them"

Section 4:

General: Lots of features are listed in Section 4 but there should be some
statement that there are many, many, many more in the 802.11 standard.
After all, we are talking about thousands of pages. (802.11-2020 is 4,377
pages long.)

General: Sees like somewhere you might mention 802.11 frame fragmentation.
On a very noisy link, you don't want to transmit for too long as the
probability of an error would be very high and the unicast link level
acknowledgement would force retransmission of a large frame. By
fragmenting, each transmission is shorter and the link level retransmission
applies to each fragment which is a smaller amount to retransmit. Then
there is the whole TXOP (transmission opportunity) feature...

Initial part of Section 4: I consider "Wi-Fi 6", "Wi-Fi 7", and "Wi-Fi 8"
to be marketing designations. Actual technical features of IEEE Std 802.11
have specific technical feature names and almost always correspond to a
particular amendment. But it may be impractical to change at this point.

Section 4.1:

The paragraph on the Wi-Fi Alliance reads like marketing. There should be
some sort of reference for the WFA. If nothing else, the
https://www.wi-fi.org/ URL.

There should also be a reference for the Avnu Alliance. Perhaps
https://avnu.org/

Section 4.2.1.4: Temporal references generally do not age well. I suggest
that both occurrences of "new" be deleted from this section.

Section 4.3.2.2: It is an interesting question whether 802.11be permits
sending the same frame more or less simultaneously over multiple links in
MLO operation. See my presentation
https://mentor.ieee.org/802.11/dcn/24/11-24-1705-01-00bn-frer-for-802-11bn.pptx

Section 5.1, last sentence: "integrated to other standards" -> "integrated
with other standards"

Section 5.2: "be combined to OFDM" -> "be combined with OFDM"

Section 5.2.1: "enables to meet industrial" -> "enables meeting industrial"

Section 5.2.1.2:

"allows to deliver a packet" -> "allows delivering a packet"

"in fact associated to a Track." -> "in fact associated with a Track."

"the transmit bundle associated to the Track" -> "the transmit bundle
associated with the Track"


I did only a light review of Sections 5, 6, 7, 10, and 11.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com