On 5/23/12 12:01 PM, Tore Anderson wrote:
> * Ingrid Wijte
>> I would like to give some further clarification on this.
>> The RIPE NCC allocates/assigns address space to organisations who have a
>> need in the RIPE NCC service region. The address space must be
>> originated from the RIPE NCC service region. Due to the diverse nature
>> of businesses, in addition to this there can be announcements from other
> Just to make 110% certain, you're saying here that it is the *need* that
> must be in the RIPE region, not the *organisation*, correct?
The need and the route origination must be in the RIPE NCC service region.
> Example 1: China Unicom sets up a legal organisation in the Netherlands,
> joins the NCC, and requests an allocation from which they intend to
> assign addresses to broadband customers in China. They intend to
> advertise the allocated prefix(es) to peers at AMS-IX (as well as from
> other exchange points around the world).
This example would be ok for several reasons:
The requestor is a RIPE NCC member. They have infrastructure in the
region and the address space will originate from the RIPE NCC service
Other similar examples would be VPN Providers but also Satellite
providers that are based in the region and have customers globally.
> Example 2: I, representing an existing LIR in the RIPE region, build a
> data center in Australia and set up a server hosting business there. I
> want to make an assignment to a new customer in this data center from my
> IPv4 allocation received from the RIPE NCC, and request that from the
> NCC hostmater using a ripe-488 form.
As long as the prefix is originated in the RIPE NCC service region, this
would be approved. The LIR has an allocation, is announcing it in the
RIPE NCC service region, and is making PA assignments to its customers.
Registration Services Assistant Manager
> Assuming all the documentation is otherwise in order and the need is
> real, will these requests be granted or denied?
> Best regards,