Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epoch Markers as Handles #25

Merged
merged 3 commits into from
Jul 10, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
addresses #23
  • Loading branch information
henkbirkholz committed Jul 6, 2023
commit 7567d81a4b2a0fed59793c683133eb9ad15cd133
2 changes: 2 additions & 0 deletions draft-birkholz-rats-epoch-markers.md
Original file line number Diff line number Diff line change
@@ -135,6 +135,8 @@ In general, there are three interaction models:
* unsolicited distribution (e.g., via uni-directional methods, such as broad- or multicasting from Epoch Bells), corresponding to Section 7.2 in {{-rats-models}}
* solicited distribution (e.g., via a subscription to Epoch Bells), corresponding to Section 7.3 in {{-rats-models}}

In all three interaction models, Epoch Markers can be used as content for the generic information element 'handle'. Handles are most useful to establish freshness in unsolicited and solicited distribution by the Epoch Bell. In ad-hoc requests, the handle is typically a nonce generated by the challenger. In consequence, a fresh Epoch Marker used as a handle in ad-hoc requests must be available to the challenger. While this strategy can provide additional capabilities to challenge-response attestation (e.g., limiting the number of ad-hoc requests by a Verifier), it can also be an overhead that can be avoided by using a nonce as the handle.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In all three interaction models, Epoch Markers can be used as content for the generic information element 'handle'. Handles are most useful to establish freshness in unsolicited and solicited distribution by the Epoch Bell. In ad-hoc requests, the handle is typically a nonce generated by the challenger. In consequence, a fresh Epoch Marker used as a handle in ad-hoc requests must be available to the challenger. While this strategy can provide additional capabilities to challenge-response attestation (e.g., limiting the number of ad-hoc requests by a Verifier), it can also be an overhead that can be avoided by using a nonce as the handle.
In all three interaction models, Epoch Markers can be used as content for the generic information element 'handle'. Handles are most useful to establish freshness in unsolicited and solicited distribution by the Epoch Bell. In ad-hoc requests, the handle is typically a nonce generated by the challenger. As a consequence, a fresh Epoch Marker used as a handle in ad-hoc requests must be available to the challenger. While this strategy can provide additional capabilities to challenge-response attestation (e.g., limiting the number of ad-hoc requests by a Verifier), it can also be an overhead that can be avoided by using a nonce as the handle.


# Epoch Marker Structure

At the top level, an Epoch Marker is a CBOR array with a header carrying an optional veracity proof about the Epoch Bell and a payload.