Partial

RFC 9085 - Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing

Every requirement this repository extracted from RFC 9085, 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 ways100.0%9 of 9 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 reason0.0%0 of 9 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 9 gated MUSTs

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

Partial proof; remaining gap0.0%0 of 9 gated MUSTs

scoped tests exist; the remaining obligation is unmet or unproven, with zero whole-requirement credit

No test at all0.0%0 of 9 gated MUSTs

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

Proven by a recorded break98.2%56 of 57 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

Audit verdicts12of 9 gated MUSTs judged

0 weak, wrong or unimplemented, 0 no longer current. Each is named below under its own requirement id

Neutral

measures that are neither good news nor bad

Gated MUSTs9of 14 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 9 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 9 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 9 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 9 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

The 8 shares marked as a part above are the whole of the 9 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
Partial proof; remaining gap	ok	green at zero, RED above it: a tested clause cannot prove the whole requirement
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
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	ok	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	14
Gated MUST-level	9
Not applicable, so out of scope	0
Declared gaps	0
Declared gaps a test demonstrates	0
Gated with no test	0
Nightly-only evidence	0
Test tags	57
Tagged units	57
Recorded audit verdicts	12
Discrimination records	56
Summary	`rfc/short/rfc9085.md`
Requirement shard	`rfc/requirements/rfc9085.md`
RFC text	`rfc/full/rfc9085.txt`

Enrolment

Enrolled: BGP-LS Segment Routing extensions: Ze decodes the SR TLVs and originates them from its IS-IS and OSPF link-state databases. Correction 2026-09-30: the eight transmit rows were recorded as gaps on the belief that no path originated them; the native IS-IS and OSPF BGP-LS exporters do, so those rows now carry origination tests. The 2026-09-21 extraction walk lowered RFC9085-2.1-1 to SHOULD, the level the document's own sentence uses, and on 2026-09-30 the duplicate rows RFC9085-2.1.2-3 and 2.1.2-4 were merged into RFC9085-2.1.2-2 and 2.1.2-1, so the MUST count is 9 rather than 12.

What the public ledger says

Status: Partial

What the ledger says is covered

SR TLVs (SID/Label, Prefix-SID, Adj-SID, SR Capabilities, SRGB/SRLB) decode as part of BGP-LS TLV coverage
the SID/Label 20-bit mask and reserved/undefined-flag fields are ignored on receipt. The native IS-IS and OSPF BGP-LS exporters originate SR Capabilities (1034), SR-Algorithm (1035), SRLB (1036), Adjacency SID (1099), LAN Adjacency SID (1100), Prefix-SID (1158) and Range (1159) with the SID/Label 20-bit mask applied and the Reserved fields, and the OSPF SR Capabilities and SRLB Flags, set to 0.

What the ledger says remains:

The offline consumer decoder does not decode the LAN Adjacency SID (TLV 1100) or Range (TLV 1159) TLVs; it carries them unparsed, Reserved field included.

Coverage

Bucket	Count	What it counts
Positive and negative tests	9	one part of the gated population
Annotated (including scoped evidence)	0	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
Partial proof; remaining gap (subset of annotated; zero whole-requirement credit)	0	an overlay: each of these is also counted by the part it falls in
Evidence that runs nightly only	0	an overlay: each of these is also counted by the part it falls in
Derived from other rows	0	outside the gated population: each asserts nothing and derives its state from the rows it names, which the parts above already count
Gated MUST-level requirements	9	every gated MUST falls in exactly one bucket above

Positive and negative tests (9): RFC9085-2.1.2-1, RFC9085-2.1.2-2, RFC9085-2.1.4-1, RFC9085-2.1.4-2, RFC9085-2.2.1-1, RFC9085-2.2.2-1, RFC9085-2.3.1-1, RFC9085-2.3.5-1, RFC9085-2.1.1-1

Requirements

Requirement	Level	Section	Tests
`RFC9085-2.1.2-1`	The flags are not currently defined for OSPFv2 and OSPFv3 and MUST be set to 0 and ignored on receipt. (§2.1.2)
	MUST	2.1.2	positive`unit/verifyTestRFC9085CapabilitiesReceiptIgnoresFlagsAndReserved` positive`unit/verifyTestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero` positive`unit/verifyTestRFC9085SRCapabilitiesIgnoresReservedAndUndefinedFlags` negative`unit/verifyTestRFC9085OSPFSourceReservedNeverOriginated`
`RFC9085-2.1.2-2`	Reserved: 1 octet that MUST be set to 0 and ignored on receipt. (§2.1.2)
	MUST	2.1.2	positive`unit/verifyTestRFC9085CapabilitiesReceiptIgnoresFlagsAndReserved` positive`unit/verifyTestRFC9085ISISOriginatedCapabilitiesReservedZero` positive`unit/verifyTestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero` positive`unit/verifyTestRFC9085SRCapabilitiesIgnoresReservedAndUndefinedFlags` negative`unit/verifyTestRFC9085ISISAllOnesSourceNeverReachesReserved` negative`unit/verifyTestRFC9085OSPFSourceReservedNeverOriginated`
`RFC9085-2.1.4-1`	The flags are not currently defined for OSPFv2 and OSPFv3 and MUST be set to 0 and ignored on receipt. (§2.1.4)
	MUST	2.1.4	positive`unit/verifyTestRFC9085CapabilitiesReceiptIgnoresFlagsAndReserved` positive`unit/verifyTestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero` negative`unit/verifyTestRFC9085OSPFSourceReservedNeverOriginated`
`RFC9085-2.1.4-2`	Reserved: 1 octet that MUST be set to 0 and ignored on receipt. (§2.1.4)
	MUST	2.1.4	positive`unit/verifyTestRFC9085CapabilitiesReceiptIgnoresFlagsAndReserved` positive`unit/verifyTestRFC9085ISISOriginatedCapabilitiesReservedZero` positive`unit/verifyTestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero` negative`unit/verifyTestRFC9085ISISAllOnesSourceNeverReachesReserved` negative`unit/verifyTestRFC9085OSPFSourceReservedNeverOriginated`
`RFC9085-2.2.1-1`	Reserved: 2 octets that MUST be set to 0 and ignored on receipt. (§2.2.1)
	MUST	2.2.1	positive`unit/verifyTestRFC9085ISISOriginatedSIDReservedZero` positive`unit/verifyTestRFC9085OSPFOriginatedSIDReservedZero` positive`unit/verifyTestRFC9085SIDReceiptIgnoresReserved` negative`unit/verifyTestRFC9085ISISAllOnesSourceNeverReachesSIDReserved` negative`unit/verifyTestRFC9085OSPFSourceReservedNeverReachesSIDReserved`
`RFC9085-2.2.2-1`	Reserved: 2 octets that MUST be set to 0 and ignored on receipt. (§2.2.2)
	MUST	2.2.2	positive`unit/verifyTestRFC9085ISISOriginatedSIDReservedZero` positive`unit/verifyTestRFC9085OSPFOriginatedSIDReservedZero` positive`unit/verifyTestRFC9085UndecodedSIDReceiptKeepsReserved` negative`unit/verifyTestRFC9085ISISAllOnesSourceNeverReachesSIDReserved` negative`unit/verifyTestRFC9085OSPFSourceReservedNeverReachesSIDReserved`
`RFC9085-2.3.1-1`	Reserved: 2 octets that MUST be set to 0 and ignored on receipt. (§2.3.1)
	MUST	2.3.1	positive`unit/verifyTestRFC9085ISISOriginatedSIDReservedZero` positive`unit/verifyTestRFC9085OSPFOriginatedSIDReservedZero` positive`unit/verifyTestRFC9085SIDReceiptIgnoresReserved` negative`unit/verifyTestRFC9085ISISAllOnesSourceNeverReachesSIDReserved` negative`unit/verifyTestRFC9085OSPFSourceReservedNeverReachesSIDReserved`
`RFC9085-2.3.5-1`	Reserved: 1 octet that MUST be set to 0 and ignored on receipt. (§2.3.5)
	MUST	2.3.5	positive`unit/verifyTestRFC9085ISISOriginatedSIDReservedZero` positive`unit/verifyTestRFC9085OSPFOriginatedSIDReservedZero` positive`unit/verifyTestRFC9085UndecodedSIDReceiptKeepsReserved` negative`unit/verifyTestRFC9085ISISAllOnesSourceNeverReachesSIDReserved` negative`unit/verifyTestRFC9085OSPFSourceReservedNeverReachesSIDReserved`
`RFC9085-2.1.1-1`	SID/Label: If the length is set to 3, then the 20 rightmost bits represent a label (the total TLV size is 7), and the 4 leftmost bits are set to 0. (§2.1.1)
	MUST	2.1.1	positive`unit/verifyTestRFC9085OriginatedSRGBLabelTwentyBits` positive`unit/verifyTestRFC9085SIDLabelMasksLeftmostFourBits` negative`unit/verifyTestRFC9085OriginatedSRGBLabelHighBitsCleared`
`RFC9085-2.1-1`	These TLVs should only be added to the BGP-LS Attribute associated with the Node NLRI that describes the IGP node that is originating the corresponding IGP TLV/sub-TLV described below. (§2.1)
	SHOULD	2.1	positive`unit/verifyTestRFC9085ISISCapabilitiesOnOriginatorNode` positive`unit/verifyTestRFC9085OSPFCapabilitiesOnOriginatorNode` negative`unit/verifyTestRFC9085ISISCapabilitiesOnNoOtherNLRI` negative`unit/verifyTestRFC9085OSPFCapabilitiesOnNoOtherNLRI`
`RFC9085-2.2-1`	These TLVs should only be added to the BGP-LS Attribute associated with the Link NLRI that describes the link of the IGP node that is originating the corresponding IGP TLV/sub-TLV described below. (§2.2)
	SHOULD	2.2	positive`unit/verifyTestRFC9085ISISLinkPlacement` positive`unit/verifyTestRFC9085NativeExportAttributePlacement` positive`unit/verifyTestRFC9085OSPFLinkPlacement` negative`unit/verifyTestRFC9085ISISLinkPlacement` negative`unit/verifyTestRFC9085NativeExportAttributePlacement` negative`unit/verifyTestRFC9085OSPFLinkPlacement`
`RFC9085-2.3-1`	These TLVs should only be added to the BGP-LS Attribute associated with the Prefix NLRI that describes the prefix of the IGP node that is originating the corresponding IGP TLV/sub-TLV described below. (§2.3)
	SHOULD	2.3	positive`unit/verifyTestRFC9085ISISPrefixPlacement` positive`unit/verifyTestRFC9085NativeExportAttributePlacement` positive`unit/verifyTestRFC9085OSPFPrefixPlacement` negative`unit/verifyTestRFC9085ISISPrefixPlacement` negative`unit/verifyTestRFC9085NativeExportAttributePlacement` negative`unit/verifyTestRFC9085OSPFPrefixPlacement`
`RFC9085-2.2.3-1`	The TLV MAY include sub-TLVs that describe attributes associated with the bundle member. (§2.2.3)
	MAY	2.2.3	positive`no test`no positive test negative`no test`no negative test
`RFC9085-2.2.3-2`	Multiple L2 Bundle Member Attributes TLVs MAY be associated with a Link NLRI (S2.2.3)
	MAY	2.2.3	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

RFC 9085 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.

`RFC9085-2.1.2-1`

The flags are not currently defined for OSPFv2 and OSPFv3 and MUST be set to 0 and ignored on receipt. (§2.1.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. D2 rejudge 2026-10-16 (independent judge, BGP-LS codec moved to internal/core/bgp/nlri/bgpls). Tagged units changed only by the package move: identifiers re-qualified with bgpls., comments re-pointed; producer bodies byte-identical modulo the writeTLV->WriteTLV and field-export renames (TLV code constants verified unchanged). The receipt units now reach bgpls.DecodeSRCapabilities through the TLV 1034 decoder the plugin registers (lookupLsAttrTLVDecoder), so the adapter is exercised too; DecodeSRCapabilities is byte-identical to the old decodeSRCapabilities (len<2 refused, Flags stored, ranges from data[2:]). RFC 9085 Section 2.1.2: "The flags are not currently defined for OSPFv2 and OSPFv3 and MUST be set to 0 and ignored on receipt." Set-0: ospf TestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero / TestRFC9085OSPFSourceReservedNeverOriginated (unchanged). Ignored: Flags ff and 0x82 accepted, range 1000@16000 intact, I flag intact; single-polarity by nature on receipt.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085OSPFSourceReservedNeverOriginated`	unit/verify	revert, verified
positive	`TestRFC9085SRCapabilitiesIgnoresReservedAndUndefinedFlags`	unit/verify	revert, verified
positive	`TestRFC9085CapabilitiesReceiptIgnoresFlagsAndReserved`	unit/verify	revert, verified
positive	`TestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero`	unit/verify	revert, verified

`RFC9085-2.1.2-2`

Reserved: 1 octet that MUST be set to 0 and ignored on receipt. (§2.1.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. D2 rejudge 2026-10-16 (independent judge, BGP-LS codec moved to internal/core/bgp/nlri/bgpls). Tagged units changed only by the package move: identifiers re-qualified with bgpls., comments re-pointed; producer bodies byte-identical modulo the writeTLV->WriteTLV and field-export renames (TLV code constants verified unchanged). The receipt units now reach bgpls.DecodeSRCapabilities through the TLV 1034 decoder the plugin registers (lookupLsAttrTLVDecoder), so the adapter is exercised too; DecodeSRCapabilities is byte-identical to the old decodeSRCapabilities (len<2 refused, Flags stored, ranges from data[2:]). RFC 9085 Section 2.1.2: "Reserved: 1 octet that MUST be set to 0 and ignored on receipt." Set-0: ospf and isis originated-zero / poisoned-source pairs (unchanged). Ignored: Reserved ff skipped, not read as range data (Range 1000, FirstSID 16000 asserted exactly).

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085ISISAllOnesSourceNeverReachesReserved`	unit/verify	revert, verified
negative	`TestRFC9085OSPFSourceReservedNeverOriginated`	unit/verify	revert, verified
positive	`TestRFC9085SRCapabilitiesIgnoresReservedAndUndefinedFlags`	unit/verify	revert, verified
positive	`TestRFC9085CapabilitiesReceiptIgnoresFlagsAndReserved`	unit/verify	revert, verified
positive	`TestRFC9085ISISOriginatedCapabilitiesReservedZero`	unit/verify	revert, verified
positive	`TestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero`	unit/verify	revert, verified

`RFC9085-2.1.4-1`

The flags are not currently defined for OSPFv2 and OSPFv3 and MUST be set to 0 and ignored on receipt. (§2.1.4)

Audit verdict: enforced (the tests do what the requirement demands), fresh. D2 rejudge 2026-10-16 (independent judge, BGP-LS codec moved to internal/core/bgp/nlri/bgpls). Tagged units changed only by the package move: identifiers re-qualified with bgpls., comments re-pointed; producer bodies byte-identical modulo the writeTLV->WriteTLV and field-export renames (TLV code constants verified unchanged). The receipt units now reach bgpls.DecodeSRCapabilities through the TLV 1034 decoder the plugin registers (lookupLsAttrTLVDecoder), so the adapter is exercised too; DecodeSRCapabilities is byte-identical to the old decodeSRCapabilities (len<2 refused, Flags stored, ranges from data[2:]). RFC 9085 Section 2.1.4: "The flags are not currently defined for OSPFv2 and OSPFv3 and MUST be set to 0 and ignored on receipt." Set-0: ospf SRLB TLV 1036 pair (unchanged). Receipt: decodeSRLocalBlock (unchanged body) decodes Flags ff to the intact range.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085OSPFSourceReservedNeverOriginated`	unit/verify	revert, verified
positive	`TestRFC9085CapabilitiesReceiptIgnoresFlagsAndReserved`	unit/verify	revert, verified
positive	`TestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero`	unit/verify	revert, verified

`RFC9085-2.1.4-2`

Reserved: 1 octet that MUST be set to 0 and ignored on receipt. (§2.1.4)

Audit verdict: enforced (the tests do what the requirement demands), fresh. D2 rejudge 2026-10-16 (independent judge, BGP-LS codec moved to internal/core/bgp/nlri/bgpls). Tagged units changed only by the package move: identifiers re-qualified with bgpls., comments re-pointed; producer bodies byte-identical modulo the writeTLV->WriteTLV and field-export renames (TLV code constants verified unchanged). The receipt units now reach bgpls.DecodeSRCapabilities through the TLV 1034 decoder the plugin registers (lookupLsAttrTLVDecoder), so the adapter is exercised too; DecodeSRCapabilities is byte-identical to the old decodeSRCapabilities (len<2 refused, Flags stored, ranges from data[2:]). RFC 9085 Section 2.1.4: "Reserved: 1 octet that MUST be set to 0 and ignored on receipt." Set-0: isis and ospf TLV 1036 pairs (unchanged). Receipt: Reserved ff on TLV 1036 decodes to the intact range.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085ISISAllOnesSourceNeverReachesReserved`	unit/verify	revert, verified
negative	`TestRFC9085OSPFSourceReservedNeverOriginated`	unit/verify	revert, verified
positive	`TestRFC9085CapabilitiesReceiptIgnoresFlagsAndReserved`	unit/verify	revert, verified
positive	`TestRFC9085ISISOriginatedCapabilitiesReservedZero`	unit/verify	revert, verified
positive	`TestRFC9085OSPFOriginatedCapabilitiesFlagsReservedZero`	unit/verify	revert, verified

`RFC9085-2.2.1-1`

Reserved: 2 octets that MUST be set to 0 and ignored on receipt. (§2.2.1)

Audit verdict: enforced (the tests do what the requirement demands), fresh. rejudge 2026-09-30 (independent): owed OSPF half delivered. Set-0: isis TestRFC9085ISISOriginatedSIDReservedZero (+) / TestRFC9085ISISAllOnesSourceNeverReachesSIDReserved (-); ospf TestRFC9085OSPFOriginatedSIDReservedZero (+, exact 1099 = 60 05 0000 005dc1) / TestRFC9085OSPFSourceReservedNeverReachesSIDReserved (-, native Adj-SID Reserved ff -> 0000, byte-exact); producer bgplsAdjAttribute zero-fills value[2:4]. Receipt: nlri/ls TestRFC9085SIDReceiptIgnoresReserved (Reserved ffff decodes). Records observed red for every unit.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085ISISAllOnesSourceNeverReachesSIDReserved`	unit/verify	revert, verified
negative	`TestRFC9085OSPFSourceReservedNeverReachesSIDReserved`	unit/verify	revert, verified
positive	`TestRFC9085SIDReceiptIgnoresReserved`	unit/verify	revert, verified
positive	`TestRFC9085ISISOriginatedSIDReservedZero`	unit/verify	revert, verified
positive	`TestRFC9085OSPFOriginatedSIDReservedZero`	unit/verify	revert, verified

`RFC9085-2.2.2-1`

Reserved: 2 octets that MUST be set to 0 and ignored on receipt. (§2.2.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. rejudge 2026-09-30 (independent): both owed items delivered. Set-0: isis SID units (+/-); ospf TestRFC9085OSPFOriginatedSIDReservedZero (+, exact 1100 = 60 06 0000 04040404 005dc2) / TestRFC9085OSPFSourceReservedNeverReachesSIDReserved (-, native LAN Adj-SID Reserved ff -> 0000). Receipt: nlri/ls TestRFC9085UndecodedSIDReceiptKeepsReserved: a 1100 with Reserved ffff is kept whole as generic-lsid-1100 and the Node Name after it still decodes; this decoder carries 1100 undecoded, so ignoring = not refusing and not interpreting, single-polarity by nature. Records observed red.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085ISISAllOnesSourceNeverReachesSIDReserved`	unit/verify	revert, verified
negative	`TestRFC9085OSPFSourceReservedNeverReachesSIDReserved`	unit/verify	revert, verified
positive	`TestRFC9085UndecodedSIDReceiptKeepsReserved`	unit/verify	revert, verified
positive	`TestRFC9085ISISOriginatedSIDReservedZero`	unit/verify	revert, verified
positive	`TestRFC9085OSPFOriginatedSIDReservedZero`	unit/verify	revert, verified

`RFC9085-2.3.1-1`

Reserved: 2 octets that MUST be set to 0 and ignored on receipt. (§2.3.1)

Audit verdict: enforced (the tests do what the requirement demands), fresh. rejudge 2026-09-30 (independent): owed OSPF half delivered. Set-0: isis SID units (+/-); ospf TestRFC9085OSPFOriginatedSIDReservedZero (+, exact 1158 = 40 01 0000 0000004d) / TestRFC9085OSPFSourceReservedNeverReachesSIDReserved (-, native Prefix-SID Reserved ff -> 0000); the 1158 nested in the OSPF 1159 is also asserted byte-exact. Receipt: nlri/ls TestRFC9085SIDReceiptIgnoresReserved (decodePrefixSID, Reserved ffff). Records observed red.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085ISISAllOnesSourceNeverReachesSIDReserved`	unit/verify	revert, verified
negative	`TestRFC9085OSPFSourceReservedNeverReachesSIDReserved`	unit/verify	revert, verified
positive	`TestRFC9085SIDReceiptIgnoresReserved`	unit/verify	revert, verified
positive	`TestRFC9085ISISOriginatedSIDReservedZero`	unit/verify	revert, verified
positive	`TestRFC9085OSPFOriginatedSIDReservedZero`	unit/verify	revert, verified

`RFC9085-2.3.5-1`

Reserved: 1 octet that MUST be set to 0 and ignored on receipt. (§2.3.5)

Audit verdict: enforced (the tests do what the requirement demands), fresh. rejudge 2026-09-30 (independent): both owed items delivered. Set-0: isis SID units (+/-); ospf TestRFC9085OSPFOriginatedSIDReservedZero (+, exact 1159 = 80 00 0010 0486 0008 40000000 00000064) / TestRFC9085OSPFSourceReservedNeverReachesSIDReserved (-, native Range Reserved ff ff ff and inner Prefix-SID Reserved ff); judge targeted break (1159 Reserved <- native r.Value[5] in extendedV2Prefix) turned the negative red while the positive stayed green. Receipt: nlri/ls TestRFC9085UndecodedSIDReceiptKeepsReserved (1159 with Reserved ff kept whole as generic-lsid-1159, attribute not refused), single-polarity by nature. Records observed red.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085ISISAllOnesSourceNeverReachesSIDReserved`	unit/verify	revert, verified
negative	`TestRFC9085OSPFSourceReservedNeverReachesSIDReserved`	unit/verify	revert, verified
positive	`TestRFC9085UndecodedSIDReceiptKeepsReserved`	unit/verify	revert, verified
positive	`TestRFC9085ISISOriginatedSIDReservedZero`	unit/verify	revert, verified
positive	`TestRFC9085OSPFOriginatedSIDReservedZero`	unit/verify	revert, verified

`RFC9085-2.1.1-1`

SID/Label: If the length is set to 3, then the 20 rightmost bits represent a label (the total TLV size is 7), and the 4 leftmost bits are set to 0. (§2.1.1)

Audit verdict: enforced (the tests do what the requirement demands), fresh. rejudge 2026-09-30: defect fixed (D-8): isis srBlock copied the 3-octet SID/Label verbatim into sub-TLV 1161; it now clears the 4 leftmost bits. isis TestRFC9085OriginatedSRGBLabelTwentyBits (+: 003e80 -> 003e80) and TestRFC9085OriginatedSRGBLabelHighBitsCleared (-: f03e80 -> 003e80) assert the exact TLV 1034; judge break (mask removed) turns the negative red. Receipt: nlri/ls TestRFC9085SIDLabelMasksLeftmostFourBits (0xF12345 -> 0x12345). Marker removed.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085OriginatedSRGBLabelHighBitsCleared`	unit/verify	revert, verified
positive	`TestRFC9085SIDLabelMasksLeftmostFourBits`	unit/verify	unproven
positive	`TestRFC9085OriginatedSRGBLabelTwentyBits`	unit/verify	revert, verified

`RFC9085-2.1-1`

These TLVs should only be added to the BGP-LS Attribute associated with the Node NLRI that describes the IGP node that is originating the corresponding IGP TLV/sub-TLV described below. (§2.1)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Re-judged 2026-10-02 (independent judge, ospf c28). OSPF exporter as judged 2026-09-30 (+ TestRFC9085OSPFCapabilitiesOnOriginatorNode, - TestRFC9085OSPFCapabilitiesOnNoOtherNLRI, targeted breaks red). IS-IS exporter now driven (new isis/bgpls_export_rfc9085_placement_test.go): two L1 LSPs through the LSDB and bgplsBuilder.build; + TestRFC9085ISISCapabilitiesOnOriginatorNode: 0000.0000.0002 (TLV 242 with sub-TLVs 2/19/22) gets exactly one 1034/1035/1036 with exact bytes; - TestRFC9085ISISCapabilitiesOnNoOtherNLRI: 0000.0000.0003 Node NLRI, both Link and both Prefix NLRIs (presence asserted) carry none. Judge overlay: TLV 242 deferred and applied to the last node built (0000.0000.0003) -> + red (0 TLV 1034) and - red ('node 0000.0000.0003 carries TLV 1034'); author overlays (copy to other node / to every Link and Prefix NLRI) -> - red only. Revert records on capabilities observed. Support remaining sentence 'tested on the OSPF exporter only' removed as now false.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085ISISCapabilitiesOnNoOtherNLRI`	unit/verify	revert, verified
negative	`TestRFC9085OSPFCapabilitiesOnNoOtherNLRI`	unit/verify	revert, verified
positive	`TestRFC9085ISISCapabilitiesOnOriginatorNode`	unit/verify	revert, verified
positive	`TestRFC9085OSPFCapabilitiesOnOriginatorNode`	unit/verify	revert, verified

`RFC9085-2.2-1`

These TLVs should only be added to the BGP-LS Attribute associated with the Link NLRI that describes the link of the IGP node that is originating the corresponding IGP TLV/sub-TLV described below. (§2.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Re-judged 2026-10-12 (independent auditor). STALE from 96ec49327b (owner-approved lint only): TestRFC9085NativeExportAttributePlacement replaces counted byte loops with range byte(3) (same 0,1,2), an if/else-if chain on kind with a tagless switch carrying the same arms and default Fatalf, and a dead route := 0 initialisation with a declaration where it is assigned. No input or assertion changed. Verdict stands. RFC 9085 §2.2 says, “These TLVs should only be added to the BGP-LS Attribute associated with the Link NLRI that describes the link of the IGP node that is originating the corresponding IGP TLV/sub-TLV described below.” Native IS-IS LSP and OSPFv2/v3 LSDB tests establish association of emitted 1099/1100 with the advertising router and correct link, including parallel links and tested topology identities, while populated Node/Prefix controls exclude link attributes. Separate replace/reconcile/export tests preserve that association into Link NLRIs, assert complete expected interface-ID/address descriptors, exact SID values and multiplicity, and reject cross-object placement. This proves the conditional placement duty for the current native producers, not implementation of all §2.2 features: native IS-IS 1172 remains absent, and RFC 9085 defines no corresponding OSPF bundle feature. It is composed native-derivation and exporter-association evidence, not a single integrated IGP-daemon-to-peer run. Independent source judgment: BGPLSPlacementWholeReview. Current five-root race-enabled observation: job-bgpls-complete-object-identity-after-9a6e8f72.log.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085NativeExportAttributePlacement`	unit/verify	revert, verified
negative	`TestRFC9085ISISLinkPlacement`	unit/verify	revert, verified
negative	`TestRFC9085OSPFLinkPlacement`	unit/verify	revert, verified
positive	`TestRFC9085NativeExportAttributePlacement`	unit/verify	revert, verified
positive	`TestRFC9085ISISLinkPlacement`	unit/verify	revert, verified
positive	`TestRFC9085OSPFLinkPlacement`	unit/verify	revert, verified

`RFC9085-2.3-1`

These TLVs should only be added to the BGP-LS Attribute associated with the Prefix NLRI that describes the prefix of the IGP node that is originating the corresponding IGP TLV/sub-TLV described below. (§2.3)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Re-judged 2026-10-12 (independent auditor). STALE from 96ec49327b (owner-approved lint only): TestRFC9085NativeExportAttributePlacement replaces counted byte loops with range byte(3) (same 0,1,2), an if/else-if chain on kind with a tagless switch carrying the same arms and default Fatalf, and a dead route := 0 initialisation with a declaration where it is assigned. No input or assertion changed. Verdict stands. RFC 9085 §2.3 says, “These TLVs should only be added to the BGP-LS Attribute associated with the Prefix NLRI that describes the prefix of the IGP node that is originating the corresponding IGP TLV/sub-TLV described below.” Native IS-IS tests establish placement of 1158/1159/1170/1171 from IPv4/IPv6 reachability, bindings and narrow-external input; native OSPFv2/v3 tests establish placement of 1158/1159/1170, including extended prefix classes and base-v3 flags. Exact values, object counts and populated Node/Link exclusions discriminate incorrect association. Separate replace/reconcile/export tests preserve origin, prefix address/length, IPv4/IPv6 NLRI type and tested topology identities; competing same-prefix OSPF classes 1/2/3/5 now retain exact descriptor 264 and their distinct SID values. This proves the conditional placement duty for current native producers, not absent OSPF 1171/1174 support; 1174 is OSPF-only, not an IS-IS gap. No integrated daemon run or received-attribute semantic validation is claimed. Independent source judgment: BGPLSPlacementWholeReview. Current five-root race-enabled observation: job-bgpls-complete-object-identity-after-9a6e8f72.log.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9085NativeExportAttributePlacement`	unit/verify	revert, verified
negative	`TestRFC9085ISISPrefixPlacement`	unit/verify	revert, verified
negative	`TestRFC9085OSPFPrefixPlacement`	unit/verify	revert, verified
positive	`TestRFC9085NativeExportAttributePlacement`	unit/verify	revert, verified
positive	`TestRFC9085ISISPrefixPlacement`	unit/verify	revert, verified
positive	`TestRFC9085OSPFPrefixPlacement`	unit/verify	revert, verified

Extraction sign-off

Field	Value
Reviewer	claude
Signed off	2026-09-21
Register	prose
Source	rfc/full/rfc9085.txt
Source fingerprint	fdec3413ebb35a14
Record	rfc/extraction/rfc9085.json
Mapped sentences	8
Declined as scope	3
Relocated to a spec, which Ze OWES	0
Unclassified	0

Sections

Section	Name	Sites	Disposition	Reason
`front`	not stated	1	walked	not stated
`1`	not stated	0	walked	not stated
`1.1`	not stated	0	walked	not stated
`2`	not stated	0	walked	not stated
`2.1`	not stated	0	walked	not stated
`2.1.1`	not stated	0	walked	not stated
`2.1.2`	not stated	2	walked	not stated
`2.1.3`	not stated	0	walked	not stated
`2.1.4`	not stated	3	walked	not stated
`2.1.5`	not stated	0	walked	not stated
`2.2`	not stated	0	walked	The lowercase placement recommendation covers all Link Attribute TLVs in Table 2: 1099, 1100 and 1172, associated with the originating node's specific Link NLRI. Recording it does not establish exporter proof.
`2.2.1`	not stated	1	walked	not stated
`2.2.2`	not stated	1	walked	not stated
`2.2.3`	not stated	0	walked	not stated
`2.3`	not stated	0	walked	The lowercase placement recommendation covers all Prefix Attribute TLVs in Table 4: 1158, 1159, 1170, 1171 and 1174, associated with the originating node's specific Prefix NLRI. Recording it does not establish exporter proof.
`2.3.1`	not stated	1	walked	not stated
`2.3.2`	not stated	0	walked	not stated
`2.3.3`	not stated	0	walked	not stated
`2.3.4`	not stated	0	walked	not stated
`2.3.5`	not stated	1	walked	not stated
`2.4`	not stated	0	walked	not stated
`2.5`	not stated	0	walked	not stated
`3`	not stated	0	walked	not stated
`3.1`	not stated	0	walked	not stated
`4`	not stated	0	walked	not stated
`5`	not stated	1	walked	not stated
`6`	not stated	0	walked	not stated
`6.1`	not stated	0	walked	not stated
`6.2`	not stated	0	walked	not stated

Excluded sentences

Site	Excluded kind	Reason	Quote
`front:1`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	Boilerplate from the Copyright Notice: it states the licence terms under which code components extracted from the document are provided ('must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions'). It binds a republisher of the text, not a BGP-LS implementation, and names no message, field or procedure.	Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
`2.1.4:1`	`cross-document` never bound Ze the obligation belongs to another document that this one only cites	The obligation to advertise the SRLB belongs to the IGP documents the same section cites three lines later: 'This information is derived from the protocol-specific advertisements. * IS-IS, as defined by the SRLB Sub-TLV in Section 3.3 of [RFC8667]. * OSPFv2/OSPFv3, as defined by the SR Local Block TLV in Section 3.3 of [RFC8665] and [RFC8666]'. RFC 9085 defines only how BGP-LS carries the range once the IGP has advertised it; the sentence explains why the IGP advertisement exists.	Therefore, in order for such applications or controllers to know the range of local SIDs available, the node is required to advertise its SRLB.
`5:1`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	A Security Considerations ASSUMPTION rather than an obligation: 'The IGP instances originating these TLVs are assumed to support all the required security and authentication mechanisms (as described in [RFC8665], [RFC8666], and [RFC8667])'. It states what this document takes for granted about the IGP that feeds BGP-LS, and the mechanisms it names are required by those three documents, not by this one.	The IGP instances originating these TLVs are assumed to support all the required security and authentication mechanisms (as described in [RFC8665], [RFC8666], and [RFC8667]) in order to prevent any security issue when propagating the TLVs into BGP-LS.

Superseded

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