Cisco Cisco IOS Software Release 12.3(11)T
Cisco Mobile Wireless Home Agent Release 2.0
The Home Agent
12
Cisco IOS Release 12.3(11)T
OL-3235-04
The following call flow illustrates a Mobile IP Resource Revocation (FA initiated revocation):
Step 1
The Mobile starts a mobile IP data session with the PDSN/FA.
Step 2
The PDSN/FA appends the registration revocation support extension to the mobile registration request,
and forwards it to the HA.
and forwards it to the HA.
Step 3
In response, the HA appends the registration revocation support extension to a registration reply, and
sends it to the PDSN/FA.
sends it to the PDSN/FA.
Step 4
Some event occurs in the PDSN/FA, and the PDSN/FA decides to close the session.
Step 5
The PDSN/FA sends a Mobile IP resource revocation message to the HA.
Step 6
The HA sends a Mobile IP resource revocation acknowledgement to the HA. The HA clears the binding
and the PDSN/FA clears the session.
and the PDSN/FA clears the session.
I-bit Support
The I (Inform) bit is used during the registration revocation phase to notify the mobile node (MN) of the
revoked data service in cases where the mobile node has more than one MobileIP flows. If, during the
registration phase, this bit is set to 1 by a mobility agent in the revocation support extension in the
RRQ/RRP, it indicates that the agent supports the use of the “I” bit in revocation messages.
revoked data service in cases where the mobile node has more than one MobileIP flows. If, during the
registration phase, this bit is set to 1 by a mobility agent in the revocation support extension in the
RRQ/RRP, it indicates that the agent supports the use of the “I” bit in revocation messages.
In the current implementation, if MobileIP RRQ is received with I bit set in the revocation support
extension, then the HA will also set the I-bit to 1, and the I-bit shall be considered to be used during the
revocation phase. When the HA initiates revocation, and if the I bit was negotiated, it shall set the I bit
to 1 in the Revocation message if a binding is administratively released, and will set it to 0 if a inter-
PDSN handoff is detected by the HA. When revocation is initiated by the PDSN, and the revocation
message has I-bit set to 1, then the HA will also set the I-bit to 1 in the revocation ACK message.
extension, then the HA will also set the I-bit to 1, and the I-bit shall be considered to be used during the
revocation phase. When the HA initiates revocation, and if the I bit was negotiated, it shall set the I bit
to 1 in the Revocation message if a binding is administratively released, and will set it to 0 if a inter-
PDSN handoff is detected by the HA. When revocation is initiated by the PDSN, and the revocation
message has I-bit set to 1, then the HA will also set the I-bit to 1 in the revocation ACK message.
Mobile IPv4 Resource Revocation Restrictions
The following list identifies the restrictions for Mobile IPv4 Resource Revocation feature for the current
release:
release:
•
The STC attribute received in access-accept during HA-CHAP is ignored, and the feature
configuration on the Home Agent will take precedence.
configuration on the Home Agent will take precedence.
•
The Revocation message, Revocation ACK message, and Revocation support extension (not
protected by either FHAE or IPSec) will not be discarded, but will be processed. We recommend
that you configure an FA-HA security association on the Home Agent, or that an IPSec tunnel exists
between the FA and the HA.
protected by either FHAE or IPSec) will not be discarded, but will be processed. We recommend
that you configure an FA-HA security association on the Home Agent, or that an IPSec tunnel exists
between the FA and the HA.
•
Resource Revocation is not supported with Home Agent redundancy.
•
Resource Revocation and Bind Update cannot be enabled simultaneously. Both are mutually
exclusive of each other.
exclusive of each other.
•
The Home Agent MIB is not updated with the Registration revocation information.
•
Mobile IP conditional debugging is not supported.