F15-IL: Yes
Rationale
For existing ILNPv6 sessions, RFC 6743 requires the correct Nonce Destination Option before a Locator Update is accepted and passed to ICMP processing. An accepted update replaces the correspondent's previous locator set. The nonzero eight-bit locator count bounds each replacement list to 255 entries. This supplies early rejection of forged off-path updates and a bounded replacement-state effect; repeated updates do not append successive advertised lists indefinitely.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
RFC 6743 nonce admission and replacement of bounded locator-update lists
Outstanding qualification
Credit only the Locator Update boundary for an existing correspondent and unpredictable established nonce. This is not an aggregate ILCC, TCP backlog or whole-process memory bound. Parsing, nonce lookup and optional logging still consume resources; temporary old/new lists and other locator-learning paths are not measured. The nonce is visible to an on-path observer and does not provide strong peer identity. A party knowing it can issue repeated valid updates. Initial session admission, SYN floods, on-path attackers and rate guarantees are outside this Yes. No IPsec, CGA, external limiter or runtime qualification is imported.
Public sources
- https://www.rfc-editor.org/rfc/rfc6743.html#section-6
- https://www.rfc-editor.org/rfc/rfc6743.html#section-2
- https://www.rfc-editor.org/rfc/rfc6743.html#section-4
- https://www.rfc-editor.org/rfc/rfc6741.html#section-11
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round552.html
- round552-sources.json