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 ]
Jan Zorz @ go6.si
jan at go6.si
Tue Jun 21 09:53:58 CEST 2011
On 6/21/11 9:34 AM, Ivan Pepelnjak wrote: >> There must be better ways to address the problem in an IPv6 >> environment with L4 termination or L7 application layer proxies >> coming to mind. > > I guess not many ops-focused people have the luxury to care. > Regardless of how you do it, you lose end-to-end connectivity and > some visibility (the latter is BTW mandated by some standards like > PCI). > >> For me however, for a load balanced service, the requirement is one >> name in the DNS and not a single IP (v4 or v6) address. > > In a perfect world with perfectly architected and implemented TCP > stacks and no security issues mandating browser DNS pinning, you're > absolutely correct. > > In the imperfect world we have to live in, you usually stop fighting > the windmills and use a single IP address if you have to get enough > nines. > > Ivan > Pragatism as paradigm. I like that. BTW, do we have any LB vendor on the list with some useful suggestion? Cheers, /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 ]