<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 21/Jun/20 12:45, Baldur Norddahl
wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CAPkb-7DrEWwy4yY+xV9TtFBFSzd2w2euaM3zt0ab5J0Coj9O4w@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>Yes I once made a plan to have one VRF per transit
provider plus a peering VRF. That way our BGP customers
could have a session with each of those VRFs to allow them
full control of the route mix. I would of course also need a
Internet VRF for our own needs.</div>
<div><br>
</div>
<div>But the reality of that would be too many copies of the
DFZ in the routing tables. Although not necessary in the FIB
as each of the transit VRFs could just have a default route
installed.</div>
</div>
</div>
</blockquote>
<br>
We just opted for BGP communities :-).<br>
<br>
Mark.<br>
</body>
</html>