Extra information in public key

[Mark H. Wood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 9 Aug 2005, David Srbecky wrote:
[snip]
> And the content might look like this:
>
> First name=David
> Last name=Srbecky
> Country=Czech Republic
> City=Usti nad Labem
> Telephone=+65 536 1024
> ICQ=#128-256-512
> Homepage url=http://www.gnupg.org/
> Prefers encrypted mail=true
> Prefers signed mail=true
> Preferred encapsulation=MIME
> PGP key url=http://www.gnupg.org/dsrbecky/pgp.key
[snip]
> So, what do you think?

I think this looks like a job for a directory service.  About half of
those attributes are already defined in some X.500 schema and could easily
be dished up via LDAP, which any recent MUA ought to understand already.
Using a directory service for directory service sounds better to me than
overloading key subpackets.  How about just one simple record (a URI?) to
provide the linkage from the key to the directory object?  (I'd be very
much surprised if there isn't an attribute ID allocated for PGP keys
already, which can effectively provide the reverse "link".)

- -- 
Mark H. Wood, Lead System Programmer   mwood at IUPUI.Edu
Open-source executable:  $0.00.  Source:  $0.00  Control:  priceless!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/

iD8DBQFC+LGps/NR4JuTKG8RAvxYAJ9nu1hCD/xjiVUr1Y/uRFvQZZ2M/QCcD6KS
5bpCKFT7eKf+nOrhBV0kL5g=
=yyg7
-----END PGP SIGNATURE-----