[AfriNIC-rpd] Transfer of IPv4 Addresses to Any Entity - AFPUB-2011-v4-001-draft-01

[Stacy Hughes]

Hi AfriNic Contituents,
Here is the latest we have from ARIN-announce:
"Based on ARIN’s Public Policy Mailing List (arin-ppml at arin.net) discussion
in February 2011 and concurrent interest from ARIN’s Board of Trustees, the
procedure requiring a Legacy or standard Registration Services Agreement (
Legacy RSA or RSA) for resources being transferred has been revised.
Effective immediately, the transferor of legacy address space is not
required to have the resources under a current registration services
agreement with ARIN."

We just made it easier.
Let me know if you have any questions,
Stacy


On Fri, Apr 22, 2011 at 2:49 AM, Andrew Alston <aa at tenet.ac.za> wrote:

> Hi Walu,
>
> The space is currently useable anywhere in reality, irrespective of it's
> registration.
>
> Until rpki becomes a reality (and that in and of itself is a terrifying
> proposition), all you have to do is create some route objects in a database
> like altdb and announce it. At most people could log complaints with your
> upstream and hopefully they will filter non legit space.
>
> The routing tables have no relation to who was assigned space or where is
> was assigned
>
> Thanks
>
> Andrew
>
> Sent from my iPhone
>
> On Apr 22, 2011, at 10:54, "Walubengo J" <jwalu at yahoo.com> wrote:
>
> Andrew,
>
> this is precisely what your proposal AFPUB-2011-v4-003-draft-02-"Limited
> Out of Region Allocation of IPv4 Resources (Proposal-Draft)" suggests.  And
> I think I asked this early this year in Feb and not sure if I got an
> answer...
>
> My question was, assume am a Legacy or even Non-legacy IP resource owner in
> Africa and I 'bypass' AfriNIC and transfer (polite for sell) the IP
> resources to Microsoft in the US.  Can M$ use these addresses without ARIN
> or AFRNIC registering the same in their whois database? Put differently, to
> what extend/effective are IP addresses that are not in registered in the
> respective whois databases route-able across the Internet?
>
> walu.
>
>
>
>
> --- On *Fri, 4/22/11, Andrew Alston <aa at tenet.ac.za>* wrote:
>
>
> From: Andrew Alston <aa at tenet.ac.za>
> Subject: Re: [AfriNIC-rpd] Transfer of IPv4 Addresses to Any Entity -
> AFPUB-2011-v4-001-draft-01
> To: "Walubengo J" <jwalu at yahoo.com>, "AfriNIC List" <rpd at afrinic.net>,
> <sm+afrinic at elandsys.com>sm+afrinic at elandsys.com
> Cc: "Alan Barrett" <apb at cequrux.com>
> Date: Friday, April 22, 2011, 11:29 AM
>
> Since Legacy IP Space was assigned before the existence of AfriNIC, I find
> it very hard to see how this could actually be stopped.
>
> ARIN has a method that Legacy IP space holders can declare their legacy
> assets and are then in effective exempt from future changes in the rules, I
> believe the same should apply in Africa.
>
> The simple fact is that it will be very difficult to apply rules
> retroactively to legacy holders, since as far as I can see they did not
> agree when receiving that space to the imposition of terms and conditions by
> AfriNIC.  The other point is, if we don’t allow legacy space holders to
> transfer space, the chances are, its going to happen anyway and all you will
> find is that your databases get completely out of sync with reality.  You
> either legitimize this and keep a measure of control, or you impose a rule
> that bars it, which is pretty much unenforceable and would also probably not
> hold up to a legal challenge, and let chaos ensue.
>
> That’s my take on it
>
> Andrew
>
>
>
> On 2011/04/22 8:32 AM, "Walubengo J" <jwalu at yahoo.com> wrote:
>
> thnx SM for the heads-up.
>
> I have just looked at this policy and have just one issue regarding how it
> provides for Legacy IP resource holders to transfer their IPv4 resources to
> any entity.
>
> The policy is silent on if/how the Legacy holders will follow the general
> AfriNIC policies for IP resources; namely conservation, aggregation and
> (unique) registration of the IP addresses. If this is not taken care of, we
> shall have/legitimize the following scenario Nortel Sells IP address to M$
> now playing out the US @
>  <http://blog.internetgovernance.org/blog/_archives/2011/4/15/4796200.html>
> http://blog.internetgovernance.org/blog/_archives/2011/4/15/4796200.html
>
> Is this good for Africa?
>
> walu.
> --- On *Fri, 4/22/11, sm+afrinic at elandsys.com <sm+afrinic at elandsys.com>*wrote:
>
>
> From: sm+afrinic at elandsys.com <sm+afrinic at elandsys.com>
> Subject: [AfriNIC-rpd] Transfer of IPv4 Addresses to Any Entity -
> AFPUB-2011-v4-001-draft-01
> To: rpd at afrinic.net
> Cc: "Alan Barrett" <apb at cequrux.com>
> Date: Friday, April 22, 2011, 1:19 AM
>
> Hello,
>
> There is currently a proposal under discussion in the AfriNIC service
> region about "Transfer of IPv4 Addresses to Any Entity".  The current draft
> is AFPUB-2011-v4-001-draft-01.  A proposal can only become a policy if it
> has the consensus of the Policy Development Working Group and it has been
> approved by the AfriNIC Board of Directors.
>
> The Interim co-chairs of the AfriNIC Policy Development Working Group never
> made any determination about whether there is consensus on
> AFPUB-2011-v4-001-draft-01 or made any recommendation on this proposal to
> the AfriNIC Board of Directors.
>
> Regards,
> S. Moonesamy
> Interim co-chair, AfriNIC Policy Development Working Group
>
> _______________________________________________
> rpd mailing list
> rpd at afrinic.net </mc/compose?to=rpd at afrinic.net>
>  <https://lists.afrinic.net/mailman/listinfo.cgi/rpd>
> https://lists.afrinic.net/mailman/listinfo.cgi/rpd
>
>
> ------------------------------
> _______________________________________________
> rpd mailing list
> rpd at afrinic.net
>  <https://lists.afrinic.net/mailman/listinfo.cgi/rpd>
> https://lists.afrinic.net/mailman/listinfo.cgi/rpd
>
>
> _______________________________________________
> rpd mailing list
> rpd at afrinic.net
> https://lists.afrinic.net/mailman/listinfo.cgi/rpd
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20110422/19efdf49/attachment.html>