X-Header Insertion And Encryption; License Requirements; X-Header Insertion - Cisco ASR 5000 Series Administration Manual

Enhanced Charging Service Overview
Limitations for Dynamically Disabling TCP Proxy
This section lists known limitations to disabling TCP proxy dynamically:
 TCP proxy cannot be disabled when one end of the TCP supports time stamp and other does not.
 Dynamic disabling does not work when both sides of the TCP have different MSS negotiated.
 Toggling the proxy on the same connection might reduce TCP performance.
 TCP proxy can only be disabled when both ends of TCP are in connected states.
 Multiple connections (1:n) connections cannot be joined together.
 TCP proxy can only be disabled when the conditions outlined for dynamic disabling is achieved (when there is
no unAcked data in the network).

X-Header Insertion and Encryption

This section describes the X-Header Insertion and Encryption features, collectively known as Header Enrichment,
which enable to append headers to HTTP/WSP GET and POST request packets for use by end applications, such as
mobile advertisement insertion (MSISDN, IMSI, IP address, user-customizable, and so on).
Important:
IPSG, and P-GW.

License Requirements

X-Header Insertion and Encryption are both licensed Cisco features. A separate feature license may be required. Contact
your Cisco account representative for detailed information on specific licensing requirements. For information on
installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations
chapter in the System Administration Guide.

X-Header Insertion

This section provides an overview of the X-Header Insertion feature.
Extension header (x-header) fields are the fields not defined in RFCs or standards but can be added to headers of
protocol for specific purposes. The x-header mechanism allows additional entity-header fields to be defined without
changing the protocol, but these fields cannot be assumed to be recognizable by the recipient. Unrecognized header
fields should be ignored by the recipient and must be forwarded by transparent proxies.
The X-Header Insertion feature enables inserting x-headers in HTTP/WSP GET and POST request packets. Operators
wanting to insert x-headers in HTTP/WSP GET and POST request packets, can configure rules for it. The charging-
action associated with the rules will contain the list of x-headers to be inserted in the packets.
For example, if you want to insert the field x-rat-type in the HTTP header with a value of rat-type, the header inserted
should be:
x-rat-type: geran
where, rat-type is geran for the current packet.
Configuring the X-Header Insertion feature involves:
In this release, the X-Header Insertion and Encryption features are supported only on the GGSN,
Cisco ASR 5x00 Enhanced Charging Services Administration Guide ▄
Enhanced Features and Functionality ▀
59