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] getting second IPv6 PA as a LIR
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Tue May 3 13:21:56 CEST 2011
On Tue, 3 May 2011, Daniel Suchy wrote: > This doesn't making sense at all. Or then each (!!) PA assigment also > must cost 2000EUR (or more, depending on assigment size, as PA > assignments are generally larger than PI assignments). Well, you're already getting charged for the LIR cost, I don't have a problem giving discount for LIR+PA costing the same as PA. > If you only increase cost of PI, "smart people" just starts using their > PA block divided into several parts... As mentioned by Marcin Kuczera > today, this is happening ALREADY... just look into your BGP table, his > scenario isn't fiction (just is hapening on their 1st IPv6 PA)... Well, then I guess we'll just have to make sure we filter at RIR allocation size. If people announce /36 from /32 PA space, we won't accept their routes. -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]