Version 7 (modified by chyz198, 8 years ago) (diff)



Client Stack has following requirements in order to support features of MobilityFirst,

  • Separation of naming and addressing
  • Hop-by-hop link level data transfer
  • Ad-hoc routing support
  • Multi-homing support


 Handle  <---- Open (scheme<GUID>, options)
 Send (handle, message, size, options)
 Sendto (handle, message, size, GUID, options)
 Recv (handle, buffer, size, &src-GUID, options)
 Recvfrom (handle, buffer, GUID, size, options)
 Close (handle)

'scheme' : Capture application intents & Enable protocol customization

A example of 'scheme': video-s://

  • 'video', a real time application, no end-to-end reliability
  • 's', security layer required
  • '', resolved to a GUID

Layering in MF Client Stack

Attachments (6)

Download all attachments as: .zip