From 650a06608be66735a3d67be9d610b03cb9fde28e Mon Sep 17 00:00:00 2001 From: Michael Richardson Date: Tue, 10 Sep 2024 12:06:56 -0400 Subject: [PATCH 1/2] clarify what Media Type is used for --- draft-ietf-anima-rfc8366bis.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/draft-ietf-anima-rfc8366bis.md b/draft-ietf-anima-rfc8366bis.md index 630428a..090f87c 100644 --- a/draft-ietf-anima-rfc8366bis.md +++ b/draft-ietf-anima-rfc8366bis.md @@ -450,7 +450,7 @@ 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 +This document defines a voucher that is JSON-encoded, and CMS signed encoding of the YANG module defined in {{voucher-yang-module}}. This format is described here as a practical basis for some uses (such @@ -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} From d1eea216bb7394c42dec260212b24f6f7896492d Mon Sep 17 00:00:00 2001 From: Michael Richardson Date: Fri, 13 Dec 2024 22:01:51 -0500 Subject: [PATCH 2/2] adjusted text to clarify what is encoded --- draft-ietf-anima-rfc8366bis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-anima-rfc8366bis.md b/draft-ietf-anima-rfc8366bis.md index 090f87c..f1413fe 100644 --- a/draft-ietf-anima-rfc8366bis.md +++ b/draft-ietf-anima-rfc8366bis.md @@ -451,7 +451,7 @@ The voucher informs the pledge which entity it should consider to be its owner. This document defines a voucher that is JSON-encoded, and CMS signed encoding of the -YANG module defined in {{voucher-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