Re: [8023-POEP] IEEE 802.3at Vport ad hoc, Oct. 11 meeting materials
Hi Fred,
I'm not sure that I'll be able to attend todays call in person so I wanted
to comment on the proposals I saw in the slide set 'Vport PSE current
requirements v3.pdf'.
Thanks and regards,
David
Comment 184 - subclause 33.3.5.4
--------------------------------
I have a couple of comments in relation to this subclause and the proposed
change.
[1] The current text is the draft states 'At any operating condition the
peak current shall not exceed PPort max/VPort for more than 50ms max and
5% duty cycle max. Peak current shall not exceed IPort max.'. Now the
first shall statement yields a peak current of Pport_max/Vport = 12.95/36
= 360mA with the additional constrains of time and duty cycle. The second
shall statement simply states that the peak current is 400mA. This has
always seemed contradictory, particularly since the second shall statement
has a higher value, yet has no time or duty cycle constrains. I have
wondered if the intent was that the first shall statement only applies
after any startup transient - hence the text 'operating condition' - and
that the second shall statement applied always including during startup.
But then 'any operating condition' could also be read to include startup
transients. Regardless these conflicting shall statements should be
clarified and I don't see that in the proposed change.
[2] Using the formula (Pport_max/Vport) x (400/350) where Pport_max is
12.95W (Table 33-12, item 2) and Vport minimum is 36V (Table 33-12, item
1) seems to allow a maximum current of (12.95/36) x (400/350) = 411mA. Now
when I look at ILIM (Table 33-5, Item 10, PSE output current - at short
circuit condition) it has a minimum value of 400mA and a maximum value of
450mA. This minimum value places a requirement that a PSE has to supply at
a minimum 400mA - but the maximum value appears to place a requirement on
the PSE to current limit at less than 450mA. Hence a PSE is required to
provide a current limit somewhere in the range 400mA to 450mA. I therefore
don't think we should be changing the PD specification to allow it to draw
in excess of the allowable minimum current limit value of a PSE. I suspect
the issue here however is the use of the Vport minimum of 36V as specified
rather than the 'average' Vport minimum of 37V which isn't.
On the assumption that it is the intent that the formula be changed in
such a way that it yields a maximum of 400mA, having this followed by
another shall statement that states the maximum shall be less than IPort
max (which is also 400mA) seems redundant. If the intent is that the peak
is 400mA and that this should occur for a maximum of 50ms with a 5% duty
cycle then the text should simply be changed to read 'At any operating
condition the peak current shall not exceed IPort max for more than 50ms
max and 5% duty cycle max.'.
Comment 183 - subclause 33.2.8.4
--------------------------------
I'm not too sure why we should use VPort = 57V in the calculation on slide
7 since the title of subclause 33.2.8.4 includes the text '.. at min
output voltage'. For VPort > 44V IPeak = 17.6/VPort yields a maximum IPeak
of 17.6/44 = 400mA. Item a) and b) therefore have the same IPeak value of
400mA which supports increasing the peak operating current a PD can draw
to 400mA since that appears to be what IEEE Std 802.3af already requires a
PSE to be able to source. I'm therefore certainly in support of simply
deleting item b) (or replacing it) as it seems to currently be redundant.
In respect to the proposed new formula on slide 10 I don't think we should
have Rch (the channel resistance) as a variable. We should select the
worse case maximum channel resistance base on the cable category that IEEE
P802.3at is going to support and place that figure in the formula. If we
don't we can't ensure the correct value will be used and this could impact
the ability for a PSE to support the cable plant that the standard is
supposed to support.
"Fred Schindler (frs)" <frs@cisco.com> wrote on 09/10/2007 18:58:59:
> Hello,
> The materials for the Oct. 11, IEEE Vport ad hoc meeting are attached.
> Anoop will run this meeting because I am out of the office.
>
> We have completed the review if the SOA comment bucket. Please confirm
> that the information collected is acceptable to the group. If accepted,
> it will be presented to the Task Force during the Richfield meeting.
> The second presentation will help us determine if the legacy PD is a
> constant power load. Understanding this will enable us to create a PSE
> current requirement.
>
> Please ensure that you review the IEEE-SA PatCom slides [
> http://standards.ieee.org/board/pat/pat-slideset.pdf ] prior to the
> start of the conference call. At the start of call I will ask that
> everybody confirms that they have read this material - if anybody hasn't
> we will pause the call until they confirm that they have done so.
>
> Thanks,
> Fred
>
> ---------------------
> Hello,
>
> The IEEE 802.3at Vport ad hoc will be meeting to cover the following:
>
> 1) PSE current requirements to fit on Figure 33-9a, of D0.9.
> Please see
> http://grouper.ieee.org/groups/802/3/at/public/sep07/vetteth_2_0907.pdf
> for our starting point.
>
> 2) Comment review and recommendations.
> a) Powering off the PSE PI when the voltage is out of specification.
> Comments 178, 137
>
> b) Short-circuit removal of power. Comments 111, 11
>
> c) SOA and response time. Comments 186, 185, 96, 78, 122
>
> d) PSE current limits and type-1 considerations. Comment 28, 23
>
> Our goal is to create a presentation for the Richfield IEEE Interim
> (Oct. 18 - 19) that address the above points.
> Thanks,
>
> Fred Schindler
> Technical Leader
> CISCO Systems
> 170 West Tasman Drive
> M/S SJ-19-3
> San Jose, CA 95134-1706
> Tel. (408) 525-9859
>
> ________________________________________________________________________
> ______
> Frederick Schindler has invited you to a Cisco Unified MeetingPlace
> Conference
>
> Date/Time: SEP 27, 2007 at 9:00AM America/Los_Angeles
> Length: 60
> Frequency: 3
> Meeting ID: 131824403
> Meeting Password:
>
> Global Access Numbers:
> http://cisco.com/en/US/about/doing_business/conferencing/index.html
>
> US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117
> India: +91.80.4103.3979 Germany: +49.619.6773.9002
> Japan: +81.3.5763.9394 China: +86.10.8515.5666
>
> TO ATTEND A WEB AND VOICE CONFERENCE:
>
> CISCO INTRANET ATTENDEES
> Join the Web & Voice Conference*
> 1. Go to http://meetingplaceinternal.cisco.com/join.asp?131824403
> <http://meetingplaceinternal.cisco.com/join.asp?131824403>
> 2. Enter your CEC User ID & Password then click OK
> - Accept any security warnings you receive and wait for the Meeting Room
> to initialize
> 3. Click on CONNECT from the Meeting Room to join the Voice Conference
> portion of the meeting
>
> EXTERNAL ATTENDEES - Outside the Cisco Intranet**
> Join the Web & Voice Conference*
> 1. Go to http://meetingplace.cisco.com/join.asp?131824403
> <http://meetingplace.cisco.com/join.asp?131824403>
> 2. Fill in the My Name is field then click Attend Meeting
> - If you have a CEC User ID, click on the Cisco icon
> - Accept any security warnings you receive and wait for the Meeting Room
> to initialize
> 3. Click on CONNECT from the Meeting Room to join the Voice Conference
> portion of the meeting
> - Note: Guest users will see a link to the Global Access Numbers.
>
> *If this is your first time attending a Web Conference, disable any
> pop-up blockers and visit
> http://meetingplace.cisco.com/mpweb/scripts/browsertestupper.asp to test
> your web browser for compatibility with the Web Conference.
> **Not all meetings are scheduled to allow external attendees into the
> Web Conference portion of the meeting, if the URL does not work, please
> follow the Voice only Conference instructions below to attend.
>
> TO ATTEND A VOICE ONLY CONFERENCE
> 1. Dial into Cisco Unified MeetingPlace (view the Access Numbers and
> link above)
> 2. Press 1 to attend the meeting
> 3. Follow the prompts to enter the Meeting ID 131824403 and join the
> meeting
>
> SUPPORT
> Information about this Conference: Contact Frederick Schindler,
> 14085259859
> Cisco IT Support Center: Attend the Voice Conference and then press #0
> on your phone keypad
>
> GLOBAL ACCESS NUMBERS
>
> COUNTRY LOCATION LOCAL NUMBER TOLL
> FREE-FREEFONE
>
> Algeria Algiers +213.21.98.9047
> Argentina Buenos Aires +54.11.4341.0101
> Australia All Locations
> +86.16.0643
> Canberra +61.2.6216.0643
> Melbourne +61.3.9659.4173
>
> North Sydney +61.2.8446.5260
> Austria Vienna +43.12.4030.6022
> Azerbaijan Baku +994.12.437.4829
> Belgium Brussels +32.2.704.5072
> Bosnia &
> Herzegovina Sarajevo +387.33.56.2898
> Brazil Brasilia +55.613.424.0220
> Rio de Janeiro +55.21.2483.6302
> Sao Paulo +55.11.5508.6311
> Bulgaria Sofia +359.2.937.5938
> Canada Calgary +1.403.514.2435
> Edmonton +1.780.441.3715
> Halifax +1.902.474.0214
> Kanata +1.613.254.0005
> Markham +1.905.470.4810
> Montreal +1.514.847.6875
> Ottawa +1.613.788.7250
> Quebec +1.418.634.5645
> Regina +1.306.566.6410
> Toronto +1.416.306.7230
> Vancouver +1.604.647.2350
> Winnipeg +1.204.336.6610
> Chile Santiago +56.2.431.4936
> China Beijing +86.10.8515.5666
> Chengdu +86.28.8696.1333
> Guangzhou +86.20.8519.3333
> Shanghai +86.21.2302.4333
> Colombia Bogota +57.1.325.6065
> Costa Rica San Jose +506.201.3617
> Croatia Zagreb +385.1.462.8908
> Czech Republic Prague +420.22.143.5100
> Denmark Aabyhoj +45.8.939.7131
> Copenhagen +45.3.958.5010
> Dominican Republic Santo Domingo +45.8.939.7131
> Egypt Cairo +20.22.488.5377
> Estonia Tallinn +372.6.67.5998
> Finland Espoo +358.204.70.6227
> France Paris +33.15.804.3116
> Germany Eschborn +49.619.6773.9002
> Hallbergmoos +49.811.554.3016
> Greece Athens +30.210.638.1303
> Hong Kong Hong Kong +852.3406.1000
> Hungary Budapest +36.1.225.4621
> India Bangalore +91.80.4103.3979
> Chennai
> +1.800.102.3979
> Mumbai IL & FS +91.22.4043.4030
> New Delhi +91.11.4261.1088
> Indonesia Jakarta +62.21.7854.7476
> Ireland Dublin +353.1.819.2717
> Israel Netanya +972.9.892.7026
> Italy Milan +39.039.629.5068
> Rome +39.06.5164.4006
> Japan Tokyo Akasaka +81.3.5763.9394
> +0120.312271
> Kazakhstan Almaty +7.327.244.2198
> Korea Seoul Asem +82.2.3429.8102
> Latvia Please see Finland
> Number
> Lebanon Beirut +961.1.97.7011
> Malaysia Kuala Lumpur +60.3.2081.1515
> Penang +60.4.631.5125
> Mexico Mexico City +52.55.5267.1800
> Monterrey +52.81.8221.2462
> Guadalajara +52.33.3770.1206
> Morocco Casablanca +212.2.242.4088
> Netherlands Amsterdam +31.20.357.1487
> New Zealand Auckland +64.9.355.1968
> Wellington +64.4.496.5554
> Nigeria Lagos +234.1.462.1048
> Norway Oslo +47.23.27.3647
> Pakistan Islamabad +92.51.209.7994
> Peru Lima +51.1.215.5101
> Philippines Makati (Manila) +63.2.750.5886
> Poland Warsaw +48.22.572.2615
> Portugal Lisbon +351.21.446.8756
> Puerto Rico San Juan +1.787.620.1865
> Romania Bucharest +40.21.302.3511
> Russia Moscow +7.495.230.5612
> Saudi Arabia Dhahran +966.3.865.7998
> Jeddah +966.2.653.6555
> Riyadh +966.1.218.2666
> Serbia Belgrade +381.11.209.2098
> Singapore Singapore Capital +65.6317.7088
> Slovakia Bratislava +421.2.5825.5309
> Slovenia Ljubljana +386.1.582.3159
> South Africa Cape Town +27.21.413.4502
> Johannesburg +27.11.267.1011
> Pretoria +27.12.844.7401
> Spain Barcelona +34.93.393.4037
> Madrid +34.91.201.2149
> Sweden Gothenburg +46.31.63.4409
> Stockholm +46.8.685.9035
> Switzerland Glattzentrum +41.44.878.7335
> Taiwan Taipei +886.2.8758.7088
> Thailand Bangkok +66.2.263.7008
> Turkey Istanbul +90.212.335.0208
> Ukraine Kiev +380.44.391.3698
> United Arab
> Emirates(UAE) Dubai +971.4.390.7840
> United Kingdom Bedfont Lakes +44.20.8824.0117
> Edinburgh +44.131.561.3643
> London City +44.20.7496.3743
> United States East +1.919.392.3330
> +1.866.349.3520
> West +1.408.525.6800
> +1.866.432.9903
> Venezuela Caracas +58.212.902.0210
> Vietnam Ho Chi Minh +84.8.823.3418
> City (Saigon)
> Hanoi +84.4.974.6250
>
> [attachment "C.htm" deleted by David Law/GB/3Com]
> [attachment "Vport SOA comment bucket.pdf" deleted by David Law/GB/3Com]
> [attachment "Vport PSE current requirements v3.pdf" deleted by David
> Law/GB/3Com]