ICANN RSP selection can wait until evaluation

RSP Selection Can Wait Until Evaluation, Not Indefinitely

Why it matters

ICANN’s 2026 rules allow an applicant to submit without naming Registry Service Providers, but that flexibility narrows at evaluation: minimum critical registry functions must be covered, or Extended Evaluation may provide more time.

Nia Okafor6 September 2026 at 07:13 UTCReading Time 1 minLast update: 6 September 2026

Three registry-service roles align between submission and the later evaluation boundary.

Summary

Applicants may submit without specifying RSPs, although ICANN encourages early identification.
By Applicant and Application Evaluation, they need providers covering at least the Main RSP, DNSSEC RSP and DNS RSP roles; Extended Evaluation may provide more time if that coverage is missing.

Section 3.1.10.1 of ICANN’s 2026 Applicant Guidebook separates submission flexibility from evaluation readiness. Applicants are encouraged to identify intended Registry Service Providers and services when submitting, yet they may submit without doing so and specify them just before Applicant and Application Evaluation.

The flexibility is not indefinite. If an applicant has not identified providers covering the required minimum critical registry functions by evaluation, Extended Evaluation may be selected to allow more time. Section 3.1.10.2 defines the minimum as a Main RSP, a DNSSEC RSP and a DNS RSP. One organization may qualify for more than one RSP type.

The rule does not show that a specific applicant is ready, that Extended Evaluation will be selected, or how long an extension would last. It also does not establish provider confirmation during contracting or eventual delegation.