Corrected wording

Contact-Identity-Verification-Draft.md → Contact-Verification-Draft.md

@@ -1,10 +1,10 @@
-# Contact Identity Verification Draft
+# Contact Verification Draft
 
 Revision: 1.0
 Date: 2024-03-08
 
 ## Introduction
-This document serves as a draft design covering all technical aspects related to facilitating contact ID verification between registrars and Punktum dk, aligning with the NIS2 directive.
+This document serves as a draft design covering all technical aspects related to facilitating contact verification between registrars and Punktum dk, aligning with the NIS2 directive.
 
 NIS2 refers to the revised version of the Network and Information Systems Directive, a regulatory framework implemented by the European Union to enhance the overall cybersecurity posture of its member states.
 
@@ -21,45 +21,46 @@ The directive mandates OES and DSPs to report significant cybersecurity incident
 Cooperation and Information Sharing:
 NIS2 encourages collaboration and information sharing among member states, competent authorities, and relevant stakeholders. This cooperative approach aims to address cross-border cybersecurity challenges effectively.
 
-### Alignment with the Contact Identity Verification Draft:
-The Contact Identity Verification Draft has been designed with the principles outlined in the NIS2 directive in mind. By aligning with NIS2, the draft ensures that the contact ID verification process not only complies with technical and legal requirements but also contributes to the overarching cybersecurity goals set forth by the European Union.
+### Alignment with the Contact Verification Draft
+The Contact Verification Draft has been designed with the principles outlined in the NIS2 directive in mind. By aligning with NIS2, the draft ensures that the contact verification process not only complies with technical and legal requirements but also contributes to the overarching cybersecurity goals set forth by the European Union.
 
-In summary, the integration of NIS2 principles into the Contact Identity Verification Draft underscores the commitment to a standardized and secure approach in managing identity verification processes within the regulatory framework of the European Union.
+In summary, the integration of NIS2 principles into the Contact Verification Draft underscores the commitment to a standardized and secure approach in managing verification processes within the regulatory framework of the European Union.
 
 ## Requirements
 The primary objective of the proposed solution is to implement minimal changes to existing integrations, ensuring compliance with all legal and technical requirements. The solution should encompass the following key elements:
 
-1. Enable registrars to inform the registry about completed identity verification before registrant creation in the registry systems.
-2. Allow registrars to update the registry on identity verification status changes for existing registrants. This includes modifications to the existing registrant information, triggered by any changes in identity verification status (e.g., from 'pending' to 'verified' or 'verified' to 'unverified').
+1. Enable registrars to inform the registry about completed contact verification before registrant creation in the registry systems.
+2. Allow registrars to update the registry on verification status changes for existing registrants. This includes modifications to the existing registrant information, triggered by any changes in identity verification status (e.g., from 'pending' to 'verified' or 'verified' to 'unverified').
 3. Give registrars the ability to query the registry for the current identity verification status of all registrants under their management.
-4. Implement asynchronous messaging to update registrars on registrant identity verification status changes in the registry.
+4. Implement asynchronous messaging to update registrars on registrant verification status changes in the registry.
 
-## Setting Identity Verification Status for Registrar-handled Contacts
+## Setting Verification Status for Registrar-handled Contacts
 Punktum dk does not require detailed documentation on the actual ID verification performed by the registrar, as long as the verification aligns with the requirements outlined in the Registrar Agreement. Consequently, registrars are only obligated to include a verification status flag in the registrar create or update process.
 
 ### Registrar Portal
-A checkbox will be added to the handle creation page, allowing registrars to confirm that ID verification has already been performed.
+- Enable registrars to specify which verification model should be applied to their account (registrar verification vs. registry verification).
+- If registar verification is enabled on account, provide dropdown to specify verification status on the handle creation page.
 
 ### EPP (Extensible Provisioning Protocol)
 A new extension, `<dkhm:id-verification>`, will be incorporated into contact.create, contact.update, and contact.info. This extension will support values of `eid`, `verified`, `rejected`, `pending` or `undverified`, with no additional information required. The update triggered by this extension will include modifications to existing contact information based on changes in ID verification status.
 
 ## Supported Identity Validation Statuses
 
-- `eid` indicates that identity control has been completed using electronic identification.
-- `verified` indicates that identity control has been performed, and relevant documentation has been reviewed and approved by Punktum dk.
-- `rejected` indicates that identity control has been performed, and relevant documentation has been reviewed and rejected by Punktum dk.
-- `pending` indicates that identity control has been requested and currently awaits a response from the contact.
-- `unverified` indicates that identity control has not been completed nor initiated on the contact. Setting this value on contact.create commands specifies that Punktum dk is requested to handle the identity verification process. For contacts residing in Denmark, this automatically triggers a request for identity verification using MitID, whereas foreign contacts will be subjected to a risk-based evaulation of the provided data, and a manual identification requests will be initiated, if deemed necessary by the risk evaluation results.
+- `eid` indicates that verification has been completed using electronic identification.
+- `verified` indicates that verification has been performed, and relevant documentation has been reviewed and approved by Punktum dk.
+- `rejected` indicates that verification has been performed, and relevant documentation has been reviewed and rejected by Punktum dk.
+- `pending` indicates that verifcication has been requested and currently awaits a response from the contact.
+- `unverified` indicates that verification has not been completed nor initiated on the contact.
 
-The reason for distinguishing between electronic and documentation-based means of identification is due to the fact that using eID solutions provides instantaneous verification of the contact, compared to document-based identity verification, where a waiting period will occur while awaiting receiving documentation from the contact.
+The reason for distinguishing between electronic (eID) and documentation-based means of verifcation is due to the fact that using eID solutions provides instantaneous verification of the contact, compared to document-based identity verification, where a waiting period will occur while awaiting receiving documentation from the contact.
 
 In cases where Punktum dk is responsible for performing the verification process, the `pending` status will be relevant to allow the registrar to follow the ongoing status of the verification process.
 
-## Notification of Identity Verification Status Changes
-As the verification handled by Punktum dk requires actions to be performed by the contact, the registrar needs to be informed as soon as the identity verification status changes. Notifications on status changes will be issued to the registrar without delay via poll messaging or email, based on the specific communication settings configured in the Registrar Portal.
+## Notification of Verification Status Changes
+As the verification handled by Punktum dk requires actions to be performed by the contact, the registrar needs to be informed as soon as the verification status changes. Notifications on status changes will be issued to the registrar without delay via poll messaging or email, based on the specific communication settings configured in the Registrar Portal.
 
 ## Limitations
-* Registrars are only able to provide statuses `eid`, `verified` and `unverified` during contact creation. `pending` and `rejected` are statuses reserved for Punktum dk identity verification process.
+* Registrars are only able to provide statuses `eid`, `verified` and `unverified` during contact creation. `pending` and `rejected` are statuses reserved for Punktum dk verification process.
 * After a contact has been assigned the status of `eid` or `verified`, these statuses are immutable and cannot be altered
 
 ## Questions