Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Registrar Across Field Address Validation

Registrar Strawman Proposal

The  requires

requires registrars to validate and verify

defined

certain data fields,

such as

including phone number, email and postal address.

[1] Included

Included in the

validation

requirements

of the Specification

is the Across Field Address Validation (AFAV) requirement.

This is an open requirement for

AFAV requires registrars to validate the registrant’s postal address fields

, and confirm consistency

to confirm a practical relationship across fields, i.e

.g

. street exists in city, city exists in state/province, city matches postal code.

[2]

The 2013 Registrar Accreditation Agreement requires ICANN to review these requirements in consultation with the Registrar WHOIS Validation Working Group

[3] to

to identify a

feasible

set of tools that

shall

will enable accredited registrars to complete these validation actions. These actions should contribute to increased accuracy rating of physical address information associated with the registered name holder.

[4]ICANN has identified a set of commercial providers offering global address validation tool-sets.[5] If

To implement this requirement successfully, the Registrar WHOIS Validation Working Group and ICANN

are able to

must mutually agree upon a solution

(s)

that is technically and commercially feasible

all applicable documentation shall be published accordingly

. 

The objective of the Strawman Proposal is to gather feedback upon review and reach consensus regarding next steps between ICANN and the Registrar WHOIS Validation Working Group.  The Registrar WHOIS Validation Working Group and ICANN shall collaborate with the intent to reach a mutual agreement based on acceptable criteria. Upon acceptance, ICANN and Registrar WHOIS Validation Working Group shall proceed with the creation of an approval process of Address Validation Service Provider(s) ‘Provider’.   If both parties reach consensus and successfully complete these activities, then Registrars shall complete a Provider(s) selection process and implement the address validation tool-set(s) based on the obligation outlined in the WHOIS Accuracy Specification of the 2013 Registrar Accreditation Agreement.

 Read the complete document: AFAV Strawman Proposal .pdf

 

 

[1] 2013 RAA WHOIS Accuracy Program Specification, Section 1(a)-Section 1(e) for specific validation requirements and Section 1(f) for verification requirement.

[2] 2013 RAA WHOIS Accuracy Program Specification Section 1(e)

[4] Ability to verify physical addresses that are technically and commercially available by an approved third party.

[5] Identification of commercial providers was based on the suggested criteria outlined in the strawman proposal. The final criteria will be mutually agreed upon between Registrar WHOIS Validation Working Group and ICANN

In 2017, ICANN identified, via a Request for Information (RFI), a set of commercial providers offering global address validation toolsets. The intent of the RFI was to gather information in order to determine whether commercial providers offered feasible solutions. After review of the potential solutions available, mutual agreement between ICANN org and the WHOIS Validation Working Group was not achieved. 

ICANN org will continue to look for technically and commercially feasible solutions that will enable mutual agreement, as defined by a minimum of two-thirds (2/3) vote by ICANN-accredited registrars in support of the defined solution(s).

At present, implementation activities surrounding the AFAV requirement are on hold, due to issues surrounding data protection, the Temporary Specification on Registration Data, and ongoing related work among ICANN and community members.