Back to matrix

F09-BL: No

Rationale

RFC 8966 section 3.6 defines selection of one route per prefix for forwarding and advertisement. Alternate candidates support repair, not concurrent useful paths for one communication. The declared IPv6/UDP/Babel composition selects no additional multipath data-plane policy or transport. It therefore does not meet F09. This is not a prohibition on multipath extensions or independently configured IPv6 forwarding. The IP column explicitly includes per-packet next-hop rotation; that policy is not inherited merely because Babel also runs over IP. Different destinations using different routes do not establish this criterion.

Assessment method

Primary specification analysis of the declared composition; no runtime test

Source context

RFC 8966 sections 2.2 and 3.6, Appendix A.3

Public sources