Showing T19: OV: ROA Grandparent Prefix Revoked,New ROA Diff AS,I-Unknown,I-Invalid
||2011-11-14 21:14:57 UTC
Same as test OV:ROA Grandarent Prefix Revoked,New ROA Diff AS,Ignore Invalid,
but the policy is to accept "valid" only.
The IUT MUST be configured to accept "valid", and ignore both "unknown" and
"invalid" validity state of a received route (i.e., a prefix and an originAS)
for further process.
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 an 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 and later receives WDs from the IUT. The IUT announces
WDs for Updates 1, 3 and 6, which became "unknown" from previously "valid".
- 00:03 - BRITE sends ROA 4, the previously revoked ROA with different AS. The IUT announces
Update 7, the previously "invalid" route, which became "valid".
- 00:04 - Test ends.