Which item is NOT typically included in TCP packet metadata?

Which item is NOT typically included in TCP packet metadata?

• A. To address
• B. From address
• C. Message size
• D. Encryption type

Answer: (D)

Think about what TCP headers actually carry. The information in a TCP segment is mainly about managing the connection: source and destination ports, sequence and acknowledgment numbers, flags, window size, checksum, and options. The actual addresses (To and From) live in the IP header, not in the TCP header, though you still use them to route the packet across networks. The size of the data is not stored as a separate “message size” field in the TCP header; you determine it from the header lengths and how much data follows. Encryption type, on the other hand, isn’t something TCP specifies. Encryption is applied by higher-layer protocols (like TLS) or by the application, so the TCP metadata itself doesn’t include any encryption details. That’s why encryption type is not typically included in TCP packet metadata.

Think about what TCP headers actually carry. The information in a TCP segment is mainly about managing the connection: source and destination ports, sequence and acknowledgment numbers, flags, window size, checksum, and options. The actual addresses (To and From) live in the IP header, not in the TCP header, though you still use them to route the packet across networks. The size of the data is not stored as a separate “message size” field in the TCP header; you determine it from the header lengths and how much data follows.

Encryption type, on the other hand, isn’t something TCP specifies. Encryption is applied by higher-layer protocols (like TLS) or by the application, so the TCP metadata itself doesn’t include any encryption details. That’s why encryption type is not typically included in TCP packet metadata.