I have seen a combination of references to 822 and 2822 in recent discussions
on the list. Is the requirement that DKIM support both 822/2822 content (822
being the current standard) or is the intent that DKIM is just required to
support 2822 content?
I believe there are two parts to the answer to that:
1. We refer to RFC 282x, as the current standard, and that's what we're
aiming to support.
2. We're trying, to the extent we reasonably can, to deal with most of
what's actually out there, which includes RFC-82x-compliant stuff as
well as some small subset of odd or "broken" behaviour that we consider
to be common enough to be worth working with.
Does anyone think that's not the right answer?
Barry
--
Barry Leiba, DKIM working group chair (leiba(_at_)watson(_dot_)ibm(_dot_)com)
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html