W3C home > Mailing lists > Public > public-usable-authentication@w3.org > April 2006

RE: Secure Metadata

From: <Michael.Mccormick@wellsfargo.com>
Date: Wed, 12 Apr 2006 12:49:04 -0500
Message-ID: <8A794A6D6932D146B2949441ECFC9D680216C8C1@msgswbmnmsp17.wellsfargo.com>
To: <staikos@kde.org>, <public-usable-authentication@w3.org>
Cc: <Pete.Palmer@wellsfargo.com>

RFC 3709 (http://www.ietf.org/rfc/rfc3709.txt) defines an X.509
extension that allows optional logographic images for community, issuer,
and subject organizations.

Say for example GM obtained web server SSL certificates from VeriSign
for use within their supplier community.  The cert could display logos
for GM, VeriSign, and the auto parts exchange (or any subset /
combination thereof).

-----Original Message-----
From: public-usable-authentication-request@w3.org
[mailto:public-usable-authentication-request@w3.org] On Behalf Of George
Sent: Tuesday, April 11, 2006 11:55 AM
To: public-usable-authentication@w3.org
Subject: Re: Secure Metadata

On Monday 10 April 2006 13:30, Thomas Roessler wrote:

> There appear to be several possible routes that this work could take, 
> including, on the simple side, an agreement and recommendation to 
> display logotype certificate attribute; on the more complex end of the

> scale, this work could also look at formats for complex trustmark-like

> objects, and a recommendation to display these in the browser chrome.

   Do you mean the logo of the CA, the site owner, or both?  I think
they all have potential issues, but I'm interested in discussing.

George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/
Received on Wednesday, 12 April 2006 17:49:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:15 UTC