Summary
Add the ability to categorize a group of domains in the registry as "forbidden to expire." These domains will either have no expiration date, or their expiration will be set into the 2040s to represent indefinite registration status.
Purpose
This feature is intended specifically for ccTLD (country-code Top-Level Domain) registries and does not match standard ICANN rules. Many ccTLDs have critical names, government, or infrastructure domains that are not meant to expire. The system should allow for a clear separation between these and normal expiring registrations.
Acceptance Criteria
- Domains can be marked (individually or in group) as 'forbidden to expire'.
- Marked domains should have no expiration date, or a far-future date (e.g., in the 2040s).
- Expiry checks and lifecycle logic must respect this setting.
- This ability must be restricted or clearly documented as non-compliant with ICANN registry policy. For ccTLD use only.
Notes
- Ensure audit logging for changes to/from this state.
- Code/documentation should clearly mention the intended, limited scope for ccTLDs.
- Provide documentation/example usage for operators.
Summary
Add the ability to categorize a group of domains in the registry as "forbidden to expire." These domains will either have no expiration date, or their expiration will be set into the 2040s to represent indefinite registration status.
Purpose
This feature is intended specifically for ccTLD (country-code Top-Level Domain) registries and does not match standard ICANN rules. Many ccTLDs have critical names, government, or infrastructure domains that are not meant to expire. The system should allow for a clear separation between these and normal expiring registrations.
Acceptance Criteria
Notes