Showing T04: OV: Scenario2, I-Invalid

Owner sspies
Date created 2011-06-09 17:39:02 UTC

Test Description

Intention

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
within the following requirements, dataset and scenario 3

Requirements

  • Policy
    Ignore prefix/origin pairs of incoming BGP announcement updates
    if their validation state is INVALID, however accept UNKNOWN and VALID.
  • 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.
  • Policy
    Do not execute any other policies on incoming BGP Updates and do not change the default BGP best path selection algorithm.

Dataset

Scenario 2 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 all ROAs as whitelists
  • t120-t180 and if "All Updates, No WL (Unknown)" success
    Goal Reannounce Invalid -> Unknown Routes: Expect to receive announcements for all red BGP routes.