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 ]
Mikael Abrahamsson
swmike at swm.pp.se
Wed Dec 2 13:56:32 CET 2009
On Wed, 2 Dec 2009, michael.dillon at bt.com wrote: > What are the broken anycast routers? Why can't they be fixed? Because we (humanity) keep screwing up regarding MTU, capacity planning and other general operational practices, I postulate that 6to4 is never going to be a fully working service, there will always be users affected by badly run 6to4 anycasted relays. Running MTU1280 when doing 6to4 solves quite a lot of the problems, but it's still hard to localise problems when they occur because of the asymmetric nature of 6to4. -- Mikael Abrahamsson email: swmike at swm.pp.se
- 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 ]