A newer version of this document is available. Customers should click here to go to the newest version.
2.2.1.1. Common Port Mux Interface
2.2.1.2. Common Port Demux Interface
2.2.1.3. Controlled Port Mux Interface
2.2.1.4. Controlled Port Demux Interface
2.2.1.5. Uncontrolled Port RX Interface
2.2.1.6. Uncontrolled Port TX Interface
2.2.1.7. Crypto RX Interface
2.2.1.8. Crypto TX Interface
2.2.1.9. Management Interface
2.2.1.10. Decrypt Port Mux Management Interface
2.2.1.11. Decrypt Port Demux Management Interface
2.2.1.12. Encrypt Port Mux Management Interface
2.2.1.13. Encrypt Port Demux Management Interface
2.2.1.14. Crypto IP Management Bus
2.2.2.1. Common Port Mux Interface Waveform
2.2.2.2. Common Port Demux Interface Waveform
2.2.2.3. Controlled Port Mux Interface Waveform
2.2.2.4. Controlled Port Demux Interface Waveform
2.2.2.5. Uncontrolled Port RX Interface Waveform
2.2.2.6. Uncontrolled Port TX Interface Waveform
2.2.2.7. Crypto RX Waveform
2.2.2.8. Crypto TX Waveform
2.2.2.9. MACsec Management Interface (Read)
2.2.2.10. MACsec Management Interface (Write)
6.3.4. Anti-Replay Protection
For packets identified to go through the Receive Rx lane, the Anti-Replay Protection check is performed on the packet. Upon successfully obtaining an SA from the SA lookup process, a comparison is made between the received packet number in the MACsec header versus the nextPN field in the SA. The packet is discarded if the Received PN < SA nextPN.
For Rx decryption, the next_pn and lowest acceptable pn updates only happen on the deframer where the request passes the secure frame verification check.
The Anti-Replay Protection check can be disabled through the REPLAYPROTECT parameter.