Browse Prior Art Database

BGP Operations and Security (RFC7454)

IP.com Disclosure Number: IPCOM000240701D
Original Publication Date: 2015-Feb-01
Included in the Prior Art Database: 2015-Feb-19
Document File: 52 page(s) / 57K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Durand: AUTHOR [+3]

Abstract

The Border Gateway Protocol (BGP), specified in RFC 4271 [2], is the protocol used in the Internet to exchange routing information between network domains. BGP does not directly include mechanisms that control whether the routes exchanged conform to the various guidelines defined by the Internet community. This document intends to both summarize common existing guidelines and help network administrators apply coherent BGP policies.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                         J. Durand Request for Comments: 7454                           Cisco Systems, Inc. BCP: 194                                                    I. Pepelnjak Category: Best Current Practice                                      NIL ISSN: 2070-1721                                               G. Doering                                                                 SpaceNet                                                            February 2015

                       BGP Operations and Security

Abstract

   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.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7454.

Durand, et al.            Best Current Practice                 [Page 1]
 RFC 7454                        BGP OPSEC                  February 2015

 Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this ...