Revision: 2.85

Specification Update

September 2012

24

12. Time SYNC: Reserved Bits Must Be Zero In PTP Header

Problem:

Receiver expects the reserved bits located in octet 1’s high nibble part of PTP message

header to be zero; future compatibility could be an issue if the specification changes and

uses those bits.

Implication: Specification violation. If these reserved bits are changed in future specifications, there

could be an issue.

Workaround: None.

Status:

A1, A2 NoFix

▼ Return to Summary

13. Internal Copper PHY: No Link In Forced Mode

Problem:

Link may fail if Auto MDI-X is enabled during forced 100BASE-TX mode operation.

Implication: Disable Auto MDI-X for Forced 100BASE-TX operation.

Workaround: Since the 82576 does not disable this function automatically, drivers must perform this

step. Auto MDI-X can be disabled by clearing PHYREG18.12. Intel software drivers are

implemented this way.

Status:

A1, A2 NoFix

▼ Return to Summary

14. Duplicate. See 18.

15. Internal Copper PHY: IEEE 1411.10.03 – 10BASE-T Harmonic Content Fails at Low Voltage

Problem:

IEEE 1411.10.03 – 10BASE-T harmonic content fails at low voltage and the results are <

27dBC.

Implication: None. Specification violation.

Workaround: None.

Status:

A1, A2 NoFix

▼ Return to Summary

16. NC-SI: Additional Multicast Packets May Be Forwarded To MC

Problem:

If the MC enables Multicast filtering for IPv6 Neighbor Advertisement and/or IPv6 Router

Advertisement, additional multicast packets will be forwarded to the MC. The additional

packets forwarded are:

1. Packets with the ICMPv6 header's Message Type: 135,137

2. IPv6 Neighbor Advertisement

3. IPv6 Router Advertisement

Implication: Additional packets may be forwarded to the MC.

Workaround: The MC should filter the different multicast packets.