[Idr] BCP 194, RFC 7454 on BGP Operations and Security

<bruno.decraene@orange.com> Thu, 19 February 2015 12:52 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id DBA241A9024; Thu, 19 Feb 2015 04:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id zB6Uo10_rb4h; Thu, 19 Feb 2015 04:52:30 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45FFE1A9037; Thu, 19 Feb 2015 04:52:30 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id EFBB1264357; Thu, 19 Feb 2015 13:52:28 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown []) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id D07EE4C0C7; Thu, 19 Feb 2015 13:52:28 +0100 (CET)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0224.002; Thu, 19 Feb 2015 13:52:28 +0100
From: bruno.decraene@orange.com
To: idr wg <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: BCP 194, RFC 7454 on BGP Operations and Security
Thread-Index: AQHQS8+HjMYsdm205UywHhGifFSYZ5z37UnA
Date: Thu, 19 Feb 2015 12:52:27 +0000
Message-ID: <4431_1424350348_54E5DC8C_4431_398_1_53C29892C857584299CBF5D05346208A0EB3EDB8@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <20150218230309.5D671181D1F@rfc-editor.org>
In-Reply-To: <20150218230309.5D671181D1F@rfc-editor.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2014.12.22.190922
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/3jnerYWqnNyWn_BZ_BRFKkNRDlY>
Subject: [Idr] BCP 194, RFC 7454 on BGP Operations and Security
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 12:52:33 -0000

FYI. Might be of interest of IDR & GROW WG 

-----Original Message-----
From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org
Sent: Thursday, February 19, 2015 12:03 AM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: opsec@ietf.org; rfc-editor@rfc-editor.org
Subject: BCP 194, RFC 7454 on BGP Operations and Security

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

        BCP 194        
        RFC 7454

        Title:      BGP Operations and Security 
        Author:     J. Durand, I. Pepelnjak, G. Doering
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2015
        Mailbox:    jerduran@cisco.com, 
        Pages:      26
        Characters: 56946
        See Also:   BCP 194

        I-D Tag:    draft-ietf-opsec-bgp-security-07.txt

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

The Border Gateway Protocol (BGP) is the protocol almost exclusively used in the Internet to exchange routing information between network domains.  Due to this central nature, it is important to understand the security measures that can and should be deployed to prevent accidental or intentional routing disturbances.

This document describes measures to protect the BGP sessions itself such as Time to Live (TTL), the TCP Authentication Option (TCP-AO), and control-plane filtering.  It also describes measures to better control the flow of routing information, using prefix filtering and automation of prefix filters, max-prefix filtering, Autonomous System
(AS) path filtering, route flap dampening, and BGP community scrubbing.

This document is a product of the Operational Security Capabilities for IP Network Infrastructure Working Group of the IETF.

BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 https://www.rfc-editor.org/search For downloading RFCs, see https://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


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.