`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`______________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`______________
`
`JUNIPER NETWORKS INC.,
`RUCKUS WIRELESS, INC.,
`BROCADE COMMUNICATION SYSTEMS, INC.,
`and NETGEAR, INC.,
`
`Petitioners,
`
`v.
`
`CHRIMAR SYSTEMS, INC.,
`
`
`
`Patent Owner.
`
`
`
`
`Case Nos. IPR2016-01391, 2106-01389, 2016-01399, and 2016-013971
`
`U.S. Patent Nos. 8,942,107 B2, 8,155,012 B2, 8,902,760 B2, and 9,019,838 B2
`
`
`
`
`
`DECLARATION OF STEVEN JOHNSON
`
`
`
`
`
`1 Ruckus Wireless, Inc., Brocade Communication Systems, Inc. and Netgear, Inc.
`
`filed a petition in (now terminated) IPR2017-00718, -00790 -00719, and -00720 who
`
`have been joined to the instant proceeding.
`
`Page 1 of 5
`
`
`
`CHRIMAR 2054
`
`

`

`
`Case Nos. IPR2016-01391, 2106-01389, 2016-01399, and 2016-01397
`
`
`
`I, Steven Johnson, declare:
`
`
`
`1.
`
`I am a paralegal employed by Brooks Kushman. I make this declaration
`
`on personal knowledge and am competent to testify.
`
`2.
`
`I was asked to review the database of webpages and documents
`
`maintained on the Internet Archive, www.archive.org. Specifically, I was asked to
`
`review the records of the 802.3af Committee captured by the Internet Archive related
`
`to http://www.ieee802.org/3/af/public/.
`
`3.
`
`According
`
`to
`
`the
`
`Internet Archive website,
`
`https://web-
`
`beta.archive.org/web/20001212033500/http://www.ieee802.org:80/3/power_study/
`
`public/nov99/index.html, the Internet Archive first captured the landing page for the
`
`“November 1999 Plenary week meeting” of the “IEEE 802.3 DTE Power via MDI
`
`Study Group” on December 12, 2000 (“the November 1999 landing page”).
`
`4.
`
`The November 1999 landing page contains a link, https://web-
`
`beta.archive.org/web/20001212033500/http://www.ieee802.org:80/3/power_study/
`
`public/nov99/anderson_1_1199.pdf, to a pdf file called “DTE Power via MDI:
`
`System Requirements,” which, according to the Internet Archive, was captured on
`
`December 12, 2000. A copy of that document is attached as Exhibit A.
`
`5.
`
`According
`
`to
`
`the
`
`Internet Archive website,
`
`https://web-
`
`beta.archive.org/web/20010212021939/http://www.ieee802.org:80/3/af/public/mar
`
`00/index.html, the Internet Archive first captured the landing page for the “March
`
`Page 2 of 5
`
`
`
`CHRIMAR 2054
`
`

`

`
`Case Nos. IPR2016-01391, 2106-01389, 2016-01399, and 2016-01397
`
`
`2000 Plenary week meeting” of the “IEEE 802.3af DTE Power via MDI Task Force”
`
`
`
`on February 12, 2001 (“the March 2000 landing page”).
`
`6.
`
`The March 2000
`
`landing page contains a
`
`link, https://web-
`
`beta.archive.org/web/20010212021939/http://www.ieee802.org:80/3/af/public/mar
`
`00/minutes_0300.pdf, to a pdf file called “Meeting Minutes,” which, according to
`
`the Internet Archive, was captured on February 12, 2001. A copy of that document
`
`is attached as Exhibit B.
`
`7.
`
`According
`
`to
`
`the
`
`Internet Archive website,
`
`https://web-
`
`beta.archive.org/web/20010212022058/http://www.ieee802.org:80/3/af/public/may
`
`00/index.html, the Internet Archive first captured the landing page for the “May
`
`2000 Interim meeting” of the “IEEE 802.3af DTE Power via MDI Task Force” on
`
`February 12, 2001 (“the May 2000 landing page”).
`
`8.
`
`The May 2000
`
`landing page contains a
`
`link, https://web-
`
`beta.archive.org/web/20010212022058/http://www.ieee802.org:80/3/af/public/may
`
`00/minutes_0500.pdf, to a pdf file called “Meeting Minutes,” which, according to
`
`the Internet Archive, was captured on February 12, 2001. A copy of that document
`
`is attached as Exhibit C.
`
`9.
`
`The May 2000
`
`landing page contains a
`
`link, https://web-
`
`beta.archive.org/web/20010212022058/http://www.ieee802.org:80/3/af/public/may
`
`00/andersson_1_0500.pdf, to a pdf file called “DTE Power over MDI: Building
`
`Page 3 of 5
`
`
`
`CHRIMAR 2054
`
`

`

`
`Case Nos. IPR2016-01391, 2106-01389, 2016-01399, and 2016-01397
`
`
`Consensus,” which, according to the Internet Archive, was captured on February 12,
`
`
`
`2001. A copy of that document is attached as Exhibit D.
`
`10. The May 2000
`
`landing page contains a
`
`link, https://web-
`
`beta.archive.org/web/20010212022058/http://www.ieee802.org:80/3/af/public/may
`
`00/anderson_1_0500.pdf,
`
`to a pdf file called “Powering and Discovery
`
`Alternatives,” which, according to the Internet Archive, was captured on February
`
`12, 2001. A copy of that document is attached as Exhibit E.
`
`11. According
`
`to
`
`the
`
`Internet Archive website,
`
`https://web-
`
`beta.archive.org/web/20010212022229/http://www.ieee802.org:80/3/af/public/jul0
`
`0/index.html, the Internet Archive first captured the landing page for the “July 2000
`
`Plenary Week meeting” of the “IEEE 802.3af DTE Power via MDI Task Force” on
`
`February 12, 2001 (“the July 2000 landing page”).
`
`12. The July 2000
`
`landing page contains a
`
`link, https://web-
`
`beta.archive.org/web/20010212022229/http://www.ieee802.org:80/3/af/public/jul0
`
`0/minutes_0700.pdf, to a pdf file called “Meeting Minutes,” which, according to the
`
`Internet Archive, was captured on February 12, 2001. A copy of that document is
`
`attached as Exhibit F.
`
`13. The July 2000
`
`landing page contains a
`
`link, https://web-
`
`beta.archive.org/web/20010212022229/http://www.ieee802.org:80/3/af/public/jul0
`
`0/karam_1_0700.pdf, to a pdf file called “Technical Feasibility of Sending Common
`
`Page 4 of 5
`
`
`
`CHRIMAR 2054
`
`

`

`
`Case Nos. IPR2016-01391, 2106-01389, 2016-01399, and 2016-01397
`
`
`Mode Power on the Signal Pairs,” which, according to the Internet Archive, was
`
`
`
`captured on February 12, 2001. A copy of that document is attached as Exhibit G.
`
` I
`
` declare under penalty of perjury that the foregoing is true and accurate to the
`
`best of my ability.
`
`
`
`Executed on: April 18, 2017
`
`
`
`
`
`/Steven Johnson/
`
`
`
`
`
`Page 5 of 5
`
`
`
`CHRIMAR 2054
`
`

`

`EXHIBIT A
`
`EXHIBIT A
`
`

`

`Network Edge TechnologyDTE Power via MDI:DTE Power via MDI:System RequirementsSystem RequirementsArlan AndersonArlan AndersonNovember 5, 1999November 5, 1999
`
`

`

`Ł
`Ł
`
`Arlan J. AndersonNetwork Edge TechnologyNovember 5, 19992of7Strict RequirementsA solution for DTE Powering via DTE must satisfy thefollowing conditions:
`
`It will meet all of the requirements of existing 802.3 Ethernet LANstandards.
`
`Its operation will not degrade in any way the performance of theEthernet data transmission.
`
`It will not damage, or be damaged by, or have its operationdegraded, or be degraded by, any other RJ-45 or RJ-11interconnected equipment to which it may be incidentallyconnected.
`It will not cause any anomalous behavior or change the expectedoperation for any connected LAN equipment (e.g. link status LEDindicators).
`
`Ł
`
`Ł
`
`Ł
`
`It will meet all applicable safety standards and regulations.
`

`

`It should be able to provide sufficient power to support a usefulrange of single IP terminal devices (e.g. IP telephones, wirelessLAN base-stations, cameras, hubs, power controls, thermostats,etc.)
`
`The powering topology should allow for the easy insertion ofpower at any point along the span.
`
`The power source equipment should support a MIB for SNMPsystem management (including any backup power system).
`
`Ł
`
`Ł
`
`Ł
`
`Arlan J. AndersonNetwork Edge TechnologyNovember 5, 19993of7Desirable RequirementsA DTE Powering solution should satisfy the followingconditions:
`
`

`

`Ł
`
`Arlan J. AndersonNetwork Edge TechnologyNovember 5, 19994of7Power Source AttributesTo satisfy the previous conditions the following LANpower source characteristics are proposed:
`
`An isolated DC voltage source meeting all applicable worldwideregulatory safety requirements;
`
`Metallic power feed on Pins 4-5, one of the idle pairs of the 10/100BASE-T LAN loop;
`
`Each loop power feed isolated to withstand ±2250 Volts DC or1500 Volts AC for 60 sec. (IEC 60950:1991 “Hipot”);
`
`The power source to each loop must be independently currentlimited to a level to be determined above the level of the maximumrated output.
`
`All protection circuitry for the loop power feed must recoverautomatically without any operator intervention once the fault hasbeen removed.
`
`Ł
`
`Ł
`
`Ł
`
`Ł
`
`

`

`The loop supply must be "smart," using a discovery mechanism toinsure that power is only provided to authorized terminal devices;
`
`The source must provide a maintenance capability to monitor andsupply power only as long as the loop connection remains valid;
`
`The source must limit the power to any non-authenticated terminalloads to protect against damage;
`
`At the point of power insertion, appropriate terminations will bepresented to the network side of the LAN connection.
`
`Ł
`
`Ł
`
`Ł
`
`Ł
`
`Arlan J. AndersonNetwork Edge TechnologyNovember 5, 19995of7Power Source Attributes (continued)To satisfy the previous conditions the following LANpower source characteristics are proposed:
`
`

`

`Ł
`
`Arlan J. AndersonNetwork Edge TechnologyNovember 5, 19996of7Terminal Power AttributesGiven the previous system attributes and requirementsthe power characteristics for the terminal are:
`
`Ł
`
`Ł
`
`Ł
`
`Ł
`
`Ł
`
`A terminal, which is authorized for LAN powering, must support aunique discovery mechanism for its powering authentication;
`
`A target for the absolute maximum peak power consumption atthe terminal of 15 Watts;
`
`A target of 10 Watts for the continuous nominal power load at theterminal;
`
`At the point of power extraction, appropriate terminations will bepresented to the terminal side of the LAN connection;
`
`Under no circumstances will the terminal source current into theloop (i.e. back feed);
`
`The terminal port must meet the “Hipot” isolation requirements ofIEC 60950:1991.
`
`

`

`Does not require any changes to the magnetics, and the potentialfor secondary effect problems;
`
`Ł
`
`Ł
`Ł
`
`Allows for simple mid-span power insertion;•Use of a DC Voltage source:
`
`Arlan J. AndersonNetwork Edge TechnologyNovember 5, 19997of7Rationale•Use of a non-signal pair for powering:
`
`Ł
`Ł
`Ł
`
`Minimizes interference into the LAN transmission signals;
`Builds on existing, mature power back-up system technology;
`Minimizes noise and potential data transmission interference;
`A DC source enables the use of integrated silicon control circuitry.
`

`

`EXHIBIT B
`
`EXHIBIT B
`
`

`

`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
`
`

`

`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:
`
`

`

`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.
`
`

`

`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).
`
`

`

`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.
`
`

`

`EXHIBIT C
`
`EXHIBIT C
`
`

`

`Minutes of the Power via the MDI Task ForceInterim Meeting, May 24-25Ottawa, CanadaThe Meeting was called to order by Steve Carlson, chairman at 8:45 am, May 24, 2000.Steve Buck, TDK was asked to be recording secretary for this meeting. The first Itemwas a statement of the objectives for week
`
`–
`
`Continue to define the constraints–
` Map possible solutions against the constraints–
` Make decision on voltage, current levels based upon data–
` Decide on powering technique and pair usage–
`
` Decide on discovery mechanismIt was noted that there were a number of new participants (about 20 or 30%).The agenda was presented to the group, no changes to the agenda were presented.The agenda included the following administrative items:Task Force StatusPar approved by NESCOM 1/00Details of the E-mail reflectorDiscussion on the use of reflector (e.g. no flaming)Discussion of Working Group voting membership rulesFuture Meetings:Plenary July 10-14 La Jolla, Ca.Interim – September 11-14, Boston, Mass.Statement of ObjectivesPresentation guidelinesShort Term ScheduleTask force ObjectivesThe Agenda and Opening remarks are posted separately to the Website.This was followed by a short discussion of the decision list (a list of outstandingquestions to be answered by the group and a review of the requirements list.• Maximum Voltage (Objective 5)• Maximum and minimum current (Objective 5)• Are classifications required, and (if so) how many (Objective 6)• Detection to be made on same pair as power• Which pair(s)? (Objective 7)• What level of support for 2-pair legacy systems (Objective 7)
`
`

`

`• Maximum voltage not to exceed SELV IEC 950
`802.3af Requirements
`
`• Level of support for 1000BASE-T (Objectives 1 & 9)• Determine fault behavior• Determine type of discovery mechanism• Single or multi-tiered discovery mechanism• Of the known RJ-45 devices can we determine which can we live with?• Level of support for mid-span insertion• AC or DC• Should we define a standard means to provide optional visual indications of theability to supply power from a connector and/or is it currently providing power?
`• Without specifying the two and only two pairs to be utilized for DTE power, DTEpower shall utilize two pair powering where each wire in the pair is at the samenominal potential and the power supply potential is between the two pairs selected.- January 2000 Interim• Regardless of the detection scheme adopted and the power feed scheme adopted,the power detection and power feed shall operate on the same set of pairs. -January 2000 Interim• Regardless of the final voltage selected, the DTE power max voltage shall notexceed the limits of SELV per IEC 950. - January 2000 Interim• In order to progress we accept that there are two isolation requirements of 802.3,environment A and B per 802.3 section 27.5.3 et al, and that for the purposes ofthis committee we will treat as a priority for consideration environment B withoutprecluding environment A. - March 2000 Plenary• For DC systems the minimum output voltage of the source equipment powersupply shall be at least 40VDC. - March 2000 Plenary• For DC systems, the source device shall be capable of supplying a minimumcurrent of at least 300mA per port. - March 2000 Plenary• The solution for DTE Powering shall support mid-span insertion of the powersource. - March 2000 Plenary
`
`

`

`Scheduled Presentation ListPresentations resulting from motions or other discussions are included within theminutes.
`
`• “
`
`Basic Methods for DTE Power Delivery”, Ed Walker, TI•
` “ISOLATION CONSIDERATIONS for MDI POWER SOURCES and MDI-POWEREDDTE”, John Jetzt, Donald Stewart, Lucent•
` “Common Mode and Differential Mode Discovery Techniques,” Rick Brooks,Nortel•
` “Update on the Diode Discovery Process,” Robert Muir, Level One•
` “IEEE 802.3 DTE Power via MDI Detection and Signature Protocol,” RichardGlaser, John Jetzt, Dieter Knollman, Robert Leonowich, Donald Stewart, Lucent•
` “Proposal for Consensus,” Ralph Andersson, TDK•
` “Cabling from the User Perspective,” Bob Love, Dave Kooistra, IBM•
` “DTE Power at the Endpoint,” Karl Nakamura, Cisco•
` “Phone Discovery at the Mid-Span, Karl Nakamura, Cisco•
` “DTE power via MDI, An Alternative Proposal,” Hans Sitte, Aligent•
` “Insertion and Return Loss with Mid-Span Insertion,” Mike Nootbar, TDK•
` “Transformer Coupling at the Mid-Span,” Kevin Brown, Broadcom•
` “DTE Power via MDI, G. Vergnaud, R. Gass, ALCATEL•
`
` “Powering and Discovery Alternatives,” Arlan Anderson, NortelMotion to approve agendaMoved: Mike McCormackSecond Bill. QuackenbushApproved by acclimation1st Presentation - Basic Methods for DTE Power DeliveryEd Walker, TI Analog Field Applications.BreakMeeting resumed at 10:30AMPresentation - Isolation Considerations -John Jetzt, Donald Stuart, LucentPresentation - Common Mode and Differential Discovery Techniques - Rick Brooks,NortelLunch BreakMeeting resumed at 1:15 PMPresentation - Update on Diode Discovery Process - Robert Muir, Level One
`
`

`

`Presentation - Detection and Signature Protocol - Bob Leonowich , Richard Glaser etal., LucentBreakMeeting resumed at 3:10PMGeoff Thompson made a short speech on IEEE Patent Policy. The new IEEE policy nowrequests a letter disclosing patents a head of time, not after a standard is approvedPresentation - TR42.1 Liaison report - Chris DominicoTR42 has set up a task group to answer the questions from IEEE 802.3Presentation - DTE Power over MDI - Building Consensus - Ralph Andersson, TDKSemiconductorPresentation - User requirements for Cabling Support - Robert Love, LAN ConnectConsultants, Dave Kooistra, IBMPresentation - Power over the MDI - Karl Nakamura, Roger Karam, Cisco SystemsPresentation - Power over the MDI using the two signal pairs - Karl Nakamura, RogerKaram, Cisco SystemsMotion to adjourn: McCormack Time: 5:24PMSecond: QuakenbushApproved by acclimationThursday May 25, 2000The Meeting was called to order by Steve Carlson, chairman at 8:30AM, May 25, 2000Presentation - DTE Power via the MDI, an Alternative Proposal - Hans Sitte, AgilentPresentation - Return Loss with Mid-span - Mike Nootbaar, TDK SemiconductorPresentation - Mid span Insertion using Transformer coupling - Kevin Brown,BroadcomBreakMeeting resumed at 10:10AMPresentation - DTE Power via the MDI - G. Vergnaud, R. Gass, R. Jaeger, AlcatelPresentation - Consideration in selecting feeding voltage/current Amir Lehr, YairDarshan, Avinoam, Levy - PowerDsinePresentation - Powering and discovery Alternatives - Arlan Anderson, NortelPresentation - Proposal to Move forward - Chris Cullin – Cisco SystemsPresentation - Consensus Proposal for DTE power via the MDI - Dan Dove, HP
`
`

`

`Lunch BreakMeeting resumed at 1:20PMMotion 1: All technical motions which are passed from this time forward, unlessspecifically excluded in the wording of the motion shall be incorporated into thedocument entitled 802.3 requirements which was created at the March Plenary. Theeditor is to maintain this document and update it within one week of the end of themeetingMoved: Michael McCormackSecond: Arlen AndersonTechnical: Not ProceduralY:44N:0A:2Time: 1:25PMMotion PassesMotion 2: The standard for DTE power distribution will use pairs associated with pins 4-5, and 7-8 as the primary pairs for distributing power over the MDI.Moved: Mike NootbaarSecond: Amir LehrTechnical: Yes 75%Y: 32N: 14A: 6Time:2:11Motion FailsMotion to table this motion until after Dan Dove Presentation. Yes:24No:14Time:1:30Motion PassesMotion 3: It is an objective that the DTE shall be required to accept power from both the12,36 and the 45,78 pair-sets with the requirement that those pair-sets both use thesame method of detection.Moved: Dan DoveSecond: Robert LoveTechnical: yes 75%Y: 27N: 21A: 6Time:2:03PMMotion FailsMotion 4: 802.3af systems shall distribute DC PowerMoved: Michael McCormackSecond: Bill QuackenbushTechnical: yes 75%Y: 53N: 0A: 2Time: 2:15PMMotion PassesMotion 5: Move it is an objective to come up with one and only one discovery method.Moved: Robert LoveSecond: Robert MuirTechnical: yes 75%Y: 31N: 11 A: 7Time: 2:32
`
`

`

`Due to the closeness of the vote a recount was takenY: 31N: 11 A: 11Time: 2:34Motion FailsMotion 6: Move: If both pair sets may be used for powering, Midspan shall supply poweron 45,78 - Supplying power on pins 12,36 from the midspan is for a later revision of thestandard.Moved: Bob LoveSecond: Don PannellTechnical: Yes 75%Y: 28N: 4A: 5Time: 2:55PMMotion PassesMotion 7: 802.3af proceed with the development of a low frequency, low energycommon mode detection method.Moved: Dan DoveSecond: Amir LehrTechnical: Yes 75%Y: 33N: 8A: 4Time: 3:05 PMMotion PassesMotion 8: The transmission of data across transformers placed in mid-span insertions isoutside of the scope of this task force and shall not be an objective.Moved: Ralph AnderssonSecond: Robert MuirTechnical: Yes 75%Y:10N:18A: 13Time: 3:39PMMotion FailsThe discussion on Motion 8 spawned a presentation:Presentation - Physical Layer Topology considerations for DTE power over the MDI -Sterling Vaden - Superior Modular ProductsDiscussion of cable modeling and connector issues such as loss, number etc. Patchcord issues. Insertion and return lossMotion 9: That it be an objective of the 802.3af task force to determine the optimalmethod to apply power at the “mid-span” and” DCE end” to minimize data-pathimpairments at a reasonable cost.Amendment: substitute “DCE end” for the word “Mid-Span”Moved : NormSeconded: Chris CullinWithdrawn, added as friendly by D. DoveMoved: Dan DoveSecond: Ralph AnderssonTechnical: Yes 75%Y: 26N: 3A: 12Time: 3:57PMMotion Passes
`
`

`

`Motion 10: The 802.3af task force shall consider 1000BASE-T support only for “DCE-end” power insertions.Moved: Ralph AnderssonSecond: James PolkTechnical: Yes 75%Y: 6N: 26A: 11Time: 4:05PMMotion FailsMotion 11: If it can be shown that the DTE support of both sets 1236 and 4578 is bothtechnically and economically feasible, the objective is to require that the DTE supportboth.Moved: Mike NootbaarSecond: Bob LoveTechnical: Yes 75%Y: 23N: 16A: 3Time: 4:15PMMotion FailsMotion 12: That DTE must be able to accept power on Pairs 4-5, 7-8 and be optionallyavailable on Pairs 1-2, 3-6Moved: Nick StapletonSecond: Arlen AndersonTechnical: Yes 75%Y: 7N: 29A: 5Time: 4:30PMMotion FailsMike McCormack (editor 802.3af) talked about the need to progress on a draft of thespecification. He intends to include straw poll information even though it has not beenapproved. A draft will be available by the next meeting.Action Item for 802.3af:Tutorial at next Plenary: A 1 hour presentation followed by a ½ hour Q&ARoger Karam, Carl Nakamura, Ralph Andersson and Bob Leonowich have volunteeredto do the presentation.Geoff Thompson, Steve Carlson, Roger, Karam, Carl Nakamura and Henry Hinrichs tohandle Q&A.Motion 13: That we accept the powering of the DTE via either sets of wire pairs (1-2, 3-6 and 4-5, 7-8), in anticipation of the detailed technical and economic feasibility of eachhaving been shown prior to the Working Group Ballot.Moved: David LawSecond: Roger KaramTechnical: Yes 75%Y: 32N: 4A: 3Time: 5:27PMMotion PassesMotion 14: To approve minutes from Albuquerque.Moved: Steve CarlsonSecond: Tom DineenTechnical: noMotion Passed by acclimation. Time: 5:30PM
`
`

`

`Liaison Letter from Bob Bell chair TR41.4Motion 15: Send a response to TR41.4Moved: Arlen AndersonSecond: Tom DineenTechnical: NoMotion Passes by acclamationTime: 5:40PMMotion to adjournMoved: Steve CarlsonSecond: Karl NakamuraTechnical: NoMotion Passed by acclimationTime: 5:41PM
`
`

`

`EXHIBIT D
`
`EXHIBIT D
`
`

`

`DTE Power over MDI:
` Building Consensus
`Ralph Andersson
`TDK Semiconductor
`Daniel Dove
`Hewlett Packard
`Robert Muir
`Level One Communications
`
`May 24, 2000
`
`Ottawa IEEE 802.3af Interim
`
`

`

`Objectives:
`
`•
`
`•
`
`I am not going to re-present all of the proposals for the application of
`power over the MDI
`I will focus on the proposals that have occurred within this group
`concerning which pairs to apply power over: the signal pairs or the
`IDLE pairs.
`• Benefits of each
`• Drawbacks of each
`• Consensus on the path where there is the greatest commonality
`•
`Is this possible?
`
`Ottawa IEEE 802.3af Interim
`
`

`

`Power over MDI:
`• Objectives to be considered from 11/99:
`(1) Economically provide power over a twisted- pair link segment to a single Ethernet
`device.
`• To be included:
`– 10BASE-T,
`– 100BASE-TX.
`• To be considered:
`– 1000BASE-T.
`(2) Select one power distribution technique for world wide use
`(3) Not cause damage and inter-operate with compliant RJ- 45 MDI Ethernet devices
`including:
`a. Switch- to- switch connections (both supplying power)
`b. Cross- over cables
`c. Common mode termination implementations
`d. Shorted conductors, pairs or loop- back plug Support current standard, 4- pair, horizontal
`cabling infrastructure for installed Cat 3 and Cat 5 cabling
`
`Ottawa IEEE 802.3af Interim
`
`

`

`Power over MDI:
`
`• Objectives to be considered from 11/99 (cont.):
`(4) Define a capability detection function that works with a powered and an un-
`powered device
`(6) Add appropriate management objects for power capability and status
`(7) Support current standard, 4- pair, horizontal cabling infrastructure for installed
`Cat 3 and Cat 5 cabling
`(8) Preserve the signal transmission and isolation characteristics of exis