Hi all, I tried to look through the list archives but the reason this was rejected last time was not clear to me. I think most people can easily guess an argument for doing this; we see people either squatting on unallocated IP/ASN space intentionally (spammers basically), or accidentally (I meant to prepend my AS, 555555 10 times but instead I just rewrote my origin to 10555555, and this "works" so it goes unnoticed and unfixed). Also AS0 ROAs are exactly for the purpose of signalling which IP space should not be announced, this is exactly that case with unallocated space. Similarly, AS0 ASPAs tell me I should be rejecting paths with AS0 in that my peer is sending me, again, this is exactly that case. I think the argument for not doing this (if I understood the list archives correctly, please correct me if I'm wrong!), is concern for overreach from the RIPE NCC? If that understanding is correct, I'm not seeing it and need someone to spell it out for me please. For example, I'm pretty confident the RIPE NCC could create an AS0 ROA or ASPA for an prefix/ASN allocated to them by IANA right now. It's technically not that difficult. They have the means to do it. It's just maybe a manual process right now. So this wouldn't be given the RIPE NCC any technical capabilities they don't already have. We're also only talking about them doing it for unallocated space, which I see RIPE NCC as having a responsibility for because that space is theirs until it's allocated to an LIR or taken back by IANA or transferred away. So not doing this for unallocated space is perhaps a little bit irresponsible of the RIPE NCC? (I'm not blaming the RIPE NCC because it was the membership that pushed back on this). Please can someone spell it out for me what the reason(s) for not doing this is, which outweigh the reason(s) for doing it? With kind regards, James Bensley (he/him) [CompanySignature] Inter..link GmbH | Boxhagener Straße 80, 10245 Berlin, Germany | Managing Directors: Marc Korthaus, Theo Voss | Commercial Register: Amtsgericht Charlottenburg, HRB 138876 | VAT ID: DE281288887 | Email: hello@inter.link<mailto:hello@inter.link> | Web: inter.link<https://inter.link>