Re: [MEXT] Binding Revocation for IPv6 Mobility Supports NEMO usecase

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

Hi Desire,

 

Added a relative subject.

 

I guess the usecase is clear and it makes sense to me.

We can add some text similar to yours to capture this functionality under the HA and MN operations after the conclusion of the WGLC..

 

BTW: Is there anyone who thinks that we should not add this usecase?

Regards,
Ahmad

 

---

From: Desire Oulai [mailto:desire.oulai at ericsson.com]
Sent: Monday, December 01, 2008 2:46 PM
To: mext at ietf.org
Cc: Muhanna, Ahmad (RICH1:2H10)
Subject:

Hi Ahmad, All,

 The Binding revocation draft does not mention revocation related to NEMO. If used as is, the BRI will revoke the binding between the MR's HoA and CoA. I think it's woth adding another level of revocation: revocation of Mobile Network Prefixes. A HA may decide to stop forwarding data to the CoA for certain MNPs and BR could be used for that. Here is a proposed text for a new section:

"In case of NEMO protocol, the HA follows the same procedure as MIPv6 if the goal is to revoke the binding between the Mobile Router's HoA and CoA. It is also possible to have finer granularity of revocation targeting the Mobile Network Prefixes assigned to the Mobile Router. In this case, the HA sends a BRI message including one or more MNP options with the A bit set and the Revocation Trigger set to a proper value, e.g. Administrative Reasons. When receiving this BRI, the MR deletes the MNP(s) from the Prefix Information field in the Binding Update List and responds with a BRA message. The BRA MUST include the MNP(s) contained in the BRI."

Also, Mobile network Prefix should be addes as valid option in section "6.2. Binding Revocation Acknowledgement Message".

BR
Desire

_______________________________________________
MEXT mailing list
MEXT at ietf.org
https://www.ietf.org/mailman/listinfo/mext