* Case Number: a20090618.10 * Status: closed * Claimants: Dirk Astrath * Respondents: * Case Manager: Bernhard Fröhlich as substitute for Nick Bebout * Arbitrator: UlrichSchroeter * Date of arbitration beginning: 2009/06/18 * Date of arbitration initializing: 2009/10/16 * Date of arbitration starts: 2009-12-07 * Date of arbitration ruling: 200?-12-25 * Date of arbitration closed: 200?-??-?? * Complaint: User registered under unvalidated name / changed to I withdraw my membership {{{ hello 'support', some days ago i got a CAP-form with the following data on it: (Both names are correct, because his name was '' until marriage ... now his name is ' ') At CAcert he entered his name as '' ... The question now is: Am I allowed to assure this name (since i read every name on his ID-Card (Personalausweis)) ... or should i ask him to remove the name '' so the name is correct? In my opinion he has to change the name at CAcert ... do you agree? have a nice day ... }}} * Relief: To be determined Before: Arbitrator UlrichSchroeter (A). Respondent: (R) Claimant: Dirk Astrath (C) Case: a20090618.10 . 2009-10-16 (A) care about case a20090618.10 . 2009-10-16 (C)(R) Request for CCA/DRP acceptance . 2009-10-16 (C)(R) Request for PoV statement . 2009-10-23 (C)(R) requests reminder sent . 2009-10-23 (C) accepts CCA / DRP under this arbitration . 2009-11-04 (R) reminder for requests sent . 2009-11-19 (R) wishes translation of initial mail . 2009-11-20 (A) resend initial mail translated, explained . 2009-11-20 (CM) OK, I'll take it as CM . 2009-11-27 (A) re-requesting CCR / DRP acceptance and statement from (R), deadline Dec 7th. . 2009-12-07 (R) is annoyed about requests. Wishes to remove his account. . 2009-12-07 (A) starting delete account procedure . 2009-12-08 (A): rcvd intermediate ruling exec report from support . 2009-12-25 (Werner Dworak): support requests progress report from (A) . 2009-12-25 (A): was busy with Assurance/Software Minitop, 2 ABC interceptions, 3 Policygroup special assurance programs pushing, one addtl. interception by PoJAM infos request arbitration and the handling of the slow-arbitrators case. Now back to the change account information cases. == Discovery == * from the general rule 'you can reduce information but never increase information' the removal of birthname 'Ressel' in the account name doesn't conflict with other assurances made * Delete Account request * account received 1 Assurance * user was not an Assurer, 0 Assurances * account has 0 certs * [[Arbitrations/Training/Lesson10|Arbitration Case -]] ---(Delete Account Request)--- case 1 - . [[Arbitrations/Training/Lesson20|Arbitration Case - Delete Account Request]] (moved to Lesson20 after renumbering 2010-02-05 u60) * ... with no assurances made and no cert has been created, support can remove the account, but as long as he has no access to the account, he cannot verify if certs are created under this account. Therefor support needs an order from an Arbitrator to get access to the account, to verify, that no certs are created. There is a feature request still open, that SE's can view from the webinterface admin console if certs are created. But this patch hasn't been applied yet. Until the patch is applied, the procedure has to follow the procedure below. See patch #794 visibility over certificates for sysadm in account administration * So either way, delete request must be handled thru arbitration process. * For details see: Arbitration case [[Arbitrations/a20080702.1|a20080702.1]], Delete Account: no assurances made, no certs created. Arbitrator: Philipp Dunkel === Family Name === I'd accept that "" and "" can be considered two different names, similar to multiple given names. So when applying the relaxed rules of the PracticeOnNames I'd consider the following family names as matching the docs in the sense of CAcert: * * * * - needs further investigations {{{ German law from 1994: Um die vielen Doppelnamen zu vermeiden, wurde 1994 das Namensrecht für Eheleute neu überarbeitet. Nach dem geschlechtsneutralen Namensgesetz (so der Name der neuen Richtlinie) kann sich das Ehepaar heute zwischen dem Geburtsnamen des Mannes und dem der Frau frei für einen gemeinsamen Familiennamen entscheiden. Neu ist auch, dass ein gemeinsamer Name gar nicht nötig ist, sowohl Mann als auch Frau können ihren eigenen Namen behalten. Entscheidet man sich für einen Familiennamen, kann der Partner, dessen Name nicht der Familienname ist, einen Doppelnamen führen. In welcher Reihenfolge die beiden Namen dabei verwendet werden ist egal. Dieser Doppelname kann jederzeit wieder abgelegt werden. Wichtig wird ein Familienname erst dann, wenn Kinder kommen. Dann muss man sich entscheiden, ob diese den Namen des Vaters oder den der Mutter bekommen. Letztlich dient dieser dann als FAMILIENname. Das gleiche gilt, wenn schon vorher ein gemeinsamer Familienname bestimmt worden ist. Übrigens: Doppelnamen sind für Kinder als Geburtsname nicht erlaubt. Deshalb ja auch die Gesetzesnovelle. Source: http://www.waswiewo.com/kategorie_d/Hochzeit_2424.html Date: 16.10.2009 }}} {{{ Namensführung bei Eheschließung Bei einer Eheschließung, bei der beide Partner deutsche Staatsangehörige sind, führen die Ehegatten Ihren Familiennamen nach dem deutschen Recht, hierbei ist auch keine andere Rechtswahl möglich. ... ... 3. Wahl eines Doppelnamens Die Eheleute bestimmen einen der Geburtsnamen zum gemeinsamen Ehenamen und der andere dessen Geburtsname nicht Ehename wird, kann dem gemeinsamen Ehenamen seinen Geburts- oder Familiennamenn hinzufügen. Ob voranstellen oder anfügen, dies ist Beides möglich. Eine Hinzufügung zum Ehenamen kann immer nur der Ehegatte mach, dessen Geburtsname nicht Ehename geworden ist. Die Hinzufügung bzw. Ablegung eines Doppelnamens ist jederzeit möglich, auch nach der Eheschließung. z.B. Herr Mustermann heiratet Frau Nix geb. Beispiel * Mann: Mustermann * Frau: Mustermann geb. Beispiel * Frau: Mustermann-Beispiel geb. Beispiel * Frau: Beispiel-Mustermann geb. Beipiel * Frau: Nix-Mustermann geb. Beispiel * Frau: Mustermann-Nix geb. Beispiel O d e r * Frau: Beispiel * Mann: Beispiel geb. Mustermann * Mann: Beispiel-Mustermann geb. Mustermann * Mann: Mustermann-Beispiel geb. Mustermann Source: http://www.hanau.de/lebeninhanau/familie/standesamt/eheschliessung/artikel/00827/ Date: 16.10.2009 }}} Translation (A): On marriage, where both parties are German citizens, the family names of both parties follows German laws. {{{ § 1355 BGB [1] ... Der vorangestellte oder angefügte Name und der Ehename werden wie bisher durch Bindestrich miteinander verbunden. ... Source: http://www.bonn.de/rat_verwaltung_buergerdienste/standesamt/heiraten/00715/index.html?lang=de Date: 16.10.2009 }}} Translation (A): The prefixed or annexed name and the familyname have to be hyphenated as hitherto [1] BGB Buch 4 - Familienrecht (§ 1355 BGB) http://www.buergerliches-gesetzbuch.info/bgb/1355.html {{{ English-speaking world Use husband's family name Historically, a woman in England would assume her new husband's family name (or surname) after marriage to him, and this remains common practice in the United Kingdom today as well as in common law countries and countries where English is spoken, including Australia, New Zealand, Pakistan, Gibraltar, Falkland Islands, Ireland, India, the English-speaking provinces of Canada, and the United States. ... Source: http://en.wikipedia.org/wiki/Married_and_maiden_names Date: 16.10.2009 }}} == Intermediate Ruling == * Request to Support * please close the account of (R) ASAP and please check following infos. * Got this user assurances ? yes/no * Did the user assure others ? yes/no * Has the user issued client certs? yes/no * Has the user issued server certs? yes/no * if issued client and/or server certs -> List of issued certificates and their expiration dates (If revoked please note but include) Only certificates with an expiration date in the future need be included. == Ruling == The case of this Arbitration started as a "Change Account information" request and ends in in the termination of the membership of the claimant in CAcert. Furthermore the claimant requested "I withdraw the membership" and "No more sending of Emails from CAcert please". Questions of reliance: 1. No reliance of others upon the claimant is likely 1. According to CAcert records no certificates were issued for the claimants account. 2. According to CAcert records no assurances were made by the claimant. By following the arbitration case [[Arbitrations/a20080702.1|a20080702.1]] as the precedence Therefore I rule this: 1. The membership of the claimant in CAcert is hereby terminated. 2. The account of the claimant is to be removed from all CAcert databases. 3. All proceedings of this arbitration will be published in the CAcert wiki. However all personally identifiable information of the claimant will be anonymized. 4. The personally identifiable information of the claimant will be retained by this arbitrator. 5. The personally identifiable information of the claimant is available to members of CAcert or another interested party by consulting with a future arbitrator. 6. The statement of "Non-Reliance" (see point 1 above. will be held by this arbitrator and is also available to all members of CAcert or other interested parties by consulting with a future arbitrator. Regarding the "No more sending of Emails from CAcert please" request, the respondent has to accept two further emails to correctly close this arbitration case. The ruling to this arbitration case and the account termination execute report from a Support Engineer. == Execution == . 2009-12-25 (A): sent ruling to (C), (R) . 2009-12-25 (A): execution request "Deactivate account" to Support * delete-an-account request * set a new password (and later forget) * hijack the account * fill the secret answers with junk * fill Givenname, Middlename, Lastname and Suffix with the arbitration case number * set DoB to 1900-01-01 and if this isn't possible then to 1970-01-01 * reset all special flags except the account blocked * delete all email addresses (except the primary email address) * delete all domains * change the account name by adding a new email address arbitration_a20090618.10@cacaert.org and deleting the original email address. * block the account * Please return the execution report in reply to this email to the CM and A of this case and also CC send the delete-an-account execution report to the respondent . 2009-12-26 (A): rcvd account delete order request execution confirmation from Support, cc'ed to (R) . 2009-12-26 (A): case closed == Similar Cases == || [[Arbitrations/a20090618.6|a20090618.6]] || [[Arbitrations/a20090618.6|User registered under abbreviated names]] || || [[Arbitrations/a20090618.5|a20090618.5]] || [[Arbitrations/a20090618.5|User requests to delete account with no Assurance Points]] || || [[Arbitrations/a20080702.1|a20080702.1]] || [[Arbitrations/a20080702.1|User requests to delete account with Assurance Points]] || || [[Arbitrations/a20090618.3|a20090618.3]] || [[Arbitrations/a20090618.3|Assurer requests to delete account]] || || [[Arbitrations/a20090826.1|a20090826.1]] || [[Arbitrations/a20090826.1|User wants account deleted, no Assurance Points, no certificates]] || == After Arbitration Close Note == * Link * [[Arbitrations/Training/Lesson10|Arbitration Case - Delete Account Request]] (Lesson 10) has been moved to Lesson 20 after renumbering 2010-02-05 (u60) * New Link [[Arbitrations/Training/Lesson20|Arbitration Case - Delete Account Request]] (Lesson 20) ---- . CategoryArbitration . CategoryArbCaseAccountDelNonAssurer . CategoryArbCaseAccountDataNameMismatch