RFC 7288 on Reflections on Host Firewalls

rfc-editor@rfc-editor.org Tue, 24 June 2014 23:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 84FFF1B2A18 for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jun 2014 16:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 0NqDksqZAQ7X for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jun 2014 16:48:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 4E69D1B29E1 for <ietf-announce@ietf.org>; Tue, 24 Jun 2014 16:47:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4775818000E; Tue, 24 Jun 2014 16:46:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7288 on Reflections on Host Firewalls
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140624234621.4775818000E@rfc-editor.org>
Date: Tue, 24 Jun 2014 16:46:21 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/_r-xvjGKCzdOZfr8FFMQeiq1bko
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 23:48:35 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7288

        Title:      Reflections on Host Firewalls 
        Author:     D. Thaler
        Status:     Informational
        Stream:     IAB
        Date:       June 2014
        Mailbox:    dthaler@microsoft.com
        Pages:      13
        Characters: 28885
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-host-firewalls-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7288.txt

In today's Internet, the need for firewalls is generally accepted in
the industry, and indeed firewalls are widely deployed in practice.
Unlike traditional firewalls that protect network links, host
firewalls run in end-user systems.  Often the result is that software
may be running and potentially consuming resources, but then
communication is blocked by a host 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.

This document is a product of the Internet Architecture Board.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC