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 ]
kzorba at otenet.gr
kzorba at otenet.gr
Mon Jun 20 20:34:04 CEST 2011
Quoting Ivan Pepelnjak <ip at ioshints.info>: > The minimum you need for load balancers is IPv6 host support, you > might add OPTIONAL support for routing protocols. > > Obviously they need to support 6-to-4 and 6-to-6 load balancing ... > are there any RFCs covering those? > This is indeed the question. Is there any work (in IETF probably) that describes what a load balancer is and what it should support in an IPv6 environment? If not I think we need to improvise. I also think that load balancing is crucial to the deployment not only for IPv6 content but any IPv6 service that needs to scale. Kostas > Ivan >
- 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 ]