Page History
...
[1] ICANN Security and Stability Advisory Committee (2011), SSAC Advisory on Domain Name WHOIS Terminology and Structure (SAC 051). Available: < http://www.icann.org/en/committees/security/sac051.pdf>
[2] ICANN, “IDNs Glossary,” Retrieved August 10, 2010, <http://www.icann.org/en/topics/idn/idn-glossary.htm>.
[3] P. Hoffman and J. Klensin.,.“Terminology Used in Internationalisation in the IETF”, RFC 6365, September 2011..
[4] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, August 2010.
From SAC058: SSAC report on Domain Name Registration Data, 27 March 2013, http://www.icann.org/en/groups/ssac/documents/sac-058-en.pdf
3. Taxonomy of Validation
Verification, validation and resolution have been used interchangeably in various literature on this topic. We choose “validation” to refer to the assessment of data as described by this document. Verification in this document refers to the process of validating. Resolution has an entirely different technical meaning that is out of scope for this document. The SSAC asserts there are three types of validation for elements of the registration data.
1. Syntactic Validation refers to the assessment of data with the intent to ensure that they satisfy specified syntactic constraints, conform to specified data standards, and are transformed and formatted properly for their intended use. For example, if the data element is expected to be an email address is it formatted as an email address? In general, it is expected that syntactic validation checks would be entirely automated and could be executed inline with a registration process, follow up information reviews, and whenever registration data changes.
2. Operational Validation refers to the assessment of data for their intended use in their routine functions. Examples of operational validation include 1) checking that an email address or phone number can receive email or phone calls; 2) checking that a postal address can receive postal mail; 3) checking that the data entered are self-consistent, i.e. that all data are logically consistent with all other data. It is expected that many operational validation checks would be automated and some could be executed inline with a registration process.
3. Identity validation refers to the assessment that the data corresponds to the real world identity of the entity. It involves checking that a data item correctly represents the real world identity for the registrant. In general, identity validation checks are expected to require some manual intervention.
