From 13403317c100daaad14d897ddc8366660f123efb Mon Sep 17 00:00:00 2001 From: ID Bot Date: Fri, 30 Aug 2024 18:16:07 +0000 Subject: [PATCH] Script updating gh-pages from 87a1d12. [ci skip] --- ...irkholz-cose-tsa-tst-header-parameter.html | 841 ++++++++---------- ...birkholz-cose-tsa-tst-header-parameter.txt | 240 +++-- 2 files changed, 476 insertions(+), 605 deletions(-) diff --git a/legenda/draft-birkholz-cose-tsa-tst-header-parameter.html b/legenda/draft-birkholz-cose-tsa-tst-header-parameter.html index 18ca99a..a4e1637 100644 --- a/legenda/draft-birkholz-cose-tsa-tst-header-parameter.html +++ b/legenda/draft-birkholz-cose-tsa-tst-header-parameter.html @@ -1170,16 +1170,13 @@

2. Modes of use

There are two different modes of composing COSE protection and timestamping.

+

The diagrams in this section illustrate the processing flow of the specified modes. +For simplicity, only the COSE_Sign1 processing is shown. +Similar diagrams for COSE_Sign can be derived by allowing multiple SK_cose boxes and replacing the label [signature] with [signatures].

@@ -1227,62 +1227,195 @@

The original datum becomes the payload of the signed COSE message.

-
+

The message imprint sent to the TSA (Section 2.4 of [RFC3161]) MUST be the hash of the payload field of the COSE signed object.

+
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - payload - Sig_structure - COSE_Sign/COSE_Sign1 - TSA - TST + Signer + TSA + datum + hash + L + timestamp + messageImprint + nonce + SK_tsa + phdr + SK_cose + ... + TST + Sign1 + uhdr + ... + [signature] + [phdr] + [payload] + [uhdr] + rfc3161-ttc + COSE + Legenda + data + key + operation + label + clock + [ + ] + L - +
Figure 1: -Timestamp, then COSE (TTC) +Timestamp, then COSE (TCC)
-

The message imprint sent to the TSA (Section 2.4 of [RFC3161]) MUST be the hash of the payload field of the COSE signed object.

@@ -1297,42 +1430,185 @@

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - COSE_Sign/COSE_Sign1 - TST - signatures/signature - TSA + Signer + phdr + datum + SK_cose + ... + Sign1 + TSA + hash + L + messageImprint + timestamp + nonce + [signature] + [phdr] + SK_tsa + uhdr + ... + TST + [payload] + [uhdr] + rfc3161-ctt + COSE + Legenda + data + key + operation + label + clock + [ + ] + L
@@ -1500,389 +1776,12 @@

-
-
-

-Appendix A. Diagrams -

-

The diagrams in this appendix illustrate the processing flow of the modes specified in Section 2.1 and Section 2.2 respectively.

-

For simplicity, only the COSE_Sign1 processing is shown. -Similar diagrams for COSE_Sign can be derived by allowing multiple SK_cose boxes and replacing the label [signature] with [signatures].

-
-
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Signer - TSA - datum - hash - L - timestamp - messageImprint - nonce - SK_tsa - phdr - SK_cose - ... - TST - Sign1 - uhdr - ... - [signature] - [phdr] - [payload] - [uhdr] - rfc3161-ttc - COSE - data - key - operation - label - clock - Legenda - [ - ] - L - - -
-
-
Figure 3: -Timestamp then COSE -
-
-
-
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Signer - phdr - datum - SK_cose - ... - Sign1 - TSA - hash - L - messageImprint - timestamp - nonce - [signature] - [phdr] - SK_tsa - uhdr - ... - TST - [payload] - [uhdr] - rfc3161-ctt - COSE - data - key - operation - label - clock - Legenda - [ - ] - L - - -
-
-
Figure 4: -COSE then Timestamp -
-
-
-
-
+

Acknowledgments

-

The editors would like to thank +

The editors would like to thank Carl Wallace, Leonard Rosenthol, Michael B. Jones, @@ -1890,11 +1789,11 @@

Orie Steele, and Steve Lasker -for their reviews and comments.

+for their reviews and comments.

-
+

Contributors

@@ -1908,7 +1807,7 @@

-
+

Authors' Addresses

diff --git a/legenda/draft-birkholz-cose-tsa-tst-header-parameter.txt b/legenda/draft-birkholz-cose-tsa-tst-header-parameter.txt index c4d7030..5d6a98f 100644 --- a/legenda/draft-birkholz-cose-tsa-tst-header-parameter.txt +++ b/legenda/draft-birkholz-cose-tsa-tst-header-parameter.txt @@ -75,7 +75,6 @@ Table of Contents 5. Security Considerations 6. IANA Considerations 7. Normative References - Appendix A. Diagrams Acknowledgments Contributors Authors' Addresses @@ -104,6 +103,12 @@ Table of Contents There are two different modes of composing COSE protection and timestamping. + The diagrams in this section illustrate the processing flow of the + specified modes. For simplicity, only the COSE_Sign1 processing is + shown. Similar diagrams for COSE_Sign can be derived by allowing + multiple SK_cose boxes and replacing the label [signature] with + [signatures]. + 2.1. Timestamp then COSE (TTC) Figure 1 shows the case where a datum is first digested and submitted @@ -118,21 +123,58 @@ Table of Contents * The original datum becomes the payload of the signed COSE message. - .---------. .---------------. .----------------------. - | payload +------------->| Sig_structure +---->| COSE_Sign/COSE_Sign1 | - '----+----' '---------------' '----------------------' - | ^ - | .---. | - | | | .-----. | - '--->| TSA +---->| TST +---' - | | '-----' - '---' - - Figure 1: Timestamp, then COSE (TTC) - The message imprint sent to the TSA (Section 2.4 of [RFC3161]) MUST be the hash of the payload field of the COSE signed object. + .--------. .-----. + | Signer | | TSA | + +--------+----------------------------------------. +-----+---------. + | .-------. .----. | | .-. | + | | datum +------------->| hash | | | | L | | + | '-+---+-' '-+--' | | '+' | + | | | | | | | | + | | | | | | v | + | | | v | | .---------. | + | | | .----------------. | | | timestamp | | + | | | | messageImprint +------+->| '---------' | + | | | '----------------' | | ^ | + | | | | | | | + | | | .-------. | | .---+----. | + | | | | nonce +---------------+->| / SK_tsa / | + | | | '-------' | | '--------' | + | | | | '-------+-------' + | | | .------------------. | | + | | | | phdr | | | + | | | .---------. | .-----. .-----. | | | + | | | / SK_cose / | | ... | | TST |<-----+---------' + | | | '----+----' | '-----' '-----' | | + | | | | '--+--+------------' | + | | | v | | | + | | | .-----. | | | + | | '-->| Sign1 |<-----' | .---------. | + | | '--+--' | | uhdr | | + | | | | | .-----. | | + | | | | | | ... | | | + | | [signature] [phdr] | '-----' | | + | | | | '----+----' | + | | | | | | + '---+------------+--------------+---------+-------' + | | | | + [payload] v v [uhdr] + | .------------------. | + '-------->| rfc3161-ttc COSE |<-----' + '------------------' + .---------. + | Legenda | + .-----------------------------------------------------------+---------+ + | data key operation label clock | + | .------. .-----. .---------. .-. | + | | | / / | | [ ] | L | | + | '------' '-----' '---------' '-' | + '---------------------------------------------------------------------' + + Figure 1: Timestamp, then COSE (TCC) + 2.2. COSE then Timestamp (CTT) Figure 2 shows the case where the signature(s) field of the signed @@ -143,21 +185,57 @@ Table of Contents This mode is utilized when a record of the timing of the signature operation is desired. - .----------------------. .-----. - | COSE_Sign/COSE_Sign1 |<--------+ TST | - '----+-----------------' '-----' - | ^ - v | - .----------------------. | - | signatures/signature | | - '----+-----------------' | - | .---. | - | | | | - '------------------->| TSA +---' - | | - '---' - - Figure 2: COSE, then Timestamp (CTT) +.--------. +| Signer | ++--------+------------------------------------------. +| .-----------. | +| | phdr | | +| .-------. .---------. | .-----. | | +| | datum | / SK_cose / | | ... | | | +| '--+-+--' '----+----' | '-----' | | +| | | | '-+-+-------' | +| | | v | | | +| | | .-----. | | | +| | '--->| Sign1 |<-----' | | +| | '-+-+-' | | .-----. +| | | | | .----. | | TSA | +| | | '----------)--->| hash | | +-----+---------. +| | | | '-+--' | | .-. | +| | | | | | | | L | | +| | | | v | | '+' | +| | | | .----------------. | | | | +| | | | | messageImprint +-+->| v | +| | | | '----------------' | | .---------. | +| | | | | | | timestamp | | +| | | | .-------. | | '---------' | +| | | | | nonce +----------+->| ^ | +| | | | '-------' | | | | +| | | | | | .---+----. | +| | [signature] [phdr] | | / SK_tsa / | +| | | | | | '--------' | +| | | | .-----------------. | | | +| | | | | uhdr | | '-------+-------' +| | | | | .-----. .-----. | | | +| | | | | | ... | | TST |<--+---------' +| | | | | '-----' '-----' | | +| | | | '--------+--------' | +| | | | | | +'----+----------+-------------+----------+----------' + | | | | + [payload] v v [uhdr] + | .------------------. | + '------>| rfc3161-ctt COSE |<-----' + '------------------' + .---------. + | Legenda | +.-----------------------------------------------------------+---------+ +| data key operation label clock | +| .------. .-----. .---------. .-. | +| | | / / | | [ ] | L | | +| '------' '-----' '---------' '-' | +'---------------------------------------------------------------------' + + Figure 2: COSE, then Timestamp (CTT) In this context, timestamp tokens are similar to a countersignature made by the TSA. @@ -303,112 +381,6 @@ Table of Contents DOI 10.17487/RFC9052, August 2022, . -Appendix A. Diagrams - - The diagrams in this appendix illustrate the processing flow of the - modes specified in Section 2.1 and Section 2.2 respectively. - - For simplicity, only the COSE_Sign1 processing is shown. Similar - diagrams for COSE_Sign can be derived by allowing multiple SK_cose - boxes and replacing the label [signature] with [signatures]. - - .--------. .-----. - | Signer | | TSA | - +--------+----------------------------------------. +-----+---------. - | .-------. .----. | | .-. | - | | datum +------------->| hash | | | | L | | - | '-+---+-' '-+--' | | '+' | - | | | | | | | | - | | | | | | v | - | | | v | | .---------. | - | | | .----------------. | | | timestamp | | - | | | | messageImprint +------+->| '---------' | - | | | '----------------' | | ^ | - | | | | | | | - | | | .-------. | | .---+----. | - | | | | nonce +---------------+->| / SK_tsa / | - | | | '-------' | | '--------' | - | | | | '-------+-------' - | | | .------------------. | | - | | | | phdr | | | - | | | .---------. | .-----. .-----. | | | - | | | / SK_cose / | | ... | | TST |<-----+---------' - | | | '----+----' | '-----' '-----' | | - | | | | '--+--+------------' | - | | | v | | | - | | | .-----. | | | - | | '-->| Sign1 |<-----' | .---------. | - | | '--+--' | | uhdr | | - | | | | | .-----. | | - | | | | | | ... | | | - | | [signature] [phdr] | '-----' | | - | | | | '----+----' | - | | | | | | - '---+------------+--------------+---------+-------' - | | | | - [payload] v v [uhdr] - | .------------------. | - '-------->| rfc3161-ttc COSE |<-----' - '------------------' - - - data key operation label clock - .------. .-----. .---------. .-. - Legenda | | / / | | [ ] | L | - '------' '-----' '---------' '-' - - Figure 3: Timestamp then COSE - -.--------. -| Signer | -+--------+------------------------------------------. -| .-----------. | -| | phdr | | -| .-------. .---------. | .-----. | | -| | datum | / SK_cose / | | ... | | | -| '--+-+--' '----+----' | '-----' | | -| | | | '-+-+-------' | -| | | v | | | -| | | .-----. | | | -| | '--->| Sign1 |<-----' | | -| | '-+-+-' | | .-----. -| | | | | .----. | | TSA | -| | | '----------)--->| hash | | +-----+---------. -| | | | '-+--' | | .-. | -| | | | | | | | L | | -| | | | v | | '+' | -| | | | .----------------. | | | | -| | | | | messageImprint +-+->| v | -| | | | '----------------' | | .---------. | -| | | | | | | timestamp | | -| | | | .-------. | | '---------' | -| | | | | nonce +----------+->| ^ | -| | | | '-------' | | | | -| | | | | | .---+----. | -| | [signature] [phdr] | | / SK_tsa / | -| | | | | | '--------' | -| | | | .-----------------. | | | -| | | | | uhdr | | '-------+-------' -| | | | | .-----. .-----. | | | -| | | | | | ... | | TST |<--+---------' -| | | | | '-----' '-----' | | -| | | | '--------+--------' | -| | | | | | -'----+----------+-------------+----------+----------' - | | | | - [payload] v v [uhdr] - | .------------------. | - '------>| rfc3161-ctt COSE |<-----' - '------------------' - - - data key operation label clock - .------. .-----. .---------. .-. -Legenda | | / / | | [ ] | L | - '------' '-----' '---------' '-' - - Figure 4: COSE then Timestamp - Acknowledgments The editors would like to thank Carl Wallace, Leonard Rosenthol,