[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 09:17:27 CET 2009
On Wed, 2 Dec 2009, Lutz Donnerhacke wrote: > * 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. No no no no. I do NOT want to duplicate the IPv4 table into IPv6 by doing that. I'd rather have a single /24 route per ASN for 6RD than multiple routes per ASN into 2002::/16. Also, the problem 6RD tries to solve won't be solved if I filter to only 2002::/16 and don't accept more specifics. -- 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 ]