Updates for the Back-to-back Frame Benchmark in RFC 2544
draft-ietf-bmwg-b2b-frame-02
Network Working Group A. Morton
Internet-Draft AT&T Labs
Updates: 2544 (if approved) May 19, 2020
Intended status: Informational
Expires: November 20, 2020
Updates for the Back-to-back Frame Benchmark in RFC 2544
draft-ietf-bmwg-b2b-frame-02
Abstract
Fundamental Benchmarking Methodologies for Network Interconnect
Devices of interest to the IETF are defined in RFC 2544. This memo
updates the procedures of the test to measure the Back-to-back frames
Benchmark of RFC 2544, based on further experience.
This memo updates Section 26.4 of RFC 2544.
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] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
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 November 20, 2020.
Morton Expires November 20, 2020 [Page 1]
Internet-Draft B2B Frame Update May 2020
Copyright Notice
Copyright (c) 2020 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Scope and Goals . . . . . . . . . . . . . . . . . . . . . . . 3
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Back-to-back Frames . . . . . . . . . . . . . . . . . . . . . 7
5.1. Preparing the list of Frame sizes . . . . . . . . . . . . 7
5.2. Test for a Single Frame Size . . . . . . . . . . . . . . 7
5.3. Test Repetition and Benchmark . . . . . . . . . . . . . . 9
5.4. Benchmark Calculations . . . . . . . . . . . . . . . . . 9
6. Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1. Normative References . . . . . . . . . . . . . . . . . . 12
10.2. Informative References . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
The IETF's fundamental Benchmarking Methodologies are defined
in[RFC2544], supported by the terms and definitions in [RFC1242], and
[RFC2544] actually obsoletes an earlier specification, [RFC1944].
Over time, the benchmarking community has updated [RFC2544] several
times, including the Device Reset Benchmark [RFC6201], and the
important Applicability Statement [RFC6815] concerning use outside
the Isolated Test Environment (ITE) required for accurate
benchmarking. Other specifications implicitly update [RFC2544], such
as the IPv6 Benchmarking Methodologies in [RFC5180].
Morton Expires November 20, 2020 [Page 2]
Internet-Draft B2B Frame Update May 2020
Recent testing experience with the Back-to-back Frame test and
Benchmark in Section 26.4 of [RFC2544] indicates that an update is
warranted [OPNFV-2017] [VSPERF-b2b]. In particular, analysis of the
results indicates that buffers size matters when compensating for
disruptions in the software packet processor, and this finding
Show full document text