idnits 2.17.1 draft-ietf-ippm-stamp-option-tlv-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 24, 2019) is 1736 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-10) exists of draft-ietf-ippm-stamp-06 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Mirsky 3 Internet-Draft X. Min 4 Intended status: Standards Track ZTE Corp. 5 Expires: January 25, 2020 G. Jun 6 ZTE Corporation 7 H. Nydell 8 Accedian Networks 9 R. Foote 10 Nokia 11 July 24, 2019 13 Simple Two-way Active Measurement Protocol Optional Extensions 14 draft-ietf-ippm-stamp-option-tlv-00 16 Abstract 18 This document describes optional extensions to Simple Two-way Active 19 Measurement Protocol (STAMP) which enable measurement performance 20 metrics in addition to ones supported by the STAMP base 21 specification. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 25, 2020. 40 Copyright Notice 42 Copyright (c) 2019 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Conventions used in this document . . . . . . . . . . . . . . 2 59 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 60 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 61 3. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 3 62 4. TLV Extensions to STAMP . . . . . . . . . . . . . . . . . . . 4 63 4.1. Extra Padding TLV . . . . . . . . . . . . . . . . . . . . 6 64 4.2. Location TLV . . . . . . . . . . . . . . . . . . . . . . 6 65 4.3. Timestamp Information TLV . . . . . . . . . . . . . . . . 8 66 4.4. Class of Service TLV . . . . . . . . . . . . . . . . . . 9 67 4.5. Direct Measurement TLV . . . . . . . . . . . . . . . . . 10 68 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 69 5.1. STAMP TLV Registry . . . . . . . . . . . . . . . . . . . 11 70 5.2. Synchronization Source Sub-registry . . . . . . . . . . . 12 71 5.3. Timestamping Method Sub-registry . . . . . . . . . . . . 13 72 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 73 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 74 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 75 8.1. Normative References . . . . . . . . . . . . . . . . . . 14 76 8.2. Informative References . . . . . . . . . . . . . . . . . 15 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 79 1. Introduction 81 Simple Two-way Active Measurement Protocol (STAMP) 82 [I-D.ietf-ippm-stamp] supports the use of optional extensions that 83 use Type-Length-Value (TLV) encoding. Such extensions are to enhance 84 the STAMP base functions, such as measurement of one-way and round- 85 trip delay, latency, packet loss, as well as ability to detect packet 86 duplication and out-of-order delivery of the test packets. This 87 specification provides definitions of optional STAMP extensions, 88 their formats, and theory of operation. 90 2. Conventions used in this document 92 2.1. Terminology 94 STAMP - Simple Two-way Active Measurement Protocol 96 DSCP - Differentiated Services Code Point 97 ECN - Explicit Congestion Notification 99 NTP - Network Time Protocol 101 PTP - Precision Time Protocol 103 HMAC Hashed Message Authentication Code 105 TLV Type-Length-Value 107 BITS Building Integrated Timing Supply 109 SSU Synchronization Supply Unit 111 GPS Global Positioning System 113 GLONASS Global Orbiting Navigation Satellite System 115 LORAN-C Long Range Navigation System Version C 117 MBZ Must Be Zeroed 119 CoS Class of Service 121 2.2. Requirements Language 123 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 124 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 125 "OPTIONAL" in this document are to be interpreted as described in BCP 126 14 [RFC2119] [RFC8174] when, and only when, they appear in all 127 capitals, as shown here. 129 3. Theory of Operation 131 STAMP Session-Sender transmits test packets to STAMP Session- 132 Reflector. STAMP Session-Reflector receives Session-Sender's packet 133 and acts according to the configuration and optional control 134 information communicated in the Session-Sender's test packet. STAMP 135 defines two different test packet formats, one for packets 136 transmitted by the STAMP-Session-Sender and one for packets 137 transmitted by the STAMP-Session-Reflector. STAMP supports two 138 modes: unauthenticated and authenticated. Unauthenticated STAMP test 139 packets are compatible on the wire with unauthenticated TWAMP-Test 140 [RFC5357] packet formats. 142 By default, STAMP uses symmetrical packets, i.e., the size of the 143 packet transmitted by Session-Reflector equals the size of the packet 144 received by the Session-Reflector. 146 4. TLV Extensions to STAMP 148 Figure 1 displays the format of STAMP Session-Sender test packet in 149 unauthenticated mode that includes a TLV. 151 0 1 2 3 152 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | Sequence Number | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | Timestamp | 157 | | 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 | Error Estimate | | 160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 161 | | 162 | | 163 | MBZ (30 octets) | 164 | | 165 | | 166 | | 167 | | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 | Type | Length | 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 ~ Value ~ 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 Figure 1: STAMP Session-Sender test packet format with TLV in 175 unauthenticated mode 177 The MBZ (Must Be Zeroed) field of a test packet transmitted by a 178 STAMP Session-Sender MUST be 30 octets long. A STAMP Session-Sender 179 test packet MUST NOT use the Reflect Octets capability defined in 180 [RFC6038]. 182 TLVs (Type-Length-Value tuples) have the two octets long Type field, 183 two octets long Length field that is the length of the Value field in 184 octets. Type values, see Section 5.1, less than 32768 identify 185 mandatory TLVs that MUST be supported by an implementation. Type 186 values greater than or equal to 32768 identify optional TLVs that 187 SHOULD be ignored if the implementation does not understand or 188 support them. If a Type value for TLV or sub-TLV is in the range for 189 Vendor Private Use, the Length MUST be at least 4, and the first four 190 octets MUST be that vendor's the Structure of Management Information 191 (SMI) Private Enterprise Number, in network octet order. The rest of 192 the Value field is private to the vendor. Following sections 193 describe the use of TLVs for STAMP that extend STAMP capability 194 beyond its base specification. 196 Figure 2 displays the format of STAMP Session-Reflector test packet 197 in unauthenticated mode that includes a TLV. 199 0 1 2 3 200 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 | Sequence Number | 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | Timestamp | 205 | | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | Error Estimate | MBZ | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | Receive Timestamp | 210 | | 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 | Session-Sender Sequence Number | 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 | Session-Sender Timestamp | 215 | | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | Session-Sender Error Estimate | MBZ | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 |Ses-Sender TTL | MBZ2 | 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | Type | Length | 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 ~ Value ~ 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 226 Figure 2: STAMP Session-Reflector test packet format with TLV in 227 unauthenticated mode 229 The MBZ2 field of a test packet transmitted by a STAMP Session- 230 Reflector MUST be 3 octets long. 232 A STAMP node, whether Session-Sender or Session-Reflector, receiving 233 a test packet MUST determine whether the packet is a base STAMP 234 packet or includes one or more TLVs. The node MUST compare the value 235 in the Length field of the UDP header and the length of the base 236 STAMP test packet in the mode, unauthenticated or authenticated based 237 on the configuration of the particular STAMP test session. If the 238 difference between the two values is larger than the length of UDP 239 header, then the test packet includes one or more STAMP TLVs that 240 immediately follow the base STAMP test packet. 242 4.1. Extra Padding TLV 244 0 1 2 3 245 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 247 | Extra Padding Type | Length | 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | | 250 ~ Extra Padding ~ 251 | | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 254 Figure 3: Extra Padding TLV 256 where fields are defined as the following: 258 o Extra Padding Type - TBA1 allocated by IANA Section 5.1 260 o Length - 2 octets long field equals length on the Extra Padding 261 field in octets. 263 o Extra Padding - a pseudo-random sequence of numbers. The field 264 MAY be filled with all zeroes. 266 The Extra Padding TLV is similar to the Packet Padding field in 267 TWAMP-Test packet [RFC5357]. The in STAMP the Packet Padding field 268 is used to ensure symmetrical size between Session-Sender and 269 Session-Reflector test packets. Extra Padding TLV MUST be used to 270 create STAMP test packets of larger size. 272 4.2. Location TLV 274 STAMP session-sender MAY include the Location TLV to request 275 information from the session-reflector. The session-sender SHOULD 276 NOT fill any information fields except for Type and Length. The 277 session-reflector MUST validate the Length value against the address 278 family of the transport encapsulating the STAMP test packet. If the 279 value of the Length field is invalid, the session-reflector MUST zero 280 all fields and MUST NOT return any information to the session-sender. 281 The session-reflector MUST ignore all other fields of the received 282 Location TLV. 284 0 1 2 3 285 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 | Location Type | Length | 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 | Source MAC | 290 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 | | Reserved A | 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 293 ~ Destination IP Address ~ 294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 ~ Source IP Address ~ 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 | Dest.port | Src.Port | Reserved B | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 Figure 4: Session-Reflector Location TLV 302 where fields are defined as the following: 304 o Location Type - TBA2 allocated by IANA Section 5.1 306 o Length - 2 octets long field equals length on the Value field in 307 octets. Length field value MUST be 20 octets for the IPv4 address 308 family. For the IPv6 address family value of the Length field 309 MUST be 44 octets. All other values are invalid. 311 o Source MAC - 6 octets 48 bits long field. The session-reflector 312 MUST copy Source MAC of received STAMP packet into this field. 314 o Reserved A - two octets long field. MUST be zeroed on 315 transmission and ignored on reception. 317 o Destination IP Address - IPv4 or IPv6 destination address of the 318 received by the session-reflector STAMP packet. 320 o Source IP Address - IPv4 or IPv6 source address of the received by 321 the session-reflector STAMP packet. 323 o Dest.port - one octet long UDP destination port number of the 324 received STAMP packet. 326 o Src.port - one octet long UDP source port number of the received 327 STAMP packet. 329 o Reserved B - two octets long field. MUST be zeroed on 330 transmission and ignored on reception. 332 The Location TLV MAY be used to determine the last-hop addressing for 333 STAMP packets including source and destination IP addresses as well 334 as the MAC address of the last-hop router. Last-hop MAC address MAY 335 be monitored by the Session-Sender whether there has been a path 336 switch on the last hop, closest to the Session-Reflector. The IP 337 addresses and UDP port will indicate if there is a NAT router on the 338 path, and allows the Session-Sender to identify the IP address of the 339 Session-Reflector behind the NAT, detect changes in the NAT mapping 340 that could cause sending the STAMP packets to the wrong Session- 341 Reflector. 343 4.3. Timestamp Information TLV 345 STAMP session-sender MAY include the Timestamp Information TLV to 346 request information from the session-reflector. The session-sender 347 SHOULD NOT fill any information fields except for Type and Length. 348 The session-reflector MUST validate the Length value of the STAMP 349 test packet. If the value of the Length field is invalid, the 350 session-reflector MUST zero all fields and MUST NOT return any 351 information to the session-sender. 353 0 1 2 3 354 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 | Timestamp Information Type | Length | 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 | Sync. Src In | Timestamp In | Sync. Src Out | Timestamp Out | 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 Figure 5: Timestamp Information TLV 363 where fields are defined as the following: 365 o Timestamp Information Type - TBA3 allocated by IANA Section 5.1 367 o Length - 2 octets long field, equals four octets. 369 o Sync Src In - one octet long field that characterizes the source 370 of clock synchronization at the ingress of Session-Reflector. 371 There are several of methods to synchronize the clock, e.g., 372 Network Time Protocol (NTP) [RFC5905], Precision Time Protocol 373 (PTP) [IEEE.1588.2008], Synchronization Supply Unit (SSU) or 374 Building Integrated Timing Supply (BITS), or Global Positioning 375 System (GPS), Global Orbiting Navigation Satellite System 376 (GLONASS) and Long Range Navigation System Version C (LORAN-C). 377 The value is one of Section 5.2. 379 o Timestamp In - one octet long field that characterizes the method 380 by which the ingress of Session-Reflector obtained the timestamp 381 T2. A timestamp may be obtained with hardware assist, via 382 software API from a local wall clock, or from a remote clock (the 383 latter referred to as "control plane"). The value is one of 384 Section 5.3. 386 o Sync Src Out - one octet long field that characterizes the source 387 of clock synchronization at the egress of Session-Reflector. The 388 value is one of Section 5.2. 390 o Timestamp Out - one octet long field that characterizes the method 391 by which the egress of Session-Reflector obtained the timestamp 392 T3. The value is one of Section 5.3. 394 4.4. Class of Service TLV 396 The STAMP session-sender MAY include Class of Service (CoS) TLV in 397 the STAMP test packet. If the CoS TLV is present in the STAMP test 398 packet and the value of the DSCP1 field is zero, then the STAMP 399 session-reflector MUST copy the values of Differentiated Services 400 Code Point (DSCP) ECN fields from the received STAMP test packet into 401 DSCP2 and ECN fields respectively of the CoS TLV of the reflected 402 STAMP test packet. If the value of the DSCP1 field is non-zero, then 403 the STAMP session-reflector MUST use DSCP1 value from the CoS TLV in 404 the received STAMP test packet as DSCP value of STAMP reflected test 405 packet and MUST copy DSCP and ECN values of the received STAMP test 406 packet into DSCP2 and ECN fields of Class of Service TLV in the STAMP 407 reflected a packet. The Session-Sender, upon receiving the reflected 408 packet, will save the DSCP and ECN values for analysis of the CoS in 409 the reverse direction. 411 0 1 2 3 412 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 413 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 414 | Class of Service Type | Length | 415 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 416 | DSCP1 | DSCP2 |ECN| Reserved | 417 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 Figure 6: Class of Service TLV 421 where fields are defined as the following: 423 o Class of Service Type - TBA4 allocated by IANA Section 5.1 425 o Length - 2 octets long field, equals four octets. 427 o DSCP1 - The Differentiated Services Code Point (DSCP) intended by 428 the Session-Sender. To be used as the return DSCP from the 429 Session-Reflector. 431 o DSCP2 - The received value in the DSCP field at the Session- 432 Reflector in the forward direction. 434 o ECN - The received value in the ECN field at the Session-Reflector 435 in the forward direction. 437 o Reserved - 18 bits long field, must be zeroed in transmission and 438 ignored on receipt. 440 A STAMP Session-Sender that includes the CoS TLV sets the value of 441 the DSCP1 field and zeroes the value of the DSCP2 field. A STAMP 442 Session-Reflector that received the test packet with the CoS TLV MUST 443 include the CoS TLV in the reflected test packet. Also, the Session- 444 Reflector MUST copy the value of the DSCP field of the IP header of 445 the received STAMP test packet into the DSCP2 field in the reflected 446 test packet. And, at last, the Session-Reflector MUST set the value 447 of the DSCP field in the IP header of the reflected test packet equal 448 to the value of the DSCP1 field of the test packet it has received. 450 Re-mapping of CoS in some use cases, for example, in mobile backhaul 451 networks is used to provide multiple services, i.e., 2G, 3G, LTE, 452 over the same network. But if it is misconfigured, then it is often 453 difficult to diagnose the root cause of the problem that is viewed as 454 an excessive packet drop of higher level service while packet drop 455 for lower service packets is at a normal level. Using CoS TLV in 456 STAMP test helps to troubleshoot the existing problem and also verify 457 whether DiffServ policies are processing CoS as required by the 458 configuration. 460 4.5. Direct Measurement TLV 462 The Direct Measurement TLV enables collection of "in profile" IP 463 packets that had been transmitted and received by the Session-Sender 464 and Session-Reflector respectfully. The definition of "in-profile 465 packet" is outside the scope of this document. 467 0 1 2 3 468 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 470 | Direct Measurement Type | Length | 471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 472 | Session-Sender Tx counter (S_TxC) | 473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 474 | Session-Reflector Rx counter (R_RxC) | 475 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 476 | Session-Reflector Tx counter (R_TxC) | 477 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 479 Figure 7: Direct Measurement TLV 481 where fields are defined as the following: 483 o Direct Measurement Type - TBA5 allocated by IANA Section 5.1 485 o Length - 2 octets long field equals length on the Value field in 486 octets. Length field value MUST be 12 octets. 488 o Session-Sender Tx counter (S_TxC) is four octets long field. 490 o Session-Reflector Rx counter (R_RxC) is four octets long field. 491 MUST be zeroed by the Session-Sender and filled by the Session- 492 Reflector. 494 o Session-Reflector Tx counter (R_TxC) is four octets long field. 495 MUST be zeroed by the Session-Sender and filled by the Session- 496 Reflector. 498 5. IANA Considerations 500 5.1. STAMP TLV Registry 502 IANA is requested to create the STAMP TLV Type registry. All code 503 points in the range 1 through 32759 in this registry shall be 504 allocated according to the "IETF Review" procedure as specified in 505 [RFC8126]. Code points in the range 32760 through 65279 in this 506 registry shall be allocated according to the "First Come First 507 Served" procedure as specified in [RFC8126]. Remaining code points 508 are allocated according to Table 1: 510 +---------------+-------------------------+-------------------------+ 511 | Value | Description | Reference | 512 +---------------+-------------------------+-------------------------+ 513 | 0 | Reserved | This document | 514 | 1- 32767 | Mandatory TLV, | IETF Review | 515 | | unassigned | | 516 | 32768 - 65279 | Optional TLV, | First Come First Served | 517 | | unassigned | | 518 | 65280 - 65519 | Experimental | This document | 519 | 65520 - 65534 | Private Use | This document | 520 | 65535 | Reserved | This document | 521 +---------------+-------------------------+-------------------------+ 523 Table 1: STAMP TLV Type Registry 525 This document defines the following new values in STAMP TLV Type 526 registry: 528 +-------+-----------------------+---------------+ 529 | Value | Description | Reference | 530 +-------+-----------------------+---------------+ 531 | TBA1 | Extra Padding | This document | 532 | TBA2 | Location | This document | 533 | TBA3 | Timestamp Information | This document | 534 | TBA4 | Class of Service | This document | 535 | TBA5 | Direct Measurement | This document | 536 +-------+-----------------------+---------------+ 538 Table 2: STAMP Types 540 5.2. Synchronization Source Sub-registry 542 IANA is requested to create Synchronization Source sub-registry as 543 part of STAMP TLV Type registry. All code points in the range 1 544 through 127 in this registry shall be allocated according to the 545 "IETF Review" procedure as specified in [RFC8126]. Code points in 546 the range 128 through 239 in this registry shall be allocated 547 according to the "First Come First Served" procedure as specified in 548 [RFC8126]. Remaining code points are allocated according to Table 1: 550 +-----------+--------------+-------------------------+ 551 | Value | Description | Reference | 552 +-----------+--------------+-------------------------+ 553 | 0 | Reserved | This document | 554 | 1- 127 | Unassigned | IETF Review | 555 | 128 - 239 | Unassigned | First Come First Served | 556 | 240 - 249 | Experimental | This document | 557 | 250 - 254 | Private Use | This document | 558 | 255 | Reserved | This document | 559 +-----------+--------------+-------------------------+ 561 Table 3: Synchronization Source Sub-registry 563 This document defines the following new values in Synchronization 564 Source sub-registry: 566 +-------+---------------------+---------------+ 567 | Value | Description | Reference | 568 +-------+---------------------+---------------+ 569 | 1 | NTP | This document | 570 | 2 | PTP | This document | 571 | 3 | SSU/BITS | This document | 572 | 4 | GPS/GLONASS/LORAN-C | This document | 573 | 5 | Local free-running | This document | 574 +-------+---------------------+---------------+ 576 Table 4: Synchronization Sources 578 5.3. Timestamping Method Sub-registry 580 IANA is requested to create Timestamping Method sub-registry as part 581 of STAMP TLV Type registry. All code points in the range 1 through 582 127 in this registry shall be allocated according to the "IETF 583 Review" procedure as specified in [RFC8126]. Code points in the 584 range 128 through 239 in this registry shall be allocated according 585 to the "First Come First Served" procedure as specified in [RFC8126]. 586 Remaining code points are allocated according to Table 1: 588 +-----------+--------------+-------------------------+ 589 | Value | Description | Reference | 590 +-----------+--------------+-------------------------+ 591 | 0 | Reserved | This document | 592 | 1- 127 | Unassigned | IETF Review | 593 | 128 - 239 | Unassigned | First Come First Served | 594 | 240 - 249 | Experimental | This document | 595 | 250 - 254 | Private Use | This document | 596 | 255 | Reserved | This document | 597 +-----------+--------------+-------------------------+ 599 Table 5: Timestamping Method Sub-registry 601 This document defines the following new values in Timestamping 602 Methods sub-registry: 604 +-------+---------------+---------------+ 605 | Value | Description | Reference | 606 +-------+---------------+---------------+ 607 | 1 | HW assist | This document | 608 | 2 | SW local | This document | 609 | 3 | Control plane | This document | 610 +-------+---------------+---------------+ 612 Table 6: Timestamping Methods 614 6. Security Considerations 616 Use of HMAC in authenticated mode may be used to simultaneously 617 verify both the data integrity and the authentication of the STAMP 618 test packets. 620 7. Acknowledgments 622 Authors much appreciate the thorough review and thoughful comments 623 received from Tianran Zhou. 625 8. References 627 8.1. Normative References 629 [I-D.ietf-ippm-stamp] 630 Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple 631 Two-way Active Measurement Protocol", draft-ietf-ippm- 632 stamp-06 (work in progress), April 2019. 634 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 635 Requirement Levels", BCP 14, RFC 2119, 636 DOI 10.17487/RFC2119, March 1997, 637 . 639 [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. 640 Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", 641 RFC 5357, DOI 10.17487/RFC5357, October 2008, 642 . 644 [RFC6038] Morton, A. and L. Ciavattone, "Two-Way Active Measurement 645 Protocol (TWAMP) Reflect Octets and Symmetrical Size 646 Features", RFC 6038, DOI 10.17487/RFC6038, October 2010, 647 . 649 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 650 Writing an IANA Considerations Section in RFCs", BCP 26, 651 RFC 8126, DOI 10.17487/RFC8126, June 2017, 652 . 654 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 655 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 656 May 2017, . 658 8.2. Informative References 660 [IEEE.1588.2008] 661 "Standard for a Precision Clock Synchronization Protocol 662 for Networked Measurement and Control Systems", 663 IEEE Standard 1588, March 2008. 665 [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, 666 "Network Time Protocol Version 4: Protocol and Algorithms 667 Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, 668 . 670 Authors' Addresses 672 Greg Mirsky 673 ZTE Corp. 675 Email: gregimirsky@gmail.com 677 Xiao Min 678 ZTE Corp. 680 Email: xiao.min2@zte.com.cn 681 Guo Jun 682 ZTE Corporation 683 68# Zijinghua Road 684 Nanjing, Jiangsu 210012 685 P.R.China 687 Phone: +86 18105183663 688 Email: guo.jun2@zte.com.cn 690 Henrik Nydell 691 Accedian Networks 693 Email: hnydell@accedian.com 695 Richard Foote 696 Nokia 698 Email: footer.foote@nokia.com