Re: [MEXT] Revocation Status Values

["Ahmad Muhanna" <amuhanna at nortel.com>]

Hi Vijay,

They sound similar but the scenarios are different. Probably we need a
better naming for the second one.

128 "Binding Does NOT Exist" When the information included in the BRI is
enough to identify the mobile node binding BUT it happened that the
binding does not exist or maybe has been released a little earlier
possibly a race condition.

132 "CAN NOT Identify Binding" The case when the information or the
mobility options included in the BRI is NOT enough to identify a mobile
node binding, then the MAG would send this status to indicate that more
information is needed.

Here is the related text:

  o   If the Global (G) bit is set and the Revocation Trigger field is
      set to "Revoking Mobility Node Local Policy", and no mobility
      options are included in the Binding Revocation Indication message
      or the MAG is not able to identify the impacted mobile nodes
      bindings based on the included mobility options, the MAG MUST
      treat this as an error scenario.  In this case, the MAG SHOULD
      send a Binding Revocation Acknowledgement message with status "CAN
      NOT Identify Binding".

Actually this text should say:

  o   If the Global (G) bit is set and the Revocation Trigger field is
      set to "Revoking Mobility Node Local Policy" and no mobility
      options are included in the Binding Revocation Indication message,
      the MAG will not able to identify the impacted mobile nodes
      bindings. In this case, the MAG MUST treat this as an error
scenario
      and reject the BRI by sending a BRA message with status value "CAN
NOT Identify Binding"

On the other hand, at any point the MAG is NOT able to locate the MN
binding while the included options are enough to identify the binding,
the MAG will send status "Binding does NOT exist"

Is this change acceptable?


Regards,
Ahmad
 

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay at wichorus.com] 
> Sent: Tuesday, March 24, 2009 6:11 PM
> To: Muhanna, Ahmad (RICH1:2H10)
> Cc: mext
> Subject: Revocation Status Values
> 
> Hello,
> 
> draft-ietf-mext-binding-revocation-04.txt defines the 
> following status value for the Binding Revocation Ack message.
> 
>        0  success
>        1  partial success
>        128  Binding Does NOT Exist
>        129  IPv4 HoA Binding Does NOT Exist
>        130  IPv4 Home Address Option Required
>        131  Global Revocation NOT Authorized
>        132  CAN NOT Identify Binding
>        133  Revocation Failed - MN is Attached
> 
> Isnt '128' the same as '132'?
> 
> Vijay
>