Network Working Group G. Mirsky Internet-Draft Ericsson Intended status: Standards Track 26 June 2023 Expires: 28 December 2023 Performance Measurement with Asymmetrical Packets in STAMP draft-mirsky-ippm-asymmetrical-pkts-00 Abstract This document describes an optional extension to a Simple Two-way Active Measurement Protocol (STAMP) that enables the use of STAMP test and reflected packets of variable length during a single STAMP test session. In some use cases, the use of asymmetrical test packets allow for the creation of more realistic flows of test packets and, thus, a closer approximation between active performance measurements and conditions experienced by the monitored application. Status of This Memo 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 28 December 2023. Copyright Notice Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved. Mirsky Expires 28 December 2023 [Page 1] Internet-Draft Asymmetrical Packets in STAMP June 2023 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3 3. Reflected Test Packet Control TLV . . . . . . . . . . . . . . 3 3.1. Theory of Operation . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction Simple Two-way Active Measurement Protocol (STAMP) [RFC8762] defined the STAMP base functionalities and, among them, the use of symmetrical test packets. In some scenarios, e.g., rate measurements discussed in [RFC7497], it is beneficial not only to use a variable size of the test packets transmitted downstream while controlling length, number, and interpacket interval for reflected test packets. This document specifies an optional extension of STAMP as defined in [RFC8972] that allows for control of the length, number, and interpacket interval of a reflected STAMP test packets transmitted in response to a received STAMP test packet. 1.1. Terminology STAMP Simple Two-way Active Measurement Protocol Mirsky Expires 28 December 2023 [Page 2] Internet-Draft Asymmetrical Packets in STAMP June 2023 1.2. Requirements Language 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] and [RFC8174] when, and only when, they appear in all capitals, as shown here. 2. Problem Statement STAMP ([RFC8762]) allows for variable lengths of the test packets transmitted by a Session-Sender. [RFC7497] analyses rate measurement scenarios where it is beneficial to enable control of the responding node reflecting the received test packet with a different length and, in some cases, with a series of equally timed test packets. 3. Reflected Test Packet Control TLV This document defines a new optional STAMP extension, Reflected Test Packet Control TLV. The format of the Reflected Test Packet Control TLV is presented in Figure 1. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |STAMP TLV Flags| Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length of the Reflected Packet | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of the Reflected Packets | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interval Between Reflected Packets | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Sub-TLVs ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Reflected Test Packet Control TLV Format The interpretation of the fields is as follows: STAMP TLV Flags is a one-octet field. Type is a fourteen-bit field that identifies the Reflected Test Packet Control TLV. IANA is requested (Section 4) to assign (TBD1) value. Mirsky Expires 28 December 2023 [Page 3] Internet-Draft Asymmetrical Packets in STAMP June 2023 Length is a two-octet field. The value is variable, not smaller than 12 octets. Length of the Reflected Packet is a four-octet field. The value is an unsigned integer that is the requested length of a reflected test packet in octets. Number of the Reflected Packets is a four-octet field. The value is the number of reflected test packets the Session-Reflector is requested to transmit in response to receiving a STAMP test packet with the Reflected Test Packet Control TLV. Interval Between Reflected Packets is a four-octet field. The value is an unsigned integer set to the interval in milliseconds between the transmission of the consecutive reflected test packets in response to receiving a STAMP test packet with the Reflected Test Packet Control TLV. Sub-TLVs - optional field that includes additional information communicated by a Session-Sender. A Session-Sender MAY include the Reflected Test Packet Control TLV in a STAMP test packet. If the received STAMP test packet includes the Reflected Test Packet Control TLV, the Session-Reflector MUST transmit a sequence of reflected test packets according to the following rules: The length of the reflected test packet MUST be the largest of the length of the Session-Reflector packet in the mode matching mode of the received STAMP test packet, as defined in Section 4.3 of [RFC8762] with all the present in the received STAMP test packet STAMP extension TLVs [RFC8972], excluding the Extra Padding TLV, and the value in the Length of the Reflected Packet aligned at a four-octets boundary. The Session-Reflector MUST use the Extra Padding TLV (Section 4.1 of [RFC8972]) to increase the length of the reflected test packet. The number of reflected test packets in the sequence MUST equal to the value of the Number of the Reflected Test Packets. If the value of the Number of Reflected Packets is larger than one, the interval between the transmission of two consecutive reflected packets in the sequence MUST be equal to the value in the Interval Between Reflected Packets in milliseconds. Mirsky Expires 28 December 2023 [Page 4] Internet-Draft Asymmetrical Packets in STAMP June 2023 If the value of the Number of Reflected Packets equals zero, then the Session-Reflector MUST NOT send a reflected packet. Processing of the received STAMP test packet with the Reflected Test Packet Control TLV is according to the local policy. Each reflected test packet in the sequence is formed according to Section 4.3 of [RFC8762]. 3.1. Theory of Operation TBA 4. IANA Considerations The IANA is requested to assign a new value for the Reflected Test Packet Control TLV from the STAMP TLV Types subregistry according to Table 1. +=========+===================================+===============+ | Value | Description | Reference | +=========+===================================+===============+ | (TBD1) | Reflected Test Packet Control TLV | This document | +---------+-----------------------------------+---------------+ Table 1: New Reflected Test Packet Control Type TLV 5. Security Considerations Security considerations discussed in [RFC8762] and [RFC8972] apply to this document. Furthermore, spoofed STAMP test packets with the Reflected Test Packet Control TLV can be exploited to conduct Denial- of-Service attack. Hence, implementations MUST provide a means of checking the source addresses of the STAMP test packets containing the Reflected Test Packet Control TLV. 6. Acknowledgments TBA 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Mirsky Expires 28 December 2023 [Page 5] Internet-Draft Asymmetrical Packets in STAMP June 2023 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple Two-Way Active Measurement Protocol", RFC 8762, DOI 10.17487/RFC8762, March 2020, . [RFC8972] Mirsky, G., Min, X., Nydell, H., Foote, R., Masputra, A., and E. Ruffini, "Simple Two-Way Active Measurement Protocol Optional Extensions", RFC 8972, DOI 10.17487/RFC8972, January 2021, . 7.2. Informative References [RFC7497] Morton, A., "Rate Measurement Test Protocol Problem Statement and Requirements", RFC 7497, DOI 10.17487/RFC7497, April 2015, . Author's Address Greg Mirsky Ericsson Email: gregimirsky@gmail.com Mirsky Expires 28 December 2023 [Page 6]