Announcing RIPE assigned prefix in ARIN/APNIC region

[Ivan Pepelnjak]

Well, the way I read that same email (with my optimistic glasses on):

* You have to have a need in RIPE region - check;
* You have to originate the address space from RIPE region - check (you
might want to advertise the "prefix of last resort" in all regions anyway)
* You can originate the address space from other regions - nice, problem
solved
* Having BGP speakers outside of RIPE region is not a problem - seems like
we don't have a problem at all.

Best,
Ivan


On Fri, May 3, 2013 at 12:05 PM, Shane Kerr <shane at time-travellers.org>wrote:

> Peter,
>
> On Thu, 2 May 2013 22:39:46 +0200
> Peter Mueller <ipv6ops at gmail.com> wrote:
> >
> > One question which came to my mind was whether or not it is ok to
> > announce a RIPE assigned prefix (the /36) in the ARIN/APNIC Region?
> > or should i go to ARIN/APNIC and request additional prefixes?
>
> Here's an answer from the RIPE NCC on the RIPE Address Policy mailing
> list:
>
>
> http://www.ripe.net/ripe/mail/archives/address-policy-wg/2012-May/006971.html
>
> In principle, it seems that you should go to ARIN and APNIC and request
> additional prefixes.
>
> In practice, the RIPE NCC doesn't monitor this stuff. I'm not
> recommending that you violate policy, just pointing out that it is very
> unlikely that there will ever be any repercussions, and even then the
> punishment will likely just be you having to get additional addresses
> at that time.
>
> The whole "regional Internet registry" is weird, since the Internet is
> global. :-P
>
> Cheers,
>
> --
> Shane
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20130503/785b3af8/attachment.htm>