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

[802.3_NGAUTO] P802.3ch D0.5 Task Force review closes September 2 2018 AOE



Per our work plan from July, Draft 0.5 is ready for our first task force review.  Please review the draft and provide comments to our Chief Editor, Natalie Wienckowski, at nwienckowski@xxxxxxx.  The review of  D0.5 will close on September 2, 2018 AOE (anywhere on earth).  This is one week before our next Interim meeting which starts on September 10th.  The Chief Editor expects to have the comment database, with proposed resolutions, ready by September 6 AOE.  You can help to make this happen by sending your comments as early as possible as there are only 3 days to provide responses to the comments.


The draft can be found in the 802.3ch private area at:  If you need the password (and are participating in the standards process – getting this email by the reflector is evidence of that), then email me and I will make sure you get it.



Comments should be submitted either by the FileMaker comment tool or the spreadsheet tool.  They are available at   Manual comments are discouraged and may not be included in the comment database prior to the September 10th meeting. I personally prefer the spreadsheet as it is easier to use, you can see all of your comments at once, and you don’t need to install anything on your PC.

As you can see, we still have many sections that need content.  The Chief Editor has tried to mark all of these with an Editor's Note box and/or yellow highlighted text.  Please plan to create comments for the missing content and a presentation related to this to be given at an upcoming AdHoc call or the September Interim.  

Here's some excellent information and tips on being an effective commenter, courtesy of P802.3cg:

Below are some important FAQs and guidelines:

Who can review the draft – Anyone.  Participation is by individual basis.

Scope of the review: The ENTIRE draft is in scope.

Good commenting guidelines: See  where there are lots of good information.  It is most helpful if you:

  • Quote the offending text (or enough of it for us to find) in your comment, AND, say what the problem is.  Any explanation should go in the comment.
  • Give a specific change to the text in the proposed response.  Try not to say more than just what needs to be done.  If there is more than one possibility, give both and briefly say what makes the determination in your mind (for example, “if the proposed functionality is supposed to be P, then change “y” to “z”.  if the proposed functionality was supposed to be Q, then change “y” to “x”.  If you need formatting or graphics, then put them in another file (text – word or PDF, or powerpoint).  Remember, equations, italics, etc. don’t come through in the comment tool.  If you need a presentation to explain and present the solution, please flag that and give it a name in the proposed response – BUT, give your editors an idea of what you will be proposing.
  • Please focus on the technical completeness of our draft.  While pointing out obvious typos or errors is useful, editorially rewording text takes valuable task force time and likely will just get reworded again during working group ballot.  A useful rule is – if you can clearly understand what is meant, then others can too, but if there are 2 or more interpretations and you need ‘inside knowledge’ or have to guess to figure out what is meant, please go ahead and comment.
  • If you think there is an issue to discuss, flag that (in addition to providing your proposed resolution).  That will be a cue to your editors not to mark the comment “EZ”.

Voting and “Required” comments:  Task Force review is informal, there is no ballot or vote.  Therefore, there is NO POINT in marking your comments “required” or not.  They will all be considered equally and all comments are non-binding.  Comments are either Editorial (E),  Technical (T) or General (G) and it is up to the commenter to determine the comment type.

Thanks to everyone who contributed text and input to D0.5, and a special thanks to our Chief Editor, Natalie Wienckowski, for getting the draft ready on time.




Steven B. Carlson

Chair, P802.3ch Multi-Gig Automotive Ethernet PHY Task Force

Executive Secretary, IEEE 802.3 Ethernet Working Group
High Speed Design, Inc.

Portland, OR




To unsubscribe from the STDS-802-3-NGAUTO list, click the following link: