Policy-Discussion

["cacert AT gmx.net" <cacert AT gmx.net>]

Hy Evaldo,


> Hi
>
> During the meeting, we came to the fact that currently we don't have a
> policy regarding names. I think we would need one, because I know or
> heard about the following situations:
>
> - Countries that have strict matching on First Name and Last Name
> - Countries that have strict matching on First Name, Middle Names, Last Name
> - Countries that allow you to have 20 first names to choose from at
> appropriate times
> - Countries that allow people to have a single name (a first conclusion
> would be that first name = last name, but it shouldnt appear twice
> - Countries that have fuzzy matching on First Name (so if you abbreviate
> >from "Foobarblahblahblah" to "Foozie" its okay, provided that its usual
> to do so)
>
> I have heard some more, but cant remember right now... maybe I will add
> here.
>   
In Luxemburg we have the situation that name "Paul" (First Name OR Last
name) could also written "Pol".
Some spanish names includes lots of middle names from grandparents and
grandgrandparents and grandgrantgrantparents and so on (Ian mentioned
it, I had several assured...). If we would include ALL of them the days
get longer and longer...
I personaly write all names on the CAP-Form.

> I would like ideas regarding CAcert policy for names, so we can actually
> serve people without creating more problems than we already have, and
> eventually solving some.
>   
My idea is that if the name(s) could be verified over at least 2 IDs and
if there is any doubt several others to proove it that could be enough.
I didn't think copys of the IDs like thawte practices it would be a good
idea.

-- 

mit freundlichen Grüßen / best regards
Henrik Heigl - CAcert Public Relations Officer

CAcert.org - Free Certificates
E-Mail: 
PR AT CAcert-Germany.de

PGP Key ID: 0x47471A1B
PGP Key Fingerprint = 3BB331E833B16FE0E655FF6AF3EC0C9147471A1B

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature