jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-suit-firmware-encryption

Commentary: Adding an example manifest using AES - KW in case where the Author knows the recipients ( the Author and the Devices have the same pre - shared key ) . 
 This is a good example . I looked through it and it made sense to me . 
 In the firmware encryption draft we have defined an extension to the envelope that indicates what encryption parameters are applied to which component . Here is the CDDL : Currently the text provides no explanation or an example of how this linkage works . 
 This aspect is related to and to the mailing list discussion 
 This issue is also related to 
 With in PR , this issue is solved .
Paragraph (version B):
The following manifests examplify how to deliver the encrypted
firmware and its encryption info to the Devices.
Paragraph (version B):
Each example uses SHA256 as the digest function.
Draft: draft-ietf-suit-firmware-encryption

Commentary: Based on discussions with  , I have updated the text in Section 7 about CEK Verification . Text about the parameters used for encryption were missing .
Paragraph (version A):
This document specifies a firmware update mechanism where the
firmware image is encrypted.  Firmware encryption uses the IETF SUIT
manifest with key establishment provided by the hybrid public-key
encryption (HPKE) scheme and the AES Key Wrap (AES-KW) with a pre-
shared key-encryption key.  Encryption of the firmware image is
encrypted using AES-GCM or AES-CCM.
Paragraph (version B):
This document specifies a firmware update mechanism where the
firmware image is encrypted.  Firmware encryption uses the IETF SUIT
manifest with key establishment provided by the hybrid public-key
encryption (HPKE) scheme and the AES Key Wrap (AES-KW) with a pre-
shared key-encryption key.  Encryption of the firmware image is
accomplished using the established content encryption key and a
mutually agreed symmetric encryption algorithm, such as AES-GCM or
AES-CCM.
Paragraph (version A):
Hybrid Public Key Encryption (HPKE), defined in I-D.irtf-cfrg-
hpke.
Paragraph (version B):
Hybrid Public Key Encryption (HPKE), defined in RFC9180.
Paragraph (version B):
The main use case of this document is to encrypt firmware.  However,
SUIT manifests may require other payloads than firmware images to
experience confidentiality protection using encryption.  While the
term firmware is used throughout the document, plaintext other than
firmware images may get encrypted using the described mechanism.
Hence, the terms firmware (image) and plaintext are used
interchangably.
Paragraph (version A):
Hybrid public-key encryption (HPKE) I-D.irtf-cfrg-hpke is a scheme
that provides public key encryption of arbitrary-sized plaintexts
given a recipient's public key.
Paragraph (version B):
Hybrid public-key encryption (HPKE) RFC9180 is a scheme that provides
public key encryption of arbitrary-sized plaintexts given a
recipient's public key.
Paragraph (version A):
AES-GCM-128 for encryption of the (detached) firmware image (at
layer 0).
Paragraph (version A):
AES-GCM-128 for encryption of the CEK in layer 1 as well as ECDH
with NIST P-256 and HKDF-SHA256 as a Key Encapsulation Mechanism
(KEM).
Paragraph (version A):
The suit-cek-verification parameter contains a byte string resulting
from the encryption of 8 bytes of 0xA5 using the CEK.
Paragraph (version B):
AES-GCM-128 for encryption of the (detached) firmware image.
Paragraph (version B):
AES-GCM-128 for encryption of the CEK as well as ECDH with NIST
P-256 and HKDF-SHA256 as a Key Encapsulation Mechanism (KEM).
Paragraph (version B):
The suit-cek-verification parameter contains a byte string resulting
from the encryption of 8 bytes of 0xA5 using the CEK with a nonce of
all zeros and empty additional data using the cipher algorithm and
mode also used to encrypt the plaintext.
Paragraph (version B):
As explained in arch, the suit-cek-verification parameter is optional
to implement and optional to use.  When used, it reduces the risk of
an battery exhaustion attack against the IoT device.