[bmwg] Fwd: New Version Notification for draft-lencse-bmwg-benchmarking-stateful-00.txt

Gábor LENCSE <lencse@hit.bme.hu> Mon, 17 May 2021 14:54 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 256403A3ABD for <bmwg@ietfa.amsl.com>; Mon, 17 May 2021 07:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 TBiY1y3_qrQe for <bmwg@ietfa.amsl.com>; Mon, 17 May 2021 07:54:24 -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 F3BBC3A3AB8 for <bmwg@ietf.org>; Mon, 17 May 2021 07:54:23 -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 14HEs4SV080896 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <bmwg@ietf.org>; Mon, 17 May 2021 16:54:09 +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]
References: <162126201925.17418.4445553239495865130@ietfa.amsl.com>
To: bmwg@ietf.org
From: Gábor LENCSE <lencse@hit.bme.hu>
X-Forwarded-Message-Id: <162126201925.17418.4445553239495865130@ietfa.amsl.com>
Message-ID: <21644075-61c3-7582-4862-4334c5d7c44a@hit.bme.hu>
Date: Mon, 17 May 2021 16:54:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <162126201925.17418.4445553239495865130@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------5674713AA4CBAA973FB65A5F"
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--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/DeWnh8TVZSZFz_-1uo4Znnae2jM>
Subject: [bmwg] Fwd: New Version Notification for draft-lencse-bmwg-benchmarking-stateful-00.txt
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: Mon, 17 May 2021 14:54:29 -0000

Dear BMWG Members,

We have just submitted a new Internet Draft titled: "Benchmarking 
Methodology for Stateful NATxy Gateways using RFC 4814 Pseudorandom Port 
Numbers"

I am not aware of any similar method, thus I feel that there is a 
significant methological gap in this area, which we would like to bridge 
with our draft. It contains the basic ideas, but not all the details. 
First, we would like to check, if our concept is right, and then plan to 
work out and add all the details.

Therefore, we would like to ask your kind feedbacks.

As a proof of concept, I have made a partial implementation of the 
method, which is available in the "stateful" branch of siitperf: 
https://github.com/lencsegabor/siitperf

Some details of the design and implementation and a few sample 
measurement results are also available in my draft paper, which is 
currently under review: 
http://www.hit.bme.hu/~lencse/publications/SFNAT64-tester-for-review.pdf
(It may be removed at any time, especially, if the paper is rejected.)

Any feedback is welcome!

Best regards

Gábor Lencse

-------- Továbbított üzenet --------
Tárgy: 	New Version Notification for 
draft-lencse-bmwg-benchmarking-stateful-00.txt
Dátum: 	Mon, 17 May 2021 07:33:39 -0700
Feladó: 	internet-drafts@ietf.org
Címzett: 	Gabor Lencse <lencse@sze.hu>, Keiichi Shima <keiichi@iijlab.net>




A new version of I-D, draft-lencse-bmwg-benchmarking-stateful-00.txt
has been successfully submitted by Gabor Lencse and posted to the
IETF repository.

Name: draft-lencse-bmwg-benchmarking-stateful
Revision: 00
Title: Benchmarking Methodology for Stateful NATxy Gateways using RFC 
4814 Pseudorandom Port Numbers
Document date: 2021-05-17
Group: Individual Submission
Pages: 13
URL: 
https://www.ietf.org/archive/id/draft-lencse-bmwg-benchmarking-stateful-00.txt
Status: 
https://datatracker.ietf.org/doc/draft-lencse-bmwg-benchmarking-stateful/
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-lencse-bmwg-benchmarking-stateful
Htmlized: 
https://tools.ietf.org/html/draft-lencse-bmwg-benchmarking-stateful-00


Abstract:
RFC 2544 has defined a benchmarking methodology for network
interconnect devices. RFC 5180 addressed IPv6 specificities and it
also provided a technology update, but excluded IPv6 transition
technologies. RFC 8219 addressed IPv6 transition technologies,
including stateful NAT64. However, none of them discussed how to
apply RFC 4814 pseudorandom port numbers to any stateful NAT (NAT44,
NAT64, NAT66) technologies. We discuss why using pseudorandom port
numbers with stateful NAT gateways is a hard problem and recommend a
solution.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat