IETF76 - Netext WG1 draft-jeyatharan-netext-pmip- bulkpbu-bitmap-00 draft-jeyatharan-netext-pmip-bulkpbu-bitmap-00 Mohana Jeyatharan panasonic.com Chan-Wah Ng

IETF76 - Netext WG2 Agenda Background Other Generic Scenarios for Bulk PBU Optimization Bitmap based Bulk PBU optimization Approach Synergy with MN group ID approach Comments Received Way Forward

IETF76 - Netext WG3 Background There is interest in optimizing PBU messages –Netext WG draft: draft-premec-netlmm-bulk-re-registration- 03.txt Focused Scenarios in draft-premec-netlmm-bulk-re- registration-03.txt –MAG Performing bulk re-registration for multiple MNs tied to a MN group ID MAG sends MN group ID option in the re-registration PBU message –LMA performing bulk revocation of multiple MN bindings using MN group ID. LMA revoking bindings tied to a blade in the LMA blade architecture by sending revocation message with the MN group ID option attached –MAG performing bulk deletion of multiple MN bindings using MN group ID MAG deleting bindings tied to a blade in the LMA blade architecture by inserting a MN group ID option in de-registration PBU message

IETF76 - Netext WG4 Other Generic Scenarios for Bulk PBU Optimization Scenario 1: –Multiple new attachment requests arriving at MAG simultaneously and MAG performing multiple initial registration PBUs Scenario 2: –Multiple MN re-registrations at a new LMA due to shut down of the previous serving LMA in a LMA failure scenario LMA1 LMA2 MAG MAG performing multiple re- registration PBUs at LMA2 LMA1 failure MN1 MN2MN3 MN4 MN5 MAG LMA MN1 MN2 MN3 MN4 MN5 Simultaneous multiple initial registration events triggered at MAG MAG performing multiple initial registration PBUs Scenario 1 Scenario 2

IETF76 - Netext WG5 Other Generic Scenarios for Bulk PBU Optimization Scenario 3: –Multiple handoff requests arriving at MAG simultaneously and MAG performing multiple handoff registration PBUs Scenario 4: –Multiple detachment events detected at MAG simultaneously and MAG performing multiple de-registration PBUs. Scenario 5: –Multiple initial registrations, handoff registrations and re-registration events happening simultaneously at MAG and MAG performing multiple PBUs tied to different type of events. Simultaneous multiple handoff registration events at MAG Multiple detachment events detected at MAG MAG performing multiple de- registration PBUs MAG performing multiple handoff registration PBUs LMA MAG MN1 MN2 MN3 MN4 MN5 LMA MAG Scenario 3 Scenario 4 MN5 MN4 MN1 MN2 MN3

IETF76 - Netext WG6 Other Generic Scenarios for Bulk PBU Optimization Scenario 6: –MNs moving in group into MAG service area. As a result, MAG performing multiple handoff or multiple new attachment PBUs for MNs tied to group mobility. Scenario 7: –MAG offloading some MNs binding lists to another MAG for load balancing purpose. New MAG sends multiple PBU registrations for all the MNs that were transferred. Simultaneous multiple handoff events registered at MAG due to group mobility MAG performing multiple handoff registration PBUs LMA Scenario 6 Scenario 7 LMA New MAG performing multiple re-registration PBUs at LMA MAG1 overloaded MN1 MN2MN3 MN4 MN5 MAG1 MAG2 Transfer BLs of MN1~MN5 MNs moving and arriving in a group MAG

IETF76 - Netext WG7 Bitmap based Bulk PBU optimization Approach Bitmap Features –Feature 1: When multiple MNs are combined in the bulk PBU only a single instance of a given mobility option is explicitly attached to the Bulk PBU –Feature 2: A bitmap is attached as a mobility option to the bulk PBU, where each field of bitmap indicates usage of the attached mobility option by a given MN attached to the bulk PBU message. MN1: MN1-ID ATT1 HNP=P1 HI=1 MN2: MN2-ID ATT2 HNP=P2 HI= P1 P2 ATT1 ATT2 H1H2 MN1 MN2 Mobility Options: P1, P2 ATT1, ATT2 H1, H2 MAG Feature 1: A union of all unique mobility options tied to MNs Feature 2: Derived Bitmap

IETF76 - Netext WG8 Synergy with MN group ID Approach Usage of bitmap with MN group ID Approach –Use Case 1: MAG sending a bitmap based bulk PBU and requesting MNs to join MN group identifiers. –Use Case 2: MAG assigning mobility options to already assigned MN group Identifiers. –Use Case 3: MAG sending a bulk PBU containing information pertaining to both grouped and un-grouped mobile nodes.

IETF76 - Netext WG9 Comments Received Is this necessary for bulk re-registration scenario? –Answer: –Necessary when LMA is changed due to failure. –Necessary when bulk re-registration for MN group ID is combined with bulk initial registration of multiple MNs. Is there a scenario where MAG want to re-assign the MNs to another group and hence bitmap based approach can be used. –Answer: –Can happen in LMA blade architecture. If one blade has failed MAG may want to reassign or re- distribute the MNs to other MN group IDs. It can also happen in LMA failure scenario. –Some MNs have left the MAG service area. The MAG want to collapse the remaining MNs to some other groups to reduce the number of groups maintained. In such cases, the regrouping of already registered MNs can be dome as a re-registration PBU using bitmaps to indicate which MN-ID belongs to which MN group ID. Draft needs to capture use case where bulk arrival of handoff events occur. It is good to capture these in the draft. –Answer: Will capture these in revised draft. Currently mentioned in slide 4. In which scenarios the bulk pbu bitmap based approach can be used that is different from the bulk PBU re-registration method Query on more practical scenarios where the bitmap based approach can be used. –Answer: Some of these are captured in the slide 4, 5 and 6. Can illustrate these in the revised ID.

IETF76 - Netext WG10 Way Forward Do people think that this approach can be used in the scenarios proposed? Do people think that the method can be used along with the MN group ID approach? Any possibility in adopting it as a WG item?