1. Quagga TODO list
  2. 2004/11/24
  3. zebra:
  4. o Pointopoint address configuration.
  5. o Multiple (alias) address configuration for the interface when kernel
  6. support it [just starting].
  7. o improve rtnetlink to handle sequence number tracking and reconciliation
  8. and resyncs.
  9. o Add support for valid and preferred lifetimes to IPv6 addresses
  10. o proper support for (at least) 1-level recursive routes
  11. o Ability to set src on routes, where systems support it.
  12. o Ability to apply route-maps to daemon route updates.
  13. bgpd:
  14. o BGP TCP MD5 authentication by password command.
  15. o HUP signal support (reload configuration file).
  16. o BGP multi-path extension
  17. o move FSM state to be per-connection, not per-peer.
  18. ripd:
  19. o Multipath support.
  20. ospfd:
  21. o Rewrite the incremental RT update code.
  22. o Demand circuits.
  23. o Multiple instances.
  24. o OSPF MIB [SNMP get is amost finished].
  25. o HUP signal treatment.
  26. o Fragment Oversized LSAs
  27. o move SPF to common code
  28. o NSSA priority rules (RFC3101 2.4)
  29. o Type-7 address ranges (RFC3101 2.2)
  30. o Originating Type-7 default into area (RFC3101 2.7)
  31. ospf6d:
  32. o move SPF to common code
  33. o add router-id lookups
  34. lib:
  35. o improve route_table speed, eg strided lookups for common prefix depths.
  36. o improve hash tables, eg auto-growing hash tables
  37. o move performance sensitive users of hashes over to jhash
  38. o clean up linked lists
  39. o ipv6 addresses need concept of valid/preferred
  40. o implement a generic daemon access/control protocol (eg D-Bus like?
  41. simplified SNMP-a-like?)
  42. o merge SPF code from ospfd and ospf6d into a common libspf
  43. o depends-on(generic A/C protocol) move snmp to seperate daemon
  44. o extend command definitions to allow them to be self-documenting
  45. o i18n command help strings
  46. o Document the exported API (DocBook/Doxygen?)
  47. vtysh:
  48. o untangle readline specific bits
  49. o add a vtyd with a vty (ie telnet) frontend (as opposed to readline)
  50. o depends-on(generic A/C protocol) use such
  51. o better AAA support than just PAM, eg krb5, SASL, LDAP..
  52. -----------------------------