No row in the public ledger

DRAFT-IETF-SIDROPS-8210BIS - The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 2

Every requirement this repository extracted from DRAFT-IETF-SIDROPS-8210BIS, the tests bound to it, and what a reader has verified about them. This summary is not enrolled.

Overview

Positive

what Ze has

Tested both ways0.0%0 of 7 binding obligations

a positive test proves Ze does what the requirement demands and a negative one proves it refuses what the requirement forbids

One polarity plus reason14.3%1 of 7 binding obligations

the requirement admits no counter-case, so one polarity plus a recorded reason is the whole proof available for it

One polarity, unexcused0.0%0 of 7 binding obligations

one direction is tested, the other is neither tested nor excused, and nothing states which

Proven by a recorded break0.0%0 of 0 tagged units

a red was observed once under a recorded procedure, and the unit, the claim and the producer it rested on still hash to what was recorded. The break is not re-run. A test pair is not a proof until one has been observed

Neutral

measures that are neither good news nor bad

MUSTs declared10of 13 this summary declares

MUST-level requirements this summary DECLARES. The gate holds none of them, because this RFC is not enrolled (backlog), so every share below reads what the summary records rather than what the gate enforces

Out of scope3of 10 gated MUSTs

a {not-applicable} annotation says the obligation does not bind Ze. Scope, not coverage: it is in no share below

Negative

what Ze owes

No test at all85.7%6 of 7 binding obligations

no test carries the requirement id, whether or not a gap states why

The 4 shares marked as a part above are the whole of the 7 obligations that bind Ze: they add to 100%. Proven by a recorded break is a share of TAGGED UNITS, a different population, so it is not one of them.

How to read the colors

A color names what the measure MEANS, not how well Ze scores on it. Green is a good outcome at any value, red is a bad one, and neither a population nor a scope count is an outcome, so both take no color. The number under the label is what says how far Ze has got.

Card	Tone here	Why that color
MUSTs declared	neutral	no color: a population is a scale, and a larger one is neither good news nor bad. It is the accounting total
Out of scope	neutral	no color: an obligation that never bound Ze is neither an achievement nor a failure, and counting it either way would be a claim
Tested both ways	ok	green at every value: a test pair is the outcome this gate exists to produce, and the share under the label is what says how far Ze has got
One polarity plus reason	ok	green at every value: where no counter-case exists, one polarity IS the complete answer, and a recorded reason is what the gate demands beside it
One polarity, unexcused	ok	green at zero, RED above it: half a proof with no reason for the other half
No test at all	bad	green at zero, RED above it: a binding obligation nothing exercises is a claim with nothing behind it, whether or not a reason is stated
Proven by a recorded break	ok	green at every value: an observed break is the outcome the discrimination gate exists to produce. The denominator is TAGGED UNITS, not obligations, so this share is not one of the parts above
Audit verdicts	warn	RED on the first weak, wrong or unimplemented verdict, amber while a verdict is no longer current or a gated MUST is unjudged, green when every one is judged sound and current

At a glance

Field	Value
Public status	No row in the public ledger
Enrolment	Not enrolled (backlog)
Requirements	13
Gated MUST-level	10
Obligations that bind Ze	7
Not applicable, so out of scope	3
Declared gaps	0
Gated with no test	6
Nightly-only evidence	0
Test tags	0
Tagged units	0
Recorded audit verdicts	0
Discrimination records	0
Summary	`rfc/short/draft-ietf-sidrops-8210bis.md`
Requirement shard	`rfc/requirements/draft-ietf-sidrops-8210bis.md`
RFC text	`rfc/drafts/draft-ietf-sidrops-8210bis.txt`

Enrolment

Not enrolled (backlog, the requirements have not been extracted from the document yet; this is work owed rather than a decision): The RPKI to Router Protocol, Version 2. Split out of rfc9582 on 2026-09-01 because the obligations below are stated by this draft and not by RFC 9582, which profiles the ROA certificate. It is not enrolled because its obligations are not yet proven and the draft is still in the RFC Editor queue, so a version bump can restate them.

What the public ledger says

No row in the public ledger, so its summary declares `| Support | - |` and docs/features/rfc-status.md carries no row for DRAFT-IETF-SIDROPS-8210BIS.

Coverage

Bucket	Count	What it counts
Positive and negative tests	0	one part of the gated population
Annotated instead of tested	4	one part of the gated population
One polarity only	0	one part of the gated population
No test and no annotation	6	one part of the gated population
Evidence that runs nightly only	0	an overlay: each of these is also counted by the part it falls in
Gated MUST-level requirements	10	every gated MUST falls in exactly one bucket above

Annotated instead of tested (4): DRAFT-IETF-SIDROPS-8210BIS-5.12-4, DRAFT-IETF-SIDROPS-8210BIS-5.12-5, DRAFT-IETF-SIDROPS-8210BIS-7-1, DRAFT-IETF-SIDROPS-8210BIS-7-3

No test and no annotation (6): DRAFT-IETF-SIDROPS-8210BIS-5.12-1, DRAFT-IETF-SIDROPS-8210BIS-5.12-2, DRAFT-IETF-SIDROPS-8210BIS-5.12-3, DRAFT-IETF-SIDROPS-8210BIS-5.12-6, DRAFT-IETF-SIDROPS-8210BIS-5.12-7, DRAFT-IETF-SIDROPS-8210BIS-7-2

Requirements

Requirement	Level	Section	Tests
`DRAFT-IETF-SIDROPS-8210BIS-5.12-1`	Provider AS set in ASPA PDU MUST contain at least one provider ASN (§5.12)
	MUST	5.12	positive`no test`no positive test negative`no test`no negative test
`DRAFT-IETF-SIDROPS-8210BIS-5.12-2`	Customer AS MUST NOT appear in its own provider set (§5.12)
	MUST NOT	5.12	positive`no test`no positive test negative`no test`no negative test
`DRAFT-IETF-SIDROPS-8210BIS-5.12-3`	Provider ASNs MUST be in ascending order within the PDU (§5.12)
	MUST	5.12	positive`no test`no positive test negative`no test`no negative test
`DRAFT-IETF-SIDROPS-8210BIS-5.12-4`	Cache MUST ensure one ASPA PDU per (Customer-AS, AFI) pair (§5.12)
	MUST	5.12	positive`no test`no positive test negative`no test`no negative test {not-applicable}: this is a cache-side emission/deduplication guarantee; ze is the RTR router that only consumes ASPA PDUs (no ASPA PDU writer exists, only query writers) and never enforces or emits this pairing (internal/component/bgp/plugins/rpki/rtr_pdu.go:92, :103)
`DRAFT-IETF-SIDROPS-8210BIS-5.12-5`	Withdraw ASPA MUST match exact (Customer-AS, AFI) pair (§5.12)
	MUST	5.12	positive`no test`no positive test negative`no test`no negative test {not-applicable}: exact-(Customer-AS,AFI) withdraw matching binds the cache's emission and a per-AFI record model; ze consumes withdraws keyed on Customer-AS alone (the §5.12 router option to ignore AFI) and maintains no AFI dimension to match (internal/component/bgp/plugins/rpki/rtr_session.go:283, aspa_cache.go:114)
`DRAFT-IETF-SIDROPS-8210BIS-5.12-6`	Router MUST ignore ASPA PDUs with unknown AFI values (§5.12)
	MUST	5.12	positive`no test`no positive test negative`no test`no negative test
`DRAFT-IETF-SIDROPS-8210BIS-5.12-7`	Customer AS 0 is reserved, MUST NOT appear (§5.12)
	MUST NOT	5.12	positive`no test`no positive test negative`no test`no negative test
`DRAFT-IETF-SIDROPS-8210BIS-7-1`	Router starting a v2 session MUST send query with version=2 (§7)
	MUST	7	positive`no test`no positive test negative`no test`no negative test {single-polarity}: ze constructs every session at rtrVersionMax and writes that version unconditionally into the initial query, so the emitted version byte is observable but there is no malformed input that yields a wrong-version query to test negatively
`DRAFT-IETF-SIDROPS-8210BIS-7-2`	On Unsupported Protocol Version error, router MUST downgrade or disconnect (§7)
	MUST	7	positive`no test`no positive test negative`no test`no negative test
`DRAFT-IETF-SIDROPS-8210BIS-7-3`	Cache receiving a version it does not support MUST send error code 4 (§7)
	MUST	7	positive`no test`no positive test negative`no test`no negative test {not-applicable}: this binds the RTR cache/server role; ze runs only an RTR client that dials out and reads error reports, with no listener and no error-report writer, so it never receives queries or sends error code 4 (internal/component/bgp/plugins/rpki/rtr_session.go:125)
`DRAFT-IETF-SIDROPS-8210BIS-7-4`	Router SHOULD start at highest supported version (§7)
	SHOULD	7	positive`no test`no positive test negative`no test`no negative test
`DRAFT-IETF-SIDROPS-8210BIS-5.12-8`	Provider ASNs SHOULD be sorted ascending; cache MUST sort, router SHOULD verify (§5.12)
	SHOULD	5.12	positive`no test`no positive test negative`no test`no negative test
`DRAFT-IETF-SIDROPS-8210BIS-5.12-9`	Router MAY ignore AFI field and apply ASPA to all address families (§5.12)
	MAY	5.12	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

Requirement	State	Reason
`DRAFT-IETF-SIDROPS-8210BIS-5.12-1` Provider AS set in ASPA PDU MUST contain at least one provider ASN (§5.12)	no test	no test carries this requirement id
`DRAFT-IETF-SIDROPS-8210BIS-5.12-2` Customer AS MUST NOT appear in its own provider set (§5.12)	no test	no test carries this requirement id
`DRAFT-IETF-SIDROPS-8210BIS-5.12-3` Provider ASNs MUST be in ascending order within the PDU (§5.12)	no test	no test carries this requirement id
`DRAFT-IETF-SIDROPS-8210BIS-5.12-4` Cache MUST ensure one ASPA PDU per (Customer-AS, AFI) pair (§5.12)	no test	no test carries this requirement id; annotated {not-applicable}: this is a cache-side emission/deduplication guarantee; ze is the RTR router that only consumes ASPA PDUs (no ASPA PDU writer exists, only query writers) and never enforces or emits this pairing (internal/component/bgp/plugins/rpki/rtr_pdu.go:92, :103)
`DRAFT-IETF-SIDROPS-8210BIS-5.12-5` Withdraw ASPA MUST match exact (Customer-AS, AFI) pair (§5.12)	no test	no test carries this requirement id; annotated {not-applicable}: exact-(Customer-AS,AFI) withdraw matching binds the cache's emission and a per-AFI record model; ze consumes withdraws keyed on Customer-AS alone (the §5.12 router option to ignore AFI) and maintains no AFI dimension to match (internal/component/bgp/plugins/rpki/rtr_session.go:283, aspa_cache.go:114)
`DRAFT-IETF-SIDROPS-8210BIS-5.12-6` Router MUST ignore ASPA PDUs with unknown AFI values (§5.12)	no test	no test carries this requirement id
`DRAFT-IETF-SIDROPS-8210BIS-5.12-7` Customer AS 0 is reserved, MUST NOT appear (§5.12)	no test	no test carries this requirement id
`DRAFT-IETF-SIDROPS-8210BIS-7-1` Router starting a v2 session MUST send query with version=2 (§7)	no test	no test carries this requirement id; annotated {single-polarity}: ze constructs every session at rtrVersionMax and writes that version unconditionally into the initial query, so the emitted version byte is observable but there is no malformed input that yields a wrong-version query to test negatively
`DRAFT-IETF-SIDROPS-8210BIS-7-2` On Unsupported Protocol Version error, router MUST downgrade or disconnect (§7)	no test	no test carries this requirement id
`DRAFT-IETF-SIDROPS-8210BIS-7-3` Cache receiving a version it does not support MUST send error code 4 (§7)	no test	no test carries this requirement id; annotated {not-applicable}: this binds the RTR cache/server role; ze runs only an RTR client that dials out and reads error reports, with no listener and no error-report writer, so it never receives queries or sends error code 4 (internal/component/bgp/plugins/rpki/rtr_session.go:125)

Proof state

A tagged unit reads unproven where no discrimination record exists for it: nothing in this tree has been observed to break it, so the claim its tag makes is unproven.