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 ]
Lutz Donnerhacke
lutz at iks-jena.de
Wed Dec 2 15:20:10 CET 2009
* Rémi Després wrote: > This is avoided with 6rd which is safe, as theory shows and practice > confirms. More specific unicast of 2002::/16 also proofed to work in production. And now? Nobody has an interest in fixing the broken routers for 2002::/16? So let's take a new prefix from the pool and iterate until other technical problems occur? Then take the next prefix ... Sorry, drop and waste is not the recommended allocation policy for any ressource.
- 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 ]