Resources: the standards we test against, answers and field notes
Five methodology pages for RFC 2544, RFC 2889, RFC 9411 with RFC 3511, RFC 6349 and ITU-T Y.1564, with the test setup, parameters and the shape of the report. A FAQ on how a project runs, a blog with protocol series and test notes, and industry news three times a week. Everything is written by the engineers who run the bench.
- 5methodology pages
- 20+answers in the FAQ
- 3 / weekindustry news digests
- EN · RU · HYblog and news languages
What is here
Four sections, each with a job
Pick by what you need right now: a method to put in a procurement document, an answer on how we work, a worked example from the bench, or what changed in the industry this week
- 1
Methodologies
RFC and ITU-T benchmarks, step by stepWhat a standard measures, how the bench is wired for it, which parameters we set and what the report contains. Written for the engineer who has to defend the numbers and the manager who signs the purchase.
- 2
FAQ
how a project runsScope, NDA, access to the bench, what counts as a test day, how a test plan turns into a quote, what we do not take on. Short answers, grouped by stage.
- 3
Blog
protocol series and bench notesHow we test BGP, OSPF, EVPN, IPsec and TLS; what breaks first under load; typical scenarios with realistic numbers. Each post reads on LinkedIn in two lines and on the page in full.
- 4
Industry news
three digests a weekOutages, vendor releases, standards updates and security advisories that touch network testing, summarised with a source link. Filter by topic, read in English, Russian or Armenian.
Methodologies
Five standards with a page each
Each page follows one structure: who the standard is for, the test bed, the parameter table, the tests, the procedure, the report. Three more are run on request and described in the index.
| Standard | What it measures | Typical device | On the bench |
|---|---|---|---|
| 01RFC 2544 | Throughput, latency, frame loss, back-to-back | Router, switch, firewall in L2-3 mode | 1–3 days per unit |
| 02RFC 2889 | Forwarding, MAC learning, congestion control | LAN and data-centre switch | 2–3 days per unit |
| 03RFC 9411 / RFC 3511 | Connections per second, concurrent sessions, L7 throughput | Firewall, NGFW, IPS | 3–5 days per profile |
| 04RFC 6349 | TCP throughput, efficiency, buffer delay | WAN link, SD-WAN, managed service | 1–2 days per path |
| 05ITU-T Y.1564 | CIR, EIR, delay, jitter, loss per service | Carrier Ethernet service, EVC | 2 h to 24 h per service set |
Durations are bench time for one unit or one path with a ready configuration; the test plan fixes the exact number before the quote
Can I use a methodology page in a tender or RFP?
Yes. Each page names the standard, the test setup, the parameters and the pass criteria, so it can be cited as the method section of an RFP. If you send us the document, we check that the plan we propose matches it line by line.
Are the reports and benchmarks public?
No. Reports belong to the client and stay under NDA. The blog carries typical scenarios with realistic numbers, built from the kind of work we do, without naming a client or a live project.
Which tools run the tests described here?
Commercial traffic generators and analysers in the CloudLAB rack, our own generator for stateful application mixes, WAN emulators and a Wi-Fi bench. The test plan names the tool behind each test; we do not default to one vendor.
How often is the content updated?
Methodology pages change when a standard or our bench changes. News is published three times a week, the blog roughly weekly. A page shows no author line or date by design; ask us if you need the revision history.
Can I get a methodology that is not listed?
RFC 5180 for IPv6, ITU-T Y.1731 for Ethernet OAM and TR-398 for Wi-Fi run on request and get a page once there is enough demand. Protocol-level tests such as BGP convergence or EVPN are covered in the blog series and in the test plan.
Have a device and a deadline?
Send the model and the KPIs that matter. You get a test plan draft within one business day and a quote in 1–3 business days.
Send the shortlist
You have the method. Now get the numbers.
Name the models and the KPIs that matter. An engineer replies within one business day with a test plan draft and a quote.
Prefer to chat? Message an engineer on WhatsApp
We use what you send only to answer you. See our Privacy Policy.