[{"author": "Tero Kivinen", "text": "

Zulip is working...

\n

Using the slide sharing in meetecho is much better than sharing screen, as that does slide changes etc better, and you can also pass the control to the speaker if needed.

", "time": "2022-11-07T15:44:23Z"}, {"author": "Carsten Bormann", "text": "

(I sent a PR for EAT. Status?)

", "time": "2022-11-07T15:47:50Z"}, {"author": "Kathleen Moriarty", "text": "

Thank you, it will help to have the support for both.

", "time": "2022-11-07T15:48:28Z"}, {"author": "Jabber", "text": "

cabo: #336 https://github.com/ietf-rats-wg/eat/pull/336

", "time": "2022-11-07T15:50:19Z"}, {"author": "Giridhar Mandyam", "text": "

@carsten - PR was only filed yesterday during blackout period. Editors have not had a chance to review. But they look OK to me

", "time": "2022-11-07T15:50:36Z"}, {"author": "Jabber", "text": "

cabo: Thanks, just asking\u2026

", "time": "2022-11-07T15:51:49Z"}, {"author": "Roman Danyliw", "text": "

Spreadsheet issue #18 appears to come from https://mailarchive.ietf.org/arch/msg/rats/sfJjlYfHNXezu5n2ifJ3pBZBRMk/

", "time": "2022-11-07T15:56:22Z"}, {"author": "Jabber", "text": "

cabo: (BTW, the I-D moratorium was already over yesterday.)

", "time": "2022-11-07T15:57:28Z"}, {"author": "Giridhar Mandyam", "text": "

I was hoping that CORIM would pre-empt all discussion of endorsements in the EAT spec

", "time": "2022-11-07T15:58:13Z"}, {"author": "Roman Danyliw", "text": "

The only place where \"endorsement\" is mentioned outside of the appendix is:
\n6.2.10. Endorsement Identification

\n

Similar to, or perhaps the same as verification key identification,
\n the profile may wish to specify how endorsements are to be
\n identified. However note that endorsement identification is
\n optional, whereas key identification is not.

", "time": "2022-11-07T16:01:08Z"}, {"author": "Dave Thaler", "text": "

Section 4.3.3 has \"4 -- Certificate Issuance:
\nCertification Authorities (CA's) may require attestations prior to the issuance of certificates related to keypairs hosted at the entity. An EAT may be used as part of the certificate signing request (CSR).\" (note \"attestations\" in that text)

", "time": "2022-11-07T16:02:42Z"}, {"author": "Dave Thaler", "text": "

I suspect above means \"Attestation Results\" instead of \"attestations\"

", "time": "2022-11-07T16:03:35Z"}, {"author": "Ned Smith", "text": "

I don't think there is industry consensus on secure boot terminology. some use verified boot, but could mean measured boot also.

", "time": "2022-11-07T16:09:48Z"}, {"author": "Ned Smith", "text": "

taking a RATs arch view, it could be defined as combining attester, verifier and maybe relying party roles on the attester device

", "time": "2022-11-07T16:11:28Z"}, {"author": "Michael Richardson", "text": "

https://github.com/ietf-rats-wg/eat/issues/296

", "time": "2022-11-07T16:25:38Z"}, {"author": "Henk Birkholz", "text": "

+1 to Dave

", "time": "2022-11-07T16:33:26Z"}, {"author": "Roman Danyliw", "text": "

cwt-reg-review@ list documents decisions/discussion for the CWT registry. Here is the EAT early registration request thread:
\nhttps://mailarchive.ietf.org/arch/msg/cwt-reg-review/Eyya7u9rR1XA5N0KcXiTfolAdTs/

", "time": "2022-11-07T16:33:46Z"}, {"author": "Brendan Moran", "text": "

Sounds like we need an ordered multi map!

", "time": "2022-11-07T17:17:48Z"}]