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

Clarify how mime type relates to voucher #64

Merged
merged 2 commits into from
Dec 14, 2024
Merged

Clarify how mime type relates to voucher #64

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
650a066
clarify what Media Type is used for
mcr Sep 10, 2024
d1eea21
adjusted text to clarify what is encoded
mcr Dec 14, 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
15 changes: 11 additions & 4 deletions draft-ietf-anima-rfc8366bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -450,8 +450,8 @@ owner.
The voucher informs the pledge which entity it should consider to be
its owner.

This document defines a voucher that is a JSON-encoded or CBOR-encoded instance of the
YANG module defined in {{voucher-yang-module}}.
This document defines a voucher that is JSON-encoded, and CMS signed encoding of the
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think this might be sort of confusing, we won't encode a yang module, but the data modeled by a yang module.

data defined in the YANG module {{voucher-yang-module}}.

This format is described here as a practical basis for some uses (such
as in NETCONF), but more to clearly indicate what vouchers look like
Expand All @@ -460,8 +460,15 @@ This description also serves to validate the YANG data model.

{{RFC8366}} defined a media type and a filename extension for the
CMS-encoded JSON type.
Which type of voucher is expected is signaled (where possible) in the form of a MIME
Content-Type, an HTTP Accept: header, or more mundane methods like use of a filename extension when a voucher is transferred on a USB key.
The media types for JOSE format vouchers is defined in {{jBRSKI}} and the COSE format voucher is defined in {{cBRSKI}}.

The Media Type is used by the Pledge (to the Registrar) and from the Registrar (to the MASA) to signal what format of voucher is expected.
Other aspects of the voucher, such as it being nonce-less or which kind of pinned anchor is used is not part of the Media type.

Only the format of voucher that is expected is signaled in the form of a (MIME) Media
Content-Type in the HTTP Accept: header.

For vouchers stored/transferred via methods like a USB storage device (USB key), then the voucher format is usually signaled by a filename extension.

## Tree Diagram {#voucher-tree-diagram}

Expand Down
Loading