Technology aggregate

BGP core

BGP base protocol, capabilities, attributes, and error handling. The RFCs whose summary names the bgp-core aggregate, with their mandatory and optional coverage.

All profiles · All RFCs

Use case: BGP performance testing with Ze

Use case: ExaBGP Migration

Mandatory55.6%193 of 347 (55.6%)

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

Optional7.0%8 of 114 (7.0%)

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

Mandatory ceiling96.5%335 of 347 (96.5%); excluded: Optional feature not offered (classification can be revisited): 1 of 347 (0.3%); Not applicable (classification can be revisited): 11 of 347 (3.2%)

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

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

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

Not walked0of 21 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: 335 of 347 (96.5%); excluded: Optional feature not offered (classification can be revisited): 1 of 347 (0.3%); Not applicable (classification can be revisited): 11 of 347 (3.2%). Optional ceiling: 114 of 114 (100.0%). Lowest mandatory ceiling: rfc8654 10 of 12 (83.3%). Lowest optional ceiling: rfc2545 2 of 2 (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 3

RFCTitleMandatoryOptional
RFC 4271 A Border Gateway Protocol 4 (BGP-4) 80 of 133 (60.2%)Ceiling: 126 of 133 (94.7%); excluded: Not applicable (classification can be revisited): 7 of 133 (5.3%) 3 of 34 (8.8%)Ceiling: 34 of 34 (100.0%)

Level 4

RFCTitleMandatoryOptional
RFC 2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing 3 of 5 (60.0%)Ceiling: 5 of 5 (100.0%) 0 of 2 (0.0%)Ceiling: 2 of 2 (100.0%)
RFC 5492 Capabilities Advertisement with BGP-4 2 of 9 (22.2%)Ceiling: 8 of 9 (88.9%); excluded: Not applicable (classification can be revisited): 1 of 9 (11.1%) 0 of 7 (0.0%)Ceiling: 7 of 7 (100.0%)
RFC 6608 Subcodes for BGP Finite State Machine Error 0 of 3 (0.0%)Ceiling: 3 of 3 (100.0%) no rowsCeiling: no rows
RFC 8212 Default External BGP (EBGP) Route Propagation Behavior without Policies 0 of 2 (0.0%)Ceiling: 2 of 2 (100.0%) 0 of 1 (0.0%)Ceiling: 1 of 1 (100.0%)
RFC 9072 Extended Optional Parameters Length for BGP OPEN Message 5 of 9 (55.6%)Ceiling: 9 of 9 (100.0%) 1 of 3 (33.3%)Ceiling: 3 of 3 (100.0%)
RFC 9687 Border Gateway Protocol 4 (BGP-4) Send Hold Timer 3 of 13 (23.1%)Ceiling: 13 of 13 (100.0%) 0 of 7 (0.0%)Ceiling: 7 of 7 (100.0%)

Level 5

RFCTitleMandatoryOptional
RFC 4760 Multiprotocol Extensions for BGP-4 5 of 6 (83.3%)Ceiling: 6 of 6 (100.0%) 1 of 11 (9.1%)Ceiling: 11 of 11 (100.0%)

Level 6

RFCTitleMandatoryOptional
RFC 2918 Route Refresh Capability for BGP-4 3 of 6 (50.0%)Ceiling: 6 of 6 (100.0%) 1 of 5 (20.0%)Ceiling: 5 of 5 (100.0%)
RFC 4486 Subcodes for BGP Cease NOTIFICATION Message 0 of 1 (0.0%)Ceiling: 1 of 1 (100.0%) 0 of 10 (0.0%)Ceiling: 10 of 10 (100.0%)
RFC 6793 (cycle with rfc5668) BGP Support for Four-Octet Autonomous System (AS) Number Space 20 of 30 (66.7%)Ceiling: 30 of 30 (100.0%) 0 of 6 (0.0%)Ceiling: 6 of 6 (100.0%)
RFC 7311 The Accumulated IGP Metric Attribute for BGP 13 of 22 (59.1%)Ceiling: 22 of 22 (100.0%) 0 of 4 (0.0%)Ceiling: 4 of 4 (100.0%)
RFC 7911 Advertisement of Multiple Paths in BGP 9 of 9 (100.0%)Ceiling: 9 of 9 (100.0%) 0 of 4 (0.0%)Ceiling: 4 of 4 (100.0%)

Level 7

RFCTitleMandatoryOptional
RFC 6286 Autonomous-System-Wide Unique BGP Identifier for BGP-4 0 of 4 (0.0%)Ceiling: 4 of 4 (100.0%) 1 of 1 (100.0%)Ceiling: 1 of 1 (100.0%)
RFC 7313 Enhanced Route Refresh Capability for BGP-4 5 of 11 (45.5%)Ceiling: 10 of 11 (90.9%); excluded: Optional feature not offered (classification can be revisited): 1 of 11 (9.1%) 0 of 6 (0.0%)Ceiling: 6 of 6 (100.0%)
RFC 7606 (cycle with rfc4364, rfc4659, rfc4798, rfc6368, rfc8277, rfc8950) Revised Error Handling for BGP UPDATE Messages 28 of 53 (52.8%)Ceiling: 52 of 53 (98.1%); excluded: Not applicable (classification can be revisited): 1 of 53 (1.9%) 0 of 4 (0.0%)Ceiling: 4 of 4 (100.0%)
RFC 8950 (cycle with rfc4364, rfc4659, rfc4798, rfc6368, rfc7606, rfc8277) Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next Hop 3 of 6 (50.0%)Ceiling: 6 of 6 (100.0%) 0 of 2 (0.0%)Ceiling: 2 of 2 (100.0%)

Level 8

RFCTitleMandatoryOptional
RFC 5549 Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop 3 of 6 (50.0%)Ceiling: 6 of 6 (100.0%) 0 of 3 (0.0%)Ceiling: 3 of 3 (100.0%)
RFC 7607 Codification of AS 0 Processing 0 of 5 (0.0%)Ceiling: 5 of 5 (100.0%) no rowsCeiling: no rows
RFC 8654 Extended Message Support for BGP 9 of 12 (75.0%)Ceiling: 10 of 12 (83.3%); excluded: Not applicable (classification can be revisited): 2 of 12 (16.7%) 1 of 4 (25.0%)Ceiling: 4 of 4 (100.0%)
RFC 9774 Deprecation of AS_SET and AS_CONFED_SET in BGP 2 of 2 (100.0%)Ceiling: 2 of 2 (100.0%) no rowsCeiling: no rows