Keep the sensor identity usable
Keep the sensor identity usable
Keep the sensor identity usable
Narrated audio tour. The full transcript is below. These are schematic teaching states, not measured protocol or elapsed lifecycle time. Choose Reduced motion for a complete still at each beat. Explanations beyond the model remain in captions.
Full transcript — certificate-lifecycle (8 beats)
B1 — Outdoor sensor identity
You are the engineer responsible for an outdoor sensor that connects through a local gateway. Its certificate identifies the device to the service. If the certificate expires while the sensor is offline, the sensor can lose its ability to connect. Keeping that identity usable is your job.
Model caption: You maintain an outdoor sensor. Certificate expiry can interrupt its authenticated connection.
B2 — Issuer trust chain
A certificate links a device's name and public key to an issuer's signature. The issuer signs it. Trust follows a chain through an intermediate issuer to a trust anchor, a trusted starting point. The device's certificate belongs at the end of that chain.
Model caption: The issuer signs the device certificate. Its trust chain leads through an intermediate issuer to a trusted starting point.
B3 — Renew before expiry
Validity means the certificate has a start time and an end time. Renewal means obtaining a replacement before the current certificate expires. For your sensor, the renewal window leaves time to obtain that replacement, including time for another attempt if renewal fails.
Model caption: Validity has a start and an end. Obtain a replacement before expiry, allowing time for retries.
B4 — Renewal buffer
Use the model's certificate validity of one hundred eighty days and renewal at thirty percent remaining. Multiply one hundred eighty by thirty to get five thousand four hundred. Divide by one hundred to get fifty-four days. Rounding leaves fifty-four. The model takes the larger of three days and that result, so the renewal buffer is fifty-four days.
Model caption: 180 × 30 = 5400; 5400 ÷ 100 = 54; rounding gives 54; max(3, 54) = 54 days before expiry.
B5 — Derived calendar example
To find when renewal begins, subtract fifty-four from one hundred eighty. That gives one hundred twenty-six days after validity begins. The example therefore starts renewal with fifty-four days left before expiry. That time allows for retries and offline devices.
Model caption: Derived calendar example: 180 − 54 = 126 days after validity begins; 54 days remain for renewal.
B6 — Offline through expiry
Suppose your sensor stays offline throughout that renewal window and receives no replacement before expiry. Its current certificate expires, and authenticated connections can fail. The fifty-four-day buffer only helps if renewal succeeds in time. An offline sensor needs a renewal window that accounts for its absence.
Model caption: Suppose the sensor remains offline through the renewal window and expiry, with no replacement. Authenticated connections can fail.
B7 — Revocation status paths
The misconception is that a future expiry date guarantees acceptance. Revocation can invalidate a certificate before that date. A client can receive a signed list of revoked certificates, or query the status of a particular certificate. Both paths depend on clients checking fresh status information, so revocation can end trust while time remains.
Model caption: A future expiry date does not guarantee acceptance. Revocation may end trust sooner. Clients use a signed revocation list or a certificate-status query and need fresh status information.
B8 — Renew and end trust
Keep the sensor's identity usable by renewing before time runs out and ending trust when authority ends.
Model caption: Keep the sensor's identity usable by renewing before time runs out and ending trust when authority ends.