Summary

  • At RIPE 93 on 26 October, NIC.br's Sávyo de Morais presented V6bench, an early open-source framework for testing whether an application completes work over IPv6.
  • Its API workflow generates DNS and test-plan scaffolding from an OpenAPI specification, then requires a person to customize variables, run scenarios and inspect results. The tool has limited tested use cases.

The router says yes. The login form says “come back with an IPv4 address.” That is the gap Sávyo de Morais brought to RIPE 93 on 26 October. IPv6 reaches the service, yet one dependency in a transaction may still refuse to play. A green network dashboard makes a handsome slide; it cannot buy a ticket through a broken checkout.

De Morais's original slides name the usual suspects: IPv4 literals, address validators, access lists, libraries, database fields, geolocation, authentication, logs and monitoring. They are possible failure surfaces, not an indictment of a named service. His proposed question is wonderfully blunt: after IPv4 is switched off, does the whole job still finish?

V6bench gives that question a workbench. For an API, the demonstration starts with an OpenAPI specification in JSON or YAML. The tool generates DNS and zone material and a ScanAPI test template. The operator then customizes the plan and its variables, executes it in a selected network environment and reads the CSV results. The project's own repository describes an early-stage implementation with possible bugs and a present focus on APIs. Calling the generated template a complete acceptance test would be like calling a blank boarding pass a holiday.

The environment choices matter. The deck lays out IPv4-only, dual-stack, IPv6-only and IPv6-with-NAT64 clients; its server side includes IPv6 with SIIT-DC. Running the lab requires more than a public IPv6 address: the slides specify a dual-stack host, root access, a Docker IPv6 bridge, Kathará and Jool. Each selected path tests a particular claim. A passing dual-stack request cannot quietly stand in for a completed IPv6-only customer journey.

An IETF working-group draft gives the wider testing vocabulary, including dependencies, authorization and logging. The NIC.br demonstration adds a concrete handoff: machine-generated starting points meet a service owner's choice of real workflows. The output should say which operation ran, in which environment, with which dependencies, and what “complete” meant. That is an acceptance record a buyer or operator can inspect; a green IPv6 icon is decoration.

Original sources