wiki:Jan2010RemainingTasks

msgq [h]

  1. review [h]
  2. spec update (theory, picture) [m]
  3. API docs (with examples) [m]
  4. stress test, inter-os tests [l]
  5. API 1.1 [y2]
    1. timeouts
    2. domain sockets
  6. benchmarks [l]

configuration [h]

  1. review finished classes [h]
  2. API 1.1 [l]
    1. scaling (don't send entire config at once)
  3. python (client) API [h]
  4. implementer doc [m]
  5. docs in svn [m]

release topics [h]

  1. "make install" should work [h]
  2. users guide (what the ARM was supposed to be) [h]
  3. release notes [h]
  4. dates for changes [h]
  5. outreach

logging [l]

  1. Use log4* [m]
  2. configuration programatically rather than external file [m]
  3. does this support the isc_log_wouldlog() functionality? [h]
  4. generic configuration? [h]
  5. what is logged? [h]
    1. function entry/exit? Probably not
    2. other things?
  6. standards [h]
    1. unique message id
    2. format
    3. query processing path (aka trace)

BoB [h]

  1. TODO list [m]
  2. Documentation (man, theory) [h, l]
  3. tests [h]
  4. review [h]
  5. upon startup, if a module fails stop it all? (Jelte request)
    1. probably a case-by-case basis
    2. at least SCREAM LOUDLY about it

statistics [h]

  1. API for query/report stats and capabilities [h]
    1. capability == type of statistic (schema?)
  2. finish SNMP daemon [l]
  3. bindctl stats [h]
  4. write any other daemon (restful XML?) [m]
    1. finer-grained access to data
    2. may not be 100% compatible with bind 9 (probably cannot be)
    3. use feedback on what users asked for to make bind 10 better
    4. share command/control restful config?
  5. review/doc which statistics [h]

bindctl [h]

  1. bindctld [h]
  2. review [h]

TSIG [h]

  1. implement in new server stuffs [h]

ACL [l]

  1. radix tree impl
  2. language is more important than implementation for yr 1 (language?)
  3. tsig list
  4. localhost, localnet
  5. programatically
  6. types of ACLs: Other ACLs, keys, "specials" like localnet, addresses
  7. configuraton syntax [h]

data source [h]

  1. API [h]
  2. API docs [m]
  3. concrete implementation [h]
  4. per-implementation docs [h]
  5. dnssec [h]
  6. tests [h]
  7. performance [m]
  8. ddns [y2]

dns message api [h]

  1. rrset API and dns message API [h]
  2. more rrtypes [h]
  3. truncation [h]
  4. benchmarks [m]
  5. testing [h]
  6. review [h]
  7. documentation [m]
  8. TSIG [h]
  9. EDNS0 for incoming queries [h]

AXFR, IXFR, and NOTIFY [h]

  1. XFR in [h]
  2. XFR out (forked as needed) [m]
    1. May have to tunnel from auth daemon
    2. maybe just put it inside the auth daemon (jelte's suggestion)
  3. tests [h]
  4. configuration [h]
  5. documentation user/dev [h, m]
  6. benchmarks [m]

python wrapper around dns message API [h]

  1. Check out to see if Francis' stuff is good [h]

auth server itself [h]

  1. testing [h]
  2. performance [m]
  3. configuration [m]

query logic [h]

  1. auth query logic [h]
  2. recursive logic [y2]

zone file loader [h]

  1. application (daemon?) [h]
  2. man page [h]
  3. bind 9 extensions ($GENERATE, etc) [m]

year 2

  1. customer support tools

ACTIONS

  1. All daemons/servers should be prefixed with b10XXX

Year 1 OS support

  1. CentOS / Redhat
  2. Ubuntu
  3. Solaris 10 sparc
  4. FreeBSD
Last modified 8 years ago Last modified on Jan 26, 2010, 7:29:26 PM