Method and implementation for network instrumentation and traffic disposition with timestamps

1. A method for network instrumentation and traffic disposition using at least one time-stamp, the method comprising:

receiving, at a device of a network, a data packet;

determining, by the device, whether the device is a boundary device located on a boundary of an instrumented sub-network of the network;

if the determination is made that the device is the boundary device, inserting a first time-stamp at a first offset from a frame checksum (FCS) field in a data frame associated with the data packet; and

if the determination is made that the device is not the boundary device, inserting a respective time-stamp corresponding to the device in the data frame associated with the data packet at a second offset from the FCS field,

wherein at least one time-stamp facilitates determination of timeliness information associated with the data packet, and

wherein the first offset from the FCS field is defined based on a width of a time-stamp count field included in the data frame associated with the data packet.

2. The method of claim 1 , wherein the received data packet is a data packet originated from a sending endpoint device of the network, and wherein the timeliness information associated with the data packet enables the receiving endpoint device of the network to enforce policies based on the timeliness information.

3. The method of claim 1 , wherein the data frame associated with the data packet includes the time-stamp count field at a fixed offset from the FCS field.

4. The method of claim 1 , further comprising determining the second offset based on the width of the time-stamp count field and a width of a first time-stamp field associated with the first time-stamp.

5. The method of claim 1 , further comprising incrementing content of the time-stamp count field when the data packet is received by the device, wherein a time-stamp portion of the data frame associated with the data packet is processable independent of a payload portion of the data frame associated with the data packet.

6. The method of claim 1 , wherein time-stamps inserted in the data frame associated with the data packet enable an endpoint device to indirectly obtain information related to network delays incurred by the data packet at each network hop.

7. The method of claim 6 , wherein time-stamps inserted in the data frame associated with the data packet enable an endpoint device to compile and analyze the information related to the network delays across a plurality of data packets over time in order to determine short-term and long-term latency and jitter performance of individual links of the network.

8. A device, comprising:

a receiving port configured to receive a data packet;

a device configuration circuitry configured to determine whether the device is a boundary device located on a boundary of an instrumented sub-network of a network;

a frame processing circuitry configured to:

insert a first time-stamp at a first offset from a frame checksum (FCS) field in a data frame associated with the data packet, if the determination is made that device is the boundary device; and

insert a respective time-stamp of the at least one time-stamp in the data frame associated with the data packet at a second offset from the FCS field, if the determination is made that the device is not the boundary device,

wherein the at least one time-stamp enables a receiving endpoint device of the network to determine timeliness information associated with the data packet, and

wherein the first offset from the FCS field is defined based on a width of a time-stamp count field included in the data frame associated with the data packet.

9. The device of claim 8 , wherein the received data packet is a data packet originated from a sending endpoint device.

10. The device of claim 8 , wherein the frame processing circuitry is further configured to insert the time-stamp count field in the data frame associated with the data packet at a fixed offset from the FCS field.

11. The device of claim 8 , wherein the frame processing circuitry is further configured to:

increment content of the time-stamp count field when the data packet is received by the device; and

determine the second offset based on the width of the time-stamp count field and a width of a first time-stamp field associated with the first time-stamp, wherein a time-stamp portion of the data frame associated with the data packet is processable independent of a payload portion of the data frame associated with the data packet.

12. A device, comprising:

a receiving port configured to receive a data packet including at least one time-stamp in a data frame associated with the data packet from a network switch of a network;

a frame processor configured to: parse the data frame associated with the data packet;

determine whether a time-stamp count extracted from the parsed data frame is one; and

if the determination is made that the time-stamp count is one, extract a first time-stamp of the at least one time-stamp, from a time-stamp portion of the parsed data frame, at a first offset from a frame checksum (FCS) field in the parsed data frame;

if the determination is made that the time-stamp count is not one, extract a time-stamp of the at least one time-stamp, from the data frame associated with the data packet, having a corresponding offset from the FCS field determined based on the time-stamp count;

and an analysis circuitry configured to determine timeliness information associated with the data packet using the at least one time-stamp,

wherein the first offset from the FCS field is defined based on a width of a time-stamp count field included in the data frame associated with the data packet.

13. The device of claim 12 , wherein the frame processor is further configured to extract the time-stamp count from the time-stamp count field in the data frame associated with the data packet at a fixed offset from the FCS field.

14. The device of claim 12 , wherein the analysis circuitry is configured to obtain information related to network delays incurred by the data packet at each network hop using the at least one time-stamp.

15. The device of claim 12 , further comprising a policy circuitry configured to enforce policies based on the timeliness information.

16. The device of claim 12 , wherein the analysis circuitry is further configured use the at least one time-stamp to compile and analyze the information related to the network delays across a plurality of data packets over time in order to determine short-term and long-term latency and jitter performance of individual links of the network.

17. A method of monitoring traffic disposition of a network using at least one time-stamp, the method comprising:

receiving, at a receiving endpoint device of the network, a data packet including at least one time-stamp in a data frame associated with the data packet from a network switch of the network;

parsing the data frame associated with the data packet;

determining whether a time-stamp count extracted from the parsed data frame is one;

if the determination is made that the time-stamp count is one, extracting a first time-stamp of the at least one time-stamp, from a time-stamp portion of the parsed data frame, at a first offset from a frame checksum (FCS) field in the parsed data frame;

if the determination is made that the time-stamp count is not one, extracting a time-stamp of the at least one time-stamp, from the data frame associated with the data packet, having a second offset from the FCS field; and

determining timeliness information associated with the data packet using the at least one time-stamp,

wherein the first offset from the FCS field is defined based on a width of a time-stamp count field included in the data frame associated with the data packet.

18. The method of claim 17 , further comprising extracting the time-stamp count from the time-stamp count field in the data frame associated with the data packet at a fixed offset from the FCS field; and further comprising enforcing policies based on the timeliness information.

19. The method of claim 18 , further comprising:

determining the second offset based on the width of the time-stamp count field and a width of a first time-stamp field associated with the first time-stamp; and

facilitating obtaining information related to network delays incurred by the data packet, at each network hop, using the at least one time-stamp.

20. A device, comprising:

a receiving port configured to receive a data packet;

memory to store a plurality of modules; and

a processor configured to execute instructions included in the plurality of modules, wherein the plurality of modules executable by the processor comprise:

a device configuration module configured to determine whether the device is a boundary device located on a boundary of an instrumented sub-network of a network;

a frame processing module configured to:

insert a first time-stamp at a first offset from a frame checksum (FCS) field in a data frame associated with the data packet, if the determination is made that device is the boundary device; and

insert a respective time-stamp of the at least one time-stamp in the data frame associated with the data packet at a second offset from the FCS field, if the determination is made that the device is not the boundary device,

wherein the at least one time-stamp enables a receiving endpoint device of the network to determine timeliness information associated with the data packet, and

wherein the first offset from the FCS field is defined based on a width of a time-stamp count field included in the data frame associated with the data packet.