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] 2014-02 New Policy Proposal (Allow IPv4 PI transfer)
- Previous message (by thread): [address-policy-wg] 2014-02 New Policy Proposal (Allow IPv4 PI transfer)
- Next message (by thread): [address-policy-wg] 2014-02 New Policy Proposal (Allow IPv4 PI transfer)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Thu Apr 24 17:24:26 CEST 2014
A couple of observations, fwiw, and no, I'm not going to assess the role of brokers :-) In general, let me start with the statement that I support all ideas to get rid of the different shapes and colours of address blocks. And that actually includes Legacy, as they are simply PI, just a tad older... How to deal with moving address space from a PI assignment to a different party? Well, I can see 2 *substantially* different scenarios: 1) the current holder of the address block doesn't need *all of it* any longer (and wants to get money from an interested party, but that's a side issue). 2) the current holder of the address block doesn't need *any* of the addresses any longer and wants to transfer the full block, in one chunk or in smaller pieces. Nr. 1 is pretty easy, and possible already or really soon now: convert the PI block to PA, thus become an LIR, and proceed according to the rules. Nr. 2 is more tricky. First of all, there was a good reason, why the resource was tightly bound to the requester. That background and assumption is also part of the basis for the low annual fee of €50,- per resource. Now, as soon as the original criteria are no longer in place, the resource MUST be returned. A PI holder offering the *full block* to an interested party (for money or for free) obviously matches that provision. The resource needs to get returned to the pool. So, why would we want to bend into this direction or that direction to create a special case for Nr. 2 to circumvent the existing policy? Just because some money is seen on the horizon? Which gets me to the point of *not* supporting this proposal! Wilfried.
- Previous message (by thread): [address-policy-wg] 2014-02 New Policy Proposal (Allow IPv4 PI transfer)
- Next message (by thread): [address-policy-wg] 2014-02 New Policy Proposal (Allow IPv4 PI transfer)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]