Changes between Version 12 and Version 13 of Internal/SystemPrototyping/Workingdocuments/SpecificationsV10

Timestamp:

Aug 9, 2013, 8:15:53 PM (11 years ago)

Author:

nkiran

Comment:

--

Internal/SystemPrototyping/Workingdocuments/SpecificationsV10

@@ -16 +16 @@
 ==== MF Packet =====
 
-{{{
+
 An MF packet is more appropriately a PDU or APDU that tries to balance 
 requirements from both application and network sides, consequently providing high
@@ -25 +25 @@
 
 
-
+{{{
 
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -48 +48 @@
       ~                                                               ~
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-
+}}}
 
 === Storage Aware Routing ===
@@ -80 +80 @@
                                               LNRS servers          GNRS servers 
 
+}}}
+
 A host/client may interact with the name resolution service to either (1) report
 or update it's present network address binding(s), or, (2) to query corresponding
@@ -108 +110 @@
 routed directly back to the original requesting client - doesn't need to retrace
 onward path.
-}}}
+
 
 
  
 ==== Requests ====
-
-{{{
 
 The name resolution service supports 3 types of requests from a client: insert, 
@@ -129 +129 @@
 The following is the general format of a request message:
 
+
+{{{
 
        0                   1                   2                   3
@@ -162 +164 @@
 ===== Insert/Update Request =====
   
-{{{ 
+
 An insert or update involves reporting new network location bindings to 
 the name resolution service. 
@@ -168 +170 @@
 Following is the format for payload in a insert/update request.
 
-       0                   1                   2                   3
+{{{  
+      0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -212 +215 @@
 ===== Lookup Request =====
 
-{{{  
+ 
 A lookup is performed to determine the present network location binding(s) 
 of a network entity.
 
-
+{{{ 
        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
@@ -230 +233 @@
 ==== Response Messages ====
 
-{{{
+
 As indicated in arch. figure above, responses may be generated at any level in the NRS 
 hierarchy, condition to the options stated in request. The response contains both the
@@ -238 +241 @@
 Following is the format of header fields of a response message:
 
+{{{
        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
@@ -272 +276 @@
 ===== Insert/Update Response =====
 
-{{{
 The payload is empty for responses to insert or update requests.
-}}}
+
 
 ===== Lookup Response =====
-
-{{{
 
 The payload in a lookup response contains the network address bindings for the
 requested GUID, and follows format in the insert/update requests.
+
+{{{
 
        0                   1                   2                   3
@@ -350 +353 @@
 || Compute Layer Processing || 0x0800 ||
 || Source Routing || 0x1000 || ||
-|| Endpoint Broadcast || 0x2000 || Request broadcast of data block by the destination, for example when addressing an access point. In effective when the destination has no mechanism to do broadcast.||
+|| Endpoint Broadcast || 0x2000 || Request broadcast of the data block at the destination, for example when addressing an access point. Ineffective when the destination has no mechanism to do broadcast ||
 || Future 1 || 0x4000 || ||
 || Extensions || 0x8000 || ||