# CF Changes in Release 14.0

This chapter identifies features and functionality added to, modified for, or deprecated from 14.0 Content Filtering software releases.

Topics covered in this chapter are:

- CF Feature Changes as of September 28, 2012
- CF Configuration Management Changes as of September 28, 2012
- CF Performance Management Changes as of September 28, 2012
- CF Security Management Changes as of September 28, 2012
- CF Feature Changes as of June 29, 2012
- CF Configuration Management Changes as of June 29, 2012
- CF Performance Management Changes as of June 29, 2012
- CF Security Management Changes as of June 29, 2012

IMPORTANT:

Enhancements to Diameter, GTPP, and RADIUS in release 14.0 are located in the Accounting Management Changes chapter.

Enhancements to SNMP MIB in release 14.0 are located in the SNMP MIB Changes chapter.

Enhancements to Web Element Manager (WEM) in release 14.0 are located in the Web Element Manager Changes chapter.

CF Feature Changes as of September 28, 2012

This section provides information on Content Filtering feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the Content Filtering Administration Guide for this release.

New Content Filtering Features

This section identifies new Content Filtering features available in release 14.0.

RTSP over ICAP Interface

RTSP traffic that contains adult content can now be content filtered over the ICAP interface. The Request packets received through RTSP will be considered for content filtering. Previously, only the HTTP and WAP traffic could be content filtered over the ICAP interface.

The following scenarios describe the failure actions where an RTSP request is received from the client. If ICAP is enabled, then the request goes to the ICAP server for content filtering.

- Allow: If the failure action configured is “allow”, the RTSP request packet is sent out after applying the appropriate disposition action. Here, the flow remains the same as in the case if the ICAP response received is 200 OK.
- Content Insert: If the failure action configured is “content-insertion <string of size 1 to 128>”, then this failure action for RTSP request will not be supported. Instead the failure action “Discard” for such an RTSP request will be supported.
- Redirect-URL: If the failure action configured is “redirect-url <string of size 1 to 128>”, then a TCP FIN_ACK packet with an RTSP “302 Moved Temporarily” response header is inserted towards the client containing the said URL for redirection. A TCP RST packet is inserted towards the server. The underlying TCP connection is thus closed. If the RTSP client wants to retry to the redirected URL, the opening of a new TCP connection must be initiated.
- Discard: If the failure action configured is “discard”, then the RTSP request packet received from the client is quietly discarded and no notification is sent to the client.
- Terminate flow: If the failure action configured is “terminate-flow”, then the TCP connection is torn down by injecting a TCP FIN-ACK towards the client and a RST packet towards the server. However, no notification will be sent to the RTSP client and the server regarding this flow termination.

For more information on the ICAP feature, see the ICAP Interface Support appendix in the administration guide for the product that you are deploying.

CF Configuration Management Changes as of September 28, 2012

This section provides information on Content Filtering configuration command changes in release 14.0.

None for this release.

CF Performance Management Changes as of September 28, 2012

This section provides information on Content Filtering performance management changes in release 14.0.

IMPORTANT:

For more information regarding bulk statistics in this section, refer to the Statistics and Counters Reference for this release.

For more information regarding commands in this section, refer to the Command Line Interface Reference for this release.

New CF Bulk Statistics

This section identifies new CF bulk statistics available in release 14.0.

The following bulk statistics are new in this release:

ECS Schema

- acf-rtsp-permit
- acf-rtsp-deny
- acf-rtsp-redirect

Modified CF Bulk Statistics

This section identifies CF bulk statistics modified in release 14.0.

None for this release.

Deprecated CF Bulk Statistics

This section identifies deprecated CF bulk statistics that are no longer supported in release 14.0.

None for this release.

New CF Performance Commands

This section identifies new CF performance commands available in release 14.0.

None for this release.

Modified CF Performance Commands

This section identifies CF performance commands modified in release 14.0.

show active-charging content-filtering server-group statistics verbose

This command displays information for Content Filtering Server Group (CFSG) configured in the service.

Exec Mode

The following fields have been added to the output of this command:

- RTSP Permit
- RTSP Deny
- RTSP Redirect

CF Security Management Changes as of September 28, 2012

This section provides information on Content Filtering security management changes in release 14.0.

None for this release.

CF Feature Changes as of June 29, 2012

This section provides information on Content Filtering feature changes in release 14.0.

IMPORTANT:

For more information regarding features in this section, refer to the Content Filtering Administration Guide for this release.

New Content Filtering Features

This section identifies new Content Filtering features available in release 14.0.

CF Policy ID

The CF Policy ID can now be enabled depending on the subscriber (Child, Adult, etc.) and not based on the subscriber's device. This can be configured through PCRF for Gx using the new SN-CF-Policy-ID attribute.

For more information on the new attribute, refer to the Diameter Dictionaries and Attribute Definitions chapter in the AAA Interface Administration and Reference.

IWF Blacklisting

The URL Blacklisting solution requires the integration of two databases in the ASR 5000 to provide blacklisting services. In addition to the existing NCMEC database, Internet Watch Foundation (IWF) is the new database supported for blacklisting. The blacklist file is obtained from the IWF database in OPTBLDB format. The WEM server then downloads the URL Blacklist database file from the specified source at configured schedule. Whenever WEM receives a new Blacklist file, it is merged with the existing blacklist files from other sources into OPTBLDB format.

For more information, refer to the Content Filtering Services Administration Guide and Web Element Manager Installation and Administration Guide.

CF Configuration Management Changes as of June 29, 2012

This section provides information on Content Filtering configuration command changes in release 14.0.

None for this release.

CF Performance Management Changes as of June 29, 2012

This section provides information on Content Filtering performance management changes in release 14.0.

None for this release.

CF Security Management Changes as of June 29, 2012

This section provides information on Content Filtering security management changes in release 14.0.

None for this release.