From cb1b85375f759eff88a4c973b18a08ec789fa3e6 Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Fri, 26 Aug 2022 12:56:20 -0700 Subject: [PATCH] jgs work-around alston --- draft-ietf-sidrops-rov-no-rr.xml | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/draft-ietf-sidrops-rov-no-rr.xml b/draft-ietf-sidrops-rov-no-rr.xml index 2661a6e..4a740b7 100644 --- a/draft-ietf-sidrops-rov-no-rr.xml +++ b/draft-ietf-sidrops-rov-no-rr.xml @@ -10,7 +10,7 @@ @@ -208,8 +208,8 @@ As storing these routes could cause problems in resource constrained devices, there MUST be a global operation, CLI, YANG, etc. allowing the operator to enable this feature, storing the - dropped routes. Such a control MUST NOT be per peer, as this - could cause inconsistent behavior. + dropped routes. Such an operator control MUST NOT be per peer, as + this could cause inconsistent behavior. @@ -247,11 +247,13 @@ If the BGP speaker's equipment has insufficient resources to - support either of the two proposed options, it MUST NOT be used - for Route Origin Validation. The equipment should either be - replaced with capable equipment or ROV not used. I.e. the knob - in should only be used in very well known and - controlled circumstances. + support either of the two proposed options (keeping a full + AdjRibIn or at least the dropped routes), the equipment should + either be replaced with capable equipment or not use ROV. I.e. + the configuration setting in should only be + used in very well known and controlled circumstances. Such + circumstances could include operational work-arounds such as the + informed consent of the affected peers.