| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
All,
I updated the slides to remove the first (not good) proposal and added another slide to show changes to DeregistrationTrigger. Also, revised and improved the description of the proposed solution.
Please, let me know if I can list you as supporter of this proposal. Marek will be submitting a TR comment later tonight
Glen
From: Marek Hajduczenia <mxhajduczenia@xxxxxxxxx>
I am happy to submit a post-deadline TR and I will not affect my current vote
Marek
From: Glen Kramer <glen.kramer@xxxxxxxxxxxx>
Marek,
I agree. Unless anyone strongly objects to it, let’s plan to submit a comment by EoD today. It is easy to withdraw it, if we later decide that we don’t want the change for whatever reason. And I suppose we can update the supplemental file any time before the maintenance TF call on Sept 7th.
Since my 802.3 membership has lapsed, I cannot submit TRs. Are you OK to submit this comment as a TR?
Thanks, Glen
From: Marek Hajduczenia <mxhajduczenia@xxxxxxxxx>
Glen,
I would like to recommend an addition pointing out the preferred approach (I assume it is still #2). Apart from this minor suggested change, I am OK to be listed as a co-author, and happy to submit a post-deadline TR comment. I already have an outstanding negative ballot against 802.3dc draft D2.0.
Given the schedule for 802.3dc calls has been already set and editors are working on the proposed responses, I would recommend we submit the comment ASAP, even if there is a revised version of the deck to be shown at the comment resolution meeting. Note that changes in co-authors or any non-technical changes are usually not a problem in such a case.
Regards
Marek
From: stds-1904-4-tf@xxxxxxxx <stds-1904-4-tf@xxxxxxxx> On Behalf Of Glen Kramer
Dear colleagues,
The 802.3 maintenance TF chair just announced a series of calls to resolve comments against 802.3 D2.0. They already have a large number of comments, including 10 post-deadline comments. I would like to submit our comment fairly soon, as they consider the post-deadline comments in FIFO order.
Please take another look at the following presentation that we discussed yesterday and let me know whether you (a) agree and support this solution, or (b) can offer an improved solution. https://www.ieee1904.org/4/meeting_archive/2021/08/tf4_2108_kramer_12.pdf
I would like to attach this presentation as a comment supplement to better illustrate to 802.3 maintenance TF the problem and the solution. And to emphasize that this material was reviewed and vetted by many people, I would like to include all names as co-authors of this presentation. Please, let me know if it is ok to include your name on the first slide. If you don’t feel like you understand this material enough or feel uncomfortable with being listed for any reason whatsoever, it is no problem, but please let me know either way, so I don’t continue waiting. I would like to submit the comment the first half of next week.
If anyone would like to discuss this more, let me know and I will be happy to schedule a webex call.
Thank you, Glen
From: Adam Healey <0000074ad040f574-dmarc-request@xxxxxxxx>
Colleagues,
I am announcing a series of teleconference meetings for the resolution of comments received against the IEEE P802.3 (IEEE 802.3dc) initial Working Group ballot.
The teleconference coordinates may be found on the IEEE 802.3 Call and Meeting Calendar. Note that motions may be considered at these meetings.
Meetings have been provisioned based on a rough guess of the time needed to complete comment resolution. Meetings will be cancelled if they are not needed. However, there is not enough time to add more meetings while keeping to the target project schedule. As a result, I will allow the 27 September meeting to run as long as needed to complete comment resolution.
Comment reports will be posted following the announcement of the ballot results. I will provide more information about the comment resolution process and the expected order of consideration as we approach the 7 September meeting.
Thanks, --Adam
To unsubscribe from the STDS-802-3-MAINT list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-MAINT&A=1 To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1 To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1 To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1 |
Attachment:
tf4_2108_kramer_12_reregistrtion_3ca_2.pdf
Description: Adobe PDF document
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature