W3C home > Mailing lists > Public > public-wsc-wg@w3.org > April 2007

RE: DNSSEC indicator

From: <michael.mccormick@wellsfargo.com>
Date: Thu, 12 Apr 2007 14:09:57 -0500
Message-ID: <8A794A6D6932D146B2949441ECFC9D6803608546@msgswbmnmsp17.wellsfargo.com>
To: <tlr@w3.org>, <public-wsc-wg@w3.org>
Cc: <member-wsc-wg@w3.org>, <kjell.rydjer@swebank.se>, <steve@shinkuro.com>

My mistake.  There's nothing confidential about this topic.  I'm
cross-posting this to the public list.

-----Original Message-----
From: Thomas Roessler [mailto:tlr@w3.org] 
Sent: Thursday, April 12, 2007 2:03 PM
To: McCormick, Mike
Cc: member-wsc-wg@w3.org; kjell.rydjer@swebank.se; steve@shinkuro.com
Subject: Re: DNSSEC indicator


the Working Group's public list (public-wsc-wg) is intended for the
technical discussion; the member-confidential one that this thread is on
right now is intended for (a) administrative things or (b) things we
have a really good reason to keep confidential. If you don't mind, I'd
rather continue this discussion on the public list.

Thomas Roessler, W3C  <tlr@w3.org>  +33.4.89063488

On 2007-04-12 13:53:28 -0500, michael.mccormick@wellsfargo.com wrote:
> From: michael.mccormick@wellsfargo.com
> To: member-wsc-wg@w3.org
> Cc: kjell.rydjer@swebank.se, steve@shinkuro.com
> Date: Thu, 12 Apr 2007 13:53:28 -0500
> Subject: DNSSEC indicator
> List-Id: <member-wsc-wg.w3.org>
> X-Spam-Level: 
> X-Archived-At:
> X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.1.5
> DHS (Steve Crocker) and SwedBank (Kjell Rydjer) gave terrific
> presentations to the FSTC Security Committee today about DNSSEC.
> One issue SwedBank has run into as DNSSEC rolls out in Sweden
> (quoting Kjell's presentation): "Will Microsoft and Mozilla
> implement a DNSSEC indicator in their browsers?"
> At the committee's request I agreed to pass this question along
> to the W3C WSC group for your consideration.  Any thoughts?
> My personal opinion is DNSSEC should probably be another input to
> the agent security context display along with the others we've
> talked about (e.g., SSL/TLS).  There are some practical obstacles
> to overcome -- for instance the name resolver built into the
> client OS or browser has to be DNSSEC-capable as a prerequisite
> for this -- but it seems it ought to be on the roadmap.  I
> believe DNSSEC has more potential benefit if it's visible to end
> users.
> >Michael McCormick, CISSP
> >Lead Architect, Information Security Technology
> >Wells Fargo Bank
> >255 Second Avenue South
> >MAC N9301-01J
> >Minneapolis MN 55479
> >*> >	612-667-9227 (desk)		* 	612-667-7037 (fax)
> >(	612-590-1437 (cell)		:-)
michael.mccormick@wellsfargo.com (AIM)
> >*	612-621-1318 (pager)		*
> >
> >This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein.  If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message.  Thank you for your cooperation.
> >
Received on Thursday, 12 April 2007 19:13:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:15 UTC