RFC 7999 on BLACKHOLE Community

rfc-editor@rfc-editor.org Thu, 20 October 2016 00:18 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63D7112985B; Wed, 19 Oct 2016 17:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.033
X-Spam-Level:
X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 dBS_opFbMnsM; Wed, 19 Oct 2016 17:18:28 -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 1B77312986C; Wed, 19 Oct 2016 17:17:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F3FC1B8016A; Wed, 19 Oct 2016 17:17:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7999 on BLACKHOLE Community
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161020001741.F3FC1B8016A@rfc-editor.org>
Date: Wed, 19 Oct 2016 17:17:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/iQBMWCLBGHaBtQhrdDpVE_a-0es>
Cc: drafts-update-ref@iana.org, grow@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Oct 2016 00:18:38 -0000

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

        
        RFC 7999

        Title:      BLACKHOLE Community 
        Author:     T. King, C. Dietzel,
                    J. Snijders, G. Doering,
                    G. Hankins
        Status:     Informational
        Stream:     IETF
        Date:       October 2016
        Mailbox:    thomas.king@de-cix.net, 
                    christoph.dietzel@de-cix.net, 
                    job@ntt.net,
                    gert@space.net, 
                    greg.hankins@nokia.com
        Pages:      9
        Characters: 16794
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-blackholing-03.txt

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

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

This document describes the use of a well-known Border Gateway
Protocol (BGP) community for destination-based blackholing in IP
networks.  This well-known advisory transitive BGP community named
"BLACKHOLE" allows an origin Autonomous System (AS) to specify that a
neighboring network should discard any traffic destined towards the
tagged IP prefix.

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