Partial

RFC 8092 - BGP Large Communities Attribute

Every requirement this repository extracted from RFC 8092, 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 ways57.1%4 of 7 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 reason42.9%3 of 7 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 7 gated MUSTs

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

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

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

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

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

Proven by a recorded break52.2%12 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

Audit verdicts7of 7 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 MUSTs7of 11 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 7 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 7 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 7 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 7 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 7 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	11
Gated MUST-level	7
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	23
Tagged units	23
Recorded audit verdicts	7
Discrimination records	12
Summary	`rfc/short/rfc8092.md`
Requirement shard	`rfc/requirements/rfc8092.md`
RFC text	`rfc/full/rfc8092.txt`

Enrolment

Enrolled: BGP Large Communities: seven MUST-level requirements over the LARGE_COMMUNITY codec (internal/core/bgp/attribute/community.go) and its RFC 7606 validator (internal/component/bgp/message/rfc7606.go:620). Both polarities: RFC8092-3-1 (duplicates not transmitted) via WriteTo/unique, RFC8092-3-2 (receiver silently removes redundant) via ParseLargeCommunities/deduplicate, RFC8092-6-2 (malformed if length not a non-zero multiple of 12) and RFC8092-6-4 (malformed -> treat-as-withdraw) via validateLargeCommunityAttr driven from ValidateUpdateRFC7606. Three {single-polarity: positive}: RFC8092-5-1 (canonical, no leading zeros) since strconv.AppendUint never emits them; RFC8092-6-1 (reserved ASN not malformed) since the validator inspects length only; RFC8092-6-3 (duplicates not malformed) since the parser deduplicates rather than rejecting. The 3-3/5-2/4-1 SHOULDs and 3-4 NOT RECOMMENDED are not gated.

What the public ledger says

Status: Partial

What the ledger says is covered:

LARGE_COMMUNITY parsing, validation, duplicate removal, JSON, and RFC 7606 length checks.

What the ledger says remains

RFC8092-4-1 aggregate-union behavior and its applicability remain unverified. Large Community codecs do not demonstrate that an aggregate contains the union of its contributing routes' communities; missing proof does not establish an absent feature or an exemption.

Coverage

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

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

Annotated (including scoped evidence) (3): RFC8092-5-1, RFC8092-6-1, RFC8092-6-3

Requirements

Requirement	Level	Section	Tests
`RFC8092-3-1`	Duplicate BGP Large Community values MUST NOT be transmitted. (Section 3)
	MUST NOT	3 - BGP Large Communities Attribute	positive`unit/verifyTestLargeCommunitiesWriteToNoDuplicates` positive`unit/verifyTestRFC8092PolicyAddOfPresentValueSentOnce` positive`unit/verifyTestRFC8092WriteRemovesRepeatedLargeCommunity` negative`unit/verifyTestLargeCommunities` negative`unit/verifyTestRFC8092WriteKeepsDistinctLargeCommunities` positive`functional/verifyrfc8092-large-community-no-repeat-egress.ci`
`RFC8092-3-2`	A receiving speaker MUST silently remove redundant BGP Large Community values from a BGP Large Community attribute. (Section 3)
	MUST	3 - BGP Large Communities Attribute	positive`unit/verifyTestLargeCommunitiesDeduplication` positive`unit/verifyTestRFC8092RedundantLargeCommunityRemovedBeforePropagation` negative`unit/verifyTestLargeCommunitiesParse` negative`unit/verifyTestRFC8092DistinctLargeCommunitiesKeptWhole`
`RFC8092-5-1`	Numbers MUST NOT contain leading zeros; a zero value MUST be represented with a single zero. (Section 5)
	MUST NOT	5 - Canonical Representation	positive`unit/verifyTestAppendText_LargeCommunityElement` negative`no test`no negative test {single-polarity}: the canonical rendering LargeCommunity.AppendText (internal/core/bgp/attribute/community.go:316) uses strconv.AppendUint, which never emits leading zeros and renders 0 as a single "0", so every value is canonical and there is no non-canonical rendering to assert as a negative
`RFC8092-6-1`	The BGP Large Communities Global Administrator field may contain any value, and a BGP Large Communities attribute MUST NOT be considered malformed if the Global Administrator field contains an unallocated, unassigned, or reserved ASN. (Section 6)
	MUST NOT	6 - Error Handling	positive`unit/verifyTestRFC8092LargeCommunityAnyGlobalAdministratorIsWellFormed` positive`unit/verifyTestRFC8092LargeCommunityValidReservedASN` negative`no test`no negative test {single-polarity}: the malformed check validateLargeCommunityAttr (internal/component/bgp/message/rfc7606.go:620) inspects the attribute length only and never the Global Administrator value, so a reserved or unallocated ASN is never treated as malformed and there is no ASN-based rejection to assert as a negative
`RFC8092-6-2`	o A BGP Large Communities attribute SHALL be considered malformed if the length of the BGP Large Communities Attribute value, expressed in octets, is not a non-zero multiple of 12. (Section 6)
	SHALL	6 - Error Handling	positive`unit/verifyTestRFC8092LargeCommunityLengthNotANonZeroMultipleOf12IsMalformed` positive`unit/verifyTestRFC8092LargeCommunityMalformedLength` negative`unit/verifyTestRFC8092LargeCommunityNonZeroMultipleOf12IsNotMalformed` negative`unit/verifyTestRFC8092LargeCommunityValidReservedASN`
`RFC8092-6-3`	o A BGP Large Communities attribute SHALL NOT be considered malformed due to presence of duplicate Large Community values. (Section 6)
	SHALL NOT	6 - Error Handling	positive`unit/verifyTestLargeCommunitiesDeduplication` positive`unit/verifyTestRFC8092DuplicateLargeCommunityIsNotMalformed` negative`no test`no negative test {single-polarity}: ParseLargeCommunities silently deduplicates and returns no error on duplicates (internal/core/bgp/attribute/community.go:422), and validateLargeCommunityAttr checks only length, so a duplicate is never treated as malformed and there is no duplicate-based rejection to assert as a negative
`RFC8092-6-4`	o A BGP UPDATE message with a malformed BGP Large Communities attribute SHALL be handled using the approach of "treat-as- withdraw" as described in Section 2 of [RFC7606]. (Section 6)
	SHALL	6 - Error Handling	positive`unit/verifyTestRFC8092LargeCommunityMalformedLength` positive`unit/verifyTestRFC8092MalformedLargeCommunityWithdrawsTheRoutes` negative`unit/verifyTestRFC8092LargeCommunityValidReservedASN` negative`unit/verifyTestRFC8092WellFormedLargeCommunityKeepsTheRoutes`
`RFC8092-3-3`	The Global Administrator field is intended to allow different ASes to define BGP Large Communities without collision. This field SHOULD be an ASN, in which case the Local Data Parts are to be interpreted as defined by the owner of the ASN. (Section 3)
	SHOULD	3 - BGP Large Communities Attribute	positive`no test`no positive test negative`no test`no negative test
`RFC8092-5-2`	BGP Large Communities SHOULD be represented in the canonical representation. (Section 5)
	SHOULD	5 - Canonical Representation	positive`no test`no positive test negative`no test`no negative test
`RFC8092-4-1`	If a range of routes is aggregated, then the resulting aggregate should have a BGP Large Communities attribute that contains all of the BGP Large Communities attributes from all of the aggregated routes. (Section 4)
	SHOULD	4 - Aggregation	positive`no test`no positive test negative`no test`no negative test
`RFC8092-3-4`	The use of Reserved ASNs (0 [RFC7607], 65535 and 4294967295 [RFC7300]) is NOT RECOMMENDED. (Section 3)
	NOT RECOMMENDED	3 - BGP Large Communities Attribute	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

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

`RFC8092-3-1`

Duplicate BGP Large Community values MUST NOT be transmitted. (Section 3)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Re-judged 2026-10-14 (independent auditor, D2). RFC 8092 Section 3: "Duplicate BGP Large Community values MUST NOT be transmitted." Producer: normalizeTransmittedUpdate's compactLargeCommunities, run by writeUpdateBody on every UPDATE write, raw included, so the adj-rib-out replay and forward-unchanged bytes the earlier verdict named now pass the same walk. Positive TestRFC8092WriteRemovesRepeatedLargeCommunity: [X,X,Y] sent as [X,Y], 20 values with one repeat (filter path) and 22 in Extended Length form sent with the repeat removed, first occurrence kept, lengths re-checked by sentLargeCommunities, on the raw, parsed, override and relay writers, zero allocations; TestRFC8092PolicyAddOfPresentValueSentOnce: received [X,Z] plus a policy body [X,Z,X,Y,Y] leaves as exactly [X,Z,Y], 36 octets, message length consistent; the .ci asserts the full relayed hex with the policy repeats gone; TestLargeCommunitiesWriteToNoDuplicates pins the local encoder. Negatives TestRFC8092WriteKeepsDistinctLargeCommunities (3, 16, 17, 20 distinct values leave byte for byte on every writer) and TestLargeCommunities, red on over-removal or reordering. Rejudged 2026-10-16 (independent reader) after the owner-approved withdrawal-Compatibility change: normalizeTransmittedUpdate gained an EncodingContext parameter read only by setWithdrawalCompatibility on an MP_UNREACH_NLRI. The edits in TestRFC8092WriteRemovesRepeatedLargeCommunity and TestRFC8092WriteKeepsDistinctLargeCommunities pass nil; their bodies carry no MP_UNREACH_NLRI, so the context is never read and the Large Community compaction and its exact-output assertions are unchanged. RFC 8092 Section 3: "Duplicate BGP Large Community values MUST NOT be transmitted." Verdict stands.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC8092WriteKeepsDistinctLargeCommunities`	unit/verify	revert, verified
negative	`TestLargeCommunities`	unit/verify	unproven
positive	`TestRFC8092PolicyAddOfPresentValueSentOnce`	unit/verify	revert, verified
positive	`TestRFC8092WriteRemovesRepeatedLargeCommunity`	unit/verify	revert, verified
positive	`TestLargeCommunitiesWriteToNoDuplicates`	unit/verify	unproven
positive	`rfc8092-large-community-no-repeat-egress.ci`	functional/verify	revert, verified

`RFC8092-3-2`

A receiving speaker MUST silently remove redundant BGP Large Community values from a BGP Large Community attribute. (Section 3)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Judge 2026-09-30 (R34, D-8 fixed). Producer reactor/rfc8092_large_community.go::removeRedundantLargeCommunities, called from publishBase: scan first (pairwise up to 16 values, seeded 64k-bit stack filter with exact confirm above), rebuild only on a repeat, keeping first occurrences in order, the peer's flags and header width, length rewritten, other attributes copied unchanged. Positive TestRFC8092RedundantLargeCommunityRemovedBeforePropagation: 2 copies (1-octet length) and 23 values with 3 repeats (extended length, filter path): no error, ActionNone, published and forwarded attribute hold each value once in first-occurrence order. Negative TestRFC8092DistinctLargeCommunitiesKeptWhole: 3 and 22 distinct values (filter path) published octet-equal to the received body and forwarded whole. Both have observed-red revert records. A non-multiple-of-12 value stays treat-as-withdraw (publishBase not reached). Attribute-package tags on ParseLargeCommunities remain unproven secondary units.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC8092DistinctLargeCommunitiesKeptWhole`	unit/verify	revert, verified
negative	`TestLargeCommunitiesParse`	unit/verify	unproven
positive	`TestRFC8092RedundantLargeCommunityRemovedBeforePropagation`	unit/verify	revert, verified
positive	`TestLargeCommunitiesDeduplication`	unit/verify	unproven

`RFC8092-5-1`

Numbers MUST NOT contain leading zeros; a zero value MUST be represented with a single zero. (Section 5)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Forbidden behaviour: a canonical rendering with a leading zero (e.g. 065001) or a zero rendered as anything but a single 0 (00, empty). TestAppendText_LargeCommunityElement asserts exact strings: {0,0,0} -> 0:0:0 goes red on either zero-clause violation, and 65001:100:200 and the 4294967295 case go red on any padding. LargeCommunity.String derives from AppendText. Single-polarity marker present.

Polarity	Test	Kind and tier	Proof state
positive	`TestAppendText_LargeCommunityElement`	unit/verify	unproven

`RFC8092-6-1`

The BGP Large Communities Global Administrator field may contain any value, and a BGP Large Communities attribute MUST NOT be considered malformed if the Global Administrator field contains an unallocated, unassigned, or reserved ASN. (Section 6)

Audit verdict: enforced (the tests do what the requirement demands), fresh. rejudge 2026-10-02 (c33 judge): {single-polarity: positive} is valid: the rule only forbids rejection and the validator has no Global Administrator path to refuse. TestRFC8092LargeCommunityAnyGlobalAdministratorIsWellFormed asserts RFC7606ActionNone through ValidateUpdateRFC7606 for reserved 0, 65535 and 4294967295, AS_TRANS 23456, documentation 64496, private 4200000000 and unallocated 1000000, each in a well-formed 12-octet value with ORIGIN, AS_PATH and NEXT_HOP present, so only the Global Administrator varies.

Polarity	Test	Kind and tier	Proof state
positive	`TestRFC8092LargeCommunityAnyGlobalAdministratorIsWellFormed`	unit/verify	revert, verified
positive	`TestRFC8092LargeCommunityValidReservedASN`	unit/verify	unproven

`RFC8092-6-2`

o A BGP Large Communities attribute SHALL be considered malformed if the length of the BGP Large Communities Attribute value, expressed in octets, is not a non-zero multiple of 12. (Section 6)

Audit verdict: enforced (the tests do what the requirement demands), fresh. rejudge 2026-10-02 (c33 judge): both clauses, both polarities. + TestRFC8092LargeCommunityLengthNotANonZeroMultipleOf12IsMalformed: lengths 0, 1, 11, 13, 23, 25 each draw TreatAsWithdraw with AttrCode 32 (zero and non-multiple). - TestRFC8092LargeCommunityNonZeroMultipleOf12IsNotMalformed: 12, 24, 36 (distinct values) draw ActionNone. HEAD units kept (length 10 / length 12). Judge break: validator condition replaced by length%12 > 1 (accepts 0, 1, 13, 25) turns only the new + red; every HEAD unit stays green, which was the gap.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC8092LargeCommunityNonZeroMultipleOf12IsNotMalformed`	unit/verify	revert, verified
negative	`TestRFC8092LargeCommunityValidReservedASN`	unit/verify	unproven
positive	`TestRFC8092LargeCommunityLengthNotANonZeroMultipleOf12IsMalformed`	unit/verify	revert, verified
positive	`TestRFC8092LargeCommunityMalformedLength`	unit/verify	unproven

`RFC8092-6-3`

o A BGP Large Communities attribute SHALL NOT be considered malformed due to presence of duplicate Large Community values. (Section 6)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Independent supplemental source rejudgment, 2026-10-06. RFC8092 Section 6: "A BGP Large Communities attribute SHALL NOT be considered malformed due to presence of duplicate Large Community values." Read both tagged units: reactor TestRFC8092DuplicateLargeCommunityIsNotMalformed and attribute TestLargeCommunitiesDeduplication. The reactor supplies one complete 12-byte value twice in a properly bounded attribute and otherwise valid ORIGIN, ASN4 AS_SEQUENCE 65002 and NEXT_HOP; teValidationSession explicitly negotiates ASN4. It requires exact RFC7606ActionNone, no error and one retained LARGE_COMMUNITY attribute. The decoder carrier requires no error and the exact two distinct values from three inputs including one duplicate. These assertions fail duplicate-triggered reset, treat-as-withdraw or attribute discard without a neighboring malformed-length confound. Traced message validator registry code 32 -> validateLargeCommunityAttr (nonzero multiple-of-12 only), enforceRFC7606 ActionNone -> publishBase -> removeRedundantLargeCommunities, and session_read.go continues non-error actions to delivery rather than dropping them. ParseLargeCommunities independently returns its deduplicated values. The existing single-positive annotation correctly avoids demanding a conforming duplicate-based rejection; malformed length is a different requirement. Current moved unit changes empty AS_PATH/rfc7311EBGPSession to a matching valid AS_SEQUENCE/ASN4 teValidationSession: fixture isolation repair in the current patch, not an assertion weakening or mere line movement. This judgment does not rejudge RFC8092-3-2 or carry forward its old D-8 finding as if unchanged; that separate row is outside this assignment. Prior enforced verdict retained; no tests or mutations run and no new defect found.

Polarity	Test	Kind and tier	Proof state
positive	`TestRFC8092DuplicateLargeCommunityIsNotMalformed`	unit/verify	revert, verified
positive	`TestLargeCommunitiesDeduplication`	unit/verify	unproven

`RFC8092-6-4`

o A BGP UPDATE message with a malformed BGP Large Communities attribute SHALL be handled using the approach of "treat-as- withdraw" as described in Section 2 of [RFC7606]. (Section 6)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Independent semantic rejudgment: RFC8092 Section 6: "A BGP UPDATE message with a malformed BGP Large Communities attribute SHALL be handled using the approach of "treat-as-withdraw" as described in Section 2 of [RFC7606]." Current TestRFC8092MalformedLargeCommunityWithdrawsTheRoutes asserts actual reactor handoff as withdrawn NLRI with no reachable NLRI/attributes, Established retained and no notification, paired with unchanged valid attribute/NLRI delivery. The caller-bypass mutation now fails that withdrawal oracle, not merely ValidateUpdateRFC7606 Action. The duplicate-values-as-malformed fault independently fails the valid duplicate carrier, providing legitimate admission discrimination; it does not create a new judgment for an unrequested duplicate requirement. Source and tagged consumers therefore protect the actual RFC7606 caller behavior, while unexecuted foreign FRR carriers remain pending. These are inspected scratch semantic executions, not canonical discrimination records. Current native record renewal/stamping remains parent-owned; no pending FRR carrier run, SRPM behavior, dataplane behavior, or full-RFC acceptance is inferred.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC8092LargeCommunityValidReservedASN`	unit/verify	unproven
negative	`TestRFC8092WellFormedLargeCommunityKeepsTheRoutes`	unit/verify	revert, verified
positive	`TestRFC8092LargeCommunityMalformedLength`	unit/verify	unproven
positive	`TestRFC8092MalformedLargeCommunityWithdrawsTheRoutes`	unit/verify	revert, verified

Extraction sign-off

Field	Value
Reviewer	ze-work agent, spec-rfcgate-6 phase 5, rfc8092
Signed off	2026-08-31
Register	rfc2119
Source	rfc/full/rfc8092.txt
Source fingerprint	e374b17f52bc7261
Record	rfc/extraction/rfc8092.json
Mapped sentences	7
Declined as scope	0
Relocated to a spec, which Ze OWES	0
Unclassified	0

Sections

Section	Name	Sites	Disposition	Reason
`front`	not stated	0	skipped (front-matter)	Title block, Abstract, Status of This Memo, Copyright Notice and Table of Contents. The Abstract restates the Introduction: the attribute is an extension to BGP-4 that signals opaque information within separate namespaces, and it suits all ASNs including four-octet ASNs. The Copyright Notice's lowercase 'Code Components extracted from this document must include Simplified BSD License text' binds whoever reuses the document's code components, not a BGP speaker.
`1`	Introduction	0	walked	Introduction. Indicative throughout: network operators attach communities to routes, an RFC 1997 community is a four-octet value whose halves are read as a two-octet ASN and a locally defined value, four-octet ASNs (RFC 6793) no longer fit that encoding, and the six-octet RFC 4360 Extended Community value cannot hold a four-octet ASN in both the Global Administrator and the Local Administrator sub-fields. The closing paragraph states what this document defines: an unordered set of one or more twelve-octet values, each a four-octet Global Administrator and two four-octet operator-defined fields. No sentence directs a speaker.
`2`	Requirements Language	0	walked	Requirements Language. The RFC 2119 key-words paragraph, which tells a reader how to read the other sections and binds no speaker; the derivation excludes it from the site inventory. It is the RFC 2119 form alone: unlike a post-RFC 8174 document it does not add the 'only when, and in all capitals' sentence, so this walk reads a lowercase modal elsewhere in the document on its own merits rather than as a key word.
`3`	BGP Large Communities Attribute	2	walked	BGP Large Communities Attribute. Two MUST-level sites, 3:1 and 3:2, the transmit and receive halves of the duplicate rule, both mapped below. The rest of the section is definitional or advisory. Definitional: the attribute is an optional transitive path attribute of variable length, all routes carrying it belong to the communities it specifies, each value is a 12-octet quantity laid out as a four-octet Global Administrator followed by Local Data Part 1 and Local Data Part 2, and 'There is no significance to the order in which twelve-octet Large Community Attribute values are encoded'. Those are indicative statements carried by the Wire Formats and Encoding Rules of rfc/short/rfc8092.md; none is written as an obligation, so none earns a checklist row. Advisory: 'This field SHOULD be an ASN' and 'The use of Reserved ASNs (0 [RFC7607], 65535 and 4294967295 [RFC7300]) is NOT RECOMMENDED'. Both carry capitalised keywords that are not MUST-level, so the rfc2119 site inventory does not count them; they are declared RFC8092-3-3 and RFC8092-3-4 and are listed unsourced here.
`4`	Aggregation	0	walked	Aggregation. One sentence, and its modal is lowercase: 'If a range of routes is aggregated, then the resulting aggregate should have a BGP Large Communities attribute that contains all of the BGP Large Communities attributes from all of the aggregated routes.' Under the rfc2119 register the site scan counts capitalised MUST-level keywords only, so it sees nothing here. The summary declares the sentence as the advisory row RFC8092-4-1, listed unsourced below.
`5`	Canonical Representation	1	walked	Canonical Representation. Defines the three-decimal colon form, in the order Global Administrator, Local Data 1, Local Data 2, and gives 64496:4294967295:2 and 64496:0:0 as examples. Its one MUST-level site is 5:1, mapped below. The closing 'BGP Large Communities SHOULD be represented in the canonical representation' is a capitalised advisory keyword rather than a MUST-level one, so the site scan does not count it; it is declared RFC8092-5-2 and listed unsourced here.
`6`	Error Handling	4	walked	Error Handling. The densest section of the document and the only one whose every sentence is normative: three bulleted SHALL-level rules and a closing MUST NOT. All four are sites, 6:1 through 6:4, and all four are mapped below to the four rows the summary declares from this section. The section carries no other sentence beyond its one-line lead-in, 'The error handling of BGP Large Communities is as follows'.
`7`	Security Considerations	0	walked	Security Considerations. No capitalised keyword and no site. Its one strong modal is lowercase and binds a trust model rather than a speaker: 'an AS relying on the BGP Large Communities attribute carried in BGP must have trust in every other AS in the path, as any intermediate AS in the path may have added, deleted, or altered the BGP Large Communities attribute', and the next sentence puts the mechanism providing that trust beyond the document's scope. The remainder is advice to operators: the attribute does not protect the integrity of a community value, a speaker can alter values in an UPDATE, securing that is the broader BGP security problem, and administrators are pointed at Section 11 of RFC 7454. Nothing here directs encoding, decoding or propagation, so there is nothing for a daemon to implement.
`8`	IANA Considerations	0	walked	IANA Considerations. One indicative sentence: 'IANA has assigned the value 32 (LARGE_COMMUNITY) in the "BGP Path Attributes" subregistry under the "Border Gateway Protocol (BGP) Parameters" registry.' Walked rather than skipped under the iana kind because it records an assignment already made, which Ze depends on to encode and recognise the attribute, rather than an action left for the registry to take. The value is carried by the Constants table of rfc/short/rfc8092.md. No obligation, so no id is read from here.
`9`	References	0	skipped (references)	References. The heading alone; its two subsections carry the entries.
`9.1`	Normative References: RFC 2119, RFC 4271, RFC 7606	0	skipped (references)	Normative References: RFC 2119, RFC 4271, RFC 7606.
`9.2`	not stated	0	skipped (references)	Informative References: RFC 1997, RFC 4360, RFC 6793, RFC 7300, RFC 7454, RFC 7607. The derived section span runs to the end of the document, so it also holds Acknowledgments, Contributors and Authors' Addresses. No sentence in the span states an obligation on a BGP speaker.

Excluded sentences

The walk over RFC 8092 declined no sentence: every site it found is mapped to a requirement.

Superseded

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