BGP operations and security
draft-jdurand-bgp-security-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-06-19
Replaced by draft-ietf-opsec-bgp-security, rfc7454
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                J. Durand
Internet-Draft                                       CISCO Systems, Inc.
Intended status: BCP                                        I. Pepelnjak
Expires: December 21, 2012                                           NIL
                                                              G. Doering
                                                                SpaceNet
                                                           June 19, 2012

                      BGP operations and security
                   draft-jdurand-bgp-security-01.txt

Abstract

   BGP (Border Gateway Protocol) is the protocol used in the internet to
   exchange routing information between network domains.  This protocol
   does not directly include mechanisms that control that routes
   exchanged conform to the various rules defined by the Internet
   community.  This document intends to summarize most common existing
   rules and help network administrators applying simply coherent BGP
   policies.  First it recalls mechanisms that administrators can use to
   protect the BGP sessions, with TTL and MD5.  Then the document
   describes the prefix filters that can be used, how some of them can
   be automated, and where they apply in the BGP network.  Afterwards,
   applicability of other methods including BGP route flap dampening,
   limiting maximum prefixes per peering, AS-path filtering and
   community scrubbing is analyzed.

Foreword

   A placeholder to list general observations about this document.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [1].

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

Durand, et al.          Expires December 21, 2012               [Page 1]
Internet-Draft                  BGP OPSEC                      June 2012

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 21, 2012.

Copyright Notice

   Copyright (c) 2012 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 document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Durand, et al.          Expires December 21, 2012               [Page 2]
Internet-Draft                  BGP OPSEC                      June 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Protection of BGP sessions . . . . . . . . . . . . . . . . . .  4
     3.1.  MD5 passwords on BGP peerings  . . . . . . . . . . . . . .  4
     3.2.  BGP TTL security . . . . . . . . . . . . . . . . . . . . .  4
   4.  Prefix filtering . . . . . . . . . . . . . . . . . . . . . . .  5
     4.1.  Definition of prefix filters . . . . . . . . . . . . . . .  5
       4.1.1.  Prefixes that MUST not be routed by definition . . . .  5
       4.1.2.  Prefixes not allocated . . . . . . . . . . . . . . . .  6
       4.1.3.  Prefixes too specific  . . . . . . . . . . . . . . . .  9
       4.1.4.  Filtering prefixes belonging to local AS . . . . . . .  9
       4.1.5.  Internet exchange point (IXP) LAN prefixes . . . . . . 10
       4.1.6.  Default route  . . . . . . . . . . . . . . . . . . . . 11
     4.2.  Prefix filtering recommendations in full routing
           networks . . . . . . . . . . . . . . . . . . . . . . . . . 11
       4.2.1.  Filters with internet peers  . . . . . . . . . . . . . 12
       4.2.2.  Filters with customers . . . . . . . . . . . . . . . . 13
       4.2.3.  Filters with upstream providers  . . . . . . . . . . . 14
     4.3.  Prefix filtering recommendations for leaf networks . . . . 14
       4.3.1.  Inbound filtering  . . . . . . . . . . . . . . . . . . 14
Show full document text