Research note / Cycle 022
Two receipts, no decision
A desk exercise and a toy dispute policy show why two qualifying receipts that name different records must be withheld rather than ranked.
Two receipts that each qualify
Lumen’s custody specification is still unsigned and was never sent, and no outside party holds an early commitment for the office. On February 13 Chen and Haddad took the question left by A receipt dated too late one step further: what should the office do if two receipts both look sound and name different records? At an internal desk they wrote four hypothetical cards. Alpha and beta each precede a change, are marked as held outside the office and carry stated time evidence and key control, but they name different digests. An internal clone is marked as held inside the office. A late record is marked as dated after the change. They then wrote a one-page table naming who could lift a hold on restoration if the cards conflicted.
No key was generated, no digest of a Lumen record was computed, no time-stamp request was made and no outside party was approached.
A rule that will not pick
The cards were then run through a software predicate. A receipt qualifies only if it precedes the change, carries time evidence, is held outside the office and has key control. The five scenarios in the table give three outcomes. One qualifying receipt is eligible, but only within the toy policy. Two qualifying receipts with different digests are withheld as a conflict, with neither preferred by date or by name. Receipts that fail a condition leave the claim unsupported. Removing any one of the four conditions from alpha makes it ineligible in every case.
Time evidence and key control are Boolean inputs. The predicate does not check a time-stamp token or a signature, so an eligible result means only that the stated inputs satisfied the rule. It is a test of the rule, not of any Lumen system. The five scenarios also never present an ineligible receipt that names a different digest, such as an inside copy that disagrees with alpha. Under this predicate such a record would simply not count. Whether it should instead raise a conflict, as a divergent view does for transparency logs, is not tested.
What the references do and do not say
RFC 3161 defines a time-stamp protocol and describes a time-stamp as supporting an assertion that a datum existed before a particular time, to be used with signature evidence and a stated policy. It does not make the signer of the datum the right one, and it does not say which of two conflicting records an office should trust. RFC 9162, an experimental Certificate Transparency specification, notes that a log presenting conflicting views to different parties can be detected by clients comparing what they were shown, a technique it calls gossip and leaves undefined. Comparison can reveal a dispute; neither source defines who settles one. Neither describes a Lumen log, procedure or implementation.
What the desk decided
The desk adopted withheld as its working disposition for conflicting qualifying receipts and wrote that neither author, nor the deputy role, may release a restoration while a conflict stands. Release would need a party outside the office that Lumen has not identified. The custody specification remains unsigned and unsent. No restoration, outside contact or real time-stamp request took place.
Results at a glance
| Constructed dispute | Receipts presented | Disposition |
|---|---|---|
| one eligible | alpha | eligible in toy policy only |
| two conflicting eligible | alpha, beta | withheld: conflict |
| two ineligible | internal clone, late record | unsupported |
| one eligible and one ineligible | alpha, late record | eligible in toy policy only |
| no receipt | none | unsupported |
External research and methods
- Certificate Transparency Version 2.0 · Ben Laurie, Eran Messeri and Rob Stradling · RFC 9162, Experimental (2021-12). Section 11.3: misbehaving logs, conflicting views and the undefined technique of gossip.
- Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) · C. Adams, P. Cain, D. Pinkas and R. Zuccherato · RFC 3161, Standards Track (updated by RFC 5816) (2001-08). Section 1: a time-stamp supports an assertion that a datum existed before a particular time.