| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
All – I look forward to making more progress on 802.3dg at the upcoming plenary meeting in Atlanta. Remember you need to register & pay the fee, whether you are there in-person or remote. 802.3dg will be meeting Wednesday afternoon (US Eastern Time) and Thursday morning.
Our main order of business is to progress the draft. Seeing where we are, I think we should be able to enter formal task force review coming out of this meeting. When we do that, some things will change. We can, of course, still hear presentations on concepts and focused on the key technical decisions, but our discussions, focus, and work product will increasingly focus on draft text for the standard.
Remember, we are here to produce a document, so text matters. Please let me know if you are making a contribution by MONDAY MARCH 3 and submit the presentation by WEDNESDAY MARCH 5, 2025, AoE. This way people can download and review before the meeting series starts. I want to prepare you for what comes next. If you are preparing a contribution with new technical content to be adopted, please consider also providing text that reflects it. You may provide that text after the fact – which is good if you want the group’s help refining something
– but please be prepared to provide it within about 2 weeks of the meeting. That way our editors have time to incorporate it in the draft. Figures don’t need to be clean and pretty – just understandable enough to be redrawn in frame. (if they are clean
and pretty, that’s nice too, because we won’t need to redraw them just yet and can paste in an image for the first review). We generally prefer a word-format for new text and have incorporated that.
Brian, Philip, and Jacobo have contributed text from the decisions last meeting (and some before) which Yan, Val, and (to a lesser extent) I are working to incorporate into the draft. At this point the task force has not yet formally accepted the draft text in 0.1 or 0.2 as baseline, nor have they formally accepted the draft text that Brian and colleagues have submitted – but we HAVE made the decisions. Our first job
is to accept the text that the editors are currently incorporating as representing those decisions. It doesn’t mean it is perfect. It will be commented on, both in task force review and in ballot cycles, and it will get changed, cleaned up, and aligned.
However, we need to review and note that it represents the decision made thus far. Those decisions can be found in the ‘baselines’ files on the top-level of the 802.3dg website. If you think I may have missed a baseline decision, please let me know, along
with the meeting at which you think the motion was made. I would VERY much like to be ready to have a motion in March to accept the text in the upcoming draft (0.3) as the basis for draft 1.0 – even if the motion includes “with editor’s notes marking sections x.y.z., a.b.c., and p.d.q. as unaccepted
draft text for review.” Once we do that, we can start formally reviewing, commenting and changing the draft text – as well as filling out the remaining technical decisions to get our draft to WG ballot. After March, if you are commenting on the text, I would prefer to use the comment tool. If you are adding new content altogether, you are free to continue with free-form presentations. My experience has been that general technical issues
are better explained first rather than dealt with in textual comments at this stage. That too will change, but probably not for a cycle or two. George A. Zimmerman, Ph.D. Chair, IEEE P802.3dg 100BASE-T1L Task Force 2nd Vice Chair, IEEE 802 LAN/MAN Standards Committee CME Consulting, Inc. 1-310-920-3860 To unsubscribe from the STDS-802-3-SPEP2P list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-SPEP2P&A=1 |