Technology aggregate

BGP-LS

BGP Link-State distribution. The RFCs whose summary names the bgp-ls aggregate, with their mandatory and optional coverage.

All profiles · All RFCs

Mandatory65.6%82 of 125 (65.6%)

MUST, MUST NOT, REQUIRED, SHALL and SHALL NOT rows of the walked RFCs that a recorded test break proves.

Optional5.5%4 of 73 (5.5%)

MAY, NOT RECOMMENDED, OPTIONAL, RECOMMENDED, SHOULD and SHOULD NOT rows, counted the same way.

Mandatory ceiling87.2%109 of 125 (87.2%); excluded: Not applicable (classification can be revisited): 16 of 125 (12.8%)

Attainable mandatory rows under current classifications, over the unchanged total.

Optional ceiling100.0%73 of 73 (100.0%)

Attainable optional rows under current classifications, over the unchanged total.

Not walked0of 6 RFCs

RFCs with no valid extraction sign-off: their rows count in neither figure.

Mandatory registernot completeevery row proven, none unwalked

A profile is complete only when it requires at least one RFC and none of them is unwalked.

Mandatory ceiling: 109 of 125 (87.2%); excluded: Not applicable (classification can be revisited): 16 of 125 (12.8%). Optional ceiling: 73 of 73 (100.0%). Lowest mandatory ceiling: rfc7752 15 of 26 (57.7%). Lowest optional ceiling: rfc7752 26 of 26 (100.0%). Ceilings describe current classifications, not an immutable Linux maximum. Not-applicable and feature-declined classifications can be revisited. Every gap remains work Ze owes.

Tree

Roots first: an RFC sits one level above the highest level of the RFCs it builds on, and the RFCs of one citation cycle share a level. Each bar is the share of that figure's rows a recorded break proves; the ceiling below it shows attainable rows under current classifications. An RFC that is not walked shows an empty bar and no figure or ceiling.

Level 12

RFCTitleMandatoryOptional
RFC 9552 Distribution of Link-State and Traffic Engineering Information Using BGP 43 of 59 (72.9%)Ceiling: 54 of 59 (91.5%); excluded: Not applicable (classification can be revisited): 5 of 59 (8.5%) 1 of 30 (3.3%)Ceiling: 30 of 30 (100.0%)

Level 13

RFCTitleMandatoryOptional
RFC 7752 North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP 8 of 26 (30.8%)Ceiling: 15 of 26 (57.7%); excluded: Not applicable (classification can be revisited): 11 of 26 (42.3%) 0 of 26 (0.0%)Ceiling: 26 of 26 (100.0%)
RFC 8571 BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions no rowsCeiling: no rows no rowsCeiling: no rows

Level 14

RFCTitleMandatoryOptional
RFC 9085 Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing 9 of 9 (100.0%)Ceiling: 9 of 9 (100.0%) 3 of 5 (60.0%)Ceiling: 5 of 5 (100.0%)

Level 15

RFCTitleMandatoryOptional
RFC 9086 Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing BGP Egress Peer Engineering 7 of 11 (63.6%)Ceiling: 11 of 11 (100.0%) 0 of 9 (0.0%)Ceiling: 9 of 9 (100.0%)

Level 16

RFCTitleMandatoryOptional
RFC 9514 Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) 15 of 20 (75.0%)Ceiling: 20 of 20 (100.0%) 0 of 3 (0.0%)Ceiling: 3 of 3 (100.0%)