Overview

Three (3) message types will be defined: Insert, Update, Lookup

Workload Formats

Insert

A new binding is being added for the GUID value. Any existing values are preserved.

<index> <client_ID> <time_offset> I <GUID> <NA1,TTL1,weight1>, <NA2,TTL2,weight2>,……

• index: a unique index used for tracking.
• client_ID: client identifier used to identify which client should be responsible for this entry.
• time_offset: the time that the message needs to be sent out.
• I: insert type.

Update

An old binding is replaced for the GUID value. The previous binding and new binding are required. A missing old value means the Update will be treated as an Insert.

<index> <client_ID> <time_offset> U <GUID> 
<new <NA1,TTL1,weight1>>, <old <NA1’,TTL1’,weight1’>>;
<new <NA2,TTL2,weight2>>, <old <NA2’,TTL2’,weight2’>>……

• index: a unique index used for tracking.
• client_ID: client identifier used to identify which client should be responsible for this entry.
• time_offset: the time that the message needs to be sent out.
• U: update type.

Lookup

The Lookup message is used to query the GNRS about the current binding(s) for a specific GUID value.

<index> <client_ID> <time_offset> Q <GUID>

• index: a unique index used for tracking.
• client_ID: client identifier used to identify which client should be responsible for this entry.
• time_offset: the time that the message needs to be sent out.
• Q: lookup type.