On Wed, Feb 17, 2021 at 11:20 AM Ned Freed
<ned(_dot_)freed(_at_)mrochek(_dot_)com> wrote:
The new text says "add at top" but saying nothing about grouping and
prohibiting reordering. Both of which are really important requirements.
By calling it a trace field, you establish the necessary requirements.
Yes, the
underlying documents have issues, but they are clear enough. And "trace
field"
is a term that most implementors understand.
That said, making the actual requirements explicit would be even better.
You
can easily do that by referring to section 4.4 in RFC 5321 and saying that
it
all now applies to the combination of Received: and Delivered-to:
FWIW, in developing RFC 8617 (ARC), we also designated those headers as
trace fields too, though we didn't trust handlers to do the right thing so
we built in mechanisms to solve for any reordering or ungrouping which may
happen in the transit chain.
--Kurt Andersen
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp