Just to confirm I've read COSE Hash Envelope again, and still think it provides 
a useful alternative to detached payloads, notably for SCITT. I support 
advancing it to WGLC.

Thanks, -Cédric

________________________________
From: Amaury Chamayou <[email protected]>
Sent: Wednesday, May 21, 2025 13:33
To: Steve Lasker <[email protected]>; Ivaylo Petrov 
<[email protected]>; [email protected] 
<[email protected]>; cose <[email protected]>
Cc: Birkholz, Henk <[email protected]>; Orie Steele 
<[email protected]>
Subject: [EXTERNAL] [COSE] Re: COSE Hash Envelope - request for WGLC

You don't often get email from [email protected]. 
Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Empty email to give Cédrick a pointer he can reply to 🙂
________________________________
From: Amaury Chamayou <[email protected]>
Sent: 31 March 2025 09:48
To: Steve Lasker <[email protected]>; Ivaylo Petrov 
<[email protected]>; [email protected] 
<[email protected]>; cose <[email protected]>
Cc: Birkholz, Henk <[email protected]>; Orie Steele 
<[email protected]>
Subject: Re: COSE Hash Envelope - request for WGLC

I have neither questions nor objections, but want to express support for moving 
to WGLC!

Amaury
________________________________
From: Steve Lasker <[email protected]>
Sent: 31 March 2025 09:28
To: Ivaylo Petrov <[email protected]>; [email protected] 
<[email protected]>; cose <[email protected]>
Cc: Birkholz, Henk <[email protected]>; Orie Steele 
<[email protected]>
Subject: [EXTERNAL] [COSE] COSE Hash Envelope - request for WGLC


Hi folks,

At 122, we presented draft 4 of COSE Hash 
Envelope<https://www.ietf.org/archive/id/draft-ietf-cose-hash-envelope-04.html>.
 We discussed proceeding with WGLC after we made a clarification of 
Pre-image-content-type (Label 259) and payload location (label 260).



These have been applied and submitted as Draft 
5<https://www.ietf.org/archive/id/draft-ietf-cose-hash-envelope-05.html>

Draft 4-->5 Diff:  
https://author-tools.ietf.org/iddiff?url2=draft-ietf-cose-hash-envelope-05



  *   Label 259 (content type of the preimage of the payload) MAY be present in 
the protected header and MUST NOT be present in the unprotected header.
  *   Label 260 (payload_location) MAY be present in the protected header and 
MUST NOT be present in the unprotected header.



Are there any questions or objections to moving to WGLC?



Thank you,

Steve





-----Original Message-----
From: [email protected]<mailto:[email protected]> 
[email protected]<mailto:[email protected]>
Sent: Friday, March 28, 2025 12:07 PM
To: Henk Birkholz 
[email protected]<mailto:[email protected]>; Orie Steele 
[email protected]<mailto:[email protected]>; Steve Lasker 
[email protected]<mailto:[email protected]>
Subject: New Version Notification for draft-ietf-cose-hash-envelope-05.txt



A new version of Internet-Draft draft-ietf-cose-hash-envelope-05.txt has been 
successfully submitted by Steve Lasker and posted to the IETF repository.



Name:     draft-ietf-cose-hash-envelope

Revision: 05

Title:    COSE Hash Envelope

Date:     2025-03-28

Group:    cose

Pages:    11

URL:      https://www.ietf.org/archive/id/draft-ietf-cose-hash-envelope-05.txt

Status:   https://datatracker.ietf.org/doc/draft-ietf-cose-hash-envelope/

HTML:     https://www.ietf.org/archive/id/draft-ietf-cose-hash-envelope-05.html

HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-cose-hash-envelope

Diff:     
https://author-tools.ietf.org/iddiff?url2=draft-ietf-cose-hash-envelope-05



Abstract:



   This document defines new COSE header parameters for signaling a

   payload as an output of a hash function.  This mechanism enables

   faster validation as access to the original payload is not required

   for signature validation.  Additionally, hints of the detached

   payload's content format and availability are defined providing

   references to optional discovery mechanisms that can help to find

   original payload content.







The IETF Secretariat






_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to