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

[rpd] Draft inbound policy

Danny afahounko at
Sat Jun 18 11:00:16 UTC 2016

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
Unless your policy draft is only about Ipv4?

On Jun 18, 2016 6:57 AM, "Sander Steffann" <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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the RPD mailing list