Add per-domain automatic renewal with RFC 3915 grace period

Open
#2,968 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

@OlegPhenomenon is already working on this.

Since Oct 22, 2026.

  • #2974 by @OlegPhenomenon — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
ruby
Domain
api, backend, database

Research direction

Start by locating the EPP/REPP domain create, update, query, and renewal entry points, then trace the existing expiry, billing, transfer, and RFC 3915 grace-period behavior. The issue names no specific files or tests, so first map the affected backend components and existing test coverage. Done means the listed preference, renewal, refund, retry, transfer, and poll-notification rules are implemented and covered by backend tests; portal and documentation work is tracked elsewhere.

Written by the indexing model from the issue text.

Description

enhancement

Goal and delivery

Implement voluntary per-domain automatic renewal, including EPP/REPP interfaces, renewal and refund accounting, funding retries and registrar poll notifications. Default is off; registrars are not obliged to offer this service. Provide the integrated registrar test release by December 2026; production effective date is 18 January 2027.

This issue owns the shared business rules, protocol contract, database changes, workers, accounting, backend tests and release coordination. Portal and documentation implementations are tracked in their respective repositories and reference this issue.

Functional requirements
  1. Preference and interfaces. Allow the sponsoring registrar to enable/disable automatic renewal during domain create/update and query the preference and current cycle through EPP and REPP. Omitted create setting means false; omitted update setting means unchanged. Publish a versioned .ee extension for settings/reversal and support RFC 3915 info responses. Add scoped REPP portfolio filters for enabled domains, active grace periods and funding retries.
  2. Automatic renewal. At original expiry, renew for one calendar year and debit the registrar's prepayment account atomically. The new expiry is effective immediately. Set RFC 3915 autoRenewPeriod until 'original expiry'+15 days.
  3. Normal domain operations. The grace period itself must not block contact, nameserver, DNSSEC, registrant changes or registrar transfer initiation. Existing independent permissions, holds and prohibitions remain applicable.
  4. Reversal and refund. Disabling during grace reverses the automatic renewal, disables the preference and refunds the exact original charge to the original payer. Restore the original expiration timeline when no later paid period exists; preserve unrelated edits and independently purchased time. Cancellation does not itself delete the domain. An explicit cycle ID distinguishes reversal from future opt-out and makes repeated requests safe.
  5. Grace expiry. At 'renewal cancellation deadline', remove the grace status without another debit or date extension. The enabled preference remains for future years. After 'renewal cancellation deadline', opt-out only affects future renewals; an explicit expired-cycle reversal fails without partial changes.
  6. Insufficient funds. Retry within the autoRenewPeriod window. Under the proposed prepayment model, no renewal/debit/RGP status occurs until funds suffice; expose an internal retry state. A late success renews from original expiry and receives only the remaining grace window. At 'renewal cancellation deadline' with insufficient funds, stop retries, automatically disable the preference and notify the registrar. No refund is due if no debit succeeded. Later top-ups cannot restart that cycle.
  7. Registrar transfer. Disable the preference on successful transfer completion, including bulk/admin paths, not merely on a pending or failed request. Resolve already-paid automatic renewal settlement using the policy decision below. Do not charge the gaining registrar automatically.
  8. Poll notifications. Poll only for registry-initiated changes, errors and warnings that are not the direct result of a registrar request. Registrar-requested enable, disable, reversal/refund and their immediate validation errors are reported in the command response, without an additional auto-renew poll message. This includes portal actions submitted through REPP. Classify by business cause, not by which process executes the work: queueing a registrar command does not turn it into an unsolicited registry event. A future scheduled renewal under an existing opt-in is a registry-initiated event.

Document automatic renewal settings, reversal and status in REPP (https://github.com/internetee/repp-apidoc)

Document automatic renewal poll notifications (https://github.com/internetee/poll-apidoc)

Dominant language
Ruby
Stars
50
Forks
18
Avg merge
5d 3h
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from internetee/registry

All issues in internetee/registry

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.