Closed ietf-svn-bot closed 2 years ago
@alexey.melnikov@isode.com changed title from Meaning of "MTA" and Related Terminology
to G.3. Meaning of "MTA" and Related Terminology
@alexey.melnikov@isode.com set component to smtp
From IETF 113 discussion:
Question 1 - "sender-SMTP" and "receiver-SMTP" vesus "SMTP client" and "SMTP server". Proposal: no change
Based on no objection from the mailing list, the following change needs to be implemented:
Add a note to the document stating that "sender-SMTP" and "SMTP client", as well as "receiver-SMTP" and "SMTP server" are used interchangeably, but otherwise do no further changes.
The change is implemented in -11
keyword_SMTP
type_defect
| by alexey.melnikov@isode.comG.3. Meaning of "MTA" and Related Terminology
A terminology issue has come up about what the term "MTA" actually refers to, a question that became at least slightly more complicated when we formalized RFC 6409 Submission Servers. Does the document need to be adjusted to be more clear about this topic? Note that the answer may interact with the question asked in Section 2 above. Possibly along the same lines, RFC 2821 changed the RFC 821 terminology from "sender-SMTP" and "receiver-SMTP" to "SMTP client" and "SMTP server" respectively. As things have evolved, it is possible that newer terminology is a source of confusion and that the terminology should be changed back, something that also needs discussion.
Issue migrated from trac:3 at 2022-01-31 12:33:13 +0000