Transporting client timing information across a network
A network device may receive a timing control packet from a first client device. The network device may determine that the network device is in a synchronized state relative to a network grandmaster clock. The network device may modify a first field of a header of the timing control packet to indicate that the network device is in a synchronized state. The network device may modify a second field of the header of the timing control packet to indicate a time at which the network device received the timing control packet from the first client device. The network device may forward, via the network, the timing control packet toward a second client device.
1. A method, comprising:
identifying, by a first network device and based on a timing control packet received from a second network device, information that indicates a first time at which the second network device received the timing control packet from a first client device;
determining, by the first network device, a second time at which the first network device will transmit the timing control packet;
determining, by the first network device based on the information that indicates the first time and information that indicates the second time, a resident time of the timing control packet;
modifying, by the first network device, the timing control packet to indicate the resident time; and
forwarding, by the first network device, the modified timing control packet to a second client device.
2. The method of claim 1 , wherein the second time is determined based on at least one of:
information that indicates a third time at which the first network device expects the timing control packet to reach a port of the first network device for transmission to the second client device,
information that indicates a fourth time at which the timing control packet passes through a time stamping component of the first network device, or
information indicating a fifth time at which the timing control packet reaches a client attachment interface.
3. The method of claim 1 , wherein the resident time of the timing control packet is determined based on:
determining that the second network device was in a synchronized state when the second network device provided the information that indicates the first time; and
determining that the first network device is in a synchronized state.
4. The method of claim 1 , wherein the first network device and the second network device are part of a network,
wherein the first network device is an egress network device, and
wherein the second network device is an ingress network device.
5. The method of claim 1 , wherein modifying the timing control packet to indicate the resident time comprises:
setting one or more fields of a header of the timing control packet that were modified by the second network device to a null state.
6. The method of claim 1 , further comprising:
determining, based on an amount of time that has passed since updating a clock value that is based on network timing information received from a network grandmaster clock device, that the first network device is in a synchronized state,
wherein the grandmaster clock device is associated with a network that includes the first network device, and
wherein the resident time of the timing control packet is determined based on determining that the first network device is in the synchronized state.
7. The method of claim 1 , wherein a first field of a header of the timing control packet comprises:
a first portion that indicates that the second network device was in a synchronized state when the second network device received the timing control packet from the first client device, and
a second portion that indicates a location of a second field, within the header, that indicates the first time.
8. A first network device, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, to:
identify, based on a timing control packet received from a second network device, information that indicates a first time at which the second network device received the timing control packet from a first client device;
determine a second time at which the first network device will transmit the timing control packet;
determine, based on the information that indicates the first time and information that indicates the second time, a resident time of the timing control packet;
modify the timing control packet to indicate the resident time; and
forward the modified timing control packet to a second client device.
9. The first network device of claim 8 , wherein the second time is determined based on at least one of:
information that indicates a third time at which the first network device expects the timing control packet to reach a port of the first network device for transmission to the second client device,
information that indicates a fourth time at which the timing control packet passes through a time stamping component of the first network device, or
information indicating a fifth time at which the timing control packet reaches a client attachment interface.
10. The first network device of claim 8 , wherein the resident time of the timing control packet is determined based on:
determining that the second network device was in a synchronized state when the second network device provided the information that indicates the first time; and
determining that the first network device is in a synchronized state.
11. The first network device of claim 8 , wherein the first network device and the second network device is part of a network,
wherein the first network device is an egress network device, and
wherein the second network device is an ingress network device.
12. The first network device of claim 8 , wherein the one or more processors, to modify the timing control packet to indicate the resident time, are to:
set one or more fields of a header of the timing control packet that were modified by the second network device to a null state.
13. The first network device of claim 8 , wherein the one or more processors are further to:
determine, based on an amount of time that has passed since updating a clock value that is based on network timing information received from a network grandmaster clock device, that the first network device is in a synchronized state,
wherein the grandmaster clock device is associated with a network that includes the first network device, and
wherein the resident time of the timing control packet is determined based on determining that the first network device is in the synchronized state.
14. The first network device of claim 8 , wherein a first field of a header of the timing control packet comprises:
a first portion that indicates that the second network device was in a synchronized state when the second network device received the timing control packet from the first client device, and
a second portion that indicates a location of a second field, within the header, that indicates the first time.
15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a first network device, cause the first network device to:
identify, based on a timing control packet received from a second network device, information that indicates a first time at which the second network device received the timing control packet from a first client device;
determine a second time at which the first network device will transmit the timing control packet;
determine, based on the information that indicates the first time and information that indicates the second time, a resident time of the timing control packet;
modify the timing control packet to indicate the resident time; and
forward the modified timing control packet to a second client device.
16. The non-transitory computer-readable medium of claim 15 , wherein the second time is determined based on at least one of:
information that indicates a third time at which the first network device expects the timing control packet to reach a port of the first network device for transmission to the second client device,
information that indicates a fourth time at which the timing control packet passes through a time stamping component of the first network device, or
information indicating a fifth time at which the timing control packet reaches a client attachment interface.
17. The non-transitory computer-readable medium of claim 15 , wherein the resident time of the timing control packet is determined based on:
determining that the second network device was in a synchronized state when the second network device provided the information that indicates the first time; and
determining that the first network device is in a synchronized state.
18. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the first network device to modify the timing control packet to indicate the resident time, cause the first network device to:
set one or more fields of a header of the timing control packet that were modified by the second network device to a null state.
19. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the first network device to:
determine, based on an amount of time that has passed since updating a clock value that is based on network timing information received from a network grandmaster clock device, that the first network device is in a synchronized state,
wherein the grandmaster clock device is associated with a network that includes the first network device, and
wherein the resident time of the timing control packet is determined based on determining that the first network device is in the synchronized state.
20. The non-transitory computer-readable medium of claim 15 , wherein a first field of a header of the timing control packet comprises:
a first portion that indicates that the second network device was in a synchronized state when the second network device received the timing control packet from the first client device, and
a second portion that indicates a location of a second field, within the header, that indicates the first time.