Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
(GOT) I was under the impression that 802.3bt allows you to gang
one active endspan PSE (Alt A) plus one active midspan PSE (Alt B) simultaneously to get additional power.
^^^ this is a really bad idea, the IEEE should have nothing to do this type of system
We had lots of discussion about this and frankly I'm not sure where we ended up (Actually, the door is still open on all questions until we establish the scope of Sponsor Ballot).
Whether we sanction it or not, people will do it in the field unless we provide explicit cautions that give them good reason not to (or that is done for us by UL or NEC).
I am happy to join those who would preclude any 802.3 support for such a system. It would certainly makes things simpler.
For my interest in the use of the term "link section" it removes the big ugly complicating case.
LY: This construction with two separate PSEs providing power to a single PD is not supported by the standard. If the PD is a single-signature PD, it will fail detection on the second PSE and remain in 2P mode. A dual-signature PD can get 4-pair power in this particular way, there is also no way to prevent this. While this technique may have been in use in the past to get high power to PDs using only Type 2 PSEs to provide the power, this isn't something that would have any use going forward with the availability of 4-pair PSEs. Lennart
From: Geoff Thompson <thompson@xxxxxxxx>
Sent: Monday, May 15, 2017 19:34 To: STDS-802-3-4PPOE@xxxxxxxxxxxxxxxxx Subject: Re: [802.3_4PPOE] Link section vs "channel" and link segment Heath-
I am all in favor of getting this fully defined dow to the last knat.
My current thought is that it should mean a PSE sourcing power and/or a PD sinking power supplied by a PSE.
A PSE that is in standby and/or searching is not "active".
We could make it more precise by specifically limiting to an explicitly defined set of state machine states
see above.
Not if we limit the definition in the standard. If they go outside or beyond what we define then I guess they would be in "proprietary active" land.
We had lots of discussion about this and frankly I'm not sure where we ended up (Actually, the door is still open on all questions until we establish the scope of Sponsor Ballot).
Whether we sanction it or not, people will do it in the field unless we provide explicit cautions that give them good reason not to (or that is done for us by UL or NEC).
I am happy to join those who would preclude any 802.3 support for such a system. It would certainly makes things simpler.
For my interest in the use of the term "link section" it removes the big ugly complicating case.
Geoff
|