Requirements For Handover Information Services MIPSHOP – IETF #65 Srinivas Sreemanthula (Ed.)

Slides:



Advertisements
Similar presentations
Doc.: IEEE /087 Submission May, 2000 Steven Gray, NOKIA Jyri Rinnemaa, Jouni Mikkonen Nokia Slide 1.
Advertisements

IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec Title: Initiate An Exercise for Generating a 21a Document Date Submitted: September 21, 2009.
1 IEEE Media Independent Handoff Overview of services and scenarios for 3GPP2 Stefano M. Faccin Liaison officer to 3GPP2.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Network Controlled Network Selection and HO scenarios Date Submitted: September,
Doc.: Handoff_WNG_Presentation r3 Submission July David Johnston, IntelSlide Handoff Presentation to WNG David Johnston.
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: LB1c-handover-issues.ppt Title: MIH Security – What is it? Date Submitted:
sec IEEE MEDIA INDEPENDENT HANDOVER DCN: sec-mih-level-security-considerations Title: MIH-level Security Considerations.
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: LB1c-handover-issues.ppt Title: MIH Security – What is it? Date Submitted:
Network Initiated Handovers T. Melia, J. Korhonen, R. Aguiar, S. Sreemanthula, V. Gupta Based on draft-melia-mipshop-niho-ps-00.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Protocol Security Date Submitted: December, 2007 Presented.
I-D: draft-rahman-mipshop-mih-transport-01.txt Transport of Media Independent Handover Messages Over IP 67 th IETF Annual Meeting MIPSHOP Working Group.
68 th IETF, Prague Czech Republic Issues with L2 abstractions and how they affect QOS-based handovers Nada Golmie Advanced Networking Technologies Division.
DCN: March 7, 2005 IETF 62 - Minneapolis, MN Media Independent Handover Services and Interoperability Ajay Rajkumar Chair, IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIIS and Its Higher Layer Transport Requirements: Ad hoc Update and Discussion on.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH_Handover primitives and scenarios Date Submitted: April, 30,
Doc.: IEEE /495r1 Submission July 2001 Jon Edney, NokiaSlide 1 Ad-Hoc Group Requirements Report Group met twice - total 5 hours Group size ranged.
Doc.: 802_Handoff_WMAN_Presentation Submission July David Johnston, IntelSlide Handoff A Technical Preview David Johnston
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Detailed analysis on MIA/MSA architecture Date Submitted: January 5, 2010 Present.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IEEE Key Features Date Submitted: July 13, 2010 Presented.
Some use cases and requirements for handover Information Services Greg Daley MIPSHOP Session IETF 64.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Analysis on Identifiers Date Submitted: January 9, 2006 Presented.
MIPSHOP – November, 2005 Event Services and Command Services for Media Independent Handover Presentation prepared by: Srini Sreemanthula Presented by:
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Subscription ID Scope Date Submitted: June, 14 th, 2007 Presented.
Securing Data Transmission and Authentication. Securing Traffic with IPSec IPSec allows us to protect our network from within IPSec secures the IP protocol.
Doc.: IEEE /0310r0 Submission Sept 2007 Srinivas Sreemanthula Slide 1 IEEE MEDIA INDEPENDENT HANDOVER DCN: MIH-Security-Options.ppt.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Capability Discovery Amendment Date Submitted: April 20, 2006.
August 2, 2005 IETF 63 – Paris, France Media Independent Handover Services and Interoperability Ajay Rajkumar Chair, IEEE WG.
Design Considerations for the Common MIH Protocol Functions draft-hepworth-mipshop-mih-design-considerations-01 Ele Hepworth (*), Robert Hancock, Srinivas.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: September,
Computer Science and Engineering Computer System Security CSE 5339/7339 Session 27 November 23, 2004.
IEEE MEDIA INDEPENDENT HANDOVER DCN: hwnm Title: Thoughts on IEEE relation with IEEE Date Submitted: May 13, 2010.
Problem Statement: Media Independent Handover Signalling draft-hepworth-mipshop-mih-problem-statement-01 Ele Hepworth (*), Greg Daley, Srinivas Sreemanthula,
Trend of Mobility Management Yen-Wen Chen Ref: 1.Draft IEEE Standard for Local and Metropolitan Area Networks: Media Independent Handover Services 2.Transport.
Transport of Media Independent HO Messages over IP
Media-Independent Pre-authentication (MPA) Framework
IEEE MEDIA INDEPENDENT HANDOVER
draft-corujo-ps-common-interfaces-lmm-00
Proposal for IEEE solution
Media Independent Handover Services and Interoperability
Media Independent Coexistence
Maryna Komarova (ENST)
An Update on Multihoming in IPv6 Report on IETF Activity
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
Abstract: Relationship between and
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE P vs IEEE Date: Authors:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
Motivation L3 enable both scenarios under
Media Independent Coexistence
Media Independent Coexistence
Media Independent Coexistence
Media Independent Coexistence
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
Presentation transcript:

Requirements For Handover Information Services MIPSHOP – IETF #65 Srinivas Sreemanthula (Ed.)

Introduction What’s present in the slides? Internet Draft location discussed here  infoserv-02.txt infoserv-02.txt Requirements to enable media independent information services (MIS) used in handovers  Within IEEE framework IETF to enable MIS over IP networks  Why? MIS provider could be an IP end point IETF Scope  define suitable transport for MIS  define discovery and security for MIS

IEEE Provides handover aiding services to be used in co-ordination with existing handover signaling mechanisms Works on media independent handover problem to enable handovers between  different 802 wireless and wireline systems  different 802 and cellular systems Provides a shim layer (MIHF) within a host to exchange  standardized link layer information over LINK- SAP  standardized app/higher layer information over MIH-SAP MIHF are located in compliant terminals and network end points (AP, AR, others) MIH Function Link Layers MIH Users LINK-SAP MIH-SAP

IEEE contd. Defines transport-independent protocol for peer MIHF communication  transported as MAC payload or IP payload Functionality split between  Information Services (MIS)  Event Services (MES)  Command Services (MCS)  (System management Services) MIH Function Remote MIS, MES & MCS MIH Function

MIS – What’s Inside? MIS provides network and link layer attachment point information to allow handover decision engines to make appropriate network selection for handover reasons Example: Serving Access Network Access Network #1 Access Network #2 IP Network MIS Provider 1. Broadcast 2. MIS Query 3. Select 4. Initiate Mobility Signaling 4. handover

Usage Models Direct Model MIS User MIS Query MIS Provider UNC MIS User MIS Query MIS Provider MIS Provider (proxy/server) MIS Query UNCNNC UNC – User to Network Comm. NNC – Network to Network Comm. Split Model

Message Exchange & Scope* MIS User MIS Provider MIS Discovery Req MIS Discovery Resp Build SA Start Connection MIS Query Req MIS Query Resp IETF Scope IEEE Scope+ IETF Security Discovery Service *Example only, some steps can be skipped

MIS Requirements Discovery Enable terminal end points or network end points to discover IPv4/IPv6 contact information of the MIS providers Common discovery mechanism (not based on MIS provider location) Protect against discovery service impersonation and modification attacks Allow discovery for more than one MIS provider at a time Allow distinct classes of MIS providers  Some capability recently added into IEEE Optionally allow MIS discovery to be compatible with MES/MCS *Intention is not to create a new discovery mechanism (use existing ones)

MIS Requirements Transport Provide transport for MIS without assumption on MIS provider location  within subnet,  same domain or  different domain Both IPv4 and IPv6 capability NAT traversal for IPv4 FW traversal for IPv4/IPv6

MIS Requirements Security IETF has sole responsibility for security aspects Provide SA negotiation mechanism  without assumption on MIS provider location within subnet, same domain or different domain  With mobility considerations (fast SA setup) Provide security  against MIS user/provider 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 MES/MCS

Thank You! Questions?