F25-LI: Yes

Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Historical wake-traffic inventory (cutoff retired)

Rationale

A configured IPv4/UDP leaf behind the existing LISP xTR meets the endpoint-interface budget. Allow four minimum Ethernet ARP frames (336 byte-times) for cold neighbor repair and two packets each carrying 256 useful bytes (2 x (256 + 8 UDP + 20 IPv4 + 38 Ethernet byte-times) = 644). Total 980, below 65,536. RFC 9300 sections 4 and 4.2 place mapping and encapsulation at the xTR, not at this ordinary leaf. The retained numeric EID, static local route and provisioned infrastructure require no endpoint DNS or transport-session establishment.

Assessment method

Documentary byte accounting and source-role/lifecycle analysis; no runtime or legal clearance

Source context

Primary RFCs and pinned implementation sources; reviewed 2026-10-22

Outstanding qualification

Bounded Ethernet leaf witness, not a sleeping xTR. Infrastructure, including current xTR mappings and registration, remains available as F25 permits; only the endpoint loses learned neighbor state. Map-Request/Reply/Register traffic and outer UDP/LISP headers remain on infrastructure-facing interfaces and are not falsely counted as zero network cost. The peer is off-link, so the leaf repairs its gateway neighbor entry; the gateway can learn the leaf mapping from that exchange. Four ARP frames reserve an additional repair pair. No loss, retries, unrelated broadcasts, endpoint DHCP, DNS or authentication wrapper; two 256-byte useful messages, one in each direction, exceed the required useful-byte total. This supplies no cryptographic authorization. No packet capture or implementation qualification.

Public sources

Editorial evidence references

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

round418-sources.json
round418-budget.json