A friend of mine buzzed me yesterday about his missing route objects. Later multiple other ISPs told the same story which triggered me to put this as a question on INNOG Mailing list. Many folks replied of missing route objects there and it seems to be limited to IRINN members only. I also asked the same question on APNIC mailing list and it was again confirmed about the issue. Before I proceed further, here’s what it is all about.
While I am spending time on APNIC’s security workshop here at APNIC 46, I got curious about DNSSEC deployment across ccTLDs. For those who may be unaware, DNSSEC adds signature the DNS responses making it possible to cryptographically verify a DNS query response. Out of 254 ccTLDs, 125 support DNSSEC with a published DS record (at least that is what I get when I check their zone) and 129 do not support it as yet.
Often this comes into the subnetting discussion by my friends who are deploying IPv6 for the first time. How do you calculate subnets outside the 4-bit nibble boundary? This also happens to be one of starting points of APNIC IPv6 routing workshop where I occasionally instruct as community trainer. So what is a Nibble boundary? In IPv6 context, it refers to 4 bit and any change in multiple of 4 bits is easy to calculate.
APNIC and RIPE NCC are doing a hackathon at APRICOT 2018. It just started today with some light interaction with various participating members yesterday. The theme of the hackathon is around IPv6. Many cool projects were suggested yesterday and teams started working today on certain shortlisted projects like: A tool for ranking CDNs - A tool based on RIPE Atlas data to rank CDNs based on latency across different regions.
Talking about root DNS server’s anycast at APNIC42. YouTube here.