F15-LI: Yes

Rationale

RFC 9301 requires authenticated Map-Register processing and acceptance only of prefixes configured for the registering ETR. A bounded registration configuration uses a fixed set of ETR credentials and exact EID prefixes, ordinary replacement registrations and no merge requests. Each record has an eight-bit Locator Count. This provides a documentary bound on admitted prefix/locator records together with rejection of unauthorized registrations before mapping publication. The bound is a configuration inference, not a measured implementation property.

Assessment method

Primary documentation and pinned source review; no runtime experiment

Source context

RFC 9301 authenticated Map-Register and configured prefix admission

Outstanding qualification

Credit only registered mapping records in this configuration. Do not infer a bound on total server memory, parsing/HMAC cost, replay-tracking metadata, request queues or logs. Retain fixed credential/xTR provisioning; dynamic enrollment and merge registrations are outside the witness. A valid credential holder can still consume processing or replay-state resources. Open Map-Requests and data-plane traffic are not protected by registration authentication. Rate limits elsewhere in RFC 9301 are not used as a global CPU ceiling. No LISP-SEC, external firewall, runtime test or public-Internet deployment qualification is imported.

Public sources

Editorial evidence references

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

round551.html
round551-sources.json