Hi Natalie,
If you like to put #184 and #185 back into EZ bucket, I have no objection.
Thanks,
William
From: Natalie Wienckowski <natalie@xxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, July 7, 2026 12:19 PM
To: William Lo <will@xxxxxxxxxx>
Cc: STDS-802-3-ISAAC@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_ISAAC] IEEE P802p3dm D2p0 proposed responses available on website
The responses for #184 and #185 do not need to be updated. The response to #113 needs to be updated.
Updated comment #113 response:
PROPOSED ACCEPT IN PRINCIPLE.
Add new paragraph on P115L47
The InterleaverDepth request the PHY sends to its link partner is bits 1.2311:12:11 (see 45.2.1.244.1). The InterleaverDepth request reported by the link partner is bits 1.2312:12:11 (see 45.2.1.245.1).
When bit 1.2311.5 (see 45.2.1.244.2) is set to one, the PrecodeSel request is set in bits 1.2311.3:2 (see 45.2.1.244.4); otherwise, the PHY determines the precoder setting. The actual setting transmitted is reflected in bit 1.2310.4:3 (see 45.2.1.243.5).
The received PrecodeSel request is reported in bit 1.2312.3:2 (see 45.2.1.245.3) by the link partner.
In 45.2.1.244.3 Change: specified in 149.4.2.4.5.
To: specified in 149.4.2.4.5 and 191.5.2.5.4.
In 45.2.1.244.4 Change: (see 149.4.2.4.5)
To: (see 149.4.2.4.5 and 191.5.2.5.4)
See my responses below on each variable you asked about.
In-Vehicle Networking Solutions LLC
IEEE P802.3dm Chair and Chief Editor
Hi Natalie,
For comments #184 and #185 you are covering
1.2311.12:11 and
1.2312.12:11
I get that part. What I am unsure is if you did this would you also have to do
1.2311.1 This does not have a reference in Clause 45 to 149, so nothing needs to be added.
1.2311.3:2 This does have a reference in Clause 45 to 149. I'll update the response for #113.
1.2311.5 This does have a reference in Clause 45 to 149. I'll update the response for #113.
1.2312.1 This does not have a reference in Clause 45 to 149, so nothing needs to be added.
1.2312.3:2 This does have a reference in Clause 45 to 149. I'll update the response for #113.
1.2316.15:0 This does not have a reference in Clause 45 to 149, so nothing needs to be added.
1.2317.15:0 This does not have a reference in Clause 45 to 149, so nothing needs to be added.
All these registers I pointed out in comments #112 and #113.
Thanks,
William
184 specifically says 45.2.244.1 which is Interleave request (1.2311.12:11) which references 149.4.2.4.5. We need to add a reference to 191.
185 specifically says 45.2.245.1 which is Interleave request (1.2311.12:11) which references 149.3.2.2.15 and 149.4.2.4.5. We need to add a reference to 191.
186 is for 45.2.1.246 MultiGBASE-T1 test mode control register (1.2313) All subsections that have a reference to 149, that apply to 191, need to be brought in with the appropriate
references.
Please let me know if you have additional questions.
In-Vehicle Networking Solutions LLC
IEEE P802.3dm Chair and Chief Editor
Hi Natalie,
I found issues with the following in the EZ bucket. Please pull.
All -
In the interest of time please see the last column in the table below as to the issues I see so we are prepared to discuss them.
|
CommentID
|
CommenterName
|
CommenterCo
|
Clause
|
Subclause
|
Page
|
Line
|
CommentType
|
Comment
|
SuggestedRemedy
|
Response
|
Topic
|
Why remove from EZ
|
|
184
|
Wienckowski, Natalie
|
IVN Solutions LLC; Ethernovia & Bosch
|
45
|
45.2.1.244.1
|
40
|
51
|
T
|
missing register that needs to be updated for 191
|
Bring in this section from 802.3, as modified by 802.3cy and add references to 191.3.2.2.14, 191.5.2.4.5
and 191.5.2.5.4, with editorial license.
|
PROPOSED ACCEPT.
|
EZ
|
What exactly are we bringing in?
|
|
185
|
Wienckowski, Natalie
|
IVN Solutions LLC; Ethernovia & Bosch
|
45
|
45.2.1.245.1
|
40
|
51
|
T
|
missing register that needs to be updated for 191
|
Bring in this section from 802.3, as modified by 802.3cy and add references to 191.3.2.2.14, 191.5.2.4.5
and 191.5.2.5.4 , with editorial license.
|
PROPOSED ACCEPT.
|
EZ
|
What exactly are we bringing in?
|
|
186
|
Wienckowski, Natalie
|
IVN Solutions LLC; Ethernovia & Bosch
|
45
|
45.2.1.246
|
40
|
51
|
T
|
missing register that needs to be updated for 191
|
Bring in this section from 802.3, as modified by 802.3cy and add appropriate references, with editorial
license.
|
PROPOSED ACCEPT.
|
EZ
|
What exactly are we bringing in?
|
|
78
|
Ran, Adee
|
Cisco Systems
|
191
|
191.1.2
|
59
|
15
|
T
|
The right side of Figure 191-2 shows the -V1 stack with an AN block, referred to as optional, and the
text above the figure points to clause 98 for the whole family (including -V1). Also in 191.1.3 AN is mentioned for both T1 and V1, and there are numerous other mentions of AN in the clause.
However, in 191.8.1 it is stated that -V1 PHYs do not support AN.
|
Delete the AN block from the right-hand stack and delete the -V1 family from references to AN.
Conside how to clarify that AN is not supported (even as an option) in -V1, in the other mentions of AN.
|
PROPOSED ACCEPT IN PRINCIPLE.
See #158 which deletes the text in question.
|
EZ
|
Propose Reject
Do not change the diagrams because V1 is supporting AN.
|
|
285
|
van Dyck, Peter
|
Infineon
|
191
|
191.3.2.2
|
79
|
31
|
E
|
Figure 191-11: For 10G, a RS-FEC superframe always has L x 1800 PAM4 symbols. A Training frame always
has 7200 PAM2 symbols. The training frame symbols match the data path symbols for a case with L=4
|
Replace:
RS-FEC superframe (L × 1800 × u symbols)
With:
RS-FEC superframe (L × 1800 symbols) / Training Frame (u x 1800 symbols)
Replace:
For PAM2 path, V=2 and u=2
With:
For PAM2 path, V=2 and u=4
|
PROPOSED ACCEPT.
|
EZ
|
Propose Reject:
The remedy is not correct.
Expanding this out all the cases
10G, L = 1 1800 symbols
10G, L = 2, 3600 symbols
10G, L = 4, 7200 symbols
5G, L = 1, 3600 symbols
5G, L = 2, 7200 symbols
2.5G, L = 1, 3600 symbols
So the current text is correct
RS-FEC superframe (L × 1800 × u symbols)
The training frame is always 7200 symbols
. There is no need to state it here since it is claer from figures 191-15 and 191-16
|
|
286
|
van Dyck, Peter
|
Infineon
|
191
|
191.3.2.2
|
80
|
29
|
E
|
Figure 191-12: For 2.5G and 5G, a RS-FEC superframe always has L x 3600 PAM2 symbols. A Training frame
always has 7200 PAM2 symbols. The training frame symbols match the data path symbols for a case with L=2
|
Replace:
RS-FEC superframe (L × 1800 × u symbols)
With:
RS-FEC superframe (L × 3600 symbols) / Training Frame (7200 symbols)
Replace:
For PAM2 path, V=2 and u=2
With:
For RS-FEC Frame u=1. For Training Frame u=2.
Replace:
PAMVu x 1800-1
With:
PAM2u x 3600-1
|
PROPOSED ACCEPT.
|
EZ
|
Propose Reject:
The remedy is not correct.
Expanding this out all the cases
10G, L = 1 1800 symbols
10G, L = 2, 3600 symbols
10G, L = 4, 7200 symbols
5G, L = 1, 3600 symbols
5G, L = 2, 7200 symbols
2.5G, L = 1, 3600 symbols
So the current text is correct
RS-FEC superframe (L × 1800 × u symbols)
The training frame is always 7200 symbols
. There is no need to state it here since it is claer from figures 191-15 and 191-16
|
|
287
|
van Dyck, Peter
|
Infineon
|
191
|
191.3.2.2
|
81
|
43
|
E
|
Figure 191-13: Same as comment for Figure 191-11
|
Replace:
For PAM2 path, V=2 and u=2
With:
For PAM2 path, V=2 and u=4
|
PROPOSED ACCEPT.
|
EZ
|
Propose Reject:
The remedy is not correct.
Expanding this out all the cases
10G, L = 1 1800 symbols
10G, L = 2, 3600 symbols
10G, L = 4, 7200 symbols
5G, L = 1, 3600 symbols
5G, L = 2, 7200 symbols
2.5G, L = 1, 3600 symbols
So the current text is correct
RS-FEC superframe (L × 1800 × u symbols)
The training frame is always 7200 symbols
. There is no need to state it here since it is claer from figures 191-15 and 191-16
|
|
288
|
van Dyck, Peter
|
Infineon
|
191
|
191.3.2.2
|
82
|
43
|
E
|
Figure 191-14: Same as comment for Figure 191-12
|
Replace:
For PAM2 path, V=2 and u=2. For PAM4 path, V=4 and u=1.
With:
For RS-FEC Frame u=1. For Training Frame u=2.
Replace:
rx_PAMVn+(u x 1800-1)
With:
rx_PAM2n+(u x 3600-1)
|
PROPOSED ACCEPT.
|
EZ
|
Propose Reject:
The remedy is not correct.
Expanding this out all the cases
10G, L = 1 1800 symbols
10G, L = 2, 3600 symbols
10G, L = 4, 7200 symbols
5G, L = 1, 3600 symbols
5G, L = 2, 7200 symbols
2.5G, L = 1, 3600 symbols
So the current text is correct
RS-FEC superframe (L × 1800 × u symbols)
The training frame is always 7200 symbols
. There is no need to state it here since it is claer from figures 191-15 and 191-16
|
|
113
|
Lo, Willliam
|
Axonne Inc.
|
191
|
191.5.2.5.4
|
115
|
52
|
TR
|
Various capabilities are defined but not mapped to a register.
|
The InterleaverDepth request is set in bits 1.2311.12:11.
The received InterleaverDepth request is reported in bit 1.2312.12:11 of the link partner.
When bit 1.2311.5 is set to 1, the PrecodeSel request is set in bits 1.2311.3:2, otherwise the PHY determines the precoder setting. The actual setting transmitted is reflected in bit 1.2310.4:3.
The received PrecodeSel request is reported in bit 1.2312.3:2 of the link partner
The OAMen is advertised in bit 1.2311.1.
The advertised status is reported in bit 1.2312.1 of the link partner.
The VendorSpecificData to send is set via bits 1.2316:15:0 and received on the link partner bits 1.2317:15:0.
|
PROPOSED ACCEPT IN PRINCIPLE.
Add new paragraph on P115L47
The InterleaverDepth request the PHY sends to its link parter is bits 1.2311:12:11 (see 45.2.1.244.1). The InterleaverDepth request reported by the link partner is bits 1.2312:12:11 (see 45.2.1.245.1).
When bit 1.2311.5 (see 45.2.1.244.2) is set to one, the PrecodeSel request is set in bits 1.2311.3:2 (see 45.2.1.244.4); otherwise, the PHY determines the precoder setting. The actual setting transmitted is reflected in bit 1.2310.4:3 (see 45.2.1.243.5).
The received PrecodeSel request is reported in bit 1.2312.3:2 (see 45.2.1.245.3) by the link partner.
|
EZ
|
Incomplete implementation
1.2311.1 and 1.2317.15:0 not implemented
|
|
47
|
Muma, Scott
|
Microchip
|
191
|
191.5.2.6
|
116
|
38
|
E
|
The literal number would be more clear than an equation in this table
|
Change 20 - 0.384 to 19.616
|
PROPOSED ACCEPT.
|
EZ
|
Task force to discuss
I think the intent is to show a relatioship between the 20 and 0.384. Merging this into one number may mess with this intent.
|
|
48
|
Muma, Scott
|
Microchip
|
191
|
191.5.2.6
|
117
|
6
|
E
|
The literal number would be more clear than an equation in this table
|
Change 20 - 0.384 to 19.616
|
PROPOSED ACCEPT.
|
EZ
|
Task force to discuss
I think the intent is to show a relatioship between the 20 and 0.384. Merging this into one number may mess with this intent.
|
Thanks,
William
Proposed responses for all 519 comments received, including the 25 late comments, have been loaded to our website.
You will find a pdf sorted by clause/subclause, an Excel file sorted by page/line, and an EZ bucket pdf. The EZ bucket includes comments that were received late and deemed EZ.
Please note - some comments are marked as "WITHDRAWN" as I received an email from the commenter that they would like to withdraw their comment.
Please send all requests to remove comments from the EZ bucket by July 5th AOE.
Agenda for July 9th call:
Motion to include "late" comments.
Confirmation of comments to remove from the EZ bucket.
Motion to approve remaining comments in the EZ bucket.
Review of comments that may need consensus prior to the Plenary.
Comment resolution of requested comments.
General comment resolution.
If there are specific comments you would like to review during this meeting because you won't be at the Plenary or will be in other TF meetings, please let me know and we can look
at these on July 9th.
I also uploaded additional files to support comments. These can be found on the
July Plenary meeting page.
In-Vehicle Networking Solutions LLC
IEEE P802.3dm Chair and Chief Editor
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
|