New IPv4 block allocated to RIPE NCC
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [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 iEYEARECAAYFAk1Pu9kACgkQXOgsmPkFrjM9FgCgsaT8cFxK0YKTFUFzj41L0PQT N1AAoIgmL1zUY8JjkCSa05xt0t8oppgP =woX5 -----END PGP SIGNATURE-----
Hi All, so _minimum_ or _maximum_? 07.02.11 11:31, Andrea Cima написав(ла):
The minimum allocation size for this /8 has been set at /22.
-- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)
http://www.ripe.net/ripe/docs/ripe-509.html#----use-of-last----for-pa-alloca... 5.6 Use of last /8 for PA Allocations <snip> • Allocations for LIRs from the last /8 On application for IPv4 resources LIRs will receive IPv4 addresses according to the following: a. LIRs may only receive one allocation from this /8. The size of the allocation made under this policy will be exactly one /22. b. LIRs receive only one /22, even if their needs justify a larger allocation. <snip> So neither minimum or maximum I guess. But exactly a /22. Nurani On 7 feb 2011, at 12.38, Max Tulyev wrote:
Hi All,
so _minimum_ or _maximum_?
07.02.11 11:31, Andrea Cima написав(ла):
The minimum allocation size for this /8 has been set at /22.
-- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)
Question. When you refer to the last /8: Do you refer to the last /8 given to RIPE NCC by IANA? or The last /8 stock of addresses in RIPE (generated may be by fragments from several other /8s)? Thanks, .as On 7 Feb 2011, at 10:43, Nurani Nimpuno wrote:
http://www.ripe.net/ripe/docs/ripe-509.html#----use-of-last----for-pa-alloca...
5.6 Use of last /8 for PA Allocations <snip> • Allocations for LIRs from the last /8
On application for IPv4 resources LIRs will receive IPv4 addresses according to the following:
a. LIRs may only receive one allocation from this /8. The size of the allocation made under this policy will be exactly one /22.
b. LIRs receive only one /22, even if their needs justify a larger allocation. <snip>
So neither minimum or maximum I guess. But exactly a /22.
Nurani
On 7 feb 2011, at 12.38, Max Tulyev wrote:
Hi All,
so _minimum_ or _maximum_?
07.02.11 11:31, Andrea Cima написав(ла):
The minimum allocation size for this /8 has been set at /22.
-- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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
- -- Tim Wilde, Senior Software Engineer, Team Cymru, Inc. twilde@cymru.com | +1-630-230-5433 | http://www.team-cymru.org/ -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk1ZYaYACgkQluRbRini9tjvSwCbBfInbsBCpZFMSri0RpL6izHC gP0An0PLvq25ywtb6YTsaagGN9qj5Xwo =vTk+ -----END PGP SIGNATURE-----
-----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-late... 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:
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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2/15/2011 7:38 AM, Andrea Cima wrote:
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-late...
Andrea, Thank you for this pointer, this is indeed an interesting and helpful file. However, I note that it has the same problem as the traditional delegated prefixes file, ie, it lists the "debogon" prefixes listed in your announcement (185.0.0.0/16, 185.1.0.0/21, and 185.1.24.0/24) as available as part of an "available" listing for all of 185.0.0.0/10: ripencc||ipv4|185.0.0.0|4194304||available If we were to use this file, we would have the same problem that we have using the traditional delegated list; we would list your "debogon" prefixes as bogon, because, according to your records, they are available, ie unallocated/unassigned, ie bogon. Do you see the problem we're running into? From my perspective, the "debogon" prefixes should be considered allocated - it's an internal allocation, and a temporary one, but it's still an allocation. This is, in fact, how 185.0.0.0/17 is listed in the RIPE WHOIS database: % Information related to '185.0.0.0 - 185.1.255.255' inetnum: 185.0.0.0 - 185.1.255.255 netname: EU-ZZ-20100510 org: ORG-NCC1-RIPE descr: RIPE NCC Test Announce country: EU admin-c: HU266-RIPE tech-c: RISM-RIPE status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-by: RIPE-NCC-RIS-MNT source: RIPE # Filtered But this is not reflected in the delegated-latest file. Should it not be there (and in this new experimental file) as an allocation, since that's what WHOIS says it is? Best regards, Tim Wilde - -- Tim Wilde, Senior Software Engineer, Team Cymru, Inc. twilde@cymru.com | +1-630-230-5433 | http://www.team-cymru.org/ -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk1ayH0ACgkQluRbRini9tg3KwCeNgN73SAWCcPaZvhgDq9Ak790 WXYAn0SgdxRNBPzDkMSNMGXpYlrfg/+W =pE2t -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Tim, Tim Wilde wrote: [...]
Andrea,
Thank you for this pointer, this is indeed an interesting and helpful file. However, I note that it has the same problem as the traditional delegated prefixes file, ie, it lists the "debogon" prefixes listed in your announcement (185.0.0.0/16, 185.1.0.0/21, and 185.1.24.0/24) as available as part of an "available" listing for all of 185.0.0.0/10:
ripencc||ipv4|185.0.0.0|4194304||available
If we were to use this file, we would have the same problem that we have using the traditional delegated list; we would list your "debogon" prefixes as bogon, because, according to your records, they are available, ie unallocated/unassigned, ie bogon. Do you see the problem we're running into? From my perspective, the "debogon" prefixes should be considered allocated - it's an internal allocation, and a temporary one, but it's still an allocation. This is, in fact, how 185.0.0.0/17 is listed in the RIPE WHOIS database:
% Information related to '185.0.0.0 - 185.1.255.255'
inetnum: 185.0.0.0 - 185.1.255.255 netname: EU-ZZ-20100510 org: ORG-NCC1-RIPE descr: RIPE NCC Test Announce country: EU admin-c: HU266-RIPE tech-c: RISM-RIPE status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-by: RIPE-NCC-RIS-MNT source: RIPE # Filtered
But this is not reflected in the delegated-latest file. Should it not be there (and in this new experimental file) as an allocation, since that's what WHOIS says it is?
Historically these pilot prefixes have never been listed in the delegated-latest file. However I agree with you that they should. We will add these temporary allocations to the delegated-latest file in the coming days. Best regards, Andrea Cima RIPE NCC
Best regards, Tim Wilde
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk1b93gACgkQXOgsmPkFrjMPwwCgiqYrdIhlGWvk87v7LH+MXHVS 4pkAoJJUbYrHpEKBbuQ5TIx/gnLYndiu =iJ0m -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2/16/2011 11:12 AM, Andrea Cima wrote:
Historically these pilot prefixes have never been listed in the delegated-latest file. However I agree with you that they should. We will add these temporary allocations to the delegated-latest file in the coming days.
Andrea, Great, thanks, I'm glad to hear it! Best regards, Tim Wilde - -- Tim Wilde, Senior Software Engineer, Team Cymru, Inc. twilde@cymru.com | +1-630-230-5433 | http://www.team-cymru.org/ -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk1cG8UACgkQluRbRini9ti06wCcCTrkV4AxO6NwaYRFdCRVT/Ib 7sQAn3Tv5KgPEFXmJbfG45Hy32pArqJB =Xxqi -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2/16/2011 10:12 AM, Andrea Cima wrote:
Historically these pilot prefixes have never been listed in the delegated-latest file. However I agree with you that they should. We will add these temporary allocations to the delegated-latest file in the coming days.
Greetings Andrea, Do you have any idea of a timeline for these blocks to be added to the delegated-latest file? I just checked the most recent file and still do not see any allocations within 185/8, including the debogon tests. Thanks, Tim Wilde - -- Tim Wilde, Senior Software Engineer, Team Cymru, Inc. twilde@cymru.com | +1-630-230-5433 | http://www.team-cymru.org/ -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk1n7FAACgkQluRbRini9tij6QCfSd1h8RgE3CaL69AsncQhooBG T5UAn1LjaVjtoqeQcIDNhWM+X+sdTVey =gWSx -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Tim, Tim Wilde wrote:
On 2/16/2011 10:12 AM, Andrea Cima wrote:
Historically these pilot prefixes have never been listed in the delegated-latest file. However I agree with you that they should. We will add these temporary allocations to the delegated-latest file in the coming days.
Greetings Andrea,
Do you have any idea of a timeline for these blocks to be added to the delegated-latest file? I just checked the most recent file and still do not see any allocations within 185/8, including the debogon tests.
The prefixes are now included in the delegated-latest file. If you have any further questions please let me know. Best regards, Andrea Cima RIPE NCC
Thanks, Tim Wilde
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk1tD+kACgkQXOgsmPkFrjO2FQCdEmt+hJ+xW2CxFKZBYf/8ywBo q0MAoL8yPD9+zFVP8IuOD7dCjEeW8S4/ =/4G9 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 3/1/2011 10:25 AM, Andrea Cima wrote:
The prefixes are now included in the delegated-latest file.
Great, thank you very much! Best regards, Tim Wilde - -- Tim Wilde, Senior Software Engineer, Team Cymru, Inc. twilde@cymru.com | +1-630-230-5433 | http://www.team-cymru.org/ -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk1tHboACgkQluRbRini9tgmRgCdEnLTfv8WruJnQ3f/aT0JiLMt /6QAnjeySS8WpCW5ycEScLwmZUlcFH7B =73dt -----END PGP SIGNATURE-----
participants (5)
-
Andrea Cima -
Arturo Servin -
Max Tulyev -
Nurani Nimpuno -
Tim Wilde