| Bob,
Let me give feedback on my comments.
#73— I meant carriage return (CR) is not needed because next paragraph is about the same thing. I used period to indicate point w/o CR and full stop to indicate point with CR. I am sorry for the confusion. Lesson learnt.
I think response to #73 should be AIP, remove carriage return from line 25.
#125— Same word “code” is used in other clauses, e.g. 55, 149, 113, etc. This comment is to change the reference number, because full 64B/65B encoding process is specified in current 166.2.5, and 166.2.5.4 only specifies one part, i.e. the control codes. Considering the document layout of D1.2, probably the most suitable word would be “process” instead of “code”. In the response to my comment #92, which I agree, the new reference is proposed to be changed to "166.2.2.8 PCS 64B/65B encoding", because title is more accurate to reflect the content of that section. Taking this into account, I think words “code” or “encoding” would be the most appropriate.
I think response to #125 should be AIP, doing reference to #92 to indicate new reference according to new layout. A valid response would be "The DECODE function shall decode the rx_block as specified in 166.2.2.8 (reference per #92 new PCS layout)”. In this way, “code” is not used and specification is still correct.
CTO at KDPOF_____________________________________________________________
Knowledge Development for POF, S.L.A: Ronda de Poniente 14 2º CD, 28760, Tres Cantos (Madrid), Spain P: +34 91 804 33 87 Ext:110 M: +34 689 319 866 I: Subscribe our quarterly Automotive Update for regular news and technology insights.
Colleagues, In response to our Chief Editor’s request, here are some proposed comments in the Text Improvement and EZ buckets I believe need to be improved and consequently ask they be discussed. EZ topic/bucket (please remove from bucket) #4 (also 5) — I think the text can be improved and would recommend an Accept in Principle: "The protocol number and the content of TXO_DATA2 through TXO_DATA8 are vendor specific and shall be specified by the assignee of the OUI or CID.” #11 — I agree with the comment and suggest it be an Accept. (Saying 2 to 8 is ambiguous as to some, “to” indicates that 8 is not included, and to others, it is included where through more clearly includes 8.) Text Improvement (please remove from the bucket) #1 (also 8) — Number base does need to be clear. I'd prefer using the 0bXXXX convention as used in Clauses 37 and 102. (Unfortunately I didn't submit a comment on P802.3 to add binary number conventions after 1.2.5.) #73 — I don’t understand the comment and therefore can’t currently support an Accept as I don’t know what change is to be made. I understand full stop and period to be synonyms (UK versus US English). #125 — The text “based on code specified" might violate IEEE requirements as it seems to specify use of a specific tool. I'll have to think about this more. —Bob On Jan 4, 2022, at 3:36 AM, Luis Manuel Torres <luismanuel.torres@xxxxxxxxx> wrote:
Colleagues,
The comments received on P802.3cz/D1.2 with proposed responses have been posted to our Task Force web pages (https://www.ieee802.org/3/cz/comments/index.html).
I have classified them into different "buckets" to facilitate our discussions. The Chief Editor's Report posted in our website includes the plan for considering these comments, and explanations for the dispositions of some “buckets" of comments as groups.
Please review the comment responses prior to our meeting next week. Suggestions in responses to comments will be appreciated, and unless TF discussion is requested, the comment responses in the Text Improvement and EZ buckets will be approved without discussion.
Thanks to all the commenters!
Kind Regards,
Luis Manuel (Luisma) Torres
Chief Editor, P802.3cz Gigabit Optical Automotive Ethernet (OMEGA) Task Force
________________________________________________________________________
To unsubscribe from the STDS-802-3-OMEGA list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-OMEGA&A=1
________________________________________________________________________ To unsubscribe from the STDS-802-3-OMEGA list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-OMEGA&A=1
To unsubscribe from the STDS-802-3-OMEGA list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-OMEGA&A=1
|