idnits 2.17.1 draft-xiao-nvo3-pm-geneve-01.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 21, 2020) is 1429 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-option-tlv-04 == Outdated reference: A later version (-03) exists of draft-xiao-nvo3-bfd-geneve-02 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 22, 2020 S. Pallagatti 6 VMware 7 May 21, 2020 9 Performance Measurement for Geneve 10 draft-xiao-nvo3-pm-geneve-01 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 22, 2020. 35 Copyright Notice 37 Copyright (c) 2020 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . 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 Headers . . . . . . . 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. Normative References . . . . . . . . . . . . . . . . . . . . 8 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 67 1. Introduction 69 "Generic Network Virtualization Encapsulation" (Geneve) 70 [I-D.ietf-nvo3-geneve] provides an encapsulation scheme that allows 71 building an overlay network by decoupling the address space of the 72 attached virtual hosts from that of the network. 74 This document describes the use of Simple Two-way Active Measurement 75 Protocol [RFC8762] to enable measuring the performance of the path 76 between two Geneve tunnel endpoints. 78 Analogous to [I-D.xiao-nvo3-bfd-geneve], in this document, NVE 79 (Network Virtualization Edge) represents the Geneve tunnel endpoint, 80 TS (Tenant System) represents the physical or virtual device attached 81 to a Geneve tunnel endpoint from the outside, and VAP (Virtual Access 82 Point) represents the NVE side of the interface between the NVE and 83 the TS. 85 2. Conventions Used in This Document 87 2.1. Terminology 89 Geneve: Generic Network Virtualization Encapsulation 91 NVE: Network Virtualization Edge 93 PM: Performance Measurement 95 STAMP: Simple Two-way Active Measurement Protocol 97 TS: Tenant System 98 VAP: Virtual Access Point 100 VNI: Virtual Network Identifier 102 2.2. Requirements Language 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 106 "OPTIONAL" in this document are to be interpreted as described in BCP 107 14 [RFC2119] [RFC8174] when, and only when, they appear in all 108 capitals, as shown here. 110 3. PM Packet Transmission over Geneve Tunnel 112 PM session is originated and terminated at VAP of an NVE, selection 113 of the PM packet encapsulation is based on how the VAP encapsulates 114 the data packets. This document defines two formats of PM packet 115 encapsulation in Geneve: 117 o with Ethernet and IP/UDP encapsulation; 119 o with IP/UDP encapsulation. 121 3.1. PM Encapsulation With Inner Ethernet/IP/UDP Header 123 If the VAP that originates the PM packets is used to encapsulate 124 Ethernet data frames, then PM packets are encapsulated in Geneve as 125 described below. 127 0 1 2 3 128 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 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | | 131 ~ Outer Ethernet Header ~ 132 | | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | | 135 ~ Outer IPvX Header ~ 136 | | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | | 139 ~ Outer UDP Header ~ 140 | | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | | 143 ~ Geneve Header ~ 144 | | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | | 147 ~ Inner Ethernet Header ~ 148 | | 149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 150 | | 151 ~ Inner IPvX Header ~ 152 | | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | | 155 ~ Inner UDP Header ~ 156 | | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | | 159 ~ STAMP Test Packet ~ 160 | | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | Outer Ethernet FCS | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 Figure 1: Geneve Encapsulation of PM Packet With the Inner 166 Ethernet/IP/UDP Header 168 The STAMP test packet MUST be carried inside the inner Ethernet frame 169 of the Geneve packet, immediately after the inner IP/UDP headers. 170 The inner Ethernet frame carrying the STAMP Test Packet has the 171 following format: 173 The Ethernet header and IP header are encoded as defined in 174 Section 3.1 of [I-D.xiao-nvo3-bfd-geneve]. 176 The destination UDP port MUST be set the well-known port 862 as 177 defined in [RFC8762]. 179 The STAMP Test Packet SHOULD be unauthenticated STAMP Session-Sender 180 test packet or unauthenticated STAMP Session-Reflector test packet. 181 The STAMP Test Packet is encoded as specified in [RFC8762] and 182 [I-D.ietf-ippm-stamp-option-tlv]. 184 When the PM packets are encapsulated in Geneve in this way, the 185 values in the Geneve header are set as specified in Section 3.1 of 186 [I-D.xiao-nvo3-bfd-geneve]. 188 3.2. PM Encapsulation With Inner IP/UDP Headers 190 If the VAP that originates the PM packets is used to encapsulate IP 191 data packets, then PM packets are encapsulated in Geneve as described 192 below. 194 0 1 2 3 195 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 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | | 198 ~ Ethernet Header ~ 199 | | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | | 202 ~ Outer IPvX Header ~ 203 | | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | | 206 ~ Outer UDP Header ~ 207 | | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | | 210 ~ Geneve Header ~ 211 | | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | | 214 ~ Inner IPvX Header ~ 215 | | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | | 218 ~ Inner UDP Header ~ 219 | | 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | | 222 ~ STAMP Test Packet ~ 223 | | 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 | FCS | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 Figure 2: Geneve Encapsulation of PM Message With the Inner IP/UDP 229 Header 231 A STAMP test packet MUST be carried inside the inner IP packet that 232 immediately follows the Geneve header. The inner IP packet carrying 233 the STAMP Test Packet has the following format: 235 The IP header is encoded as defined in Section 3.2 of 236 [I-D.xiao-nvo3-bfd-geneve]. 238 The destination UDP port MUST be set the well-known port 862 as 239 defined in [RFC8762]. 241 The STAMP Test Packet SHOULD be unauthenticated STAMP Session-Sender 242 test packet or unauthenticated STAMP Session-Reflector test packet. 243 The STAMP Test Packet is encoded as specified in [RFC8762] and 244 [I-D.ietf-ippm-stamp-option-tlv]. 246 When the PM packets are encapsulated in Geneve in this way, the 247 values in the Geneve header are set as specified in Section 3.2 of 248 [I-D.xiao-nvo3-bfd-geneve]. 250 4. Reception of PM packet from Geneve Tunnel 252 Once a packet is received, the NVE MUST validate the packet as 253 specified in Section 4 of [I-D.xiao-nvo3-bfd-geneve], except that the 254 received STAMP test packet would be processed by STAMP Session-Sender 255 or STAMP Session-Reflector, instead of BFD. 257 4.1. Demultiplexing of the PM packet 259 Analogous to BFD over Geneve, multiple PM sessions for the same VNI 260 may be running between two NVEs, so there needs to be a mechanism for 261 demultiplexing received PM packets to the proper session. 263 If the PM packet is received with STAMP Session Identifier equals to 264 0, the procedure for demultiplexing the received PM packets would 265 follow the procedure for demultiplexing the received BFD packets with 266 Your Discriminator equals to 0, which is specified in Section 4.1 of 267 [I-D.xiao-nvo3-bfd-geneve]. 269 If the PM packet is received with a non-zero STAMP Session 270 Identifier, then PM session MUST be demultiplexed only with STAMP 271 Session Identifier as the key. 273 5. Security Considerations 275 This document does not raise any additional security issues beyond 276 those of the specifications referred to in the list of normative 277 references. 279 6. IANA Considerations 281 This document has no IANA action requested. 283 7. Acknowledgements 285 TBA. 287 8. Normative References 289 [I-D.ietf-ippm-stamp-option-tlv] 290 Mirsky, G., Xiao, M., Nydell, H., Foote, R., Masputra, A., 291 and E. Ruffini, "Simple Two-way Active Measurement 292 Protocol Optional Extensions", draft-ietf-ippm-stamp- 293 option-tlv-04 (work in progress), March 2020. 295 [I-D.ietf-nvo3-geneve] 296 Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic 297 Network Virtualization Encapsulation", draft-ietf- 298 nvo3-geneve-16 (work in progress), March 2020. 300 [I-D.xiao-nvo3-bfd-geneve] 301 Xiao, M., Mirsky, G., and J. Networks, "BFD for Geneve", 302 draft-xiao-nvo3-bfd-geneve-02 (work in progress), February 303 2020. 305 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 306 Requirement Levels", BCP 14, RFC 2119, 307 DOI 10.17487/RFC2119, March 1997, 308 . 310 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 311 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 312 May 2017, . 314 [RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple 315 Two-Way Active Measurement Protocol", RFC 8762, 316 DOI 10.17487/RFC8762, March 2020, 317 . 319 Authors' Addresses 321 Xiao Min 322 ZTE Corp. 323 Nanjing 324 China 326 Phone: +86 25 88013062 327 Email: xiao.min2@zte.com.cn 329 Greg Mirsky 330 ZTE Corp. 331 USA 333 Email: gregimirsky@gmail.com 334 Santosh Pallagatti 335 VMware 337 Email: santosh.pallagatti@gmail.com