Partial

RFC 7311 - The Accumulated IGP Metric Attribute for BGP

Every requirement this repository extracted from RFC 7311, 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 ways75.0%3 of 4 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 4 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 4 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 6 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 MUSTs4of 8 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 4 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 all25.0%1 of 4 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 4 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	Partial
Enrolment	Enrolled
Requirements	8
Gated MUST-level	4
Obligations that bind Ze	4
Not applicable, so out of scope	0
Declared gaps	1
Gated with no test	0
Nightly-only evidence	0
Test tags	6
Tagged units	6
Recorded audit verdicts	0
Discrimination records	0
Summary	`rfc/short/rfc7311.md`
Requirement shard	`rfc/requirements/rfc7311.md`
RFC text	`rfc/full/rfc7311.txt`

Enrolment

Enrolled: The Accumulated IGP Metric Attribute for BGP (AIGP, code 26): four MUST-level requirements. Three over the codec (internal/core/bgp/attribute/aigp.go) are tested with both polarities in aigp_test.go: RFC7311-3-1 (type-1 TLV MUST have length 11) via TestParseAIGP (valid length-11 metric accepted) and TestParseAIGPMalformedMetricWrongLength (length 8 rejected, aigp.go:118); RFC7311-3-2 (total attribute length consistent with contained TLVs) via TestParseAIGPMultipleTLVs (two TLVs summing to the total) and TestParseAIGPMalformedTruncatedValue (declared TLV overruns the buffer -> error, aigp.go:111); RFC7311-3-3 (unknown TLV types preserved not discarded) via TestParseAIGPMultipleTLVs (unknown type-2 retained with exact data while type-1 still interpreted) and TestAIGPWriteToMultipleTLVs (unknown TLV survives the WriteTo re-encode round-trip). RFC7311-3.2-1 (MUST NOT propagate AIGP to a different-administrative-domain eBGP peer) is {gap}: Ze forwards received attributes verbatim (forward_context.go:11) with no AIGP admin-domain strip and the AIGP plugin is a stub, so received AIGP leaks to eBGP; disclosed in the docs/features/rfc-status.md RFC 7311 row (Partial). The 3-4/3.2-2/3.2-3 SHOULDs and 3.1-1 MAY are not gated.

What the public ledger says

Status: Partial

What the ledger says is covered:

AIGP wire encoding, decoding, JSON, and set/increment/decrement filters
TLV validation (type-1 length 11, total-length consistency, unknown-TLV preservation) gated per requirement in rfc/requirements/rfc7311.md.

What the ledger says remains

AIGP is not consumed by best-path selection, and Ze does not strip AIGP at the eBGP administrative-domain boundary (§3.2 MUST NOT): received AIGP is forwarded verbatim as an optional-transitive attribute, removable only by explicit operator policy. Gated as a gap in rfc/short/rfc7311.md.

Coverage

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

Positive and negative tests (3): RFC7311-3-1, RFC7311-3-2, RFC7311-3-3

Annotated instead of tested (1): RFC7311-3.2-1

Requirements

Requirement	Level	Section	Tests
`RFC7311-3-1`	AIGP TLV type 1 MUST have length 11 (3 header + 8 metric) (§3)
	MUST	3	positive`unit/verifyTestParseAIGP` negative`unit/verifyTestParseAIGPMalformedMetricWrongLength`
`RFC7311-3-2`	Total attribute length must be consistent with contained TLVs (§3)
	MUST	3	positive`unit/verifyTestParseAIGPMultipleTLVs` negative`unit/verifyTestParseAIGPMalformedTruncatedValue`
`RFC7311-3-3`	Unknown TLV types MUST be preserved and not discarded (§3)
	MUST	3	positive`unit/verifyTestParseAIGPMultipleTLVs` negative`unit/verifyTestAIGPWriteToMultipleTLVs`
`RFC7311-3.2-1`	AIGP attribute MUST NOT be attached to or propagated to a route advertised to a peer in a different administrative domain (§3.2)
	MUST NOT	3.2	positive`no test`no positive test negative`no test`no negative test {gap}: Ze does not strip the AIGP attribute at the eBGP administrative-domain boundary. AIGP is an optional-transitive attribute (internal/core/bgp/attribute/aigp.go:37) and Ze forwards received route attributes largely verbatim (internal/component/bgp/reactor/forward_context.go:11 reuses the source context with only AS_PATH/AGGREGATOR ASN-width rewrite and the eBGP local-AS prepend), with no AIGP-specific removal for a peer in a different administrative domain. The AIGP plugin is an explicit stub (internal/component/bgp/plugins/aigp/aigp.go:7-8 "Full AIGP processing will be added when the spec-aigp work is implemented"). AIGP can be removed only by an explicit operator remove-attribute policy, not automatically at the domain boundary, so a received AIGP would leak to a different-domain eBGP peer. Disclosed in docs/features/rfc-status.md
`RFC7311-3-4`	Unknown TLV types SHOULD be preserved and propagated unchanged (§3)
	SHOULD	3	positive`no test`no positive test negative`no test`no negative test
`RFC7311-3.2-2`	A BGP speaker that receives an AIGP attribute SHOULD propagate it to IBGP peers and to eBGP peers within the same administrative domain (§3.2)
	SHOULD	3.2	positive`no test`no positive test negative`no test`no negative test
`RFC7311-3.2-3`	When propagating, the accumulated metric SHOULD be updated by adding the IGP metric to the next hop (§3.2)
	SHOULD	3.2	positive`no test`no positive test negative`no test`no negative test
`RFC7311-3.1-1`	A BGP speaker MAY attach an AIGP attribute to a connected route, a route learned from an IGP, or a route already carrying AIGP (§3.1)
	MAY	3.1	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

Requirement	State	Reason
`RFC7311-3.2-1` AIGP attribute MUST NOT be attached to or propagated to a route advertised to a peer in a different administrative domain (§3.2)	{gap}, no test	Ze does not strip the AIGP attribute at the eBGP administrative-domain boundary. AIGP is an optional-transitive attribute (internal/core/bgp/attribute/aigp.go:37) and Ze forwards received route attributes largely verbatim (internal/component/bgp/reactor/forward_context.go:11 reuses the source context with only AS_PATH/AGGREGATOR ASN-width rewrite and the eBGP local-AS prepend), with no AIGP-specific removal for a peer in a different administrative domain. The AIGP plugin is an explicit stub (internal/component/bgp/plugins/aigp/aigp.go:7-8 "Full AIGP processing will be added when the spec-aigp work is implemented"). AIGP can be removed only by an explicit operator remove-attribute policy, not automatically at the domain boundary, so a received AIGP would leak to a different-domain eBGP peer. Disclosed in docs/features/rfc-status.md

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.

`RFC7311-3-1`

AIGP TLV type 1 MUST have length 11 (3 header + 8 metric) (§3)

Audit verdict: not audited: no reader has judged these tests

Polarity	Test	Kind and tier	Proof state
negative	`TestParseAIGPMalformedMetricWrongLength`	unit/verify	unproven
positive	`TestParseAIGP`	unit/verify	unproven

`RFC7311-3-2`

Total attribute length must be consistent with contained TLVs (§3)

Audit verdict: not audited: no reader has judged these tests

Polarity	Test	Kind and tier	Proof state
negative	`TestParseAIGPMalformedTruncatedValue`	unit/verify	unproven
positive	`TestParseAIGPMultipleTLVs`	unit/verify	unproven

`RFC7311-3-3`

Unknown TLV types MUST be preserved and not discarded (§3)

Audit verdict: not audited: no reader has judged these tests

Polarity	Test	Kind and tier	Proof state
negative	`TestAIGPWriteToMultipleTLVs`	unit/verify	unproven
positive	`TestParseAIGPMultipleTLVs`	unit/verify	unproven

`RFC7311-3.2-1`

AIGP attribute MUST NOT be attached to or propagated to a route advertised to a peer in a different administrative domain (§3.2)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC7311-3.2-1, so no unit is bound to it.

Extraction sign-off

No extraction sign-off exists for RFC 7311, so no reviewer has walked its text sentence by sentence.

Superseded

No document obsoletes RFC 7311, so its obligations are stated where they were written.