<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 17/Jun/20 10:20, Baldur Norddahl
wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CAPkb-7BB+H+fi58+cQuyxru0J8K6mrZQbyoCTadBEK3cTycD1w@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jun 17, 2020 at
10:07 AM Niels den Otter <<a
href="mailto:niels.denotter@surfnet.nl"
moz-do-not-send="true">niels.denotter@surfnet.nl</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p>Hello Baldur,</p>
<p>If you want to validate routes in a VRF you need to
configure;</p>
<p>set routing-options validation notification-rib
<rib></p>
<p>Have you done so?</p>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<div><br>
</div>
<div>That was missing from the config. After adding it and
running the command "request validation policy" I got the
prefixes validated.</div>
</div>
</div>
</blockquote>
<br>
Not to sound funny, but this is one of the reasons I am still afraid
to run the Internet in a VRF. There are a lot more things to
consider, I've often found, compared to what you take for granted in
the global table.<br>
<br>
That said, this is great to know, given that many operators run the
Internet in a VRF, and we need RPKI + ROV to be supported far and
wide.<br>
<br>
Mark.<br>
</body>
</html>