Revision: 2.85

Specification Update

September 2012

30

1 will cause the packet to be dropped but for the wrong reason (late packet instead of

bad tagged).

Implication: These packets are not processed correctly and may cause statistic differences (when

compared to specification requirements).

Workaround: None.

Status:

A1, A2 NoFix

▼ Return to Summary

34. MACSec: SA Creation Doesn’t Clear Frame Verification Statistics

Problem:

SA (Secruity Association) creation doesn’t zero frame verification statistics. The creation

of the RX SA should reset the following statistics (per SA):

1.) InPktsOK (LSECRXOK 0x4360-0x4364)

2.) InPktsInvalid (LSECRXINV 0x4380-0x4384)

3.) InPktsNotValid(LSECRXNV 0x43A0-0x43A4)

4.) InPktsNotUsingSA(LSECRXNUSA 0x43C0)

5.) InPktsUnusedSA (LSECRXUNSA 0x43D0)

Implication: Statistics are not cleared out as expected by the specification.

Workaround: Read frame verification statistics before validating the SA (reading clears the statistics).

Status:

A1, A2 NoFix

▼ Return to Summary

35. MACSec: LSECRXNUSA and LSECRXUNSA Statistic Counters Not Provided

Problem:

InPktsNotUsingSA (LSECRXNUSA) and InPktsUnusedSA (LSECRXUNSA) should be defined

per SA. In this implementation, these are counted in one counter.

Implication: Statistics defined in the MACSec standard cannot be provided.

Workaround: None.

Status:

A1, A2 NoFix

▼ Return to Summary

36. MACSec: When MC Is MACSec owner, MAC Reset Still Clears Keys

Problem:

When MC is the owner of the MACSec and a MAC reset occurs, MACSec settings are lost.

A MAC reset (CTRL.RST) can clear out the MACSec - 82576 FW will give an indication to

MC [using the MACSec AEN (NC-SI) or in the MACSec Parameters and MACSec Status

Indication (SMBus)] when this occurs so the MC can reconfigure the keys.

Implication: MAC reset can clear the MACSec setting at anytime.

Workaround: MC must recognize the indication from the FW and reconfigure the keys when this

occurs.