Policy-Discussion

[Bernhard Froehlich <ted AT convey.de>]

Iang schrieb:
> [...]
> A quick straw poll:  Who here has One Perfect Single Name on 
> all documents, and who here has more than one?
>
> I have two, the variation being the middle initial.
>
>
>
> So, as a general principle, it would seem that people can
> have more than one valid name?  Have we established that?
>
> (It may be that we establish a principle ... to find that 
> the code and assurance systems can't deal with ... but 
> that's ok, get the principles established first.)
>
>
>
> Then we have the issue that if I have multiple names, and I
> "decide" to add another one, does the assurance process have
> to catch up?
>
> It might seem that each *name* should be assured, at least 
> to the minimum level, before being offered as an option for 
> a cert?
>
> In Assurance Statement terms, this might say that the 
> Name(s) of the Individual have been Assured to a Level.
>   

To handle different names I'd propose that CAcert's statement should be 
"If the name Joe Cool is included in a certificate the owner has 
provided at least one good document proving that he is Joe Cool"? This 
does not exclude that he is also called "Joe Very Cool" or "Joseph Cook" 
on other documents.

Thinking a bit further along the way: If someone has documents for 
different names s/he could always create two CAcert accounts, go to one 
assurer and get one name assured, then go to another and get the other 
one assured. So why shouldn't we allow different names for one account? 
Of course each name would have to be assured.

But this still leaves the problems of different transliterations. Just 
note that I created my account on "Bernhard Froehlich" (because of bad 
experiences with PGP) and got it assured, though my ID says I'm 
"BERNHARD ANDREAS FRÖHLICH"... Should I file a dispute now?
> iang
>   
Ted
;)

--
PGP Public Key Information
Download complete Key from http://www.convey.de/ted/tedkey_convey.asc
Key fingerprint = 31B0 E029 BCF9 6605 DAC1  B2E1 0CC8 70F4 7AFB 8D26

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