throbber
RE: Signal vs. Idle debate
`
`Thread Prev
`
`Thread Links
`Thread Next
`
`Thread Index
`
`Date Prev
`
`Date Links
`Date Next
`
`Date Index
`
`RE: Signal vs. Idle debate
`
`To: stds-802-3-pwrviamdi@xxxxxxxx
`Subject: RE: Signal vs. Idle debate
`From: "Larry Miller" <ldmiller@xxxxxxxxxxxxxxxxxx>
`Date: Mon, 08 May 2000 08:01:12 -0700
`Sender: owner-stds-802-3-pwrviamdi@xxxxxxxx
`
`(I sent this out last week but it didn't seem to make it into the
`reflector. Try #2:)
`Paul Yew and others,
`There are a number of Committee members that are concerned about (and,
`indeed, have serious reservations about) the probable side effects of
`superimposing comparatively high current DC on the signaling pairs. To date
`we have had no systematic demonstration by Cisco or anyone else that this
`arrangement is benign, and one of the charter items for the Committee is
`that the DC powering scheme chosen "shall not degrade the transmission
`environment".
`And, as it happens, Cisco apparently did not choose to adopt some of the
`isolation requirements that the Committee reaffirmed from existing 802.3
`standards.
`So it isn't quite such an opened-and-closed book situation as the marketing
`hype would have you believe. And the onus is on Cisco to provide enough
`information to make their case, the "trust us" statements appearing here
`notwithstanding.
`At the March meeting Cisco asked the question "what do we have to do to
`convince the Committee?". I have posted an answer to this at the IEEE
`802.3af public web site:
` http://grouper.ieee.org/groups/802/3/af/public/mar00/index.html
`It is titled "Recommended quantitative measurements of the parameters" and
`is comprised of extracts from IEEE 802.3 and ANSI TP-PMD specifications.
`These are the "numbers" that we all test our products against (hopefully)
`and constitute the criteria for which ANY scheme (not just Cisco's) will
`have to pass muster, in addition to the special requirements set forth by
`the Committee.
`I am sure that most of the Committee members are familiar with these
`criteria, particularly in view of the fact that many of the members
`participated in the standards committees that drew up these requirements in
`the first place.
`A solid presentation of measurements of these parameters in an actual
`operating system (with margins, not just PASS or FAIL results) would do a
`lot to give the Committee sufficient information to evaluate the viability
`of the Cisco design or any other that is proposed.
`(Comments on the requirements list are welcome)
`Regards,
`Larry Miller
`
`Prev by Date: RE: Signal vs. Idle debate (was: Here's a new idea)
`Next by Date: RE: Signal vs. Idle debate (A picture is worth a thousand words)
`
`http://www.ieee802.org/3/power_study/email/msg00122.html[6/12/2013 2:19:19 PM]
`
`

`

`RE: Signal vs. Idle debate
`
`Prev by thread: Use of the DTE Power Reflector
`Next by thread: Remove my name
`Index(es):
`Date
`Thread
`
`http://www.ieee802.org/3/power_study/email/msg00122.html[6/12/2013 2:19:19 PM]
`
`

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