On Oct 21, 2010, at 9:53 AM, Murray S. Kucherawy wrote:
Take a tour through the eleven parts of Section 7 of RFC5451, and then
Appendices A and C. They provide all kinds of warnings about misinterpreting
the data provided, which amounts to pretty firm implementation advice, and
identifies ways you can shoot yourself in the foot. But none of those
sections are normative. (Actually there are two SHOULDs in 7.4, but in
retrospect they shouldn't really be there.)
That's what I'm advocating here: The normative stuff defines the core
mechanics of the protocol itself, and the informative stuff explains why it's
done that way, detailed implementation advice including stuff about other
layers, and how one should (and shouldn't) interpret the output.
+1
Cheers,
Steve
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html