| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Preface: there is a lot of information here. Please READ IT ALL.
All, the editorial team has provided proposed responses to all comments and provided seven files to help you review these responses, found in one zip file here:
https://www.ieee802.org/3/da/comments/802.3da_draft2p1_Proposed%20Remedies.zip. The seven files are: 4 Fancy Committee Reports (various sort methods) 1 Spreadsheet 1 EZ Bucket 1 Editorial Bucket We received 123 total comments, with 6 coming in after the deadline, so they are late. The editors will ask if there is any objection to including these comments in with the comments that were submitted on
time. These comments all came in slightly past the deadline and were well within the window for the editors to consider them during their processing.
Of particular interest are the EZ bucket and Editorial bucket files. As these are considered non-controversial, we will attempt to approve these two buckets with motions, which would resolve 63 of the 123
comments. Your job, as a TF member, is to review these EZ and Editorial comments and let the editors know if you would like any comments removed from those buckets.
The deadline for this request is Thursday 6 March 2025, 11:59 AOE.
As we only have one day to process the remaining 60 comments (plus whatever is pulled from the EZ and Editorial buckets),
I am announcing that I will schedule two meetings for the week following the plenary series to allow us to complete comment resolution. These meetings will be on Tuesday 18 March and Thursday 20 March, from 10am
– noon US Eastern time. We will discuss the agenda of these two meetings as we wrap up business in Atlanta during the AM2 session on 12 March. I will send calendar invites shortly.
We have limited time during the plenary and the editors have given you ample time to preview the comments and resolutions. Please use this time to get yourself acquainted with the responses and come ready
to close comments. I will not entertain slowing down for someone to digest a comment response because they showed up unprepared. If you disagree with a response, use the reflector to start conversations and perhaps modify the remedies. Let’s all work together
to make this process efficient. Thank you and see you in Atlanta. Regards, Chad Jones Principal Engineer, Cisco Systems Executive Secretary, IEEE 802.3 Working Group Chair, IEEE P802.3da Task Force Principal, NFPA 70 CMP3 To unsubscribe from the STDS-802-3-SPMD list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-SPMD&A=1 |