Binding Revocation for IPv6 Mobility draft-muhanna-mip6-binding-revocation-01.txt MIP6 WG, IETF 69 Ahmad Muhanna Mohamed Khalil Sri Gundavelli K. Chowdhury Parviz Yegani

Overview Need for Binding Revocation in IPv6 Mobility Binding Revocation Scenarios –Mobile IPv6 –Monami6 –PMIPv6 Binding Revocation Messages Format Why Message Format for Binding Revocation Conclusions Next Steps

Need for Binding Revocation in IPv6 Mobility Home Agent Revokes Mobile Node’s binding for Administrative Reasons Network Resource Optimization Gracefully Revoke multiple sessions before scheduled or emergency system maintenance Avoid out of sync state between MN and mobility entities

Binding Revocation Scenarios MIPv6 Scenarios : –HA revokes all user bindings for admin reason using NAI option. –HA revokes a MN binding using HoA/ CoA option. Monami6 Scenarios : –Revoking a single Binding using BID option. –Revoking Multiple Bindings using multiple BID options. –Revoking All Bindings PMIPv6 Scenarios : –MAG Revokes a MN binding after exiting Network –LMA Revokes a MN binding for MAG to cleanup resources –Bulk Binding terminations, e.g. LMA is going through an unscheduled maintenance.

Binding Revocation Message Format Payload Prot. Header Len Checksum GNM Sub-Type Sequence Number Reserved MH TypeReserved P A G Mobility Options Mob Hdr Revocation Indication –Binding Revocation Indication: MH Type =Generic Notification Message (TBD) GNM Sub-Type:Binding Revocation Indication (TBD)

Binding Revocation Message Format –Binding Revocation Ack: Payload Prot. Header Len Checksum GNM Sub-Type Sequence Number Reserved MH TypeReserved P Mobility Options Mob. Hdr Revocation Ack. Status MH Type =Generic Notification Message (TBD) GNM Sub-Type:Binding Revocation Ack. (TBD)

Binding Revocation Message Format Binding Revocation Messages use Generic Notification Message Format. Each Message use a different subtype value avoiding the use of new MH types. Binding Revocation is used in many different scenarios where one or several options is needed to identify the action at the receiving end. e.g. –HoA address. –Care-of-Address option –Mobile Node ID, e.g. NAI –HNP Option –One or several BID options

Why Message Format for Binding Revocation Different type of options can be carried to identify the scenarios Multiple options of the same type or different types can be used to identify different scenarios Can be expanded to address future revocation scenarios which may require new options Allows the flexibility for using a separate sequence number and status spaces

Conclusions Binding Revocation is Needed for optimizing Network resources and give operators control on Serving a MN. Binding Revocation is applicable to several IP mobility related wgs MIPv6, MONAMI6, and PMIPv6. Message format gives the flexibility to use binding revocation for many different scenario. Using subtypes of the Generic Notification Message MH type preserve the MH type space.

Next Steps Adopting draft-muhanna-mip6-binding- revocation-01.txt as a MIP6 WG document. Adding the Binding Revocation to the MIP6 Charter.