<div dir="ltr">Ask RIPE NCC going to routing level to check announcement might not be such a good idea.<div><br></div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 11, 2015 at 2:57 PM, Garry Glendown <span dir="ltr"><<a href="mailto:garry@nethinks.com" target="_blank">garry@nethinks.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
>> I will readily admit that I can not come up with a text which prevents<br>
>> abuse _and_ allows for valid operational needs, though.<br>
> Indeed. Mergers & acquisitions are real-world business events that APWG<br>
> cannot affect. I see a big nut to crack on how to address abuse via<br>
> "illegitimate" M&A, including figuring out what is and what is not<br>
> "illegitimate" and "abuse".<br>
I reckon if/when this proposal has gone through (either confirmed or<br>
rejected), some sane solution to this whole thing has to be found ... as<br>
several people - even some nay-sayers - have said, the current proposal<br>
does not cover enough bases to discourage or prevent policy abuse.<br>
<br>
I'm sure that - as it has a direct impact on the business of both<br>
IP-brokers and wannabe-profiteers - it will face even stronger<br>
opposition by several people, but most likely no substantial arguments<br>
(as we have already seen these last couple days - after all, saying "it<br>
will cut in my personal profit" won't be a valid argument against the<br>
policy to knowingly cut into profits of policy-abusers in order to allow<br>
late entries into the ISP market some affordable set of IPv4 addresses).<br>
<br>
Without really thinking about all possibilities, I would imagine there<br>
are certain reasons for or against the transfer of IPs, though some<br>
wording and "way of proof" would have to be found that be used to decide<br>
whether a transfer was permitted or not ...<br>
<br>
>From the top of my head, for a transfer, certain situations come to mind:<br>
<br>
* merger/acquisition of company (can be proved through official<br>
papers/registration information)<br>
* is there actually any other justifiable reason?<br>
<br>
Personally, I would see certain use cases where a transfer is not<br>
necessary for any technical/organizational reasons: (which may even<br>
weigh stronger than e.g. the merger/acquisition argument)<br>
<br>
* shutdown of an ISP or company, where loss of IP usage would not impact<br>
customers (current use is terminated, IPs are no longer announced)<br>
* IPs were never (publicly?) used or only intermittently announced (how<br>
could actual use be documented apart from just an announcement? Would an<br>
announcement on the Internet be sufficient?), or have been unused for a<br>
certain amount of time (3 months?)<br>
<br>
Due to the fact that IP addresses (especially PAs assigned to an LIR)<br>
are not "owned" by the LIR (in part documented by the yearly bill for<br>
the resource) IPs should not count as an asset with monetary value, thus<br>
allowing the RIR to collect them if policy requirements aren't met.<br>
<br>
Possibly: Requirement to announce and use IPs from last-/8 within 3<br>
months of assignment, otherwise the non-transferal-duration would be<br>
extended by 1 year<br>
<br>
*putting on flame-resistant armor*<br>
<span class="HOEnZb"><font color="#888888"><br>
-garry<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">--<br>Kind regards.<br>Lu<br><br>This transmission is intended solely for the addressee(s) shown above.<br>It may contain information that is privileged, confidential or<br>otherwise protected from disclosure. Any review, dissemination or use<br>of this transmission or its contents by persons other than the<br>intended addressee(s) is strictly prohibited. If you have received<br>this transmission in error, please notify this office immediately and<br>e-mail the original at the sender's address above by replying to this<br>message and including the text of the transmission received.</div>
</div></div></div>