Requirements for handover information services mipshop ietf 65
This presentation is the property of its rightful owner.
Sponsored Links
1 / 11

Requirements For Handover Information Services MIPSHOP – IETF #65 PowerPoint PPT Presentation


  • 63 Views
  • Uploaded on
  • Presentation posted in: General

Requirements For Handover Information Services MIPSHOP – IETF #65. Srinivas Sreemanthula (Ed.). Introduction. What’s present in the slides? Internet Draft location discussed here http://www.ietf.org/internet-drafts/draft-faccin-mih-infoserv-02.txt

Download Presentation

Requirements For Handover Information Services MIPSHOP – IETF #65

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Requirements for handover information services mipshop ietf 65

Requirements For Handover Information ServicesMIPSHOP – IETF #65

Srinivas Sreemanthula (Ed.)


Introduction

Introduction

  • What’s present in the slides?

  • Internet Draft location discussed here

    • http://www.ietf.org/internet-drafts/draft-faccin-mih-infoserv-02.txt

  • Requirements to enable media independent information services (MIS) used in handovers

    • Within IEEE 802.21 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 802 21

IEEE 802.21

MIH Users

  • 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-SAP

MIH Function

LINK-SAP

Link Layers


Ieee 802 21 contd

IEEE 802.21contd.

  • 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

MIH

Function

Remote

MIS, MES & MCS


Mis what s inside

IPNetwork

MIS

Provider

Serving

Access

Network

Access

Network #2

Access

Network #1

2. MIS Query

4. handover

1. Broadcast

1. Broadcast

3. Select

4. Initiate Mobility Signaling

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:


Usage models

Usage Models

  • Direct Model

MIS

User

MIS Query

MIS

Provider

UNC

  • Split Model

MIS

User

MIS Provider

(proxy/server)

MIS

Provider

MIS Query

MIS Query

UNC

NNC

UNC – User to Network Comm.

NNC – Network to Network Comm.


Message exchange scope

MIS

User

Message Exchange & Scope*

Discovery

Service

MIS

Provider

MIS Discovery Req

MIS Discovery Resp

IETF

Scope

Start Connection

Build SA

MIS Query Req

IEEE

Scope+

IETF

Security

MIS Query Resp

*Example only, some steps can be skipped


Mis requirements discovery

MIS RequirementsDiscovery

  • 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 802.21

  • 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

MIS RequirementsTransport

  • 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

MIS RequirementsSecurity

  • 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


Requirements for handover information services mipshop ietf 65

Thank You!

Questions?


  • Login