Hi Alanna I herewith sign out of RFC-to-be 9787.
cheers Bernie On 15.08.25 18:32, Alanna Paloma wrote: > Hi Authors , > > Thank you for the updated XML file. We have updated the other document files > accordingly; see below. > > We will await Bernie’s approval prior to moving this document forward in the > publication process. > > Please see the AUTH48 status page for this document here: > https://www.rfc-editor.org/auth48/rfc9787 > > — FILES (please refresh) — > > The files have been posted here: > https://www.rfc-editor.org/authors/rfc9787.xml > https://www.rfc-editor.org/authors/rfc9787.txt > https://www.rfc-editor.org/authors/rfc9787.html > https://www.rfc-editor.org/authors/rfc9787.pdf > > The relevant diff files have been posted here: > https://www.rfc-editor.org/authors/rfc9787-diff.html (comprehensive diff) > https://www.rfc-editor.org/authors/rfc9787-auth48diff.html (AUTH48 changes) > https://www.rfc-editor.org/authors/rfc9787-auth48rfcdiff.html (AUTH48 changes > side by side) > https://www.rfc-editor.org/authors/rfc9787-lastdiff.html (last version to > this one) > https://www.rfc-editor.org/authors/rfc9787-lastrfcdiff.html (rfcdiff between > last version and this) > > Best regards, > Alanna Paloma > RFC Production Center > >> On Aug 14, 2025, at 8:45 PM, Daniel Kahn Gillmor <[email protected]> >> wrote: >> >> Hi RFC Editor, all-- >> >> As Bernie noted, the authors have agreed on some additional terminology >> cleanup for draft-ietf-lamps-e2e-mail-guidance, aka RFC-to-be-9787. >> >> This terminology cleanup aligns it with the terminology from the >> companion document draft-ietf-lamps-header-protection (RFC-to-be-9788), >> which tries to be more specific about the particular role that the MUA >> and the user are playing ("composing" and "rendering" being different >> from "sending and receiving", for example). >> >> Please see the attached updated XML. >> >> Regards, >> >> --dkg >> >> <rfc9787.xml>
sender_key.asc
Description: application/pgp-keys
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
