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

Bearer vouchers #66

Merged
merged 2 commits into from
Dec 16, 2024
Merged

Bearer vouchers #66

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4b465bd
update voucher-request to refer to new name for pinned-domain-cert
mcr Sep 10, 2024
206979f
some additional explanation of why bearer vouchers are out of scope
mcr Oct 4, 2024
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
14 changes: 9 additions & 5 deletions draft-ietf-anima-rfc8366bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -315,7 +315,7 @@ Owner Audit | X | X | X | | X | X |
|--
Owner ID | | X | X | X | X | |
|--
Bearer out-of-scope| X| | wildcard | wildcard | optional|opt|
Bearer voucher| X| | wildcard | wildcard | optional|opt|
|==

NOTE: All voucher types include a 'Pledge ID serial-number'
Expand Down Expand Up @@ -354,10 +354,14 @@ Bearer Voucher:
: A Bearer Voucher is named after the inclusion of a registrar ID
wildcard. Because the registrar identity is not indicated, this
voucher type must be treated as a secret and protected from exposure
as any 'bearer' of the voucher can claim the Pledge
device. Publishing a nonceless bearer voucher effectively turns the
specified Pledge into a "TOFU" device with minimal mitigation
against MiTM registrars. Bearer vouchers are out of scope.
as any 'bearer' of the voucher can claim the pledge
device. This variation is included in the above description in order to clearly
how other voucher types differ.
This specification does not support bearer vouchers at this time.
There are other specifications in the industry which are equivalent though.
Publishing a nonceless bearer voucher effectively turns the
specified pledge into a "TOFU" device with minimal mitigation
against MiTM registrars. Bearer vouchers are therefore out of scope.

# Changes since RFC8366

Expand Down
3 changes: 1 addition & 2 deletions ietf-voucher-request.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,8 +94,7 @@ RFCEDITOR: please replace XXXX with the RFC number assigned.
mandatory false;
}

refine "voucher/pinned-domain-cert" {
mandatory false;
refine "voucher/pinning/pinned-domain-cert" {
description "A pinned-domain-cert field
is not valid in a voucher request, and
any occurrence MUST be ignored";
Expand Down
Loading