How RFC 9691 improves key rollover in RPKI Trust Anchors
New support for key transitions will give RIRs greater flexibility and improve long-term resilience of the RPKI.
APNIC registry API now available
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.
The benefits of RPKI Signed Checklists
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.
Route management prevalidation
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’.
APNIC Registry API
The APNIC Registry API will, among other things, automate repetitive processes in MyAPNIC and integrate with IPAM products.
APNIC-NIR Data Reconciliation
Historical delegation and transfer information from the Korea Network Information Center (KRNIC) has now been incorporated into APNIC’s address registry.
RDAP: Search using POSIX Regular Expressions
APNIC is working on a collaborative project to develop a full-featured RDAP search facility using POSIX Extended Regular Expressions to query registry data.
Transitioning to a single trust anchor
APNIC is transitioning from the current set of five Resource Public Key Infrastructure (RPKI) trust anchors to a single “all resources” trust anchor in an effort to streamline the RPKI process.
Third Party DNS Operator to Registrars / Registries Protocol
APNIC is testing a new protocol that allows service operators to easily notify of DNS changes.
Working with the draft RPSL signature specification
APNIC and RIPE NCC have collaborated to test prototype signer/validator implementations of a specification, which allows clients to verify that certified resource holders have authorized the creation of an RPSL object.