From 2f10b3c344cf85935c6984b72f564c1e8c8b1f8f Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Wed, 1 Feb 2023 12:11:30 -0800 Subject: [PATCH] error term explicit flush --- draft-ietf-sidrops-8210bis.xml | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/draft-ietf-sidrops-8210bis.xml b/draft-ietf-sidrops-8210bis.xml index ca4798f..e1432a4 100644 --- a/draft-ietf-sidrops-8210bis.xml +++ b/draft-ietf-sidrops-8210bis.xml @@ -1,7 +1,5 @@ - - @@ -133,6 +131,10 @@ race conditions, Break Before Make and Shorter Prefix First. + + Language was clarified when multiple caches are + configured, and an interesting affect is noted. + The protocol version number incremented from 1 (one) to 2 (two) and has been updated @@ -236,13 +238,22 @@ one or more caches with which it has client/server relationships. It is configured with a semi-ordered list of caches and establishes a connection to the most preferred cache, - or set of caches, which accept the connections. + or set of caches with that same priority, which accept the + connections. The router MUST choose the most preferred, by configuration, cache or set of caches so that the operator may control load on their caches and the Global RPKI. + + If the router is fetching from multiple caches, then withdraws + of a particular VRP invalidating some prefix may take effect for + longer than announcements of that VRP. This is because all + caches must have withdrawn the VRP for the router to not have a + copy; but if any router has received an announcement then that + VRP is in effect. + Periodically, the router sends a Serial Query to the cache the most recent Serial Number for which it has received data from