Re: [MEXT] Revoking all bindings of an MN

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

Hi Suresh,

Probably what you meant is to modify the requirement under section 6.1.

What about the following:

   o  Home Network Prefix option [RFC5213].  This option is mandatory
      when the (P) bit is set and the BRI is used for revoking a single 
      binding cache entry.

What do you think?

Regards,
Ahmad
 

> -----Original Message-----
> From: mext-bounces at ietf.org [mailto:mext-bounces at ietf.org] On 
> Behalf Of Suresh Krishnan
> Sent: Tuesday, October 21, 2008 10:46 AM
> To: mext at ietf.org
> Subject: [MEXT] Revoking all bindings of an MN
> 
> Hi Folks,
>    Section 9.2.1 contains the following text about revoking 
> all PMIP bindings for a given MN-ID when no HNP is present
> 
> "
>         1. If only the mobile node identifier, MN-ID, option 
> is included,
>            the local mobility anchor MUST revoke all bindings for this
>            mobile node which have a proxy CoA that is used as 
> the source
>            of the IPv6 packet that carried the BRI or in the Alternate
>            Care-of-Address option in the BRI.
> "
> 
> I consider this to be a valid use case. But the text in 
> Section 6.1 about the P bit disallows this scenario
> 
> 
> "o  Home Network Prefix option [RFC5213].  This option is mandatory
>      when the (P) bit is set."
> 
> I request the authors to remove this restriction in section 6.1.
> 
> Cheers
> Suresh
> _______________________________________________
> MEXT mailing list
> MEXT at ietf.org
> https://www.ietf.org/mailman/listinfo/mext
> 
_______________________________________________
MEXT mailing list
MEXT at ietf.org
https://www.ietf.org/mailman/listinfo/mext