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] 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 ]
Daniel Suchy
danny at danysek.cz
Tue May 3 13:41:58 CEST 2011
On 05/03/2011 01:21 PM, Mikael Abrahamsson wrote: > 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. Not really. As LIR, I can obtain second, third, fourth PA and I'll pay almost the same membership fee. Well, there will be slight change due to category change - but extra large LIR pays 5500EUR - that's less than cost of three PI blocks in your pricing scheme and much larger address space available for anything... > 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. And who does that, in reality? Just look into global BGP table, look on prefixes advertised by Google, for example. Reality is, that people deaggregates right now and nobody filters them. Prefixes are announced by customers and customers are paying for that to their upstream providers. In the fact, not policy, but sales department controls, what is announced in global tables. Daniel
- 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 ]