Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful
Gábor LENCSE <lencse@hit.bme.hu> Tue, 25 May 2021 20:12 UTC
Return-Path: <lencse@hit.bme.hu>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280873A1D4F for <bmwg@ietfa.amsl.com>; Tue, 25 May 2021 13:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sVcj8jhvmiPq for <bmwg@ietfa.amsl.com>; Tue, 25 May 2021 13:12:32 -0700 (PDT)
Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [IPv6:2001:738:2001:4020::2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 945DE3A1D4E for <bmwg@ietf.org>; Tue, 25 May 2021 13:12:32 -0700 (PDT)
Received: from [192.168.1.146] (host-79-121-40-143.kabelnet.hu [79.121.40.143]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id 14PKCDFu011689 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <bmwg@ietf.org>; Tue, 25 May 2021 22:12:19 +0200 (CEST) (envelope-from lencse@hit.bme.hu)
X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-40-143.kabelnet.hu [79.121.40.143] claimed to be [192.168.1.146]
To: bmwg@ietf.org
References: <CAERpkxBMxSsMZhSPHrRAptZkxyFPmMZfj=O29aSzC-Op9Kb5QA@mail.gmail.com>
From: Gábor LENCSE <lencse@hit.bme.hu>
Message-ID: <5e5acd05-720c-8888-b6c4-06feb249ce7d@hit.bme.hu>
Date: Tue, 25 May 2021 22:12:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <CAERpkxBMxSsMZhSPHrRAptZkxyFPmMZfj=O29aSzC-Op9Kb5QA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------5C15FA5DB8BD5953ACA5354E"
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.102.4 at frogstar.hit.bme.hu
X-Virus-Status: Clean
Received-SPF: pass (frogstar.hit.bme.hu: authenticated connection) receiver=frogstar.hit.bme.hu; client-ip=79.121.40.143; helo=[192.168.1.146]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10;
X-DCC-wuwien-Metrics: frogstar.hit.bme.hu; whitelist
X-Scanned-By: MIMEDefang 2.79 on 152.66.248.44
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/r2wb1Y8gbVlrW7KlMoi6anroKCU>
Subject: Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 May 2021 20:12:37 -0000
Dear Edwin Cordeiro, Thank you very much for your review and support! I would like to note regarding testing with TCP that all RFC 2544, RFC 5180 and also RFC 8219 recommends testing with UDP. Additional testing with TCP seems to be feasible, but it requires some considerations and design decisions. For example, whereas you can simply send UDP datagrams as test traffic, but you need to establish a TCP connection first. The 3-way handshake may be done during the preliminary phase, and one can send TCP segments as test traffic in the real test phase. However, it is does not seem trivial to me, how deeply the Tester should follow the TCP protocol. On the one hand, perfectly implementing all the rules of the TCP protocol would impose a lot of limitations on the Tester, thus it would not be able to send test frames at the required rates. This would prohibit the execution of the benchmarking tests like throughput, frame loss rate, latency etc, :-( On the other hand, normal routers do not look into the TCP protocol header, but NAT boxes do. Thus sending TCP segments with improper Sequence number, Acknowledgement number, etc. fields could result in different problems in the DUT depending on how deeply it follows the TCP protocol. Best regards, Gábor 24/05/2021 13:51 keltezéssel, Edwin Cordeiro írta: > Dear authors of draft-lencse-bmwg-benchmarking-stateful, > > I agree with the motivation and ideas of the draft and I support its > adoption. > > I recommend that the TCP considerations for such benchmarking > methodology should not be left for a future document, as TCP still is > the most used protocol. So, the details on TCP difficulties and an > extension of this benchmark to consider TCP, should be in the scope of > this document. > > Best regards, > > Edwin Cordeiro > > _______________________________________________ > bmwg mailing list > bmwg@ietf.org > https://www.ietf.org/mailman/listinfo/bmwg
- [bmwg] draft-lencse-bmwg-benchmarking-stateful Edwin Cordeiro
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Gábor LENCSE
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Edwin Cordeiro
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Keiichi SHIMA
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Łukasz Bromirski
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Keiichi SHIMA
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Gábor LENCSE
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Sandor R. Repas Dr.
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Gábor LENCSE
- Re: [bmwg] draft-lencse-bmwg-benchmarking-stateful Keiichi SHIMA