| NVO3 Working Group | X. Min |
| Internet-Draft | G. Mirsky |
| Intended status: Standards Track | ZTE Corp. |
| Expires: May 6, 2020 | S. Pallagatti |
| VMware | |
| November 3, 2019 |
Performance Measurement for Geneve
draft-xiao-nvo3-pm-geneve-00
This document describes the method to achieve Performance Measurement (PM) in point-to-point Generic Network Virtualization Encapsulation (Geneve) tunnels that form an overlay network.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 6, 2020.
Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
"Generic Network Virtualization Encapsulation" (Geneve) [I-D.ietf-nvo3-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 Packet Loss and Delay Measurement for MPLS Networks [RFC6374], as well as Simple Two-way Active Measurement Protocol [I-D.ietf-ippm-stamp], to enable measuring the performance of the path between two Geneve tunnel endpoints.
In this document, NVE (Network Virtualization Edge) represents a Geneve tunnel endpoint, TS (Tenant System) represents a physical or virtual device attached to a Geneve tunnel endpoint, and VAP (Virtual Access Point) represents the NVE side of the interface between the NVE and the TS.
GAL: Generic Associated Channel Label
G-ACh: Generic Associated Channel
Geneve: Generic Network Virtualization Encapsulation
MPLS: Multiprotocol Label Switching
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
Analogous to what's specified in Section 3 of [I-D.xiao-nvo3-bfd-geneve], this document considers three options of PM packet encapsulation in Geneve:
If the Protocol Type field (as defined in Section 3.4 of [I-D.ietf-nvo3-geneve]) of data packets indicates that an inner Ethernet header immediately follows the Geneve header, i.e., the Protocol Type equals to 0x6558 (Ethernet frame), then PM packets are encapsulated in Geneve as described below.
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer Ethernet Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer IPvX Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer UDP Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Geneve Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Inner Ethernet Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Inner IPvX Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Inner UDP Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ STAMP Test Packet ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FCS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Geneve Encapsulation of PM Message With the Inner Ethernet/IP/UDP Header
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: [I-D.ietf-ippm-stamp] and [I-D.ietf-ippm-stamp-option-tlv].
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
If the PM packets are encapsulated in Geneve as described above, the values in the Geneve header are set as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Ver| Opt Len |O|C| Rsvd. | Protocol Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Virtual Network Identifier (VNI) | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Variable Length Options |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Geneve Header
If the Protocol Type field (as defined in Section 3.4 of [I-D.ietf-nvo3-geneve]) of data packets indicates that an inner IP header immediately follows the Geneve header, i.e., the Protocol Type equals to 0x0800 (IPv4) or 0x86DD (IPv6), then PM packets are encapsulated in Geneve as described below.
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer Ethernet Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer IPvX Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer UDP Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Geneve Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Inner IPvX Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Inner UDP Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ STAMP Test Packet ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FCS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Geneve Encapsulation of PM Message With the Inner IP/UDP Header
A STAMP test packet MUST be carried inside the inner IP/UDP packet that immediately follows the Geneve header. The values in the inner IP packet carrying the STAMP Test Packet are as follows: [I-D.ietf-ippm-stamp] and [I-D.ietf-ippm-stamp-option-tlv].
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
When the PM packets are encapsulated in Geneve in this way, the Geneve header follows the value set below.
If the Protocol Type field (as defined in Section 3.4 of [I-D.ietf-nvo3-geneve]) of data packets indicates that an MPLS label stack immediately follows the Geneve header, i.e., the Protocol Type equals to 0x8847 (MPLS) or 0x8848 (MPLS with the upstream-assigned label), then PM packets are encapsulated in Geneve, as described below.
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer Ethernet Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer IPvX Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Outer UDP Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Geneve Header ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS Interface Context Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS GAL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS G-ACh |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Measurement Message, |
~ Delay Measurement Message, or ~
| Combined Loss/Delay Measurement Message |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FCS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Geneve Encapsulation of PM Message With the Inner MPLS GAL/G-ACh
The Loss Measurement Message, Delay Measurement Message, or Combined Loss/Delay Measurement Message MUST be carried inside the inner MPLS packet that immediately follows the Geneve header. The values in the inner MPLS packet carrying the Loss Measurement Message, Delay Measurement Message, or Combined Loss/Delay Measurement Message are as follows:
When the PM packets are encapsulated in Geneve in this way, the Geneve header follows the value set below.
Once a packet is received, NVE MUST validate the packet as described in [I-D.ietf-nvo3-geneve] and Section 4 of [I-D.xiao-nvo3-bfd-geneve].
Similar to BFD over Geneve, multiple PM sessions 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 Session Identifier value equals to 0, for different PM encapsulation, the procedure for demultiplexing the received PM packets is different, which would follow the procedure for a BFD packet with Your Discriminator equals to 0, as specified in Section 4.1 of [I-D.xiao-nvo3-bfd-geneve].
If the PM packet is received with a non-zero Session Identifier, then PM session MUST be demultiplexed only with Session Identifier as the key.
With respect to PM for Geneve, the use of the specific VNI would follow the principle as specified in Section 4.1 of [I-D.xiao-nvo3-bfd-geneve].
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.
| [I-D.ietf-bfd-vxlan] | Networks, J., Paragiri, S., Govindan, V., Mudigonda, M. and G. Mirsky, "BFD for VXLAN", Internet-Draft draft-ietf-bfd-vxlan-07, May 2019. |
| [I-D.ietf-ippm-stamp] | Mirsky, G., Jun, G., Nydell, H. and R. Foote, "Simple Two-way Active Measurement Protocol", Internet-Draft draft-ietf-ippm-stamp-10, October 2019. |
| [I-D.ietf-ippm-stamp-option-tlv] | Mirsky, G., Xiao, M., Nydell, H., Foote, R., Masputra, A. and E. Ruffini, "Simple Two-way Active Measurement Protocol Optional Extensions", Internet-Draft draft-ietf-ippm-stamp-option-tlv-02, October 2019. |
| [I-D.ietf-nvo3-geneve] | Gross, J., Ganga, I. and T. Sridhar, "Geneve: Generic Network Virtualization Encapsulation", Internet-Draft draft-ietf-nvo3-geneve-14, September 2019. |
| [I-D.xiao-nvo3-bfd-geneve] | Xiao, M., Mirsky, G. and J. Networks, "BFD for Geneve", Internet-Draft draft-xiao-nvo3-bfd-geneve-01, October 2019. |
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. |
| [RFC5586] | Bocci, M., Vigoureux, M. and S. Bryant, "MPLS Generic Associated Channel", RFC 5586, DOI 10.17487/RFC5586, June 2009. |
| [RFC6374] | Frost, D. and S. Bryant, "Packet Loss and Delay Measurement for MPLS Networks", RFC 6374, DOI 10.17487/RFC6374, September 2011. |
| [RFC8174] | Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017. |