Cisco Cisco Packet Data Interworking Function (PDIF)
HSGW Changes in Release 17
▀ HSGW Enhancements for 17.1
▄ Release Change Reference, StarOS Release 17
226
HSGW Enhancements for 17.1
This section identifies all of the HSGW enhancements included in this release:
Feature Changes - new or modified features or behavior changes. For details, refer to the HSGW Administration Guide
for this release.
for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the ASR 5x00 Command Line
Interface Reference for this release.
Interface Reference for this release.
Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters and/or
fields in new or modified schema and/or show command output. For details, refer to the ASR 5x00 Statistics and
Counters Reference for this release.
fields in new or modified schema and/or show command output. For details, refer to the ASR 5x00 Statistics and
Counters Reference for this release.
Important:
This release includes enhancements that are applicable to multiple products. The following lists the
various multi-product enhancements sections, some of which might include content applicable to your HSGW.
AAA Enhancements
CF Enhancements
ECS Enhancements
Firewall Enhancements
GTPP Enhancements
Lawful Intercept Enhancements
MVG Enhancements
NAT Enhancements
SNMP MIB Enhancements
System and Platform Enhancements
CSCuc87249 - HSGW and PGW support RFC6275 (Checksum standard of S2a)
Feature Changes
HSGW and P-GW Support RFC6275
There is a checksum field in the mobility header. The checksum is calculated from the octet string. This includes a
“pseudo-header” followed by the entire Mobility Header starting with the Payload Proto field. The checksum is the 16-
bit one's complement of the one's complement sum of this octet string. In RFC 3775, the next header value used in the
pseudo header is 2. In RFC 6275, the next header value used in the “pseudo header” was changed to 135.
“pseudo-header” followed by the entire Mobility Header starting with the Payload Proto field. The checksum is the 16-
bit one's complement of the one's complement sum of this octet string. In RFC 3775, the next header value used in the
pseudo header is 2. In RFC 6275, the next header value used in the “pseudo header” was changed to 135.
Previous Behavior: For incoming messages, both RFC 3775 and RFC 6275 based checksums are acceptable. For
outgoing messages only RFC 3775 can be used to calculate the checksum.
outgoing messages only RFC 3775 can be used to calculate the checksum.
New Behavior: For incoming messages, both RFC 3775 and RFC 6275 based checksums are acceptable . For outgoing
messages, it is now possible to choose between RFC 3775 and RFC 6275 for calculating the checksum using a CLI
based switch.
messages, it is now possible to choose between RFC 3775 and RFC 6275 for calculating the checksum using a CLI
based switch.