[bind10-dev] ddns update

[Jelte Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Okay, so the DDNS discussion mostly veered off into discussions about
optional receptionists and where to do acl checks, but there was also
some nice other feedback.

So here's a proposed set of tickets I can create to get us started with
the development:

Most tickets will really be dependent on this first one, but I'd like to
get some initial estimates on them anyway, and see if we can speed
things up a bit (and not have to wait another cycle)

- - write a design document. This is already a ticket:
http://bind10.isc.org/ticket/1447
- - do the user stories for non-RFC requirements (ideally we'd have these
already, and we do have sort of a list on the wiki, but we can at least
get started with the basic RFC support)
- - create a skeleton module (assuming that we do indeed go for the
separate process approach this can be done independently of the previous
two, but the rest will most probably depend on this)

- - Either come up with a framework approach or add UDP passing to the
current socket share code
- - add communication with Auth (depends on the previous one, I originally
said 'the same as for xfrout', that still goes, but i'll add
'independent of whether we change how communication with xfrout works ;)))

- - add prerequisite checks
  o for several cases as dictated by the rfc

- - add changes-to-ixfr-out-compatible functionality
- - use that functionality to get from DDNS update to a changeset

- - add consistency checking (not sure how deep this must initially be)

And, probably resonably independent:
- - define tests (similar to xfrinsystemtests document)
- - write tests

Did I miss anything? I plan to create tickets for this tomorrow

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7Xu1wACgkQ4nZCKsdOncU/nwCg1nwhRoDVrs/hdq0HtQdRBXJU
/voAn1SQiQ0MkDj51MwCCN13Sd32NFim
=XDcA
-----END PGP SIGNATURE-----