Residence Time Measurement in MPLS network

Time synchronization protocols, e.g., Network Time Protocol version 4 (NTPv4) and Precision Time Protocol (PTP) Version 2 define timing messages that can be used to synchronize clocks across a network domain. Measurement of the cumulative time one of these timing messages spends transiting the nodes on the path from ingress node to egress node is termed Residence Time and it is used to improve the accuracy of clock synchronization. (I.e., it is the sum of the difference between the time of receipt at an ingress interface and the time of transmission from an egress interface for each node along the path from ingress node to egress node.) This document defines a new Generalized Associated Channel (G-ACh) value and an associated residence time measurement (RTM) packet that can be used in a Multi-Protocol Label Switching (MPLS) network to measure residence time over a Label Switched Path (LSP). Although it is possible to use RTM over an LSP instantiated using LDP, that is outside the scope of this document. Rather, this document describes RTM over an LSP signaled using RSVP-TE because the LSP's path can be either explicitly specified or determined during signaling. Comparison with alternative proposed solutions such as is outside the scope of this document.

MPLS: Multi-Protocol Label Switching ACH: Associated Channel TTL: Time-to-Live G-ACh: Generic Associated Channel GAL: Generic Associated Channel Label NTP: Network Time Protocol ppm: parts per million PTP: Precision Time Protocol LSP: Label Switched Path OAM: Operations, Administration, and Maintenance RRO: Record Route Object RTM: Residence Time Measurement IGP: Internal Gateway Protocol

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

Packet Loss and Delay Measurement for MPLS Networks can be used to measure one-way or two-way end-to-end propagation delay over LSP or PW. But these measurements are insufficient for use in some applications, for example, time synchronization across a network as defined in the Precision Time Protocol (PTP). In PTPv2 residence times is accumulated in the correctionField of the PTP event message, as defined in , or in the associated follow-up message (or Delay_Resp message associated with the Delay_Req message) in case of two-step clocks (see the detailed discussion in ). IEEE 1588 uses this residence time to correct the transit time from ingress node to egress node, effectively making the transit nodes transparent. This document proposes a mechanism that can be used as one of types of on-path support for a clock synchronization protocol or to perform one-way measurement of residence time. The proposed mechanism accumulates residence time from all nodes that support this extension along the path of a particular LSP in Scratch Pad field of an RTM packet . This value can then be used by the egress node to update, for example, the correctionField of the PTP event packet carried within the RTM packet prior to performing its PTP processing.

RFC 5586 and RFC 6423 define the G-ACh to extend the applicability of the PW Associated Channel (ACH) to LSPs. G-ACh provides a mechanism to transport OAM and other control messages over an LSP. Processing of these messages by select transit nodes is controlled by the use of the Time-to-Live (TTL) value in the MPLS header of these messages. The packet format for Residence Time Measurement (RTM) is presented in

First four octets are defined as G-ACh Header in The Version field is set to 0, as defined in RFC 4385 . The Reserved field MUST be set to 0 on transmit and ignored on receipt. The RTM G-ACh field, value (TBA1) to be allocated by IANA, identifies the packet as such. The Scratch Pad field is 8 octets in length. It is used to accumulate the residence time spent in each RTM capable node transited by the packet on its path from ingress node to egress node. The first RTM-capable node MUST initialize the Scratch Pad field with its residence time measurement. Its format is IEEE double precision and its units are nanoseconds. Note that depending on whether the timing procedure is one-step or two-step operation (), the residence time is either for the timing packet carried in the Value field of this RTM packet or for an associated timing packet carried in the Value field of another RTM packet. The Type field identifies the type and encapsulation of a timing packet carried in the Value field, e.g., NTP or PTP . IANA will be asked to create a sub-registry in Generic Associated Channel (G-ACh) Parameters Registry called "MPLS RTM TLV Registry". The Length field contains the length, in octets , of the of the timing packet carried in the Value field. The optional Value field MAY carry a packet of the time synchronization protocol identified by Type field. It is important to note that the packet may be authenticated or encrypted and carried over LSP edge to edge unchanged while the residence time is accumulated in the Scratch Pad field. The TLV MUST be included in the RTM message, even if the length of the Value field is zero.

presents format of a PTP sub-TLV that MUST be included in the Value field of an RTM packet preceding the carried timing packet when the timing packet is PTP.

where Flags field has format

The Type field identifies PTP sub-TLV defined in the Table 19 Values of messageType field in . The Length field of the PTP sub-TLV contains the number of octets of the Value field and MUST be 20. The Flags field currently defines one bit, the S-bit, that defines whether the current message has been processed by a 2-step node, where the flag is cleared if the message has been handled exclusively by 1-step nodes and there is no follow-up message, and set if there has been at least one 2-step node and a follow-up message is forthcoming. The PTPType indicates the type of PTP packet carried in the TLV. PTPType is the messageType field of the PTPv2 packet whose values are defined in the Table 19 . The 10 octets long Port ID field contains the identity of the source port. The Sequence ID is the sequence ID of the PTP message carried in the Value field of the message.

The operation of RTM depends upon TTL expiry to deliver an RTM packet from one RTM capable interface to the next along the path from ingress node to egress node. This means that a node with RTM capable interfaces MUST be able to compute a TTL which will cause the expiry of an RTM packet at the next node with RTM capable interfaces.

Note that the RTM capability of a node is with respect to the pair of interfaces that will be used to forward an RTM packet. In general, the ingress interface of this pair must be able to capture the arrival time of the packet and encode it in some way such that this information will be available to the egress interface. The supported modes (1-step verses 2-step) of any pair of interfaces is then determined by the capability of the egress interface. For both modes, the egress interface implementation MUST be able to determine the precise departure time of the same packet and determine from this, and the arrival time information from the corresponding ingress interface, the difference representing the residence time for the packet. An interface with the ability to do this and update the associated Scratch Pad in real-time (i.e. while the packet is being forwarded) is said to be 1-step capable. Hence while both ingress and egress interfaces are required to support RTM for the pair to be RTM-capable, it is the egress interface that determines whether or not the node is 1-step or 2-step capable with respect to the interface-pair. The RTM capability used in the sub-TLV shown in is thus associated with the egress port of the node making the advertisement, while the ability of any pair of interfaces that includes this egress interface to support any mode of RTM depends on the ability of that interface to record packet arrival time in some way that can be conveyed to and used by that egress interface. When a node uses an IGP to carry the RTM capability sub-TLV, the sub-TLV MUST reflect the RTM capability (1-step or 2-step) associated with egress interfaces.

The format for the RTM Capabilities sub-TLV is presented in

Type value (TBA2) will be assigned by IANA from appropriate registry for OSPFv2. Length MUST be set to 4. RTM (capability) - is a three-bit long bit-map field with values defined as follows: 0b001 - one-step RTM supported; 0b010 - two-step RTM supported; 0b100 - reserved. Reserved field must be set to all zeroes on transmit and ignored on receipt. explains that the Interface Switching Capability Descriptor describes switching capability of an interface. For bi-directional links, the switching capabilities of an interface are defined to be the same in either direction. I.e., for data entering the node through that interface and for data leaving the node through that interface. That principle SHOULD be applied when a node advertises RTM Capability. A node that supports RTM MUST be able to act in two-step mode and MAY also support one-step RTM mode. Detailed discussion of one-step and two-step RTM modes in .

The capability to support RTM on a particular link (interface) is advertised in the OSPFv2 Extended Link Opaque LSA described in Section 3 via the RTM Capability sub-TLV. Its Type value will be assigned by IANA from the OSPF Extended Link TLV Sub-TLVs registry that will be created per request.

The capability to support RTM on a particular link (interface) can be advertised in OSPFv3 using LSA extensions as described in . Exact use of OSPFv3 LSA extensions is for further study.

The capability to support RTM on a particular link (interface) is advertised in the GENINFO TLV described in via the RTM Capability sub-TLV. With respect to the Flags field of the GENINFO TLV: The S bit MUST be cleared to prevent the RTM Capability sub-TLV from leaking between levels. The D bit of the Flags field MUST be cleared as required by . The I bit and the V bit MUST be set accordingly depending on whether RTM capability being advertised is for an IPv4 or an IPv6 interface. Application ID (TBA3) will be assigned from the Application Identifiers for TLV 251 IANA registry. The RTM Capability sub-TLV MUST be included in GENINFO TLV in Application Specific Information.

Throughout this document we refer to a node as RTM capable node when at least one of its interfaces is RTM capable. provides an example of roles a node may have with respect to RTM capability:

A is a Boundary Clock with its egress port in Master state. Node A transmits IP encapsulated timing packets whose destination IP address is G. B is the ingress LER for the MPLS LSP and is the first RTM capable node. It creates RTM packets and in each it places a timing packet, possibly encrypted, in the Value field and initializes the Scratch Pad field with its residence time measurement C is a transit node that is not RTM capable. It forwards RTM packets without modification. D is RTM capable transit node. It updates the Scratch Pad filed of the RTM packet without updating of the timing packet. E is a transit node that is not RTM capable. It forwards RTM packets without modification. F is the egress LER and the last RTM capable node. It processes the timing packet carried in the Value field using the value in the Scratch Pad field. It updates the Correction field of the PTP message with the value in the Scratch Pad field of the RTM ACH, and removes the RTM ACH encapsulation. G is a Boundary Clock with its ingress port in Slave state. Node G receives PTP messages. An ingress node that is configured to perform RTM along a path through an MPLS network to an egress node verifies that the selected egress node has an interface that supports RTM via the egress node's advertisement of the RTM Capability sub-TLV. In the Path message that the ingress node uses to instantiate the LSP to that egress node it places LSP_ATTRIBUTES Object with RTM_SET Attribute Flag set which indicates to the egress node that RTM is requested for this LSP. RTM_SET Attribute Flag SHOULD NOT be set in the LSP_REQUIRED_ATTRIBUTES object , unless it is known that all nodes support RTM, because a node that does not recognize RTM_SET Attribute Flag would reject the Path message. If egress node receives Path message with RTM_SET Attribute Flag in LSP_ATTRIBUTES object, it MUST include initialized RRO and LSP_ATTRIBUTES object where RTM_SET Attribute Flag is set and RTM_SET TLV is initialized. When Resv message received by ingress node the RTM_SET TLV will contain an ordered list, from egress node to ingress node, of the RTM capable node along the LSP's path. After the ingress node receives the Resv, it MAY begin sending RTM packets on the LSP's path. Each RTM packet has its Scratch Pad field initialized and its TTL set to expire on the closest downstream RTM capable node. It should be noted that RTM can also be used for LSPs instantiated using in an environment in which all interfaces in an IGP support RTM. In this case the RTM_SET TLV and LSP_ATTRIBUTES Object MAY be omitted.

RTM capable interfaces can be recorded via RTM_SET TLV. The RTM_SET sub-object format is of generic Type, Length, Value (TLV), presented in .

Type value (TBA4) will be assigned by IANA from its Attributes TLV Space sub-registry. The Length contains the total length of the sub-object in bytes, including the Type and Length fields. The I bit flag indicates whether the downstream RTM capable node along the LSP is present in the RRO. Reserved field must be zeroed on initiation and ignored on receipt. The content of an RTM_SET TLV is a series of variable-length sub-TLVs. Only a single RTM_SET can be present in the LSP_ATTRIBUTES object. The sub-TLVs are defined in below. The following processing procedures apply to every RTM capable node along the LSP that in this paragraph is referred as node for sake of brevity. Each node MUST examine Resv message whether RTM_SET Attribute Flag in the LSP_ATTRIBUTES object is set. If the RTM_SET flag set, the node MUST inspect the LSP_ATTRIBUTES object for presence of RTM_SET TLV. If more than one found, then the LSP setup MUST fail with generation of the ResvErr message with Error Code Duplicate TLV and Error Value that contains Type value in its 8 least significant bits. If no RTM_SET TLV has been found, then the LSP setup MUST fail with generation of the ResvErr message with Error Code RTM_SET TLV Absent . If one RTM_SET TLV has been found the node will use the ID of the first node in the RTM_SET in conjunction with the RRO to compute the hop count to its downstream node with reachable RTM capable interface. If the node cannot find matching ID in RRO, then it MUST try to use ID of the next node in the RTM_SET until it finds the match or reaches the end of RTM_SET TLV. If match have been found, then the calculated value is used by the node as TTL value in outgoing label to reach the next RTM capable node on the LSP. Otherwise, the TTL value MUST be set to 255. The node MUST add RTM_SET sub-TLV with the same address it used in RRO sub-object at the beginning of the RTM_SET TLV in associated outgoing Resv message before forwarding it upstream. If the calculated TTL value been set to 255, as described above, then the I flag in node RTM_SET TLV MUST be set to 1 before Resv message forwarded upstream. Otherwise, the I flag MUST be cleared (0). The ingress node MAY inspect the I bit flag received in each RTM_SET TLV contained in the LSP_ATTRIBUTES object of a received Resv message. Presence of the RTM_SET TLV with I bit field set to 1 indicates that some RTM nodes along the LSP could be included in the calculation of the residence time. An ingress node MAY choose to resignal the LSP to include all RTM nodes or simply notify the user via a management interface. There are scenarios when some information is removed from an RRO due to policy processing (e.g., as may happen between providers) or RRO is limited due to size constraints . Such changes affect the core assumption of the method to control processing of RTM packets. RTM SHOULD NOT be used if it is not guaranteed that RRO contains complete information.

The RTM Set sub-object contains an ordered list, from egress node to ingress node, of the RTM capable nodes along the LSP's path. The contents of a RTM_SET sub-object are a series of variable-length sub-TLVs. Each sub-TLV has its own Length field. The Length contains the total length of the sub-TLV in bytes, including the Type and Length fields. The Length MUST always be a multiple of 4, and at least 8 (smallest IPv4 sub-object). Sub-TLVs are organized as a last-in-first-out stack. The first -out sub-TLV relative to the beginning of RTM_SET TLV is considered the top. The last-out sub-TLV is considered the bottom. When a new sub-TLV is added, it is always added to the top. Only a single RTM_SET sub-TLV with the given Value field MUST be present in the RTM_SET TLV. If more than one sub-TLV is found the LSP setup MUST fail with the generation of a ResvErr message with the Error Code "Duplicate sub-TLV" and Error Value contains 16-bit value composed of (Type of TLV, Type of sub-TLV). Three kinds of sub-TLVs for RTM_SET are currently defined.

Type 0x01 IPv4 address Length The Length contains the total length of the sub-TLV in bytes, including the Type and Length fields. The Length is always 8. IPv4 address A 32-bit unicast host address. Reserved Zeroed on initiation and ignored on receipt.

Type 0x02 IPv6 address Length The Length contains the total length of the sub-TLV in bytes, including the Type and Length fields. The Length is always 20. IPv6 address A 128-bit unicast host address. Reserved Zeroed on initiation and ignored on receipt.

Type 0x03 Unnumbered interface Length The Length contains the total length of the sub-TLV in bytes, including the Type and Length fields. The Length is always 12. Node ID The Node ID interpreted as Router ID as discussed in the Section 2 . Interface ID The identifier assigned to the link by the node specified by the Node ID. Reserved Zeroed on initiation and ignored on receipt.

After instantiating an LSP for a path using RSVP-TE as described in or as described in the second paragraph of and in , ingress node MAY begin sending RTM packets to the first downstream RTM capable node on that path. Each RTM packet has its Scratch Pad field initialized and its TTL set to expire on the next downstream RTM-capable node. Each RTM-capable node on the explicit path receives an RTM packet and records the time at which it receives that packet at its ingress interface as well as the time at which it transmits that packet from its egress interface; this should be done as close to the physical layer as possible to ensure precise accuracy in time determination. The RTM-capable node determines the difference between those two times; for 1-step operation, this difference is determined just prior to or while sending the packet, and the RTM-capable egress interface adds it to the value in the Scratch Pad field of the message in progress. Note, for the purpose of calculating a residence time, a common free running clock synchronizing all the involved interfaces may be sufficient, as, for example, 4.6 ppm accuracy leads to 4.6 nanosecond error for residence time on the order of 1 millisecond. For 2-step operation, the difference between packet arrival time (at an ingress interface) and subsequent departure time (from an egress interface) is determined at some later time prior to sending a subsequent follow-up message, so that this value can be used to update the correctionField in the follow-up message. See for further details on the difference between 1-step and 2-step operation. The last RTM-capable node on the LSP MAY then use the value in the Scratch Pad field to perform time correction, if there is no follow-up message. For example, the egress node may be a PTP Boundary Clock synchronized to a Master Clock and will use the value in the Scratch Pad field to update PTP's correctionField.

The proposed approach can be directly integrated in a PTP network based on the IEEE 1588 delay request-response mechanism. The RTM capable node nodes act as end-to-end transparent clocks, and typically boundary clocks, at the edges of the MPLS network, use the value in the Scratch Pad field to update the correctionField of the corresponding PTP event packet prior to performing the usual PTP processing.

One-step mode refers to the mode of operation where an egress interface updates the correctionField value of an original event message. Two-step mode refers to the mode of operation where this update is made in a subsequent follow-up message. Processing of the follow-up message, if present, requires the downstream end-point to wait for the arrival of the follow-up message in order to combine correctionField values from both the original (event) message and the subsequent (follow-up) message. In a similar fashion, each 2-step node needs to wait for the related follow-up message, if there is one, in order to update that follow-up message (as opposed to creating a new one. Hence the first node that uses 2-step mode MUST do two things: Mark the original event message to indicate that a follow-up message will be forthcoming (this is necessary in order to Let any subsequent 2-step node know that there is already a follow-up message, and Let the end-point know to wait for a follow-up message; Create a follow-up message in which to put the RTM determined as an initial correctionField value. IEEE 1588v2 defines this behavior for PTP messages. Thus, for example, with reference to the PTP protocol, the PTPType field identifies whether the message is a Sync message, Follow_up message, Delay_Req message, or Delay_Resp message. The 10 octet long Port ID field contains the identity of the source port, that is, the specific PTP port of the boundary clock connected to the MPLS network. The Sequence ID is the sequence ID of the PTP message carried in the Value field of the message. PTP messages also include a bit that indicates whether or not a follow-up message will be coming. This bit, once it is set by a 2-step mode device, MUST stay set accordingly until the original and follow-up messages are combined by an end-point (such as a Boundary Clock). Thus, an RTM packet, containing residence time information relating to an earlier packet, also contains information identifying that earlier packet. For compatibility with PTP, RTM (when used for PTP packets) must behave in a similar fashion. To do this, a 2-step RTM capable egress interface will need to examine the S-bit in the Flags field of the PTP sub-TLV (for RTM messages that indicate they are for PTP) and - if it is clear (set to zero), it MUST set it and create a follow-up PTP Type RTM message. If the S bit is already set, then the RTM capable node MUST wait for the RTM message with the PTP type of follow-up and matching originator and sequence number to make the corresponding residence time update to the Scratch Pad field. In practice an RTM operating according to two-step clock behaves like a two-steps transparent clock. A 1-step capable RTM node MAY elect to operate in either 1-step mode (by making an update to the Scratch Pad field of the RTM message containing the PTP even message), or in 2-step mode (by making an update to the Scratch Pad of a follow-up message when its presence is indicated), but MUST NOT do both. Two main subcases can be identified for an RTM node operating as a two-step clock: A) If any of the previous RTM capable node or the previous PTP clock (e.g. the BC connected to the first node), is a two-step clock, the residence time is added to the RTM packet that has been created to include the associated PTP packet (i.e. follow-up message in the downstream direction), if the local RTM-capable node is also operating as a two-step clock. This RTM packet carries the related accumulated residence time and the appropriate values of the Sequence Id and Port Id (the same identifiers carried in the packet processed) and the Two-step Flag set to 1. Note that the fact that an upstream RTM-capable node operating in the two-step mode has created a follow-up message does not require any subsequent RTM capable node to also operate in the 2-step mode, as long as that RTM-capable node forwards the follow-up message on the same LSP on which it forwards the corresponding previous message. A one-step capable RTM node MAY elect to update the RTM follow-up message as if it were operating in two-step mode, however, it MUST NOT update both messages. A PTP event packet (sync) is carried in the RTM packet in order for an RTM node to identify that residence time measurement must be performed on that specific packet. To handle the residence time of the Delay request message on the upstream direction, an RTM packet must be created to carry the residence time on the associated downstream Delay Resp message. The last RTM node of the MPLS network in addition to update the correctionField of the associated PTP packet, must also properly handle the two-step flag of the PTP packets. B) When the PTP network connected to the MPLS and RTM node, operates in one-step clock mode, the associated RTM packet must be created by the RTM node itself. The associated RTM packet including the PTP event packet needs now to indicate that a follow up message will be coming. The last RTM node of the LSP, if it receives an RTM message with a PTP payload indicating a follow-up message will be forthcoming, must generate a follow-up message and properly set the two-step flag of the PTP packets.

IANA is requested to reserve a new G-ACh as follows: Value Description Reference TBA1 Residence Time Measurement This document

IANA is requested to create sub-registry in Generic Associated Channel (G-ACh) Parameters Registry called "MPLS RTM TLV Registry". All code points in the range 0 through 127 in this registry shall be allocated according to the "IETF Review" procedure as specified in . Code points in the range 128 through 191 in this registry shall be allocated according to the "First Come First Served" procedure as specified in . This document defines the following new values RTM TLV type s: Value Description Reference 0 Reserved This document 1 No payload This document 2 PTPv2, Ethernet encapsulation This document 3 PTPv2, IPv4 Encapsulation This document 4 PTPv2, IPv6 Encapsulation This document 5 NTP This document 6-127 Unassigned 128 - 191 Unassigned 192 - 254 Private Use This document 255 Reserved This document

IANA is requested to create sub-registry in MPLS RTM TLV Registry, requested in , called "MPLS RTM Sub-TLV Registry". All code points in the range 0 through 127 in this registry shall be allocated according to the "IETF Review" procedure as specified in . Code points in the range 128 through 191 in this registry shall be allocated according to the "First Come First Served" procedure as specified in . . This document defines the following new values RTM sub-TLV types: Value Description Reference 0 Reserved This document 1 PTP 2-step This document 2-127 Unassigned 128 - 191 Unassigned 192 - 254 Private Use This document 255 Reserved This document

IANA is requested to assign a new type for RTM Capability sub-TLV from OSPFv2 Extended Link TLV Sub-TLVs registry as follows: Value Description Reference TBA2 RTM Capability This document

IANA is requested to assign a new Application ID for RTM from the Application Identifiers for TLV 251 registry as follows: Value Description Reference TBA3 RTM This document

IANA is requested to assign a new Type for RTM_SET sub-object from Attributes TLV Space sub-registry as follows: Type Name Allowed on LSP_ATTRIBUTES Allowed on LSP_REQUIRED_ATTRIBUTES Allowed on LSP Hop Attributes Reference TBA4 RTM_SET sub-object Yes No No This document IANA requested to create new sub-registry for sub-TLV types of RTM_SET sub-object. All code points in the range 0 through 127 in this registry shall be allocated according to the "IETF Review" procedure as specified in . Code points in the range 128 through 191 in this registry shall be allocated according to the "First Come First Served" procedure as specified in . This document defines the following new values of RTM_SET object sub-object types: Value Description Reference 0 Reserved This document 1 IPv4 address This document 2 IPv6 address This document 3 Unnumbered interface This document 4-127 Unassigned 128 - 191 Unassigned 192 - 254 Private Use This document 255 Reserved This document

IANA is requested to assign new flag from Attribute Flags registry Bit No Name Attribute Flags Path Attribute Flags Resv RRO ERO Reference TBA5 RTM_SET Yes Yes No No This document

IANA is requested to assign new Error Codes from Error Codes and Globally-Defined Error Value Sub-Codes registry Error Code Meaning Reference TBA6 Duplicate TLV This document TBA7 Duplicate sub-TLV This document TBA8 RTM_SET TLV Absent This document

Routers that support Residence Time Measurement are subject to the same security considerations as defined in . In addition - particularly as applied to use related to PTP - there is a presumed trust model that depends on the existence of a trusted relationship of at least all PTP-aware nodes on the path traversed by PTP messages. This is necessary as these nodes are expected to correctly modify specific content of the data in PTP messages and proper operation of the protocol depends on this ability. As a result, the content of the PTP-related data in RTM messages that will be modified by intermediate nodes cannot be authenticated, and the additional information that must be accessible for proper operation of PTP 1-step and 2-step modes MUST be accessible to intermediate nodes (i.e. - MUST NOT be encrypted in a manner that makes this data inaccessible). While it is possible for a supposed compromised node to intercept and modify the G-ACh content, this is an issue that exists for nodes in general - for any and all data that may be carried over an LSP - and is therefore the basis for an additional presumed trust model associated with existing LSPs and nodes. The ability for potentially authenticating and/or encrypting RTM and PTP data that is not needed by intermediate RTM/PTP-capable nodes is for further study. Security requirements of time protocols are provided in RFC 7384 .

Authors want to thank Loa Andersson, Lou Berger and Acee Lindem for their thorough reviews, thoughtful comments and, most of, patience.