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

Re: [8023-POEP] Fwd: Open_for_ballot:_Project_Number_3-0324-B-1, proposed_cre...



Chris-

I can live with your suggestion.
I agree that it might be easier for TIA to swallow than my wording.

Thanks
Geoff


At 03:22 PM 3/10/2009 , CDimi80749@xxxxxxx wrote:


I agree that P802.3at should send a liaison letter to TIA regarding TSB-184
regarding the technical changes in the default ballot to section 5 cabling selection (copied below).

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Technical change in default ballot:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Changed from: Remote powering should be implemented using 4-pair balanced cabling.

 To: Remote powering should be implemented using category 5e or
better 4-pair balanced twisted-pair cabling as specified in ANSI/TIA-568-
C.2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The new language can be easily interpreted  as a conflict between TIA-184 and 802.3at as it states "how remote powering should be implemented'. The previous TSB-184 text also included suggestions on remote powering implementation but was less objectionable as it aligned with 802.3at.

Recommendation to include in liaison:

TSB-184 states  "...It is intended to guide new installations and renovations."; this statement is buried in the introduction. Therefore, I'd advise the following change to TSB-184 be requested in the liaison letter to avoid ambiguity and potential conflicts between 802.3at and TSB-184.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Change from: Remote powering should be implemented using category 5e or
better 4-pair balanced twisted-pair cabling as specified in ANSI/TIA-568-
C.2 

To: When planning new installations delivering SELV power, Category 5e or
better 4-pair balanced twisted-pair cabling as specified in ANSI/TIA-568-
C.2 is recommended.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Regards,

Chris DiMinico
MC Communications
cdiminico@xxxxxxxx