| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Definitely Pull: 1, 210, 191, 192, and 124
Possibly pull 152, 1, 240, and 241 (if Editor is good with these being handlable under editorial license, I’m fine with it too, and we don’t need to pull them)
See notes below
-george
Comment 152:
The response has several typos. If these are within editorial license, we can leave it in, but just to note the proposed text has the following typos (fuction should be function and controls should be control).
Comment 1:
Since, as the editor has pointed out, there was a prior change (in 802.df) to 8 bits for the PMA/PMD type selection, the 802.3dm text should not show a change in the “Bits” column. Additionally, the table was modified by 802.3dk-2026 – which should be added to the editing instruction. This comment should be used to correct those errors in the draft. – PULL.
Comment 210: Pull. – the usage is to have underscores when you are referring to a variable name (including signals, messages, etc.), but not when it is plain English. The text at line 22 that is being changed is not speaking to the variable, but rather just to plain English. “It obtains block lock to PHY frames…” is correct. It is the text at line 27 (which is parallel) that should be changed “It obtains block_lock to the PHY frames” to omit the underscore.
Comment 240 & 241: even these are only spaces, the responses needs to be harmonized to 235. – this may be doable in editorial license.
Pull 191 & 192 – these have TFTF (which I assume is supposed to be TFTD?) - they’ can’t be EZ…. There is a decision and discussion to occur, and this is a technical change.
Pull 124 – “ensure” is a reserved word for IEEE SA mandatory editorial coordination, to be avoided. Let’s fix this right by rewording now. There are many possible decent substitutes, and we all agree “insure” is wrong. Going with a one-word change is probably best – Suggest, change “insure” to “establish”: “To establish a consistent methodology on measuring the delays is used by all implementations, the following points in the data stream are used.”
--- I’ll probably have more later, I’ve only gotten to page 20 and am going to enjoy some of my sunday
George Zimmerman, Ph.D.
President & Principal
CME Consulting, Inc.
Experts in Advanced PHYsical Communications
310-920-3860
To unsubscribe from the STDS-802-3-ISAAC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-ISAAC&A=1
To unsubscribe from the STDS-802-3-ISAAC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-ISAAC&A=1