[802SEC] IEEE 802.3 comments on IEEE802 PARs/CSDs - November 2024
Colleagues,
The IEEE 802.3 WG provides the following comments on the PARs/CSDs under
consideration at the November 2024 Plenary meeting:
With regards,
-Kent
Chair, IEEE 802.3 PAR review Ad Hoc
P802.1CB - Standard - Frame Replication and Elimination for Reliability -
Revision to IEEE Standard 802.1CB-2017
PAR Comments: none
P802.1CBec - Amendment - Guidance for Sequence Recovery Function Parameter
Configuration
PAR Comments:
5.2.b: there is a statement "This amendment also includes technical and
editorial corrections in the description of existing IEEE Std 802.1CB
functionality." For clarification how is this scope different from the
revision PAR at
https://www.ieee802.org/1/files/public/docs2024/cb-Hantel-draft-PAR-0924-v01
.pdf
Suggest to clarify the difference in the text.
CSD Comments:
In 1.2.3, it is our understanding that the base specification already
"addresses the setting of parameters" and that this project would be adding
an informative annex to provide information on setting the parameters.
Suggest to change "addresses the setting of parameters" to "addresses the
recommended setting of parameters"
In 1.2.4, the first sentence of the response is unclear as to the expected
output of the project. Is the output expected to be a process or flow to
set parameter values or is it a recommended set of values to use for the
parameters? Please clarify.
In 1.2.5, there is a similar lack of clarity on the output of the project as
in 1.2.4. Please clarify if the output expected to be a process or flow to
set parameter values or a recommended set of values to use for the
parameters.
P802.11bq - Amendment - Enhancements for Integrated mmWave (IMMW) WLAN
PAR Comments:
In 5.2.b: expand acronym OFDM in the first sentence of the first paragraph.
Also expand PPDU in the first sentence of the second paragraph.
In 5.2.b: remove "standardized" from the first sentence as this is
superfluous for a standard.
In 5.5: the response is puzzling for us. If we understand the project
properly, it is to enable non-standalone operation in the 42 GHz and 71 GHz
bands. However, the response of 5.5 boils down to wireless LANs need a lot
of throughput, the 42 GHz and 71 GHz bands provide spectrum, and then a
simple statement that the functionality of this standard (non-standalone
operation) is needed.
Please clarify if there will be standalone as well as non-standalone modes
of operation, and whether there are existing non-cost-effective methods in
the standard.
Suggest to change the last sentence of the response to be "Enabling
operation in the unlicensed bands between 42 GHz and 71 GHz in addition to
one or more of the existing bands, i.e., non-standalone operation, is
required."
CSD Comments:
In 1.2.1, the long response could be condensed to improve readability and
comprehension by the reader.
In 1.2.5 item b, please expand on the impact of the cost impact of the new
mmWW radio, if any.
Suggest change is to replace "enhance the throughput and improve latency of"
with "to access the 42 GHz and 71 GHz bands with". The rationale is that
the existing language suggests a different project focus.
P802.16 - Standard for Air Interface for Broadband Wireless Access Systems
PAR comments: none
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.