-
Notifications
You must be signed in to change notification settings - Fork 0
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
+28
−27
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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}}. | ||||||
|
||||||
# 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}}. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
|
||||||
~~~~ DER | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
TSTInfo ::= SEQUENCE { | ||||||
|
@@ -210,8 +215,6 @@ TSTInfo ::= SEQUENCE { | |||||
extensions [1] IMPLICIT Extensions OPTIONAL } | ||||||
~~~~ | ||||||
|
||||||
--- back | ||||||
|
||||||
# Acknowledgements | ||||||
{:unnumbered} | ||||||
|
||||||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.