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/address-policy-wg@ripe.net/
[address-policy-wg] IPv6 allocations for 6RD
- Previous message (by thread): [address-policy-wg] IPv6 allocations for 6RD
- Next message (by thread): [address-policy-wg] IPv6 allocations for 6RD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Hogewoning
marcoh at marcoh.net
Wed Dec 2 10:31:11 CET 2009
On 2 dec 2009, at 10:20, Florian Frotzler wrote: > Hi Marco, > > I am slow in understanding, please clarify on this. Why exactly would > 6RD lead to more specifics? There are certainly reasons for load > balancing v6 traffic, but what changes 6RD in comparison to dual > stack? Well I can only assume what happens, but given the number of perfectly good /16's that get broken into small pieces 'because it is otherwise hard to loadbalance' What those people usually struggle with is that they have 2 uplinks, but one large CDN picking a particulair route will saturate one of them, so the break it up to split the traffic over multiple upstreams. It lead to the same problem if all of a sudden a large portion of their traffic moves to the /24 single annoucement, especially since they haven't invested too much in IPv6 connectivity. This of course can be solved by buying a bigger pipe, but then again the whole /24 can be avoided by running multiple instances of 6RD, since that was put down as additional cost I have no hopes on the /24 as well. MarcoH
- Previous message (by thread): [address-policy-wg] IPv6 allocations for 6RD
- Next message (by thread): [address-policy-wg] IPv6 allocations for 6RD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]