Supported

RFC 7313 - Enhanced Route Refresh Capability for BGP-4

Every requirement this repository extracted from RFC 7313, 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 ways30.0%3 of 10 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 reason30.0%3 of 10 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 10 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 23 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 MUSTs10of 16 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 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 all40.0%4 of 10 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 10 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	16
Gated MUST-level	10
Obligations that bind Ze	10
Not applicable, so out of scope	0
Declared gaps	4
Gated with no test	0
Nightly-only evidence	0
Test tags	23
Tagged units	23
Recorded audit verdicts	0
Discrimination records	0
Summary	`rfc/short/rfc7313.md`
Requirement shard	`rfc/requirements/rfc7313.md`
RFC text	`rfc/full/rfc7313.txt`

Enrolment

Enrolled: Enhanced Route Refresh Capability for BGP-4: ten MUST-level requirements. Six are met in internal/component/bgp: 4-3 (the ROUTE-REFRESH Message Subtype selects normal/BoRR/EoRR handling), 5-1 (an invalid-length ROUTE-REFRESH is a NOTIFICATION Route-Refresh Error), and 5-3 (an unknown Message Subtype is ignored and the session stays Established) carry positive+negative tags; 4-1 (send a BoRR before re-advertising), 4-2 (send an EoRR after re-advertising), and 5-2 (the NOTIFICATION data carries the complete ROUTE-REFRESH message) are {single-polarity: positive}. Four are {gap}: 4-4 and 4-5 (a received BoRR/EoRR is log-only, so ze marks no Adj-RIB-In routes stale and purges none) and 4-6 and 4-7 (no Graceful-Restart End-of-RIB gate on BoRR emission or acceptance). Disclosed in the docs/features/rfc-status.md RFC 7313 row.

What the public ledger says

Status: Supported

What the ledger says is covered:

BoRR and EoRR support, capability checks, bounded route resend.

What the ledger says remains

Four MUST-level receive-side gaps annotated in rfc/short/rfc7313.md: RFC7313-4-4/4-5 -- a received BoRR/EoRR is log-only (internal/component/bgp/plugins/rib/rib.go), so ze marks no Adj-RIB-In routes stale and purges none; and RFC7313-4-6/4-7 -- neither the send nor receive path applies a Graceful-Restart End-of-RIB gate to BoRR emission or acceptance.

Coverage

Bucket	Count	What it counts
Positive and negative tests	3	one part of the gated population
Annotated instead of tested	7	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	10	every gated MUST falls in exactly one bucket above

Positive and negative tests (3): RFC7313-4-3, RFC7313-5-1, RFC7313-5-3

Annotated instead of tested (7): RFC7313-4-1, RFC7313-4-2, RFC7313-4-4, RFC7313-4-5, RFC7313-5-2, RFC7313-4-6, RFC7313-4-7

Requirements

Requirement	Level	Section	Tests
`RFC7313-4-1`	Before starting a route refresh (locally initiated or in response to a normal route refresh request), the speaker MUST send a BoRR message (§4)
	MUST	4 - Operation	positive`unit/verifyTestDispatchBGPPeerBoRR` positive`unit/verifyTestRFC7313RefreshBracketsReadvertisementWithBoRRAndEoRR` positive`unit/verifyTestRouteRefreshSubtypes` negative`no test`no negative test {single-polarity}: ze dispatches the BoRR before sendRoutes in one straight-line path (internal/component/bgp/plugins/rib/rib.go:1013-1014); there is no re-advertise-without-BoRR code path to drive a negative
`RFC7313-4-2`	After completing the re-advertisement of the entire Adj-RIB-Out to the peer, the speaker MUST send an EoRR message (§4)
	MUST	4 - Operation	positive`unit/verifyTestDispatchBGPPeerEoRR` positive`unit/verifyTestRFC7313RefreshBracketsReadvertisementWithBoRRAndEoRR` positive`unit/verifyTestRouteRefreshSubtypes` negative`no test`no negative test {single-polarity}: ze dispatches the EoRR after sendRoutes in one straight-line path (internal/component/bgp/plugins/rib/rib.go:1014-1015); there is no re-advertise-without-EoRR code path to drive a negative
`RFC7313-4-3`	In processing a ROUTE-REFRESH message, the BGP speaker MUST examine the "message subtype" field and take appropriate actions (§4)
	MUST	4 - Operation	positive`unit/verifyTestHandleRouteRefreshBoRR` positive`unit/verifyTestHandleRouteRefreshEoRR` negative`unit/verifyTestHandleRouteRefreshUnknown` negative`unit/verifyTestHandleRouteRefresh_UnknownSubtype`
`RFC7313-4-4`	When a BGP speaker receives a BoRR, it MUST mark all routes with that <AFI, SAFI> from that peer as stale (§4)
	MUST	4 - Operation	positive`no test`no positive test negative`no test`no negative test {gap}: ze logs a received BoRR but does not mark the peer's Adj-RIB-In routes stale -- internal/component/bgp/plugins/rib/rib.go:751-753 handles a received BoRR as log-only and rib_structured.go:506 returns early for a non-zero subtype, so no stale-marking occurs
`RFC7313-4-5`	When a BGP speaker receives an EoRR, it MUST immediately remove any routes still marked as stale for that <AFI, SAFI> (§4)
	MUST	4 - Operation	positive`no test`no positive test negative`no test`no negative test {gap}: ze logs a received EoRR but performs no stale-route removal -- internal/component/bgp/plugins/rib/rib.go:754-756 handles it as log-only, and because no BoRR stale-marking exists (RFC7313-4-4) there is nothing to purge
`RFC7313-5-1`	If the length (excluding fixed header) of a BoRR/EoRR message is not 4, send NOTIFICATION with Error Code 7, subcode 1 (§5)
	MUST	5 - Error Handling	positive`unit/verifyTestRouteRefreshBadLengthByMessageSubtype` positive`unit/verifyTestRouteRefreshInvalidLengthNotDelivered` negative`unit/verifyTestRouteRefreshBadLengthByMessageSubtype` negative`unit/verifyTestRouteRefreshBadLengthWithoutCapability70` negative`unit/verifyTestRouteRefreshUnknownSubtypeIsIgnoredWhateverItsLength` negative`unit/verifyTestRouteRefreshValidLengthDelivered` negative`unit/verifyTestRouteRefreshWellFormedWithoutCapability70DrawsNoNotification`
`RFC7313-5-2`	The Data field of the NOTIFICATION message MUST contain the complete ROUTE-REFRESH message (§5)
	MUST	5 - Error Handling	positive`unit/verifyTestRouteRefreshBadLengthByMessageSubtype` positive`unit/verifyTestRouteRefreshInvalidLengthNotDelivered` negative`no test`no negative test {single-polarity}: routeRefreshNotificationData (internal/component/bgp/reactor/session_handlers.go) always copies the entire received body after the header, so every ROUTE-REFRESH NOTIFICATION carries the complete message; there is no truncating code path to drive a negative
`RFC7313-5-3`	When receiving a ROUTE-REFRESH with subtype other than 0, 1, or 2, the speaker MUST ignore the message (§5)
	MUST	5 - Error Handling	positive`unit/verifyTestHandleRouteRefreshReserved` positive`unit/verifyTestHandleRouteRefreshUnknown` positive`unit/verifyTestRouteRefreshUnknownSubtypeIsIgnoredWhateverItsLength` negative`unit/verifyTestHandleRouteRefreshBoRR`
`RFC7313-4-6`	A BGP speaker supporting Graceful Restart MUST NOT send a BoRR for an <AFI, SAFI> before sending the EoR for that <AFI, SAFI> (§4)
	MUST NOT	4 - Operation	positive`no test`no positive test negative`no test`no negative test {gap}: ze's sendRouteRefresh (internal/component/bgp/reactor/reactor_api_forward.go:112) applies no Graceful-Restart End-of-RIB gate, and rib.go:1008-1013 emits the BoRR without checking End-of-RIB state, so the GR/EoR interaction is not enforced
`RFC7313-4-7`	A BGP speaker that has received Graceful Restart Capability MUST ignore any BoRRs for an <AFI, SAFI> before receiving the EoR for that <AFI, SAFI> from the neighbor (§4)
	MUST	4 - Operation	positive`no test`no positive test negative`no test`no negative test {gap}: the received-BoRR path is log-only (internal/component/bgp/plugins/rib/rib.go:751-753) with no Graceful-Restart End-of-RIB gating, and it depends on the unimplemented stale-marking of RFC7313-4-4
`RFC7313-4-8`	A BGP speaker supporting message subtypes and related procedures SHOULD advertise the Enhanced Route Refresh Capability (§4)
	SHOULD	4 - Operation	positive`no test`no positive test negative`no test`no negative test
`RFC7313-5-4`	When receiving unknown subtype, the speaker SHOULD log an error for further analysis (§5)
	SHOULD	5 - Error Handling	positive`no test`no positive test negative`no test`no negative test
`RFC7313-4-9`	When ignoring BoRR before EoR (Graceful Restart), the speaker SHOULD log an error of the condition (§4)
	SHOULD	4 - Operation	positive`no test`no positive test negative`no test`no negative test
`RFC7313-4-10`	A BGP speaker MAY ignore any EoRR received without a prior receipt of an associated BoRR (§4)
	MAY	4 - Operation	positive`no test`no positive test negative`no test`no negative test
`RFC7313-4-11`	Purged stale routes MAY be logged for future analysis (§4)
	MAY	4 - Operation	positive`no test`no positive test negative`no test`no negative test
`RFC7313-4-12`	An implementation MAY impose a locally configurable upper bound on how long it retains stale routes (§4)
	MAY	4 - Operation	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

Requirement	State	Reason
`RFC7313-4-4` When a BGP speaker receives a BoRR, it MUST mark all routes with that <AFI, SAFI> from that peer as stale (§4)	{gap}, no test	ze logs a received BoRR but does not mark the peer's Adj-RIB-In routes stale -- internal/component/bgp/plugins/rib/rib.go:751-753 handles a received BoRR as log-only and rib_structured.go:506 returns early for a non-zero subtype, so no stale-marking occurs
`RFC7313-4-5` When a BGP speaker receives an EoRR, it MUST immediately remove any routes still marked as stale for that <AFI, SAFI> (§4)	{gap}, no test	ze logs a received EoRR but performs no stale-route removal -- internal/component/bgp/plugins/rib/rib.go:754-756 handles it as log-only, and because no BoRR stale-marking exists (RFC7313-4-4) there is nothing to purge
`RFC7313-4-6` A BGP speaker supporting Graceful Restart MUST NOT send a BoRR for an <AFI, SAFI> before sending the EoR for that <AFI, SAFI> (§4)	{gap}, no test	ze's sendRouteRefresh (internal/component/bgp/reactor/reactor_api_forward.go:112) applies no Graceful-Restart End-of-RIB gate, and rib.go:1008-1013 emits the BoRR without checking End-of-RIB state, so the GR/EoR interaction is not enforced
`RFC7313-4-7` A BGP speaker that has received Graceful Restart Capability MUST ignore any BoRRs for an <AFI, SAFI> before receiving the EoR for that <AFI, SAFI> from the neighbor (§4)	{gap}, no test	the received-BoRR path is log-only (internal/component/bgp/plugins/rib/rib.go:751-753) with no Graceful-Restart End-of-RIB gating, and it depends on the unimplemented stale-marking of RFC7313-4-4

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.

`RFC7313-4-1`

Before starting a route refresh (locally initiated or in response to a normal route refresh request), the speaker MUST send a BoRR message (§4)