rfc9693v2.txt		rfc9693.txt
	Internet Engineering Task Force (IETF) G. Lencse		Internet Engineering Task Force (IETF) G. Lencse
	Request for Comments: 9693 Széchenyi István University		Request for Comments: 9693 Széchenyi István University
	Category: Informational K. Shima		Category: Informational K. Shima
	ISSN: 2070-1721 SoftBank Corp.		ISSN: 2070-1721 SoftBank Corp.
	December 2024		January 2025
	Benchmarking Methodology for Stateful NATxy Gateways		Benchmarking Methodology for Stateful NATxy Gateways
	Abstract		Abstract
	RFC 2544 defines a benchmarking methodology for network interconnect		RFC 2544 defines a benchmarking methodology for network interconnect
	devices. RFC 5180 addresses IPv6 specificities, and it also provides		devices. RFC 5180 addresses IPv6 specificities, and it also provides
	a technology update but excludes IPv6 transition technologies. RFC		a technology update but excludes IPv6 transition technologies. RFC
	8219 addresses IPv6 transition technologies, including stateful		8219 addresses IPv6 transition technologies, including stateful
	NAT64. However, none of them discuss how to apply pseudorandom port		NAT64. However, none of them discuss how to apply pseudorandom port
	skipping to change at line 46 ¶		skipping to change at line 46 ¶
	Internet Engineering Steering Group (IESG). Not all documents		Internet Engineering Steering Group (IESG). Not all documents
	approved by the IESG are candidates for any level of Internet		approved by the IESG are candidates for any level of Internet
	Standard; see Section 2 of RFC 7841.		Standard; see Section 2 of RFC 7841.
	Information about the current status of this document, any errata,		Information about the current status of this document, any errata,
	and how to provide feedback on it may be obtained at		and how to provide feedback on it may be obtained at
	https://www.rfc-editor.org/info/rfc9693.		https://www.rfc-editor.org/info/rfc9693.
	Copyright Notice		Copyright Notice
	Copyright (c) 2024 IETF Trust and the persons identified as the		Copyright (c) 2025 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Revised BSD License text as described in Section 4.e of the		include Revised BSD License text as described in Section 4.e of the
	Trust Legal Provisions and are provided without warranty as described		Trust Legal Provisions and are provided without warranty as described
	skipping to change at line 536 ¶		skipping to change at line 536 ¶
	As described in [RFC4814], pseudorandom port numbers are REQUIRED,		As described in [RFC4814], pseudorandom port numbers are REQUIRED,
	which the authors believe is a good approximation of the distribution		which the authors believe is a good approximation of the distribution
	of the source port numbers a NATxy gateway on the Internet may be		of the source port numbers a NATxy gateway on the Internet may be
	faced with.		faced with.
	Although the enumeration of all possible four tuples is not a		Although the enumeration of all possible four tuples is not a
	requirement for the first extreme situation and the usage of		requirement for the first extreme situation and the usage of
	different four tuples in test phase 1 is not a requirement for the		different four tuples in test phase 1 is not a requirement for the
	second extreme situation, pseudorandom enumeration of all possible		second extreme situation, pseudorandom enumeration of all possible
	four tuples in test phase 1 is a good solution in both cases.		four tuples in test phase 1 is a good solution in both cases.
	Pseudorandom enumeration of all possible four tuples may be computing		Pseudorandom enumeration of all possible four tuples may be generated
	efficiently generated by preparing a random permutation of the		in a computationally efficient way by using Durstenfeld's random
	previously enumerated all possible four tuples using Durstenfeld's		shuffle algorithm [DUST1964] to prepare a random permutation of the
	random shuffle algorithm [DUST1964].		previously enumerated all possible four tuples.
	The enumeration of the four tuples in increasing or decreasing order		The enumeration of the four tuples in increasing or decreasing order
	(or in any other specific order) MAY be used as an additional		(or in any other specific order) MAY be used as an additional
	measurement.		measurement.
	4.5. Measurement of the Maximum Connection Establishment Rate		4.5. Measurement of the Maximum Connection Establishment Rate
	The maximum connection establishment rate is an important		The maximum connection establishment rate is an important
	characteristic of the stateful NATxy gateway, and its determination		characteristic of the stateful NATxy gateway, and its determination
	is necessary for the safe execution of test phase 1 (without frame		is necessary for the safe execution of test phase 1 (without frame
	skipping to change at line 1039 ¶		skipping to change at line 1039 ¶
	of the DUT. If the DUT is a general-purpose computer and some		of the DUT. If the DUT is a general-purpose computer and some
	software NATxy gateway implementation is tested, then the hardware		software NATxy gateway implementation is tested, then the hardware
	description SHOULD include the following:		description SHOULD include the following:
	* computer type		* computer type
	* CPU type		* CPU type
	* number of active CPU cores		* number of active CPU cores
	* memory type		* memory type, size, and speed
	* size and speed
	* network interface card type (also reflecting the speed)		* network interface card type (also reflecting the speed)
	* direct cable connections or the type of switch used for		* the fact that direct cable connections were use or the type of
	interconnecting the Tester and the DUT		switch used for interconnecting the Tester and the DUT
	The operating system type and version, kernel version, and version of		The operating system type and version, kernel version, and version of
	the NATxy gateway implementation (including the last commit date and		the NATxy gateway implementation (including the last commit date and
	number if applicable) SHOULD also be given.		number if applicable) SHOULD also be given.
	7. Implementation and Experience		7. Implementation and Experience
	The stateful extension of siitperf [SIITPERF] is an implementation of		The stateful extension of siitperf [SIITPERF] is an implementation of
	this concept. Its first version that only supports multiple port		this concept. Its first version that only supports multiple port
	numbers is documented in this (open access) paper: [LEN2022]. Its		numbers is documented in this (open access) paper: [LEN2022]. Its
End of changes. 5 change blocks.
	11 lines changed or deleted		9 lines changed or added
This html diff was produced by rfcdiff 1.48.