[bind10-dev] Resolver Address Database - Requirements and Design

[Shane Kerr]

Stephen,

Late to the discussion. Hopefully I didn't miss these points already
discussed...

On Tue, 2010-10-05 at 23:51 +0100, Stephen Morris wrote:
> The fact of their existence was buried a bit in my last email, but the
> updated requirements for the resolver's address database (now renamed
> the nameserver address store) can be found at
> http://bind10.isc.org/wiki/NameserverAddressStoreRequirements 

Does it make sense to add a requirement to allow the database to be
serialized in some way? This will allow us to store it to disk between
boots, and migrate it between machines.

This has certain design implications, depending on how it is done.

I suppose this may be feature bloat though, and perhaps added to a
wishlist.

> and a draft design at
> http://bind10.isc.org/wiki/NameserverAddressStoreDesign.

I noticed the statement that we use a random RTT initially. I think that
makes sense, but perhaps we should go ahead and specify that we use a
pseudo-random RTT.

Pseudo-random is preferred to true random because we don't have to find
a source of entropy, and we can use a high-speed generator. Also, it
allows us to explicitly state that we have thought about security
implications and do not think there are any. (There are not any, right?)

Anyway, looks good!

--
Shane