Application Programming Interface to a Trigger Database for MOBIKE
description
Transcript of Application Programming Interface to a Trigger Database for MOBIKE
Application Programming Interface to a Trigger Database for MOBIKE
<draft-schilcher-mobike-trigger-api-02.txt >
Udo Schilcher
Hannes Tschofenig
Franz Muenz
Motivation
• MOBIKE has to maintain an address list for all available interfaces
• Many events for changing the address set are out of scope of MOBIKE,e.g., IEEE 802.21 Media Independent Handover (MIH)
• These information have to be combined with higher layer information
Scope of the MOBIKE work
B
A
Mobility control
Policy
SEND
NUD
MOBIKE IKEv2
R1
GPRSphone
SGSN
BSS
GGSNR2
BT IrDA
AP1
AP2
PPPIPv4
IPv6TCP
ESP
DNA 802.3
802.11
802.21
MOBIKE
playground
Making Information available
to various protocols
Features
• Define an API to insert these information (so called triggers) into a DB
• Triggers can be provided to MOBIKE and other higher layer protocols
• Offered services are quite similar to MIH,but can be extended for other protocols
• PF_TRIGGER IF is analogue to PF_KEY
(based on BSD routing socket API)
Note: Please do not misunderstand the term „database“.
We solicit input for better terminology here.
High-Level Interaction
Trigger Database
Media Independent Handover
Lower Layers (Layer 2 and below)
MOBIKE daemon
PF_TRIGGER socket
TDB Events TDB Commands
MIH Events MIH CommandsInformation
Service
Link Events Link CommandsInformation
Service
Optional; integration withIEEE 802.21 could be useful.
Conclusion
• This is an attempt to define an API to make mobility related information available.
• Please let us know if you think that this work is useful.
• Code might be available in the near future.