A new Request for Comments is now available in online RFC libraries.
RFC 9693
Title: Benchmarking Methodology for Stateful NATxy
Gateways
Author: G. Lencse,
K. Shima
Status: Informational
Stream: IETF
Date: January 2025
Mailbox: [email protected],
[email protected]
Pages: 24
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bmwg-benchmarking-stateful-09.txt
URL: https://www.rfc-editor.org/info/rfc9693
DOI: 10.17487/RFC9693
RFC 2544 defines a benchmarking methodology for network interconnect
devices. RFC 5180 addresses IPv6 specificities, and it also provides
a technology update but excludes IPv6 transition technologies. RFC
8219 addresses IPv6 transition technologies, including stateful
NAT64. However, none of them discuss how to apply pseudorandom port
numbers from RFC 4814 to any stateful NATxy (such as NAT44, NAT64,
and NAT66) technologies. This document discusses why using
pseudorandom port numbers with stateful NATxy gateways is a difficult
problem. It recommends a solution that limits the port number ranges
and uses two test phases (phase 1 and phase 2). This document shows
how the classic performance measurement procedures (e.g., throughput,
frame loss rate, latency, etc.) can be carried out. New performance
metrics and measurement procedures are also defined for measuring the
maximum connection establishment rate, connection tear-down rate, and
connection tracking table capacity.
This document is a product of the Benchmarking Methodology Working Group of the
IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
