[src/trunk]: src/usr.sbin/npf/npfctl add another

[christos <christos%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/68a37ab78897
branches:  trunk
changeset: 785423:68a37ab78897
user:      christos <christos%NetBSD.org@localhost>
date:      Wed Mar 13 02:36:51 2013 +0000

description:
add another

diffstat:

 usr.sbin/npf/npfctl/todo |  3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diffs (13 lines):

diff -r a470244bb09d -r 68a37ab78897 usr.sbin/npf/npfctl/todo
--- a/usr.sbin/npf/npfctl/todo  Wed Mar 13 02:34:37 2013 +0000
+++ b/usr.sbin/npf/npfctl/todo  Wed Mar 13 02:36:51 2013 +0000
@@ -15,6 +15,9 @@
    for system failures is probably not good enough. For example if a module
    failed to autoload, it is probably an error and it should be reported
    differently?
+-- npf algorithms like icmp, are loaded via modules. Perhaps it is better
+   to have some config magic to autoload it instead of needing to run a
+   module command.
 
 ok npf and dependent modules should autoload automagically as they are used
 ok have a way to register cloners? through a mapping file? consistently naming