Protocol Action: 'BGP operations and security' to Best Current Practice (draft-ietf-opsec-bgp-security-07.txt)

The IESG <> Mon, 08 December 2014 17:18 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B5E571AC409; Mon, 8 Dec 2014 09:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3wSeS7dqEzTf; Mon, 8 Dec 2014 09:18:11 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 534581AC40F; Mon, 8 Dec 2014 09:18:06 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'BGP operations and security' to Best Current Practice (draft-ietf-opsec-bgp-security-07.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 08 Dec 2014 09:18:06 -0800
Cc: opsec mailing list <>, opsec chair <>, RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Dec 2014 17:18:12 -0000

The IESG has approved the following document:
- 'BGP operations and security'
  (draft-ietf-opsec-bgp-security-07.txt) as Best Current Practice

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

The IESG contact persons are Joel Jaeggli and Benoit Claise.

A URL of this Internet Draft is:

Technical Summary

  BGP (Border Gateway Protocol) 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
   (like TTL, TCP-AO, control plane filtering) and to better control the
   flow of routing information, using prefix filtering and
   automatization of prefix filters, max-prefix filtering, AS path
   filtering, route flap dampening and BGP community scrubbing.

Working Group Summary

Nothing particular to point out. The document and work contribution went 
smoothly without hiccups.

Document Quality

This Is an operational document describing best practices. The baseline 
of the document is the writing down of what successful BGP network
 implementations have deployed.


Document Shepherd: Gunter Van de Velde
Responsible Area director: Joel Jaeggli