Introduction & background

  I'll introduce myself, too.

  My background is originally embedded 8-bit OS's.  From there, I
moved to ISDN, security systems, and network protocol analysis.  My
day job is working for a company producing multi-gigabit
classification hardware & software.  We have a high-level packet
description language, and can handle large numbers of rules over
pretty much any combination of protocols & fields.  As part of that
job, I'm heavily involved in network analysis, protocol design, and
protocol implementation.

  I got involved in ASRG because of:

	http://www.striker.ottawa.on.ca/

  Someone has to be on the tail end of the bell curve for receiving
spam, and that's me.  The test I've done show that I'm receiving ~2x
the spam messages that Nortel is receiving.  Per capita, I'm receiving
probably 1000x the spam of AOL.  My system bas been receiving more
than 99% spam for 3 years, with another '9' being added every year.

  The worst part of it, (from my perspective) is that either no one
believes me, or they believe that such loads will never happen to them
(classic head in the sand approach).  My involvement in ASRG is
because I'd ideally like to come up with a solution to the spam
problem.  Barring that, I'd like to be able to convince a wider
audience that it's a problem which desperately needs to be addressed,
and that the status quo just won't cut it any more.

  I volunteered to coordinate this effort because I haven't been an
author of any draft, and because I think that the general concept
behind DNS-based anti-spam efforts is a good one.  I'd like to see
DNS-based defenses become one piece of the anti-spam puzzle.

  Alan DeKok.