[routing-wg] Re: New IPv4 block allocated to RIPE NCC
- Previous message (by thread): [routing-wg] Re: New IPv4 block allocated to RIPE NCC
- Next message (by thread): [routing-wg] Re: New IPv4 block allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrea Cima
andrea at ripe.net
Tue Feb 15 13:38:56 CET 2011
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Tim, The file you mention contains all IP ranges allocated and assigned by the RIPE NCC. IP ranges from the new /8(s) will only appear in this list once the RIPE NCC starts using it for allocations (and, if applicable, for assignments). A complete list of allocated and available resources, including the new /8(s) are listed here: http://labs.ripe.net/Members/mirjam/new-ripe-ncc-address-statistics-reports and specifically in: http://albatross.ripe.net/delegated-extended/delegated-ripencc-extended-latest.bz2 I hope this helps. Best regards, Andrea Cima RIPE NCC Tim Wilde wrote: > Greetings Andrea & Team, > > Are there any plans for these allocations to show up in the > authoritative delegated-ripencc-latest file at > ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest ? We use > this file as the basis for our fullbogon efforts, which list all blocks > that have not yet been allocated by RIRs, and as best as I can tell, > these debogon blocks do not exist there, even though they are in the > RIPE WHOIS. It would be ideal if this type of allocation could be > included in the delegated file as well so we do not have to manually > maintain exceptions, and so that users of our fullbogons feed can > properly hit your debogon addresses. > > Best regards, > Tim Wilde > > On 2/7/2011 4:31 AM, Andrea Cima wrote: >> [Apologies for duplicate mails] > >> Dear Colleagues, > >> The RIPE NCC has received the IPv4 address range 185/8 from the IANA. > >> This is the final allocation of IPv4 address space that the RIPE NCC >> will receive from the IANA as stated in ripe-436, "Global Policy for the >> Allocation of the Remaining IPv4 Address Space". > >> The minimum allocation size for this /8 has been set at /22. > >> You may wish to adjust any filters you have in place accordingly. > >> More information on the IP address space administered by the RIPE NCC >> can be found on our website at: > >> https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html > >> Additionally, please note that three "pilot" prefixes will be announced >> from this /8. The prefixes are: > >> 185.0.0.0/16 >> 185.1.0.0/21 >> 185.1.24.0/24 > >> They all originate in AS12654. > >> The pingable addresses will be: > >> 185.0.0.1 >> 185.1.0.1 >> 185.1.24.1 > >> More information on this activity is available in the document >> "De-Bogonising New Address Blocks", which can be found at: > >> http://www.ripe.net/ripe/docs/ripe-351.html > > >> Kind regards, > >> Andrea Cima >> Registration Services Manager >> RIPE NCC > > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk1ac+AACgkQXOgsmPkFrjOH/ACdHXnEyaGljIchFgSETyzL0Zwl bSMAoJYi0IV+UhPCvcu4rtpQB2jc4SbE =qLdL -----END PGP SIGNATURE-----
- Previous message (by thread): [routing-wg] Re: New IPv4 block allocated to RIPE NCC
- Next message (by thread): [routing-wg] Re: New IPv4 block allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]