|
copying the lists.
Regards, From: Muhanna, Ahmad (RICH1:2H10) Sent: Wednesday, August 19, 2009 1:57 AM To: Tina TSOU; ops-dir at ietf.org Cc: draft-ietf-mext-binding-revocation at tools.ietf.org Subject: RE: Comments on draft-ietf-mext-binding-revocation-08 Hello Tina,
Initially the NEMO case was part of the Binding Revocation
presentations that were made in, at least, two IETF meetings. However, based on
further discussion on the MEXT/Netlmm mailing lists, the wg failed to find a use
for Binding Revocation in the case of NEMO for the following
reasons:
1. The MNP is allocated via a mechanism other than the
BU/BA signaling. In other words, DHCP could be an option. Therefore, the
argument was made that there is no justification for the home agent to send a
Binding Revocation Indication message in order to revoke a specific
MNP.
2. On the other hand, at any time the MR would like to
revoke a specific MNP binding to its home address, the MR can send a BU with the
remaining MNPs that still valid and the home agent will update the MR BCE
accordingly. In addition, the MR can send a de-registration to de-register all
MNPs is a single message.
3. In the case that BU/BA is used for allocating MNP(s) to
a specific MR with a specific HoA, then Binding Revocation makes sense, but, at
the time of discussing this issue that mechanism for MNP allocation was NOT
available or standardized.
I hope this addresses your concern.
Regards,
|