Hi Pradosh,
On Tue, 5 Nov 2013, Pradosh Mohapatra wrote:
Couple of points.
2) That said, it is still a good practice to set preference based on each
validation state
because of the distributed nature of the network (the ROA database on all
routers
in an AS will not be consistent) and because of incremental deployment of
origin
validation. Think of the following simple topology:
I dont agree, the ROA database is the same everywhere. I verified and
checked this between several routers having a validation database.
All routers have the same amount of ROAs.
Suppose the same destination prefix 'p' is received on both R2 and R3. 'p'
may not
be present on R2's ROA database, making it 'NotFound'. At the same time,
'p' is
present on R3's ROA database, making it 'Valid'. You would want to set the
preference
correctly through your routing policy so that R1 prefers R3 (assume R1
does not yet
support origin validation).
This thus won't happen.
Jac
--
Jac Kloots
Network Services
SURFnet bv
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
