This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] 2019-07 New Policy Proposal (Default assignment size for IXPs)
- Previous message (by thread): [address-policy-wg] 2019-07 New Policy Proposal (Default assignment size for IXPs)
- Next message (by thread): [address-policy-wg] 2019-07 New Policy Proposal (Default assignment size for IXPs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Fri Oct 25 08:30:21 CEST 2019
* Arash Naderpour > Do we know how many /29 we have available in the IXP reserved pool? if there are only few ones, it doesn't make scene to me set the default to /29 as it would be a good practice for just few allocations. > > Can someone from RIPE NCC provide us with an statistic on number of different prefixes in the IXP pool? Hi Arash, While I'm not from the NCC, below is the complete list of blocks smaller than /24 currently found in the IXP pool (or could be in quarantine, but destined for the IXP pool nevertheless). I spot at least four /29s in it (193.58.0.48/29, 193.188.134.136/29, 193.188.134.200/29, 194.180.226.144/29). An additional 13 /29s are currently assigned; if returned, these will also be added to the IXP pool under current policy. Tore $ curl -s ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-extended-latest | awk '-F|' '$3 == "ipv4" && $5 < 256 && $7 == "reserved"' ripencc||ipv4|193.34.193.128|128||reserved ripencc||ipv4|193.34.196.128|128||reserved ripencc||ipv4|193.34.199.128|128||reserved ripencc||ipv4|193.34.201.128|128||reserved ripencc||ipv4|193.58.0.48|8||reserved ripencc||ipv4|193.164.232.96|64||reserved ripencc||ipv4|193.164.232.224|32||reserved ripencc||ipv4|193.188.134.136|8||reserved ripencc||ipv4|193.188.134.200|56||reserved ripencc||ipv4|193.192.12.0|128||reserved ripencc||ipv4|193.201.145.128|128||reserved ripencc||ipv4|193.201.147.192|32||reserved ripencc||ipv4|193.201.148.128|64||reserved ripencc||ipv4|193.201.149.0|64||reserved ripencc||ipv4|193.201.149.128|64||reserved ripencc||ipv4|193.201.150.192|64||reserved ripencc||ipv4|193.201.151.64|128||reserved ripencc||ipv4|193.201.155.0|128||reserved ripencc||ipv4|193.201.157.128|128||reserved ripencc||ipv4|193.201.159.0|128||reserved ripencc||ipv4|193.218.207.64|16||reserved ripencc||ipv4|193.243.183.0|64||reserved ripencc||ipv4|193.243.183.128|64||reserved ripencc||ipv4|194.42.47.0|128||reserved ripencc||ipv4|194.93.123.0|128||reserved ripencc||ipv4|194.117.50.0|128||reserved ripencc||ipv4|194.117.55.0|128||reserved ripencc||ipv4|194.153.153.0|128||reserved ripencc||ipv4|194.153.157.0|128||reserved ripencc||ipv4|194.153.158.0|128||reserved ripencc||ipv4|194.153.159.128|128||reserved ripencc||ipv4|194.180.159.0|240||reserved ripencc||ipv4|194.180.226.0|152||reserved ripencc||ipv4|194.180.226.160|96||reserved ripencc||ipv4|194.246.39.0|96||reserved ripencc||ipv4|194.246.39.192|32||reserved ripencc||ipv4|195.13.37.128|128||reserved ripencc||ipv4|195.35.104.0|32||reserved ripencc||ipv4|195.60.80.0|96||reserved ripencc||ipv4|195.60.81.128|64||reserved ripencc||ipv4|195.60.83.32|32||reserved ripencc||ipv4|195.60.83.128|32||reserved ripencc||ipv4|195.60.84.128|128||reserved ripencc||ipv4|195.60.85.128|128||reserved ripencc||ipv4|195.60.88.0|128||reserved ripencc||ipv4|195.60.91.128|128||reserved ripencc||ipv4|195.60.92.192|64||reserved ripencc||ipv4|195.60.93.64|64||reserved ripencc||ipv4|195.60.94.128|128||reserved
- Previous message (by thread): [address-policy-wg] 2019-07 New Policy Proposal (Default assignment size for IXPs)
- Next message (by thread): [address-policy-wg] 2019-07 New Policy Proposal (Default assignment size for IXPs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]