rules-clear-drop
Purpose
Confirm clear_drop: a request rule may set soft drop and then cancel it
so the query still forwards and returns a successful A answer. Operators can
undo soft-drop intent on the same rule.
Results appear on the Conduit behavior matrix (one stub peer).
How it works
- The peer answers
allow.clear-drop.test→192.0.2.20. - Conduit runs with a matching rule that applies
dropthenclear_drop, then the catch-allset_pool. - A client queries that name through Conduit.
- Checks require NOERROR and at least one answer RR.
Outcomes
| Outcome | Meaning for operators |
|---|---|
| pass | Soft drop was cleared; the forward path returned a successful A answer. |
| fail | Unexpected: still no answer or other failure — clear_drop did not restore forward. |
| skip | This peer/profile combination is out of scope. |
| characterized | Not used for this case today. If it appeared, it would mean a documented peer-specific quirk rather than a Conduit regression. |
Matrix: conduit (Conduit behavior)
Suites: full
Oracles: property