Re: [ietf-dkim] Comments on -overview document?

In addition, this number is what both Murray/Eric and I are seeing assendmail

*milters*, which is much more likely to be an *upper* bound rather than

a lower bound or typical result. I've been trying to tease out what theactualcomputational cost is lately, but it's not really easy as it depends alot on

how much trafffic needs to be signed, how much is signed, how long the
average DNS latency is, etc, etc, etc.

      Mike

Bill(_dot_)Oxley(_at_)cox(_dot_)com wrote:

Dave,
This document fine except for the following section
"Usually, email is i/o-intensive, with unused
  computational capacity.  So, it is likely that no new hardware will
  be required."

This should be deleted. For example if others in my organization who
have not followed the mailing list were to see that paragraph they would
conclude that the WG did not have a clear understanding of today's large
mail environment and would tend to resist implementation efforts. The
paragraph above that gives a 10 to 15% processing utilization should
speak to what cpu, what architecture those numbers came from if we are
going to include any numbers at all.
Thanks,

Bill OxleyMessaging EngineerCox Communications, Inc.Alpharetta GA404-847-6397bill(_dot_)oxley(_at_)cox(_dot_)com

-----Original Message-----
From: ietf-dkim-bounces(_at_)mipassoc(_dot_)org
[mailto:ietf-dkim-bounces(_at_)mipassoc(_dot_)org] On Behalf Of Dave Crocker
Sent: Sunday, July 09, 2006 9:37 PM
To: ietf-dkim(_at_)mipassoc(_dot_)org
Subject: Re: [ietf-dkim] Comments on -overview document?



Bill(_dot_)Oxley(_at_)cox(_dot_)com wrote:

Dave,
if you are speaking to thehttp://mipassoc.org/dkim/info/DKIM-Intro-Allman.html


oops.  sorry.  no.

I meant:

        Title           : DomainKeys Identified Mail Overview
        Author(s)       : T. Hansen, et al.
        Filename        : draft-ietf-dkim-overview-00.txt
        Pages           : 30
        Date            : 2006-6-22
        
  DomainKeys Identified Mail DKIM [I-D.ietf-dkim-base] defines a
  domain-level authentication framework for email using public-key
  cryptography and key server technology to permit verification of

the

  source and contents of messages by either Mail Transfer Agents

(MTAs)

  or Mail User Agents (MUAs).  The ultimate goal of this framework is
  to permit a signing domain to assert responsibility for a message,
  thus proving and protecting message sender identity and the

integrity

  of the messages they convey while retaining the functionality of
  Internet email as it is known today.  Proof and protection of email
  identity, including repudiation and non-repudiation, may assist in
  the global control of "spam" and "phishing".

  This document provides an overview of DomainKeys Identified Mail

and

  how it can fit into overall messaging systems, how it relates to
  other IETF message signature technologies, implementation and
  migration considerations, and outlines potential DKIM applications
  and future extensions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dkim-overview-00.txt


announced on 22 June.

d/


_______________________________________________

NOTE WELL: This list operates according tohttp://mipassoc.org/dkim/ietf-list-rules.html