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] 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 ]
Jan Zorz @ go6.si
jan at go6.si
Mon Jun 20 18:33:23 CEST 2011
>>> 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. Ok, so I see some consensus on the question, if load balancers are needed in RIPE-501 foloowup document or not. The answer is yes. My question is, should we create new hw category for this or should we put it in any of existing category? Merike, Sander, I'm inviting you back to drawing board to fix this request :) /jan
- 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 ]