This object reports which compression algorithm, if any, this remote-access session is using to reduce the size of packets before transmission, directly explaining the gap, or lack thereof, seen between the compressed and uncompressed octet counters elsewhere in this MIB for the same session. It matters for both bandwidth and CPU trade-off decisions; some compression algorithms save more bandwidth but cost more CPU cycles per packet, so an admin might want to know which algorithm is negotiated on high-volume sessions to judge whether that trade-off is appropriate. Seeing this report none on a session an admin expected to be compressed would explain why that session's compressed and uncompressed octet counters are showing identical, non-diverging values.