Performance Measurement for Geneve

"Generic Network Virtualization Encapsulation" (Geneve) provides an encapsulation scheme that allows building an overlay network by decoupling the address space of the attached virtual hosts from that of the network. This document describes the use of Simple Two-way Active Measurement Protocol to enable measuring the performance of the path between two Geneve tunnel endpoints. Analogous to , in this document, NVE (Network Virtualization Edge) represents the Geneve tunnel endpoint, TS (Tenant System) represents the physical or virtual device attached to a Geneve tunnel endpoint from the outside, and VAP (Virtual Access Point) represents the NVE side of the interface between the NVE and the TS.

Geneve: Generic Network Virtualization Encapsulation NVE: Network Virtualization Edge PM: Performance Measurement STAMP: Simple Two-way Active Measurement Protocol TS: Tenant System VAP: Virtual Access Point VNI: Virtual Network Identifier

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 BCP 14 when, and only when, they appear in all capitals, as shown here.

PM session is originated and terminated at VAP of an NVE, selection of the PM packet encapsulation is based on how the VAP encapsulates the data packets. This document defines two formats of PM packet encapsulation in Geneve: with Ethernet and IP/UDP encapsulation; with IP/UDP encapsulation.

If the VAP that originates the PM packets is used to encapsulate Ethernet data frames, then PM packets are encapsulated in Geneve as described below.

The STAMP test packet MUST be carried inside the inner Ethernet frame of the Geneve packet, immediately after the inner IP/UDP headers. The inner Ethernet frame carrying the STAMP Test Packet has the following format: The Ethernet header and IP header are encoded as defined in Section 3.1 of . The destination UDP port MUST be set the well-known port 862 as defined in . The STAMP Test Packet SHOULD be unauthenticated STAMP Session-Sender test packet or unauthenticated STAMP Session-Reflector test packet. The STAMP Test Packet is encoded as specified in and . When the PM packets are encapsulated in Geneve in this way, the values in the Geneve header are set as specified in Section 3.1 of .

If the VAP that originates the PM packets is used to encapsulate IP data packets, then PM packets are encapsulated in Geneve as described below.

A STAMP test packet MUST be carried inside the inner IP packet that immediately follows the Geneve header. The inner IP packet carrying the STAMP Test Packet has the following format: The IP header is encoded as defined in Section 3.2 of . The destination UDP port MUST be set the well-known port 862 as defined in . The STAMP Test Packet SHOULD be unauthenticated STAMP Session-Sender test packet or unauthenticated STAMP Session-Reflector test packet. The STAMP Test Packet is encoded as specified in and . When the PM packets are encapsulated in Geneve in this way, the values in the Geneve header are set as specified in Section 3.2 of .

Once a packet is received, the NVE MUST validate the packet as specified in Section 4 of , except that the received STAMP test packet would be processed by STAMP Session-Sender or STAMP Session-Reflector, instead of BFD.

Analogous to BFD over Geneve, multiple PM sessions for the same VNI may be running between two NVEs, so there needs to be a mechanism for demultiplexing received PM packets to the proper session. If the PM packet is received with STAMP Session Identifier equals to 0, the procedure for demultiplexing the received PM packets would follow the procedure for demultiplexing the received BFD packets with Your Discriminator equals to 0, which is specified in Section 4.1 of . If the PM packet is received with a non-zero STAMP Session Identifier, then PM session MUST be demultiplexed only with STAMP Session Identifier as the key.

This document does not raise any additional security issues beyond those of the specifications referred to in the list of normative references.

This document has no IANA action requested.

TBA.