RIPE NCC: Difference between revisions
No edit summary |
No edit summary |
||
Line 33: | Line 33: | ||
RIPE NCC was established on September 16th, 1990, to deal with administrative tasks for RIPE, although it was not formally established and recognized until 1992. RIPE NCC did not become a separate legal entity until 1998. Although the two organizations are legally independent today, they remain highly interdependent. RIPE NCC supports RIPE by facilitating RIPE meetings and providing support for RIPE working groups. RIPE NCC maintains the RIPE database, a public database containing registration details of the IP addresses and AS numbers originally allocated to members by the RIPE NCC.<ref>[http://www.ripe.net/ripe/about/the-history-of-ripe RIPE History], RIPE.net.</ref> | RIPE NCC was established on September 16th, 1990, to deal with administrative tasks for RIPE, although it was not formally established and recognized until 1992. RIPE NCC did not become a separate legal entity until 1998. Although the two organizations are legally independent today, they remain highly interdependent. RIPE NCC supports RIPE by facilitating RIPE meetings and providing support for RIPE working groups. RIPE NCC maintains the RIPE database, a public database containing registration details of the IP addresses and AS numbers originally allocated to members by the RIPE NCC.<ref>[http://www.ripe.net/ripe/about/the-history-of-ripe RIPE History], RIPE.net.</ref> | ||
In November 2011, RIPE NCC received a temporary order from Dutch police that prevented any changes from being made to a registration of four specific blocks of [[IPv4]] address space in the RIPE Registry. The injunction was ordered the 8th of November and | In November 2011, RIPE NCC received a temporary order from Dutch police that prevented any changes from being made to a registration of four specific blocks of [[IPv4]] address space in the RIPE Registry. The injunction was ordered the 8th of November and was in effect through March 22, 2012.<ref>[http://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/ripe-ncc-blocks-registration-in-ripe-registry-following-order-from-dutch-police NCC Blocks Registration, ripe.net]</ref> In return, the organization intended to settle the matter further in Dutch court. It did not withdraw, remove, or reclaim the address blocks but temporary locked registration for them.<ref>[https://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/ripe-ncc-to-seek-clarification-from-dutch-court-on-police-order-to-temporarily-lock-registration RIPE NCC Intends to Seek Clarification from Dutch Court on Police Order to Temporarily Lock Registration], RIPE.net. Published 18 November 2011.</ref> In January 2012, the locks were removed under RIPE's opinion that legal grounding to execute the order was insufficient.<ref>[https://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/ripe-ncc-unlocks-registration-in-ripe-registry RIPE NCC Unlocks Registration in RIPE Registry], RIPE.net. Published 10 January 2012. | ||
On September 14, 2012, RIPE NCC distributed the last blocks of [[IPv4]] address space that it had available. As a result RIPE is now distributing IPv4 address space to Local Internet Registries (LIRs) from the last /8 according to section 5.6 of "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”.<ref>[http://www.circleid.com/posts/20120914_ripe_ncc_distributed_last_ipv4_address_space_from_available_pool/ Ripe NCC Distributed Last IPv4 Address Space From Available Pool, CircleID.com]</ref> | On September 14, 2012, RIPE NCC distributed the last blocks of [[IPv4]] address space that it had available. As a result RIPE is now distributing IPv4 address space to Local Internet Registries (LIRs) from the last /8 according to section 5.6 of "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”.<ref>[http://www.circleid.com/posts/20120914_ripe_ncc_distributed_last_ipv4_address_space_from_available_pool/ Ripe NCC Distributed Last IPv4 Address Space From Available Pool, CircleID.com]</ref> |