Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802.3_SPEP2P] Notes from Val: [802.3_SPEP2P] Announcing 802.3dg Task Force Review Cycle - Draft 1.1



Thanks val.  That sounds like a good plan. 

 

George Zimmerman, Ph.D.

President & Principal

CME Consulting, Inc.

Experts in Advanced PHYsical Communications

george@xxxxxxxxxxxxxxxxxxxx

310-920-3860

 

From: vmaguire@xxxxxxxx <vmaguire@xxxxxxxx>
Sent: Friday, June 6, 2025 3:39 AM
To: George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx>; STDS-802-3-SPEP2P@xxxxxxxxxxxxxxxxx
Cc: Yan Zhuang <zhuangyan.zhuang@xxxxxxxxxx>
Subject: Notes from Val: [802.3_SPEP2P] Announcing 802.3dg Task Force Review Cycle - Draft 1.1

 

Hi George and Yan,

 

Just a couple of notes:

 

  1. I don’t plan on submitting comments this round (I don’t feel I have much to offer towards technical completeness and I’m a little P802.3dg text-blind at the moment!)
  2. I made a comment folder for you (2025_0619_TF d1p1) with the usual inside elements
  3. Please note that I haven’t found a way to edit the Access database from within Google drive (my computer’s security won’t let me open macros from the drive) - I can move it to my desktop, make edits, and then drag it back to get around this

 

TGIF - Val

 

      Valerie Maguire, BSEE

       602-228-7943 mobile

 

 

From: George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, June 5, 2025 12:16 PM
To: STDS-802-3-SPEP2P@xxxxxxxxxxxxxxxxx
Subject: [802.3_SPEP2P] Announcing 802.3dg Task Force Review Cycle - Draft 1.1

 

All – with this email I am announcing that draft 802.3dg D1p1 is released for review.  A compare file to D1p0 is provided.  Both are in the 802.3dg private area.

These drafts incorporate the baselines decided at the May interim, and the comments resolved – with editorial license – as authorized. 

Many thanks to Yan Zhuang and Valerie Maguire for the hard work in putting this together.  You will see a lot of new content and changes went into this draft.

Additionally, thanks to Brian Murray, Philip Curran, and Jacobo Riesco for providing baseline content and guidance on implementing it.

 

As for the review –

We have a comment resolution meeting on June 25. If I give myself minimal time, I need comments by end of day June 19 AoE, and should be able to provide proposed recommendations for review by end of day June 23.  That’s a pretty tight turnaround, so please don’t plan on being late. It gives you 2 full weeks to provide comments, and only 4 days to process all of them (two of which are weekend days).

 

Please submit changes as comments to the draft on review – please use the 802.3 comment form, found at https://www.ieee802.org/3/WG_tools/index.html.  I prefer you use the spreadsheet form if you can.

I am going to suggest that people mark their comments (correction [CORR], editorial [EDIT], or ‘new content’[NEW]), AT THE START of the comment text field

 

Corrections are for things that aren’t aligned with our approved baselines, editorial are for typos, cross references, editing instructions, format, and new content are things that fill in the missing pieces.  Hopefully people will concentrate on new content with next emphasis on corrections, and not focus on pure editorial.  We still have significant work to do to get to Working Group ballot, and once we get there we can still do clean up.  Better to focus on getting to ‘technically complete’.

 

If you need to submit a presentation to explain a complicated change or provide significant text, just summarize the content and state ‘presentation to follow’  if you can give a filename for the presentation it would help (lastname_03dg_0n_06252025.pdf – where “n” is the number of your presentation, either “1” or higher if you are submitting more than one).  Presentations for Comment resolution are due Monday June 23, AoE.

 

If we follow the suggested process above, I think it will help us streamline comment resolution and get to technically complete.  Also note that the markings are in addition to the “Technical” or “Editorial” (or “General”) comment type.  Note that there are no required comments (TR, ER, or GR) in task force review.  All comments will be heard, as they say, no need to shout.

 

Thank you for your participation and the review of the draft. 

 

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.

george@xxxxxxxxxxxxxxxxxxxx

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


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