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 14:04:32 CEST 2011
On 05/03/2011 01:45 PM, Mikael Abrahamsson wrote: > > I surely hope not, then the current policy is defective. Last I heard, > RIPE made reservation for growth when handing out first /32, so next > it'll be /31, /30 etc, up to the reserved /29. > But, PI has minimum at /48. In /32, there're 65536 /48 blocks. And costs of LIR doesn't increase so much, if he moves from /32 to /31, 30... (and similary in IPv4). Thats' the point... And probably nobody will support change in current billing policy of RIPE NCC towards higher cost of larger PA assignments (=increase it's own costs). 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 ]