The peer-to-peer (P2P) Icarus (Integrated Computer Application for Recognizing User Services) developed and used at the University of Florida can identify Kazaa traffic by isolating nodes involved and beginning campus judicial proceedings based on university policy. Icarus has been in use since fall 2003. The university has been able to recover 85 percent of the dormitory network's scarce bandwidth. The amount of work for IT and frustration among serious student users that has been eliminated is astounding. Students can do their work without dealing with incredibly slow network performance caused by P2P bandwidth gluttony, and university judicial officers who once spent way too much time scheduling and handling hearings on computer use policy violations can work on more pressing matters. Residence hall network and system administrators have more time to deploy system enhancements because they do not have to be so busy trying to track down P2P hogs. P2P operates out side the DNS system. Its nodes must have 'significant or total autonomy from central servers.' At UF, 9,000 connected nodes run at 100Mbps and are overseen by three IT staff, all of whom know how to use Perl, a flexible language used for parsing data gathered for Icarus and scripting actions to be taken when a policy is disobeyed. The MySQL database is at the core of the Icarus framework and handles about 25GB of data, which is 5 days' worth of entries, and the data can be analyzed at any time. To deal with ES5 (Earthstation 5), the IT team has uncovered an ES5 signature that takes place over time and allows them to identify ES5 traffic and to quarantine machines that run the software.