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.
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.
APNIC is testing a new protocol that allows service operators to easily notify of DNS changes.
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.