Skip to content

v0.24.0

Latest

Choose a tag to compare

@github-actions github-actions released this 06 Nov 17:33
· 3 commits to main since this release
v0.24.0
b46d7b7

Breaking changes

  • Afi and Safi gain the EVPN family and ExtendedCommunity gains MacMobility: Afi::L2vpn (25) and Safi::Evpn (70) now parse instead of failing, and the MAC Mobility extended community (type 0x06, sub-type 0x00) parses into ExtendedCommunity::MacMobility { sticky, sequence } instead of a raw 8-byte blob. ExtendedCommunity::Raw now reports the registered type of an undecoded community (Evpn for the other EVPN sub-types) rather than Unknown. Downstream exhaustive matches on these enums need a new arm. (#355)

Added

  • EVPN NLRI support (RFC 7432, RFC 9136): MP_REACH_NLRI and MP_UNREACH_NLRI for AFI 25 / SAFI 70 decode into Nlri::evpn_nlris, one EvpnNlri per route with its route distinguisher and a route-type-specific body: type 2 (MAC/IP advertisement: ESI, Ethernet tag, MAC, optional IP, label), type 3 (inclusive multicast), and type 5 (IP prefix). Route types 1 and 4 keep their octets in EvpnRoutePayload::Raw, and an EVPN end-of-RIB marker decodes to an empty list. Until now an EVPN BMP feed produced only AttributeValue::Raw and no fields at all. The encoder writes the same routes back, so MrtRecord::try_from(&BmpMessage) keeps converting EVPN route monitoring messages, and text output renders an ANNOUNCED (EVPN) / WITHDRAWN (EVPN) section instead of dropping them. (#355)
  • MAC Mobility extended community encoder: ExtendedCommunity::MacMobility re-encodes to the 8 wire octets, so a decoded EVPN route survives a decode/encode round trip of its communities. (#355)

Fixed

  • Withdrawals are no longer lost when the ADD-PATH guess cannot frame an NLRI block that starts with the default route: parse_nlri_list took a leading 0x00 byte as an ADD-PATH path identifier, kept that reading for the rest of the block, and retried at the failure position, so a withdrawn list beginning with 0.0.0.0/0 or ::/0 dropped prefixes in the middle of the list, and a list that failed both ways left the message with none of those withdrawals: the classic IPv4 fields came back as an empty list plus a MalformedNlri finding, and a failing MP_UNREACH_NLRI attribute was kept raw with an OptionalAttributeError finding. The ADD-PATH guess is now all-or-nothing for the block, and a failed guess re-parses the block from its start, which keeps ADD-PATH data wrapped in a non-ADD-PATH record (issue #31) decoding with its path ids. A block whose bytes frame under both readings is still decoded as ADD-PATH, so a short non-ADD-PATH list of that shape keeps the old reading. In RIPE RIS 2026-02 updates files a 1020-withdrawal message and a 166-withdrawal message returned nothing, and a 627-withdrawal message kept its element count while losing 11 real prefixes and inventing 7. (#360)