Dear All,
In the Tuesday WG meeting, the 'Ideal Process' Sub-Team presented a first rough outline of a possible process for change of control (see attached). Everyone is encouraged to review this outline and share it with their respective stakeholder groups / constituencies for input, if deemed appropriate. In addition to general comments, there are a couple of specific issues the sub-team would like to receive input on. These are highlighted in the attached document as 'note' and include the following:
- Decide on terminology of the process (e.g. Change of control vs. change of registrant, losing / gaining registrant vs. old / new registrant)
- Clarify / define difference between AuthInfo code and FOA in order to determine whether one or both could also serve as credentials in the case of a change of control (does somebody have a definition for either one)
- Clarify role of 'thick' vs. 'thin' registry in relation to providing / setting AuthInfo code AND/OR being capable to verify authorization for a transfer (it is our understanding currently that each registry using EPP can use Auth Codes, regardless of being thick or thin – does anybody have information that would contradict this?)
- Determine what can be used as transfer authorization credentials, the idea is that these will need to be produced and transmitted to the registry/registrar(?) by the new registrant (PIN, password, string, code, AuthInfo code) in order to prove that the previous registrant has given their consent to a transfer out
- Who provides notification to old and new registrant – gaining registrar, registry? In the case of thin registries, should both registrars or only the gaining registrar make this determination (in case the change of control is combined with a change of registrar)
- Should this process be conducted with the same authorization credentials or separate ones from existing ones such as the AuthInfo code, or should a combined model be explored?
Your comments would be appreciated ahead of next week's IRTP Part C WG meeting.
Thanks,
Marika