Internet-Draft | RPKI ROV Without Route Refresh | November 2021 |
Bush, et al. | Expires 16 May 2022 | [Page] |
A BGP Speaker performing RPKI-based Route Origin Validation should not issue Route Refresh to its neighbors when receiving new VRPs. A method for avoiding doing so is described.¶
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.¶
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 16 May 2022.¶
Copyright (c) 2021 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.¶
Memory constraints in early routers caused classic [RFC4271] BGP implementations to not keep a full Adj-RIB-In (Sec. 1.1). When doing RPKI-based Route Origin Validation ([RFC6811] and [RFC8481]), if such a BGP speaker receives new ROAs/VRPs, it might not have kept paths previously marked as Invalid. Such an implementation must then request a Route Refresh [RFC7313] from its neighbors to recover the paths which might be covered by these new VRPs. This will be perceived as rude by those neighbors as it passes a serious resource burden on to them. This document recommends implementations keep but mark Invalidated paths so the Route Refresh is no longer needed.¶
Routers MUST either keep the full Adj-RIB-In or implement this specification.¶
Operators deploying ROV SHOULD ensure that the router implementation is not causing unnecessary Route Refresh requests to neighbors.¶
If the router does not implement the recommendations here, the operator SHOULD enable the vendor's knob to keep the full Adj-RIB-In, sometimes referred to as "soft reconfiguration inbound". The operator should then ensure that this stops unnecessary Route Refresh requests to neighbors.¶
If the router has insufficient resources to support this, it MUST not be used for Route Origin Validation.¶
This document describes a denial of service Route Origin Validation may place on a BGP neighbor, and describes how it may be ameliorated.¶
Otherwise, this document adds no additional security considerations to those already described by the referenced documents.¶
None¶