[bind10-dev] Planning for next sprint - input required

[JINMEI Tatuya / 神明達哉]

At Thu, 25 Nov 2010 18:25:41 +0000,
Stephen Morris <stephen at isc.org> wrote:

> General/Common

> Logging Framework
[snip] 
> Notes: this was raised at the last face to face.  BIND-10 needs a
> comprehensive logging framework.  The longer we put this off, the
> more code we will have to re-factor to include include it.  It
> therefore makes sense to do this early and to start adding it to
> code as we write it.

I agree, and in case you were not aware of it there's already a python
version of logging framework for BIND 10 (src/lib/python/isc/log/).

For C++, there's a proposal of logging framework for boost
(http://boost-log.sourceforge.net/), but it doesn't seem to be merged
to the official boost libraries.  It also requires compiled library of
boost (according to the documentation), so it's probably not suitable
for us.  We could port BIND 9's logging framework, although this may
be one of the areas where we don't like to take an in-house approach.

Another thing: We'll also need a common wrapper layer to crypto
library for
- TSIG
- in CPU signing
- DNSSEC validation

> Authoritative Server
> ====================

> DNSSEC
> * Zone signing
> * Signing mechanisms
> * Key management

These seem to be quite advanced for me.  I'm not even sure if these
can be in year two goals.

> * Handling DO=1 queries
>   - Returning signature information
>   - Returning NSEC/NSEC3 information
> 
> Notes: The basic DNSSEC operations and we should not underestimate
> the complexity of the task.

This feature is at least functional for the sqlite3 data source.  Of
course we need to do it for the in memory data source (which should be
in year 2 goals) and eventually unify the interface so that we can do
this in a polymorphic way.

---
JINMEI, Tatuya