Your most pressing questions about ASPA, answered
Answering some of the most frequently asked questions about ASPA.
Answering some of the most frequently asked questions about ASPA.
With support now available in MyAPNIC and the Registry API, APNIC Members can publish ASPAs to help detect route leaks and strengthen the integrity of Internet routing.
MyAPNIC now supports RPKI Signed Checklists (RSCs), providing Members with a new way to cryptographically sign and verify documents using their RPKI resources. Your feedback is welcome.
New support for key transitions will give RIRs greater flexibility and improve long-term resilience of the RPKI.
The new APNIC registry API supports the retrieval of delegation information, as well as the management of whois records, RDNS records, ROAs, and route objects.
A new type of RPKI signed object that permits a resource holder to sign arbitrary files or documents with a set of Internet Number Resources.
MyAPNIC users will soon receive warnings if they attempt to submit route management changes that would cause any of their current BGP announcements to be considered ‘RPKI-invalid’.
The APNIC Registry API will, among other things, automate repetitive processes in MyAPNIC and integrate with IPAM products.
Historical delegation and transfer information from the Korea Network Information Center (KRNIC) has now been incorporated into APNIC’s address registry.
APNIC is working on a collaborative project to develop a full-featured RDAP search facility using POSIX Extended Regular Expressions to query registry data.