idnits 2.17.1 draft-detnet-jitter-bandwidth-misordering-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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([I-D.chen-detnet-loss-delay]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 6, 2019) is 1807 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) -- Looks like a reference, but probably isn't: '2' on line 284 -- Looks like a reference, but probably isn't: '8' on line 284 -- Looks like a reference, but probably isn't: '9' on line 284 == Outdated reference: A later version (-13) exists of draft-ietf-detnet-architecture-12 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DeNet WG L. Chen 3 Internet-Draft S. Qian 4 Intended status: Standards Track SEU 5 Expires: November 7, 2019 T. Ao 6 ZTE 7 May 6, 2019 9 DetNet Packet Jitter, Bandwidth and Misordering Passive Performance 10 Measurement 11 draft-detnet-jitter-bandwidth-misordering-00 13 Abstract 15 Deterministic Networking (DetNet) can provide data transmission with 16 end-to-end bounded latency and extremely low packet loss for user's 17 services. In order to better control and manage deterministic 18 network services. It is necessary to measure and monitor DetNet QoS 19 information. As introduced in [I-D.chen-detnet-loss-delay], packet 20 loss rates and end-to-end delay can be measured by using passive 21 Performance Measurement (PM) in MPLS-based DetNet encapsulation. 23 This document implement three new QoS related attribute to support 24 passive Performance Measurement for DetNet service. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on November 7, 2019. 43 Copyright Notice 45 Copyright (c) 2019 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 62 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. DetNet Control Word based PM . . . . . . . . . . . . . . . . 3 64 2.1. Jitter . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 2.2. Used Bandwidth . . . . . . . . . . . . . . . . . . . . . 5 66 2.3. Misordering packets . . . . . . . . . . . . . . . . . . . 6 67 3. Security Considerations . . . . . . . . . . . . . . . . . . . 7 68 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 69 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 70 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 6.1. Informative References . . . . . . . . . . . . . . . . . 7 72 6.2. Normative References . . . . . . . . . . . . . . . . . . 7 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 75 1. Introduction 77 As defined in [I-D.ietf-detnet-architecture], DetNet can provide data 78 transmission with end-to-end bounded latency and extremely low packet 79 loss for user's services. In order to ensure the efficiency and 80 accuracy of information collection and management, it is necessary to 81 measure and monitor DetNet QoS information. 83 DetNet QoS information includes minimum and maximum delay, bounded 84 jitter, packet loss ratio and an upper bound on misordering packet in 85 general. Apart from this, link bandwidth information also play an 86 important role in resource allocation. 88 As introduced in [I-D.chen-detnet-loss-delay], packet loss rates and 89 end-to-end delay can be measured by using passive Performance 90 Measurement (PM) in MPLS-based DetNet encapsulation. Which defines 91 two new flags in the d-CW(control word) and three new TLVs to LM and 92 DM messages. 94 Inspird by that, we implement protocol mechanisms to support passive 95 Performance Measurement for bounded jitter, misordering packet and 96 used bandwidth. 98 1.1. Requirements Language 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in [RFC2119]. 104 1.2. Terminology 106 The terminology is defined as [I-D.ietf-detnet-architecture], 107 [RFC3270], [RFC6374], [RFC2475] and [RFC2474]. 109 2. DetNet Control Word based PM 111 MPLS-based DetNet encapsulation introduces an S-Lable and a d-CW. 112 Meanwhile [I-D.chen-detnet-loss-delay] document defines two new flags 113 in the d-CW. Here this document defines a new flag in the d-CW(as 114 shown in Figure 1). The B bit is defined to indicate whether the 115 bandwidth measurement is enabled. 117 +-----------------+ 118 ~ IP/MPLS Tunnel ~ 119 +-----------------+ <--\ 120 | Service Label | | 121 +-----------------+ +-- Service Layer Header 122 +----| Control Word | | 123 | +-----------------+ <--/ 124 | | Payload | 125 | +-----------------+ 126 | 127 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 +--->|0 0 0 0|L|D|B| Sequence Number | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 Figure 1: DetNet Control Word 133 where: 135 o L bit: Loss measurement indicator; 1 means the loss measurement is 136 enabled, otherwise the loss measurement is not enabled. 138 o D bit: Delay measurement indicator; 1 means the delay measurement 139 is enabled, otherwise the delay measurement is not enabled. When 140 a node receive a packet with D bit set, it will timestamp the 141 packet and copy it for further PM processing. 143 o B bit: Bandwidth measurement indicator; 1 means the bandwidth 144 measurement is enabled, otherwise the bandwidth measurement is not 145 enabled. 147 Assume a DetNet service path between node A and node B, where node A 148 is the ingress node, and node B is the egress node. The packets with 149 same interval number belong to the same measurement interval. 151 [Editor notes: The detail of measurement interval and flags in DetNet 152 Control Word can be found in [I-D.chen-detnet-loss-delay]] 154 2.1. Jitter 156 In brief, jitter can be calculated by delay.To measure the delay of a 157 packet, the D bit of the d-CW MUST be set. 159 If the D bit of the d-CW is set, recording both the flow-id of DetNet 160 flow and the node-id of node. 162 At the ingress node, record the time when sending the packet, with 163 the timestamp indexed by the sequence number. At the egress node, 164 when receiving a packet with D bit set, record the time when the 165 packet was received, with the timestamp indexed by the sequence 166 number. 168 When the measurement interval comes, all the information of node-id, 169 flow-id, sequence number and timestamps need to be sent to the 170 centralized controller. 172 The mechanism for sending information to a centralized controller is 173 out side the scope of this document. 175 After that, the centralized controller can find the sequence number 176 and timestamps between adjacent nodes such as AB by flow-id and node- 177 id. 179 Then, with the timestamps from the ingress and egress nodes, and the 180 sequence number, the packet delay can be calculated as below. 182 Delay[n] = B_RxT[n] - A_TxT[n], where: 184 o B_RxT[n] identifies the timestamp at node B when receiving the No. 185 "n" packet; 187 o A_TxT[n] identifies the timestamp at node A when sending the No. 188 "n" packet; 190 After getting multiple sets of Delay[n] informatin, the packet jitter 191 in the No. "t" measurement interval can be calculated as below. 193 Jitter[t] = Max(Delay[i] - Delay[j]), where: 195 o Delay[i] identifies the No. "i" packet's delay between A and B; 197 o Delay[j] identifies the No. "j" packet's delay between A and B; 199 2.2. Used Bandwidth 201 To measure the used bandwidth of DetNet flows between A and B, both 202 of the D bit and B bit of the d-CW MUST be set. 204 If the B and D bit of the d-CW are set, recording both the flow-id of 205 DetNet flow and the node-id of node. 207 At the ingress node, record the time and accumulate the packet bytes 208 when sending the packet, with the timestamp indexed by the sequence 209 number. At the egress node, when receiving a packet with B and D bit 210 set, record the time and accumulate the packet bytes when the packet 211 was received, with the timestamp indexed by the sequence number. 213 When the measurement interval comes, all the information of node-id, 214 flow-id, sequence number, timestamps and packet bytes need to be sent 215 to the centralized controller. Then the packet bytes need to be 216 reset to zero for next measurement interval. 218 After that, the centralized controller can find the sequence number, 219 timestamps and packet bytes between adjacent nodes such as AB by 220 flow-id and node-id. 222 Then, with the timestamps and packet bytes from the ingress and 223 egress nodes, and the sequence number, the used bandwidth in No. "t" 224 measurement interval can be calculated as below. 226 Bandwidth[t] = Max(A_TxB[t], B_RxB[t])*8/Delay [t], where: 228 o Delay [i] identifies the No. "i" packet's delay between A and B, 229 the measurement method has been introduced in section 2.1; 231 o B_RxB[n] identifies the total bytes received at node B in the No. 232 "n" measurement interval with the same flow-id; 234 o A_TxB[n] identifies the total bytes sended at node A in the No. 235 "n" measurement interval with the same flow-id; 237 2.3. Misordering packets 239 Since the measurement of the maximum misordering packets only 240 requires the sequence number of the DetNet flows, there is no need to 241 additionally add a flag bit to the MPLS control word. The D bit of 242 the d-CW can re reused. 244 To measure the maximum misordering packets, the D bit of the d-CW 245 MUST be set. 247 At the ingress node, record the time when sending the packet, with 248 the timestamp indexed by the sequence number. At the egress node, 249 when receiving a packet with D bit set, record the time when the 250 packet was received, with the timestamp indexed by the sequence 251 number. 253 When the measurement interval comes, all the information of node-id, 254 flow-id, sequence number and timestamps need to be sent to the 255 centralized controller. 257 After that, the centralized controller can find the sequence number 258 and timestamps between adjacent nodes such as AB by flow-id and node- 259 id. 261 A packet can be classified as a misordering packet if it has a 262 sequence number smaller than its predecessors. 264 Specifically, let M DetNet flows, denoted as (S1, . . . ,Sm), be the 265 total number of flows sent from node A to B. 267 In each flow Si consisting of K packets, we assign to each packet j a 268 sequence number aj which is a successive integer from 1 to K in the 269 order of the packet emission and so we create the source sequence as 270 (a1, . . . ,aK). Assume an output sequence (b1, . . . , bP) of Si 271 observed at the receiving node B, where P <= K be the total number of 272 packets received out of the K packets sent. Due to loss, the amount 273 K may less than P. 275 The sequence is said to be in order if for any index k (1 <= k <= P) 276 holds bk <= bq (0 <= q <= k), else the flow is said to reached at the 277 destination midordering, and the packet k is a reordered packet in 278 the reordered flow. The total number of reordered packets in flow Si 279 is written as Li. 281 For example, for the sequence of an arrived reordered flow 282 (1,2,3,5,4,7,6,8), there are 2 reordered packets (packet 4 and packet 283 6), which leads to L = 2. Note that in this document reordering does 284 not correlate with loss (same as [2][8][9]). For example, a received 285 flow (1,2,3,4,5,6,8) is considered as in order. 287 3. Security Considerations 289 TBD. 291 4. IANA Considerations 293 TBD. 295 5. Acknowledgements 297 TBD. 299 6. References 301 6.1. Informative References 303 [RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., 304 and W. Weiss, "An Architecture for Differentiated 305 Services", RFC 2475, DOI 10.17487/RFC2475, December 1998, 306 . 308 6.2. Normative References 310 [I-D.chen-detnet-loss-delay] 311 Chen, M. and A. Malis, "DetNet Packet Loss and Delay 312 Performance Measurement", draft-chen-detnet-loss-delay-01 313 (work in progress), October 2018. 315 [I-D.ietf-detnet-architecture] 316 Finn, N., Thubert, P., Varga, B., and J. Farkas, 317 "Deterministic Networking Architecture", draft-ietf- 318 detnet-architecture-12 (work in progress), March 2019. 320 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 321 Requirement Levels", BCP 14, RFC 2119, 322 DOI 10.17487/RFC2119, March 1997, 323 . 325 [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, 326 "Definition of the Differentiated Services Field (DS 327 Field) in the IPv4 and IPv6 Headers", RFC 2474, 328 DOI 10.17487/RFC2474, December 1998, 329 . 331 [RFC3270] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, 332 P., Krishnan, R., Cheval, P., and J. Heinanen, "Multi- 333 Protocol Label Switching (MPLS) Support of Differentiated 334 Services", RFC 3270, DOI 10.17487/RFC3270, May 2002, 335 . 337 [RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay 338 Measurement for MPLS Networks", RFC 6374, 339 DOI 10.17487/RFC6374, September 2011, 340 . 342 Authors' Addresses 344 Liquan Chen 345 South-east University 346 No.2 Sipailou 347 Nanjing, Jiangsu 210096 348 PR China 350 Email: lqchen@seu.edu.cn 352 Sijie Qian 353 South-east University 354 No.2 Sipailou 355 Nanjing, Jiangsu 210096 356 PR China 358 Email: sijieqian@foxmail.com 360 Ting Ao 361 ZTE corporation 362 No.50 Software Avenue 363 Nanjing, Jiangsu 210012 364 PR China 366 Email: ao.ting@zte.com.cn 367 URI: http://www.zte.com.cn