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

Re: [802.3_ISAAC] revised wording for 98B.4

Scott, I have no issue with your changes. Compatible is probably better than common. Given that we now have complementary phys.
Going offline now

Get Outlook for iOS
From: Scott.Muma@xxxxxxxxxxxxx <Scott.Muma@xxxxxxxxxxxxx>
Sent: Tuesday, 15 September 2026 08:13:17
To: George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx>; STDS-802-3-ISAAC@xxxxxxxxxxxxxxxxx <STDS-802-3-ISAAC@xxxxxxxxxxxxxxxxx>
Subject: RE: revised wording for 98B.4
 

Hi George,

This was related to comment #150. 

 

Thanks for cleaning up the editing instructions.  My concerns with the new version of the paragraph are:

  1. The wording is going back to “common” abilities rather than “compatible” abilities, which differs from the updated text in 98.2.4.2.
  2. It duplicates some of 98.2.4.2 but not completely right, so I would also delete the sentence about resolved ability since there is more to it. 
  3. The second and final sentences are also near duplicate, so one should be removed.

 

Would this work:

 

Since a local device and a link partner may have multiple compatible abilities, a prioritization scheme exists to choose the highest priority compatible (i.e., HCD) technology (see 98.2.4.2). Table 98B–2 specifies the relative priorities of the technologies supported by the IEEE 802.3 Selector Field value. When the Leader PHY and Follower PHY both indicate the Technology Ability present in a given row of Table 98B–2, that is considered a compatible ability.

 

Thanks

Scott

 

From: George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, September 8, 2026 5:59 PM
To: STDS-802-3-ISAAC@xxxxxxxxxxxxxxxxx
Subject: [802.3_ISAAC] revised wording for 98B.4

 

EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe

The following changes the edit to replacing the entire section, removes the 'collided edits' of the first sentence and the paragraph, cleans up language that will get us MEC comments ("ensure"), and tries to make sense of 'common denominator', 'priority', and the number assigned in Table (which is now clearly the priority).

 

<ed instruction> Replace Content of 98B.4 as follows: <end ed instruction>

 

Since a local device and a link partner may have multiple abilities in common, a prioritization scheme exists to choose the highest common denominator (i.e., highest priority) ability.  Table 98B–2 indicates the relative priorities of the technologies  supported by the IEEE 802.3 Selector Field value. The technology with the lowest priority number (i.e., highest priority) is the resolved ability. When the Leader PHY and Follower PHY both indicate the Technology Ability present in a given row of Table 98B–2, that is considered a common ability. Table 98B–2 specifies the relative priorities of the technologies supported by the IEEE 802.3 Selector Field value.

 

<then have Table 98B-2, as in D2p1>

 

George Zimmerman, Ph.D.

President & Principal

CME Consulting, Inc.

Experts in Advanced PHYsical Communications

george@xxxxxxxxxxxxxxxxxxxx

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