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