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:
I would prefer to do that *and* call Delivered-to: what it is: A trace field.
Yup.
At some point we need to fix the 5322 trace field ABNF but emailcore is
down the hall from here.
Regards,
John Levine, johnl(_at_)taugh(_dot_)com, Primary Perpetrator of "The Internet for
Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp