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 only network at RIPE 68
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nicolas CARTRON
nicolas at ncartron.org
Fri May 16 15:09:05 CEST 2014
On Fri, May 16, 2014 at 2:44 PM, Andrew 👽 Yourtchenko <ayourtch at gmail.com>wrote: > Zbynek, > > The choice for having a NAT64 was to provide a more gentle headstart, > since a NAT64 has a strictly bigger set of apps/sites that do work. > And, we felt that we should tread lightly - maximize the potential of > actually using the v6only as a "business as usual" SSID. > > The "true IPv6-only" was a DNS server address away: e.g. you could > temporarily hardcode the 2001:4860:4860::8888 for the tests, instead > of the DNS64 local resolver address. > > But would be very interesting to hear from the community, what would > people think is the most useful option to do ? Fully agreed with Zbynek, having a v6-only network would be interesting as well. -- Nicolas -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ipv6-wg/attachments/20140516/088c4a6a/attachment.html>
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]