Re: [802.3_OMEGA] D3.01 comment resolution status

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

Colleagues,

I have drafted new proposed responses to comments in the EZ bucket that have been requested for improvement.

The new text will be presented in brackets in the Proposed Response window during our next comment resolution session for discussion.

I list below the comments with their new text for the Proposed Response:

#i-118:

[PROPOSED ACCEPT IN PRINCIPLE
Page 22 Line 15
Change "for a 10 Gb/s Ethernet full duplex over" to "for a 10 Gb/s full duplex Ethernet over"
Page 22 Line 21
Change "for a 2.5 Gb/s Ethernet full duplex over" to "for a 2.5 Gb/s full duplex Ethernet over"
Page 22 Line 25
Change "for a 25 Gb/s Ethernet full duplex over" to "for a 25 Gb/s full duplex Ethernet over"
Page 22 Line 31

Change "for a 50 Gb/s Ethernet full duplex over" to "for a 50 Gb/s full duplex Ethernet over"]

#i-138:

[PROPOSED ACCEPT]

#i-57:

[PROPOSED ACCEPT IN PRINCIPLE.
Page 63 Line 37
Page 64 Line 38
Page 66 Line 46
Page 66 Line 51
Change "by" to "of"]

#i-62:

No change; first change occurs only once, second change occurs three times.

#i-172

[PROPOSED ACCEPT IN PRINCIPLE
Change
"RS-FEC(544,522) codeword"
to
"RS-FEC(544,522) codeword example"]

Kind Regards,

Luisma

IEEE 802.3cz Chief Editor

El 14/10/2022 a las 23:09, Natalie A Wienckowski escribió:

i-118 also includes "Similarly in 1.4.95a, 1.4.116a and 1.4.165a". This needs to include the specific implementation for each of these as they are not all 10Gb/s.

Natalie Wienckowski

From: ROBERT GROW <bobgrow@xxxxxxx>
Sent: Wednesday, October 12, 2022 12:09 PM
To: STDS-802-3-OMEGA@xxxxxxxxxxxxxxxxx <STDS-802-3-OMEGA@xxxxxxxxxxxxxxxxx>
Subject: [802.3_OMEGA] D3.01 comment resolution status

Colleagues,

We have been making good progress on P802.3cz/D3.01 comment resolution this week. We only have a few comments and the EZ bucket yet to deal with. We have received requests to pull some comments from the EZ bucket for improvement of the responses. Our editor and I would appreciate a notice as soon as possible if there are any other requests to pull comments from the EZ bucket. EZ bucket response improvements suggestions I’ve received so far:

i-118 - As the proposed response contains an "or", I suggest changing "Proposed Accept" to "Proposed Accept in Principle"
i-138 - As the proposed response accepts the change as presented, I suggest changing this to "Proposed Accept"

i-57 - I would recommend repeating the disposition for comment i-140

i-62 - I think there is an extra last line in the Proposed comment resolution that should be removed - Change "codeword CW" to "codeword".

i-172 - As the proposed response contains an "or", I suggest changing "Proposed Accept" to "Proposed Accept in Principle".

There is also the option to reconsider responses adopted in our first two teleconferences.

I hope we can complete comment resolution during our third comment resolution teleconference. When we have responded to all comments, motions will be in order. It will be up to the TF if we recess until the scheduled contingent 18 Oct teleconference before taking final actions actions to adopt responses for inclusion in a D3.1 draft; or if we take those actions during the 13 October (third teleconference). If we adjourn, rather than recess, to conclude the third teleconference, the fourth teleconference will be cancelled.

Robert M. (Bob) Grow
Chair, P802.3cz Multi-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

Luisma Torres Principal Engineer 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 681 29 11 53
E: luismanuel.torres@xxxxxxxxx
W: https://www.kdpof.com