Changes between Version 36 and Version 37 of WikiStart

Timestamp:

Jun 9, 2015, 4:39:07 PM (9 years ago)

Author:

wontoniii

Comment:

--

WikiStart

@@ -23 +23 @@
 
 ==== Named Based Services ====
+
 [[Image(namedAPI.png, 800, nolink, align=center)]]
 
+At the core of the architecture is a name-based networking abstraction that contrasts with the name-address conflated communication interface associated with Berkeley sockets and the TCP/IP stack. All network-attached objects in the MobilityFirst architecture enjoy direct addressability through long lasting unique network names or identifiers (we use GUIDs). This new GUID-centric network service API, first presented in [10] offers network primitives for basic messaging (send, recv) and content operations (get and post) while supporting several delivery modes innately supported by the MF network such as multihoming, multicast, anycast and DTN delivery. Combined with the GUID indirection and group- ing (GUID mapped to one or more other GUIDs) concepts supported by the naming services, the new communication API can produce novel addressing and delivery capabilities only indirectly possible (and with certain in-efficiency) in today’s IP architecture. Supporting the variety of services that are introduced in this API are then fundamental towards the validation of the architecture design.
 
 === Hybrid GUID/NA Routing and Forwarding ===
 [[Image(hybrid-guid-na.png, 800, nolink, align=center)]]
+
 !MobilityFirst naming involves three layers: User level descriptor, such as Joe's car or John's mobile is  first translated into a network level identifier. This is the globally unique identifier (GUID) that is a long lasting identifier at the network level. Next, in order to deliver packet to the end points, a GUID needs to be mapped to the current location of the GUID in the network. The mapping of the identifier to its routable network address (NA) is maintained by the global name resolution service (GNRS).
-As seen from the packet structure: [[Image(packet_structure.png, 300)]]
+As seen from the packet structure:
+
+[[Image(packet_structure.png, 300)]]
 
 data for an end-host is addressed both by its GUID and the NA it is currently attached to. Address can be resolved incrementally as the packet progresses through the network. 
@@ -61 +66 @@
 }}}
 
-