Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Looking at their email exchange and history of calls they had: they had a number of calls before their first F2F Task Force meeting, during which they reached broad industry consensus which lead to baseline proposal at the first F2F meeting and its approval. I might have phrased the previous email incorrectly Marek From: Marek Hajduczenia [mailto:marek.hajduczenia@xxxxxxxxx] Curtis, I believe this was achieved by offline consensus building, where Task Force was ready to approve the previously agreed baseline at the first F2F meeting … Marek From: Curtis Knittle [mailto:C.Knittle@xxxxxxxxxxxxx] Jorge, Apologies for the delay. Thank you for the suggestions below. In looking through all this information, do you (or anyone else) know how the .3by task force accomplished a “baseline” coincident with the first task force meeting? To follow a similarly aggressive timeline would mean we need “baseline” in January. Curtis From: Salinger, Jorge [mailto:Jorge_Salinger@xxxxxxxxxxxxxxxxx] Curtis, Following up on the discussion after the meeting, I think it would be great if we could start putting together a “project plan” for the Task Force. Marek already started working on something along those lines with one of his contributions (attached). It would be great if we could expand on Marek’s contribution to outline all the areas of the spec that would need to be worked on (I understand some are unknown), put together a tentative plan for required discussions/contributions, and an overall project timeline that would lead us to the following tentative targets and tentative dates:
For reference I attached below the plan for 802.3by (25G Ethernet, which was very aggressive). Hopefully we can do a lot of planning during these weekly meetings that leads us to an approved target timeline during the 1st TF meeting in January and the expeditious development of the standard. Thanks! Jorge From: Curtis Knittle <C.Knittle@xxxxxxxxxxxxx>
|