BGP Maximum Prefix Limits Inbound
draft-sas-idr-maxprefix-inbound-00

Document Type Active Internet-Draft (individual)
Last updated 2020-04-15
Replaces draft-sa-idr-maxprefix
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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)
Inter-Domain Routing                                         J. Snijders
Internet-Draft                                                       NTT
Updates: 4271 (if approved)                                   M. Aelmans
Intended status: Standards Track                        Juniper Networks
Expires: October 17, 2020                                     M. Stucchi
                                                             Independent
                                                          April 15, 2020

                   BGP Maximum Prefix Limits Inbound
                   draft-sas-idr-maxprefix-inbound-00

Abstract

   This document describes mechanisms to limit the negative impact of
   route leaks [RFC7908] and/or resource exhaustion in BGP [RFC4271]
   implementations.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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 https://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 October 17, 2020.

Copyright Notice

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

Snijders, et al.        Expires October 17, 2020                [Page 1]
Internet-Draft      BGP Maximum Prefix Limits Inbound         April 2020

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Changes to RFC4271 Section 6  . . . . . . . . . . . . . . . .   2
   3.  Changes to RFC4271 Section 8  . . . . . . . . . . . . . . . .   3
   4.  BGP Yang Model Considerations - PERHAPS REMOVE BEFORE
       PUBLICATION . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Changes to RFC4271 Section 9  . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION   5
   10. Appendix: Implementation Guidance . . . . . . . . . . . . . .   6
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   This document updates [RFC4271] by revising control mechanism which
   limit the negative impact of route leaks [RFC7908] and/or resource
   exhaustion in Border Gateway Protocol (BGP) implementations.  While
   [RFC4271] described methods to tear down BGP sessions or discard
   UPDATES after certain thresholds are exceeded, some nuances in this
   specification were missing resulting in inconsistencies between BGP
   implementations.

2.  Changes to RFC4271 Section 6

   This section updates [RFC4271] to specify what events can result in
   AutomaticStop (Event 8) in the BGP FSM.

   The following paragraph replaces the second paragraph of Section 6.7
   (Cease), which starts with "A BGP speaker MAY support" and ends with
   "The speaker MAY also log this locally.":

Snijders, et al.        Expires October 17, 2020                [Page 2]
Internet-Draft      BGP Maximum Prefix Limits Inbound         April 2020

      A BGP speaker MAY support the ability to impose a locally-
      configured, upper bound on the number of address prefixes the
      speaker is willing to accept from a neighbor (inbound maximum
      prefix limit).  The limit on the prefixes accepted from a neighbor
Show full document text