RFC 7754 on Technical Considerations for Internet Service Blocking and Filtering

rfc-editor@rfc-editor.org Thu, 03 March 2016 19:43 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 245FE1B420A for <ietf-announce@ietfa.amsl.com>; Thu, 3 Mar 2016 11:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.908
X-Spam-Level:
X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id baWxTklUaRvd for <ietf-announce@ietfa.amsl.com>; Thu, 3 Mar 2016 11:43:40 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6349D1A9034 for <ietf-announce@ietf.org>; Thu, 3 Mar 2016 11:43:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 711EC180016; Thu, 3 Mar 2016 11:42:40 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7754 on Technical Considerations for Internet Service Blocking and Filtering
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160303194240.711EC180016@rfc-editor.org>
Date: Thu, 03 Mar 2016 11:42:40 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/3R1_phX8vWZ0WAEudfD8cYiumz8>
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Mar 2016 19:43:42 -0000

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

        
        RFC 7754

        Title:      Technical Considerations for Internet Service 
                    Blocking and Filtering 
        Author:     R. Barnes, A. Cooper,
                    O. Kolkman, D. Thaler,
                    E. Nordmark
        Status:     Informational
        Stream:     IAB
        Date:       March 2016
        Mailbox:    rlb@ipv.sx, 
                    alcoop@cisco.com, 
                    kolkman@isoc.org,
                    dthaler@microsoft.com, 
                    nordmark@arista.com
        Pages:      33
        Characters: 85046
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-filtering-considerations-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7754

        DOI:        http://dx.doi.org/10.17487/RFC7754

The Internet is structured to be an open communications medium.  This
openness is one of the key underpinnings of Internet innovation, but
it can also allow communications that may be viewed as undesirable by
certain parties.  Thus, as the Internet has grown, so have mechanisms
to limit the extent and impact of abusive or objectionable
communications.  Recently, there has been an increasing emphasis on
"blocking" and "filtering", the active prevention of such
communications.  This document examines several technical approaches
to Internet blocking and filtering in terms of their alignment with
the overall Internet architecture.  When it is possible to do so, the
approach to blocking and filtering 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 objectionable communications.  We observe that certain
filtering and blocking approaches can cause unintended consequences
to third parties, and we discuss the limits of efficacy of various
approaches.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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