[Tsv-art] Tsvart last call review of draft-ietf-bmwg-evpntest-07
Jana Iyengar via Datatracker <email@example.com> Mon, 24 May 2021 17:38 UTC
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 214AE3A304B; Mon, 24 May 2021 10:38:25 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
From: Jana Iyengar via Datatracker <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org, email@example.com
Reply-To: Jana Iyengar <firstname.lastname@example.org>
Date: Mon, 24 May 2021 10:38:25 -0700
Subject: [Tsv-art] Tsvart last call review of draft-ietf-bmwg-evpntest-07
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Mon, 24 May 2021 17:38:25 -0000
Reviewer: Jana Iyengar Review result: Ready with Issues This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC email@example.com if you reply to or forward this review. The document seems fine overall. There are some minor grammar and consistency things, but I expect that the RFC-editors will handle those. The one thing that stuck out to me is the following: It helps in documents such as this to be more precise about exactly what a measurement tool or tester should consider success or failure. One piece of text where this precision should be improved is in the Soak Test (both 3.12 and 4.11): "The CPU spike is determined as the CPU usage which shoots at 40 to 50 percent of the average usage. The average value vary from device to device. Memory leak is determined by increase usage of the memory for EVPN process. The expectation is under steady state the memory usage for EVPN process should not increase." Perhaps something like the following for defining CPU spikes might be helpful: "A CPU spike is defined as a sudden increase and subsequent decrease in usage from average usage to about 150% of average usage." Similarly, memory leak is very weakly defined. Do you mean _any increase_ in memory usage, or is there a threshold that you want to propose? Do you mean consistent increase over time? Can you define a leak more precisely in the context of your test?
- [Tsv-art] Tsvart last call review of draft-ietf-b… Jana Iyengar via Datatracker
- Re: [Tsv-art] [Last-Call] Tsvart last call review… Sarah Banks