Skip to main content

Reflections On Host Firewalls

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Dave Thaler
Last updated 2013-06-21 (Latest revision 2013-06-04)
Replaced by draft-iab-host-firewalls
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-iab-host-firewalls
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:


In today's Internet, the need for firewalls is generally accepted in the industry and indeed firewalls are widely deployed in practice. Often the result is that software may be running and potentially consuming resources, but then communication is blocked by a firewall. It's taken for granted that this end state is either desirable or the best that can be achieved in practice, rather than (for example) an end state where the relevant software is not running or is running in a way that would not result in unwanted communication. In this document, we explore the issues behind these assumptions and provide suggestions on improving the architecture going forward.


Dave Thaler

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