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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-03-01
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: September 3, 2012                                           NIL
                                                              G. Doering
                                                                SpaceNet
                                                           March 2, 2012

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

Abstract

   This documents describes best current practices to manage securely
   BGP in a network.  It will explain the basic policies ones should
   configure on BGP peerings to keep an healthy BGP table.  This
   document will only focus on unicast and multicast tables (SAFI 1 and
   2) for IPv4 and IPv6.

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/.

   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 September 3, 2012.

Copyright Notice

Durand, et al.          Expires September 3, 2012               [Page 1]
Internet-Draft                  BGP OPSEC                     March 2012

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Protection of BGP sessions . . . . . . . . . . . . . . . . . .  3
     3.1.  MD5 passwords on BGP peerings  . . . . . . . . . . . . . .  3
     3.2.  BGP TTL security . . . . . . . . . . . . . . . . . . . . .  3
   4.  Prefix filtering . . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  Definition of prefix filters . . . . . . . . . . . . . . .  4
       4.1.1.  Prefixes that are not routable by definition . . . . .  4
       4.1.2.  Prefixes not allocated . . . . . . . . . . . . . . . .  5
       4.1.3.  Prefixes too specific  . . . . . . . . . . . . . . . .  7
       4.1.4.  Anti-spoofing filters  . . . . . . . . . . . . . . . .  8
       4.1.5.  Exchange point LAN prefixes  . . . . . . . . . . . . .  8
       4.1.6.  Default route  . . . . . . . . . . . . . . . . . . . .  8
     4.2.  Prefix filtering recommendations in full routing
           networks . . . . . . . . . . . . . . . . . . . . . . . . .  8
       4.2.1.  Filters with internet peers  . . . . . . . . . . . . .  8
       4.2.2.  Filters with customers . . . . . . . . . . . . . . . . 10
       4.2.3.  Filters with upstream providers  . . . . . . . . . . . 11
     4.3.  Prefix filtering recommendations for leaf networks . . . . 11
       4.3.1.  Ingress filtering  . . . . . . . . . . . . . . . . . . 11
       4.3.2.  Egress filtering . . . . . . . . . . . . . . . . . . . 12
   5.  BGP route flap dampening . . . . . . . . . . . . . . . . . . . 12
   6.  Maximum prefixes on a peering  . . . . . . . . . . . . . . . . 12
   7.  AS-path filtering  . . . . . . . . . . . . . . . . . . . . . . 12
   8.  BGP community scrubbing  . . . . . . . . . . . . . . . . . . . 13
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 14
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 14
Show full document text