Epoch Markers
draft-birkholz-rats-epoch-markers-08
| Document | Type |
Replaced Internet-Draft
(rats WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Henk Birkholz , Thomas Fossati , Wei Pan , Carsten Bormann | ||
| Last updated | 2024-10-08 (Latest revision 2024-07-22) | ||
| Replaced by | draft-ietf-rats-epoch-markers | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-rats-epoch-markers | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines Epoch Markers as a way to establish a notion of freshness among actors in a distributed system. Epoch Markers are similar to "time ticks" and are produced and distributed by a dedicated system, the Epoch Bell. Systems that receive Epoch Markers do not have to track freshness using their own understanding of time (e.g., via a local real-time clock). Instead, the reception of a certain Epoch Marker establishes a new epoch that is shared between all recipients.
Authors
Henk Birkholz
Thomas Fossati
Wei Pan
Carsten Bormann
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)