Requirements For Handover Event/Command Services MIPSHOP – IETF #65

1. Requirements For Handover Event/Command ServicesMIPSHOP – IETF #65 Srinivas Sreemanthula (Ed.)

2. Introduction • What’s present in the slides? • Internet Draft location discussed here • http://www.ietf.org/internet-drafts/draft-sreemanthula-es-cs-problem-02.txt • Requirements to enable media independent event and command services (MECS) used in handovers • Within IEEE 802.21 framework • IETF to enable MECS over IP networks • Why? MECS could be an IP end point • IETF Scope • define suitable transport for MECS • define discovery and security for MECS • Commonality with MIS work item (without assuming co-location) • IEEE 802.21 model discussion

3. MES – What’s Inside? Event sources (others) • MES provides current link or new link status information to remote end point • Examples: new-link-detect, link-up, link-going-down • Useful for network selection Local Events Remote Events (MES) MIH Function Local Events Event sources (link)

4. MCS – What’s Inside? Command sources • MCS provides mechanism for one point to request execution of certain commands in the remote end point • Examples: link-scan, link-switch • Execution of commands may impact the current link connectivity • Useful for network selection and handover control • Works in complement with IP mobility protocols e.g. • No IP address updates • No tunnel setups Local Commands Remote Commands (MCS) MIH Function

5. Usage Models • Direct Model Terminal MECS MECS Exchange Network MECS UNC • Split Model Terminal MECS Network MECS (proxy/server) Network MECS MECS Exchg. MECS Exchg. UNC NNC UNC – User to Network Comm. NNC – Network to Network Comm.

6. Usage Scenario: Network Selection • Network selection is to determine suitable network in the presence of two or more links • Terminal or Network can do the network selection • Network selection in network allows service providers to provide better user experience to users e.g. QoS, cost IPNetwork 4. Network selection Network MES Serving Access Network Access Network #2 Access Network #1 3. MES (link-detect) 1. Broadcast 1. Broadcast 2. Generate event link-detect

7. Usage Scenario: Handover Control • Network selection is to determine suitable network in the presence of two or more links • Terminal or Network can do the network selection • Network selection in network allows service providers to provide better user experience to users e.g. QoS, cost IPNetwork 1. Network selection Network MCS 6. MCS (link-switch-resp) Serving Access Network Target Access Network 2. MCS (link-switch-req) 5. IP level Handover 3. Execute Command 4. Initiate Mobility Signaling

8. MECS RequirementsDiscovery • Enable terminal end points or network end points to discover IPv4/IPv6 contact information of the MECS end points • Common discovery mechanism (not based on MECS end point location) • Protect against discovery service impersonation and modification attacks • Allow discovery for more than one MECS end point at a time • Optionally allow MECS discovery to be compatible with MIS *No new discovery solution required, existing ones should suffice

9. MECS RequirementsTransport • Provide transport for MECS without assumption on end point location • within subnet, • same domain or • different domain • Both IPv4 and IPv6 capability • NAT traversal for IPv4 • FW traversal for IPv4/IPv6 • Efficient, optimized and timely delivery of MECS communication

10. MECS RequirementsSecurity • IETF has sole responsibility for security aspects • Provide SA negotiation mechanism • without assumption on MECS end point within subnet, same domain or different domain • With mobility considerations (fast SA setup) • Provide security • against MECS end point impersonation • peer/mutual authentication • message authentication and confidentiality • against replay attacks • for identity against eavesdroppers • security for DoS attacks • Independent of MIS payload • Capability to disable security features • Optionally allow compatibility with MIS

11. Thank You! Questions?