Specifications

The following sections detail the specifications for a prototype MobilityFirst Network, and includes details of overall architecture, network elements, software services, protocols, end-host stack and network API.

Host - GNRS interaction

Early-binding

• It is assumed that an end-host has obtained the GUID(s) of the other communication end-point or network entity through an out-of-band mechanism.
• A host can initiate communication through one of the following API:
  • sendTo(GUID, message, [serviceId], [serviceOptios], ...)
  • get(GUID, ...)
  • ....
• Implementations of the above API within the end-host's MF stack execute early-binding when requested
• A GNRS lookup message (GL-msg) is prepared for the dest-GUID. See section on GNRS message specification for included fields.
• Target NRS server: A default or preferred server may be specified in a local config file, or one obtained by listening to local advertisements
• GL-msg is sent out on the default interface for GNRS lookups
• Closest or preferred NRS server will execute the actual lookup on the GNRS service plane
• A GNRS lookup response (GLR-msg) prepared by server with mapping is routed to the querying entity, and is picked up by the stack
• End-host stack inserts the network address from GLR-msg into the message header and transmits the packet on appropriate interface