An Internet Firewall Transparency Requirement
draft-freed-firewall-req-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ned Freed , Kevin V. Carosso | ||
| Last updated | 1997-12-30 | ||
| 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
This memo defines a basic transparency requirement for Internet firewalls. While such a requirement may seem obvious, the fact of the matter is that firewall behavior is currently either unspecified or underspecified, and this lack of specificity often causes problems in practice. This requirement is intended to be a necessary first step in making the behavior of firewalls more consistent and correct.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)