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.
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.
The traffic on the public whois service at APNIC continues unabated, but there is a far simpler, better way to query the same information: RDAP.
APNIC has operated its own dual stack network for many years, but recently embarked on two additional IPv6 network projects. This is what we experienced.
Discussions around Coordinated Address Space Management (CASM) continued during IETF 99 and the RIRs are participating.
The APNIC whowas service provides visibility into prior states of APNIC resource registration records.
After sharing my notes from the IEPG meeting and aspects of the DNS, here are the rest of the items that I personally found to be of interest at IETF 99 last week.
Interest in the DNS appears to come in waves and we seem to be be in the midst of a furious burst of activity.
Automating DNSSEC key management and validating issues with the KSK roll where two of the many novel discussions had during the recent IEPG meeting in Prague.
Security of the Domain Name System, and privacy, was a topic of much discussion during the recent DNS operations Working Group.
Should there be a hard limit for the /64 boundary? A question hotly debated during the 6MAN working group at IETF 99.