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-mihinfoserv-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


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



Provides a shim layer (MIHF) within a
host to exchange



different 802 wireless and wireline systems
different 802 and cellular systems
standardized link layer information over LINKSAP
standardized app/higher layer information
over MIH-SAP
MIHF are located in compliant terminals
and network end points (AP, AR, others)
MIH Users
MIH-SAP
MIH Function
LINK-SAP
Link Layers
IEEE 802.21

Defines transport-independent protocol for peer MIHF
communication


contd.
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:
IP Network
MIS
Provider
Serving
Access
Network
Access
Network #2
2. MIS Query
1. Broadcast
Access
Network #1
4. handover
1. Broadcast
3. Select
4. Initiate Mobility Signaling
Usage Models

Direct Model
MIS
User

MIS Query
UNC
MIS
Provider
Split Model
MIS
User
MIS Query
UNC
MIS Provider MIS Query
(proxy/server)
NNC
UNC – User to Network Comm.
NNC – Network to Network Comm.
MIS
Provider
Message Exchange & Scope*
MIS
User
Discovery
Service
MIS Discovery Req
MIS Discovery Resp
IETF
Scope
Start Connection
Build SA
IEEE
Scope+
IETF
Security
*Example only, some steps can be skipped
MIS Query Req
MIS Query Resp
MIS
Provider
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 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

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



Provide security









without assumption on MIS provider location within subnet, same
domain or different domain
With mobility considerations (fast SA setup)
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?