[GROW] RFC 7789 on Impact of BGP Filtering on Inter-Domain Routing Policies

rfc-editor@rfc-editor.org Thu, 07 April 2016 00:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83AED12D7CD; Wed, 6 Apr 2016 17:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.932
X-Spam-Level:
X-Spam-Status: No, score=-106.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 LQ-CeGlQm--k; Wed, 6 Apr 2016 17:15:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBA7E12D52B; Wed, 6 Apr 2016 17:15:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8CF6618000B; Wed, 6 Apr 2016 17:14:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160407001445.8CF6618000B@rfc-editor.org>
Date: Wed, 06 Apr 2016 17:14:45 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/868FfoRFiU8iRHaolgwkw2BkQpQ>
Cc: grow@ietf.org, rfc-editor@rfc-editor.org
Subject: [GROW] RFC 7789 on Impact of BGP Filtering on Inter-Domain Routing Policies
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 00:15:41 -0000

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

        
        RFC 7789

        Title:      Impact of BGP Filtering on 
                    Inter-Domain Routing Policies 
        Author:     C. Cardona, P. Francois,
                    P. Lucente
        Status:     Informational
        Stream:     IETF
        Date:       April 2016
        Mailbox:    juancamilo.cardona@imdea.org, 
                    pifranco@cisco.com, 
                    plucente@cisco.com
        Pages:      16
        Characters: 38047
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-filtering-threats-08.txt

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

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

This document describes how unexpected traffic flows can emerge
across an autonomous system as the result of other autonomous systems
filtering or restricting the propagation of more-specific prefixes.
We provide a review of the techniques to detect the occurrence of
this issue and defend against it.

This document is a product of the Global Routing Operations Working Group of the IETF.


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