Vport comment bucket v2

Frs

Description

Vport ad hoc D1.0 Vport related comment resolutionJanuary 2008Joseph Maggiolino BroadcomAnoop Vetteth Cisco SystemsKeith Hopwood PhihongBill Delveaux Cisco SystemsKest Gue ?Chad Jones Cisco SystemsKirk Hayden Akros SiliconChristian Beia STLarry Shorthill NXPChristophe Gouwy AMI SemiconductorMartin Patoka Texas InstrumentsClay Stanford Linear TechnologyMatthew Landry Silicon LabsDavid Law 3COMPeter Johnson SIFOSEran Bello MicrosemiRamesh Sastry Cisco SystemsFred Schindler Cisco SystemsFred SchindlerRandy Rannow Tyco ElectronicsGeoff Thompson Nortel NetworksRiccardo Russo ST MicroelectronicsGeoff Thompson Nortel NetworksRick Frosch PhihongCisco Systems Gianluca Sanita Nokia Siemens NNetworksTamir Reshef MicrosemiHugh Barrass Cisco SystemsYair Darshan MicrosemiJohn Jetzt AvayaYasuki Kawatsu Hitachi Cable3 ad hocs with an average attendance of 16 people since the last IEEE meeting. 1Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon, v1Agenda• Principles based comment resolution• Comment Clusters• Recommendations for the Vport-comment bucket.2Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, OregonPrinciples to use• Develop some principles to use to guide the ad hoc during comment resolution.Use concise textFocus on what operation you want doneCover only compliance (i.e., avoid discussing noncompliance devices)Do not repeat requirementsChange as little as possible when improving textTry to ...

Informations

• Publié par: Soim
• Nombre de lectures: 46
• Langue: English

Extrait

Vport ad hoc D1.0 Vport related comment resolution

January 2008

Fred Schindler Cisco Systems

Anoop Vetteth Cisco Systems Bill Delveaux Cisco Systems Chad Jones Cisco Systems Christian Beia ST Christophe Gouwy AMI Semiconductor Clay Stanford Linear Technology David Law 3COM Eran Bello Microsemi Fred Schindler Cisco Systems Geoff Thompson Nortel Networks Geoff Thompson Nortel Networks Gianluca Sanita Nokia Siemens NNetworks Hugh Barrass Cisco Systems John Jetzt Avaya

Joseph Maggiolino Broadcom Keith Hopwood Phihong Kest Gue ? Kirk Hayden Akros Silicon Larry Shorthill NXP Martin Patoka Texas Instruments Matthew Landry Silicon Labs Peter Johnson SIFOS Ramesh Sastry Cisco Systems Randy Rannow Tyco Electronics Riccardo Russo ST Microelectronics Rick Frosch Phihong Tamir Reshef Microsemi Yair Darshan Microsemi Yasuki Kawatsu Hitachi Cable

3 ad hocs with an average attendance of 16 people since the last IEEE meeting.

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon, v1

1

Agenda

•

•

•

Principles based comment resolution

Comment Clusters

Recommendations for the Vport-comment bucket.

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

2

Principles to use

me use to guide the ad hoc during •p o r n i . nciples to ne tocm e m De u v li o t l  e p r o o s s Use concise text Focus on what operation you want done Cover only compliance (i.e., avoid discussing noncompliance devices) Do not repeat requirements Change as little as possible when improving text rain from re e once it has been r T e r s y  o t l o v   e re d f . pat the same issue  Ensure that legacy devices are compliant.

Consider simplify requirements into logic statements to help support the above principles.

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

3

Comment Clusters

•2PSE current limit curve:81, 132

•3Vport turn off and transient:246, 247,135, 80

•4Definitions:118, 34, 32, 260

•16Matching PSE and PD currents:137, 114, 227, 79, 56, 249, 36, 105, 143, 33, 59, 165, 94, 90, 9, 95

Comments inredare related but are not part of this bucket.

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

4

Cluster: PSE current limit curve

•

3 PSE current limit curve: 81, 9, 132

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

5

Comment 81

Min.

This says Iport_max > Icable, Icable m This says Iport <= 820 mA, for t > 75 m

Both of these statements are true.

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

This is suppose to be: 400/350Pport/Vport see fig. 33-12b

6

Comment 81 Resolution

•

Recommend Correcting figure 33-9a, and generically using Icable for type 1 and 2 PSEs in table 33-5.

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

7

Pro

Comment 132

osed Resolution:

at least 15 mA/us

of up to 35 mA/us

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

8

Cluster: Vport turn off and transient

•

3 Vport turn off and transient: 246, 247,135, 80

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

9

Comment 246

This describes what to do for a noncompliant device.

A PSE meeting all the requirements of this standard except Vport is not attached to a PD and may remove the port power. This may be resolved by 135. This same statement was covered during the Richfield Vport ad hoc comment resolution. This is related to comments 247, 135, and 80.

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

10

Simplified view of the problem

Requirement A: Provide Vport for all valid PD loads. Nuance i: Iport <= Pport/Vport, (average PD demand) Nuance ii: Iport <= Ipeak, for TLIM, 5% duty (peak PD demand) Nuance iii: Remove power before exceeding SOA Passing the PICS ensures equipment is compliant. Allowance B: You may remove power if Vport is out of spec. i based on design Allo r w e a q n ui c r e e  B m , e  l n e t t s s .  you implement A-ii your  Power Valid = I & II Power removed = III

Vport ad hoc IEEE 802.3at Task Force, January 2008, Portland, Oregon

11