Showing T21: OV: ROA Successive Revocations / Renews, I-Invalid

Owner okim
Date created 2011-11-15 15:15:49 UTC

Test Description

Check to see whether an IUT correctly determines and updates the validity state of received Updates (routes) when ROAs for grandparent prefix (super-super prefix), parent prefix (super-prefix) and a more-specific prefix are revoked (or expired) in sequence and are subsequently renewed in reverse order. The IUT is expected to demonstrate their impacts (i.e., the successive revocations / renews of ROAs) on the route selection based on the route validity state. When an end-entity ROA is revoked, IUT is expected to send the best path route (10.10.0.0/24,AS20) which is the route with the shortest AS path length over the existing route (10.10.0.0/24,AS30). When an end-entity ROA is renewed, IUT is expected to announce a route with valid ROA, which is (10.10.0.0/24,AS30). It is assumed that a ROA is considered as revoked or expired when an EE used to sign the corresponding ROA is revoked or expired, or any intermediate CA certificates in the certification chain used to validate the EE is expired (or revoked).

Requirements

The IUT MUST be configured to reject "invalid", and to accept both "valid" and "unknown" validity state of a received route (i.e., a prefix and an originAS) for further process. Here, the ROA is defined as "data record" received by the IUT from a RPKI Cache.

Test data and Topology



                         (AS2)----------(AS25)----------(AS24)----------(AS20)
                          |
       [BRITE              |
       COLLECTOR]---------IUT(AS10000)----------[BRITE Cache]
                          |
                          |
                         (AS3)----------(AS39)----------(AS36)----------(AS31)----------(AS30)
    

At the beginning of the test, three ROAs and 7 BGP Updates (see below) are sent to the IUT. A ROA for grandparent prefix is revoked first, followed by a ROA for parent prefix, and followed by an end-entity ROA (with a more-specific prefix). The ROAs are renewed in reverse order, i.e., an end-entity ROA (with a more-specific prefix) first, followed by a ROA for parent prefix, and followed by a ROA for grandparent prefix.

Scenario and Expectations

  • 00:00 - BRITE cache sends three ROAs (data records) to the IUT:
    • ROA 1 [10.10.0.0/16,24,AS30]: ROA for grandparent prefix (i.e., super-super prefix) with maxLength.
    • ROA 2 [10.10.0.0/20,24,AS30]: ROA for parent prefix (i.e., super prefix) with maxLength.
    • ROA 3 [10.10.0.0/24,24,AS30]: ROA for end-entity prefix with no maxLength (or prefix length is equal to maxLength).
  • 00:01 - The following Updates are sent to the IUT:
    • Update 1 (10.10.0.0/16, AS30)
    • Update 2 (10.10.0.0/20, AS30)
    • Update 3 (10.10.128.0/20, AS30)
    • Update 4 (10.10.0.0/24, AS30)
    • Update 5 (10.10.15.0/24, AS30)
    • Update 6 (10.10.128.0/24, AS30)
    • Update 7 (10.10.0.0/24, AS20)
    • BRITE expects to receive six Updates (Updates 1-6) except an invalid route, Update 7, from the IUT.
  • 00:02 - BRITE revokes ROA 1. The IUT changes the validity state of the previously "valid" routes to "unknown" (Updates 1, 3 and 6) and sends no WDs or ANNs.
  • 00:03 - BRITE revokes ROA 2. The IUT changes the validity state of the previously "valid" routes to "unknown" (Updates 2 and 5) and sends not WDs or ANNs.
  • 00:04 - BRITE revokes ROA 3. The IUT changes the validity state of the previously "valid" route to "unknown" (Update 4) and sends the best route (Update 7) which is also "unknown", but with shorter ASpath compared to Update 4. ASpath of Update 7 is [2 25 24 20] whereas ASpath of Update 4 is [3 39 36 31 30].
  • 00:05 - BRITE sends the previously revoked ROA 3 again. The IUT changes the validity state of the previously "unknown" route (Update 4) to "valid" again and announces Update 4 since a valid ROA exists for the route.
  • 00:06 - BRITE sends the previously revoked ROA 2 again. The IUT changes the validity state of the previously "unknown" routes to "valid" (Updates 2 and 5) and sends no Updates.
  • 00:07 - BRITE sends the previously revoked ROA 1 again. The IUT changes the validity state of previously "unknown" routes to "valid" (Updates 1, 3 and 6) and send no Updates.
  • 00:08 - Test ends.