Showing T06: OV: Scenario3, I-Invalid
||2011-06-09 17:39:02 UTC
This test checks, if an IUT (Implementation Under Test) can
re-validate prefix/origin pairs of incoming BGP announcement Updates
according to RPKI/RTR whitelist entries, which are announced afterwards
can still operate the acceptance policy (ignore-invalid)
correctly, when the validation state of prefix/origin pairs changes
can fulfil both above, if ROA2 is replaced by ROA2_repair (18.104.22.168/16, OAS6)
and ROA4 is replaced by ROA4_repair (22.214.171.124/16-24, OAS11)
within the following requirements
and scenario 3
Ignore prefix/origin pairs of incoming BGP announcement updates
if their validation state is INVALID, however accept UNKNOWN
Cache to Router
It is expected that the implementation under
test will send a "Query Request" message within 60 seconds of
the receipt of a "Notify" message.
Do not execute any other policies on incoming BGP Updates and do not change
the default BGP best path selection algorithm.
Scenario 3 and Expectations according to ignore-invalid
- t0: Send all BGP Updates
t0-t60: Goal "All Updates, No WL (Unknown)"
Expect to receive all green, blue and red BGP routes.
- t60: Send all ROAs as whitelists
t60-120 and if "All Updates, No WL (Unknown)" success
Goal "Withdraw Invalid Routes": Expect to receive withdrawals
for all red BGP routes.
- t120: Remove ROA2 and ROA4 as whitelists
t120-t180 and if "Withdraw Invalid Routes" success:
Goal "Announce Invalid -> Unknown Routes by broken WL remove": Expect to receive announcements for BGP
routes (126.96.36.199/16, OAS6), (188.8.131.52/17, OAS6), (184.108.40.206/16, OAS11), (220.127.116.11/20, OAS11), (18.104.22.168/24, OAS11)
and (22.214.171.124/25, OAS11)
- t180: Add ROA2_repair (126.96.36.199/16, OAS6) and ROA4_repair (188.8.131.52/16-24, OAS11) as whitelists
t180-t240 and if "Announce Invalid -> Unknown Routes by broken WL remove" success
Goal "Withdraw Unknown -> Invalid (More Specific/ML Exceed) Routes by repaired WL add":
Expect to receive withdrawals for the BGP routes (184.108.40.206/17, OAS6) and (220.127.116.11/25, OAS11)