draft-ietf-mext-binding-revocation-09.txt   draft-ietf-mext-binding-revocation-10.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Intended status: Standards Track Nortel Intended status: Standards Track Nortel
Expires: February 16, 2010 S. Gundavelli Expires: February 16, 2010 S. Gundavelli
Cisco Systems Cisco Systems
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
P. Yegani P. Yegani
Juniper Networks Juniper Networks
August 15, 2009 August 15, 2009
Binding Revocation for IPv6 Mobility Binding Revocation for IPv6 Mobility
draft-ietf-mext-binding-revocation-09.txt draft-ietf-mext-binding-revocation-10.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 24, line 16 skipping to change at page 24, line 16
include any of the BID mobility options. include any of the BID mobility options.
8.2. Receiving Binding Revocation Acknowledgement 8.2. Receiving Binding Revocation Acknowledgement
When the home agent receives a packet carrying a valid Binding When the home agent receives a packet carrying a valid Binding
Revocation Acknowledgement that was successfully processed as in Revocation Acknowledgement that was successfully processed as in
Section 7.2, the home agent SHOULD examine the Status field as Section 7.2, the home agent SHOULD examine the Status field as
follows: follows:
o If the Status field indicates that the Binding Revocation o If the Status field indicates that the Binding Revocation
Indication was processed successfully, the home agent deletes the Indication was processed successfully, the home agent MUST delete
current timer and the mobile node bindings and all related the current timer and the mobile node bindings and all related
resources. resources.
o If the Status field indicates any value other than success, the o If the Status field indicates any value other than success, the
home agent SHOULD examine any mobility options included in the home agent SHOULD examine any mobility options included in the
Binding Revocation Acknowledgement. The home agent MAY log the Binding Revocation Acknowledgement. In this case, it is based on
appropriate event to reflect the received status. the home agent local policy how to handle the mobile node BCE.
The home agent MAY log the appropriate event to reflect the
received status.
9. Local Mobility Anchor Operation 9. Local Mobility Anchor Operation
9.1. Binding Revocation Initiator 9.1. Binding Revocation Initiator
9.1.1. Sending Binding Revocation Indication 9.1.1. Sending Binding Revocation Indication
To terminate a mobile node PMIPv6 registration and its current To terminate a mobile node PMIPv6 registration and its current
binding with the local mobility anchor, the local mobility anchor binding with the local mobility anchor, the local mobility anchor
sends a packet to the mobile access gateway containing a Binding sends a packet to the mobile access gateway containing a Binding
skipping to change at page 35, line 20 skipping to change at page 35, line 20
received Binding Revocation Acknowledgement as per the followings: received Binding Revocation Acknowledgement as per the followings:
o When the mobile access gateway receives a packet carrying a valid o When the mobile access gateway receives a packet carrying a valid
Binding Revocation Acknowledgement and the Global (G) and Proxy Binding Revocation Acknowledgement and the Global (G) and Proxy
Binding (P) bits are set and the mobile nodes BCEs are in the Binding (P) bits are set and the mobile nodes BCEs are in the
state of Revocation in Progress, the mobile access gateway SHOULD state of Revocation in Progress, the mobile access gateway SHOULD
examine the Status field as follows: examine the Status field as follows:
o If the Status field indicates that the Binding Revocation o If the Status field indicates that the Binding Revocation
Indication was processed successfully, the mobile access gateway Indication was processed successfully, the mobile access gateway
delete the current timer and the mobile nodes proxy bindings and MUST delete the current timer and the mobile nodes proxy bindings
all associated resources. and all associated resources.
o If the Status field indicates (Global Revocation NOT Authorized), o If the Status field indicates (Global Revocation NOT Authorized),
the mobile access gateway is not authorized to participate in a the mobile access gateway is not authorized to participate in a
Per-Peer Global Revocation. The mobile access gateway SHOULD NOT Per-Peer Global Revocation. The mobile access gateway SHOULD NOT
retry sending a Binding Revocation Indication with the Global (G) retry sending a Binding Revocation Indication with the Global (G)
bit set to the same local mobility agent. The mobile access bit set to the same local mobility agent. The mobile access
gateway should raise an alarm or log an event to indicate this gateway should raise an alarm or log an event to indicate this
rejection. rejection.
11. Mobile Node Operation 11. Mobile Node Operation
 End of changes. 4 change blocks. 
7 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/