Supported

RFC 8203 - BGP Administrative Shutdown Communication

Every requirement this repository extracted from RFC 8203, 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 ways80.0%4 of 5 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 reason20.0%1 of 5 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 5 binding obligations

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

No test at all0.0%0 of 5 binding obligations

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

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 MUSTs5of 9 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 5 gated MUSTs

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

The 4 shares marked as a part above are the whole of the 5 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	ok	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	9
Gated MUST-level	5
Obligations that bind Ze	5
Not applicable, so out of scope	0
Declared gaps	0
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/rfc8203.md`
Requirement shard	`rfc/requirements/rfc8203.md`
RFC text	`rfc/full/rfc8203.txt`

Enrolment

Enrolled: Administrative Shutdown Communication: five MUST-level requirements over the Cease NOTIFICATION shutdown message, all bound to the message codec (internal/component/bgp/message/notification.go). RFC8203-2-1 (subcode 2/4) is proven by ShutdownMessage extracting for Admin Shutdown/Reset and returning empty for any other subcode; RFC8203-2-3 (UTF-8) and RFC8203-2-4 (MUST NOT interpret invalid UTF-8) by a valid message round-tripping while an invalid sequence is rejected; RFC8203-6-1 (shortest form) by an overlong 0xC0 0xAF encoding being rejected where the canonical form is accepted (Go utf8.Valid enforces shortest form). RFC8203-2-2 (length 0-128) is {single-polarity: positive}: BuildShutdownData caps the sender at 128, while the receiver deliberately follows RFC 9003 (which obsoletes RFC 8203 and raised the cap to 255), so there is no over-128 rejection on receive to assert.

What the public ledger says

Status: Supported

What the ledger says is covered:

UTF-8 shutdown message for Cease/Admin Shutdown and Cease/Admin Reset.

What the ledger says remains:

Sender keeps the conservative 128-byte RFC 8203 limit.

Coverage

Bucket	Count	What it counts
Positive and negative tests	4	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	5	every gated MUST falls in exactly one bucket above

Positive and negative tests (4): RFC8203-2-1, RFC8203-2-3, RFC8203-6-1, RFC8203-2-4

Annotated instead of tested (1): RFC8203-2-2

Requirements

Requirement	Level	Section	Tests
`RFC8203-2-1`	Error Subcode value must be 2 ("Administrative Shutdown") or 4 ("Administrative Reset") (§2)
	MUST	2 - Shutdown Communication	positive`unit/verifyTestRFC8203Subcode` negative`unit/verifyTestRFC8203Subcode`
`RFC8203-2-2`	Length field must range from 0 to 128 inclusive (§2)
	MUST	2 - Shutdown Communication	positive`unit/verifyTestRFC8203LengthCap` negative`no test`no negative test {single-polarity}: the sender enforces the 0-128 range -- BuildShutdownData truncates a longer message to 128 at a UTF-8 boundary (internal/component/bgp/message/notification.go:312) -- but the receiver deliberately follows RFC 9003, which obsoletes RFC 8203 and raised the cap to 255 (ShutdownMessage reads a 1-byte length up to 255, notification.go:268-284), so ze intentionally does not reject a 129-255 length on receive and there is no over-128-rejected behavior to assert
`RFC8203-2-3`	Shutdown Communication field must be encoded using UTF-8 (§2)
	MUST	2 - Shutdown Communication	positive`unit/verifyTestRFC8203UTF8Valid` negative`unit/verifyTestRFC8203UTF8Invalid`
`RFC8203-6-1`	UTF-8 "Shortest Form" encoding is required (§6)
	MUST	6 - Security Considerations	positive`unit/verifyTestRFC8203ShortestFormUTF8` negative`unit/verifyTestRFC8203ShortestFormUTF8`
`RFC8203-2-4`	Receiving BGP speaker must not interpret invalid UTF-8 sequences (§2)
	MUST NOT	2 - Shutdown Communication	positive`unit/verifyTestRFC8203UTF8Invalid` negative`unit/verifyTestRFC8203UTF8Valid`
`RFC8203-2-5`	Reporting of Shutdown Communication should include methods such as Syslog (§2)
	SHOULD	2 - Shutdown Communication	positive`no test`no positive test negative`no test`no negative test
`RFC8203-4-1`	Log a message for the operator when an invalid Length value or invalid UTF-8 sequence is received (§4)
	SHOULD	4 - Error Handling	positive`no test`no positive test negative`no test`no negative test
`RFC8203-2-6`	Sender may include a UTF-8 encoded string in the Cease NOTIFICATION (§2)
	MAY	2 - Shutdown Communication	positive`no test`no positive test negative`no test`no negative test
`RFC8203-4-2`	Erroneous or malformed Shutdown Communication may be logged in hexdump format (§4)
	MAY	4 - Error Handling	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

RFC 8203 declares no gap, and every gated MUST it carries has a test bound to it.

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.