Clone this wiki locally
summary Mirroring opportunities and operating models
test-ipv6.com is looking for mirrors, under a variety of models.
- Unofficial mirrors: You deploy for your organization or customer base as you see fit. Please stay on the email@example.com mailing list, and keep your installation up to date!
- Official mirrors: Deployed for the public, and listed on http://test-ipv6.com/mirrors.html . Additionally used by all mirrors for IPv6-capable clients, to validate global connectivity (aka, the "Other Sites" tab, that IPv6-enabled users see on our site).
- Transparent mirrors: These look and feel like the real site - only ran on your network.
Mirror sites are beneficial:
- Country specific mirrors can help ensure localized content is translated, and focus on needs within that region.
- A distribution of mirrors can help some users understand if their are path-dependent failure cases
- Can provide necessary capacity if significantly high traffic hits the master site, more than the master site can accommodate.
- Larger mirrors list can help crowd-source internet peering issues between the end user, and all of the mirrors
Please keep up to date if you are going to run a mirror.
If you consider running a mirror, ask yourself these questions:
- Will it be for your customers only?
- Would you consider letting it be on the official mirrors list?
- Does it require translation for your audience? Who can do the translation?
- Who will keep the mirror up to date?
If I maintain your mirror: Please examine the following requirements.
This is a particularly interesting option for larger internet service providers, who use test-ipv6.com as part of their customer support / help desk flow. This removes most of the burden from my site (making volume less of an issue). It also ensures that the actual detailed tests are ran entirely in your network, and not confused by public transit issues.
Running a transparent mirror means that "test-ipv6.com" itself will be on your network. The same look and feel; the same branding; the same commenting options; the same stats url. Most importantly: after a user takes the test, the test results are posted back to my server in the USA. Some jurisdictions may make this questionable. If you're in such a jurisdiction, a transparent mirror is not for you. Instead, run a mirror under your domain, where you can control whether or not that data is collected.
Users are sent to your instance of test-ipv6.com automatically. This is done by looking at where the DNS request came from; and mapping this back to your network BGP ASN. Queries from your ASN (or ASNs plural) will be routed to your VM instance. If your VM is down, my DNS server will detect that; and fall back to serving off the master site.
If you do opt to provide a transparent mirror, you'll still be encouraged to offer a non-transparent version of the mirror site (i.e., test-ipv6.example.com). This will allow people to explicitly use your site to test IPv6. They may want to do this because of your physical location in the world (picking an in-coutry mirror, or at least a nearby mirror). This will also be useful when testing connectivity from all clients visiting all mirrors, connecting back to you on IPv6 for a quick validation.