[tenta]

We natively work a BGP, making it easy and practical to do things like "anycast" (announcing the same IP address from multiple datacenters), or using BGP for load balancing or failover. Looking at large and successful DNS providers (Google, Amazon, Dyn, Neustar, etc), all are running BGP as part of their DNS offering. We've combined it into one piece of software.

[tptacek]

This is a much more interesting feature than DNSSEC and is what you should lead with.

[scurvy]

Why not leave that responsibility to something else like bird, quagga, etc? Those have been doing the job just fine for years.

A lot of this sounds like rewriting the wheel in Go because Go is "hip".

Do one thing, and do it well.

[tenta]

Well, we didn't rewrite BGP in go, we used the excellent OSRG library for that. We played with several of the open source BGP libraries, but these inevitably result in a giant mess of configs and scripts holding things together, and furthermore, it's hard to signal network condition back and forth between the different parts of the process. One of the great powers of go lies in the ability to pull in fully functional components via the package manager. Rather than having to provide a long list of other dependencies to install along with Tenta DNS, we simply provide a single binary that has all the parts rolled in.