On 6/29/2011 9:40 AM, John R. Levine wrote: > RFC 4871 is full of gratuitous and often wrong advice on everything from > APIs to MUA design to key management. 4871bis got rid of some of it, but > there's still a lot left. If Pete can force us to strip out more of the > gratuitous stuff and stick to telling people how to do reliably > interoperable signing and verification, the actual standards part of the > standard, he'll be doing everyone a favor in the long run.
Well, perhaps you are right. After all, the group's ability to make decisions about changes, it's enthusiasm for such an effort and the community's demonstrated problems with the problematic text are all clear enough to easily justify our continuing to expend significant effort and to further delay publication of this document. Not. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
