E01-BL: Yes
Rationale
The IETF 101 public implementation report identifies BIRD as a from-scratch implementation and reports BIRD 1.6/2.0 interoperating with deployed babeld for base IPv6 routing. BIRD 2.0 already parsed mandatory sub-TLVs and discarded unicast Hellos. RFC 8966 Appendix F explicitly preserves a compatible base mode when unicast/unscheduled Hellos and extensions using mandatory sub-TLVs are not sent. This closes the date-only gap for the reported common IPv6 routing behavior; final publication after the test does not erase that evidence. Independent code lineages and a public implementer report satisfy E01 for this bounded function.
Assessment method
Public implementer-report review and normative compatibility mapping; no new interop test
Source context
IETF 101 BIRD implementation report and RFC 8966 compatibility rules
Outstanding qualification
Credit base IPv6 route exchange only, using the common multicast-Hello mode without incompatible extensions. The slides identify BIRD releases but do not pin an exact babeld commit or supply packet captures. This is implementer-reported interoperability, not an independently repeated test, full RFC conformance, data-plane performance or execution of the study-specific ULA hierarchy and filters. It does not resolve G05/E04/E05 or authentication-extension behavior.
Public sources
- https://www.ietf.org/proceedings/101/slides/slides-101-babel-babel-in-bird-implementation-status-00.pdf
- https://www.rfc-editor.org/rfc/rfc8966.html#appendix-F
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round228-sources.json