Thanks, Henk! We assume if any updates are necessary to the document, Thomas will either make the change in the repo or let us know here.
Current: Thomas Fossati Linaro Email: [email protected] <mailto:[email protected]> Megan Ferguson RFC Production Center > On Jun 28, 2026, at 5:51 AM, Henk Birkholz <[email protected]> wrote: > > As Thomas is transitioning from Linaro to NVIDIA, his current (most likely > interim) email address is: [email protected] > > I changed his email in the TO accordingly. > > On 28.06.2026 13:04, Henk Birkholz wrote: >> Hi RPC, >> thank you for kickstarting the process! >> zu 1.) my github username is recorded in the datatracker, but here it is via >> email: henkbirkholz >> Viele Grüße, >> Henk >> On 22.06.2026 20:20, [email protected] wrote: >>> *****IMPORTANT***** >>> >>> RFC Author(s): >>> -------------- >>> >>> Your document has now entered Final Review (formerly AUTH48). >>> >>> Final Review is being handled in GitHub as part of the GitHub pilot test >>> (see https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github- >>> phase-0-pilot-test). >>> >>> Your document is available for review at: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10013 >>> >>> Please do the following: >>> >>> a) accept your invitations to join the repo as collaborators. Simon, >>> Hannes, and Henk, please provide your GitHub usernames so that we can send >>> you invitations. We have already sent an invitation to Thomas. If the AD >>> (Christopher Inacio) and the WG Chairs (Kathleen Moriarty and Ned Smith) >>> would like invitations as well, please provide GitHub usernames. >>> >>> b) see the README for details on the Final Review process: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10013/blob/ >>> Approved/README.md >>> >>> c) review the edits in the RPC-edits pull request: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10013/pulls >>> >>> d) address the issues: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10013/issues >>> >>> Once the content is stable in GitHub, we will provide the updated XML file >>> and the output files for review and approval. >>> >>> You and your coauthors are responsible for engaging other parties >>> (e.g., Contributors or Working Group) as necessary before providing >>> your approval. >>> >>> Once the document has been reviewed and approved by all of the authors, >>> it will be published as an RFC. If an author is no longer available, >>> there are several remedies; see the Unavailable Authors section >>> (https://authors.ietf.org/rfc-publication-process#unavailable-authors). >>> >>> Details on the status of your Final Review are here: >>> https://queue.rfc-editor.org/final-review/rfc10013/ >>> >>> Please let us know if you have any questions. >>> >>> Thank you for your cooperation, >>> >>> RFC Production Center >>> >>> -------------------------------------- >>> RFC 10013 (draft-ietf-rats-eat-measured-component) >>> >>> Title : Entity Attestation Token (EAT) Measured Component >>> Author(s) : S. Frost, >>> T. Fossati, >>> H. Tschofenig, >>> H. Birkholz >>> WG Chair(s) : Ned Smith, Kathleen Moriarty >>> Area Director(s) : Deb Cooley, Christopher Inacio > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
