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/policy-announce@ripe.net/
[policy-announce] [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Previous message (by thread): [policy-announce] [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Next message (by thread): [policy-announce] 2012-04 New Draft Document Published (PI Assignments from the last /8)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed Sep 5 15:19:41 CEST 2012
Hi, On Wed, Sep 05, 2012 at 12:04:02PM +0200, Wilfried Woeber, UniVie/ACOnet wrote: > With that point of view I'd like to ask for clarification of the following > provision: > > " > LIRs that receive a re-allocation from another LIR cannot re-allocate complete > or partial blocks of the same address space to another LIR within 24 months of > receiving the re-allocation. > " > > But the receiving LIR may do so with other parts from their IPv4 address pool? > What is the motivation for that particular restriction and for that particular > wording? Getting a transfer policy in place "back in the days" was a very difficult process, and the net result is a compromise... that particular sentence was there because it was feared that people would stockpile address space, wait for the price to rise, and then sell it off at a higher price - so, you have to sit on it for 24 months. This is not talking about a normal LIR, which has some free space here and there, might need something extra for a while, and then sell it off again... > And, I am wondering, whether the following restriction is (still) useful: > > " > The block that is to be re-allocated must not be smaller than the minimum > allocation block size at the time of re-allocation. > " Well, it's an attempt to avoid even further fragmentation of the IPv4 address space (and subsequent burdening of the routing system). We haven't seen that many transfers yet, so I, at least, don't know how "useful" or "harmful" that restriction is in practice. Shall we put these two topics on the agenda for the upcoming RIPE meeting (in "Y. Open Policy Hour")? Would you be willing to lead the discussion? Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
- Previous message (by thread): [policy-announce] [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Next message (by thread): [policy-announce] 2012-04 New Draft Document Published (PI Assignments from the last /8)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]