MIME-Version: 1.0
References: <0568e332-6791-4861-b360-6267240967ef@gmx.net>
In-Reply-To: <0568e332-6791-4861-b360-6267240967ef@gmx.net>
From: Ken Takayama <11kenterada@gmail.com>
Date: Sun, 8 Feb 2026 19:34:24 +0900
Message-ID: 
 <CAMGQZH6+6XV9tW9F=gTuG9G_OLxPX5rsVLa98hQcLmkgkEz=Pw@mail.gmail.com>
To: Hannes Tschofenig <hannes.tschofenig=40gmx.net@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008b2b29064a4d9134"
Message-ID-Hash: 4EONJYWPBO6JTOZFPUCXNUARCHV7X5P7
CC: "TEEP@ietf.org" <teep@ietf.org>,
 Ken Takayama <ken.takayama.ietf@gmail.com>
Precedence: list
Subject: =?utf-8?q?=5BTeep=5D_Re=3A_SUIT_Report_CDDL_Consistency_=28Ken_Takayama=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/teep/u3JiLDon0BCODi9qeYKj0-d9LCM>

--0000000000008b2b29064a4d9134
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hannes,

Thank you for addressing the issue.
However, as I mentioned in my comment here, I believe a few more
adjustments are still needed:
https://github.com/ietf-teep/teep-protocol/issues/404#issuecomment-38669234=
47

In short, `SUIT_Report` represents the SUIT Report without COSE protection,
i.e. with neither authentication nor encryption.

Best regards,
Ken

2026=E5=B9=B42=E6=9C=881=E6=97=A5(=E6=97=A5) 21:24 Hannes Tschofenig <hanne=
s.tschofenig=3D
40gmx.net@dmarc.ietf.org>:

> Hi Ken,
>
> thanks for your feedback regarding the SUIT Report encoding consistency.
>
> I have made the following changes:
>
> - Made SUIT Reports CDDL consistent across all messages (QueryRequest,
> QueryResponse, Success, Error) with "suit-reports =3D> [ + bstr .cbor
> SUIT_Report ]"
> - Enhanced documentation to clarify:
>    * Reports are encoded as CBOR byte strings (protected or unprotected)
>    * When a SUIT Report includes own COSE protection, the cryptographic
>      key must be distinct from the TEEP message's COSE security wrapper
>    * Unprotected reports rely on the TEEP message's COSE_Sign1/Sign wrapp=
er
>      for authenticity
>
> I hope version -22 addresses your feedback:
> https://www.ietf.org/archive/id/draft-ietf-teep-protocol-22.txt
>
> FWIW I also addressed this issue:
> https://github.com/ietf-teep/teep-protocol/issues/403
>
> Ciao
> Hannes
>
> PS: The changes can be found here:
>
> https://github.com/ietf-teep/teep-protocol/commit/07295b4e5dddfed09504e21=
f8261422e89e28bbf
>
>
>
> _______________________________________________
> TEEP mailing list -- teep@ietf.org
> To unsubscribe send an email to teep-leave@ietf.org
>

--0000000000008b2b29064a4d9134
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hannes,</div><div><br></div><div>Thank you for addres=
sing the issue.</div><div>However, as I mentioned in my comment here, I bel=
ieve a few more adjustments are still needed:</div><div><a href=3D"https://=
github.com/ietf-teep/teep-protocol/issues/404#issuecomment-3866923447">http=
s://github.com/ietf-teep/teep-protocol/issues/404#issuecomment-3866923447</=
a></div><div><br></div><div>In short, `SUIT_Report` represents the SUIT Rep=
ort without COSE protection, i.e. with neither authentication nor encryptio=
n.</div><div><br></div><div>Best regards,</div><div>Ken</div></div><br><div=
 class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmai=
l_attr">2026=E5=B9=B42=E6=9C=881=E6=97=A5(=E6=97=A5) 21:24 Hannes Tschofeni=
g &lt;hannes.tschofenig=3D<a href=3D"mailto:40gmx.net@dmarc.ietf.org">40gmx=
.net@dmarc.ietf.org</a>&gt;:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">Hi Ken,<br>
<br>
thanks for your feedback regarding the SUIT Report encoding consistency.<br=
>
<br>
I have made the following changes:<br>
<br>
- Made SUIT Reports CDDL consistent across all messages (QueryRequest, <br>
QueryResponse, Success, Error) with &quot;suit-reports =3D&gt; [ + bstr .cb=
or <br>
SUIT_Report ]&quot;<br>
- Enhanced documentation to clarify:<br>
=C2=A0=C2=A0 * Reports are encoded as CBOR byte strings (protected or unpro=
tected)<br>
=C2=A0=C2=A0 * When a SUIT Report includes own COSE protection, the cryptog=
raphic<br>
=C2=A0=C2=A0 =C2=A0 key must be distinct from the TEEP message&#39;s COSE s=
ecurity wrapper<br>
=C2=A0=C2=A0 * Unprotected reports rely on the TEEP message&#39;s COSE_Sign=
1/Sign wrapper<br>
=C2=A0=C2=A0 =C2=A0 for authenticity<br>
<br>
I hope version -22 addresses your feedback:<br>
<a href=3D"https://www.ietf.org/archive/id/draft-ietf-teep-protocol-22.txt"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/archive/id/draft=
-ietf-teep-protocol-22.txt</a><br>
<br>
FWIW I also addressed this issue:<br>
<a href=3D"https://github.com/ietf-teep/teep-protocol/issues/403" rel=3D"no=
referrer" target=3D"_blank">https://github.com/ietf-teep/teep-protocol/issu=
es/403</a><br>
<br>
Ciao<br>
Hannes<br>
<br>
PS: The changes can be found here:<br>
<a href=3D"https://github.com/ietf-teep/teep-protocol/commit/07295b4e5dddfe=
d09504e21f8261422e89e28bbf" rel=3D"noreferrer" target=3D"_blank">https://gi=
thub.com/ietf-teep/teep-protocol/commit/07295b4e5dddfed09504e21f8261422e89e=
28bbf</a><br>
<br>
<br>
<br>
_______________________________________________<br>
TEEP mailing list -- <a href=3D"mailto:teep@ietf.org" target=3D"_blank">tee=
p@ietf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:teep-leave@ietf.org" targ=
et=3D"_blank">teep-leave@ietf.org</a><br>
</blockquote></div>

--0000000000008b2b29064a4d9134--