Technical Considerations for Internet Service Blocking
draft-barnes-blocking-considerations-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Richard Barnes , Olaf Kolkman | ||
Last updated | 2013-01-15 (Latest revision 2012-07-16) | ||
Replaced by | draft-iab-filtering-considerations | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-iab-filtering-considerations | |
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
The Internet is structured to be an open communications medium. This openness is one of the key underpinnings of Internet innovation, but it can allow communications that may be viewed as either desirable or undesirable by different parties. Thus, as the Internet has grown, so have mechanisms to limit the extent and impact of abusive or allegedly illegal communications. Recently, there has been an increasing emphasis on "blocking", the active prevention of abusive or allegedly illegal communications. This document examines several technical approaches to Internet content blocking in terms of their alignment with the overall Internet architecture. In general, the approach to content blocking that is most coherent with the Internet architecture is to inform endpoints about potentially undesirable services, so that the communicants can avoid engaging in abusive or illegal communications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)