Dear James,

I believe this direction of policy to be harmful to the ecosystem. This is not what ASPA was designed for, and creation of such ASPAs does not protect member resources.

Members can create an ASPA after receiving the resource, if they’d like. The RIR should not be creating signed objects for unassigned resources. It’s where dragons be.

Kind regards,

Job

On 23 Jul 2026, at 10:20, James Bensley <james@inter.link> wrote:


Hi WG,

AFAIK there is an existing policy/process that the RIPE NCC will create ROA AS0 records for prefixes not currently allocated to any LIR. This prevents unused IP space from being originated into the DFZ.

Is there a similar policy or process that ensures RIPE will create ASPA AS0 records for ASNs not currently allocated (again, to ensure they aren't used)?

If I look at an example ASN allocated to RIPE by IANA, but not currently allocated by RIPE to any LIR (AS219350), there is no ASPA AS0 record for this ASN.

If no such policy or process exists, what is the correct path to establish such a policy/process?

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 | Web: inter.link
-----
To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/