Revised BGP Maximum Prefix Limits Outbound
draft-sas-idr-maxprefix-outbound-01
Inter-Domain Routing M. Aelmans
Internet-Draft Juniper Networks
Updates: 4271 (if approved) M. Stucchi
Intended status: Standards Track Independent
Expires: April 19, 2021 J. Snijders
NTT
October 16, 2020
Revised BGP Maximum Prefix Limits Outbound
draft-sas-idr-maxprefix-outbound-01
Abstract
This document updates RFC4271 by adding a control mechanism which
limits the negative impact of outbound route leaks (RFC7908) in order
to prevent resource exhaustion in Border Gateway Protocol (BGP)
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 April 19, 2021.
Aelmans, et al. Expires April 19, 2021 [Page 1]
Internet-Draft BGP Maximum Prefix Limits Outbound October 2020
Copyright Notice
Copyright (c) 2020 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
(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. Changes to RFC4271 Section 9 . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
8. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
This document updates [RFC4271] by adding a control mechanism which
limits the negative impact of outbound route leaks [RFC7908] in order
to prevent resource exhaustion in Border Gateway Protocol (BGP)
implementations. [RFC4271] describes methods to tear down BGP
sessions or discard UPDATES after certain inbound thresholds are
exceeded. In addition to "inbound maximum prefix limits", this
document introduces a specification for "outbound maximum prefix
limits". [I-D.sas-idr-maxprefix-inbound] updates sections in
[RFC4271] to clarify "inbound maximum prefix limits". This documents
updates those sections again to add "outbound maximum prefix limits".
2. Changes to RFC4271 Section 6
This section updates [RFC4271] to specify what events can result in
AutomaticStop (Event 8) in the BGP FSM.
Aelmans, et al. Expires April 19, 2021 [Page 2]
Internet-Draft BGP Maximum Prefix Limits Outbound October 2020
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.":
A BGP speaker MAY support the ability to impose a locally-
configured, upper bound on the number of address prefixes the
Show full document text