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

[802.3_SPMD] Comment 194

As I’m making my way through the comments, I will use the reflector to discuss things that I don’t think need a whole presentation. Here’s my first one:

 

Comment 194

30

30.17.1.1.3

28

50

T

the aMPSETypeDiscovery enumerated values miss the case where type "mixed" MPDs are discovered…  they just have the case where Both type 0 and type 1 MPDs have been discovered.  This case should also include type "mixed" discovered, as listed in 30.17.2.1.1 (as well as in clause 189)

Change description of "mixed" to read "Type Mixed, or a mixture of MPD Types"

PROPOSED ACCEPT IN PRINCIPLE.



TFTD.



(Editor's note: We need to determine with "Mixed" is a Type, or if it is just that the MPD change types just like the MPSE can change types.)

 

Commentor has a point that mixed is missing from this text, but the remedy doesn’t fix it. The answer is here is that we are misusing mixed in this context. Type0 should mean that the PSE has only discovered type 0 and type mixed MPDs. Similarly type1 means only type 1 and type mixed MPDs are present. Mixed REALLY means I have a mixture of type 1 and type 0, and in this case we don't care it there are any type mixed present. The main point is I have two PD types that are incompatible with interoperation. We should find a new name for mixed here, "blended" is a better description. There could be a fourth case called mixed where it only discovered type mixed MPDs and the PSE can then power as whatever type it is.

 

Regards,

 

Chad Jones

Principal Engineer, Cisco Systems

Executive Secretary, IEEE 802.3 Working Group

Chair, IEEE P802.3da Task Force

Principal, NFPA 70 CMP3

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