This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
- Previous message (by thread): [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
- Next message (by thread): [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Pekka Savola
pekkas at netcore.fi
Tue May 4 07:14:57 CEST 2010
On Mon, 3 May 2010, Gert Doering wrote: >> http://labs.ripe.net/content/ipv6-ripeness > > You're asking for ideas for the "5th star". Some random thoughts... > > - have IPv6 transport (with addresses from their own prefix) to all/some of > the DNS servers that the IPv6 reverse zone is delegated to For the purposes of automation, I'd say "at least one of the (reverse) DNS servers for the prefix answers to a DNS query over v6" should be sufficient, and better than the two first alternatives. While there may be some small relevance whether the DNS server is from another prefix, it would result in false negatives in the cases where a (somehow defined) organisation is using multiple prefixes (e.g. due to mergers etc.). That would be confusing. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
- Previous message (by thread): [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
- Next message (by thread): [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]