Supported

DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY - Software Version Capability for BGP

Every requirement this repository extracted from DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY, 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 ways0.0%0 of 11 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 reason0.0%0 of 11 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 11 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

Gated MUSTs11of 15 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 11 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 all100.0%11 of 11 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 11 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
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
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	Supported
Enrolment	Enrolled
Requirements	15
Gated MUST-level	11
Obligations that bind Ze	11
Not applicable, so out of scope	0
Declared gaps	0
Gated with no test	11
Nightly-only evidence	0
Test tags	0
Tagged units	0
Recorded audit verdicts	0
Discrimination records	0
Summary	`rfc/short/draft-abraitis-bgp-version-capability.md`
Requirement shard	`rfc/requirements/draft-abraitis-bgp-version-capability.md`
RFC text	`rfc/drafts/draft-abraitis-bgp-version-capability.txt`

Enrolment

Enrolled: Software Version capability for BGP (code 75): eleven MUST-level requirements. Send side is implemented and gated by config -- encodeValue writes one length octet plus the constant ZeVersion and extractSoftverCapabilities declares code 75 only for a peer or group whose config carries a software-version key that is not disable or refuse (internal/component/bgp/plugins/softver/softver.go), which is 3-1, 3-2, 3-3, 3-6, 3-8 and 4-2. Receive side: parseCapability (internal/core/bgp/capability/capability.go) has no case for code 75, so a received capability becomes an Unknown nothing reads, which is how 3-4, 3-5, 3-7 and 4-1 are met. 3.1-1 requires RFC 9072, which is enrolled separately and Partial. No requirement carries a tagged test yet; the coverage rollup names them.

What the public ledger says

Status: Supported

What the ledger says is covered

Send side only, and the draft makes both halves optional: "Implementations are not required to advertise the version nor to process received advertisements" (Abstract). encodeValue (internal/component/bgp/plugins/softver/softver.go) writes one length octet plus the constant ZeVersion, and extractSoftverCapabilities (same file) declares code 75 only for a peer or group whose config carries a software-version capability key that is not disable or refuse, so the default is disabled. Receive side: parseCapability (internal/core/bgp/capability/capability.go) has no case for code 75, so a received capability becomes an Unknown that nothing reads. That is the RFC 5492 Section 3 outcome the draft points at, and it is why the three receiver obligations are met by ignoring rather than by parsing. ze bgp decode capability 75 <hex> decodes a payload an operator supplies
that path is a diagnostic tool and is not on the session receive path. Carried in this table as draft-ietf-idr-software-version until 2026-09-01. No IETF document of that name exists: the datatracker knows only draft-abraitis-bgp-version-capability, revision 18, "Software Version Capability for BGP", which IANA names as the reference for code 75. docs/architecture/wire/capabilities.md had always spelled the real one.

What the ledger says remains:

Coverage

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

Requirements

Requirement	Level	Section	Tests
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-1`	"If an implementation supports the inclusion of the capability, the implementation MUST include a configuration option to enable or disable its use, and MUST default to disabled" -- the configuration option half (§3)
	MUST	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-2`	"If an implementation supports the inclusion of the capability, the implementation MUST include a configuration option to enable or disable its use, and MUST default to disabled" -- the default-to-disabled half (§3)
	MUST	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-3`	"The Capability Length for the Software Version Capability MUST be greater than zero" (§3)
	MUST	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-4`	"A value of zero SHALL be treated as an encoding error and the Capability MUST be ignored" -- the encoding-error half (§3)
	SHALL	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-5`	"A value of zero SHALL be treated as an encoding error and the Capability MUST be ignored" -- the ignore half (§3)
	MUST	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-6`	"The Version field MUST be encoded using UTF-8" (§3)
	MUST	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-7`	"A receiving BGP speaker MUST NOT interpret invalid UTF-8 sequences" (§3)
	MUST NOT	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-8`	"A sender SHOULD limit generated product identifiers to what is necessary to identify the product; a sender MUST NOT generate advertising or other nonessential information within the product identifier" -- the MUST NOT half (§3)
	MUST NOT	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-9`	"The Capability Length SHOULD be no greater than 64" (§3)
	SHOULD	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-10`	"A sender SHOULD limit generated product identifiers to what is necessary to identify the product" (§3)
	SHOULD	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-11`	"A sender SHOULD NOT generate information in product-version that is not a version identifier" (§3)
	SHOULD NOT	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-12`	"It is NOT RECOMMENDED for use outside a single Autonomous System, or a set of Autonomous Systems under a common administration" (§3)
	NOT RECOMMENDED	3 - Software Version Capability	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3.1-1`	"Implementations of this specification are REQUIRED Extended Optional Parameters Length for BGP OPEN Message support as defined in [RFC9072]" (§3.1)
	REQUIRED	3.1 - Capabilities Length Overflow	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-4-1`	"The Software Version Capability MUST only be used for displaying the version of a BGP speaker's router daemon to make troubleshooting easier" (§4)
	MUST	4 - Operation	positive`no test`no positive test negative`no test`no negative test
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-4-2`	"Enabling (i.e., turning on) this capability requires bouncing all existing BGP sessions and the feature MUST be explicitly configured before an implementation advertizes the Software Version Capability" (§4)
	MUST	4 - Operation	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

Requirement	State	Reason
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-1` "If an implementation supports the inclusion of the capability, the implementation MUST include a configuration option to enable or disable its use, and MUST default to disabled" -- the configuration option half (§3)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-2` "If an implementation supports the inclusion of the capability, the implementation MUST include a configuration option to enable or disable its use, and MUST default to disabled" -- the default-to-disabled half (§3)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-3` "The Capability Length for the Software Version Capability MUST be greater than zero" (§3)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-4` "A value of zero SHALL be treated as an encoding error and the Capability MUST be ignored" -- the encoding-error half (§3)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-5` "A value of zero SHALL be treated as an encoding error and the Capability MUST be ignored" -- the ignore half (§3)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-6` "The Version field MUST be encoded using UTF-8" (§3)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-7` "A receiving BGP speaker MUST NOT interpret invalid UTF-8 sequences" (§3)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-8` "A sender SHOULD limit generated product identifiers to what is necessary to identify the product; a sender MUST NOT generate advertising or other nonessential information within the product identifier" -- the MUST NOT half (§3)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3.1-1` "Implementations of this specification are REQUIRED Extended Optional Parameters Length for BGP OPEN Message support as defined in [RFC9072]" (§3.1)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-4-1` "The Software Version Capability MUST only be used for displaying the version of a BGP speaker's router daemon to make troubleshooting easier" (§4)	no test	no test carries this requirement id
`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-4-2` "Enabling (i.e., turning on) this capability requires bouncing all existing BGP sessions and the feature MUST be explicitly configured before an implementation advertizes the Software Version Capability" (§4)	no test	no test carries this requirement id

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.

`DRAFT-ABRAITIS-BGP-VERSION-CAPABILITY-3-1`

"If an implementation supports the inclusion of the capability, the implementation MUST include a configuration option to enable or disable its use, and MUST default to disabled" -- the configuration option half (§3)