idnits 2.17.1 draft-xiao-nvo3-pm-geneve-03.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 (May 17, 2021) is 1073 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 (-13) exists of draft-ietf-nvo3-bfd-geneve-02 == Outdated reference: A later version (-10) exists of draft-ietf-nvo3-geneve-oam-01 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NVO3 Working Group X. Min 3 Internet-Draft G. Mirsky 4 Intended status: Standards Track ZTE Corp. 5 Expires: November 18, 2021 S. Pallagatti 6 VMware 7 May 17, 2021 9 Performance Measurement for Geneve 10 draft-xiao-nvo3-pm-geneve-03 12 Abstract 14 This document describes the method to achieve Performance Measurement 15 (PM) in point-to-point Generic Network Virtualization Encapsulation 16 (Geneve) tunnels used to make up an overlay network. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on November 18, 2021. 35 Copyright Notice 37 Copyright (c) 2021 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 54 2.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 2 55 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 56 3. PM Packet Transmission over Geneve Tunnel . . . . . . . . . . 3 57 3.1. PM Encapsulation With Inner Ethernet/IP/UDP Header . . . 3 58 3.2. PM Encapsulation With Inner IP/UDP Header . . . . . . . . 5 59 4. Reception of PM packet from Geneve Tunnel . . . . . . . . . . 7 60 4.1. Demultiplexing of the PM packet . . . . . . . . . . . . . 7 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 62 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 63 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 64 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 65 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 66 8.2. Informative References . . . . . . . . . . . . . . . . . 8 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 69 1. Introduction 71 "Generic Network Virtualization Encapsulation" (Geneve) [RFC8926] 72 provides an encapsulation scheme that allows building an overlay 73 network by decoupling the address space of the attached virtual hosts 74 from that of the network. 76 This document describes the use of "Simple Two-way Active Measurement 77 Protocol" (STAMP) [RFC8762] and "Simple Two-Way Active Measurement 78 Protocol Optional Extensions" (STAMP Optional Extensions) [RFC8972], 79 to enable measuring the performance of the path between two Geneve 80 tunnel endpoints, like delay, delay variation, and packet loss. 82 Analogous to [I-D.ietf-nvo3-bfd-geneve], in this document, Network 83 Virtualization Edge (NVE) represents the Geneve tunnel endpoint, 84 Tenant System (TS) represents the physical or virtual device attached 85 to a Geneve tunnel endpoint from the outside, Virtual Access Point 86 (VAP) represents the NVE side of the interface between the NVE and 87 the TS, the usage of Management Virtual Network Identifier (VNI) is 88 described in [I-D.ietf-nvo3-geneve-oam] and outside the scope of this 89 document. 91 2. Conventions Used in This Document 93 2.1. Abbreviations 95 Geneve: Generic Network Virtualization Encapsulation 97 NVE: Network Virtualization Edge 98 PM: Performance Measurement 100 SSID: STAMP Session Identifier 102 STAMP: Simple Two-way Active Measurement Protocol 104 TS: Tenant System 106 VAP: Virtual Access Point 108 VNI: Virtual Network Identifier 110 2.2. Requirements Language 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 114 "OPTIONAL" in this document are to be interpreted as described in BCP 115 14 [RFC2119] [RFC8174] when, and only when, they appear in all 116 capitals, as shown here. 118 3. PM Packet Transmission over Geneve Tunnel 120 PM session is originated and terminated at VAP of an NVE, selection 121 of the PM packet encapsulation is based on how the VAP encapsulates 122 the data packets. This document defines two formats of PM packet 123 encapsulation in Geneve: 125 o with Ethernet and IP/UDP encapsulation; 127 o with IP/UDP encapsulation. 129 3.1. PM Encapsulation With Inner Ethernet/IP/UDP Header 131 If the VAP that originates the PM packets is used to encapsulate 132 Ethernet data frames, then PM packets are encapsulated in Geneve as 133 described below, here the PM packets are STAMP test packets. 135 0 1 2 3 136 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 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | | 139 ~ Outer Ethernet Header ~ 140 | | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | | 143 ~ Outer IPvX Header ~ 144 | | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | | 147 ~ Outer UDP Header ~ 148 | | 149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 150 | | 151 ~ Geneve Header ~ 152 | | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | | 155 ~ Inner Ethernet Header ~ 156 | | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | | 159 ~ Inner IPvX Header ~ 160 | | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | | 163 ~ Inner UDP Header ~ 164 | | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 | | 167 ~ STAMP Test Packet ~ 168 | | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 | Outer Ethernet FCS | 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 Figure 1: Geneve Encapsulation of PM Packet With the Inner 174 Ethernet/IP/UDP Header 176 The STAMP test packet MUST be carried inside the inner Ethernet frame 177 of the Geneve packet, immediately after the inner Ethernet/IP/UDP 178 header. The inner Ethernet frame carrying the STAMP test packet has 179 the following format: 181 The Ethernet header and IP header are encoded as defined in 182 Section 3.1 of [I-D.ietf-nvo3-bfd-geneve]. 184 The destination UDP port MUST follow the STAMP UDP port usage 185 defined in Section 4.1 of [RFC8762]. 187 The STAMP test packet can be STAMP Session-Sender test packet or 188 STAMP Session-Reflector test packet. The STAMP test packet is 189 encoded as specified in [RFC8762] and [RFC8972]. 191 When the PM packets are encapsulated in Geneve in this way, the 192 values in the Geneve header are set as specified in Section 3.1 of 193 [I-D.ietf-nvo3-bfd-geneve]. 195 3.2. PM Encapsulation With Inner IP/UDP Header 197 If the VAP that originates the PM packets is used to encapsulate IP 198 data packets, then PM packets are encapsulated in Geneve as described 199 below, here the PM packets are STAMP test packets. 201 0 1 2 3 202 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 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | | 205 ~ Ethernet Header ~ 206 | | 207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 208 | | 209 ~ Outer IPvX Header ~ 210 | | 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 | | 213 ~ Outer UDP Header ~ 214 | | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 | | 217 ~ Geneve Header ~ 218 | | 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | | 221 ~ Inner IPvX Header ~ 222 | | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | | 225 ~ Inner UDP Header ~ 226 | | 227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 | | 229 ~ STAMP Test Packet ~ 230 | | 231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 232 | FCS | 233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 Figure 2: Geneve Encapsulation of PM Packet With the Inner IP/UDP 236 Header 238 The STAMP test packet MUST be carried inside the inner IP packet that 239 immediately follows the Geneve header. The inner IP packet carrying 240 the STAMP test packet has the following format: 242 The IP header is encoded as defined in Section 3.2 of 243 [I-D.ietf-nvo3-bfd-geneve]. 245 The destination UDP port MUST follow the STAMP UDP port usage 246 defined in Section 4.1 of [RFC8762]. 248 The STAMP test packet can be STAMP Session-Sender test packet or 249 STAMP Session-Reflector test packet. The STAMP test packet is 250 encoded as specified in [RFC8762] and [RFC8972]. 252 When the PM packets are encapsulated in Geneve in this way, the 253 values in the Geneve header are set as specified in Section 3.2 of 254 [I-D.ietf-nvo3-bfd-geneve]. 256 4. Reception of PM packet from Geneve Tunnel 258 Once a packet is received, the NVE MUST validate the packet as 259 specified in Section 4 of [I-D.ietf-nvo3-bfd-geneve], except that the 260 received STAMP test packet would be processed by STAMP Session-Sender 261 or STAMP Session-Reflector, instead of BFD. 263 4.1. Demultiplexing of the PM packet 265 Analogous to BFD over Geneve, multiple STAMP sessions for the same 266 VNI may be running between two NVEs, so there needs to be a mechanism 267 for demultiplexing received STAMP test packets to the proper session. 269 If the STAMP test packet is received with STAMP Session Identifier 270 (SSID) equals to 0, the procedure for demultiplexing the received 271 STAMP test packets would follow the procedure for demultiplexing the 272 received BFD packets with Your Discriminator equals to 0, which is 273 specified in Section 4.1 of [I-D.ietf-nvo3-bfd-geneve]. 275 If the STAMP test packet is received with a non-zero SSID, then the 276 STAMP session MUST be demultiplexed only with SSID as the key. 278 5. Security Considerations 280 This document does not raise any additional security issues beyond 281 those of the specifications referred to in the list of references. 283 6. IANA Considerations 285 This document has no IANA action requested. 287 7. Acknowledgements 289 TBA. 291 8. References 292 8.1. Normative References 294 [I-D.ietf-nvo3-bfd-geneve] 295 Min, X., Mirsky, G., Pallagatti, S., and J. Tantsura, "BFD 296 for Geneve", draft-ietf-nvo3-bfd-geneve-02 (work in 297 progress), March 2021. 299 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 300 Requirement Levels", BCP 14, RFC 2119, 301 DOI 10.17487/RFC2119, March 1997, 302 . 304 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 305 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 306 May 2017, . 308 [RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple 309 Two-Way Active Measurement Protocol", RFC 8762, 310 DOI 10.17487/RFC8762, March 2020, 311 . 313 [RFC8926] Gross, J., Ed., Ganga, I., Ed., and T. Sridhar, Ed., 314 "Geneve: Generic Network Virtualization Encapsulation", 315 RFC 8926, DOI 10.17487/RFC8926, November 2020, 316 . 318 [RFC8972] Mirsky, G., Min, X., Nydell, H., Foote, R., Masputra, A., 319 and E. Ruffini, "Simple Two-Way Active Measurement 320 Protocol Optional Extensions", RFC 8972, 321 DOI 10.17487/RFC8972, January 2021, 322 . 324 8.2. Informative References 326 [I-D.ietf-nvo3-geneve-oam] 327 Mirsky, G., Boutros, S., Black, D., and S. Pallagatti, 328 "OAM for use in GENEVE", draft-ietf-nvo3-geneve-oam-01 329 (work in progress), November 2020. 331 Authors' Addresses 333 Xiao Min 334 ZTE Corp. 335 Nanjing 336 China 338 Phone: +86 25 88013062 339 Email: xiao.min2@zte.com.cn 340 Greg Mirsky 341 ZTE Corp. 342 USA 344 Email: gregory.mirsky@ztetx.com 346 Santosh Pallagatti 347 VMware 349 Email: santosh.pallagatti@gmail.com