| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi John, Thanks for considering my comments. Your updated text looks fine to me. I would not have any concern with sending this updated text out of the September meeting.
Tom From: jdambrosia@xxxxxxxxx <jdambrosia@xxxxxxxxx> Tom, When I wrote this draft, I anticipated that this liaison will be sent out of the Sept Interim meeting. At that point in time we have to be careful to not mis convey
any meanings on what we send out, and the clarifications of pending final approval become important. Also, I added in some text to address other thoughts our discussion has led. So here is my latest updated proposed text –
The list of currently adopted objectives, pending final approval by the IEEE 802.3 Working Group, may be found at
https://www.ieee802.org/3/B400G/proj_doc/objectives_b400g_210826.pdf.
It is anticipated that the approved output of the IEEE 802.3 Beyond 400 Gb/s Ethernet Study Group will result in the formation of the IEEE P802.3df Task Force with the first Task Force meeting likely to happen in
January 2022. At that time the new Task Force will begin its work on developing the new amendment to address 800 Gb/s Ethernet and 1.6 Tb/s specifications, as well as developing new physical layer specifications for 200 Gb/s and 400 Gb/s Ethernet. However, I am wondering if this is the wrong tact – and we should write the liaison out of the Nov meeting and add highlighted text for David to address after the
SA Board has approved the project at the Dec standards board meeting. I just checked the IOWN website and see that their next members meeting is Oct 6 – 8. So if we wanted to give them something for that meeting to consider then we
should respond in September, however, given all of the discussions this draft has generated, it would seem to me that this would be clearer if we just write the response based on a Nov timeframe. Thoughts? John
From: Huber, Tom (Nokia - US/Naperville) <tom.huber@xxxxxxxxx>
Hi John, I also don’t suggest that we need a full description of the process. However, we do want to avoid conveying any impression that the work of the B400G SG being complete means there is a B400G Ethernet standard available in the near future.
We all know that there are many years of work ahead of us when the SG finishes and a TF is formed, but we shouldn’t assume that IOWN will understand that subtlety of the process. Since the SG home page has a link to the objectives and includes the notice that they are pending, another option might be to delete the sentence pointing to the objectives and the paragraph that indicates the objectives are not yet approved,
and modify the penultimate paragraph to say: It is anticipated that the work of the IEEE 802.3 Beyond 400 Gb/s Ethernet Study Group will complete by the end of the year, and a Task Force will be formed to develop the text of an amendment to 802.3 based on
the work of the Study Group. The first meeting of this task force is expected to happen in January 2022. Regards, Tom From: jdambrosia@xxxxxxxxx <jdambrosia@xxxxxxxxx>
Tom, These edits are not properly addressing the process. This language implies that only 802.3 approves the project. That is just the first step – I left out the 802 EC approval and the Standards Board approvals on purpose, and didn’t go into the sausage making on purpose.
Furthermore, I don’t see a TF as modifying to meet objectives. Instead it would begin the process of selecting baselines that would form the basis of the new amendment to the 802.3 standard. I don’t suggest going into the full process, and using the tact I originally used. I can try to come up with better language to address the second point. John From: Huber, Tom (Nokia - US/Naperville) <tom.huber@xxxxxxxxx>
Hi John, As this is the first liaison exchanged with IOWN, it might be useful to provide them with a bit more information regarding the next steps in the 802.3 process. The text as written could be misinterpreted if the IOWN folks don’t fully appreciate
the difference between the 802.3 Working Group, an 802.3 Study Group, and an 802.3 Task Force.
I would suggest changing the second and third to last paragraphs as shown, so that it’s more clear that the SG concluding is more of an administrative formality, and that there is still considerable work to be done: Please note that the objectives and accompanying project documentation are still pending approval by the IEEE 802.3 Ethernet Working Group.
It is expected that this approval will occur before the end of the year. Once that approval is given, a Task Force will be created to begin the work of determining the modifications to be made 802.3 to address the stated objectives.
The first meeting of this Task Force is anticipated to occur in January 2022.
Regards, Tom From: John D'Ambrosia <jdambrosia@xxxxxxxxx>
All In preparation for next week’s Interim meeting I have reviewed the liaisons that have been assigned to the Study Group to consider. (Note that the September session page has been updated to include these liaisons -
https://www.ieee802.org/3/B400G/public/21_09/index.html). I propose the following –
Anyone disagreeing with these recommendations are invited to comment on the reflector. Anyone wishing to comment on the proposed liaison to IOWN, please direct to the reflector.
Please note that if responses to ITU-T SG15 or OIF are deemed necessary, we need to generate and approve them at next week’s meeting in order to bring in front of the WG. Regards, John D’Ambrosia Chair, IEEE 802.3 Beyond 400 Gb/s Ethernet Study Group To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1 To unsubscribe from the STDS-802-3-B400G list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1 |