Internet Content Filtering Protocol
draft-gutfreund-content-filtering-protocol-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Keith Gutfreund | ||
| Last updated | 1999-05-10 | ||
| 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
The Content Filtering Protocol (CFP) has been developed to facilitate the connection of content filtering databases to Internet firewall systems. CFP compliance allows content filters to be located 'behind the firewall,' where they are safe from outside hostile attack. The CFP is a binary protocol used by firewall systems to communicate over a private TCP/IP connection to the content filtering database server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)