Visible to Intel only — GUID: hol1655335942281
Ixiasoft
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)
Visible to Intel only — GUID: hol1655335942281
Ixiasoft
6.4.2. Packet Framer
The plaintext packet entering the Encryption Framer logic block is framed with the SecTAG and IV. One example is shown below, where 8 packets from port/stream 0 are accessing 4 different Crypto channels. Cycle 0 to 11 are showing the Crypto channel allocation cycles where a key is sent to the Crypto HIP. From cycle 11, 2 packets data payloads are packed in the same cycle to improve performance. Crypto HIP supports this packet packing format when the 2 assumptions below are met:
- No channel allocation (key) is sent into the Crypto HIP.
- The start of packet (IV, AAD_LEN) can only happen on the 16 bytes align segment. For example, cycle 12 shows one 8B idle segment is inserted to ensure the next start of packet happens on the 4th segment instead of the 3rd segment.
Figure 30. 8 Packets Accessing 4 Crypto ChannelsIn this table, each colored block represents a different cryptographic channel.