Cisco Cisco Packet Data Interworking Function (PDIF) Documentation Roadmaps
New In This 8.0 Release
PDIF/FA Features ▀
Cisco ASR 5000 Series Product Overview ▄
OL-22937-01
PDIF/FA Features
Congestion Control and Overload Disconnect Support
Beginning with the 8.1 release of 01/01/09, PDIF supports congestion control and overload disconnect.
Refer to the ―Congestion Control‖ chapter in the PDIF Administration Guide, and to the Command Line Interface
Reference Guide for more configuration information
Reference Guide for more configuration information
Custom DNS Handling
New CLI added to Crypto Template Config Mode: dns-handling { normal | custom }
During IKEv2 session setup, MS may or may not include INTERNAL_IP4_DNS in the Config Payload (CP). PDIF
may obtain one or more DNS addresses for the subscriber in DNS NVSE from a proxy-MIP Registration Reply
message. If Multiple Authentication is used, these DNS addresses may be also received in Diameter AVPs during the
first authentication phase, or in RADIUS attributes in the Access Accept messages during the second authentication
phase.
may obtain one or more DNS addresses for the subscriber in DNS NVSE from a proxy-MIP Registration Reply
message. If Multiple Authentication is used, these DNS addresses may be also received in Diameter AVPs during the
first authentication phase, or in RADIUS attributes in the Access Accept messages during the second authentication
phase.
In
mode, by default PDIF always returns the DNS address in the config payload in the second authentication
phase if one is received from either the configuration or the HA.
mode is a new feature added to the CLI for this release to provide an alternative to the default operation. In
mode, depending on the number of INTERNAL_IP4_DNS, PDIF supports the variety of behaviors described
mode, depending on the number of INTERNAL_IP4_DNS, PDIF supports the variety of behaviors described
in the
section in the ―Crypto Template Configuration Mode Commands‖ chapter of the CLI
Reference Guide.
DELETE Payload Default Action Change
The IKEv2 stack currently always inserts a DELETE Payload in an INFORMATIONAL DELETE Response from both
the PDIF and the MN (WMN).
the PDIF and the MN (WMN).
This default behavior has been updated to not insert a DELETE Payload when the response is from the PDIF.
Note that this behavior is supported by clarifications in RFC 4718.
IPMS Support
IPMS is a licensed feature for PDIF. It provides access to more saved reporting and analysis information.