IEEE1588 chapter 7

7.2 PTP timescale

7.2.1 General

The timescale for a domain is established by the grandmaster clock.(一个domain的timescale是由grandmaster clock建立的)
There are two types of timescales supported by PTP: (PTP support 两种type的timescale)
⎯ The timescale PTP: In normal operation, the epoch is the PTP epoch and the timescale is continuous; see 7.2.4. The unit of measure of time is the SI second as realized on the rotating geoid.
⎯ The timescale ARB (arbitrary): In normal operation, the epoch is set by an administrative procedure. The epoch is permitted to be reset during normal operation. Between invocations of the administrative procedure, the timescale is continuous. Additional invocations of the administrative procedure may introduce discontinuities in the overall timescale.

7.2.2 Epoch
The epoch is the origin of the timescale of a domain.(epoch是domain的timescale的起点)
The PTP epoch is 1 January 1970 00:00:00 TAI, which is 31 December 1969 23:59:51.999918 UTC.
NOTE 1— The PTP epoch coincides with the epoch of the common Portable Operating System Interface (POSIX) algorithms for converting elapsed seconds since the epoch to the ISO 8601:2004 printed representation of time of day; see ISO/IEC 9945:2003 [B16] and ISO 8601:2004 [B17].
NOTE 2— See Annex B for information on converting between common timescales.

7.3 PTP communications

7.3.1 Messaging Model

Although the standard is written based on the multicast model, it is permissible to create an implementation based on a unicast model provided that the behavior of the protocol is preserved.(尽管该标准是基于muticast 模型编写的，但允许创建一个实现基于Unicast的model，前提是保留协议的行为)

7.3.2 Message attributes
All PTP-related communications occur via PTP messages. PTP messages have the following attributes:
⎯ Message class
⎯ Message sourcePortIdentity
⎯ Message type
⎯ Message sequenceId
⎯ Flags defining options

7.3.3.1 Event message

a) Sync:

b) Delay_Req:

c) Pdelay_Req:

d) Pdelay_Resp:

Event messages shall be assigned the timestamps defined above as specified in 7.3.4.

7.3.3.2 General messages

a) Announce:

b) Follow_Up:

c) Delay_Resp:

d) Pdelay_Resp_Follow_Up:

e) Management:

f) Signaling:

General messages are not required to be timestamped.