Cisco Cisco Packet Data Interworking Function (PDIF)
P-GW Changes in Release 17
P-GW Enhancements for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
367
New Behavior: Added case for handling the disconnect reason IMS_AUTHORISATION_FAILED case in SM-APP.
As a result, EGTP_CREATE_SESSION_RESPONSE is received with
EGTP_CAUSE_USER_AUTHENTICATION_FAILED in such a case.
As a result, EGTP_CREATE_SESSION_RESPONSE is received with
EGTP_CAUSE_USER_AUTHENTICATION_FAILED in such a case.
CSCug96117 - Alternate Care-of Address Mobility Option support on PGW/LMA
Feature Changes
Alternate Care-of Address Mobility Option Support
Proxy Mobile IPv6 is a network-based mobility management protocol. The mobility entities involved in the Proxy
Mobile IPv6 protocol, the Mobile Access Gateway (MAG) and the Local Mobility Anchor (LMA), setup tunnels
dynamically to manage mobility for a mobile node within the Proxy Mobile IPv6 domain. This document describes an
extension to the Proxy Mobile IPv6 protocol to register an IPv4 or IPv6 data plane address that is different from the
Proxy Care-of Address with the LMA. This allows separation of control and data plane.
Mobile IPv6 protocol, the Mobile Access Gateway (MAG) and the Local Mobility Anchor (LMA), setup tunnels
dynamically to manage mobility for a mobile node within the Proxy Mobile IPv6 domain. This document describes an
extension to the Proxy Mobile IPv6 protocol to register an IPv4 or IPv6 data plane address that is different from the
Proxy Care-of Address with the LMA. This allows separation of control and data plane.
Some of the deployments of Proxy Mobile IPv6 separated the control and data plane end points for Mobile Access
Gateway. There will be a separate IP address for the entity that sends and received the Proxy Mobile IPv6 signaling
messages. Similarly, there will be a separate IP address for the entity that encapsulates and decapsulates the data traffic
to and from the mobile node.
Gateway. There will be a separate IP address for the entity that sends and received the Proxy Mobile IPv6 signaling
messages. Similarly, there will be a separate IP address for the entity that encapsulates and decapsulates the data traffic
to and from the mobile node.
In order to allow the separation of the control and data plane, the address of the data plane traffic endpoint needs to be
sent in a separate extension to register two IP addresses with the LMA. The IP address used for the signaling messages
will continue to be called the Proxy Care-of-Address. A separate IP address for the data plane is carried in the Proxy
Binding Update to indicate the tunnel end point for the data traffic.
sent in a separate extension to register two IP addresses with the LMA. The IP address used for the signaling messages
will continue to be called the Proxy Care-of-Address. A separate IP address for the data plane is carried in the Proxy
Binding Update to indicate the tunnel end point for the data traffic.
The extension Alternate Care-of-Address Mobility Option defined in RFC 6275 should be used. When using IPv6
transport and IPv4 transport, Alternate Ipv4 Care of Address Mobility Option defined in RFC 6463 should be used.
transport and IPv4 transport, Alternate Ipv4 Care of Address Mobility Option defined in RFC 6463 should be used.
Normally, a binding update specifies the desired care-of-address in the source address field of the IPv6 header.
However, in some cases such as when the mobile node wishes to indicate a Care-of Address that it cannot use as a
topologically correct source address or when the used security mechanism does not protect the IPv6 header it is not
possible.
However, in some cases such as when the mobile node wishes to indicate a Care-of Address that it cannot use as a
topologically correct source address or when the used security mechanism does not protect the IPv6 header it is not
possible.
The Alternate Care-of-Address option is for this type of situation. This option is valid only in binding update. The
Alternate Care-of Address field contains an address to use as the care-of-address for binding rather than using the source
address of the packet as the care-of-address.
Alternate Care-of Address field contains an address to use as the care-of-address for binding rather than using the source
address of the packet as the care-of-address.
A MAG may include the Alternate IPv4 Care-of-Address option in a PBU. An LMA that receives and implements the
Alternate IPv4 Care-of-Address option must echo the option back to the MAG in a reply PBA.
Alternate IPv4 Care-of-Address option must echo the option back to the MAG in a reply PBA.
With this feature, P-GW/LMA will support data-plane address endpoint separation with alternate care-of-address
mobility option defined in RFC 6275 and RFC 6463 for IPv6 and IPv4 transport respectively.
mobility option defined in RFC 6275 and RFC 6463 for IPv6 and IPv4 transport respectively.
Command Changes
alt-coa-allowed
This new command allows Alternate Care-of-address support to be added at LMA to separate signaling and control
plane traffic.
plane traffic.
configure
context context_name