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/ipv6-wg@ripe.net/
[ipv6-wg] Have we failed as IPv6 Working Group?
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jens Link
lists at quux.de
Wed Oct 9 19:03:28 CEST 2019
Sander Steffann <sander at steffann.nl> writes: > I would expect such devices mostly in a home network (gaming consoles > etc). On a business meeting network like RIPE the number of IPv4-only > devices is negligible. I guess there will be quite a few devices were people disable IPv6. >> We cannot use DNS64 if we expect IPv4 literals or local DNSSEC validation. > > I am sure the few of us who run local DNSSEC validation would love the > opportunity to make it work. Finding IPv4 literals and fixing them is a > feature :) And finding hosts in DNSSEC signed zones not supporting IPv6. I know at least one. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink at quux.de | --------------- | ----------------------------------------------------------------------------
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]