On Mon, Aug 09, 2021 at 01:52:36PM -0700, Dave Crocker wrote:
On 8/9/2021 1:41 PM, Rolf E. Sonneveld wrote:
The key unanswered question is what the "audience" for the header
content
+1
A nice example of the proverbial solution in search of a problem.
From the Introduction, what about this is insufficiently clear or complete?
All of it. What is the new experimental use of the header?
It can be helpful for a message to have a common way of indicating
each delivery in the handling sequence, and to include each address
that led to the final delivery.
Useful to whom and to what end?
This can aid in the analysis of a message's transit handling.
OK: 1. Human reading tea leaves.
An additional use can be for detecting a delivery sequence loop.
OK: 2. Existing loop detection use-case.
So the only proposed uses are the current ones, which is reassuring, but
also rather invites the question of what exactly is then the the nature
of the proposed "experiment"?
Instead of promposing an "experiment" why not just clarify the existing
uses above, and making it clear that the header is a trace header, and
that its payload SHOULD be an "addr-spec" from RFC5322. The draft can
then be informational.
--
Viktor.
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp