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/[email protected]/
[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 09:09:16 CET 2009
* Mikael Abrahamsson wrote: > If we have separate space for /24 allocation policy then at least I can > filter the de-aggregation and stop some of the madness. Use the 2002::/16 space for 6to4 unicast routing. You do not need special software (works out of the box), you do not need special allocations, you only have to ask for route objects. If you do not accept those routes, the system still works. And if 6to4 get's depreceated sometimes, all those more specific routes, setup etc. will vanish altogether by dropping 2002::/16 ge 16 routes.
- 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 ]