Operational Considerations Regarding Reputation Services
draft-kucherawy-repute-considerations-00

Document Type Replaced Internet-Draft (individual)
Author Murray Kucherawy 
Last updated 2012-11-12 (latest revision 2012-11-07)
Replaced by draft-ietf-repute-considerations
Stream (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-repute-considerations
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kucherawy-repute-considerations-00.txt

Abstract

The use of reputation systems is has become a common tool in many applications that seek to apply collected intelligence about traffic sources. Often this is done because it is common or even expected operator practice. It is therefore important to be aware of a number of considerations for both operators and consumers of the data. This document includes a collection of the best advice available regarding providers and consumers of reputation data, based on experience to date. Much of this is based on experience with email reputation systems, but the concepts are generally applicable.

Authors

Murray Kucherawy (superuser@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)