<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi Daniel, The IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region state that ' <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> These policies apply to the RIPE NCC and the Local Internet Registries (LIRs) within the RIPE NCC service region.' <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> In addition, RFC 2050 says: "This document makes a distinction between the allocation of IP addresses and the assignment of IP addresses. Addresses are allocated to ISPs by regional registries to assign to its customer base. ISPs who exchange routing information with other ISPs at multiple locations and operate without default routing may request space directly from the regional registry in its geographical area. ISPs with no designated regional registry may contact any regional registry and the regional registry may either handle the request or refer the request to an appropriate registry." The RIPE NCC interprets these statements as we explained on the mailing list. If the RIPE community feels this interpretation is not correct, do let us know. Regards, Ingrid Wijte Registration Services Assistant Manager RIPE NCC On 5/24/12 9:09 AM, Daniel Roesen wrote: <blockquote cite="mid:20120524070922.GB16448@srv03.cluenet.de" type="cite"> <pre wrap="">On Wed, May 23, 2012 at 11:13:15AM +0200, Ingrid Wijte wrote: </pre> <blockquote type="cite"> <pre wrap="">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 regions. </pre> </blockquote> <pre wrap="">Could you please point us to the policy requiring such routing requirements? Best regards, Daniel </pre> </blockquote> </body> </html>