Skip to content

Commit

Permalink
minor fixes to replay privacy (#167)
Browse files Browse the repository at this point in the history
Co-authored-by: Laurence Lundblade <lgl@securitytheory.com>
  • Loading branch information
laurencelundblade and Laurence Lundblade authored Feb 17, 2022
1 parent 8090055 commit 17959f3
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion draft-ietf-rats-eat.md
Original file line number Diff line number Diff line change
Expand Up @@ -2155,7 +2155,7 @@ Implementers should consider laws and regulations governing the transmission of
Implementers should consider using location management facilities offered by the operating system on the entity generating the attestation.
For example, many mobile phones prompt the user for permission when before sending location data.

## Replay Protection and Privacy (#replayprivacyconsiderations)
## Replay Protection and Privacy {#replayprivacyconsiderations}

EAT offers 2 primary mechanisms for token replay protection (also sometimes
known as token "freshness"): the cti/jti claim and the nonce claim. The cti/jti claim
Expand Down Expand Up @@ -2753,3 +2753,5 @@ no new claims have been added.
* Remove security-level from early allocation

* Add boot odometer claim

* Add privacy considerations for replay protection

0 comments on commit 17959f3

Please sign in to comment.