Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] Merges/Acquisitions/Closures document

Andrew Alston Andrew.Alston at
Thu Feb 20 08:13:10 UTC 2014

Tough question,

I have to say for me, if you aggregate the space into a single organization that is sub-assigning to the op-co's, you SHOULD need to follow the standard utilization rules to get more space.

That being said, keep in mind that IP space is not necessarily tied to an ASN, and yes, I know it's horrible and it results in deaggregation, but in Saul's case there is nothing stopping him as an LIR doing a sub-assignment to the other company which would then push him over the 75% mark on the holding company, then applying for more space under the holding company.

This would be completely within the rules and totally legitimate.



From: lordmwesh at [mailto:lordmwesh at] On Behalf Of Kivuva
Sent: Thursday, February 20, 2014 10:58 AM
To: Saul Stein
Cc: Seun Ojedeji; Andrew Alston; rpd
Subject: Re: [rpd] Merges/Acquisitions/Closures document

Using Saul's experience, should this "policy" go to PDP?

Mwendwa Kivuva, Nairobi, Kenya.<>
google ID | Skype ID: lordmwesh

On 20 February 2014 09:43, Saul Stein <saul at<mailto:saul at>> wrote:

I have had a different but similar problem in the past:
We opened a pop in another region, not connected to our existing infrastructure, so it has its own AS. Since we hadn't used out 75% IP allocation, we were not able to get IP space for this region (no problem with additional AS number). I didn't go into it in depth, but guess it fell foul partially to this policy.

The guys at AFRINIC all understood the problem, but due to "policy", the only way around was to join again and let the other region be a second AFRINIC member at additional cost.

From: rpd-bounces at<mailto:rpd-bounces at> [mailto:rpd-bounces at<mailto:rpd-bounces at>] On Behalf Of Seun Ojedeji
Sent: 19 February 2014 09:22 PM
To: Andrew Alston
Cc: rpd

Subject: Re: [rpd] Merges/Acquisitions/Closures document

Hello Andrew,

On 19 Feb 2014 16:49, "Andrew Alston" <Andrew.Alston at<mailto:Andrew.Alston at>> wrote:
> Hi McTim,
> See this is my question.  If this IS a set of procedures, then things it lacks clarity on either need more process, or policy.
> An example (which I assume that up till now would be dealt with under this policy):
> A holding company owns 8 op-co's.  Those entities continue to exist, but the holding companies wishes to merge all their resources into the holding company to create a single administrative entity which then sub-assigns to its op-co's.  Now, technically this is not a merger nor an acquisition, and the IP space will continue to be USED by the entities that it was assigned to and for the same purpose.  However, it is merged into the holding the company so that there is ONE member and ONE administrative entity.
> Is a situation like that covered under this document?

The way I understand the document, I think your scenario is not applicable as the merger referred on the guideline is based on entities(organisations) and not on resource OR better put, a merger needs to happen at organisation level before resource update can be considered (2.1..... Following this policy guideline, AFRINIC must ensure that for each merger and/or takeover, the resulting organization is planning to continue using the allocated/assigned number resources for the original criteria under which these resources were issued.....).

Disclaimer: My individual view (not Co-chairs')
sent from Google nexus 4
kindly excuse brevity and typos.

rpd mailing list
rpd at<mailto:rpd at>

DISCLAIMER: This email contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient, you must not use, disclose, copy, print, or rely on this email. We cannot accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of this company or one of its agents.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the RPD mailing list