On Sun, 5 Apr 2009 11:53:34 -0400 Barry Leiba
<barryleiba(_at_)computer(_dot_)org>
wrote:
This updates RFC 4871, DomainKeys Identified Mail (DKIM) Signatures.
Specifically the document clarifies the nature, roles and
relationship of the two DKIM identifier tag values that are
candidates for payload delivery to a receiving processing module.
The Update is in the style of an Errata entry, albeit a rather long
one.
I would much prefer that it created a new RFC to _Supersede_ RFC 4871,
containing the full text as amended, and with an Appendix listing the
changes made (whether in full "old/new" format like this draft, or
otherwise), and pointing out that NO change to the protocol was intended
or implied.
Thanks, Charles; noted. What you say was one of the original choices
the chairs posed.
This was not, though, the consensus we arrived at in the meeting, and
there hasn't been enough support for this choice on the mailing list
either.
I'll confess that my available mental bandwidth for this wg has been
somewhat limited lately, but I hadn't considered that we were not doing a
complete replacement of 4871. This is confusing enough without having to do
mental gymastics between two RFCs to understand DKIM.
Scott K
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html