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/[email protected]/
[address-policy-wg] aggregating unused allocations
- Previous message (by thread): [address-policy-wg] 2014-12 Proposal Accepted (Allow IPv6 Transfers)
- Next message (by thread): [address-policy-wg] aggregating unused allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Antonis Lioumis
alioumis at noc.grnet.gr
Thu Mar 19 09:54:29 CET 2015
Hello Recently my company got a /22 allocation through the well known transfer procedure between LIR's. In the past we also got the /22 we qualify from RIPE NCC's last /8. This /22 was put aside for future use. For aggregation purposes we asked RIPE NCC to return both /22 and get back a /21 but according to current policies this is forbidden. Since global routing table has exceeded 500000 prefixes and expected to grow more maybe RIPE community should rethink permitting the exchange of smaller IPv4 blocks with contiguous one. Regards Antonis Lioumis
- Previous message (by thread): [address-policy-wg] 2014-12 Proposal Accepted (Allow IPv6 Transfers)
- Next message (by thread): [address-policy-wg] aggregating unused allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]