diff --git a/draft-ietf-sidrops-rov-no-rr.xml b/draft-ietf-sidrops-rov-no-rr.xml index f44c6f1..cb6520b 100644 --- a/draft-ietf-sidrops-rov-no-rr.xml +++ b/draft-ietf-sidrops-rov-no-rr.xml @@ -80,7 +80,7 @@ A BGP Speaker performing RPKI-based policy should not issue Route - Refresh to its neighbors because it has received new RPKI data. +q Refresh to its neighbors because it has received new RPKI data. This document updates RFC8481 by describing how to avoid doing so by either keeping a full Adj-RIB-In or saving paths dropped due to ROV (Route Origin Validation) so they may be reevaluated with @@ -243,7 +243,7 @@ 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 equiptment should either be + for Route Origin Validation. The equipment should either be replaced with capable equipement or ROV not used. I.e. the knob in should only be used in very well known and controlled circumstances. @@ -295,9 +295,9 @@
- The authors wish to thank Ben Maddison, Derek Yeung, John - Heasley, John Scudder, Matthias Waehlisch, Nick Hilliard, Saku - Ytti, and Ties de Kock. + The authors wish to thank Alvaro Retana, Ben Maddison, Derek + Yeung, John Heasley, John Scudder, Matthias Waehlisch, Nick + Hilliard, Saku Ytti, and Ties de Kock.