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] Transfer Requirements for IPv4 Allocations
- Previous message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
- Next message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Vladimir Andreev
vladimir at quick-soft.net
Thu Apr 23 14:38:35 CEST 2015
I mean official (accepted) documents. For now we also have a discussion :) 23.04.2015, 15:36, "Mikael Abrahamsson" <swmike at swm.pp.se>: > On Thu, 23 Apr 2015, Vladimir Andreev wrote: >>> openig a bunch of LIR only for transfering their /22 V4 to another LIR >>> is - and always was - abusing the policy. >> Any links to documents proving it? > > Read the mailing list discussions about the last /8 policy. The /22 per > LIR was always about having new entrants to the market being able to at > least get a little chunk of addresses so they could have NAT444, email > servers etc. > > It was NEVER meant for people to start LIR, get /22, transfer /22, close > LIR, start another LIR, get another /22, transer /22, close LIR, repeat > again and again. If the community wanted it to work that way, the policy > would have been very differently worded. > > -- > Mikael Abrahamsson email: swmike at swm.pp.se -- With best regards, Vladimir Andreev General director, QuickSoft LLC Tel: +7 903 1750503
- Previous message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
- Next message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]