Which two protocols can have their headers compressed through MQC?

Which two protocols can have their headers compressed through MQC? (Choose two.)

Which two protocols can have their headers compressed through MQC? (Choose two.)

A.
RTP

B.
RTSP

C.
HTTP

D.
TCP

E.
UDP

Explanation:
RTP or TCP IP header compression is a mechanism that compresses the IP header in a data packet before the packet is transmitted. Header compression reduces network overhead and speeds up transmission of RTP and TCP packets.

Cisco IOS software provides a related feature called Express RTP/TCP Header Compression. Before this feature was available, if compression of TCP or RTP headers was enabled, compression was performed in the process-switching path. Compression performed in this manner meant that packets traversing interfaces that had TCP or RTP header compression enabled were queued and passed up the process to be switched. This procedure slowed down transmission of the packet, and therefore some users preferred to fast-switch uncompressed TCP and RTP packets.
Now, if TCP or RTP header compression is enabled, it occurs by default in the fast-switched path or the Cisco Express Forwarding-switched (CEF-switched) path, depending on which switching method is enabled on the interface. Furthermore, the number of TCP and RTP header compression connections was increased.

If neither fast-switching nor CEF-switching is enabled, then if TCP or RTP header compression is enabled, it will occur in the process-switched path as before.

The Express RTP and TCP Header Compression feature has the following benefits:

It reduces network overhead.

It speeds up transmission of TCP and RTP packets. The faster speed provides a greater benefit on slower links than faster links.



Leave a Reply 1

Your email address will not be published. Required fields are marked *