From noreply at ripe.net  Tue Jan 19 16:58:09 2010
From: noreply at ripe.net (Paul Rendek)
Date: Tue, 19 Jan 2010 16:58:09 +0100
Subject: [ncc-announce] IANA IPv4 Address Pool Dips Below 10%
Message-ID: <82511D9A-AF61-4EBB-AE31-A1B0E2A03889@ripe.net>

[Apologies for duplicates]

Dear Colleagues,

With the distribution of two /8 blocks to APNIC, the Number Resource  
Organization (NRO) today announced that less than ten percent of  
available IPv4 addresses remain unallocated.

?This is a key milestone in the growth and development of the global  
Internet,? noted Axel Pawlik, Chairman of the NRO. ?With less than ten  
percent of the entire IPv4 address range still available for  
allocation to RIRs, it is vital that the Internet community take  
considered and determined action to ensure the global adoption of  
IPv6. The limited IPv4 addresses will not allow us enough resources to  
achieve the ambitions we all hold for global Internet access. The  
deployment of IPv6 is a key infrastructure development that will  
enable the network to support the billions of people and devices that  
will connect in the coming years.?

You can view the NRO press release in its entirety at:
http://www.nro.net/media/less-than-10-percent-ipv4-addresses-remain-unallocated.html

Please contact <ncc at ripe.net> if you have any questions or comments.

Regards,

Paul Rendek
Head of External Relations and Communications
RIPE NCC


From xavier at ripe.net  Thu Jan 21 12:14:26 2010
From: xavier at ripe.net (Xavier Le Bris)
Date: Thu, 21 Jan 2010 12:14:26 +0100
Subject: [ncc-announce] 2009-03  "Run-out fairly"  implemented
Message-ID: <4B583712.4020109@ripe.net>

[Apologies for duplicate e-mails.]


Dear Colleagues,

We are pleased to announce that the policy described in proposal
2009-03,"Run Out Fairly", has been implemented. Requests for IPv4
address space received on or after Friday, 22 January will be evaluated
by the RIPE NCC Registration Services Department under the new policy.

Full text of the policy proposal can be found at:
http://ripe.net/ripe/policies/proposals/2009-03.html

The following RIPE documents have been updated to reflect this policy
implementation:

http://www.ripe.net/ripe/docs/ripe-488.html
http://www.ripe.net/ripe/docs/ripe-489.html
http://www.ripe.net/ripe/docs/ripe-490.html
http://www.ripe.net/ripe/docs/ripe-491.html


Regards,

Xavier Le Bris
Registration Services



From sjoerdoo at ripe.net  Fri Jan 22 17:50:58 2010
From: sjoerdoo at ripe.net (Sjoerd Oostdijck)
Date: Fri, 22 Jan 2010 17:50:58 +0100
Subject: [ncc-announce] Reverse DNS Outage Announcement
Message-ID: <4B59D772.4060002@ripe.net>

[Apologies for duplicates]

Dear Colleagues,

At 13:50 on Thursday, 21 January, an error was introduced into the RIPE
NCC's reverse DNS provisioning system. This caused reverse DNS
delegations to stop working for allocations in the following range:
77.0.0.0 to 77.220.7.255

This error was triggered by an internal cleanup of our Early
Registration Transfer (ERX) DNS delegations, which was being conducted
as part of the RIPE NCC's Registration Data Quality (RDQ) project.

The reverse DNS provisioning system was corrected again on 22 January at
09:50 (UTC). However, due to negative caching in DNS resolvers, the
problem may have remained visible for a further two hours.

The RIPE NCC is currently revising the reverse DNS provisioning system
to prevent errors such as this occurring in future. If you have any
questions or comments, please send an email to <ncc at ripe.net>.


Regards,

Sjoerd Oostdijck
DNS Services Group, RIPE NCC