diff --git a/index.html b/index.html index 185ffd3..83ed684 100644 --- a/index.html +++ b/index.html @@ -24,6 +24,14 @@

Editor's drafts for main branch of some-abstract

+ + + + + + +
CHEplain textdiff with main
+ + diff --git a/some-abstract/draft-steele-cose-hash-envelope.txt b/some-abstract/draft-steele-cose-hash-envelope.txt new file mode 100644 index 0000000..7bc930d --- /dev/null +++ b/some-abstract/draft-steele-cose-hash-envelope.txt @@ -0,0 +1,261 @@ + + + + +Network Working Group O. Steele +Internet-Draft Transmute +Intended status: Standards Track 15 November 2023 +Expires: 18 May 2024 + + + COSE Hash Envelope + draft-steele-cose-hash-envelope-latest + +Abstract + + This document defines new COSE header parameters in support of a + mechanism that uses hashes of detached payload as the COSE payload, + which enables faster signature validation for detached payload as the + availability of the original payload is not required for signature + validation. Additionally, hints about the detached payload's content + format and availability are defined. + +About This Document + + This note is to be removed before publishing as an RFC. + + The latest revision of this draft can be found at + https://OR13.github.io/draft-steele-cose-hash-envelope/draft-steele- + cose-hash-envelope.html. Status information for this document may be + found at https://datatracker.ietf.org/doc/draft-steele-cose-hash- + envelope/. + + Discussion of this document takes place on the CBOR Object Signing + and Encryption Working Group mailing list (mailto:cose@ietf.org), + which is archived at https://mailarchive.ietf.org/arch/browse/cose/. + Subscribe at https://www.ietf.org/mailman/listinfo/cose/. + + Source for this draft and an issue tracker can be found at + https://github.com/OR13/draft-steele-cose-hash-envelope. + +Status of This Memo + + This Internet-Draft is submitted in full conformance with the + provisions of BCP 78 and BCP 79. + + Internet-Drafts are working documents of the Internet Engineering + Task Force (IETF). Note that other groups may also distribute + working documents as Internet-Drafts. The list of current Internet- + Drafts is at https://datatracker.ietf.org/drafts/current/. + + Internet-Drafts are draft documents valid for a maximum of six months + and may be updated, replaced, or obsoleted by other documents at any + time. It is inappropriate to use Internet-Drafts as reference + material or to cite them other than as "work in progress." + + This Internet-Draft will expire on 18 May 2024. + +Copyright Notice + + Copyright (c) 2023 IETF Trust and the persons identified as the + document authors. All rights reserved. + + This document is subject to BCP 78 and the IETF Trust's Legal + Provisions Relating to IETF Documents (https://trustee.ietf.org/ + license-info) in effect on the date of publication of this document. + Please review these documents carefully, as they describe your rights + and restrictions with respect to this document. Code Components + extracted from this document must include Revised BSD License text as + described in Section 4.e of the Trust Legal Provisions and are + provided without warranty as described in the Revised BSD License. + +Table of Contents + + 1. Introduction + 1.1. Signed Hashes + 1.1.1. Protected Header + 1.1.2. Attached Payload + 1.1.3. Detached Payload + 1.2. Encrypted Hashes + 2. Conventions and Definitions + 3. Security Considerations + 3.1. Choice of Hash Function + 4. IANA Considerations + 4.1. COSE Header Algorithm Parameters + 4.2. Named Information Hash Algorithm Registry + 5. Normative References + Acknowledgments + Author's Address + +1. Introduction + + COSE defined detached payloads in [RFC9052] in Section 2. However, + in order to verify a detached payload the payload content needs to + availble. + + This is challenging for large payload, which can not be easily be + transported. + + This draft addresses this challenge by describing a simply way to + protect hashes of payloads while maintaining information about their + content type. + +1.1. Signed Hashes + +1.1.1. Protected Header + + TBD 0 (typ), TBD 1 (payload hash alg) and TBD 2 (content type of the + preimage of the payload) MUST be present in the protected header and + MUST NOT be present in the unprotected header. + + TBD 0 will be assinged by [I-D.ietf-cose-typ-header-parameter], it + represents the content type of the code envelope, which includes the + protected header and payload. + + { + / Algorithm / + 1: -35, + / Key identifier / + 4: h'75726e3a...32636573', + / typ of the envelope / + TBD 0: application/hashed+cose + / Hash algorithm of the payload / + TBD 1: 1 / sha-256 / + / cty of the preimage of the payload / + TBD 2: application/jwk+json + } + +1.1.2. Attached Payload + + The payload MAY be attached. + + 18( / COSE Sign 1 / + [ + h'a4013822...3a616263', / Protected / + {} / Unprotected / + h'317cedc7...c494e772', / Payload / + h'15280897...93ef39e5' / Signature / + ] + ) + +1.1.3. Detached Payload + + The payload MAY be detached. + + 18( / COSE Sign 1 / + [ + h'a4013822...3a616263', / Protected / + {} / Unprotected / + nil, / Detached payload / + h'15280897...93ef39e5' / Signature / + ] + ) + +1.2. Encrypted Hashes + + Should we define this? + +2. Conventions and Definitions + + The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", + "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and + "OPTIONAL" in this document are to be interpreted as described in + BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all + capitals, as shown here. + + TBD 0: will be assinged by [I-D.ietf-cose-typ-header-parameter], it + represents the content type of the code envelope, which includes + the protected header and payload. + + TBD 1: the hash algorithm used to generate the hash about the + payload. + + TBD 2: the content type of the payload the hash represents. + +3. Security Considerations + + TODO Security + +3.1. Choice of Hash Function + + It is RECOMMENDED to align the strength of the chosen hash function + to the strength of the chosen signature algorithm. For example, when + signing with ECDSA using P-256 and SHA-256, use SHA-256 to hash the + payload. + +4. IANA Considerations + +4.1. COSE Header Algorithm Parameters + + * Name: payload hash algorithm + + * Label: TBD_1 + + * Value type: int + + * Value registry: https://www.iana.org/assignments/named- + information/named-information.xhtml + + * Description: Hash algorithm used to produce the payload. + +4.2. Named Information Hash Algorithm Registry + + * Name: SHAKE256 + + * Label: TBD_2 + + * Value type: int + + * Value registry: https://www.iana.org/assignments/named- + information/named-information.xhtml + + * Description: SHAKE256 a described in + https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.202.pdf + + * Name: ASCON128 + + * Label: TBD_3 + + * Value type: int + + * Value registry: https://www.iana.org/assignments/named- + information/named-information.xhtml + + * Description: ASCON128 a described in + https://csrc.nist.gov/CSRC/media/Projects/lightweight- + cryptography/documents/round-2/spec-doc-rnd2/ascon-spec-round2.pdf + +5. Normative References + + [I-D.ietf-cose-typ-header-parameter] + Jones, M. B. and O. Steele, "COSE "typ" (type) Header + Parameter", Work in Progress, Internet-Draft, draft-ietf- + cose-typ-header-parameter-01, 7 November 2023, + . + + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . + + [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC + 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, + May 2017, . + + [RFC9052] Schaad, J., "CBOR Object Signing and Encryption (COSE): + Structures and Process", STD 96, RFC 9052, + DOI 10.17487/RFC9052, August 2022, + . + +Acknowledgments + + The following individuals provided input into the final form of the + document: Carsten Bormann, Henk Birkholz, Antoine Delignat-Lavaud, + Cedric Fournet. + +Author's Address + + Orie Steele + Transmute + Email: orie@transmute.industries diff --git a/some-abstract/index.html b/some-abstract/index.html new file mode 100644 index 0000000..d0249aa --- /dev/null +++ b/some-abstract/index.html @@ -0,0 +1,45 @@ + + + + OR13/draft-steele-cose-hash-envelope some-abstract preview + + + + +

Editor's drafts for some-abstract branch of OR13/draft-steele-cose-hash-envelope

+ + + + + + +
CHEplain textsame as main
+ + +