|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
I would also agree with Bruce that a PSE denying power to a port is not necessarily a fault condition. If there was a PD fault then the PSE would not be granting power. The PSE choosing to not provide power is a system decision that is likely not a fault at all.
I would suggest that you assume that POWER_DENIED is NOT a fault in the interest of expedience. I’d rather have you do it once than twice.
I would like to hear more opinions as this is a group decision. Please respond to this thread with a simple “IS A FAULT” or “IS NOT A FAULT” and we can do an informal (and certainly not binding) ‘opinion of the reflector' poll.
MGR, HW ENG, Cisco Systems
Chair, IEEE P802.3bt 4PPoE Task Force
From: Dan Dove <dan.dove@xxxxxxxxxxxxxxxxxx>
Organization: Dove Networking Solutions
Reply-To: Dan Dove <dan.dove@xxxxxxxxxxxxxxxxxx>
Date: Wednesday, February 11, 2015 at 3:26 PM
To: 4PPOE Reflector <STDS-802-3-4PPOE@xxxxxxxxxxxxxxxxx>
Subject: Re: [802.3_4PPOE] POWER_DENIED
Agreed. I think your point below is exactly the logic and reasoning most people will have.
The question I pose, is that if you go to a candy machine with due number of coins, and it doesn't have the choice you want, do you consider that a fault?
If you are a candy machine mechanic, no..you just order a restock for it. If you are a customer, you go back to the conference room and tell everyone "that *#(! candy machine doesn't have my candy!" and while it may be the candy-stocker's fault, its clearly a fault in their eyes.
All humor aside, the language in the text is ambiguous and we probably want to straighten it out. Fixing the state diagram will be relatively easy once we hash through the text. Its only a question of which hierarchical block the state resides within the diagram.
Dan DoveOn 2/11/15 11:16 AM, Bruce Nordman wrote:
Dove Networking Solutions
530-906-3683 - Mobile