RE: [10GBASE-T] Auto-Negotiation Support
But, what if is not just a stand alone NIC? I can see embedded applications
that would require operation in low power modes. Why limit the applications?
Is there a significant cost associated with the trade off of supporting
auto-negotiation at 100/1000/10000 Mbps vs. 1000/10000 Mbps. If so, can
someone clarify the cost implications?
-----Original Message-----
From: Koenen, David [mailto:David.Koenen@hp.com]
Sent: Tuesday, January 14, 2003 10:24 AM
To: Rich_Hernandez@exchange.dell.com
Cc: stds-802-3-10gbt@ieee.org
Subject: RE: [10GBASE-T] Auto-Negotiation Support
Microsoft has the only WOL support requirement I know of. It is an optional
feature in PCI/PCI Power Management Specs. Microsoft's requirement is that
the Desktop/Server support WOL on a least one NIC. That can be accomplished
by most all of the Fast (10/100) or Gigabit (10/100/1000T) embedded or
standup NICs today and possibly 1000SX in the near future. We're
considering the 10GBase-T to be a high speed, stand-alone option NIC. In
which case, it doesn't require WOL.
: djk
-----Original Message-----
From: Rich_Hernandez@dell.com [mailto:Rich_Hernandez@dell.com]
Sent: Tuesday, January 14, 2003 9:03 AM
To: stds-802-3-10gbt@ieee.org
Subject: [10GBASE-T] Auto-Negotiation Support
Is the study group considering the PCI and PCI-E power management
requirements for an add-in adapter implementation of 10GBASE-T? To my
knowledge the low power management requirement can only be met by the
current 1000Base-T controllers when running at 10/100 Mpbs. Hence, I can see
the need for supporting auto-negotiation that includes 100Base-T and
1000Base-T. The controller should be able to negotiate down to 100 Mbps when
operating in a lower power mode i.e. Wake on LAN or remote management(ASF,
IPMI).