[802.3_NGAUTO] Update to response for comments 1, 119, & 167

[NATALIE WIENCKOWSKI <NWIENCKOWSKI@xxxxxxx>]

Dear NGAUTO participants,

In implementing the "vendor" comments, I found that the instructions did not include the changes that needed to be made to the "Description" in the tables.  Below describes what I have currently implemented.  Please review and let me know if you see any issues.   The changed text (either new or replacement) is shown in red.

Thanks,

Natalie

In Table 45-3:

Change the name of register 1.2316 to "MultiGBASE-T1 user defined data" in subclause 45.2.1.199

Change the name of register 1.2317 to "MultiGBASE-T1 link partner user defined data" in subclause 45.2.1.200

In 45.2.1.199:

Change the title to "MultiGBASE-T1 user defined data register (Register 1.2316)"

Change the text to: "The assignment of bits for the MultiGBASE-T1 user defined data register is shown in Table 45–155f. The values of the bits in this register are outside the scope of this standard."

In Table 45-155f:

Change the title to: "MultiGBASE-T1 user defined data register bit definitions"

Change the Name to: "MultiGBASE-T1 user defined data"

Change the Description to: "16 bits of vendor specific data that the PHY sends to its link partner"

Delete the last row of the table.

Change footnote a to "R/W = Read/Write"

In 45.2.1.199.1:

Change the title to: "PHY vendor specific data (1.2316.15:0)"

Change text to:  "Bits 1.2316.15:0 contain vendor specific data that the PHY may communicate to its link partner during training."

Delete 45.2.1.199.2

Create a new level 4 subclause:

"45.2.1.200 MultiGBASE-T1 link partner user defined data register (Register 1.2317)" with text:

"The assignment of bits for the MultiGBASE-T1 link partner user defined data register is shown in Table 45–155g. The values of the bits in this register are outside the scope of this standard."

Create Table 45-155g with title "MultiGBASE-T1 link partner user defined data register bit definitions" and a row with Name entry for 1.2317.15:0 is "Link partner PHY vendor specific data", Description is "16 bits of vendor specific data that the PHY may receive from its link partner", R/W is "RO",  and footnote a is "RO = Read only"

Create a new level 5 subclause:

"45.2.1.200.1 Link partner PHY vendor specific data (1.2317.15:0)" with text "Bits 1.2317.15:0 contain vendor specific data that the PHY may receive from its link partner during training."

---

To unsubscribe from the STDS-802-3-NGAUTO list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-NGAUTO&A=1