What is RFC 3095?
RFC 3095 Robust Header Compression July 2001 Appendix A. Detailed classification of header fields Header compression is possible thanks to the fact that most header fields do not vary randomly from packet to packet. Many of the fields exhibit static behavior or change in a more or less predictable way.
When did RFC 3095 Robust Header Compression come out?
RFC 3095 Robust Header Compression July 2001 Note: The static and dynamic chains of IR or IR-DYN packets for profile 0x0001 (ROHC RTP) MUST end with the static and dynamic parts of an RTP header. If not, the packet MUST be discarded and the context MUST NOT be updated.
Where is the sequence number on a RFC 3095 header?
RFC 3095 Robust Header Compression July 2001 Otherwise, a compressed sequence number is included in the IPX compression field in an Extension 3 of an UOR-2 header. The authentication data field in AH changes from packet to packet and is sent as-is.
What are the inner IP header flags in RFC 3095?
RFC 3095 Robust Header Compression July 2001 Inner IP header flags These correspond to the inner IP header if there are two, and the single IP header otherwise. 0 1 2 3 4 5 6 7. | TOS | TTL | DF | PR | IPX | NBO | RND | ip2 | if ip = 1. TOS, TTL, PR, IPX: Indicates presence of fields as shown to the right of the field in question below.