Compelling Reason for Deploying DNSSEC

[Paul Romano]

Does the lack of response indicate a lack of compelling reason or just lack of interest in this topic?  
 
Is there a way to tie an ROI into a DNSSEC deployment? 
Are any agencies planning on deying access to unsigned domains?
Are there any numbers indicating a trend in DNS related attacks?
 
 

 
From: "WBrown at e1b.org" <WBrown at e1b.org>
To: Paul Romano <ittech68 at yahoo.com>
Sent: Wednesday, September 14, 2011 8:46 AM
Subject: Re: Compelling Reason for Deploying DNSSEC

Paul Romano wrote on 09/13/2011 10:13:36 PM:

> From: Paul Romano <ittech68 at yahoo.com>
> I am trying to justify deploying DNSSEC to my management.  We have 
> many domains and I want to use this project as an opportunity to 
> review and classify our many domains (legacy, defensive, current 
> production, etc.).  Since money is very tight we need a compelling 
> reason to justify the project. I have explained the value of 
> protecting our traffic along with our reputation. We communicate 
> with some government agencies and I have said that there may be some
> concern about communicating with these agencies in the future.  The 
> project has still been declined.  Can any of you give a more 
> compelling justification for deployment? 

I would like to hear the justification as well.  I know the gTLDs have 
been signed, but there are a lot of domains for large tech companies that 
are not signed yet. 

Is it a matter of reaching critical mass?



Confidentiality Notice: 
This electronic message and any attachments may contain confidential or 
privileged information, and is intended only for the individual or entity 
identified above as the addressee. If you are not the addressee (or the 
employee or agent responsible to deliver it to the addressee), or if this 
message has been addressed to you in error, you are hereby notified that 
you may not copy, forward, disclose or use any part of this message or any 
attachments. Please notify the sender immediately by return e-mail or 
telephone and delete this message from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20110915/396777cc/attachment.html>