node’s data structures in memory. The does not include the overhead of exchanging control instructions in its simulation results.

 Behavior
---------

Since implements the entire network stack, our protocols define groups of packets generated by one source node destined to another node as a message. A message is equivalent to RFC-5050’s bundles as the base unit of data. The packets used to share routing information between nodes are control packets. Control packets are not messages because they are routing protocol specific, so they are not the base unit of data. Our protocols assume an -based convergence layer. Unlike the , cannot generate a message as a single object of any size, so large messages are segmented into groups of individual packets. Each packet is assigned a header with a custom identifier that associates each packet with the rest of the message. This architecture integrates with the existing code base, and does not require the modification of protocols below the routing layer. The following subsections discuss how defines and handles messages. The discussion includes the differences from PacketEpidemic message handling, and our message-traffic generation.

Message Definition
------------------

Our data packet header shown in Figure \[fig:MsgHdr\] is the custom header that identifies 