Colleagues,
The proposed response reports were updated after more review by the editorial team.
Updated responses were provided for comments 64, 457,549, 550, 561, 571, 572, 575, 322, and 196.
Additionally, the following comments were moved into ‘bucket1’ (T/TR): 561, 571, 572.
Lastly, comment 196 was removed from bucket2 because it was reclassified from ER to T.
Please note that there are four update files:
With regards,
-Kent
_____________________________________________
From: Lusted, Kent C <kent.c.lusted@xxxxxxxxx>
Sent: Thursday, May 30, 2024 5:03 PM
To: STDS-802-3-B400G@xxxxxxxxxxxxxxxxx
Cc: Lusted, Kent C <kent.c.lusted@xxxxxxxxx>
Subject: Task Force Review (D1.0) - Proposed Responses and Bucket1 & Bucket2 Posted
Dear Colleagues,
The P802.3dj Task Force Chair delegated to me the announcement of the proposed response reports.
Note to all commenters and participants –
Participants are asked not to pull comments from ‘bucket1’ to make editorial modifications or wording improvements to the proposed response text.
During the P802.3dj Task Force electronic meeting session, a motion is anticipated on 6 June 2024 to accept the proposed responses to T/TR comments in “Bucket 1.” Please note any comments withdrawn from “Bucket 1” will be excluded
explicitly in this motion.
As announced during the review period, the “bucket2” E/ER items were left to editorial discretion for implementation. The TF leadership and the editorial team will not accept requests to pull comments from bucket2. Instead, participants
are encouraged to submit E/ER comments to the relevant editor lead via the marked up PDF process.
Additionally, the editorial team may continue to refine the proposed responses to comments and may provide updated proposed response comment reports. These updates, if made, will be announced via the email reflector.
My thanks to all individuals for their review of the document, and Matt Brown and our amazing editorial team for their diligent efforts in developing proposed responses. Please recognize that the editorial team spent hundreds of hours
preparing the responses to save participants time during comment resolution.
Regards,
-Kent