Hi Megan!
The document looks good to move along.
Thank you for all the work!
Viele Grüße,
Henk
On 21.07.2026 17:54, Megan Ferguson wrote:
Hannes,
Thanks for sending along your approval. We have recorded it at the AUTH48 /
Final Review status page (see below).
Once we have approvals from Henk and Simon, this document should be ready to
move forward in the publication process.
XML file:
https://www.rfc-editor.org/authors/rfc10013.xml
Output files:
https://www.rfc-editor.org/authors/rfc10013.txt
https://www.rfc-editor.org/authors/rfc10013.html
https://www.rfc-editor.org/authors/rfc10013.pdf
Comprehensive diff file of the text:
https://www.rfc-editor.org/authors/rfc10013-diff.html
https://www.rfc-editor.org/authors/rfc10013-rfcdiff.html (side by side)
For the Final Review status of this document, please see:
https://queue.rfc-editor.org/final-review/rfc10013
Thank you.
Megan Ferguson
RFC Production Center
On Jul 15, 2026, at 5:51 AM, Hannes Tschofenig <[email protected]>
wrote:
Thank you all for the work on this document!
It looks great to me.
Am 07.07.2026 um 23:02 schrieb Thomas Fossati:
Hi Megan, all,
The document looks ready to me. Thanks very much for all your help!
cheers, t
On Tue, Jul 7, 2026 at 1:13 AM Megan Ferguson
<[email protected]> wrote:
All,
We have merged the updates in GitHub as requested by Thomas.
Please review the XML file and its outputs (TXT, HTML, PDF), and let us know
(via a Reply-All to this email) if any changes are required or if you approve
the RFC for publication in its current form.
Note: We will consider this your final assent that the document is ready for
publication.
XML file:
https://www.rfc-editor.org/authors/rfc10013.xml
Output files:
https://www.rfc-editor.org/authors/rfc10013.txt
https://www.rfc-editor.org/authors/rfc10013.html
https://www.rfc-editor.org/authors/rfc10013.pdf
Comprehensive diff file of the text:
https://www.rfc-editor.org/authors/rfc10013-diff.html
https://www.rfc-editor.org/authors/rfc10013-rfcdiff.html (side by side)
For the Final Review status of this document, please see:
https://queue.rfc-editor.org/final-review/rfc10013
Thank you.
Megan Ferguson
RFC Production Center
On Jun 29, 2026, at 4:47 PM, Megan Ferguson <[email protected]>
wrote:
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]
