On 02/11/2018 05:46 PM, Dave Crocker wrote:
On 2/10/2018 10:47 AM, Michael Thomas wrote:
But I still think this entire conversation is silly in its
theoreticality.
Extra design complexity and consuming development resources --
programming, bench testing, interoperability testing -- for something
that is not essential, nevermind offers no actual value, is about as
practical as any standards issue can get.
Protocol complexity matters, especially for features that have no
immediate use.
d/
You guys have already spent 10 times the amount of effort prattling on
about these theoretical differences than any amount
of supposed savings for us poor, poor programming types. You clearly
have no idea what you are talking about.
Mike
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html