tracking: missing semantic support for published BGP RFCs

[digizeph]

Scope

Track published BGP RFCs for which bgpkit-parser lacks dedicated semantic parsing. Raw retention and generic TLV framing are valuable compatibility behavior, but do not constitute typed RFC support.

Recognized path attributes retained raw

• RFC 5543 — Traffic Engineering attribute (type 24); resolved by #322.
• RFC 6368 — ATTR_SET (type 128); requires recursive nested-attribute parsing and encoding.
• RFC 6514 — PMSI_TUNNEL (type 22) and PE_DISTINGUISHER_LABELS (type 27).
• RFC 8205 — BGPsec_PATH (type 33).

Extended-community semantic decoding

• RFC 10005 — Link Bandwidth Extended Community; resolved by #319.

Recent published protocol extensions

• RFC 9815 — BGP-LS SPF: new SAFI and BGP-LS NLRI/attribute TLVs.
• RFC 9830 — SR Policy SAFI and Tunnel Encapsulation sub-TLVs.
• RFC 9831 — additional SR Policy segment sub-TLVs.
• RFC 9832 — Classful Transport Planes SAFI and extended communities.
• RFC 9857 — SR Policy information in BGP-LS NLRI/TLVs.
• RFC 9871 — BGP CAR SAFIs, NLRI/TLVs, and extended communities.

Not a standalone parser target

RFC 9819 clarifies SRv6 service signaling in RFC 9252; dedicated support depends on broader RFC 9252/EVPN support.

Documentation convention

The crate-level RFC list documents typed support. RFCs whose attributes are only framed and raw-retained are listed separately under “Wire Framing and Raw Retention”, rather than represented as fully supported.