[8023-POEP] Fw: Rejected posting to STDS-802-3-POEP@xxxxxxxxxxxxxxxxx

[Robert E Lounsbury <relounsbury@xxxxxxxxxxxxxxx>]

----- Forwarded by Robert
E Lounsbury/Cleveland/RA/Rockwell on 07/08/2009 06:53 AM -----

"IEEE LISTSERV Server (15.5)" <LISTSERV@xxxxxxxx>

07/08/2009 06:47 AM

To	Bob Lounsbury <relounsbury@xxxxxxxxxxxxxxx>
cc
Subject	Rejected posting to STDS-802-3-POEP@xxxxxxxxxxxxxxxxx

Your posting to the STDS-802-3-POEP list has been
rejected by the content
filter. Your email appears to have unacceptable proprietary claims.

----- Message from Robert E Lounsbury <relounsbury@xxxxxxxxxxxxxxx>
on Wed, 8 Jul 2009 06:47:16 -0400 -----

To:	thompson@xxxxxxxx
cc:	owner-stds-802-3-poep@xxxxxxxx, STDS-802-3-POEP@xxxxxxxxxxxxxxxxx
Subject:	Re: [8023-POEP] Liaison letter from IEC TC65/SC65C/JWG10 - Power over Ethernet performance in industrial environments

Hello All, 
  
 As I read the email thread, I see one consistent theme that tells me that
there is a misconception. Please read the liaison letter and respond to
the questions.  As for the damaged device, you are all making an assumption
that this was incorrectly designed.  I can tell you that it is not,
it fully meets and was certified to the 802.3 specification.  It has
a 150 ohms (75 + 75, Bob Smith Termination) between pairs 12, and 36. This
is NOT in the 19K to 29K range as defined by PoE.  I see a need in
the spec for warnings to designers regarding not having impedances in the
signature range throughout out the specification.  
  
Regards

Rockwell Automation
Bob Lounsbury – Principal Engineer 
   Control and Visualization Business 
   1 Allen-Bradley Drive, Mayfield Heights, OH. 44124
   Tel:    +1.440.646.4297 
   Fax:   +1.440.646.3076 
   Cell:   +1.440.610.4485 
   email: relounsbury@xxxxxxxxxxxxxxx

Geoff Thompson <thompson@xxxxxxxx>
Sent by: owner-stds-802-3-poep@xxxxxxxx

07/07/2009 07:53 PM

Please respond to
thompson@xxxxxxxx

To	STDS-802-3-POEP@xxxxxxxxxxxxxxxxx
cc
Subject	Re: [8023-POEP] Liaison letter from IEC TC65/SC65C/JWG10 - Power over Ethernet performance in industrial environments

Folks-

Dan is correct here.
When we did 802.3af, we were very careful to pick a signature characteristic
that wasn't within the specified or common behavior of UTP applications.
What we didn't (and couldn't) do was pick something that was FORBIDDEN
in each of those applications, especially 802.3 applications.

The piece we missed was we didn't (as a part of 802.3af or .3at) put advisory
or normative text in each of the twisted pair applications within our scope
to advise implementers of those twisted pair applications to avoid anything
within their implementations (with special emphasis on those NOT doing
PoE) to not do anything that would be confused with the detection of a
signature network as specified in clause 33.

I am not as convinced as Dan that "this is
a maintenance issue though, and not an 802.3at issue."
This is all (admittedly arguably) a deficiency of the way we did the original
standard, the enhanced standard has to less of an obligation to "protect
its signaling space" for detection.  I'm willing to cut a little
slack here though as we are so late in the process. On that basis alone,
I am willing to consider doing it in maintenance.

I do feel that we should be able to quickly come up with advisory reference
text to put into the UTP clauses that says something like: 
Note-
Implementers are strongly advised to consider implications of the requirement
for additional components and signal detection in the link segment. Please
see 33.nn 
and that the addition of such non-normative text should not slow down the
progress of P802.3at.

Best regards,

    Geoff

On 7/7/09 2:36 PM, Dove, Daniel wrote: 
All,

I agree with Hugh's general theme, but I still see a need to add language
into the UTP clauses that directs an implementer to avoid a valid PD signature
at the MDI if they are not building a PD. While Hugh is correct that an
Ethernet designer should be aware of the exposure created by failing to
pay attention to clause 33, such changes would eliminate the exposure completely.

Its my opinion this is a maintenance issue though, and not an 802.3at issue.

Dan

-----Original Message-----
From: owner-stds-802-3-poep@xxxxxxxx
[mailto:owner-stds-802-3-poep@xxxxxxxx]
On Behalf Of George Zimmerman
Sent: Tuesday, July 07, 2009 1:45 PM
To: STDS-802-3-POEP@xxxxxxxxxxxxxxxxx
Subject: Re: [8023-POEP] Liaison letter from IEC TC65/SC65C/JWG10 - Power
over Ethernet performance in industrial environments

Hugh - I agree with your well-written response.
-george

-----Original Message-----
From: owner-stds-802-3-poep@xxxxxxxx
[mailto:owner-stds-802-3-poep@xxxxxxxx]
On Behalf Of Hugh Barrass
Sent: Tuesday, July 07, 2009 10:51 AM
To: STDS-802-3-POEP@xxxxxxxxxxxxxxxxx
Subject: Re: [8023-POEP] Liaison letter from IEC TC65/SC65C/JWG10 - Power
over Ethernet performance in industrial environments

David,

I can see that the liaison from IEC has caused some interesting discussion
amongst PoE experts (and myself), however I think that we are

being asked to comment on what may well be design flaws in specific products
and I do not think that is a healthy discussion within 802.3.

I suggest that we should send a reply along the following lines:

==========================================

The problems described in your liaison spurred some vigorous discussion
amongst our task force members regarding possible causes for the damage
that you describe. However the members are not aware of any similar reports
that might indicate a systemic problem with 802.3 compliant equipment.
It is the opinion of the members of IEEE P802.3at Task Force that the standard
allows product manufacturers to build reliable and interoperable equipment
that will meet the requirements for supplying power over Ethernet in many
environments. However, the standard does not

define how a manufacturer must build the product to ensure reliability
or how an installer should ensure that the media is suitable for correct

operation within the standard. We suggest that you should work with the
equipment manufacturers involved to determine whether the failure is the

result of a systemic problem with the standard and whether a specific amendment
may be required.

With respect to the bit error rate performance of 802.3 links when power

is being supplied over the same link, the members of IEEE P802.3at Task
Force believe that a compliant system supplying power over an 802.3 link

will not perturb the channel sufficiently to degrade the performance of
the underlying link. However, it is the responsibility of the product manufacturer
to ensure that noise introduced by the load does not couple

to the link and violate the power over Ethernet specifications or the channel
specifications required for the link. Similarly it is the responsibility
of the system installer that the channel characteristics are met in the
presence of environmental noise.


===========================================

Hugh.

David Law wrote:

  
All,

The IEEE 802.3 Working Group has received a liaison letter from IEC 
TC65/SC65C/JWG10, Industrial process measurement, control and 
automation/Industrial networks with respect to Power over Ethernet 
performance in industrial environments.

I just wanted to inform you that I intend to delegate the generation of
    
a 
  
draft response to the IEEE P802.3at DTE Power Enhancements Task Force 
during the plenary week in July. The draft response will be consider
    
and 
  
then voted upon at the closing IEEE 802.3 Working Group plenary as part
    
of 
  
the IEEE P802.3at closing report. You therefore may wish to review the
letter prior to the meeting, the letter can be accessed at the URL [ 
http://www.ieee802.org/3/minutes/jul09/0709_IEC_SC65C_JWG10_to_802_3.pd
    
f 
  
].

Best regards,
David Law
IEEE 802.3 Working Group Chair