Back to matrix

D04-BL: No

Rationale

RFC 8966 router identifiers distinguish routing sources and accompany advertised prefixes; they are not ordinary-user communication identities. The selected IPv6/ICMPv6 data plane still delivers using interface addresses. Babel supplies route discovery/selection rather than an additional independently controlled user identity over existing addresses.

Assessment method

Documentary selected-stack classification; no new network execution

Source context

Official specifications and versioned project documentation retrieved 2026-10-15; retained document hashes

Outstanding qualification

Choosing another router-id does not satisfy D04. Namespaces or delegated interface administration can isolate network configuration, but do not add the missing user-identity mechanism to this stack. No TLS, application authentication or Babel security extension is silently added. This No does not negate D01 ordinary endpoint use.

Public sources

• https://www.rfc-editor.org/rfc/rfc8966.html
• https://www.rfc-editor.org/rfc/rfc4291.html#section-2.1

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

• round240-sources.json