TX FollowUp packet must not have FLAG_TWO_STEP set, and it must have FLAG_PTP_TIMESCALE set
Sync message is required to contain the header (See Clause 11.4.2) followed by 10 reserved octets set to zero, see Table 11-8
Pdelay_Req message is required to contain the header (See Clause 11.4.2) followed by 20 reserved octets set to zero.
TX announce packet must have reserved fields set to 0 instead of being set to the current RTC time. See Table 10-7.
As per AVnu_PTP-5 PICS, we are to stop spamming a non-AVB network if we receive two pdelay responses for one request, not three.
Fix problem where a single lost PDelayResp caused the next calculated neighborRateRatioValid to be FALSE.  See 802.1AS-2011 Clause 11.2.15.2.3 Note 2
Simplify path delay debug prints to make them easier to read
Added more debug prints to show why ptp pdelay request state machine is reset
gPTP.com.c.18.1.a and gPTP.com.c.18.1.c fixes, stop after multiple pDelay responses are seen
gPTP.com.c.18.1.a fixes: re-enable port after multiplePdelayTimer decreases to 0
printk fix and wrong paren fix
i not port
i not port
refactor for gPTP.com.c.18.1.a
Enable verbose gPTP logging
fix syntax for additional printk
Track lost response count
fix syntax err
More logging and gPTP fixes for gPTP.com.c.15.3 and gPTP.com.c.18
threshold for gPTP.com.c.15.3 is less than not less than or equal