You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Review parser coverage as the IETF 126 IDR drafts mature. This is a tracking issue only: do not implement an Internet-Draft as a stable public API without separately assessing its maturity and the relevant IANA assignments.
The following agenda drafts define or extend BGP wire formats that bgpkit-parser does not currently decode into dedicated models. Some encodings may be retained as generic/raw data, but that is not semantic support.
Explicitly out of parser scope unless that changes
The agenda also includes base-spec/YANG, operational/deployment, route-selection, formatting, and threat-model documents. They do not add a parser wire encoding requiring a bgpkit-parser model at their current revisions.
Follow-up
For each draft that reaches RFC status, open or update a focused implementation issue with its final code points, normative wire format, parser/encoder expectations, and test vectors.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Scope
Review parser coverage as the IETF 126 IDR drafts mature. This is a tracking issue only: do not implement an Internet-Draft as a stable public API without separately assessing its maturity and the relevant IANA assignments.
The following agenda drafts define or extend BGP wire formats that
bgpkit-parserdoes not currently decode into dedicated models. Some encodings may be retained as generic/raw data, but that is not semantic support.Core BGP
draft-braet-idr-bgp-source-selective-attr-00— SOURCE_SELECTIVE path attribute.draft-ietf-idr-bgp-bfd-strict-mode-18— BFD Strict-Mode capability.draft-krierhorn-idr-upa-03— Unreachable Prefix Announcement.draft-zhang-idr-portid-ec-02— PORT extended community.BGP-LS and SR Policy
draft-ietf-idr-bgp-ls-bgp-only-fabric-05— BGP-only-fabric BGP-LS NLRI/TLV extensions.draft-tong-idr-bgp-ls-sav-rule-05— SAV-rule BGP-LS information.draft-ietf-idr-sr-p2mp-policy-01— P2MP SR Policy signaling.draft-li-idr-bgp-sr-policy-bfd-extension-02— SR Policy BFD sub-TLVs.draft-li-idr-bgp-nrp-01— Network Resource Partition BGP extensions.draft-gong-idr-inter-domain-srv6-flex-algo-01— inter-domain SRv6 Flex-Algo signaling.Tunnel encapsulation and FlowSpec
draft-rosomakho-idr-bgp-masque-tunnel-00— MASQUE tunnel types and URI Template/ALPN sub-TLVs.draft-ietf-idr-fsv2-ip-basic-07— FlowSpec v2 base NLRI and action encoding.draft-kao-idr-bitwise-ip-filters-05— FlowSpec bitwise IP-filter components.draft-he-idr-bgp-flowspec-ifit-03— FlowSpec IFIT actions.draft-lin-idr-flowspec-quic-00— FlowSpec QUIC component.draft-wu-idr-flowspec-redirect-group— FlowSpec redirect load-balancing-group community.draft-song-idr-flowspec-classid-filter-01— FlowSpec ClassID component.Explicitly out of parser scope unless that changes
The agenda also includes base-spec/YANG, operational/deployment, route-selection, formatting, and threat-model documents. They do not add a parser wire encoding requiring a
bgpkit-parsermodel at their current revisions.Follow-up
For each draft that reaches RFC status, open or update a focused implementation issue with its final code points, normative wire format, parser/encoder expectations, and test vectors.
Source: IETF 126 IDR agenda
Beta Was this translation helpful? Give feedback.
All reactions