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] New version (or followup) of RIPE-501 document...
- Previous message (by thread): [ipv6-wg] New version (or followup) of RIPE-501 document...
- Next message (by thread): [ipv6-wg] New version (or followup) of RIPE-501 document...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ivan Pepelnjak
ip at ioshints.info
Mon Jun 20 15:37:23 CEST 2011
Lack of IPv6 support in some LB products has nothing to do with orthodox beliefs in purity of NAT-less IPv6 world and all to do with the vendors' decisions to cut hardware costs by supporting only 32-bit addresses in their hardware implementation (if you have a software-only LB that still doesn't support IPv6 today, please let me know ;). And of course some of us were stupid enough (or trusting the vendor, which is the same thing) not to check whether the appliance we bought a few years ago will ever support IPv6. Ivan > > Getting more and more off-topic, but regardless of what purists might > think, load balancing is a crucial function (until TCP stack and/or socket > API get fixed - read: not likely) and at least some of them do and will > use some sort of NAT to do their job. > > I think this is the key point. While providers are not putting up content > on IPv6 for this reason, it is an issue. > > Tim
- Previous message (by thread): [ipv6-wg] New version (or followup) of RIPE-501 document...
- Next message (by thread): [ipv6-wg] New version (or followup) of RIPE-501 document...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]