Distributed Black/White Lists
draft-newton-shafranovich-distributed-blacklists-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Andy Newton , Yakov Shafranovich | ||
Last updated | 2005-02-14 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Many traditional, centrally-managed blacklists and whitelists describe Internet end-points by characteristics such as connectivity type or network function, and these characteristics are often used to infer behavior from which authorization is derived. However, it is often the case that connectivity type or network function are not related to good or bad behavior. This document describes a means of creating blacklists and whitelists representative of Internet end-points based on observed behavior by many participants in a distributed monitoring network. The authors hope that distributed lists will mitigate some of the problems associated with existing centrally managed lists. While the concept, architecture, and data model are general enough to be applied to any type of network service, the authors of this document are specifically addressing the problem of spam in blogs.
Authors
Andy Newton
Yakov Shafranovich
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)