1. Introduction
2. Interface Overview
3. Parameters
4. Designing with the IP Core
5. Functional Description
6. Configuration Registers for MACsec IP
7. MACsec Intel® FPGA IP Example Design
8. MACsec Intel FPGA IP User Guide Archives
9. Document Revision History for the MACsec Intel FPGA IP User Guide
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. Management Interface
2.2.1.8. Decrypt Port Mux Management Interface
2.2.1.9. Decrypt Port Demux Management Interface
2.2.1.10. Encrypt Port Mux Management Interface
2.2.1.11. Encrypt Port Demux Management Interface
2.2.1.12. Crypto IP Management Bus
2.2.1.13. Miscellaneous Control Signals
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)
5.7. Cryptographic AES
The diagram below shows the egress packet flow using a MACsec pattern profile. This is a single 256 bit or 128 bit key that would be used in a GCM encrypt (+ authenticate) or decrypt (+ authenticate) operation.
Figure 29. Egress Packet Flow Using MACsec Pattern Profile (with a Single 256 Bit or 128 Bit Key)
Additional Authenticated Data (AAD) is GCM’s additional authenticated data that does not require encryption or decryption but only requires authentication. For this traffic pattern, the supported AAD length is 2^32 bytes).
Data or text is either the clear text or the cipher text or data that requires encryption or decryption. The size of this data could be up to the maximum allowed by GCM, which is 2^32 bits.
Initialization vector is the 96 bit initialization vector required for every GCM operation. It is 96 bits in length for this pattern.
The diagram below shows the egress packet flow using a MACsec pattern profile. The 16B ICV is dropped into Crypto QHIP and not sent back to the MACsec IP. Only the ICV comparison result (TUSER.auth_error) is sent back to the MACsec IP.
Figure 30. Egress Packet Flow Using MACsec Pattern Profile (with 16B ICV Dropped into Crypto QHIP)