F25-CX: 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
For the approved F25 workload, configure bounded names and retain the producer trust key and static FIB. One CRC32C Interest and one ECDSA-SHA256 Content Object carrying 256 useful bytes each fit a conservative 1,024-byte CCNx envelope. The inventory includes validation metadata, signature, complete TLV wrappers and fixed header. Adding IPv4/UDP and Ethernet overhead to both packets, plus ARP request/reply after neighbor-cache expiry, gives at most 2,348 endpoint byte-times, below 65,536.
Assessment method
Constructive documentary byte bound
Source context
CCNx wire format and complete endpoint accounting
Outstanding qualification
Constructive configuration witness: complete Name TLVs at most 64 bytes, secp256k1 signature at most 72 bytes, bounded public-key/KeyLink metadata and no certificate fetch because the trust key remains provisioned. No DNS, TLS or new security wrapper. Static FIB configuration is retained; learned ARP is rebuilt. This does not qualify a complete executable CCNx ECDSA codec or establish a bound for arbitrary names/certificate chains. No runtime measurement.
Public sources
- https://www.rfc-editor.org/rfc/rfc8609.html
- https://www.rfc-editor.org/rfc/rfc8569.html
- https://www.rfc-editor.org/rfc/rfc826.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round314-budget.json
- round314-sources.json