throbber
Minutes of theDTE Power via MDI Task ForceAlbuquerque, NM7-8 March 2000Recording Secretary - Scott BurtonThe meeting was called to order by Steve Carlson, chairman of the DTE Power via MDI Study Group at8:30 AM, 7 March 2000.MotionA motion to affirm Steve Carlson as chair of what is now the DTE Power via MDI Task Force.Moved: M. McCormack Second: A. AndersonMotion carried unanimously.The agenda was presented to the group. There were no additions or changes requested.A show of hands indicated that there were several first-time attendees. Individual introductions of allattendees were then completed.Steve gave an overview of the email reflector and its use, which included a request to not attach files toreflector submissions due to virus concerns. Other administrative issues were then discussed includingworking group voting requirements, the signing procedure for the attendance books, and the schedule andlocation of the next interim meeting. The objectives for this meeting were then presented. Finally, thepresentation guidelines were reviewed. These included keeping presentations simple and small in size andsubmitting them to the chair, in PDF format if possible, two weeks prior to the meeting. The short termschedule for the group was then presented along with the DTE power objectives as approved in Nov 99 inYork.Steve then presented the following: the Decision List (list of questions that have been or need to bedecided); the list of Action items from the last meeting; the list of conclusions from the last meeting and thelist of presentations for this meeting.The presentations followed.Presentation 1 – Isolation Issues, Scott Burton, MitelMuch discussion about the interpretation of 802.3 and the relationship to the ‘950 standards with regard tothe isolation/safety requirements.The following motion resulted.MotionIn order to progress we accept that there are now two isolation requirements of 802.3, environment A and Bper 802.3 section 27.5.3 et al, and that for the purposes of this committee we will treat as a priority forconsideration environment B without precluding environment A.Moved: N. Stapleton Second: L. MillerTechnical 75%Y: 23 N: 3 A: 9 Time 10:00Motion passed.Presentation 2 – Patch Panel/Outlet/Cable Current Considerations, Donald Stewart, LucentPresentation 3 – DTE Power Supply Options, Scott Burton, MitelPresentation 4 – BER Performance with Dynamic loads, Mike Nootbaar, TDKLunch Break at 11:55AMPresentation 5 - Roger Karam, Cisco
`
`Page 1 of 5
`
`CHRIMAR 2041
`
`

`

`Presentation 6 – Considerations of Mid-Span Power Insertion, Kevin Brown, BroadcomPresentation 7 – DTE Power Detection Algorithm, Kevin Brown, BroadcomBreak at 2:45PMPresentation 8 – Proposal for a discovery process, R. Gass/G. Vergnaud, AlcatelPresentation 9 – DTE Power via MDI Detection and Signature Guideline, Robert Leonowich, LucentPresentation 10 – DC Power Discovery Algorithm, Phil Holland, Circa CommunicationsPresentation 11 – Regulatory 802.3 and IEC950, Nick Stapleton, 3COMAdjourn at 4:30pmWednesday March 8, 2000Meeting called to order by Steve at 8:35AMPresentation 12 - Connector Update, Elwood Parsons, Tyco Electronics (AMP)Vote held to determine group’s preference for location of September interim meeting.Result: Copenhagen 14 Boston 18Boston preferred by majority.Presentation 13 - System Considerations for DTE Power, Arlan Anderson, NortelPresentation 14 – Idle Pair Discovery Process, Robert Muir, Level OnePresentation 15 – Voltage and Current Issues, Mike McCormack, 3ComPresentation 16 – Why would anyone want AC? Mike Nootbar, TDKBreak at 9:55AMPresentation 17 – PDTE Detection Mechanism, Amir Lehr, PowerDsinePresentation 18 – Simulation Results for the Diode Discovery Process, Dan Dove, HPPresentation 19 – Why Power over the Signal Pairs? Michael Nootbar, TDKMotionMove that the chair of 802.3af appoint a person to create a document entitled ”802.3af Requirements”which shall include the technical decisions of the January interim and the March Plenary and present saiddocument to the Task Force no later than the close of March 8 2000.Moved: M. McCormack Second: D. RichkasNon-technical 50%Y: 42 N: 0 A: 0 Time 11:38Motion Passes.The chair appointed M. McCormack to create the document.MotionMove that a requirement be added which states:
`
`Page 2 of 5
`
`CHRIMAR 2041
`
`

`

`For DC systems, the power supply system of DCE equipment shall be voltage regulated and currentlimited.Move: M. McCormack Second: NoneMotionMove that a requirement be added which states:For DC systems the minimum output voltage of the source equipment power supply shall be at least40VDC.Moved: M. McCormack Second: N. StapletonTechnical 75%Y: 36 N: 3 A: 8 Time 11:53Motion passes.Lunch Break at 11:55AMCall to order at 1:10PMPresentation 20 – Power Over Ethernet Customer Requirements, David Leon-Guerrero, 3ComPresentation 21 – A Case for Maintaining Future Flexibility, Bob Bell, CiscoMotionThat a requirement be added that states:For whatever powering scheme is decided upon and whatever detection scheme is decided upon, that theability to distinguish between classes of devices not be precluded from theses schemes.Moved: B. Bell Second: A. AndersonTechnical 75% requiredY: 13 N: 15 A: 14 Time: 2:10PMMotion fails.MotionMove that a requirement be added which states:For DC systems, the source device shall be capable of supplying a minimum current of at least 300mA perport.Moved: M. McCormack Second: P. HollandTechnical 75%Y: 39 N: 0 A: 3 Time: 2:25PMMotion passes.Break at 2:25PMMotionMove to add a requirement that:The solution for DTE powering shall support mid-span insertion of the power source.Moved: A. Anderson Second: D. DoveTechnical 75%Y: 33 N: 0 A: 1 Time: 2:45PM Motion passes.MotionThe standard for DTE power distribution will use pairs associated with pins 4-5, and 7-8 as the primarypairs for distributing power over the MDI.Moved: D. Dove Second: A. AndersonTechnical 75%Y: 31 N: 11 A: 7Recount held due to closeness of vote.
`
`Page 3 of 5
`
`CHRIMAR 2041
`
`

`

`Y: 32 N: 11 A: 7 Time: 3:05PMMotion FailsMotionFor DC systems the output voltage of the source equipment power supply system shall be 53+/-5Volts DC.Technical 75% required.Moved P. Holland Second: S. BurtonY: 8 N: 6 A: 27 Time: 3:15PMMotion FailsStraw pollHow many would be in favor of putting a stake in the ground for a source voltage of 48V+/-6V?Y: 33Straw PollThose who would be willing to consider requiring the DTE to accept power from either pair of pairs. Thesource would only need to support provision of power on one of the two pairs.Y: 11 N: 0 Don’t know/care: 28Straw PollHow many are in favor of a differential (center-tap) discovery scheme.Y: 15 N: 4 Don’t know/care: 15Administrative MattersMotionMotion to approve minutes of Dallas meeting.Moved: B. Quackenbush Seconded: S. EllsworthPassed by acclamationActionGroup to perform extensive quantitative measurements of the parameters relevant to the two poweringschemes (active pairs and spare pairs) and have the results ready for presentation at the May meeting. Usethe reflector to organize the workload and report on progress as necessary to ensure that all the testing canbe completed as efficiently as possible. The following link budget performance parameters need to bequantified:• Return loss
`
`• insertion loss
`• overshoot
`• duty cycle distortion
`• sag
`• harmonic distortion
`• jitter
`• common-mode crosstalk
`• insertion and return loss of magnetics for mid-span
`• 1802.3 conformance test for 10BASE-T
`• receiver return loss and crosstalk enhancement
`• 100TX conformance
`• MAU conformance test suite
`• Auto-negotiation
`• common mode to differential mode conversion when injected onto the data pairs/unused pairs
`• 100BASE-T noise budget
`
`• EMI measurementsIt was also suggested that input could be requested from TIA TR42 (Chris DeMinico is liaison).
`
`Page 4 of 5
`
`CHRIMAR 2041
`
`

`

`ActionLarry Miller to post list of recommended tests to the reflector.ActionMike McCormack to see that 802.3af Requirements List is posted to the Task Force Website, and to ensurethat each of the requirements is dated.VoteNeed to elect an editor for the Task Force. Both Mike McCormack and Bob Bell have volunteered. Thosein favor of:Mike McCormack: 28Bob Bell: 5Mike McCormack is elected editor.Next MeetingThe next meeting for the Task Force is to be held on May 24 and 25 in Ottawa, Canada. As this is aninterim meeting there is no registration charge. The Task Force will be meeting in the Quebec Room of theWestin Hotel. The hotel room rate is $200CDN and reservations can be made by calling 613-560-7000 or1-800-228-3000. The group code is Nortel Networks IEEE Group. Due to US and Canadian statutoryholidays around those dates, attendees were encouraged to make flight and hotel reservations early.Email ReflectorSteve C. encouraged all in attendance to make use of the reflector prior to the May meeting in order tomake that meeting as productive as possibleMotionMotion to adjourn meeting.Moved: M. McCormack Seconded: B. QuackenbushMotion approved by acclamation.Meeting adjourned at 4:57PM.
`
`Page 5 of 5
`
`CHRIMAR 2041
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket