Partial

RFC 9086 - Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing BGP Egress Peer Engineering

Every requirement this repository extracted from RFC 9086, 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 ways63.6%7 of 11 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 11 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 11 gated MUSTs

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

Proven by a recorded break100.0%22 of 22 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 20 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

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 11 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 11 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 11 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

Negative

what Ze owes

Partial proof; remaining gap9.1%1 of 11 gated MUSTs

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

No test at all27.3%3 of 11 gated MUSTs

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

Audit verdicts7of 11 gated MUSTs judged

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

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

Enrolment

Enrolled: BGP-LS Egress Peer Engineering SID decoding and native PeerNode SID origination from configured local SRGB assignments and established BGP sessions.

What the public ledger says

Status: Partial

What the ledger says is covered

PeerNode/Adj/Set SID TLVs and BGP Router-ID/Member-ASN descriptors decode. The native bgp-epe producer installs configured PeerNode labels through the MPLS FIB owner, waits for installation acknowledgement, and publishes live session identities with its SRGB. bgp-ls-export advertises that state and withdraws replaced or removed identities.

What the ledger says remains:

PeerAdj and PeerSet segment assignment and their advertisement controls are not implemented; neither is per-recipient selection of EPE information. Native EPE uses persistent operator-assigned indices, not three-octet label assignments.

Coverage

Bucket	Count	What it counts
Positive and negative tests	7	one part of the gated population
Annotated (including scoped evidence)	4	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)	1	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	11	every gated MUST falls in exactly one bucket above

Positive and negative tests (7): RFC9086-3-1, RFC9086-3-2, RFC9086-4.2-1, RFC9086-4.2-2, RFC9086-5-1, RFC9086-5-3, RFC9086-5-10

Annotated (including scoped evidence) (4): RFC9086-5.2-1, RFC9086-5-2, RFC9086-7-1, RFC9086-7-2

Partial proof; remaining gap (subset of annotated; zero whole-requirement credit) (1): RFC9086-7-1

Requirements

Requirement	Level	Section	Tests
`RFC9086-3-1`	Each BGP session MUST be described by a PeerNode SID (S3)
	MUST	3	positive`unit/verifyTestRFC9086NativePeerIndexAdvertisesSRGB` negative`unit/verifyTestRFC9086NativeLinkWithoutPeerNodeRefused`
`RFC9086-3-2`	One PeerNode SID MUST be instantiated to describe the BGP peer session (S3)
	MUST	3	positive`unit/verifyTestRFC9086NativePeerIndexAdvertisesSRGB` negative`unit/verifyTestRFC9086NativeRepeatedUpKeepsOnePeerNodeSID`
`RFC9086-4.2-1`	The following Node Descriptor TLVs MUST be included in BGP-LS NLRI as Local Node Descriptors when distributing BGP information: * BGP Router-ID (TLV 516), which contains a valid BGP Identifier of the local BGP node. * Autonomous System Number (TLV 512) [RFC7752], which contains the Autonomous System Number (ASN) or AS Confederation Identifier (an ASN) [RFC5065], if confederations are used, of the local BGP node. (S4.2)
	MUST	4.2	positive`unit/verifyTestRFC9086EveryBGPNLRICarriesLocalRouterIDAndASN` positive`unit/verifyTestRFC9086NativePeerIndexAdvertisesSRGB` negative`unit/verifyTestRFC9086NativePeerRequiresLocalRouterID` negative`unit/verifyTestRFC9086NativePeerRequiresNodeIdentities`
`RFC9086-4.2-2`	The following Node Descriptor TLVs MUST be included in BGP-LS Link NLRI as Remote Node Descriptors when distributing BGP information: * BGP Router-ID (TLV 516), which contains the valid BGP Identifier of the peer BGP node. * Autonomous System Number (TLV 512) [RFC7752], which contains the ASN or the AS Confederation Identifier (an ASN) [RFC5065], if confederations are used, of the peer BGP node. (S4.2)
	MUST	4.2	positive`unit/verifyTestRFC9086NativePeerIndexAdvertisesSRGB` negative`unit/verifyTestRFC9086NativePeerRequiresNodeIdentities`
`RFC9086-5-1`	When enabled for Egress Peer Engineering, the BGP router MUST include the PeerNode SID TLV in the BGP-LS Attribute for the BGP-LS Link NLRI corresponding to its BGP peering sessions. (S5)
	MUST	5	positive`unit/verifyTestRFC9086NativePeerIndexAdvertisesSRGB` negative`unit/verifyTestRFC9086NativeLinkWithoutPeerNodeRefused`
`RFC9086-5.2-1`	Link Descriptors MUST include the following TLV, as defined in [RFC7752]: - Link Local/Remote Identifiers (TLV 258) contains the 4-octet Link Local Identifier followed by the 4-octet Link Remote Identifier. (S5.2)
	MUST	5.2	positive`no test`no positive test negative`no test`no negative test {gap}: LinkDescriptor.WriteTo emits TLV 258 but no origination path builds a PeerAdj SID advertisement (internal/core/bgp/nlri/bgpls/types_descriptor.go:203-206)
`RFC9086-5-2`	A 3-octet local label where the 20 rightmost bits are used for encoding the label value. In this case, the V- and L-Flags MUST be SET. (S5)
	MUST	5	positive`no test`no positive test negative`no test`no negative test {gap}: the encoder writes the Flags byte verbatim and never originates a label-encoded SID, so no path sets V/L (internal/component/bgp/plugins/nlri/ls/attr_link.go:521)
`RFC9086-5-3`	- Rsvd bits: Reserved for future use and MUST be zero when originated and ignored when received. (S5)
	MUST	5	positive`unit/verifyTestRFC9086NativePeerSIDReservedFlagsZero` positive`unit/verifyTestRFC9086OriginatedPeerSIDRsvdBitsZero` positive`unit/verifyTestRFC9086PeerSIDIgnoresReservedFields` positive`unit/verifyTestRFC9086PeerSIDRsvdBitsIgnoredWhenReceived` negative`unit/verifyTestRFC9086NativePeerSIDReservedFlagsZero` negative`unit/verifyTestRFC9086SourceRsvdBitsNeverOriginated`
`RFC9086-5-10`	A 4-octet index defining the offset in the Segment Routing Global Block (SRGB) [RFC8402] advertised by this router. In this case, the SRGB MUST be advertised using the extensions defined in [RFC9085]. (S5)
	MUST	5	positive`unit/verifyTestRFC9086NativePeerIndexAdvertisesSRGB` negative`unit/verifyTestRFC9086NativePeerIndexRequiresSRGB`
`RFC9086-7-1`	The operator MUST be provided with the options of configuring, enabling, and disabling the advertisement of each of the PeerNode SID, PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer. (S7)
	MUST	7	positive`unit/verifyTestRFC9086NativeConfigurationEnableDisable` negative`unit/verifyTestRFC9086NativeConfigurationEnableDisable` {partial}: tested "The operator MUST be provided with the options of configuring, enabling, and disabling the advertisement of each of the PeerNode SID,"; gap "PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer."; Owner R3 preserves the tested PeerNode configuration scope. internal/component/bgp/plugins/epe/epe_config.go::ParseConfig provides PeerNode assignments only. internal/component/bgp/plugins/ls_export/export_config.go::parseExportConfig provides no per-recipient EPE information controls. PeerAdj and PeerSet controls remain absent, as recorded by RFC9086-7-2. No whole-requirement conformance is claimed. Scoped evidence: Tests and tag-claim records apply only to Tested; zero whole-requirement credit. partial (the tests enforce only the declared tested scope; the whole requirement remains unmet), fresh. Independent EPEReconcileNow judgment against RFC9086 Section 7 and owner R3. Tested: "The operator MUST be provided with the options of configuring, enabling, and disabling the advertisement of each of the PeerNode SID,". Gap: "PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer." TestRFC9086NativeConfigurationEnableDisable parses PeerNode configuration, asserts label 16007 and exact PeerNode TLV bytes, then removes configuration and requires both collector withdrawals and label removal while the session stays up. The registered producer/exporter path connects these controls to native advertisements. internal/component/bgp/plugins/epe/epe_config.go::ParseConfig provides only PeerNode assignments. internal/component/bgp/plugins/ls_export/export_config.go::parseExportConfig exposes no per-recipient EPE control, and exporter reconciliation supplies the same desired topology to attached collectors. Existing publishLocked breaks establish producer reachability for both retained claims, not complete Section 7 conformance. The complete sentence remains unmet; no absent PeerAdj, PeerSet, or per-recipient capability is implemented by this correction.
`RFC9086-7-2`	PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer. (S7)
	MUST	7	positive`no test`no positive test negative`no test`no negative test {gap}: R3 split of the operator-control sentence; native bgp-epe implements only PeerNode assignment, not PeerAdj/PeerSet advertisement options or per-recipient information controls (internal/component/bgp/plugins/epe/epe_config.go ParseConfig; internal/component/bgp/plugins/ls_export/export_config.go parseExportConfig).
`RFC9086-5-7`	The values of the PeerNode SID, PeerAdj SID, and PeerSet SID Sub-TLVs SHOULD be persistent across router restart. (S5)
	SHOULD	5	positive`no test`no positive test negative`no test`no negative test
`RFC9086-3-3`	As such, when the IBGP design includes sessions with route reflectors, a BGP router SHOULD NOT instantiate a BGP Peering SID for those sessions to peer nodes that are not in the forwarding path since the purpose of BGP Peering SID is to steer traffic to those specific peers. (S3)
	SHOULD NOT	3	positive`no test`no positive test negative`no test`no negative test
`RFC9086-3-4`	One or more PeerAdj SID MAY be instantiated corresponding to the underlying link(s) to the directly connected BGP peer session. (S3)
	MAY	3	positive`no test`no positive test negative`no test`no negative test
`RFC9086-3-5`	A PeerSet SID MAY be instantiated and additionally associated and shared between one or more PeerNode SIDs or PeerAdj SIDs. (S3)
	MAY	3	positive`no test`no positive test negative`no test`no negative test
`RFC9086-4.3-1`	The following Node Descriptor TLVs MAY be included in BGP-LS NLRI as Local Node Descriptors when distributing BGP information: * Member-ASN (TLV 517), which contains the ASN of the confederation member (i.e., Member-AS Number), if BGP confederations are used, of the local BGP node. * Node Descriptors as defined in [RFC7752]. The following Node Descriptor TLVs MAY be included in BGP-LS Link NLRI as Remote Node Descriptors when distributing BGP information: * Member-ASN (TLV 517), which contains the ASN of the confederation member (i.e., Member-AS Number), if BGP confederations are used, of the peer BGP node. (S4.3)
	MAY	4.3	positive`no test`no positive test negative`no test`no negative test
`RFC9086-4.3-2`	The following Node Descriptor TLVs MAY be included in BGP-LS NLRI as Local Node Descriptors when distributing BGP information: * Member-ASN (TLV 517), which contains the ASN of the confederation member (i.e., Member-AS Number), if BGP confederations are used, of the local BGP node. * Node Descriptors as defined in [RFC7752]. The following Node Descriptor TLVs MAY be included in BGP-LS Link NLRI as Remote Node Descriptors when distributing BGP information: * Member-ASN (TLV 517), which contains the ASN of the confederation member (i.e., Member-AS Number), if BGP confederations are used, of the peer BGP node. * Node Descriptors as defined in [RFC7752]. (S4.3)
	MAY	4.3	positive`no test`no positive test negative`no test`no negative test
`RFC9086-5-8`	The PeerAdj SID and PeerSet SID TLVs MAY be included in the BGP-LS Attribute (S5)
	MAY	5	positive`no test`no positive test negative`no test`no negative test
`RFC9086-5-9`	Additional BGP-LS Link Attribute TLVs as defined in [RFC7752] MAY be included with the BGP-LS Link NLRI in order to advertise the characteristics of the peering link (S5)
	MAY	5	positive`no test`no positive test negative`no test`no negative test
`RFC9086-5.2-2`	Additional Link Descriptors TLVs, as defined in [RFC7752], MAY also be included to describe the addresses corresponding to the link between the BGP routers (S5.2)
	MAY	5.2	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

Requirement	State	Reason
`RFC9086-5.2-1` Link Descriptors MUST include the following TLV, as defined in [RFC7752]: - Link Local/Remote Identifiers (TLV 258) contains the 4-octet Link Local Identifier followed by the 4-octet Link Remote Identifier. (S5.2)	{gap}, no test	LinkDescriptor.WriteTo emits TLV 258 but no origination path builds a PeerAdj SID advertisement (internal/core/bgp/nlri/bgpls/types_descriptor.go:203-206)
`RFC9086-5-2` A 3-octet local label where the 20 rightmost bits are used for encoding the label value. In this case, the V- and L-Flags MUST be SET. (S5)	{gap}, no test	the encoder writes the Flags byte verbatim and never originates a label-encoded SID, so no path sets V/L (internal/component/bgp/plugins/nlri/ls/attr_link.go:521)
`RFC9086-7-1` The operator MUST be provided with the options of configuring, enabling, and disabling the advertisement of each of the PeerNode SID, PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer. (S7)	{partial}, Partial proof; remaining gap	tested "The operator MUST be provided with the options of configuring, enabling, and disabling the advertisement of each of the PeerNode SID,"; gap "PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer."; Owner R3 preserves the tested PeerNode configuration scope. internal/component/bgp/plugins/epe/epe_config.go::ParseConfig provides PeerNode assignments only. internal/component/bgp/plugins/ls_export/export_config.go::parseExportConfig provides no per-recipient EPE information controls. PeerAdj and PeerSet controls remain absent, as recorded by RFC9086-7-2. No whole-requirement conformance is claimed.
`RFC9086-7-2` PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer. (S7)	{gap}, no test	R3 split of the operator-control sentence; native bgp-epe implements only PeerNode assignment, not PeerAdj/PeerSet advertisement options or per-recipient information controls (internal/component/bgp/plugins/epe/epe_config.go ParseConfig; internal/component/bgp/plugins/ls_export/export_config.go parseExportConfig).

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.

`RFC9086-3-1`

Each BGP session MUST be described by a PeerNode SID (S3)

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

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9086NativeLinkWithoutPeerNodeRefused`	unit/verify	revert, verified
positive	`TestRFC9086NativePeerIndexAdvertisesSRGB`	unit/verify	revert, verified

`RFC9086-3-2`

One PeerNode SID MUST be instantiated to describe the BGP peer session (S3)

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

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9086NativeRepeatedUpKeepsOnePeerNodeSID`	unit/verify	revert, verified
positive	`TestRFC9086NativePeerIndexAdvertisesSRGB`	unit/verify	revert, verified

`RFC9086-4.2-1`

The following Node Descriptor TLVs MUST be included in BGP-LS NLRI as Local Node Descriptors when distributing BGP information: * BGP Router-ID (TLV 516), which contains a valid BGP Identifier of the local BGP node. * Autonomous System Number (TLV 512) [RFC7752], which contains the Autonomous System Number (ASN) or AS Confederation Identifier (an ASN) [RFC5065], if confederations are used, of the local BGP node. (S4.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. rejudge 2026-10-02 (c33 judge): + TestRFC9086EveryBGPNLRICarriesLocalRouterIDAndASN reads both emitted NLRIs (Node type 1 and Link type 2, Protocol-ID 7) and asserts one Local Node Descriptors TLV 256 holding TLV 516 c0 00 02 01 and TLV 512 00 00 fd e8 exactly once each, closing the unchecked Node NLRI. - TestRFC9086NativePeerRequiresLocalRouterID (local router-id 0.0.0.0 or absent: State errors, no label, no NLRI) beside HEAD TestRFC9086NativePeerRequiresNodeIdentities (local ASN 0). Judge break: the local-identifier check in epe_source.go State reduced to rejecting only a non-IPv4 address turns the new negative red. The confederation-identifier clause is conditional on confederations, which have no configuration surface in Ze (internal/component/bgp/reactor/forward_local_pref.go), so TLV 512 always carries the plain local ASN.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9086NativePeerRequiresLocalRouterID`	unit/verify	revert, verified
negative	`TestRFC9086NativePeerRequiresNodeIdentities`	unit/verify	revert, verified
positive	`TestRFC9086EveryBGPNLRICarriesLocalRouterIDAndASN`	unit/verify	revert, verified
positive	`TestRFC9086NativePeerIndexAdvertisesSRGB`	unit/verify	revert, verified

`RFC9086-4.2-2`

The following Node Descriptor TLVs MUST be included in BGP-LS Link NLRI as Remote Node Descriptors when distributing BGP information: * BGP Router-ID (TLV 516), which contains the valid BGP Identifier of the peer BGP node. * Autonomous System Number (TLV 512) [RFC7752], which contains the ASN or the AS Confederation Identifier (an ASN) [RFC5065], if confederations are used, of the peer BGP node. (S4.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. (a) forbidden: a BGP-LS Link NLRI whose Remote Node Descriptors lack TLV 516 or TLV 512 of the peer. (b) TestRFC9086NativePeerIndexAdvertisesSRGB asserts remote 516=192.0.2.2 and remote 512=65001 on the Link NLRI; each goes red if that TLV is dropped or carries the local value. Negative: TestRFC9086NativePeerRequiresNodeIdentities, a remote Router-ID of 0.0.0.0 refuses origination, installs no label and emits no command.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9086NativePeerRequiresNodeIdentities`	unit/verify	revert, verified
positive	`TestRFC9086NativePeerIndexAdvertisesSRGB`	unit/verify	revert, verified

`RFC9086-5-1`

When enabled for Egress Peer Engineering, the BGP router MUST include the PeerNode SID TLV in the BGP-LS Attribute for the BGP-LS Link NLRI corresponding to its BGP peering sessions. (S5)

Audit verdict: enforced (the tests do what the requirement demands), fresh. (a) forbidden: an EPE-enabled BGP session advertised as a Link NLRI whose BGP-LS Attribute lacks the PeerNode SID TLV 1101. (b) TestRFC9086NativePeerIndexAdvertisesSRGB asserts exportTLVValues(linkAttrs, 1101) equals exactly the assigned SID; TestRFC9086NativeLinkWithoutPeerNodeRefused asserts a BGP Link snapshot with no 1101 is refused (replace errors, no command emitted).

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9086NativeLinkWithoutPeerNodeRefused`	unit/verify	revert, verified
positive	`TestRFC9086NativePeerIndexAdvertisesSRGB`	unit/verify	revert, verified

`RFC9086-5.2-1`

Link Descriptors MUST include the following TLV, as defined in [RFC7752]: - Link Local/Remote Identifiers (TLV 258) contains the 4-octet Link Local Identifier followed by the 4-octet Link Remote Identifier. (S5.2)

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

No test carries RFC9086-5.2-1, so no unit is bound to it.

`RFC9086-5-2`

A 3-octet local label where the 20 rightmost bits are used for encoding the label value. In this case, the V- and L-Flags MUST be SET. (S5)

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

No test carries RFC9086-5-2, so no unit is bound to it.

`RFC9086-5-3`

- Rsvd bits: Reserved for future use and MUST be zero when originated and ignored when received. (S5)

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). RFC 9086 Section 5: "Rsvd bits: Reserved for future use and MUST be zero when originated and ignored when received." Originate: ls_export 0xc0/0xcf pair and the native PeerNode reserved-flags unit (unchanged). Receive: TestRFC9086PeerSIDRsvdBitsIgnoredWhenReceived iterates bgpls.TLVPeerNodeSID/AdjSID/SetSID (same codes 1101-1103) over the registered decoders with reserved set and clear, requiring equal flags, weight and SID; decodePeerSID unchanged.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9086NativePeerSIDReservedFlagsZero`	unit/verify	revert, verified
negative	`TestRFC9086SourceRsvdBitsNeverOriginated`	unit/verify	revert, verified
positive	`TestRFC9086NativePeerSIDReservedFlagsZero`	unit/verify	revert, verified
positive	`TestRFC9086OriginatedPeerSIDRsvdBitsZero`	unit/verify	revert, verified
positive	`TestRFC9086PeerSIDIgnoresReservedFields`	unit/verify	revert, verified
positive	`TestRFC9086PeerSIDRsvdBitsIgnoredWhenReceived`	unit/verify	revert, verified

`RFC9086-5-10`

A 4-octet index defining the offset in the Segment Routing Global Block (SRGB) [RFC8402] advertised by this router. In this case, the SRGB MUST be advertised using the extensions defined in [RFC9085]. (S5)

Audit verdict: enforced (the tests do what the requirement demands), fresh. (a) forbidden: advertising an index-encoded PeerNode SID without advertising the SRGB through the RFC 9085 SR Capabilities TLV. (b) TestRFC9086NativePeerIndexAdvertisesSRGB asserts the Node NLRI attribute carries TLV 1034 with range 100 and base label 16000 alongside the index SID 7; TestRFC9086NativePeerIndexRequiresSRGB asserts an index SID with no SRGB is refused and no command is emitted.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC9086NativePeerIndexRequiresSRGB`	unit/verify	revert, verified
positive	`TestRFC9086NativePeerIndexAdvertisesSRGB`	unit/verify	revert, verified

`RFC9086-7-1`

The operator MUST be provided with the options of configuring, enabling, and disabling the advertisement of each of the PeerNode SID, PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer. (S7)

Scoped tag-claim records only: tested "The operator MUST be provided with the options of configuring, enabling, and disabling the advertisement of each of the PeerNode SID,"; gap "PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer."; Owner R3 preserves the tested PeerNode configuration scope. internal/component/bgp/plugins/epe/epe_config.go::ParseConfig provides PeerNode assignments only. internal/component/bgp/plugins/ls_export/export_config.go::parseExportConfig provides no per-recipient EPE information controls. PeerAdj and PeerSet controls remain absent, as recorded by RFC9086-7-2. No whole-requirement conformance is claimed.; zero whole-requirement credit.

Audit verdict: partial (the tests enforce only the declared tested scope; the whole requirement remains unmet), fresh. Independent EPEReconcileNow judgment against RFC9086 Section 7 and owner R3. Tested: "The operator MUST be provided with the options of configuring, enabling, and disabling the advertisement of each of the PeerNode SID,". Gap: "PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer." TestRFC9086NativeConfigurationEnableDisable parses PeerNode configuration, asserts label 16007 and exact PeerNode TLV bytes, then removes configuration and requires both collector withdrawals and label removal while the session stays up. The registered producer/exporter path connects these controls to native advertisements. internal/component/bgp/plugins/epe/epe_config.go::ParseConfig provides only PeerNode assignments. internal/component/bgp/plugins/ls_export/export_config.go::parseExportConfig exposes no per-recipient EPE control, and exporter reconciliation supplies the same desired topology to attached collectors. Existing publishLocked breaks establish producer reachability for both retained claims, not complete Section 7 conformance. The complete sentence remains unmet; no absent PeerAdj, PeerSet, or per-recipient capability is implemented by this correction.

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

`RFC9086-7-2`

PeerAdj SID, and PeerSet SID as well as control of which information is advertised to which internal or external peer. (S7)

Audit verdict: unimplemented (no code path enforces the requirement), fresh. Independent EPEReconcileNow first judgment against the complete RFC9086 Section 7 operator-control sentence and owner R3. The retained split-gap clause requires PeerAdj SID and PeerSet SID advertisement controls and selection of information for each internal or external recipient. internal/component/bgp/plugins/epe/epe_config.go::ParseConfig accepts PeerNode assignments only; it has no PeerAdj or PeerSet assignment. internal/component/bgp/plugins/ls_export/export_config.go::parseExportConfig configures exporter enablement and domain mappings, not per-recipient EPE information controls. The exporter supplies the same desired topology to its attached collectors. These absent capabilities remain disclosed in Support remaining and the gap annotation. Existing PeerNode enable/disable tests prove none of this absent scope; recording it does not authorize implementation or imply another distinct RFC sentence.

No test carries RFC9086-7-2, so no unit is bound to it.

Extraction sign-off

Field	Value
Reviewer	claude
Signed off	2026-09-21
Register	prose
Source	rfc/full/rfc9086.txt
Source fingerprint	0e661e69fa88a113
Record	rfc/extraction/rfc9086.json
Mapped sentences	10
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
`2`	not stated	0	walked	not stated
`3`	not stated	2	walked	not stated
`4`	not stated	0	walked	not stated
`4.1`	not stated	0	walked	not stated
`4.2`	not stated	2	walked	not stated
`4.3`	not stated	0	walked	not stated
`5`	not stated	4	walked	not stated
`5.1`	not stated	0	walked	not stated
`5.2`	not stated	1	walked	not stated
`5.3`	not stated	0	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
`7`	not stated	2	walked	not stated
`8`	not stated	1	walked	not stated
`9`	not stated	0	walked	not stated
`9.1`	not stated	0	walked	not stated
`9.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	IETF Trust boilerplate on the Simplified BSD License for extracted Code Components; it binds republication of the document, not any protocol behaviour.	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.
`7:2`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	A comparative remark closing the operator-control paragraph: 'what is required by a BGP speaker' is lowercase and states that this control is nothing new, imposing no behaviour of its own.	This is not different from what is required by a BGP speaker in terms of information origination and advertisement.
`8:1`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	Security Considerations prose: 'is also required to ensure' is lowercase and describes a deployment expectation about session isolation that RFC 7752 Section 8 defines, not an obligation this document places on the encoder or decoder.	The isolation of BGP-LS peering sessions is also required to ensure that BGP-LS topology information (including the newly added BGP peering topology) is not advertised to an external BGP peering session outside an administrative domain.

Superseded

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