Partial

RFC 8050 - Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Path Extensions

Every requirement this repository extracted from RFC 8050, the tests bound to it, and what a reader has verified about them. This summary is enrolled and gated by ./le rfc check.

Overview

Positive

what Ze has

Tested both ways66.7%4 of 6 gated MUSTs

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

One polarity plus reason16.7%1 of 6 gated MUSTs

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 6 gated MUSTs

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

Proven by a recorded break0.0%0 of 9 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

Gated MUSTs6of 7 this summary declares

MUST-level requirements the gate HOLDS. A population, not a result: the shares beside it are what says how Ze stands

Out of scope0of 6 gated MUSTs

an obligation that does not bind Ze. A {not-applicable} annotation says it never bound; a {feature-declined} annotation says its condition is an optional feature Ze does not offer, and quotes the RFC sentence that makes it optional. Scope, not coverage: it stays in the denominator every share on this page is taken over

Not applicable0.0%0 of 6 gated MUSTs

a {not-applicable} annotation says the obligation does not bind Ze, so no test is owed for it. It stays in the denominator every share here is taken over

Met below Ze0.0%0 of 6 gated MUSTs

a {lower-layer} annotation says a layer under Ze performs the behavior, on state Ze installs into that layer, and names the producer that installs it. The obligation binds Ze and is met; Ze proves none of it, because its own boundary carries no value the behavior reads

Optional feature declined0.0%0 of 6 gated MUSTs

a {feature-declined} annotation says the obligation is conditional on a feature the RFC makes optional and Ze does not offer, and it quotes the sentence that makes it optional. The condition is false, so nothing is owed and nothing is missing. It stays in the denominator every share here is taken over

Negative

what Ze owes

No test at all16.7%1 of 6 gated MUSTs

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

The 7 shares marked as a part above are the whole of the 6 gated MUSTs: 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
Gated MUSTs	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
Not applicable	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
Met below Ze	neutral	no color: an obligation met below Ze is neither a test Ze wrote nor work Ze owes, and the two green shares above are what says how much Ze proves itself
Optional feature declined	neutral	no color: an obligation whose condition Ze never meets is neither an achievement nor a failure. The absent FEATURE is disclosed on the RFC's own status row, as an implementation gap a later scope decision can revisit
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	Partial
Enrolment	Enrolled
Requirements	7
Gated MUST-level	6
Not applicable, so out of scope	0
Declared gaps	1
Gated with no test	0
Nightly-only evidence	0
Test tags	9
Tagged units	9
Recorded audit verdicts	0
Discrimination records	0
Summary	`rfc/short/rfc8050.md`
Requirement shard	`rfc/requirements/rfc8050.md`
RFC text	`rfc/full/rfc8050.txt`

Enrolment

Enrolled: MRT Routing Information Export Format with BGP Additional Path Extensions: six MUST-level requirements. Five are met with test tags in internal/mrt: 4.1-1 (the RIB add-path subtype places the 4-octet Path Identifier between Originated Time and Attribute Length), 4.2-1 (RIB_GENERIC add-path keeps the Path Identifier in the NLRI blob), x-3 (BGP4MP add-path preserves the Path Identifier inside the encapsulated message), and x-4 (add-path is distinguished purely by MRT subtype with no capability lookup) carry positive+negative tags; x-2 (the Path Identifier is big-endian) is {single-polarity: positive}. x-1 (the emitted subtype reflects whether add-path is in use) is {gap}: ze selects the subtype from a static operator config toggle rather than each peer's negotiated RFC 7911 capability. Disclosed in the docs/features/rfc-status.md RFC 8050 row.

What the public ledger says

Status: Partial

What the ledger says is covered

Add-path MRT subtypes: TABLE_DUMP_V2 RIB_*_ADDPATH (8-11) carry a 4-byte big-endian Path Identifier between Originated Time and Attribute Length
RIB_GENERIC_ADDPATH (12) keeps the Path Identifier in the raw NLRI blob and does not redefine the RIB Entry
BGP4MP add-path subtypes (8-11) preserve the Path Identifier inside the encapsulated message's NLRI
add-path is distinguished purely by MRT subtype. Tests bound per requirement in rfc/requirements/rfc8050.md.

What the ledger says remains

One MUST gap, gated in rfc/short/rfc8050.md: ze selects the MRT add-path subtype from a static operator config toggle (internal/plugins/mrt/dump.go ribSubtype/bgp4mpTypeSubtype, config.go AddPath) rather than from each peer's negotiated RFC 7911 Add-Path capability (internal/plugins/mrt/component.go OnBGPMessage does not consult it), so a single dump cannot represent a mix of add-path and non-add-path peers.

Coverage

Bucket	Count	What it counts
Positive and negative tests	4	one part of the gated population
Annotated instead of tested	2	one part of the gated population
One polarity only	0	one part of the gated population
No test and no annotation	0	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	6	every gated MUST falls in exactly one bucket above

Positive and negative tests (4): RFC8050-4.1-1, RFC8050-4.2-1, RFC8050-x-3, RFC8050-x-4

Annotated instead of tested (2): RFC8050-x-1, RFC8050-x-2

Requirements

Requirement	Level	Section	Tests
`RFC8050-x-1`	A collector that receives add-path BGP sessions must use the add-path subtypes (BGP4MP_MESSAGE_ADDPATH, etc.) when writing MRT records (Compatibility)
	MUST	x	positive`no test`no positive test negative`no test`no negative test {gap}: ze selects the MRT add-path subtype from a static operator config toggle (internal/plugins/mrt/dump.go:206-250, config.go:19) rather than from each peer's negotiated RFC 7911 Add-Path capability (component.go:113 does not consult it), so a single dump cannot represent a mix of add-path and non-add-path peers
`RFC8050-4.1-1`	For AFI/SAFI-specific RIB subtypes (8-11), the RIB Entry must include a 4-byte Path Identifier between Originated Time and Attribute Length (Section 4.1)
	MUST	4.1	positive`unit/verifyTestRIBRecordAddPathRoundTrip` negative`unit/verifyTestRIBRecordRoundTrip`
`RFC8050-4.2-1`	For RIB_GENERIC_ADDPATH (subtype 12), RIB Entries must not be redefined; the Path Identifier is in the raw NLRI blob, not in the RIB Entry (Section 4.2)
	MUST	4.2	positive`unit/verifyTestRIBGenericAddPathRoundTrip` negative`unit/verifyTestRIBGenericRoundTrip`
`RFC8050-x-2`	Path Identifier must be 4 bytes in network byte order, per RFC 7911 (Encoding Rules)
	MUST	x	positive`unit/verifyTestRIBRecordAddPathRoundTrip` negative`no test`no negative test {single-polarity}: the Path ID is written and read big-endian (internal/mrt/encode.go:107, decode.go:295); there is no alternate-endianness path
`RFC8050-x-3`	For BGP4MP add-path subtypes, the Path Identifier is inside the encapsulated BGP message's NLRI, not in the MRT header (Encoding Rules)
	MUST	x	positive`unit/verifyTestBGP4MPMessageRoundTrip` negative`unit/verifyTestBGP4MPStateChangeRoundTrip`
`RFC8050-x-4`	The subtype alone determines whether add-path encoding is present; no capability negotiation or flag bits (Decoding Rules)
	MUST	x	positive`unit/verifyTestIsAddPathHelpers` negative`unit/verifyTestIsAddPathHelpers`
`RFC8050-x-5`	Non-add-path-aware MRT parsers should skip records with unknown subtype codes per normal MRT parsing (Compatibility)
	SHOULD	x	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

Requirement	State	Reason
`RFC8050-x-1` A collector that receives add-path BGP sessions must use the add-path subtypes (BGP4MP_MESSAGE_ADDPATH, etc.) when writing MRT records (Compatibility)	{gap}, no test	ze selects the MRT add-path subtype from a static operator config toggle (internal/plugins/mrt/dump.go:206-250, config.go:19) rather than from each peer's negotiated RFC 7911 Add-Path capability (component.go:113 does not consult it), so a single dump cannot represent a mix of add-path and non-add-path peers

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.

`RFC8050-x-1`

A collector that receives add-path BGP sessions must use the add-path subtypes (BGP4MP_MESSAGE_ADDPATH, etc.) when writing MRT records (Compatibility)