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.

Sign up for GitHub

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

consistently use term Pledge #78

Open
wants to merge 1 commit into
base: registrar-uses-information
Choose a base branch
from
Open

consistently use term Pledge #78

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions draft-ietf-anima-rfc8366bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -292,7 +292,7 @@ Assertion Basis:
the imprint (this is distinct from the voucher signature that
protects the voucher itself). This includes
manufacturer-asserted ownership verification, assured
logging operations, or reliance on Pledge endpoint behavior
logging operations, or reliance on Pledge behavior
such as secure root of trust
of measurement. The join registrar uses this information to make a determination as to whether to accept the Pledge intot he network.
Only some methods are normatively defined in this
Expand All @@ -314,7 +314,7 @@ Anti-Replay Protections:
A number of onboarding scenarios can be met using differing
combinations of this information. All scenarios address the primary
threat of an on-path active attacker (or MiTM) impersonating the registrar.
This would gain control over the Pledge device.
This would gain control over the Pledge.
The following combinations are "types" of vouchers:

| | Assertion || Registrar ID || Validity |
Expand Down
Loading