Datasheet

© 2006 Cisco Systems, Inc. All rights reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com.
Page 5 of 11
Obscure X-Forwarded-For Header (HTTP)
When an HTTP request passes through one or more proxies before reaching the server, the IP address of the client may be present in the X-
Forwarded-For header of the HTTP request packet. In some instances, this may be a private address that should not be available outside of
a provider’s network. To support that requirement, the Cisco CSG can replace the IP address in the X-Forwarded-For header with blanks,
effectively obscuring the client’s IP address.
RADIUS VSA Subattribute Parsing
The RADIUS report attribute and RADIUS pod attribute commands are changed to support subattributes. This allows for a more efficient RADIUS
attribute reporting implementation.
SMTP CDR Header Removal
Simple Mail Transport Protocol (SMTP) call detail records (CDRs) can be very large—they include a report attribute for each SMTP header
embedded at the beginning of a message. These specific headers can be eliminated from the CDR, leaving only the SMTP envelope headers
and the size attribute in the report. These are reported as X-CSG-MAIL, X-CSG-RCPT, and X-CSG-SIZE.
IP Fragment Support for E-Mail Protocols
IP fragmentation support is added for Post Office Protocol 3 (POP3), SMTP, and Internet Mail Access Protocol (IMAP). This includes support
for out-of-order fragments.
Support for Out-of-Order Packets for E-Mail and HTTP
Packets received out of order will be buffered and processed in the proper order. This does not guarantee that they will transmit in any specific order,
only that the Cisco CSG will tolerate them arriving out of order. This allows two Cisco CSGs to be deployed back-to-back. As an example, the first
CSG could be used for content-filtering functions and the second CSG could be used for content billing.
Service-Level Reporting for WAP 1.x, RTSP, and FTP
The Service Usage CDR is generated after a configured volume or time is reached. The record contains no transaction-level information about the
session. Support for WAP 1.x, RTSP, and FTP is now supported.
HTTP Multipart Support
The Cisco CSG supports HTTP encapsulation of several body parts into one message. Multipart types may be returned on the condition that the
client has indicated acceptability (using
Accept:) of the multipart type for HTTP sessions. The Cisco CSG will parse the data for the delimiter
specified in the header and will bill at Layer 7, rather than downgrading to Layer 4 as was done in prior releases.
WAP Segmentation and Reassembly Support
This feature allows the Cisco CSG to apply the appropriate policy to a WAP transaction containing a URL spanning multiple WAP segmented
packets.
WAP 1.x Performance Improvement
Internal processing improvements have been implemented that provide an incremental performance improvement to the WAP 1.x protocol
processing. In many cases, depending on protocol mix, this results in as much as a 25-percent improvement for WAP 1.x processing.