randy/draft-rov-no-rr
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

lars nits

Browse source
This commit is contained in:
Randy Bush 2022-08-24 11:39:56 -07:00
parent d4d1217fd7
commit 34827af356
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
draft-ietf-sidrops-rov-no-rr.xml
View file

@ -121,7 +121,7 @@ q Refresh to its neighbors because it has received new RPKI data.
might be covered by these new RPKI data. This will be perceived
as rude by those neighbors as it passes a serious resource burden
on to them. This document recommends implementations keep and
mark paths affected by RPKI-based policy so Route Refresh is no
mark paths affected by RPKI-based policy, so Route Refresh is no
longer needed.
</t>
@ -149,7 +149,7 @@ q Refresh to its neighbors because it has received new RPKI data.
BGP speaker implementations have been found which, when receiving new
RPKI data (VRPs, see <xref target="I-D.ietf-sidrops-8210bis"/>)
issue a BGP Route Refresh <xref target="RFC7313"/> to all sending
BGP peers so that it can reevaluate the received paths aginst the
BGP peers so that it can reevaluate the received paths against the
new data.
</t>
@ -193,7 +193,7 @@ q Refresh to its neighbors because it has received new RPKI data.
<t>
If new RPKI data arrive which invalidate the best route, and the
BGP speaker did not keep all alternatives, then it MUST issue a
route refresh so those alternatives may be evaluated for best
route refresh, so those alternatives may be evaluated for best
route.
</t>