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

Thomas and Henk interactive session #4

Merged
merged 2 commits into from
May 4, 2022
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
19 changes: 11 additions & 8 deletions draft-birkholz-rats-epoch-markers.md
Original file line number Diff line number Diff line change
@@ -39,10 +39,11 @@ author:
email: cabo@tzi.org

normative:
RFC3161:
RFC3161: TSA

informative:
I-D.ietf-rats-architecture: rats-arch
I-D.ietf-rats-reference-interaction-models: rats-models

venue:
mail: rats@ietf.org
@@ -91,16 +92,16 @@ Epoch Markers also provide the option to include (concise) remote attestation ev
# Epoch IDs

The RATS architecture introduces the concept of Epoch IDs that mark certain events during remote attestation procedures ranging from simple handshakes to rather complex interactions including elaborate freshness proofs.
Epoch Markers are a solution that includes the lessons learned from TSAs and provides several means to identify a new freshness epoch as illustrated by the RATS architecture.
The Epoch Markers defined in this document are a solution that includes the lessons learned from TSAs, the concept of Epoch IDs and provides several means to identify a new freshness epoch. Some of these methods are introduced and discussed in Section 10.3 by the RATS architecture {{-rats-arch}}.
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Suggested change
The Epoch Markers defined in this document are a solution that includes the lessons learned from TSAs, the concept of Epoch IDs and provides several means to identify a new freshness epoch. Some of these methods are introduced and discussed in Section 10.3 by the RATS architecture {{-rats-arch}}.
The Epoch Markers defined in this document are a solution that includes the lessons learned from TSAs, the concept of Epoch IDs and provides several means to identify a new freshness epoch. Some of these methods are introduced and discussed in {{Section 10.3 of -rats-arch}}.


# Interaction Models

The interaction models illustrated in this section are derived from the RATS Reference Interaction Models.
In general there are three of them:

* unsolicited distribution (e.g., via uni-directional methods, such as broad- or multicasting from Epoch Bells)
* solicited distribution (e.g., via a subscription to Epoch Bells)
* ad-hoc requests (e.g., via challenge-response requests addressed at Epoch Bells)
* ad-hoc requests (e.g., via challenge-response requests addressed at Epoch Bells), corresponding to Section 7.1 in {{-rats-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}}

# Epoch Marker CDDL

@@ -188,7 +189,11 @@ multi-nonce-list = [+ multi-nonce]
strictly-monotonically-increasing-counter = uint ; counter context? per issuer? per indicator?
~~~~

--- back

## RFC 3161 TSTInfo
As a reference for the definition of TST-info-based-on-CBOR-time-tag the code block below depects the original layout of the TSTInfo structure from {{-TSA}}.
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Suggested change
As a reference for the definition of TST-info-based-on-CBOR-time-tag the code block below depects the original layout of the TSTInfo structure from {{-TSA}}.
As a reference for the definition of TST-info-based-on-CBOR-time-tag the code block below depicts the original layout of the TSTInfo structure from {{-TSA}}.



~~~~ DER
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Suggested change
~~~~ DER
~~~~ ASN.1

TSTInfo ::= SEQUENCE {
@@ -210,8 +215,6 @@ TSTInfo ::= SEQUENCE {
extensions [1] IMPLICIT Extensions OPTIONAL }
~~~~

--- back

# Acknowledgements
{:unnumbered}