- Case Number: a20100208.1
- Status: closed
- Claimants: Nis W
- Respondents: CAcert
Case Manager: UlrichSchroeter
Arbitrator: MartinGummi
- Date of arbitration start: 2010-02-09
- Date of ruling: 2010-02-25
- Case closed: 2010-03-01
- Complaint: Minor Name Change
- Relief: transliteration of name
Before: Arbitrator MartinGummi (A), Respondent: CAcert (R), Claimant: Nis W (C), Case: a20100208.1
History Log
- 2010-02-09 (issur.c.o): case [s20100208.129]
2010-02-09 (UlrichSchroeter): added to wiki, request for CM / A
- 2010-02-09 (CM): I'll take care about this case
- 2010-02-09 (CM): sent init mailing requesting CCA / DRP acceptance from (C)
- 2010-02-09 (C): I'll accept the CCA / DRP under this arbitration
- 2010-02-09 (A): I'll take care about this case
- 2010-02-09 (CM): forward of all mails to (A)
- 2010-02-22 (C): requests progress report
Discovery
- Request is about a simple transliteration within the name.
- There was no malfeasance of any type alleged or found.
- Assurers doesn't need to be questioned because the transliteration request from the original dispute filing indicates no conflict for the assurances that were made by the assurers in transfering points.
- The transliteration from Umlaut to 'oe' in the name is an allowed variant as by AP 2.2.
The CPS comes to draft at Status: DRAFT p20091108
- If the user has created client certificates, with the not yet corrected name in the account, the certs are built up with the untransliterated name from account.
CPS 3.1.1. Types of names - Client Certificates. The Subscriber Naming consists of:
- CN= The common name takes its value from one of:
- For individual Members, a Name of the Subscriber, as Assured under AP.
- CN= The common name takes its value from one of:
- Question: how untransliterated name in Cert influences transliterated name in account after name change?
Ruling
- The name in the Respondent's account shall be changed from "Nis Börge Wechselberg" to "Nis Boerge Wechselberg".
- Client Certificates that has been created by the user after 2009-11-08 and includes the untransliterated name in the cert, must be revoked by the user.
- Certs w/o name or certs w/o the untransliterated name part are not affected.
- User has to confirm in either way that no client certs exists or only certs w/o untransliterated name part or that he revoked such certs that are affected by this ruling with a CARS statement.
Lübeck, Feb 25th, 2010
Rationale
Related to matter Certs:
- If existing certs include the name with the untransliterated name part, those needs to be revoked. But users has the option to create certs w/o name or also Givenname + Lastname (w/o the Middlename), so the untransliterated name may not included in the cert. Those not conflicts by the name change.
- The question: how untransliterated name in Cert influences transliterated name in account after name change? affected by AP rule (Umlaut to transliteration allowed, transliteration to Umlaut not allowed) about transliteration only parts of the name, so therefor this ruling takes care about those differences.
Givenname Middlename Lastname -> Givenname Lastname are not affected. less informations in names not a problem.
Execution
- 2010-02-26 (A): sent out Ruling notification to (C)
- 2010-02-26 (A): please change name like ruling req. to Support
- 2010-02-26 (A): please revoke certs if needed, see ruling. please sent me feedback after this. to (C)
- 2010-02-26 (C): according to Ruling I just revoked all affected Client Certificates.
- 2010-02-26 (Support): name has been changed
- 2010-03-01 (A): all changes executed, case closed.
Similiar Cases