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

[rpd] Draft inbound policy

Barrack Otieno otieno.barrack at
Mon Jun 20 05:34:54 UTC 2016

Hi all,

I support the Policy, when getting into a transitory period the old is
as important as the new, IP v4 will still be necessary as much as we
all desire to migrate to v6.


On 6/19/16, Christopher Mwangi <christopher.mwangi at> wrote:
> Hi Danny,
> An example would be Mergers and acquisition where an organization wanted to
> consolidate all resources (IPs and ASNs) into an African holding company.
> So we thought of having this one policy that all inclusive and takes care of
> that.
> Thanks
> Christopher
> ________________________________
> From: Danny <afahounko at>
> Sent: Saturday, June 18, 2016 2:00:16 PM
> To: Sander Steffann
> Cc: rpd List
> Subject: Re: [rpd] Draft inbound policy
> Hello Andrews,
> We all agreed that IPv6 is the way to go (IPv4 depletion,  no NAT, etc..).
> In real use case what situation can force an infrastructure based in Afrinic
> region to use IPv6  ressources from other regions? And we all know that IPv6
> by design can scale and cover almost all new generation infrastructures.
> Unless your policy draft is only about Ipv4?
> Regards,
> Danny
> On Jun 18, 2016 6:57 AM, "Sander Steffann"
> <sander at<mailto:sander at>> wrote:
> Hi Kris,
>> @Sander : What are the key provisions of the outbound policy in Ripe? or
>> is there a two way policy already in place?
> Our policy is very simple:
> RIPE currently has a policy that can work both ways, we work with whatever
> the other RIR requires. For transfers from the RIPE region we basically
> require that the outbound transfer conforms to the RIPE policy. For example:
> there are resources that cannot be transferred within 24 months of the
> seller getting them, to prevent people from getting or buying addresses and
> then selling them on immediately. Such restriction obviously still apply.
> Roughly: if the transfer would be valid for a RIPE->RIPE transfer, it will
> also be valid for RIPE->OTHER-RIR transfers.
> Cheers,
> Sander
> _______________________________________________
> RPD mailing list
> RPD at<mailto:RPD at>

Barrack O. Otieno
Skype: barrack.otieno
PGP ID: 0x2611D86A

More information about the RPD mailing list