Hi Bernie,
On 23/05/2025 16:26, Bernie Hoeneisen wrote:
Hi Alanna, Alexey, et al.
Below (inline) my comments on the discussions between Alanna and Alexey.
(I intend to send further feedback in separate emails.)
On Fri, 23 May 2025, Alexey Melnikov wrote:
Hi Alanna,
On 22/05/2025 18:50, Alanna Paloma wrote:
Hi Alexey and other authors,
We have updated the files per Alexey’s response. Please note that
some of our initial questions have not been addressed and we have
follow-up questions.
7) <!--[rfced] For clarity and consistency, may we update the
phrasing of
"Legacy receiving MUA" and "modern receiving clients" as follows?
Original:
The message generation guidance aims to minimize negative
interactions with any Legacy receiving MUA while providing
actionable cryptographic properties for modern receiving
clients.
Perhaps:
The message generation guidance aims to minimize negative
interactions with any Legacy MUA recipient while providing
actionable cryptographic properties for modern client
recipients.
-->
Slight change in meaning. We are not typically talking about legacy
recipients, as any recipient can have a mixture of MUAs, some
legacy and some not.
) We have tweaked the text further. Does the sentence below retain
the intended meaning?
Perhaps:
The message generation guidance aims to minimize negative
interactions with any Legacy MUA being received while providing
actionable cryptographic properties for clients receiving modern
MUAs.
No, this doesn't read right.
The original is using "Legacy receiving MUA", which is a "receiving
MUA" which is Legacy. Does this help?
+1
Maybe "Legacy (receiving) MUA"?
I think the original is fairly clear as "receiving MUA" is a good
description on what we want to express. i.e. sth like "An MUA in its
role of receiving email messages". (IIRC, "receiving MUA/side/client"
are used also elsewhere in the document.) I am not quite sure what is
the motivation for changing this. I would suggest to leave it as in
the original are maybe replace "client" by MUA at the end, as in the
following:
The message generation guidance aims to minimize negative
interactions with any Legacy receiving MUA while providing
actionable cryptographic properties for modern receiving MUAs.
I was actually thinking the same, so I like your suggestion.
--
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org
