From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: 
 <172047704310.461285.3728066842265531644@dt-datatracker-5f88556585-j5r2h>
References: 
 <172047704310.461285.3728066842265531644@dt-datatracker-5f88556585-j5r2h>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Mon, 08 Jul 2024 18:29:45 -0400
Message-ID: <9578.1720477785@obiwan.sandelman.ca>
Message-ID-Hash: V7CFJN63VBG46GZRTXU27TGDN5ZS2YYO
Precedence: list
Subject: =?utf-8?q?=5BAnima=5D_Re=3A_I-D_Action=3A_draft-ietf-anima-rfc8366bis-12=2Et?=
	=?utf-8?q?xt?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/anima/t9cUMJULngoAHPmGB1qG2KLwXCk>

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


I have finally returned to the ~23 issues that have been open for ~1 year.
I only got three issues closed today, but I'll continue working up to the m=
eeting.
So please expect a more complete -13 on July 20th.

internet-drafts@ietf.org wrote:
> Authors: Kent Watsen

I'm considering resorting the author names to be alphabetical.

    > Abstract:

    > This document defines a strategy to securely assign a pledge to an
    > owner using an artifact signed, directly or indirectly, by the
    > pledge's manufacturer.  This artifact is known as a "voucher".

This probably deserves a rewrite, but it will get done last.

    > A diff from the previous version is available at:
    > https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-anima-rfc8366b=
is-12

I have added Appendix A with CMS examples.
The JWS and COSE examples are in the [jBRSKI] and [cBRSKI] documents.

https://www.ietf.org/archive/id/draft-ietf-anima-rfc8366bis-12.html#name-ke=
y-pairs-associated-with-e
In the appendix, there is some space taken up with the private keys and
certificates.   I have to double check that I've got all the right files, as
the IDevID private key says "RSA", but is an EC key.  There are two possible
formats for private keys, the PKCS8 one and the PKCS1 one.  Are there
preferences?

Perhaps a picture of the relationship of all the files/keys is in order.
I included one key, the CA self-signed certificate expanded.
("openssl x509 -in foo -text" vs "openssl x509 -in foo " )
Do people want them all expanded?

I also notice that the certificates have expired, and I'll go back to my
reference code and update things.  I have asked Kent for a worked example of
an SZTP key.  I have a CMS signed key from Thomas Werner @ Siemens which I
can include as well.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQFJBAEBCgA0FiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmaMaFkWHG1jcitpZXRm
QHNhbmRlbG1hbi5jYQAKCRCAi3D73dDdZS39B/dhfsQhalbPNOmDIpEPFGN2HmNh
W2U11zQjgHXR3DEZmqkw5NDzsFB3VkTLQDLJyY7zRQcSCLKhFJ44Bpd+e2yYy5I1
JB7V7H18cQsVbJ2vQOgBg+gdi+qFFkPKxuLqPTER66hG1va36PrSgruCOy72mf4k
8a4fBjs2DAz2LTWXv0I8197PmK0cIRTrGwtbYCvL/4jb2IJFaUBMwr5BqR+0dN1O
32+lDoCkJcBw3jqOyTy9Bi7Zs4rrUnihBYliTRC1L+ZPuIJsCkIWq5o2o22XviHR
0CP44Jg4XykqDN5jQtTU4u+r9NLKJbJ261UL/+B6uSX2xHdFyVqSJT7Jk5U=
=ngUU
-----END PGP SIGNATURE-----
--=-=-=--